memex

What this switchboard knows, and does not

Nothing about a person or their vault rests here, not even sealed and not even briefly. What people share moves between their own devices, over a channel sealed end to end between them. This switchboard introduces devices and, when no direct path opens, forwards frames it cannot read.

What it holds, while a device is connected

• For each connected device: a random fingerprint and a public key, and which rooms it is in.
• For each room: who is in it right now. A room is a share, or a person’s own devices; its id is random.
• Nothing after the socket closes. There is no database.

What it sees pass through

• Session hellos between two devices: public keys, and signatures over them.
• Frames sealed under a key the two devices derived between themselves, when they could not connect directly. Sizes and timing; never contents.
• WebRTC offers and answers, so two devices can find a direct path. That path may reveal a device’s network address to the other device and to a STUN server.

What it does not hold

• The key to anything. The part of a share link after # never reaches it.
• Any record, any file, any name. Only sealed frames, and only in transit.
• Names, e-mail addresses, phone numbers. There are no accounts.
• Request logs. The platform in front of it keeps what it keeps; the switchboard itself logs nothing about who spoke to whom.

Running your own

This switchboard is the same software anyone can run: relay/ in the memex repository, one Vercel Function or one container. Point the app at it under Settings, Sharing.