Graph showing the centralization of the Mastodon platform on Mastodon.social

https://social.growyourown.services/@FediGarden/115587663680180965

78 points · 16 comments · view on lemmy.world

16 Comments

jaggedrobotpubes@lemmy.world · 26 pts · 271d (3 replies)

Easiest answer would be some kind of small FOSS tool/script that makes switching instances easy and automated. Make it easy for people already on there to do their part towards fixing this in three clicks if they want.

olorin99@kbin.earth · 20 pts · 271d (1 reply)

Mastodon already natively supports moving profiles between instances. https://docs.joinmastodon.org/user/moving/

IanTwenty@piefed.social · 2 pts · 270d

Posts don't move with you though (yet?)

stinerman@midwest.social · 5 pts · 271d

100%. Make migrations really easy and the problem fixes itself. To the extent people want to leave m.s. Some people don't want to leave and trying to force them to or make it impossible to join m.s is a great way to push people to nonfederated social media.

Skavau@piefed.social · 17 pts · 271d

It's interesting to see how the Fediverse has gone the opposite way, with Lemmy.world in slow decline as a proportion of active users.

ICastFist@programming.dev · 13 pts · 271d

They'd do good to close down registrations for some months, let other servers grow

rimu@piefed.social · 10 pts · 271d (1 reply)

Mastodon.social is too big to defederate. Any instance that does would be undesirable to most people.

What is the point where a network is too concentrated? My gut feeling is its when 1 instance is more than 33% of the active users. Ideally 10%?

Blaze@piefed.zip · 5 pts · 271d

In Threadiverse, on top of active users, you have to account for active communities. But yes, 10% feels right

Xylight@feddit.online · 8 pts · 271d (1 reply)

Mastodon and ActivityPub in general really need a way to move profiles, not just migrate. I don't want to have 8 different split comment/post histories and inboxes if an instance fails. This is supposedly the problem ATProto was made to fix but we see how that turned out

Sergio@piefed.social · 8 pts · 271d

Anecdote: I joined Mastodon about a year ago, bc I wanted to participate in the monsterdon watch party. After about a month of "analysis paralysis", I joined a non-mastodon.social instance. And I participated in the watch party, i.e. commenting as we all started watching a movie at the same time. But all my posts showed up like 3-4 hours late! So I made an account on mastodon.social and have been there since.

OpenStars@piefed.social · 6 pts · 271d

So obviously the devs are going to start listening to users and make following accounts and searching for content across instances easier and more streamlined... r-r-right?! RiGhT?!???????

There is a reason that things happen. Oh well, hopefully they pull their heads out of their asses before Bluesky pisses off its user base and they miss yet another major migration wave.

eleijeep@piefed.social · 3 pts · 270d

The graph doesn't actually say what the y-axis is showing. Percentage of what? User accounts? Active user accounts? Posts? Interactions?

If mastodon.social is the default instance for new users, it could just have a load of inactive accounts of people who tried it and didn't stick. Or it could have the same number of accounts as others, but the accounts are just way more engaged in posting.

It's impossible to tell from this graph.

ArcaneSlime@lemmy.dbzer0.com · 1 pts · 270d (2 replies)

Hey this actually might be a good place to ask this!

SO I have a mastodon acct but the server admin limits cache to 2w for other servers, so posts on my instance last forever and I can see the entire history of my fellow server denizens, but for everyone else I can only see the last 2w.

I'm not leaving my main acct but I would however like to create an account on a server that will let me go back the farthest on other servers. The problem so far I've run into is that all the "joinmasto [.] com" type sites do not mention cache just a short blurb about the server and the number of accts.

Does anyone have any good recommendations for a server that would work for me?

cornshark@lemmy.world · 1 pts · 270d (1 reply)

What about mastodon.social?

ArcaneSlime@lemmy.dbzer0.com · 1 pts · 270d

That is a contender (based solely on assumptions, as I have no idea their cache retention in reality, I just assume it's probably "yes.")

But then, this post is right, centralization and such. If there is another applicable instance I'd likely pick that one first, though if I can't get any info on it I'll surely try .social first.