01 — Blocks
A cache is a channel of blocks
Write a note, paste a link, drop in an image URL. Only text is ever stored; previews are worked out from the text itself, because there is no backend to go and unfurl anything.
Peer-to-peer knowledge base
A shared library that lives on the machines of the people using it
Cache is a place to collect text, links and images with other people. Every member keeps a full copy and syncs straight to everyone else's browser. No account, no database, no company in the middle holding it for you.
02 — Replicas
Everyone holds the whole thing
Joining pulls down a complete copy. From then on you read from your own machine, online or not. Edits merge on their own — every change is an immutable operation, and any two members holding the same set agree without anyone arbitrating.
03 — No middle
Nothing is hosted
A relay introduces two browsers and then gets out of the way — it never sees cache names, keys, or contents. When it can't reach someone, the request hops from member to member instead, each passing it to everyone it knows. Shut the relay down and connected members carry on regardless.
04 — Mortality
It can disappear
A cache exists only as long as a member does. When the last person closes their tab, it is gone, and nothing anywhere remembers it. That is the trade for having no server, and it is worth knowing before you put something important in one.
Getting someone in
Membership is a link. It carries the key that decrypts the cache in the part of the URL browsers never send to a server, so handing it to someone is the entire process — they become a full member with their own copy, able to add to it.
Open the app