NIP-01 is a little ambiguous around REQ messages. One part of the nip says "(...) a new `REQ` is sent using the same `<subscription_id>`, in which case relay MUST overwrite the previous subscription."
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
RebelOfBabylon
npub16p…z7gjy
2024-08-25 21:08:24
Author Public Key
npub16phxqxxplnmasr20rzh8afnflgg0ssufl90k6x7ua2tj0jexdseszz7gjyPublished at
2024-08-25 21:08:24Event JSON
{
"id": "91faf72ec48d019695f40a5ee8d5f3a5b1943f4151bd6a373a8dc3790f5f6374",
"pubkey": "d06e6018c1fcf7d80d4f18ae7ea669fa10f84389f95f6d1bdcea9727cb266c33",
"created_at": 1724620104,
"kind": 1,
"tags": [
[
"t",
"asknostr"
]
],
"content": "NIP-01 is a little ambiguous around REQ messages. One part of the nip says \"(...) a new `REQ` is sent using the same `\u003csubscription_id\u003e`, in which case relay MUST overwrite the previous subscription.\"\n\nAnd the other part regarding CLOSED messages gives an example of one being sent when a REQ is received having the same subscription id. \n\nWhich one is it? are REQs like replaceable events? #asknostr\n",
"sig": "d8fc707fbd8c53b12058f23b84640ab51097da6ebf5adabc9cb45a3ba8543f95d343bff9d51897b83091c8ccdd211a4ce9d74c3944ab757d437a0663c852b3ea"
}