A great opportunity to update the part of my API code that deals with Slack to make it handle errors more gracefully!
Users may be unable to connect or experiencing degraded performance
101–110 of 225 posts
Re: Users may be unable to connect or experiencing degraded performance
#102Is Discord a viable alternative to Slack? If not, why not?
Unfortunately their video is terrible. Screen sharing would peg our computers and spin up our coolers.
Re: Users may be unable to connect or experiencing degraded performance
#103Why do companies spring for slack and webex when xmpp exists and works better?
Cost. It costs money to maintain it.
Example: We pay for looker. One day I thought to myself I'll spin up Metabase and try it out for myself against our prod database. It worked very well, fast and easy to query my data unlike Looker.
I haven't used it in about a month and today I try to access it but the app just doesn't load. Now I need to spend time to look into why this app isn't loading. Nevermind that I have zero Java experience or devops experience. I just ran a Docker file per their instructions.
It's often cheaper to pay for a service.
Re: Users may be unable to connect or experiencing degraded performance
#104This backend outage reveals how horrible the Slack UI is implemented. You post a message.... you think it got sent. Then 1min later, it tells you it was not.
> 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.
Re: Users may be unable to connect or experiencing degraded performance
#105It has had slow performance since I started using it 3 years ago.
Re: Users may be unable to connect or experiencing degraded performance
#106Has worked fine for me in Spain all day.
Re: Users may be unable to connect or experiencing degraded performance
#107This backend outage reveals how horrible the Slack UI is implemented. You post a message.... you think it got sent. Then 1min later, it tells you it was not.
It's not an implementation detail, it's a whole (controversial) UX design pattern: https://www.smashingmagazine.com/2016/11/true-lies-of-optimi...
I worked on a project that used this, I hated it. The excuse I was given repeatedly was "it's unlikely to fail" which I kept responding with "but when it does, the user is already 3 pages away and we have no good way to tell them so they're SOL"
Re: Users may be unable to connect or experiencing degraded performance
#108Earlier quoted context omitted.
It's not an implementation detail, it's a whole (controversial) UX design pattern: https://www.smashingmagazine.com/2016/11/true-lies-of-optimi...
I worked on a project that used this, I hated it. The excuse I was given repeatedly was "it's unlikely to fail" which I kept responding with "but when it does, the user is already 3 pages away and we have no good way to tell them so they're SOL"
You could surface a notification when it fails...
Re: Users may be unable to connect or experiencing degraded performance
#109The android mobile apps have been horrible ever since the update a few months back. messages dont get refreshed even if the status shows updated
Re: Users may be unable to connect or experiencing degraded performance
#110Slack is generally an immensely slow piece of Software.