IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
ipfs.io
ipfs.io
We are also planning on implementing various different modes for authentication and encryption. Our pubsub currently is plaintext and open for anyone to publish to any topic
A shining example of pubsub in use is PeerPad, a collaborative text editor exchanging CRDTs over IPFS/Pubsub: https://peerpad.net
Would require extra storage and overhead, but the result is maybe even more helpful than a tor site for important content.
because they can always get your ip address.
You will need to use some other method if you want anonymity.
[1] Domain fronting lets you use a well-established web frontend for your web service. E.g. we could host /ws nodes in Google Cloud, and to the ISP the TLS handshake looks like it's for google.com, while inside the connection there's e.g. a `Host: libp2p.googlecloud.com` header. More info: https://www.bamsoftware.com/papers/fronting/
But then again, net neutrality is a political issue! You don't solve it for good with technology.
I'm not sure how peers handle that situation, I'd assume it'd be treated like wire corruption (retry) or give up and try to fetch from a different peer.
I presume future clients would block nodes that share false content (if clients don't already).
"Floodsub" indeed.
For a more overarching perspective, I'd suggest A Progress Report on the Decentralized Web: https://www.youtube.com/watch?v=WK4PIGr3RB8