Dear Slack: Your service is down, it's not "slow performance". Be honest to your customers, or I will make sure our team switches to Microsoft Teams.
We have both Slack and Teams. Almost everyone I know who has an option picks Slack.
Users may be unable to connect or experiencing degraded performance
21–30 of 225 posts
Re: Users may be unable to connect or experiencing degraded performance
#22This 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.
The message is in a light grey colour until it's confirmed. I'm not saying it's amazingly obvious but at least the information's there. In fact I'm mostly posting this comment so others know what to look for. (I know this because I just spent 60 seconnds staring at my message trying to figure out why the formatting was off before it told me it wasn't sent. It sent immediately when I retried though.)
I’ve had messages that were black for at least one minute turn gray and only then notify me that they failed to send
Re: Users may be unable to connect or experiencing degraded performance
#23Dear Slack: Your service is down, it's not "slow performance". Be honest to your customers, or I will make sure our team switches to Microsoft Teams.
We have both Slack and Teams. Almost everyone I know who has an option picks Slack.
I've never used Teams, but if everyone prefers Slack over it, it must be horrible.
Re: Users may be unable to connect or experiencing degraded performance
#24Dear Slack: Your service is down, it's not "slow performance". Be honest to your customers, or I will make sure our team switches to Microsoft Teams.
We have both Slack and Teams. Almost everyone I know who has an option picks Slack.
I prefer Slack too, but I'd like my services to be reliable and not go down on a regular basis.
Re: Users may be unable to connect or experiencing degraded performance
#25This 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.
The message is in a light grey colour until it's confirmed. I'm not saying it's amazingly obvious but at least the information's there. In fact I'm mostly posting this comment so others know what to look for. (I know this because I just spent 60 seconnds staring at my message trying to figure out why the formatting was off before it told me it wasn't sent. It sent immediately when I retried though.)
[deleted]
Re: Users may be unable to connect or experiencing degraded performance
#26Dear Slack: Your service is down, it's not "slow performance". Be honest to your customers, or I will make sure our team switches to Microsoft Teams.
Didn’t Teams just have a massive outage too?
Re: Users may be unable to connect or experiencing degraded performance
#27Dear Slack: Your service is down, it's not "slow performance". Be honest to your customers, or I will make sure our team switches to Microsoft Teams.
Please don’t punish your coworkers like that just for your personal pleasure.
Re: Users may be unable to connect or experiencing degraded performance
#28Dear Slack: Your service is down, it's not "slow performance". Be honest to your customers, or I will make sure our team switches to Microsoft Teams.
We have both Slack and Teams. Almost everyone I know who has an option picks Slack.
Yep, Slack certainly has major performance/memory usage issues. And somehow Teams is even worse.
Re: Users may be unable to connect or experiencing degraded performance
#29Re: Users may be unable to connect or experiencing degraded performance
#30It's taking ages for me to switch channels in the Linux desktop app.
Which means there's a network request involved in switching channels, which is not a great design.