In the early days of the fediverse user numbers (aka hosting costs) were low and enthusiasm was high.
Admins made their instance because they wanted to. Moderators volunteered because it felt meaningful (or whatever). We all had similar values and vibes were good. When the hat was passed around everyone happily threw a few bucks into it. Setting up a small instance can be done fairly easily by using a pre-configured docker image so only basic linux skills were needed.
All that is about to change.
The underlying protocol is chatty
ActivityPub, the language used by instances to synchronise, is inherently inefficient.
Let’s imagine a person who has 500k followers spread across, let’s say, 10k servers. Each post that such a person sends creates 10k Sidekiq jobs. Each interaction—another 10k Sidekiq jobs. If the post gets popular and gets 1k boosts (that’s 1/500 of the total followership of that person) in a short period of time, we’re talking about 10M Sidekiq jobs. And all of that needs to be coordinated by one server. More on this.
This is ok when user numbers are low. What’s going to happen at 100 million users?
Mastodon is a heavy app
At a minimum, a Mastodon instance needs about 4GB of RAM. Here is an attempt to make it work on less. This can only increase as user numbers do.
A medium-sized instance (by today’s standards, which will be a micro instance next year) can easily use 1 TB of storage https://hub.fosstodon.org/more-upgrades-twitter-storm/ and cost about $2000/mo to run, with everyone involved unpaid.
The effort & skill involved in running an instance will increase
Pretty quickly we find that the default installation of Mastodon is not suitable and various upgrades and reconfigurations need to be made, requiring a skilled administrator to correctly identify where the bottleneck is and what to do about it. The changes described here are not rocket science but going beyond that into more complex scenarios is going to require people with lots of experience and a professional background. Thousands of them.
Cultural changes are inevitable
At the same time, the nature of the user base is changing. Early on the fediverse was populated by people who chose to be there because of strong feelings about FOSS, ads, privacy and so on. We’re now seeing people arrive who are revolted by what twitter has become but who were quite happy there before even with all its ads, surveillance and racism. While these people are far greater in number they will be less likely to pony up a few bucks when their server needs to eat. Future, much bigger, waves will be people who would prefer to use twitter et al but who no longer have a choice because twitter is dead. If their fediverse admin is running out of money or starting to charge a subscription they’ll just move to a different server.
It’s possible that the blossoming of our lives due to the awesomeness of the fediverse will be of such obvious benefit that people of all waves willingly support their instance’s patreon account and we all live happily ever after. But anyone who has been to a city knows that as the population goes up the friendliness goes down.
Volunteers burn out. People with specialised skills are rare and in high demand. Sooner or later, bills need to be paid. How are we going to do that?
Ads – an anathema to us and without tracking and creepy AI unlikely to be very attractive to advertisers.
Subscriptions – sort of like $8 per month for a blue tick, isn’t it.
Patrons – universities, municipalities, philanthropists. What’s in it for them?
How do you think this is going to work out?
I remain very hopeful. We’re off to an amazing start with the best people involved and a great vision.
I’m hopeful too. In my case, I kept planning on joining mastodon, but didn’t want to stop following some people on twitter. The twitter exodus got some communities to branch out to mastodon, which made the switch easier for me.
More along these lines:
Concerns about scalability of ActivityPub: https://gist.github.com/jdarcy/60107fe4e653819138396257df302eef
Governance of the Fediverse:
Collectively owned instances:
Comments are closed.