I would actually rather that Damus not keep trying failed relays after those few initial seconds, and then when it gives me the X of X report I know that's the end state of things unless I take some action myself. If Damus is going to keep trying then all that "result" is is just a status at a point in time, and that status could be different one second later.
Publishing is complex, and at least in damus is not apparent which relays an event is published to.
For example, say you have 10 relays. You hit post, and hear back from three with successful post. Two relays reject your post. You have not heard back from the remainder five relays in a short amount of time.
Compare and contrast with posting on single relay X.
See design that reveals the complexity to the user - https://github.com/damus-io/damus/issues/2083#issuecomment-2215338126
Discussion
This discussion is about surfacing the relay posted / not posted feedback as UI to the poster, not the logic of publishing to relays.
yes that's what I mean
I don’t understand
I mean if I sent a post on Damus, and a toast popped up after a few seconds saying "Sent to 3/5 relays", to me that would be meaningless if Damus kept trying to send to the other two relays.
It wouldn't help with confidence at all, because maybe a short while after the other two relays will take it. Who knows?
For such a notification, it only makes sense to me if it's an end result and not an update at a point in time.
Like on WhatsApp, when you get a message failed notice it means the message failed and WhatsApp is not going to keep trying anymore. If you want to try again, go ahead, it's on you.