{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidef3ikxwwm2er3vqzjinrmgjwrxkrdyhoknhsexcib7awelwtp6u",
    "uri": "at://did:plc:ixd3llanirxy6by2epvxdu7k/app.bsky.feed.post/3mlqt2na36nz2"
  },
  "description": "@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\n\nNodeBB 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.\n\nFor a variety of reasons, but mainly to avoid NIH, I'd consider switching to a dependency.\n\nMy 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?\n\nI suppose, same question re: double-knocking.[...]",
  "path": "/post/1865",
  "publishedAt": "2026-05-13T17:24:32.440Z",
  "site": "https://activitypub.space",
  "tags": [
    "httpsig",
    "cavage-12",
    "httpsignatures",
    "activitypub",
    "@chocobozzz@framapiaf.org",
    "Are we HS2019 yet?",
    "@peertube"
  ],
  "textContent": "@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\n\nNodeBB 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.\n\nFor a variety of reasons, but mainly to avoid NIH, I'd consider switching to a dependency.\n\nMy 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?\n\nI suppose, same question re: double-knocking.[...]",
  "title": "Re: @peertube/http-signature",
  "updatedAt": "2026-05-13T17:24:54.001Z"
}