> But I see absolutely no reason to expect the platform to avoid the problems that Twitter encountered as it grew (and Mastodon fostered as it failed to grow).

> But I see absolutely no reason to expect the platform to avoid the problems that Twitter encountered as it grew (and Mastodon fostered as it failed to grow). Its own “federated protocol”—literally the entire reason it was built, and the main/only technical pitch in its early days—is totally irrelevant. 100% agree. There's no technical reason to use bsky - people are there mostly for the ... people. It has turned into another echo chamber; but that's probably what everyone wants. In my view, true decentralized networks (which would be great) won't take off until the Direct Sockets API [1] (or similar) and the File System API [2] are adopted across browsers. Chrome (and Edge et al) has had them for a while now. Add: Why do I think it won't work? In my view, federation is a compromise because p2p isn't possible right now. Federation brings all sorts of issues w.r.t. identity and portabilty. Users just want to talk to other people, and p2p is the simplest abstraction for it. Bluesky is as of now a centralized service, no different from Twitter. We're still waiting for the Napster moment. [1]: https://wicg.github.io/direct-sockets/ https://wicg.github.io/direct-sockets/ [2]: https://developer.chrome.com/docs/capabilities/web-apis/file-system-access https://developer.chrome.com/docs/capabilities/web-apis/file...