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