News for hackers. Stuff that matters.
Re:Slack Connectivity Issues by alrs on Friday June 10, 2016 @01:57PM (#11878422)
We lost USENET to Reddit and Stack Overflow, and it feels like we're about to lose IRC to Slack.

The Internet dies a little every time someone starts a new Slack channel. I'm glad for the SPOF reminder.

Can you imagine how many copy-pasted certs, passwords, and CC# would be hoovered up were Slack compromised?

Re:Slack Connectivity Issues by skywhopper on Friday June 10, 2016 @02:11PM (#11878546)
It's sad, I agree. But IRC is such a pain for most people to deal with it's never going to reach a mass audience in its current form. Whereas Slack is dead-simple easy to use and no one has trouble understanding how to use it. If you want to save IRC, then we need to make it usable by everyone.
Re:Slack Connectivity Issues by silencio on Friday June 10, 2016 @02:16PM (#11878599)
Plus it's not like IRC itself isn't also a SPOF in a different way. I've had [private] servers go down, netsplits and connectivity issues on freenode effectively hindering communication...

And all of the things that people use to make IRC more bearable are problems in their own right. Imagine a vulnerability with the znc bouncer? Tons and tons of people compromised right there. irccloud down? Oops. and so on.

Re:Slack Connectivity Issues by rocky1138 on Friday June 10, 2016 @03:27PM (#11879255)
Can't we make it better? Can't we write an IRC protocol upgrade, server, and client that does the same thing that Slack beats IRC with?

Namely, archived chats and in-chat images.

Re:Slack Connectivity Issues by api on Friday June 10, 2016 @02:03PM (#11878479)
Don't blame the replacement. We lost USENET to spam and IRC to lack of innovation and poor UX.

I stopped using both USENET and IRC long before any of these alternatives appeared.

Re:Slack Connectivity Issues by DanielStraight on Friday June 10, 2016 @02:13PM (#11878565)
Right. People are more than happy to use free, open source, standardized, distributed, self-owned software and services... when that software and those services offer the best solution for their needs. There's only so much ease of use and functionality people can be realistically expected to trade away.

Yeah, Slack is down... but the gains made from using it outweigh the pain of having to deal with the failure. Improve the less proprietary options to where this isn't true anymore and people will stop using the more proprietary options.

There are always trade-offs, and expecting people not to make them is unrealistic.

Re:Slack Connectivity Issues by Touche on Friday June 10, 2016 @02:10PM (#11878540)
The question I have is why aren't industry leaders contributing to these specs? Why isn't Slack sending RFCs to improve IRC?
Re:Slack Connectivity Issues by skywhopper on Friday June 10, 2016 @02:14PM (#11878583)
What benefit would it be to Slack to publish their protocols? Or to IRC to know about them? I think the chances are extremely slim that IRC could be improved by knowing how Slack works. Slack is not a technical marvel with mysterious underpinnings. It's a centralized chat service with a pretty interface, simple clients, and (the secret sauce that won them all the converts) seamless integrations with pretty much every other open or semi-open service out there.
Re:Slack Connectivity Issues by Touche on Friday June 10, 2016 @02:38PM (#11878805)
IRC would benefit simply by having someone that's actually working to improve it. It doesn't matter if the improvements are superficial; humans are superficial, that stuff matter a lot.
Re:Slack Connectivity Issues by api on Friday June 10, 2016 @02:13PM (#11878563)
There is no economic model to support free/open systems and standards. It's in nobody's best interest.
Re:Slack Connectivity Issues by Touche on Friday June 10, 2016 @02:36PM (#11878778)
Slack's business is built on free/open standards, they don't exist without http and html. Asking them to contribute in their area of expertise is not asking a lot.
Re:Slack Connectivity Issues by ams6110 on Friday June 10, 2016 @02:48PM (#11878895)
Not just that, none of the current web economy exists without linux and gnu and other free/libre software.
Re:Slack Connectivity Issues by aaronbrethorst on Friday June 10, 2016 @02:11PM (#11878547)
Why would they want to? Improving IRC does nothing to benefit Slack.
Re:Slack Connectivity Issues by chrisfosterelli on Friday June 10, 2016 @02:07PM (#11878510)
This is a very good point. Many people I know stopped using IRC quite a bit before they ever started using Slack.
Re:Slack Connectivity Issues by draw_down on Friday June 10, 2016 @02:30PM (#11878722)
I really wish people would stop pretending Slack is just IRC with a brand name slapped on. It's so much better to use in every single way.

If you don't care about UX then you don't care about UX, but at least have the intellectual honesty to say it.

Re:Slack Connectivity Issues by spotman on Friday June 10, 2016 @02:42PM (#11878842)
I don't think the parent comment is talking about the UX really.

But on the topic of UX and what are or are not losing, I will say that the UX of slack is not so good when it eats 2gb of memory all day and beachballs a modern day iMac quite badly if you have a channel with lots of fancy formatting.

I have written to slack about this and they wrote a polite response back acknowledging the issue. Really hope they do solve this soon (Despite the connectivity issues) because it's become unusable for my team lately. Supposedly according to slack it is compounded when you have multiple teams.

We have a team per client as we primarily do consulting, so now we have had to switch some teams over to another solution so that we can allow the teams that must be in slack to stay in slack.

So, while I think slack has the potential to be much better in every single way, days like today illustrate that it's an SPOF, and on days when it is available, I would not call the experience reliably good, not as reliably good as modern day IRC is, unfortunately. (and I don't say this lightly, i love things like in-line code blocks, @ notifying people, mobile clients, and more)

Re:Slack Connectivity Issues by forgottenpass on Friday June 10, 2016 @04:03PM (#11879566)
If you don't care about UX then you don't care about UX, but at least have the intellectual honesty to say it.

I care about UX. What I don't care for is the idea the UX has become a distance multiplier when talking about differences in software.

Is anyone suggesting that Slack is literally just a client for the existing IRC protocol? No. They're suggesting that slack is just a particularly nice and popular iteration on IRC. You seem to have some impression that just because a slack feature isn't part of the IRC protocol, that it isn't a short evolutionary distance from IRC. Breed in some modern design conventions and use paradigms and you're pretty close. So it's not crazy to call slack IRC, it's a convenient shorthand for people who don't demand exacting terminology (and don't mind mentioning slack in the same breath as an icky ugly fixed with text-only app).

And that intellectual dishonesty comment is just a way to say a really shitty thing and fly it under dang's radar.

Re:Slack Connectivity Issues by ams6110 on Friday June 10, 2016 @02:51PM (#11878914)
I care about UX but I care about my desired UX. I'm not a slack user but assuming it were to be offered to me I'd want a command-line client. If it didn't have that capability I'd pass.
Re:Slack Connectivity Issues by devhead on Friday June 10, 2016 @03:57PM (#11879526)
Re:Slack Connectivity Issues by gumby on Friday June 10, 2016 @04:20PM (#11879678)
draw_down, could you tell me what you think the advantages are other than UX? I believe the bot integration may be better though I don't use it. I'm genuinely curious: I consider it simply Yet Another Chat System -- am I missing out on something?
Re:Slack Connectivity Issues by liveoneggs on Friday June 10, 2016 @02:16PM (#11878597)
> were Slack compromised? ... again
Re:Slack Connectivity Issues by netguy on Friday June 10, 2016 @02:01PM (#11878455)
Looks like this is a core router internet issue. I cannot access twitter.com, amazon.com, slack.com just to name a few.

However from a remote site I can access all sites. The sites aren't down - the internet routes are down.

Twitter shows a core router for telia went down last night "Telia lost a core backbone router in NY" https://twitter.com/ScottSwezey/status/741124806330978304

My tracerts to slack.com are dropping at a telia.net hop

Looking glass tool shows slack.com and amazon.com are down from the New York (111 8th Ave) router. - http://looking-glass.telia.net/

Re:Slack Connectivity Issues by AdamJacobMuller on Friday June 10, 2016 @02:08PM (#11878519)
FWIW, all of my telia services out of NYC are fine (with no hiccups for days at least).
Re:Slack Connectivity Issues by zjaffee on Friday June 10, 2016 @02:33PM (#11878754)
A ton of sites went down yesterday that were on the cloud-flare network due to them having an issue with one of their transit carriers.

Its crazy how the downtime of what seams like one edge network provider can damage so much of web access.

Re:Slack Connectivity Issues by brown9-2 on Friday June 10, 2016 @01:27PM (#11878075)
Somewhat related, but the status page states Uptime last 30 days: 99.99% but https://status.slack.com/calendar shows quite a few incidents in the past 30 days. Do only total "outages" count against the uptime?

FWIW, 0.01% of 30 days is 4 minutes 19 seconds.

Re:Slack Connectivity Issues by throwanem on Friday June 10, 2016 @02:43PM (#11878848)
The calendar also shows 100% uptime for June 2016 despite the big red outage indicator in today's box.

Perhaps the displayed uptime percentage is for the status page itself?

Re:Slack Connectivity Issues by avitzurel on Friday June 10, 2016 @01:40PM (#11878242)
If your status page is not 100% transparent, don't have a status page. If you can't stand behind the number, don't show the number.

As brown9-2 mentioned, 0.01% in the last 30 days is ~4 minutes, the outage I personally am experiencing with Slack is way more than that.

Re:Slack Connectivity Issues by ppierald on Friday June 10, 2016 @01:26PM (#11878051)
Developer productivity increases by an order of magnitude.
Re:Slack Connectivity Issues by dplgk on Friday June 10, 2016 @01:33PM (#11878162)
Except that I can't communicate with my dev team.
Re:Slack Connectivity Issues by alpb on Friday June 10, 2016 @01:34PM (#11878170)
Yeah, maybe that's why their productivity has increased? :)
Re:Slack Connectivity Issues by dplgk on Friday June 10, 2016 @01:35PM (#11878184)
We're currently discussing architecture decisions.
Re:Slack Connectivity Issues by abduhl on Friday June 10, 2016 @01:45PM (#11878298)
Have you tried using email and/or a phone? These seem to work well for all other industries.
Re:Slack Connectivity Issues by wmccullough on Friday June 10, 2016 @02:42PM (#11878837)
Don't be a jerk... he has a tool that he and his team likes, and he was using it for a real task. No need to be a jerk about it. Yes a phone would work, was that what he was using at the time? No.
Re:Slack Connectivity Issues by abduhl on Friday June 10, 2016 @02:49PM (#11878901)
Well he might have been using the Slack iOS or Android app so I think it's a bit premature to assume that he wasn't using a phone at the time.
Re:Slack Connectivity Issues by buryat on Friday June 10, 2016 @02:05PM (#11878496)
discuss SPOFs more
Re:Slack Connectivity Issues by misingnoglic on Friday June 10, 2016 @01:45PM (#11878301)
Whooooosh
Re:Slack Connectivity Issues by chrismbarr on Friday June 10, 2016 @02:15PM (#11878589)
Not for me! I was literally in the middle of working on a Slack integration. At least now I know I wasn't crazy when it seemed like only half the requests I made generated a bot message.
Re:Slack Connectivity Issues by draw_down on Friday June 10, 2016 @01:56PM (#11878414)
Nope!
Re:Slack Connectivity Issues by surds on Friday June 10, 2016 @01:52PM (#11878367)
You know you have major problems when the status page itself fails to load.

Is there a meta-status page?

Re:Slack Connectivity Issues by mangeletti on Friday June 10, 2016 @01:56PM (#11878404)
I tried http://status.status.slack.com to see what was going on with their status page, but there was a server error. So, I tried http://status.status.status.slack.com to see what was going on with their status page status page, but there was a server error.
Re:Slack Connectivity Issues by rdoherty on Friday June 10, 2016 @02:10PM (#11878534)
Yup: https://metastatuspage.com/

Slack's status page is hosted by StatusPage, and it appears that the Slack client attempts to load the status page when it can't connect to Slack. So in effect, Slack is DDOS'ing their own status page.

Re:Slack Connectivity Issues by surds on Friday June 10, 2016 @02:16PM (#11878602)
I really did not expect anyone to actually come up with that. :)

They might want to do something about sending everyone over to that page.

Re:Slack Connectivity Issues by daw___ on Friday June 10, 2016 @01:22PM (#11878003)
Status page takes more than 30 seconds to load. Uhm.
Re:Slack Connectivity Issues by ben336 on Friday June 10, 2016 @01:44PM (#11878281)
Slack is generally very reliable. I wouldn't be surprised if this is the first "real world" load test its status page has ever had.
Re:Slack Connectivity Issues by rekoros on Friday June 10, 2016 @01:39PM (#11878232)
Re:Slack Connectivity Issues by HillRat on Friday June 10, 2016 @02:32PM (#11878744)
That's why you use Hipchat -- use it for a month and you'll learn to always be ready for it to go down.
Re:Slack Connectivity Issues by erickhill on Friday June 10, 2016 @02:06PM (#11878497)
New Eng Policy: Never push critical code to production on a Friday.
Re:Slack Connectivity Issues by balls187 on Friday June 10, 2016 @02:37PM (#11878788)
New?
Re:Slack Connectivity Issues by erickhill on Friday June 10, 2016 @02:39PM (#11878824)
@ Slack, perhaps.
Re:Slack Connectivity Issues by univalent on Friday June 10, 2016 @01:29PM (#11878110)
Ha! I opened HN after Slack went down. I guess I should get back to work.
Re:Slack Connectivity Issues by j15e on Friday June 10, 2016 @01:44PM (#11878293)
Too much friday beer?