Learn
Short pages for anyone who wants to understand what Veil does before using it. Each one is written in English and in Italian and ends with the questions people ask most.
- A public key directory tells you whose key is whose. Why a key alone is not enough, and how a transparency log and its witnesses keep the directory honest.
- Keybase tied keys to Twitter, GitHub and Reddit accounts in 2014. What Veil owes it, and where the two differ today.
- Keyoxide keeps identity proofs inside your own key, with no central server. Veil keeps them on a card in a witnessed public log. What each is good for.
- What SKS and keys.openpgp.org do, what they leave out, and when a keyserver is still the right place for your PGP key.
- How to check that a Discord account belongs to the person it claims to be, with their Veil card, and what someone who steals that account still can’t do.
- Sign a release with veil sign --release, let users check it in their browser or with one command, and tie your apt signing key to your card.
- An organisation card lists who really works for you, puts your logo beside their names, and marks your official servers. How it works and what the reader checks.
- What a Discord community gets when it asks members for a Veil card: a role for linked members, a staff list people can check, and less room for impostors.
For the API, the command line and the Discord app, read the documentation.