Relay-Specific Notes

https://github.com/jb55/nips/blob/relay-specific-notes/35.md

https://github.com/nostr-protocol/nips/pull/1146

cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

Reply to this note

Please Login to reply.

Discussion

add the to field is hard to many databases .

I am definitely interested in a solution for this. There are a few similar proposals with different methods and I think there are pros and cons to each of them. I tend to think https://github.com/nostr-protocol/nips/pull/1030 is the best approach but it requires widespread adoption to be useful which is a significant barrier. It also relies solely on relays to enforce and doesn’t provide a (signed) way for the client or non-author user to validate if a relay is cooperating.

Your proposal accomplishes the goal today for anyone who wants to support it which is useful, but since it requires signature validation changes it will be harder for relays to implement. It can’t be done as a write plugin or on a proxy in front of the relay because the DB needs to support the new field. It also forces the user to re-create the event to add another to relay which leads to duplicates.