Also, I understand you guys do not intend to EEE the ActivityPub network... but that's what actually happens when the flagship doesn't prioritize compatibility.
Implementors need to bend backwards to support the Mastodon flavor of ActivityPub or else they get shut out of the network.
As another example, ED25519 private keys do not exist in the network despite being smaller and more secure than 256bit RSA, because Mastodon implementation of HTTP-Signatures did not support them.
So if you guys want to be taken at your word, please do something about these things. I'll gladly shut up if there's something done about compatibility.

).
. Maybe all it would take is a single visible example?

