4 ms·
I don't see anything here that is backed up with anything other than more dubious opinions. When it comes to scaling in particular, we have a counter-example i
by vidarh 4y ago
I don't see anything here that is backed up with anything other than more dubious opinions.
When it comes to scaling in particular, we have a counter-example in e-mail which shows scaling an inbox model + reflection (mailing-lists) to a follower-list can scale to a vastly larger audience. Of course it can, given that it decomposes neatly into a trivially parallelisable set of components of a well understood nature.
It was when Twitter was still getting their fail whales, sometime around 2007, I first pointed out that parallel (might even have been on HN). There are some tricks to avoiding lag in presentation for accounts with huge numbers of followers, but there decentralisation already serves to turn a flat list of followers into a tree of instances -> subsets of followers per instance, and if/when any instances gets to a size when scaling a single instance becomes problematic, then decomposing into a virtual federated set of instances presenting a unified namespace solves that just fine (have built a mail setup doing just that - mapping <user>@<domain> to <user>@<backend shard> is not hard)
The issue of "unpaid Labour" and peoples lack of desire to self host also depends on an assumption that Mastodon is inherently tied to unpaid volunteers or self hosting, but you can already pay for Mastodon hosting, and more options are sure to appear if it keeps growing. And the largest Mastodon instance is run by a non-profit getting paid by sponsorships already.
And this goes straight to the issue of what happens when someone popular joins an instances and/or trust: No instance needs to accept someone who brings undue load without expecting donations or charging or just turning them away, but the converse is that trust is layered in Mastodon:
You can trust someone on the basis of a history of behaviour and integrity of the node you're on, but people who need more trust can also run their own instance on their trusted domain. E.g. if POTUS wants a trusted Mastodon account, the logical choice would be to have webfinger for @potus@whitehouse.gov or similar point to a trusted instance run by the government. Nobody else can set up addresses on whitehouse.gov because it requires controlling the ability to run a webfinger setup responding at https://whitehouse.gov/.well-known/webfinger?resource=acct%3Apotus@whitehouse.gov https://whitehouse.gov/.well-known/webfinger?resource=acct%3...
Conversely, if people need someone trusted to run their instance, there are any number of people who'll happily take their money to provide guarantees.