You know what's even more impressive about 1 billion Fediverse posts per month?
So much of it is quality.
Don't get me wrong, spam exists and I saw some of it yesterday.
But most of the time, I'm reading stuff that I enjoy.
Top-level
You know what's even more impressive about 1 billion Fediverse posts per month? So much of it is quality. Don't get me wrong, spam exists and I saw some of it yesterday. But most of the time, I'm reading stuff that I enjoy. 22 comments
@atomicpoet with all respect and gratitude, the #Fediverse should not be content with how it works so far. It scales by omission - in a way what they accused twitter, it just happens for different reasons. @atomicpoet one may see a big proportion because they are on a large server where someone follows someone else and it gets propagated. a third will think why the heck does this not get any responses because they only follow the original poster and nobody else on their server is interested in the topic. @atomicpoet I think when clicking on a post in the web "client", my server should fetch the thread. This would allow meaningful discussion on a common ground. That's not exactly scaling. If a single instance fails completely then all its users fail to get service, can't even login, that isn't scaling it's a Point of Failure. That instance could itself be scaled but it can't hand off the load to other instances and users can't migrate without their instance being up. There are other distributed but non scaled features like attachments, in that case attachments are a burden for all instances and probably a limiting factor. @simon_lucy And what if a centralized service goes down? Well, youβre shit out of luck. Which was the case with Google+, Friendster, Vine and a whole lot of services. On the Fediverse, the network persists even if one instance goes down. I can also still read messages from instances that are no longer even active. @atomicpoet not if it's scaled. Yes if it ceases to operate at all. Just like Mastodon instances that fail. You may get historical posts on Mastodon because they are on other instances but that is not scaling that's a kind of eventual consistency. Don't confuse scaling for traffic with resilience of an overall service made up of independent operators. Resilience, product resilience is important but it is not the same as scaling to a level of traffic that's magnitudes greater than at present. @simon_lucy You miss the point. Scale doesnβt even matter if Big Social pulls the plug on the service. On the Fediverse, that will never happen. Whatever scaling benefits you believe come from centralization ultimately means jack if the service lacks persistence. Which eventually is going to happen for Big Socialβitβs always a matter of time. Meanwhile, the Fediverse is now sending 1 billion messages per month. And itβs doing this because 22,000+ instances are federating right now. At which point did I say centralisation? Scale always matters and it makes no difference whether it's what you call centralised, single ownership, or multiple individual ownership. @simon_lucy Bullshit. I'm using scaling in the context of "How does 1 billion messages get sent." And it's 100% true that the Fediverse is capable of sending 1 billion messages per month, as we've already just seen. I'm less concerned about Mastodon itself "scaling" and more concerned about it DDOS'ing tiny sites all over the internet. This problem is still getting worse. Mastodon encourages a resurgence of blogging, but simultaneously can increase the technical burden of hosting a small blog. I'm also not that worried about ActivityPub "inefficiency," because at some point, some working group is going to finish a spec for an updated ActivityPub, and servers are all going to slowly migrate. @mekkaokereke Now this is quite a valid concern, and something that has frustrated me at length. I actually do wonder what will happen once thereβs 100 million active users, and a site goes viral. This is a good point. Each site fetches the posts from the original site, right? so the only 'efficiency' comes from multiple users in one instance sharing the same fetch. There are about 23,000 instances at the moment and about 10,000 users. Is it possible to model/simulate some scenarios for something going viral and the kind of burden they may put on different types of instances? π€ @atomicpoet If it's a link to a site, getting buried is a risk that has existed forever.. partly why things like blogspot took off. @atomicpoet Speaking from an American perspective, there are many who don't believe anything can succeed without a profit motive. Some of the best things in life are free. @atomicpoet @soatok also, the quality of interactions with others tends to be far better than on twitter. It reminds me of the way twitter used to be a decade or more ago. @atomicpoet @chancerydaily Iβm really impressed that itβs hit that level and not become total overload for small servers @atomicpoet In 6 months now I have one bad experience, 90% of which came from one single server which I have now blocked. #fediverse #mastodon #thisistheway @atomicpoet |
People ask if the Fediverse can scale. They wonder if decentralized social media has the wherewithal to handle "serious" network traffic.
1 billion messages per month should be the answer!
How do we do it?
It's quite simple: horizontal scale is scale.