@stefan My intent has always been to showcase the things that the fediverse can do that nothing else can. There's a lot of work right now to open up relays and get everyone onto a 'fediverse firehose' for 'content discovery' reasons and all that, and I'm not averse to that.
But I also think that there's ways of federating, ways of grouping (allowlist-federation and followers-only, for instance) that is only a fediverse thing right now.
And I'm still working on building something much more rudimentary than Acorn, but essentially software to try to organize community reporting, monitoring, and feed composition (groups/networks) on the fediverse where followers-only becomes a delivery mechanism for semi-private discussion groups, where we opt-in to circles of discovery at both a server federation level (allowlists) and at a group level.
This is all part of what I'm trying to build in Pelago, to fill a gap and highlight a unique way of connecting across the fediverse.
And with the FIRES protocol, we now have a means to distribute follow lists (starter packs) and allowlists, not just 'blocklists', we have the ability to offer recommendations beyond just 'silence', along with community labeling, and ideally allows some of those federation/blocking decisions to pass to the user when possible.
The 'smallweb' DIY nature of the fediverse is what I love, not the large-scale projects. The ability for 10 people to chip in $1/mo and essentially host their own instance (GTS or Snac or something in that scenario, most likely, not Mastodon).
The affordability of controlling the 'means of posting' means that this is truly a community project. That's what I like about it. It's an experiment in realtime we're all building together.