Skip to content

How it fits together ​

Every app here works the same way: a relay introduces the browsers, the browsers then talk directly, and storage servers keep what they share for when everyone has left.

1. Relays introduce ​

FreeRTC relays pass the few messages two browsers need to meet: who is in the room, and the offer, answer and ICE candidates of a WebRTC connection. Signaling only: nothing else goes through them. The relays speak PSP, an open standard, and federate with each other, so a browser on one relay can meet a browser on another.

2. Peers connect directly ​

PeerPigeon links the browsers in a mesh over WebRTC. Moves, posts and messages go straight between them, by gossip to the whole room or as direct messages to one peer. A peer does not connect to everyone: it keeps a few links, and messages cross the mesh hop by hop (CECR is how a direct message finds its way).

3. PigeonFS keeps ​

PigeonFS storage servers keep each room's signed records, so a game, a post or a file is still there when everyone has left. A room's records live on the three servers closest to the room's id. The servers can't read them: each record is the room's own ciphertext.

What sits on top ​

  • Accounts come from PigeonIdP: one name on every app, signed by the person's own keys, with no company holding them.
  • Keys, signatures and encryption come from UnSea, the same library in every part.
  • Apps such as PigeonChess and PigeonFeed are ordinary web pages that use these pieces. There is no app server.

Anyone can run every part ​

A relay on Cloudflare takes a few minutes; a relay, a storage server and a PigeonAI server run together on a Mac with PigeonStack. Each one makes the network stronger. See Run your own.

peer.ooo · peer to peer on PeerPigeon