الأسئلة الشائعة

What happens if I lose my seed?

For an externally held Side key, loss of the seed and every backup removes your ability to sign as that Side. The registry cannot reconstruct an external key from its public key.

Browser-created Sides use keys held in the hosting service's encrypted vault. Account password, passkey, and two-factor recovery are separate from external key recovery. Use the recovery options shown for your account. Trustee and threshold recovery are not available in this release.

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 not built.

What can I edit in the browser?

You can edit public profile blocks and use the community and event tools. Open your handle and choose Edit blocks. Saved blocks appear on the public profile.

Signed page bundles are separate. Publishing them requires a compatible client or the API; this release has no browser composer for those bundles. Browser Sides use hosted signing keys. That custody is described in the privacy policy.

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. Use a client that implements the current wire format, and keep its signing key out of build logs and published artifacts.

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. You can run your own registry from it. Native clients are not released yet.