NIP-01 is a little ambiguous around REQ messages. One part of the nip says "(...) a new `REQ` is sent using the same `
And the other part regarding CLOSED messages gives an example of one being sent when a REQ is received having the same subscription id.
Which one is it? are REQs like replaceable events? #asknostr
Paging nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpp4mhxue69uhkummn9ekx7mqcu9929 nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8g2lcy6q
It's unclear to me what relays implement, I'm not sure even about my own relay. Once we find that out we must update the NIP.
I'll start looking at different implementations and see what I find.
I just assume the relay ignores duplicate subids. This is reasonable to me
What about when you unfollow someone? Wouldn't that require a REQ update? Ignoring duplicate subids would mean you would need to close the REQ and open a new one no?
You could just keep the REQ running and filter out unfollowed people locally.
And when you follow someone and want to load their notes from that same relay you could maybe close the first REQ and start a new one with "since":
Okay here are my findings:
- strfry seems to treat REQs with the same subID as replaceable: https://github.com/hoytech/strfry/blob/32a367738c6db7430780058c4a6c98b271af73b2/src/QueryScheduler.h#L23
- gnost-relay just overwrites, doesn't check for duplicates at all: https://github.com/barkyq/gnost-relay/blob/817ff549b2f4b078d984abec9105010555e76e80/main.go#L661
- nostr-rs-relay replaces: https://git.sr.ht/~gheartsfield/nostr-rs-relay/tree/master/item/src/conn.rs#L118
- nostream ignores duplicates: https://github.com/cameri/nostream/blob/b6133a18fde1bba396bc04419adc39f186ea8eb0/src/handlers/subscribe-message-handler.ts#L92
- nnostr replaces: https://github.com/Kukks/NNostr/blob/78753daa9c0a81adebab1b50ebea923de654036a/Relay/StateManager.cs#L56
So 4/5 I've looked at replace, only one rejects duplicates.
