Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Yumechi | ゆめち | :ferris: :haskell: Wheel Inventor (yume@mi.yumechi.jp)'s status on Saturday, 19-Oct-2024 18:32:21 JST Yumechi | ゆめち | :ferris: :haskell: Wheel Inventor

   https://arxiv.org/pdf/2402.03239
   
   Where is a path from the posters on the left to the viewers on the right that does not go through BS's infrastructure?
   
   Even with a "custom App View" as they described (which, interestingly, they did not publish a reference implementation AFAIK)
   
   The only thing "federated" here is user data itself... Federated user data does not equal to a federated social media.
   
   Every communication has to go through and filtered by an App view (hosted by BS or not). It is the App view's job to keep track of and figure out who follows/blocks who and "multicast" the message in a user->user manner (they openly admit it in page 5), how is this federated?
   
   Essentially, I feel this is not "Usable Decentralized Social Media" but a "Centralized Social Media that feels Twitter but Decentralizes Data"
   
   CC: @lhc_fl@stelpolva.moe she pointed out some issues with identity federation in BS as well.
   
   #federation #activitypub