Yes, but you can't make it easy. There are no servers that don't need maintenance, at least for electricity and connectivity issues. But also bugs, security issues, etc. The closest we came to this is VPSs on the cloud, and I support that a lot, but still, these friends need to know how to deal with emergencies.. just ask anyone who is running a mastodon instance.

If people keep pretending the mempool is a gatekeeper, people will start submitting transactions to mining pools directly like popular Nostr relays... is that how you keep bitcoin mining permissionless and decentralised?

Bluesky metrics are steadily declining, and that is the network that has the best chance of going mainstream. It is time to stop caring about global feeds and just make our small-worlds web better and more sovereign and be happy with that.

You can't fight physics, all centralised social media will have to deal with this, and I don't think you can make a non-centralised social media, unless you redefine social media to; chatt apps that feel like twitter but have the same reach as a telegram group.

OP_RISCV

I have to admit, every time I see a screenshot or link from Mastodon I get envious of the quality of people and conversations there. This can very well be a selection bias, but I might cave in and create a Mastodon account. I just wish Mastodon was using Pkarr, so I neither have to setup a server nor worry about who is the first server I sign up to.

For anyone who cares, the reason I a argue for a sovereign e2ee filesystem, is because that is the only thing we can make interoperable between apps... just like POSIX and files in general are the only interoperability success story in history. What I consider feasible is taking that and make it Web native without getting locked in platforms like Google Drive. Once that is in place, let the best app developer win, and if one file format becomes very useful, we reverse engineer it like we always do, like interoperability always worked; forcefully.