> I always found what Bluesky was "optimizing" for to be a stupid goal, and inherently a bad idea -- namely "the ability to keep your everything permanent."
Not only that, but also having a globally (eventually) consistent view of every conversation from every server. Unlike the "message passing" model used by email and ActivityPub, this means that every server has to carry all the traffic of the whole network (i.e., to be prepared to be a centralized service for the whole world). This is the main reason ATProto is mostly centralized - every alternative server has to be global scale, and who wants to bother with that just to show exactly the same content that Bluesky Inc does?
Holy. Moly. I had no idea that this was another goal. That's ridiculous to try to do at the protocol level.
What I'm realizing, perhaps as an old timer -- projects like this seem to utterly forget the concept of "layers," despite, you know that being the whole internet, OSI and whatnot.
I remember having the idea that even this exact use case, air-quotes "twitter", could be done by simply layering something over email, e.g. you shoot an email to "posty-instance@myserver" or whatever and then some central-ish thing posts that to a public feed or whatever.
So much unnecessary reinvention.