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

Slack – Degraded service affecting multiple features

status.slack.com

Post reply on HN
Print view View original

181–190 of 246 posts

Re: Slack – Degraded service affecting multiple features

#181

Post by untog »

pmlnr wrote: post #165
untog wrote: post #148

Earlier quoted context omitted.

Obviously you can create IRC integrations for anything. But how many are installable with one click, like Slack integrations are? Having to write custom implementations is yet another extra task and point of failure compared to just paying someone to manage it all for you.

another "but". First "but it doesn't scale". Now "but integrations". There will always be another "but", and there will always be a link on the internet showing that it's been done already. "but shiny web gui" - https://thelounge.chat/ "but mobile app" - https://github.com/MCMrARM/revolution-irc "but it's complicated" - https://www.mirc.com/ since 1995 IRC does have limits. Some. One is that to make it "modern" it ne…

> another "but"

That's my entire point. It's death by a thousand cuts. Now I'm responsible for an IRC server, a web frontend, a mobile app and a bouncer.

The OP said "just run an IRC server". There is no "Slack or just an IRC server". There's "Slack or a number of connected, interdependent services you need to maintain". I'm not saying it can't be done, or that it isn't the right answer for some people, but it's also a lot more work (and thus, expense) than just paying for Slack. It absolutely makes sense that people do it.

Re: Slack – Degraded service affecting multiple features

#182

Post by ageitgey »

valerij wrote: post #135
amelius wrote: post #129

Earlier quoted context omitted.

> a genius at IBM Are you saying it is the user's fault where it is clearly Slack's inadequate implementation that is the problem?

i stand by my opinion that "lets create one chat room and invite hundreds of thousands of people into it" is a bad idea regardless of what technology implements the chat room

I love that companies will make it hard to expense a $50 meal but they will gladly let you book an hour meeting with 20 high-paid developers or even let you directly ping 200,000 people which must cost the company many thousands of dollars.

Re: Slack – Degraded service affecting multiple features

#184

Post by pmlnr »

untog wrote: post #181
pmlnr wrote: post #165

Earlier quoted context omitted.

another "but". First "but it doesn't scale". Now "but integrations". There will always be another "but", and there will always be a link on the internet showing that it's been done already. "but shiny web gui" - https://thelounge.chat/ "but mobile app" - https://github.com/MCMrARM/revolution-irc "but it's complicated" - https://www.mirc.com/ since 1995 IRC does have limits. Some. One is that to make it "modern" it ne…

> another "but" That's my entire point. It's death by a thousand cuts. Now I'm responsible for an IRC server, a web frontend, a mobile app and a bouncer. The OP said "just run an IRC server". There is no "Slack or just an IRC server". There's "Slack or a number of connected, interdependent services you need to maintain". I'm not saying it can't be done, or that it isn't the right answer for some people, but it's also…

Why is paying another company better than getting employees and paying them the same or even less money?!

When did this madness start?

Re: Slack – Degraded service affecting multiple features

#185

Post by LinuxBender »

kkirsche wrote: post #15
darkwater wrote: post #13

Earlier quoted context omitted.

Or not. I'm remote and I cannot ask questions nor coordinate action to solve live production problems due to this outage. Slack is becoming a SPOF for many organizations, especially distributed.

For anyone else curious, SPOF means single point of failure in this context.

At my workplace we were told SPOF was too negative, so one of the engineers changed it to SPOS. Single Point Of Success.

Re: Slack – Degraded service affecting multiple features

#186

Post by mkohlmyr »

kortilla wrote: post #167
iamnotacrook wrote: post #161

Earlier quoted context omitted.

If you want to tell everyone in your company something, you could email them I guess. Is it the fact that it's a "chat room" which means you expect it not to work? What's best, here? SMS? Email? Putting something on the website and making everyone check the website once a day at noon? Tell one in ten people and get them to "pass it on"?

Is this a serious question? Companies have been using email for internal announcements for decades.

Yes, and he's making the point that it manages to work. And that perhaps your expectation should be the same for a chat client as for an email client. Which may or may not be a valid point.

Re: Slack – Degraded service affecting multiple features

#187

Post by noelsusman »

exabrial wrote: post #102

One problem with Slack we have in the finance world is that _literally everything_ employees say on company assets needs to be recorded and readily accessible for audit (No this is not an invasion of privacy, you're on company time on company systems, we don't peer into your personal phone or anything). Unfortunately, Slack does not do this very well. I'd really like to know if there's another service that _does_ do…

Probably Teams. https://docs.microsoft.com/en-us/microsoftteams/security-com...

Re: Slack – Degraded service affecting multiple features

#188

Post by whack »

kortilla wrote: post #167
iamnotacrook wrote: post #161

Earlier quoted context omitted.

If you want to tell everyone in your company something, you could email them I guess. Is it the fact that it's a "chat room" which means you expect it not to work? What's best, here? SMS? Email? Putting something on the website and making everyone check the website once a day at noon? Tell one in ten people and get them to "pass it on"?

Is this a serious question? Companies have been using email for internal announcements for decades.

And without proper mailing-list-moderation, that too can cause email storms. No one blames "the genius who decided to put everyone in one mailing list" when that happens.

The real fail here isn't putting everyone in one channel. The real fail is not using/providing proper admin tools

Re: Slack – Degraded service affecting multiple features

#189

Post by LinuxBender »

cloverich wrote: post #140
Twirrim wrote: post #104

Earlier quoted context omitted.

At one stage when there was an outage about a year ago, folks at work were scrambling around trying to get HipChat resurrected (which we'd been using prior to moving to Slack). I had an ircd of some description installed, configured and ready for use in under 3 minutes, and started to get my team using it as a stop gap measure. Had that rolling long before either the outage was resolved, or the HipChat server was res…

Do you have a recommended server / client? The last time I tried to use IRC (joining an existing chat) I actually had quite a bit of trouble, and ended up just giving up.

For ages, I ran unrealircd [1] and anope [2] services. One could put TheLounge [3] (web front end with redis) in front of it for persistence. Not as easy as inspire to set up, but rock solid and feature rich.

[1] - https://www.unrealircd.org/

[2] - https://www.anope.org/

[3] - https://thelounge.chat/

Re: Slack – Degraded service affecting multiple features

#190

Post by llamataboot »

valerij wrote: post #62

reminds me of that one time a genius at IBM created an `ibm-global-announcements` channel and force-invited 200'000 people in it, and then some guy `@channel`d and all ibm's slack workspaces were down for 30 minutes https://status.slack.com/ibm/2018-03/f01d4c22cd953dd7 https://i.imgur.com/Rk6Kdgp.png EDIT: also that channel made using slack impossible for mac book air users, they had around 80% cpu usage for slack. s…

I still hate that anyone can add anyone to a channel - it's not an "invite", it's just global "add to room" privileges.

In general I find Slack not very concerned with your own ability to control your experience (no ignore user feature, can be added to rooms, can be added to rooms that then get pinged with @channel and your notifications start blowing up, etc).

This may be 'expected' in a small company where of course everyone should talk to everyone, but for larger companies and the plethora of various open-source or interest-based communities now using Slack, it's not so good.

Post reply on HN