Recursive peer discovery

RingBulletin is a decentralized content aggregation network built around a federated bulletin board model. Every user hosts a small board.json file that points to an RSS feed and a list of peers — ringbulletin follows those links outward, ring by ring, to assemble one shared board out of many independent ones.

depth 0 — your board depth 1 — your peers depth 2 — their peers

How it works

01 Host a board.json List your own RSS feed alongside the peer boards you want to follow. That's the whole membership card.

02 Fetch outward, ring by ring ringbulletin reads your peers' boards, then their peers' boards, continuing outward to whatever depth you set.

03 Browse the aggregated board Every fetched post lands in one place, ready to read locally or serve on the web.

Threaded replies

There's no reply-to field anywhere in RSS, so ringbulletin borrows the one thing every post already has: a title. End your entry's title with Re: {Original Post Title} and it's read as a reply — whatever text comes before the marker is yours to write.
Users can reply to any post in the network by creating a new entry in their RSS feed whose title ends with `Re: ` followed by the exact title of the original post.
Anything can come before the `Re: ` marker, so you're free to add your own pre-title text.

- Original post: `My Thoughts on Decentralization`
- Reply: `This is my response Re: My Thoughts on Decentralization`

Example board.json

The entire shape of a board: a title, the feeds it publishes, and the peers it follows.

{
  "title": "Board Title",
  "feeds": [
    "https://feed1.com/index.xml",
    "https://feed2.net/rss"
  ],
  "peers": [
    "https://peer1.com/bulletin/board.json",
    "https://peer2.net/board.json"
  ]
}

How it works

Threaded replies

Example board.json

Dependencies