<oembed><type>rich</type><version>1.0</version><title>Mazin wrote</title><author_name>Mazin (npub18k…mx5sz)</author_name><author_url>https://yabu.me/npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>NIP-98 is HTTP auth header event signed by a pubkey. 29 is a private group spec based on custom relays.&#xA;&#xA;Our solution currently uses neither. It was written before 29 existed and 98 is not used for get requests by any client.&#xA;&#xA;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.</html></oembed>