3 ms·
> tells you it was not. At which point there is no option to cancel and say "you know what... don't send it". If you notice it 24 hours later, your choices ar
by adrianmonk 6y ago
> tells you it was not.
At which point there is no option to cancel and say "you know what... don't send it".
If you notice it 24 hours later, your choices are (1) be nagged about retrying it forever or (2) retry sending a message that may now be irrelevant.
When it comes to retries, the easiest thing for the user is for the software to be responsible for retrying failed actions. Choosing not to do that makes sense IF the goal is to give the user more control because they may not necessarily still want the action done.
But if you don't give them that control, it's the worst of both worlds. The retry happens slower, with more manual work, and without the benefit of choice.
- arwineap 6y agoI have a DM on mobile with a failed slack message in it that has clogged my UI for months; literally months. On mobile it means that I can't tell if this user has responded to a message or is online at all. I tried telling it not to send ages ago when it actually failed but it hasn't worked, and frankly now it's so far back in history it's impossible for me to try again. I've deleted slack and re-installed to no avail. It's really an awful problem.
- xmprt 6y agoCan you not delete the message after it fails?
- adrianmonk 6y agoOK, that's a good question. I can't recall that there's a way to. But I can't reproduce it now to test it and answer definitively.