oh! i was wondering why the recommended way to verify ur masto was to post a keybase signed message when even https://keybase.io/verify doesn't support keybase signed messages any more
it's because a pgp signed message is longer than 500 chars. it's only like 510 if u remove the --begin-- and --end-- thingies but it's still too long for a toot
probly would make sense just to put a signed proof on my keybase.pub instead? 🤔 then it could be pgp OR keybase bc no char limits
@00dani the purpose of verification?
@Azrael it proves that my masto profile belongs to the same person as my keybase, which also has proofs that my twitter, facebook, github, etc., belong to the same person
or at least that all those people have the same private key anyway
basically it's a way to leverage trust across social profiles? if u believe my birdsite profile really belongs to me, then u have proof that my masto belongs to me as well
@00dani interesting concept.
@Azrael yeah it's cool :3 actually i have a bunch of keybase.io invites if you'd like one! it's pretty fun, especially now it actually provides something obviously useful (chat between keybase users, which is encrypted and signed :3 )