ultracycling!Speaking of out-of-network content, btw, it's also what shaped Bluesky's architecture to a substantial degree. It was built from the outset on the assumption that people need to see posts from outside of their network, that it's an essential non-negotiable property that this system must have.
 5 comments
So since Bluesky assumes that most users want to see posts by strangers chosen by some sort of algorithm, which picks them out of the entire pool of content on the platform, then, well, you need the entire pool of content on the platform to pick posts from. Hence the unwieldy "shared heap" architecture. ActivityPub's publish-subscribe approach would've been a serious nuisance if you were to build such a product on top of it. @grishka conveniently, that also makes advertising a lot easier, and raise the bar of competition much higher. Hard to say it’s bad, after all they are just delivering to what people ask for. Today, we are spoiled by the endless feed, and increasingly comfortable with being profiled by algorithms (instead of talking about hobbies, many ask each others “what’s your algorithms”). |
That's the fundamental difference between Bluesky and the fediverse. Bluesky tries very hard to emulate the current commercial television-like passive-consumption entertainment-ass social media. Fediverse, on the other hand, takes an old-school user-friendly approach where you see the posts from people you follow, in the order in which they were made, and nothing else at all. If you really insist on seeing random posts from people you don't know, there are local and federated timelines.