Earlier quoted context omitted.
Everyone is approaching the social media issue as if it was a technical problem - it's not. No amount of decentralisation or protocols address (or even attempt) the root cause. The closest would be the crypto-based social networks, which while they have their own problems at least attempt to address the issue of funding the platform. You know it's bad when the closest thing to a solution comes from crypto grifters. S…
No. You're still thinking about Mastodon as a federation of medium- and large- sized small social networks; star systems in a galaxy. That's how it works now, but I don't think it's going to stay that way for long. I don't think large shared Mastodon instances, at least larger than you'd see for a group blog, make much sense. It doesn't make sense for all the reasons you're spelling out: the amount of effort to keep…
RSS/Google Reader was mostly a "pull" medium. Creators create content while consumers passively consume it but can't write back. This works but is fundamentally different from Twitter and the modern concept of social media. Furthermore, RSS offloads all the work to the clients, so RSS servers don't have to store nor process any state regardless of how many consumers there are (you can serve the same cached response to all of them).
If you want it to be like social media, you need people to also be able to "push" things (that others who don't directly follow you see) so people can reply and comment and do social-media-y things. This then not only opens the floodgates for spam, but also makes everything harder if every instance has to federate with tens of thousands of small ones instead of a few hundred like we currently have (the current system works fine with a "hosts"-like file manually curated by instance admins, but if instances start proliferating you'd need a DHT of sorts so they can all discover each other, and again need some way of vetting the quality of them so you don't get spam into it). This turns instances into hosts not just for the original content of the instance admin but also for the replies of people, again raising both server resource issues as well as issues relating to spam, illegal content and moderation in general.
> think of this like Blogger and Google Reader mashed together, with Twitter's surface-level user experience
Blogger could potentially pull it off because it's a closed system that has one consistent moderation policy. It doesn't have to broker or host unvetted third-party content. But blogging/publishing is fundamentally still a different medium to something like Twitter.
> People forget that the "blogosphere" worked pretty great before Twitter and Facebook wrecked it.
I think that the blogosphere and social media are fundamentally different mediums. Blogging is write-once, read-many, with minimal, mostly consumer-to-publisher interactions (comments on the blog itself). For a lot of people, social media also involves direct consumer-to-consumer communication, merely adjacent to the publisher's content but completely outside of their control. Your proposal does not address this use-case.