Closed manuroe closed 3 weeks ago
I wonder what should happen when there is already one message (or more) in failed state, and the user sends another message. I think both of the following options are reasonable:
There could even be some failed and some pending local echoes at the same time (in the case multiple messages failed and just one was retried). Again the question arises what to do when a message is sent (i.e. a new local echo added).
Once a message has failed completely and only can be send again manually by re-triggering the message should not be part of the queue anymore. The user would see the message (locally) in the timeline with the error message "Cannot be send".
Any following message should enter the queue and be send.
It's debatable how long the failed message should stay locally on the phone. WA for example keeps all failed messages forever (unless you uninstall the app)
Okay. What I'm a little worried about then is the case of the previous message entering failed state just as the user is about to send another message. They probably don't intend the second one to be sent before / independently of the first (now failed) one, right? Anyways, can always revisit later.
Yes, that's true but a scenario I could live with.
Most if not everything was covered by https://github.com/element-hq/element-internal/issues/312
As a user, I want to see the sending status in the timeline when posting a message:
messages that failed to sent must be highly visible in the timeline
Timestamp and postion in the timeline (doc):
Stretch goals
None at this time