Users may be unable to connect or experiencing degraded performance

Re:Users may be unable to connect or experiencing degraded p... by onion2k on Monday October 05, 2020 @12:48PM (#24689443)

I understand why they use this UI paradigm, but I don't understand why it's not reversed eg make it light grey until the API has confirmed it's been posted. That would maintain the nice 'you posted a message nice and quickly' responsive UI idea, but without making the user angry when it doesn't work.

Even if the idea is to fool the user in to thinking Slack is faster than it is, the UI could at least use the reversed 'light grey until confirmed' UI once it's detected that there's a problem. That would make it a bit less tiresome.

[ Parent | on HN ]

Re:Users may be unable to connect or experiencing degraded p... by ggreer on Monday October 05, 2020 @12:52PM (#24689489)

Ripcord[1] does what you describe. My guess is that Slack doesn't do this because it makes Slack's latency extremely obvious. Even on a great connection, a decent fraction of messages will take multiple seconds to go from gray to black. Apparently even when Slack's API is operating normally, it can take a very long time to respond with, "Your message was received."

1. https://cancel.fm/ripcord/

[ Parent | on HN ]

Re:Users may be unable to connect or experiencing degraded p... by emerged on Monday October 05, 2020 @12:52PM (#24689485)

This morning I sent a message and it was greyed out until finally sending a minute later. So it would seem both cases are possible somehow. Different stages of data propagation?

[ Parent | on HN ]