Conversation

Notices

1. Embed this notice
   wakest ⁂ (liaizon@social.wake.st)'s status on Friday, 28-Jun-2024 20:05:00 JST wakest ⁂

   Threads implements #Misskey's `_misskey_quote` standard and gives them a shutout in the Facebook Engineering blog and then *blocks them* for "No publicly accessible feed" which is a completely baseless reason for blocking a server.

   "We chose _misskey_quote because its naming makes it clear that it’s not an official ActivityPub method, and because we know that it’s supported by Misskey, Firefish, and potentially other servers that use quote posts." https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse #fediverse #threads

   • clacke@libranet.de is my main likes this.
   • Embed this notice
     Blurry Moon (sun@shitposter.world)'s status on Friday, 28-Jun-2024 20:04:59 JST Blurry Moon

     in reply to
     @liaizon they block people for stupid reasons so
   • Embed this notice
     lainy (lain@lain.com)'s status on Friday, 28-Jun-2024 20:11:28 JST lainy

     in reply to
     @liaizon and with that, all hope for semantically meaningful AP on the wire ever dies
     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     wakest ⁂ (liaizon@social.wake.st)'s status on Wednesday, 10-Jul-2024 14:37:31 JST wakest ⁂

     in reply to

     • aliceif

     @aliceif cause its the instance thats run by the Misskey project itself and by the person who started misskey and made the standard that threads is using...

     clacke@libranet.de is my main likes this.
   • Embed this notice
     aliceif (aliceif@mkultra.x27.one)'s status on Wednesday, 10-Jul-2024 14:37:32 JST aliceif

     in reply to

     @liaizon@social.wake.st why you are equating misskey with that server on the .io TLD here?