whitepaper VS Cacophony

P2P by definition cannot be banned. For example no one can "ban" a user from download or uploading a file with bittorrent. We've been working on a fully P2P reddit alternative for 2 years, if you're interested in the design we have a whitepaper https://github.com/plebbit/whitepaper/discussions/2

I've been working on a fully P2P reddit alternative that doesn't have "instances" that can block each other. Demo: https://plebbit-test.netlify.app Whitepaper: https://github.com/plebbit/whitepaper/discussions/2

demo: https://plebbit-test.netlify.app/#/ whitepaper: https://github.com/plebbit/whitepaper/discussions/2

Plebbit seems to be a crypto 4chan idea of Reddit. From the FAQ

Can't recommend Aether based on this discussion thread. Way too many hard sells listed for an unmaintained alternative. The latest forum thread even tells people to use a different platform, Plebbit (demo) (whitepaper), altogether.

high level whitepaper: https://github.com/plebbit/whitepaper/discussions/2

the protocol is a light protocol over IPFS/IPNS/Libp2p Gossipsub

IPFS files (JSON/base64): https://github.com/plebbit/plebbit-js#schema

we have a high level whitepaper on our github https://github.com/plebbit/whitepaper/discussions/2

For more info you can check the whitepaper https://github.com/plebbit/whitepaper/discussions/2 and also the upcoming design change for the mutable comment data https://github.com/plebbit/plebbit-js/issues/12

Unrelated but we've been working on a P2P reddit alternative for more than a year, here's the whitepaper https://github.com/plebbit/whitepaper/discussions/2

I have sketched up some explanation around how I did this in my decentralized video experiment: https://github.com/jmdisher/Cacophony/wiki/Inter-Channel-Relationship ("followers" randomly select some subset of the author's data to replicate, with a bias toward the more recent, in order to distribute the load across the network, provide availability, and satisfy streaming needs with local-only data). What you are describing sounds similar in terms of the problem it would need to solve.

Purely peer-to-peer applications. These are more ambitious systems but are either just sketches on napkins or are only used by the people prototyping them (like my own Cacophony where most of the content is related to the development of the system - at least I can dogfood it).

My thinking around some of these "global data/user search" problems is that they are analogous to the early-internet where expecting the protocol to present a global view wasn't possible so search engines were built to infer structure from the meaning of page linking. Hence, I am mostly just stating these assumptions and proceeding, not directly worrying about them (the bigger problem is the mobile user problem). Going forward, my main concern is making sure that the on-IPFS data model and protocol-level data schemas allow for that meaningful connectivity, both for local user convenience and potential global search indexing. The question around respondingTo is an example of that kind of question.