Mazin on Nostr: NIP-98 is HTTP auth header event signed by a pubkey. 29 is a private group spec based ...
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.
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.