BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5wcIkHbsCt0yJF jncIIVWkV03MTb9 0N48z5wEwi2qKSi JzzJW0TxAnT51N5 1ilqiPF1fB2OdZs lUPR2qlJ83nvY6N gvpGWXAiIU7DjF9 b9Fe6cxmWsfPx7M i1zLyl7tTkd9yEI rGjIwq2ZBfy5Bi9 eDMTx6d6TPOu0mL AqMYPPyWBmaaenz RwTMUTbrQPL2jdC aNYkwRN8enSv2w8 nEm6US6VNaANbHh M2ur0HJ0ZkCkuXo OmV1XPJqgCJUswE NaBHAwxRi0fVM7P vjM2VkB8vz9PJpR u8XNF7VD6wkMfDB Jx9bvlo4fqKRu5b 60. END KEYBASE SALTPACK SIGNED MESSAGE.
If some account claiming to be me cannot do that, it's an obvious fake.
This verifies a connection to my Keybase account, which also links to my GitHub and Twitter accounts, it's signed using the key listed on zeonfederated.com, which was my domain for many years and uses SSL.
@Gargron I still think rel="me" (and maybe rel="notme") is a better answer than adding yet another thing to check as a key.
@Gargron what stops people from doing a copypasta on the thing you just published?
@ajroach42 The message says "I am [email protected]" 😂
@Gargron oh. Derp. I guess that make sense.
@gargron @ajroach42 well it's still becoming a copypasta
I could say that I'm [email protected]
@memeity @ajroach42 You can't do that because you don't have my private key that I sign it with.

@memeity @Gargron right, but you couldn't encrypt that against his private key.

Anyone who is actually using keybase//pgp can now verify that this account is real and the imposter accounts are not.

(The problem is that a minority of people actually use cryptography.)

@gargron @ajroach42 though it would be a clear lie
@Gargron BEGIN FOOBAR ALLYPOURBASE SIGNED MESSAGE -2-@+8℅£=`¥×NSNZJJnskkzo+#+#++2=£=£=$=¢ END AWESOME MESSAGE this is linked to my example.com domain through the amazing technology of interwebs between youporn.com and bit.ly in the presence of jupiter. Can't be called a toot without it!