My Problems with Mastodon
Even with growing pains accommodating an influx of new users, Lemmy has made it clear that a federated social media site can be nearly as good as the original thing. I joined Lemmy, and it exceeded my expectations for a Reddit alternative run by an independent team.
These expectations were originally pretty low when Mastodon, the popular federated Twitter alternative, was the only federated social media I had experience with. After using Lemmy, Mastodon seems to be missing basic features. I initially believed these were just shortcomings of federated social media.
-
Likes aren’t counted by users outside your instance, and replies don’t seem to be counted at all (beyond 0, 1, 1+), leading to posts that look like they have way more boosts (retweets) than likes or replies:
This incentivizes people to just gravitate toward the biggest instance more than people already do. My guess is that self-hosting a mastodon instance would also not be ideal, since the only likes you’ll see are your own.
-
There’s really only one effective ways to find popular or ‘trending’ posts. There’s the explore tab which has ‘posts’, and ‘tags’ sections.
The ‘posts’ section shows some trending posts across your instance and all the instances that it’s federated with, this is the one I use it the most.
The ‘tags’ section is a lot like the trending tab on Twitter, but it’s reserved just for hashtags, which I guess isn’t a huge deal, but it feels like a downgrade. However, I do like the trend line it shows next to each tag!
The ‘Local’ and ‘Federated’ tabs are a live feed of post from your home instance and all the other instances, respectively. I feel these are pretty useless and definitely don’t warrant their own tabs. Having a local trending tab for seeing popular posts on your instance would be more interesting.
-
The search bar basically doesn’t work, is this just me???
-
This one is more minor and more specific to a Twitter alternative, but when looking at a user’s follows, you’ll only see the one’s on your home instance but for some reason this rule doesn’t apply to followers.
From what I’ve heard, a lot of these issues are intentional in order to create a healthier social media experience. Things like less focus on likes, reduces a hivemind mentality, addiction, things like that (I couldn’t find a source for this, if anyone has one confirming or disproving this please lmk).
Why this is a Problem
Mastodon seems to have two goals: To be an example of how a federated alternative to Twitter can work well, and to be a healthier social media experience. It’s not obvious, but I think these goals conflict with each other. A lot of the features that are removed in the pursuit of a healthier social media will be perceived as the shortcomings of federation as a concept.
In my eyes, Mastodon’s one main goal should be proving federated social media as a whole to the public, by being a seamless, familiar, full-featured alternative to Twitter. For me, Lemmy has done that for Reddit, upvotes are counted normally, you can see trending posts locally and globally same with communities, and the search function works! All its shortcomings aren’t design flaws, and I fully expect them to be fixed down the road as it matures.
As annoying as Jack Dorsey is, I have high hopes for BlueSky.
So users viewing this post on another instance will see the same exact comments and upvotes?
Hi from lemm.ee👋
Indeed, at least that’s the idea. Viewing and posting from kbin.social.
My understanding is yes, but only if the instances have federated with each other.
That’s the idea, but in practice since the data exists independently on each server, it takes network time and computational time for them to align. In practice I expect comments to function as you expect, and upvotes to be slightly off depending on which instance you’re viewing from.
Things get a bit more weird when an instance gets defederated from another instance. My understanding here is that if you have instance A defederate from instance B, but instance B was listening to some of instance A’s communities, that instance B will have an independent replica of that community that doesn’t sync (this happened when beehaw defederated from open registration instances like lemmy.world).
Hello from feddit.de 👋
It’s aboot time something worked so well innit?
-lemmy.ca
Hello from kbin.social 👋
Yes, on my instance for example your comment has 10 upvotes and 7 replies - the same counts are reflected on the origin instance
lemmy.world
.sh.itjust.works user here :)
Hi from feddit.nl 🙌!
Hello from zerobytes.monster 👋