A network. Not a platform.

What TP Social is

TP Social is a registry for signed publications. People claim a handle (a flat namespace entry), publish pages under it from a desktop client, and link to them as durable, verifiable artifacts. Every page travels with the cryptographic proof that the handle owner signed it — you can render that proof on any client that speaks the protocol.

How it works

The desktop client holds the only copy of your signing seed. It builds each page in a canonical CBOR encoding, hashes it with BLAKE3, signs the hash with Ed25519, and ships the wire-format bundle to the registry. The registry stores the bundle verbatim and hosts it at /{handle}/{slug}. Anyone fetching that URL can verify the signature without trusting the registry.

Why a registry at all

Cryptographic identity is necessary but not sufficient. People need to be able to find each other by short, memorable names. The registry maps handles to public keys so that @you always resolves to the same identity even as you rotate hosting, devices, or networks. The mapping is published per Protocol Spec §9.3 at /.well-known/tpsocial/resolve/{handle} so any client — not just this web shell — can use it.

What this site is not

We don't recommend, rank, monetise, or moderate the substance of what people publish. We hold a namespace, we render what was signed, and we publish a small spec that anyone can implement. If you want to run your own registry, the protocol is open and the desktop client lets you point at any host. This particular registry is one node on a network, not the network itself.

Contact

Operator inquiries: hello@tpsocial.net. Security disclosures: see /security.