#httpsig

httpsig.org is a site with one sole purpose, to advocate for the adoption of RFC 9421 HTTP Signatures. It has a "Libraries" tab that does exactly what it advertises, it lists a bunch of libraries for you to use so you don't have to roll your own. If you want to integrate AP today, but you don't want to roll your own everything, where do you go? Who do you ask? All I know is: Fedify → Typescript (thanks @hongminhee@hollo.social!) FedBOX → Go (thanks @mariusor@metalhead.club!)[...] Do we even have a list sorted by language? This would be huge. What other AP frameworks do you know of? Granted, I didn't do a lot of thinking and deep diving before I listed those two examples, but even then, that's 1 more example than is listed on https://activitypub.rocks so I think I might be on to something here from a developer advocacy point of view. If I were looking to integrate AP, one of the first conclusions I'd come to is that the protocol itself is fairly complex and a library or framework might help. I don't think there is a list that plainly lists supported libraries by language.

@Chocobozzz@framapiaf.org I have a question for you... I'm seeing in Are we HS2019 yet? that Peertube and Misskey both use your package: @peertube/http-signature NodeBB currently rolls its own cavage-12 support but and I did some preliminary research into updating to the latest HTTP Signatures draft, but quickly got overwhelmed. For a variety of reasons, but mainly to avoid NIH, I'd consider switching to a dependency. My question is: does your library support verification for non-hs2019 signatures, or will I need to invoke your library in front, and fall back to existing cavage-12 verification otherwise? I suppose, same question re: double-knocking.[...]