@andros Q: Why would you publish the private key? Hmmm 🧐

well, I suggested that in https://eapl.me/timeline/conv/k2ob6bq

The idea was to help those following the spec in https://twtxt.dev/exts/directmessage.Html, to replicate the steps and validate whether your implementation gives the same result.

BTW, you could add a link to the spec in the echo web.

I'm also thinking that some kind of tag might be needed to automatically hide twts from unknown extensions. For example our client doesn't support DMs and always shows the !<nick url><encrypted_message> syntax which is meaningless.

not a big deal as I can skip those messages, but again, it's an extension, so older clients shouldn't be affected by a new feature.

@andros doesn't this defeat the point of public cryptography?