Cacophony VS plebbit-js

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.

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

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

Continued working on the implementation of Plebbit's backend, including rigorous tests for each functionality.

Continued working on finalizing the design for Plebbit's APIs, including the mod API. Our final aim is to recreate reddit exactly, then expand to different types of clients, for example that look like 4chan or discourse, all using the same underlying protocol and all interoperable. The underlying data and protocol is completely open, so you can display the data any way you want to your users.

Updating code in plebbit-js to follow design as specified by README.md

https://github.com/plebbit/plebbit-js -> "wrap around the IPFS APIs used by Plebbit."

Check the github for development progress