> to design a protocol that prevents admins from deciding what bytes go in and out of the machines they pay to run?
By designing a peer to peer protocol without admins.
> those admins will choose to _not_ to run that encrypted protocol.
Yet people are still using freenet. Regardless, you can run a protocol like this on top of AP, to the admin it will look as if people are just exchanging encrypted data.
> By designing a peer to peer protocol without admins.
You can't require a client app for a social media service if you want any adoption. It's extremely important to allow at least viewing the content via a regular web browser. And to allow that to be done natively and frictionlessly, without having to rely on protocol bridges.
I can send a link to a Mastodon post wherever to whomever, even if they have never heard about Mastodon. Can't do that with p2p networks.
By designing a peer to peer protocol without admins.
> those admins will choose to _not_ to run that encrypted protocol.
Yet people are still using freenet. Regardless, you can run a protocol like this on top of AP, to the admin it will look as if people are just exchanging encrypted data.