https://media0.giphy.com/media/L2qukNXGjccyuAYd3W/giphy.gif?cid=9b38fe91blqrd7b0eshhiqigm0g0fhn72w5aqyc0a4fuzdnd&ep=v1_gifs_search&rid=giphy.gif&ct=g

https://media0.giphy.com/media/L2qukNXGjccyuAYd3W/giphy.gif?cid=9b38fe91blqrd7b0eshhiqigm0g0fhn72w5aqyc0a4fuzdnd&ep=v1_gifs_search&rid=giphy.gif&ct=g

https://media0.giphy.com/media/L2qukNXGjccyuAYd3W/giphy.gif?cid=9b38fe91blqrd7b0eshhiqigm0g0fhn72w5aqyc0a4fuzdnd&ep=v1_gifs_search&rid=giphy.gif&ct=g

https://media0.giphy.com/media/L2qukNXGjccyuAYd3W/giphy.gif?cid=9b38fe91blqrd7b0eshhiqigm0g0fhn72w5aqyc0a4fuzdnd&ep=v1_gifs_search&rid=giphy.gif&ct=g

Change of plans, we're going to the meat mkt to order another half cow instead. #grownostr #hometownmeatmkt

Change of plans, we're going to the meat mkt to order another half cow instead. #grownostr #hometownmeatmkt

Change of plans, we're going to the meat mkt to order another half cow instead. #grownostr #hometownmeatmkt

煮るやり焼くなり好きにしろライセンスだ！

煮るやり焼くなり好きにしろライセンスだ！

煮るやり焼くなり好きにしろライセンスだ！

煮るやり焼くなり好きにしろライセンスだ！

Good morning and pura vida, Nostr! It's time to create notes and send zaps! 💜🤙🏻🫂

Good morning and pura vida, Nostr! It's time to create notes and send zaps! 💜🤙🏻🫂

Good morning and pura vida, Nostr! It's time to create notes and send zaps! 💜🤙🏻🫂

Good morning and pura vida, Nostr! It's time to create notes and send zaps! 💜🤙🏻🫂

Public Domain でなく NYSL でした。(まぁほぼ同じ) https://github.com/mattn/mattn-icons

Public Domain でなく NYSL でした。(まぁほぼ同じ) https://github.com/mattn/mattn-icons

Public Domain でなく NYSL でした。(まぁほぼ同じ) https://github.com/mattn/mattn-icons

If you only ever heed one piece of advice from me, let it be this one: TAKE SELF CUSTODY OF YOUR BITCOIN CONTROL YOUR OWN KEYS Thank me later.

If you only ever heed one piece of advice from me, let it be this one: TAKE SELF CUSTODY OF YOUR BITCOIN CONTROL YOUR OWN KEYS Thank me later.

If you only ever heed one piece of advice from me, let it be this one: TAKE SELF CUSTODY OF YOUR BITCOIN CONTROL YOUR OWN KEYS Thank me later.

If you only ever heed one piece of advice from me, let it be this one: TAKE SELF CUSTODY OF YOUR BITCOIN CONTROL YOUR OWN KEYS Thank me later.

I understand that position, however I think it depends on how the kind=5 deletion event was specified, and the relay’s policy with regards to storing replaced events. NIP-09 allows either the ‘e’ tag (specific event id) or the ‘a’ tag (“kind:pubkey:d-identifier”). If the deletion event specifies a particular event by its id (‘e’ tag), then it’s an open question how to proceed. Consider these different cases: ## Delete then replace 1. User creates replaceable event A. 2. User deletes replaceable event A with ‘e’ tag specificity. 3. User creates replacement event B. Expected behavior: REQs receive B. ## Replace then delete original 1. User creates replaceable event A. 2. User creates replacement event B. 3. User deletes replaceable event A with ‘e’ tag specificity. Expected behavior: REQs receive B. ## Replace, then delete replacement 1. User creates replaceable event A. 2. User creates replacement event B. 3. User deletes replaceable event B with ‘e’ tag specificity. Expected behavior: ??? IMO, the correct behavior is to serve event A. A is still a valid event. Its replacement was deleted. An alternative interpretation would be that REQs get nothing since the relay receiving B immediately purged A on the grounds that it was replaced. To my knowledge, NIP-01 and NIP-09 do not address this specific case. NIP-01 states that “even if the relay has more than one version stored, it SHOULD return just the latest one.” It does not specify what should happen if the latest one was deleted. NIP-01 continues with “These are just conventions and relay implementations may differ.” I interpret this to mean that the handling of replaced events is a matter of relay policy, especially when incorporating the additional complication of NIP-09 deletes.

I understand that position, however I think it depends on how the kind=5 deletion event was specified, and the relay’s policy with regards to storing replaced events. NIP-09 allows either the ‘e’ tag (specific event id) or the ‘a’ tag (“kind:pubkey:d-identifier”). If the deletion event specifies a particular event by its id (‘e’ tag), then it’s an open question how to proceed. Consider these different cases: ## Delete then replace 1. User creates replaceable event A. 2. User deletes replaceable event A with ‘e’ tag specificity. 3. User creates replacement event B. Expected behavior: REQs receive B. ## Replace then delete original 1. User creates replaceable event A. 2. User creates replacement event B. 3. User deletes replaceable event A with ‘e’ tag specificity. Expected behavior: REQs receive B. ## Replace, then delete replacement 1. User creates replaceable event A. 2. User creates replacement event B. 3. User deletes replaceable event B with ‘e’ tag specificity. Expected behavior: ??? IMO, the correct behavior is to serve event A. A is still a valid event. Its replacement was deleted. An alternative interpretation would be that REQs get nothing since the relay receiving B immediately purged A on the grounds that it was replaced. To my knowledge, NIP-01 and NIP-09 do not address this specific case. NIP-01 states that “even if the relay has more than one version stored, it SHOULD return just the latest one.” It does not specify what should happen if the latest one was deleted. NIP-01 continues with “These are just conventions and relay implementations may differ.” I interpret this to mean that the handling of replaced events is a matter of relay policy, especially when incorporating the additional complication of NIP-09 deletes.