NIP-98 is HTTP auth header event signed by a pubkey. 29 is a private group spec based on custom relays.
Our solution currently uses neither. It was written before 29 existed and 98 is not used for get requests by any client.
We went for pure kind 1 client interoperability, so we are augmenting REQs granularly on the relay side to access control content. We paired this with a custom file host that only authorizes users to view restricted content when they connect to the relay. This way even if your event leaks, the content can’t be viewed.
Mazin
npub18k…mx5sz
2023-12-30 03:18:30
in reply to nevent1q…0jc7
Author Public Key
npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5szPublished at
2023-12-30 03:18:30Event JSON
{
"id": "29a93097c9ee601c2a4550c2560eed87dbf3d6d23c2b97a8a515c08bffbcb2a2",
"pubkey": "3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d",
"created_at": 1703906310,
"kind": 1,
"tags": [
[
"e",
"41aaa11b9a425850eddcc222b87b8f74ad7424ad0b32a5ee240f5a6e0148aee4"
],
[
"e",
"8490e08c1e526495962bf3574189cc4fed75a9df79a60b0b908360eb4ea34d49"
],
[
"p",
"3f289d3caf5e18dd3ea1c1f6860eab2d34684e23da5afa8651d40463cf35b9fc"
],
[
"p",
"5be6446aa8a31c11b3b453bf8dafc9b346ff328d1fa11a0fa02a1e6461f6a9b1"
],
[
"p",
"5be6446aa8a31c11b3b453bf8dafc9b346ff328d1fa11a0fa02a1e6461f6a9b1"
]
],
"content": "NIP-98 is HTTP auth header event signed by a pubkey. 29 is a private group spec based on custom relays.\n\nOur solution currently uses neither. It was written before 29 existed and 98 is not used for get requests by any client.\n\nWe went for pure kind 1 client interoperability, so we are augmenting REQs granularly on the relay side to access control content. We paired this with a custom file host that only authorizes users to view restricted content when they connect to the relay. This way even if your event leaks, the content can’t be viewed.",
"sig": "41ad0d4775a380970480275cff29b2a987d78d8a8e3debbfd567f68c0fe9f0a57f8bb4a1ceba29c09c138acef9cf33e62218d2f6d6e79944a617324f75eb863e"
}