FAQ

FAQ

Questions we hear often.

What happens if I lose my seed?

You lose the ability to publish under that handle. There is no recovery on the registry side — the whole point of holding the seed locally is that the registry cannot impersonate you. If your handle matters, back up the seed (the desktop client offers an encrypted export at first launch and on demand from the settings panel).

If you also lose the ability to log in to the registry (e.g. email takeover), email hello@tpsocial.net and we can help with the account itself. We still cannot recover the seed.

Can I move my handle to a different registry?

You can publish under the same handle on any registry that accepts a new claim from your keypair, provided that registry's name is not already taken. The keypair is portable; the handle name is per registry. Federation across registries — where @alice on one resolves on another — is the v1.4 milestone.

Why isn't there a web editor?

Because the registry doesn't hold your seed, only the desktop client can sign a page. Adding a web editor would either require us to take custody of the seed (defeating the model) or send the seed to the browser (an enormous attack surface for very little gain). The desktop client is small, native, and offline-capable, which is the right place to do signing.

Can I publish from a CI/CD pipeline?

Yes — the protocol doesn't require the desktop client specifically. Any process that holds the seed and can produce a canonical CBOR wire + Ed25519 signature can POST /pages. The desktop client is just the most ergonomic implementation; the CLI surface inside the client also accepts headless invocations.

How big can a page be?

The registry caps at 256 KiB of wire bytes per page by default. Operators can raise this in config/tpsocial.php. The protocol itself doesn't pin a size — but very large pages defeat the "signed and verifiable" model in practice (verifying a multi-MB blob on a phone is no fun).

Are pages discoverable?

The registry hosts an /explore surface listing recently claimed handles and recently published pages, and per-handle Atom feeds at /{handle}/feed.xml. There is no algorithmic ranking, no "for you" timeline, and no engagement-based reach mechanic. We expose the metadata; what you do with it is up to you.

How is moderation handled?

We do not moderate the substance of speech. We remove content that violates the law where the registry operates or that we receive a credible court order about. See the terms for the precise scope, and the security policy for the disclosure pipeline.

Is the protocol open?

Yes. The spec is published in plain English and any client or server that implements it interoperates. The reference implementation is this Laravel + Rust stack. If you want to run your own registry, point your desktop client at it.