Live data from Hacker News

Slack – Degraded service affecting multiple features

status.slack.com

141–150 of 246 posts

Re: Slack – Degraded service affecting multiple features

#141
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…

> 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?

Well, you know what happens when you email @yourcompany.com? Is it a protocol problem? Implementation problem? User problem?

Re: Slack – Degraded service affecting multiple features

#142
post #130
post #99

Earlier quoted context omitted.

"just running an IRC server" is... a lot. Or can be. Who is running it? Does it scale well? How is login synced with corporate logins? What about mobile devices? It's not "better" than email, it's different. Real time. It has a million and one service integrations, which IRC doesn't. Point is, it's really not all that crazy to just pay a third party to manage all this stuff for you. You might imagine the alternative…

Come on, in the 90s and early 00s, volunteers ran and managed IRC networks scaling up to hundreds of thousands of users. This was back when hardware and bandwidth were much weaker and 100x more expensive. It's really not that hard.

Yes, volunteers ran these things. How many? Because you're going to need to have paid employees rather than volunteers running your servers. Is it going to be more reliable and cost effective than just paying a third party to run a service for you?

Re: Slack – Degraded service affecting multiple features

#143

Earlier quoted context omitted.

There should be a way to turn off @here and @channel. It should be a user-level setting, a channel-level setting, and an organization-level setting. Even if my org or channel doesn't opt out, I should be able to.

Or at least a way to force users to pay a fee whenever they use those features.

It would be interesting to have a karma function whereby it was based on your use of @channel or @everyone - or something similar to how HN used to require 500 karma to be able to downvote...

Re: Slack – Degraded service affecting multiple features

#144
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'm more surprised that the IBM server has 200k users?

According to Wikipedia, IBM has 380k employees. Not that surprising that half of the use the company Slack.

Re: Slack – Degraded service affecting multiple features

#145
post #74

Can someone explain to me why any company should outsource something as critical as internal communication to a company that is 5 years old? The video messaging left aside, is it really that better than time-tested solutions like email or just running an IRC server?

IRC is pretty much useless since you don't have history. Comparing Slack and IRC are like comparing TCP and HTML5. Why IRC is pretty bad in enterprise:

- no audio / video

- no history

- no SSO / AD integration

- no rich features like links, pictures, upload docs ect ...

- easy bot integration with APIs, I can have Datadog pushing things to Slack ( alerts, graph... )

- no archiving channels on the go, Slack is very useful when you have an incident and you create a temp channel and then archive it when the incident is closed.

Re: Slack – Degraded service affecting multiple features

#146
post #74

Can someone explain to me why any company should outsource something as critical as internal communication to a company that is 5 years old? The video messaging left aside, is it really that better than time-tested solutions like email or just running an IRC server?

Ive always said Slack is IRC for millennials.

"The Wheel of Time turns, and Ages come and pass, leaving memories that become legend. Legend fades to myth, and even myth is long forgotten when the Age that gave it birth comes again."

Re: Slack – Degraded service affecting multiple features

#148
post #124
post #99

Earlier quoted context omitted.

"just running an IRC server" is... a lot. Or can be. Who is running it? Does it scale well? How is login synced with corporate logins? What about mobile devices? It's not "better" than email, it's different. Real time. It has a million and one service integrations, which IRC doesn't. Point is, it's really not all that crazy to just pay a third party to manage all this stuff for you. You might imagine the alternative…

> Does it scale well? It's IRC. On modern hardware. It's practically infinite. > it has a million and one service integrations, which IRC doesn't. There and were are things way before Slack, eg https://loqi.me/

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.

Re: Slack – Degraded service affecting multiple features

#149

In other news: an unexplained productivity spike has been recorded today across the tech industry.

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.

Yeah, i understand. hosting your own mattermost (or other slack clone) is not enough for you? You can also have 2 self-hosted solution on different servers (one on our own, one on any CSP), in case your server fails.

Re: Slack – Degraded service affecting multiple features

#150

Earlier quoted context omitted.

The internet is specifically designed to route around downed links such that there is no SPOF, that’s the theory anyway. However, when major backbones go down it takes it a while to recover.

Well, kinda! Just look at this recent CloudFlare blog post[1]. It's true, theres no Single Point of Failure - there are MANY points of failure ;) [1]: https://blog.cloudflare.com/how-verizon-and-a-bgp-optimizer-...

The internet, like the road network is designed to cope with failures - even if a major problem leads to congestion.

We build services on top of that that don't cope with failures.

Post reply on HN