Skip to content
TP Social
Sections

Quick start

Quick start

Claim a handle, install the client, publish your first page.

Before you start

You need:

  • An email address you can sign in with.
  • A desktop with macOS, Windows, or Linux (mobile clients are alpha and don't yet handle key generation).
  • About ten minutes.

You don't need a credit card, a domain, or a federated identity from some other platform.

1. Claim your handle

Pick a name. Handles are flat per Protocol Spec §9.3 — there are no nested namespaces. Lowercase letters, digits, and hyphens; up to 64 characters; no leading or trailing hyphen.

ok     @alice
ok     @cafe-de-flore
bad    @CafeDeFlore       (uppercase)
bad    @-alice            (leading hyphen)
bad    @alice-            (trailing hyphen)

Claim it from the desktop client (next step) — the registry will verify that your client holds the signing seed by checking a signature on the claim before writing it to the namespace.

2. Install the desktop client

Pick your platform from the downloads section on the landing page. The installer is signed and notarised on macOS, code-signed on Windows, and ships as an AppImage and .deb on Linux.

The first launch:

  1. Generates an Ed25519 seed (32 bytes).
  2. Wraps it with a passphrase you choose (Argon2id, parameters documented in the Protocol Spec).
  3. Stores the wrapped seed under your OS's standard application support directory.

The plaintext seed never leaves the process that generated it. It is not synced to the cloud, included in any backup we control, or transmitted to the registry.

3. Publish your first page

In the desktop client:

  1. Pick the handle you want to publish under (you can hold multiple).
  2. Write the page. Markdown is the easiest mime; HTML is supported but gets rendered in a sandboxed iframe per §9.4.
  3. Hit "Publish". The client builds the canonical CBOR bundle, BLAKE3- hashes it, signs the hash with your seed, and POSTs the wire to /pages on the registry.

The response is the public URL: /{your-handle}/{your-slug}. Share it anywhere — anyone who fetches it can independently verify that you signed it.

4. Sign in to the web shell

The web shell at this registry is read-only — content authoring lives in the desktop client. The shell is for:

  • Browsing your handles and their pages.
  • Copying public links.
  • Reviewing what's currently published under each handle.
  • Settings: profile, sessions, exports.

Sign in via paired-device login: enter your email at /login, then approve the challenge from the desktop client. No password leaves your machine.

What's next

  • Protocol — what's actually happening under the hood.
  • API reference — if you're integrating another client.
  • FAQ — common gotchas.