Agreed and I like the "dependable" phrasing. I think UX needs to be transparent about what happens.
For ex. If I like a post don't mark it "liked" until it's not broadcast. Personally that's why I lik...
That "like" usecase will cause you a lot of issues. In practice we have to save the like locally (and show it to the user) and retry sending to relays later. Otherwise, people will just get frustrated because everything will be really slow to give feedback to users.
Zaps on mobile are like that, for instance, it has a little progress bar when sending and it only clears when finishes after seconds/minutes. People hate it. It's way better if we switch to fast confirmation quickly and then have a queue that can retry later if it fails.
Zaps on mobile are like that, for instance, it has a little progress bar when sending and it only clears when finishes after seconds/minutes. People hate it. It's way better if we switch to fast confirmation quickly and then have a queue that can retry later if it fails.