Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @mradcliffe@nokoto.org
mradcliffe@mradcliffe@nokoto.org (2026-05-19 07:14:23)
When last I left off, I made a pull request to peertube/http-signature library try to help the JavaScript ecosystem reach RFC 9421 parity while being backwards-compatible with cavage-12 draft implementations. There has not been any traction on this yet. Maybe because PeerTube has abandoned its own use of the library.

So our current ecosystem state is the following:

PeerTube uses misskey-dev/node-http-message-signatures library and owns the defacto unmaintained peertube/http-signature library.
Misskey and the rest of the ‘keyverse use peertube/http-signature library and Misskey owns the defacto...
---Reply---
silverpill@silverpill@mitra.social (2026-05-19 20:02:11)
@mradcliffe Does your instance support RFC-9421 verification?

---Replies---

mradcliffe@mradcliffe@nokoto.org (2026-05-19 20:28:31)
@silverpill It should, but it isn’t node.js based.

I wanted to help the node.js ecosystem by making peertube/http-signature backwards-compatible for both draft and RFC-9421.

Although I apologize that I am requiring alg.