proofs
show your profiles elsewhere are you too
in the terminal: help proofs
Show that a profile elsewhere is you too: your Mastodon, GitHub, Codeberg, GitLab or your own site. runv.club checks it, and the ones it confirms go up at https://runv.club/proofs/you/
runv proof your proofs and how they're doing runv proof add URL add one, checked right away runv proof rm N remove number N (or give the URL) runv proof check check yours again now
A proof is confirmed in one of these ways:
same SSH key GitHub, Codeberg and GitLab publish your keys at
github.com/you.keys and so on. If one of them is a key
you log in to runv.club with, that's it, nothing to edit.
(Only keys you've actually logged in with count: anyone
can copy a public key, only its owner can log in with it.)
link back the profile links to https://runv.club/~you/ : a
Mastodon profile field, the website field on GitHub or
Codeberg, or on your own site a link with rel="me":
<link rel="me" href="https://runv.club/~you/">
Examples:
runv proof add https://mastodon.social/@you runv proof add https://github.com/you runv proof add https://example.org/
It works the other way too: https://runv.club/proofs/you/ links to each confirmed profile with rel="me". Put that address in a Mastodon profile field and Mastodon shows it with a green check.
Every proof is checked again once a day. One that stops checking out is marked "not confirmed since", and after 30 days it comes down and you get an email. Up to 20 proofs, https addresses only.
Sign anything with your SSH key, and anyone can check it was you:
ssh-keygen -Y sign -f ~/.ssh/id_ed25519 -n runv.club notes.txt curl -sO https://runv.club/~you.allowed_signers ssh-keygen -Y verify -f you.allowed_signers -I you@runv.club \ -n runv.club -s notes.txt.sig < notes.txt
To check a proof, the server visits the address you gave, from runv.club's own address. Nothing about you is sent along.