Justin Thomas

I've built #Enigmatick to manage threading using conversation IDs like Mastodon uses. But that's not aligned with #ActivityPub - or at least it wasn't the least time I looked. ActivityPub uses inReplyTo to indicate direct parent relationships and doesn't have a concept for linking multiple objects under a single ID.

Other systems don't use the conversation convention and that's caused some discord in my timeline. So now I'm learning about closure tables and concepts I probably would already know if I had studied computer science in college. But it's never too late to learn!

I finally figured out why Pleroma signatures wouldn't verify on Enigmatick.

Actor objects in Pleroma have a public key that ends with -----END PUBLIC KEY-----\n\n. Mastodon (and Enigmatick) have -----END PUBLIC KEY-----\n. Apparently that extra newline doesn't play well with the RSA Rust library's rsa::RsaPublicKey. As soon as I remove it, the key is processed with no trouble.

Now to figure out how I'm going to enshrine that finding in my verification code.