I've had a lot of people ask how BlueSky compares to Mastodon and the Fediverse. I've tried to make the answer as simple and easy to understand as possible:
BlueSky is designed to give corporations and wealthy people full control of the network. All of its traffic has to flow through expensive-to-run corporate relays.
The Fediverse is designed to give ordinary people control of the network. All of its traffic flows directly from one cheap-to-run server to another.
@FediTips The thing that is missing from your diagram is that while #Fediverse servers CAN communicate with each other, not all of them DO. This is most noticeable when you follow a #hashtag - If you are on a large, well connected instance you will see many (maybe almost all) posts containing that hashtag. If you are on a small instance, or an instance that is not well connected (for whatever reason) you will see only a small percentage (maybe close to 0%) of the posts made using that hashtag.
In situations like that, from the user's perspective the #Bluesky / AT protocol is superior, because with the centralized server and corporate relays pretty much anything posted using a given hashtag will be seen by all those who follow that hashtag.
I'm not saying we all should move to Bluesky. I'm saying that this is a problem that needs to be solved by whoever writes the software for #Mastodon and similar Fediverse instances. And if there already is a solution but few instances are using it, what is that solution and where can you find a list of instances that are already using it? I understand there will always be some blockages because instance operators don't want traffic from certain types of instances, but I'm not talking about that, I am talking about cases where a post with a hashtag doesn't reach your instance because no one using your instance is specifically following the user that made that post.
There are various ways to make any Fediverse server see a lot more of the Fediverse:
https://fedi.tips/using-relays-to-quickly-expand-a-servers-view-of-the-fediverse/
@FediTips @kryptec Right, but as a USER I have no way of knowing if the instance I am using has implemented any of those. How about publishing a list of such servers? And if you have no way of knowing which servers are using any of those various ways, then how is the user supposed to know? A solution that few instances are using and/or where users have no way of knowing if their instance (or any other) is using that solution adds a level of complication and annoyance that you don't have with the big corporate platform.
The idea isn't to have a listed set of features, it's just to provide more posts visible to the instance.
Also, the user themselves can implement things like following groups which totally bypass whatever their instance can see. If you follow a group, you will see the same posts no matter which instance you are on. It's the same if you follow a particular set of accounts, the act of a user following an account changes which posts are visible to the user's instance.
@FediTips Well the problem with groups is that you first have to know that a group you are interested in exists, and then chances are if you do find one it's not specific enough. Say I am running some piece of software that is giving me trouble, I can subscribe to a hashtag with the name of that piece of software, which (hopefully) will only show me posts related to that software, although that is not always the case, for example if I want to see posts about Joplin (the note taking application) I could use (hashtag)Joplin and hopefully I would get mostly posts about that software and not Joplin, Missouri or Scott Joplin the composer.
But will there be a group about Joplin? Probably not. And also, as I understand it, groups follow users, not hashtags. And in that case you can get inundated with posts that are not about the topic of interest. I have tried to follow groups a few times and generally speaking I've had to turn them off almost immediately because they flooded my timeline with uninteresting and irrelevant posts.
I think we might be talking about different kinds of groups? A lot of different services on here have used the name "group".
Groups from services like Guppe are basically just "super hashtags". If you mention the group, the post is distributed to everyone that follows the group on any server. You can make a new group just by mentioning it.
If someone spams the group with irrelevant content, they can be reported for spamming (just like they can be with hashtag spamming).
@FediTips Well there is a chicken/egg issue there, far more people are likely to use a hashtag than a group mention, and that is because they are familiar with hashtags from the dead bird site and other existing social media platforms.
So again taking Joplin (the software) as an example, chances are there is no existing group for it, and yes I could easily create one but chances are all I'm going to get is crickets because other people who post about Joplin will be using the hashtag (with which they are familiar) and not the group identifier.
Basically what I am hearing is "we can't make hashtags work the way they are supposed to in the Fediverse, so here is this substitute that few users have heard of and even fewer will actually use", rather than "we really need to fix the fediverse software so that hashtags work as they are supposed to."