Embed Notice

the nature of an ecosystem when one software can steamroll in whatever direction it wants too unimpeded (because again: marketshare) and how this cripples the advancement of careful protocol development when much of it's "behind closed doors" of one vendor (at least to my understanding), outside of actual standards bodies and community-organized efforts-- @arcanicanis@were.social

YES, THIS! Sums up my frustrations pretty well back from when Misskey was having federation issues with Peertube and Owncast because of HTTP Signatures.

Just as a reminder, the version of HTTP signatures the elephant in the room uses (and thus makes everyone else use) is based on an RFC draft which is now "expired & archived".

Also when I was looking up the name of the RFC draft again I found out that its successor RFC 9421 "HTTP Message Signatures" has been published this month. I hope someone in particular will be making some kind of move on that if you know what I mean. :gargamel: