-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

If you only use 140 characters like on Twitter, you will be able to sign those 140 char
messages with GPG (ECC keys) here on mastodon.social
-----BEGIN PGP SIGNATURE-----

iF4EARYIAAYFAljlAp4ACgkQmbnNRBSuRb2qBgEA/wWH3rjSfESf4tYzqQ1j15Cq
g+GdYA4XFehfXaVSlngBAJyx9iK0PLRLAGQhrLp/LwtbG0wbjaKh7mgEvUBTGFMG
=p/Hi
-----END PGP SIGNATURE-----

@cypherpunk this could be done in JS, fron-end side. Nice idea.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

@cypherpunk lol
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQSQY6O3/njWTMf2fpw7BtmZlYsD8wUCWOUa6AAKCRA7BtmZlYsD
82MZAQCFHqYxg39e/dlm9buDrts5oHvQPHZd+MIKK30AjloctwD+JBPvUSf4KLQE
GCwgSkL5Fggi6YUi4ciXsdXJ/Xt3uAI=
=f6YJ
-----END PGP SIGNATURE-----

@cypherpunk mastodon changes the signed data if it includes an off-instance user! I signed the message with @ cypherpunk @ mastodon.social
gpg: key 99B9CD4414AE45BD: public key "CYPHERPUNK-256 <[email protected]>" imported

@cypherpunk

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

All your base are belong to us
-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQRSt51cX153kxmtrhvpu64l4Dx/LAUCWOUflgAKCRDpu64l4Dx/
LFQpAP40kKcbba5sOlxEDqnQCHGcwNkT/9rmAvGz/MWPCR5ZuAEA4dGmDUAPeKZM
nXAfJu4O5UvTFhFMTzPPgc2Ocug7FwA=
=TZYh
-----END PGP SIGNATURE-----

@cypherpunk Good point! Would be interesting to see that implemented into clients