Understood. Thanks for taking time to always explain me things.
Discussion
That said, it’s true that Jumble marking a post as successful after just one relay accepts it isn’t ideal. I’ll adjust it so it only shows success once maybe a third or half of the relays have confirmed.
I just would like something like:
1- The person has for example four write relays, he reply someone, goes to only one relay. The UI show a message like: Reply tent to only one relay of four that you have. Do you want to try to send to the others relays or skip and send to just one?
*reply sent
Usually a reply gets sent to around ten or more relays. To achieve what you’re imagining, you’d have to wait for all of them to respond or time out, which would make the user experience really poor.
what would be better is a queue that just tries, when it succeeds, remove the item from the queue, and retry the others with an increasing delay until it's like 5 minutes then give up
What I don't understand or what I don't want to understand, haha, is:
Why we don't have a way to know if our reply was or not published on a read relay of the person we are replying? Because if we know that it was not, the Jumble UI could show a warning that the user we replied didn't get a notification and maybe show a way to try to notify the user.
We can know whether an event was delivered, but doing so would make the publishing process feel very slow.
I don’t think it’s worth sacrificing the experience for these rare cases. In most cases, sending succeeds, and if it fails, retrying will likely fail too—it could be a network issue or the relay simply refusing your event.