A major difference with Bluesky tho, is that users can choose their own "algorithm". Nobody is forced on Discover (Bluesky's "for you" algorithm).
I wonder if this will play a role.
I wonder if this will play a role.
I likened it to 2003, when people fled Windows for the MacBook over issues like crapware (which: the X algorithm basically is). And: a lot of early MacBook adopters, most especially the ones that had been there for a long time, were insufferable! But we hit a point where one product was clearly better than the other, and you roll the tape forward and see how good the long-term prospects are for the niche product that just does what all its real users actually want it to.
Hard to imagine why someone would go through so much trouble to acquire Twitter just to Ballmer-ize it. You usually have to have started and built up a product yourself to screw it up this badly.
That said, this might be different on phones than on the web app.
To your larger point, I think BlueSky is hobbled right now by the religious committment to decentralization, which the new arrivals don't care about at all. I would compare the situation to a world where people had to flee Windows for Linux—neither alternative is one that just works the way you'd want it to.
Not enough people stayed in the Fediverse, and I found early Bsky culture, hm, difficult to mainline day-in day-out, so I went back to Twitter, and I'd be fine, regardless of ownership, if it would just be a good product that everyone wanted to use.
So to me, Bsky just felt like Twitter with different owners; it still sort of does. Which: if you're looking for a less-shitty Twitter, to me, that's Bsky's offering today.
I'm sure there are additional limitations, too. All of these stem from highly religious architectural choices that are of no interest to 99% of the current user base, who just want pre-Musk Twitter back. The obvious endpoint is what happened to email—there will be one central provider who can set arbitrary policy, and the decentralization part will just linger on as a series of annoying hoops that developers have to jump through to work with the de facto centralized site.