Overview

What you'll find here

These docs cover everything you need to publish to a Sideverse registry, verify a signed page yourself, or implement a client that talks the protocol.

If you're new, start with Quick start — it explains the supported publishing paths. Browser members first enter through an invitation, verify their email and receive their inviter’s personal confirmation.

If you're building tooling, Protocol is the canonical reference for handle naming, the resolve endpoint, the signing scheme, and the sandbox model that lets clients render untrusted HTML safely.

If you're integrating an existing system, the API reference lists every HTTP endpoint this registry exposes, the bodies they accept, and the responses they return.

If you're building the TrustPlane app or anything on the social layer, the API reference has three sections for you: The app: pairing and what a side sees, Experiences, people, groups inside a group, and A group's look. This registry is also the namespace authority for trust://sa/@handle names — see Names on the trust web.

The product name is Sideverse, formerly TP Social. Existing tpsocial API names and signed-data formats remain unchanged for compatibility.

Using these docs with the website

These technical documentation bodies are currently available in English. The website also offers Arabic navigation and account controls; changing the interface language does not translate these technical references or member-authored content.

Use Sign in for an existing browser account; no app download is needed. Device sign-in is an optional separate path for compatible clients. When new entry is paused, approved members can still sign in. Official website controls include Light, Dark and System appearance; member-authored page and community themes keep their own design.

The browser workspace connects Discover, Communities, Events and Your Sides. Use the displayed Side when publishing or participating. Account recovery, invitation quota and security settings belong to the account; custom-domain settings let you select the Side whose handle you are managing.

Start with Discover to find upcoming events and communities available to your selected Side. Open an event to see its details and RSVP, or open a community to learn about its membership rules and join when permitted. Organizers enter venue names or addresses and optional external links; the website does not embed maps or perform place searches.

Feature availability depends on this registry's configuration. The status page describes configured availability and reported incidents. Native download links show an unavailable page when no release asset is available. For the data recorded by the website and the separate native sender, see Telemetry and Privacy.

A few principles to set expectations

Signed pages can be verified independently. A preserved page and its signed records remain verifiable against their public key; availability still requires a copy and a working host.

Custody depends on how you use Sideverse. Browser Sides use encrypted keys held by this hosting service. The service knows which account owns each Side. A paired external client can retain its own key; pairing that Side grants no access to sibling identities or account recovery. Account password, passkey and TOTP recovery are separate from recovering an external Side key. Trustee or threshold recovery is not available.

The spec is plain English. We try to keep it short, exact, and free of optional behaviour. If you find ambiguity, file it — that's a bug in the doc, not a bug in your implementation.

Conventions in these docs

• Code blocks contain text you can paste verbatim.
• §9.3-style references point at the canonical Protocol Spec sections.
• We use @alice for the example handle and hello for the example slug throughout.