Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Users may be unable to connect or experiencing degraded performance

status.slack.com

Post reply on HN
Print view View original

111–120 of 225 posts

Re: Users may be unable to connect or experiencing degraded performance

#111

Post by cameronfraser »

jrib wrote: post #52
seibelj wrote: post #11

Slack is unusable, but it did get me to restart Docker which had ballooned to 16 GB memory and a bazillion processes. Modern software development is something else

waiting the 10 seconds it takes to build a javascript frontend these days always leaves me reminiscing about my highschool days of editing my javascript in notepad and refreshing my browser to instantly see my mistakes. I understand there are benefits and reasons for the state of affairs...

if its taking 10 seconds to rebuild then I doubt the bundler is the problem, I get near instant updates on changes with a fairly vanilla react/webpack setup

Re: Users may be unable to connect or experiencing degraded performance

#112

Post by StavrosK »

znpy wrote: post #79
StavrosK wrote: post #23

Earlier quoted context omitted.

I've never used Teams, but if everyone prefers Slack over it, it must be horrible.

There are a lot of other adjectives between "slack-like" and horrible. I've used teams in the past and it's not that bad. It's a valid alternative to slack imho.

I don't know, I hate Slack. It's slow, bloated, can't even keep up with my typing on a brand new Ryzen and it doesn't even do conversations well.

I know I sound like a Zulip shill, but try that for a bit and you'll see the difference, I love it.

Re: Users may be unable to connect or experiencing degraded performance

#113

Post by ryanSrich »

rexreed wrote: post #89
juvoni wrote: post #81

Earlier quoted context omitted.

Yes it is, but a key feature discord lacks is threads. Still it is a huge upgrade from Slack in terms of performance and ease of use.

I am a heavy Slack user but I don't use threads. Threads seem like a confusing mess. Am I missing something not using Slack threads?

Wow really? I'm genuinely surprised. I couldn't imagine using Slack without threads, how do you keep discussions on track for certain topics? At any given time I have 30-40 threads going, which means I can easily track conversations. Without threads I'm just endlessly scrolling, or trying to find something, or god forbid relying on Slack's utterly broken search.

Re: Users may be unable to connect or experiencing degraded performance

#114

Post by fphilipe »

juvoni wrote: post #81
rexreed wrote: post #60

Is Discord a viable alternative to Slack? If not, why not?

Yes it is, but a key feature discord lacks is threads. Still it is a huge upgrade from Slack in terms of performance and ease of use.

Messages within threads are not searchable. Maybe that changed, but until recently that was definitely the case.

Re: Users may be unable to connect or experiencing degraded performance

#115

Post by mushishi »

rexreed wrote: post #89
juvoni wrote: post #81

Earlier quoted context omitted.

Yes it is, but a key feature discord lacks is threads. Still it is a huge upgrade from Slack in terms of performance and ease of use.

I am a heavy Slack user but I don't use threads. Threads seem like a confusing mess. Am I missing something not using Slack threads?

I would say they help to scope a part of a discussion that clarifies some detail or maybe when giving a link elsewhere, without derailing the mainline of the discussion.

It's useful when people arrive in the discussion at different times and you don't want to necessarily let the whole channel to be notified about your specific remark, and don't want to write a private message either -- one reason being it would lose the context.

In our project we have multiple channels that have actively 3-5 persons and work at different times. The things we chat about are lightweight changes or news, or maybe someone has a quick clarifying question about implementation detail. Something that wouldn't be posted in an issue for one reason or other.

Re: Users may be unable to connect or experiencing degraded performance

#116

Post by epicide »

saagarjha wrote: post #86
Wowfunhappy wrote: post #80

Earlier quoted context omitted.

Funny story—iMessage on one of my laptops used to very frequently tell me "This message could not be delivered" even though the person on the other end received it fine. (The problem went away after an OS reinstall.)

Pessimistic design lets you surprise and delight ;)

It is not delightful to accidentally annoy someone with the same message several times because you thought it did not send.

Re: Users may be unable to connect or experiencing degraded performance

#117

Post by rexreed »

ryanSrich wrote: post #113
rexreed wrote: post #89

Earlier quoted context omitted.

I am a heavy Slack user but I don't use threads. Threads seem like a confusing mess. Am I missing something not using Slack threads?

Wow really? I'm genuinely surprised. I couldn't imagine using Slack without threads, how do you keep discussions on track for certain topics? At any given time I have 30-40 threads going, which means I can easily track conversations. Without threads I'm just endlessly scrolling, or trying to find something, or god forbid relying on Slack's utterly broken search.

The comment below is on point. It's all-or-nothing on threads. If people don't commit to using threads it gets hopeless really fast.

Re: Users may be unable to connect or experiencing degraded performance

#118

Post by arwineap »

adrianmonk wrote: post #104
jacquesc wrote: post #13

This 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 I…

I have a DM on mobile with a failed slack message in it that has clogged my UI for months; literally months.

On mobile it means that I can't tell if this user has responded to a message or is online at all. I tried telling it not to send ages ago when it actually failed but it hasn't worked, and frankly now it's so far back in history it's impossible for me to try again.

I've deleted slack and re-installed to no avail. It's really an awful problem.

Re: Users may be unable to connect or experiencing degraded performance

#119

Post by brundolf »

epicide wrote: post #116
saagarjha wrote: post #86

Earlier quoted context omitted.

Pessimistic design lets you surprise and delight ;)

It is not delightful to accidentally annoy someone with the same message several times because you thought it did not send.

Pretty sure the GP was /s
Post reply on HN