[visualradio]

> Another layer of federated content publishing doesn't solve any problems.

HTTP is a request-response rather than content broadcast or publish-subscribe protocol. Presumably you could develop a publish-subscribe protocol with low-latency encryption support embedded in protocol layer similar to QUIC.

> if fediverse style apps take off the problem would just move to the most popular nodes on that network.

So suppose the Department of Energy provides a public cloud which people can get a network address to hold files for them similar to how they can get a Post Office box number at the post office. Except when you put a file in your own PO box the PO will make free copies of the file for others on your behalf which are subscribed to your PO box without destroying the original copy.

This would really just create a lower-level protocol or new number system for publish-subscribe content. It would compete with the other ARPAnet protocols such as TCP.