I really want a paid relay that accepts everything but authenticates users to download events and you can only download if it has a p-Tag to the authenticated user.

In that way, when people send GiftWrap messages to that relay, my user is the only one that can download those messages from the relay. No one else can "watch" and count how many private likes, private zaps or messages I have.

Reply to this note

Please Login to reply.

Discussion

Isn’t that exactly what was proposed with kind 4 initially?

It's an idea that comes and goes. Hopefully with the new simplified NIP-65 with an inbox marker for private relays like that people start to publish relays that can actually support it.

we actually built a relay couple of months back with NIP-42 auth and only allows the p tag to download DMs. it is still online wss://securedm.current.fyi it needs the pubkey to be registered with current domain. let me know if you need a key. i can DM it to you.

this will be the error notice: Subscription rejected: Subscription requires #p or authors filter of authed pubkey

Nice! Do you have the code available somewhere?

yes. it is forked version of nostream. check here. Not sure if this branch has the changes. will check and update next week https://github.com/lightning-digital-entertainment/nostream/tree/NIP29

Quer privacidade pague por isso πŸ˜ŽπŸ€™

Nostr fix it πŸ€ͺ🍷

Se vc usa a propriedade de outra pessoa (o relay), tem que pagar mesmo.

Correct me if I'm wrong, but doesn't the ability to rebroadcast a note to any relay from any client break the privacy offered by a relay?

Like if I share private information on a private relay to my family but one of the tech illiterate ones tap the broadcast button on #Amethyst, then the private data leaks to other relays right?

Yes, that is very likely to happen.

However, privacy is not a binary thing. There are benefits to hiding most of your stuff while accepting that leaks will happen here and there.

That's why we designed the new DM protocol in such a way that even if the user re-broadcasts the outer or the inner event, it would still not leak any message or metadata information.

Because rebroadcasts will happen.

Was thinking about building such a thing. Hopefully someone will beat me to it

It goes really well with the new inbox tag for NIP-65