I’s heard news that BlueSky has been growing a lot as Xitter becomes worse and worse, but why do people seem to prefer BlueSky? This confuses me because BlueSky does not have any federalization technologies built into it, meaning it’s just another centralized platform, and thus vulnerable to the same things that make modern social media so horrible.
And so, in the hopes of having a better understanding, I’ve come here to ask what problems Mastodon has that keep people from migrating to it and what is BlueSky doing so right that it attracts so many people.
This question is directed to those who have used all three platforms, although others are free to put out their own thoughts.
(To be clear, I’ve never used Xitter, BlueSky or Mastodon. I’m asking specifically so that I don’t have to make an account on each to find out by myself.)
Edit:
Edit2: (changed the wording a bit on the last part of point 1 to make my point clearer.)
From reading the comments, here are what seems to be the main reasons:
- Federation is hard
The concept of federation seems to be harder to grasp than tech people expected. As one user pointed out, tech literacy is much less prevalent than tech folk might expect.
On Mastodon, you must pick an instance, for some weird “federation” tech reason, whatever that means; and thanks to that “federation” there are some post you cannot see (due to defederalization). To someone who barely understands what a server is, the complex network of federalization is to much to bare.
BlueSky, on the other hand, is simple: just go to this website, creating an account and Ta Da! Done! No need to understand anything else.
The federalized nature of Mastodon seems to be its biggest flaw.
The unfamiliar and more complex nature of Mastodon’s federalization technology seems to be its biggest obstacle towards achieving mass adoption.
- No Algorithm
Mastodon has no algorithm to surface relevant posts, it is just a chronological timeline. Although some prefer this, others don’t and would rather have an algorithm serving them good quality post instead of spending 10h+ curating a subscription feed.
- UI and UX
People say that Mastodon (and Lemmy) have HORRIBLE UX, which will surely drive many away from Mastodon. Also, some pointed out that BlueSky’s overall design more closely follows that of Twitter, so BlueSky quite literally looks more like pre-Musk Xitter.
As a layman, I promise you “write your own algorithmic code” is not a feature that would compel me to sign up for a service
I was thinking along the lines of being given a list of popular algorithms, but if you find an algorithm you like on another instance you can copy it over to your instance. So it is not necessary to write code and nearly nobody would do it, they would just use ones that other people created.
But I realize this is an extremely difficult request so I’m not really serious when I propose it.
I think it would be an awesome feature but like you said, just not something that is going to sway a typical social media user to give it a shot. But I can see it being a really cool way for advanced users to really customize their experience.
Oh yeah this has little to do with the original question about why bsky is more popular. This suggestion of “let people write their own algorithms” is for the devs who think algorithms are harmful. They aren’t harmful if you give users the power to choose their own algorithm. Techie people can write the algorithms and non-techie people can choose them. Chances are a few algorithms would eventually become the most popular and very few would be written after that, but the point is you let the users decide instead of the Mastodon devs having to write the algorithms.
And now I realize bsky actually has something like this: Custom Feeds. If I understand correctly, they get around the “running untrusted code” issue by not running the code on bsky servers. Instead whoever wrote the custom feed gets the data from bsky, runs the algorithm on a separate server, then returns the custom feed. Pretty clever. https://docs.bsky.app/docs/starter-templates/custom-feeds