add "mute" OK=false status for no-op ephemeral events#1965
Conversation
|
This is fine, with the proviso that if the relay handles the event itself (like with #1079) it should not send a mute reply. |
|
How about |
|
I agree it's weird, but I couldn't think of anything better. I guess |
|
How about |
|
How about +1 on this idea |
|
|
|
feel it shoud be a single word, how about |
|
What do you have against |
|
ignoring to me means it was seen but chose to ignore. in this case, it wasn't seen, so it couldn't have been ignored. you can't ignore something if you don't know it exists.. it shouldn't matter much though so I'm fine with whatever |
|
We should have gone with numbers.
Since we can't do more than one word I guess |
|
We still could, just use No, but |
|
I like well-defined, extremely specific error codes. |
|
I read "We should have gone with numbers" to mean something like "relayed to 7 subscribed clients" and then use 0 when nobody was listening. But I think this doesn't fit into the protocol as specified. |
|
Please, gentlemen, can I merge? |
|
Yes, this is handled in flotilla |
This will probably make RPC and real-time communication use cases like NIP-46, NIP-47 etc much better, as the client sending the message will be able to learn instantly that their message wasn't read by anyone, instead of having to wait for some arbitrary amount of time and cancel the request because the other side is taking too long to answer.
This is implemented in https://github.com/fiatjaf/khatru.