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

Slack outage: Connectivity issues affecting all workspaces

status.slack.com

Post reply on HN
Print view View original

71–80 of 278 posts

Re: Slack outage: Connectivity issues affecting all workspaces

#71

Post by rkeene2 »

dswalter wrote: post #28
sdf43543t345 wrote: post #4

IRC had uptime in the scale of decades. Why are our 2018 solutions so fragile?

Native emoji support, aesthetically pleasing front-ends, and clear product direction are some of the main positives I see, even if the combination of php on the backend and electron on the frontend aren't the most sophisticated technical components in history. I prefer decentralized and open things, but a cohesive vision can sometimes provide a better user experience across a more restricted set of functionality than…

Native emoji support, pretty front-ends, and clear product direction are possibilities on-top of IRC (or XMPP) since their absence isn't a core part of IRC (or XMPP) -- it's just not a good way to make a profit it if you don't lock down the network and act as the gatekeeper of the interface. Slack's API is fairly open though and it's not a huge hurdle to interact with it. I built an IRCSlack gateway that bridges the differences fairly well ( https://slack.tcl-lang.org/ , you know, if Slack were working).

Re: Slack outage: Connectivity issues affecting all workspaces

#72

Post by [deleted] »

palencharizard wrote: post #47
ivm wrote: post #36

Earlier quoted context omitted.

Luckily most of my active communities are on Discord nowadays. It works much faster and even has a dark theme by default.

> even has a dark theme by default. I love how having a dark theme is second only to "it works" in terms of how we pick services these days XD

[deleted]

Re: Slack outage: Connectivity issues affecting all workspaces

#73

Post by dictum »

ivm wrote: post #36
sarreph wrote: post #33

You know how much of the community uses one messaging system when 15 minutes after it going down, it has over 40 points on the front page! This says a lot about how it's a single point of failure in modern company comms. It's even worrying to think about how some users probably have production-dependent (dare I postulate it) workflows in Slack that get crippled by its outage... ITT: Chat about decentralisation that w…

Luckily most of my active communities are on Discord nowadays. It works much faster and even has a dark theme by default.

I say this as someone who almost always prefers the dark theme wherever it is available: I wonder how much this desire for dark interfaces comes from almost every app interface having bright colors on white.

Somewhere along the shift to flat design, grays and non-bright colors have been ignored in the visual design of applications.

Re: Slack outage: Connectivity issues affecting all workspaces

#75

Post by hs86 »

dswalter wrote: post #28
sdf43543t345 wrote: post #4

IRC had uptime in the scale of decades. Why are our 2018 solutions so fragile?

Native emoji support, aesthetically pleasing front-ends, and clear product direction are some of the main positives I see, even if the combination of php on the backend and electron on the frontend aren't the most sophisticated technical components in history. I prefer decentralized and open things, but a cohesive vision can sometimes provide a better user experience across a more restricted set of functionality than…

Have you tried IRCCloud? Their web based front-end is as nice as Slack's but it still works with decentralized IRC servers. They also manage the client's state (unread messages) better than regular IRC bouncers.

Re: Slack outage: Connectivity issues affecting all workspaces

#76

Post by amarraja »

neuromantik8086 wrote: post #45
amarraja wrote: post #38

Spare a thought for the chatops crowd who may be blissfully unaware that their own infrastructure is down

I have little pity for the folks who decided that re-implementing a shell in a chat application was a well-conceived notion.

Hopefully they're learning this lesson.

I can just see it now. A company's app is dying from all the timeouts to a slack webhook, however they can't deploy because slack is down.

Re: Slack outage: Connectivity issues affecting all workspaces

#77

Post by aliljet »

JeanFred wrote: post #61
aliljet wrote: post #51

Are there solid Slack-style self-hosted alternatives? (The gitlab of the slack world, to be clear.)

Gitlab itself ships with Mattermost " rel="nofollow">https://mattermost.com/> :)

This doesn't look half bad... while slack's down, seems like a pretty optimal chance to try https://github.com/mattermost/mattermost-server

Re: Slack outage: Connectivity issues affecting all workspaces

#78

Post by detaro »

dswalter wrote: post #28
sdf43543t345 wrote: post #4

IRC had uptime in the scale of decades. Why are our 2018 solutions so fragile?

Native emoji support, aesthetically pleasing front-ends, and clear product direction are some of the main positives I see, even if the combination of php on the backend and electron on the frontend aren't the most sophisticated technical components in history. I prefer decentralized and open things, but a cohesive vision can sometimes provide a better user experience across a more restricted set of functionality than…

Emoji seem to work just fine on IRC nowadays, what do you mean by "native" support? The shortcodes? The fact that there's official clients you can entirely rely on supporting it?

Re: Slack outage: Connectivity issues affecting all workspaces

#79

Post by nixgeek »

majewsky wrote: post #69
nixgeek wrote: post #31

Earlier quoted context omitted.

Slack Enterprise has never run on your own infrastructure.

It doesn't? I thought that was its only reason to exist.

It’s pitch is a little different, it gives you ‘Workspaces’ which are somewhat connected, and tools to manage big deployments.

IBM, Oracle and many large companies use it because 100,000+ participants in one workspace is quite unmanageable.

Think channel namespacing whilst unifying user provisioning and enabling DM and MPDM across the entire company. Users can have access to one or many namespaces, they sign in once and it populates all enabled workspaces into that users client.

You can share channels between workspace within Enterprise Grid fairly trivially (although this now works between Slack tenancies owned by different companies too!)

Still runs on the same infrastructure in AWS as other Slack customers though.

From a policy perspective you can push down settings to all Workspaces in your SEG, and define whether you “centrally control” or “delegate to Workspace owners” on a setting by setting basis.

Re: Slack outage: Connectivity issues affecting all workspaces

#80

Post by crankylinuxuser »

Sir_Cmpwn wrote: post #49

If only there were a venerable, decentralized instant messaging system we could use, perhaps some kind of internet relay chat system... You reap what you sow. Depending on Slack for your communications is a bad idea. I can't even remember the last time any of the IRC networks I frequent had a total outage.

Irc left out federation when the spec was crafted in 1984. It was deemed to bandwidth heavy.

Jabber/xmpp was a good step in the right direction. Too bad it overused plugins and bad extensions and XML abuse. Would have been loads better had they though far enough in advance.

Post reply on HN