Connectors
A connector is a source you pair to your ~handle so ~Alter can tell it is genuinely yours. Nothing is ever read from something you did not pair, and each page below states exactly what is read, what is refused, and how to undo it.
They are grouped by how each one proves you hold it, because that is the part worth knowing before you start. Most of them ask nothing of you beyond something you already control.
You prove it yourself
No login and no application registered anywhere. You either sign a one-time challenge with a key you already hold, or you publish a string somewhere public and it gets read back.
- Bio proof A one-time string in any public bio, anywhere on the web.
- Bluesky A nonce in your public profile, read back over the open network.
- did:key Decoded locally. The only connector that makes no network request.
- did:web A DID document you publish on your own domain.
- EAS An on-chain attestation somebody else wrote about you.
- ENS A name layer over an address you have already attested.
- Farcaster Custody of your FID, read off the chain.
- ISNI The public registry identifier the record world already keeps.
- Lens A username, resolved to the account and owner holding it.
- Mastodon A string in your public bio, found by WebFinger.
- Nostr A signed challenge, plus the NIP-05 mapping your domain publishes.
- ORCID The persistent identifier the scholarly world already keeps.
- SNS A .sol name, resolved to the address that owns it.
- Unstoppable Domains Ownership of the domain itself, never its records.
- Telegram Pairs through a bot, so it waits on that being provisioned.
You sign in, nothing registered
A real sign-in at the provider, but no application ~alter had to register and no secret ~alter holds. The exchange is protected by the flow itself.
- IndieAuth You approve the pairing at your own server, as your own domain.
- Lichess A public client with no requested permission scope at all.
- Personal website A record or file on a domain you control.
- Steam Sign-in through Valve, with no key held anywhere.
You sign in through the provider
An ordinary authorisation screen at a platform. Each page below names the exact fields read and the ones explicitly refused.
- Amazon Account-level identity only.
- Are.na The shape of how you collect and recombine, waiting on the pairing credential.
- Discord Your account and the servers you are visibly part of.
- GitHub Public contribution shape, never private repository contents.
- GitLab The same shape, on self-hosted or hosted instances.
- Google Account-level identity only.
- TikTok Account-level identity only.
- Twitch Account-level identity only.
- X Account-level identity only.
It never leaves your machine
Read locally by the runtime on your own device. Nothing is uploaded.
- Obsidian vault A folder you point at, read where it sits.