Why do you need a private relay if the events themselves are encrypted? The idea is to push encrypted events to each receiver's own relay by simply subscribing to the author's feed.

Reply to this note

Please Login to reply.

Discussion

thinking from standpoint of performance / scalability (yes it can be centralized like club relay)

if can push encrypted in "mesh of relays" only for subscribed npubs efficiently it can work too

Metadata hiding for one thing

πŸ€™πŸΌπŸ’œ #nostr push encryption #discussion

Sure, but I would argue most of use cases are semi-public anyway (like substack subscriptions).

good point ! if nostr wss can handle will be great

most r TIERED subs based - free / basic / pro

You could probably do it if all subscribers are on same renewable schedule, you rotate keys when subscribers renew, and renewed subscribers get updated key to be able to decrypt. Otherwise you're trying to encrypt duplicate notes, one to each subscriber which is a lot of unnecessary data.

Yeah this would do it and be scalable. However, a user could share the key with a friend to grant access to the content. Dunno how much that would matter in practice.

Shared secrets are fine for majority of subscriptions. The owner just needs to rotate the secret here and there.

But we should have a more strict scheme for the authors that are suffering with too many leaks.

can u share your seed with in DM friend LoL ;-)