What is Nostr?
Yumechi | ゆめち :ferris: :haskell: :role_ojousama: /
npub1s5h…qgkp
2024-10-19 09:26:15

Yumechi | ゆめち :ferris: :haskell: :role_ojousama: on Nostr: https://arxiv.org/pdf/2402.03239 Where is a path from the posters on the left to the ...

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: npub13mmlujflnk49ey67ak9da8jvv0cezhwusat4dsvgzkctlas4enlqk9zqqt (npub13mm…zqqt) she pointed out some issues with identity federation in BS as well.

#federation #activitypub

https://mi.yumechi.jp/files/82331b3d-7752-4d84-ae6a-e38bf301dc1f
Author Public Key
npub1s5h3t3yqn8h54jngg5h9ruke5ykhpv7zeeqhkfwedrl9hxy6f5css7qgkp