News for hackers. Stuff that matters.
Re:Why Slack is inappropriate for open source communications by exelius on Tuesday April 11, 2017 @11:20AM (#14088704)
So get a better IRC client? Really not hard to do things like syntax formatting and auto link follow (GUI versions of IRCII had plugins for this in the late 90s, so it's not like it's even a novel idea).
Re:Why Slack is inappropriate for open source communications by djsumdog on Tuesday April 11, 2017 @11:48AM (#14089137)
IRC as a protocol is very outdated. If I log in at home and forgot out log out at work, I need another username.

IRCv3 has a lot of enhancements that should move IRC out of the 1990s as far as a communication protocol, but there's not a whole lot of movement on it. I think FreeNode has some v3 support.

We don't have a lot of developers dedicating time to this. I'd love to myself, because it's something the OSS community needs, but it's also very difficult to contribute to projects when you're already doing 40 hours a week at a day job.

Today I feel like most of the OSS projects that are getting support are ones that are corporately supported:

http://penguindreams.org/blog/the-philosophy-of-open-source-...

Re:Why Slack is inappropriate for open source communications by kuschku on Tuesday April 11, 2017 @01:02PM (#14090020)
> but there's not a whole lot of movement on it. I think FreeNode has some v3 support.

That’s as wrong as you can get.

Networks with support, ranked by amount of supported features, are: InspIRCd Testnet, EsperNet, IRCCloud Teams, Snoonet, Rizon, IRCHighWay, freenode: http://ircv3.net/support/networks.html

Clients with support, ranked alphabetically, are:

Desktop: AdilIRC, BitchX, ChatZilla, Colloquy, Conspire, Hexchat, IceChat, Instantbird, Irssi, Konversation, KVIrc, LimeChat, mIRC, Mozilla Thunderbird, Quassel, Textual, WeeChat.

Web: IRCCLoud, Iris, Kiwi IRC, The Lounge, Mibbit, Quassel-Webserver

Mobile: AndChat, IRC for Android, AndroIRC, Colloquy, IRC7, IRCCloud, LimeChat, Palaver, Quasseldroid, YAAIC

Bouncers: Quassel, ZNC

Bots: Limnoria, Sopel, Moon Moon

http://ircv3.net/software/clients.html

And libraries are: cinch, Communi, irc-framework, Kitteh IRC Client Library, Net::Async::IRC, pydle, Rust irc, Warren, zIRC

That’s quite a whole lot of movement. That’s every project related to IRC

Re:Why Slack is inappropriate for open source communications by rsync on Tuesday April 11, 2017 @11:57PM (#14094631)
"If I log in at home and forgot out log out at work, I need another username."

You don't log into irc from your work or your home or your anything.

You run screen in your shell account and log into irc once and never log in again.

Christ - do we need a refresher course here in how to use the Internet for the incoming freshman class of 1994 ?

Re:Why Slack is inappropriate for open source communications by brain5ide on Thursday April 13, 2017 @06:30AM (#14105653)
Kids these days use tmux.
Re:Why Slack is inappropriate for open source communications by cortesoft on Tuesday April 11, 2017 @11:23AM (#14088757)
A better IRC client isn't going to provide chat history.
Re:Why Slack is inappropriate for open source communications by VLM on Tuesday April 11, 2017 @11:35AM (#14088911)
Just run your IRC client in screen/tmux like we've done for a quarter century.

The real advantage of slack isn't even client its stuff like massive logging for e-discovery and single sign on integration. Admittedly not terribly appealing for FOSS but once you use it at work...

Also integrations in general are smoother in slack than in IRC. Someone has already written the bot and its a click away to install and it generally works.

Re:Why Slack is inappropriate for open source communications by to3m on Tuesday April 11, 2017 @05:26PM (#14092614)
> Just run your IRC client in screen/tmux like we've done for a quarter century.

Wait... did you just tell me to go fuck myself?

Re:Why Slack is inappropriate for open source communications by aiiane on Tuesday April 11, 2017 @06:36PM (#14093146)
I believe they did, Bob.
Re:Why Slack is inappropriate for open source communications by kuschku on Tuesday April 11, 2017 @11:38AM (#14088967)
> The real advantage of slack isn't even client its stuff like massive logging for e-discovery and single sign on integration. Admittedly not terribly appealing for FOSS but once you use it at work...

Which can also be done with IRC clients.

This is a video of a search system I built for the Quassel IRC client: https://dl.kuschku.de/videos/2016-09-16_04-03-36.mp4

Quassel is a distributed system, so you have a bouncer and client which integrate tightly, with clients for Linux, Windows, Mac, Web, Android, iOS, which stores backlog in a database.

This search system is a very simple one, and simply uses postgres’ fulltext word vector search.

Re:Why Slack is inappropriate for open source communications by VLM on Tuesday April 11, 2017 @11:54AM (#14089237)
Encapsulates this era as the battleground of silo'd "as a service" vs "can be done"

For example I can have jenkins email build fails to slack in, oh, probably less than two minutes, I've done it before. From memory I make a custom email addrs in slack and tell slack which channel to feed it into, and then add that address to my jenkins that already sent buildSpam.

In IRC I could do it... google implies there's a ZenIRCBot project on github and probably many others. Probably there are bots and tools that google didn't immediately find.

Its not rocket surgery to use fetchmail and some kind of Perl IRC library to simply POP everything out of a mailbox into a directory /tmp/wtf and probably about 3 lines of perl to read all the files in /tmp/wtf, connect to irc on some channel, output what it found, and if successful delete the emails from /tmp/wtf. Then put fetchmail and the 3 line perl script into cron and away we go.

Looks like Zapier is kinda in between "I could do it" and "AAS"

Re:Why Slack is inappropriate for open source communications by jasonjayr on Tuesday April 11, 2017 @01:30PM (#14090365)
Jenkins has a IRC plugin, already in the stock distribution. Jenkins bot idles in channel, and logs all sorts of failures or successes, or whatever. With the irc server + channels setup, this also takes less than 2 minutes.
Re:Why Slack is inappropriate for open source communications by anonymoushn on Tuesday April 11, 2017 @03:10PM (#14091384)
You can have Jenkins send IRC messages using a single invocation of netcat. This should take less than two minutes.
Re:Why Slack is inappropriate for open source communications by NateDad on Tuesday April 11, 2017 @12:18PM (#14089562)
"log in to slack" vs. "deploy 3 services in the cloud by yourself and force everyone to use a specific irc client (good luck)"

There's a reason people like slack so much. It does a ton of stuff out of the box with no headaches. Nobody wants to maintain all that stuff.

Re:Why Slack is inappropriate for open source communications by kuschku on Tuesday April 11, 2017 @12:51PM (#14089910)
> There's a reason people like slack so much. It does a ton of stuff out of the box with no headaches. Nobody wants to maintain all that stuff.

So instead of paying someone to maintain it, you pay someone to maintain it who keeps all your data from you and prevents you from accessing it, and who admits he’ll read all your stuff.

How is that better again?

That said, IRCCloud already does it for free, in the cloud, just works™, and the Quassel people are also working on improving ease of use and deployment.

Re:Why Slack is inappropriate for open source communications by qudat on Tuesday April 11, 2017 @01:26PM (#14090297)
> So instead of paying someone to maintain it, you pay someone to maintain it who keeps all your data from you and prevents you from accessing it, and who admits he’ll read all your stuff.

You aren't paying "someone" you're paying an entire company that is dedicated to making the application highly available, with all the bells and whistles, with zero hassle.

Really, if you think IRC is so similar to Slack, then why are so many companies, organizations flocking to it? There has to be a reason.

Re:Why Slack is inappropriate for open source communications by kuschku on Tuesday April 11, 2017 @01:35PM (#14090417)
> Really, if you think IRC is so similar to Slack, then why are so many companies, organizations flocking to it? There has to be a reason.

If HN has higher discussion quality than reddit, why are not all devs on HN instead? If Linux is better for servers, why are people still starting projects on Windows? etc...

The power of marketing, directly or word-of-mouth, is important. And a decentral community can never do as perfect marketing as a company can do.

There are IRC clients and apps, and third party integrations as powerful as Slack, and as easy to use. But you have to find them, install them separately – there’s no single combined effort to market a single "just works" solution, yet ;)

Re:Why Slack is inappropriate for open source communications by NateDad on Tuesday April 11, 2017 @02:10PM (#14090807)
How many people maintain their own email servers vs. use gmail?

Slack doesn't prevent you from accessing your data, in fact they explicitly built exporting features.

We're talking about open source, so reading your stuff shouldn't be a problem. For proprietary, maybe, but even then, reading someone's private slack info would be highly damaging to their brand, and to what benefit?

Re:Why Slack is inappropriate for open source communications by VLM on Tuesday April 11, 2017 @05:18PM (#14092537)
"prevents you from accessing it"

with respect to something like e-discovery its all a matter of perspective. If this were true, which it isn't, I wouldn't necessarily mind, as the financial worth of combined ancient IRC logs is unquestionably a net negative value.

Re:Why Slack is inappropriate for open source communications by s73ver on Tuesday April 11, 2017 @05:11PM (#14092493)
You can get upset over this and argue with people, but that's not going to make anyone choose IRC over Slack.
Re:Why Slack is inappropriate for open source communications by eric_h on Tuesday April 11, 2017 @06:24PM (#14093080)
Slack, Hipchat, Campfire, etc. are all just IRC for normal people. There is without a doubt a barrier to entry to IRC that actually requires a bit of understanding of how the protocol works. "I'm in #this-channel-you-told-me-about, but no one else is in here, wtf?". "Oh, you're on the wrong network - it's EFNet, not Freenode".

There is no such barrier for the current set of chat apps. Download > Login with google, start chatting with the person who invited you. Search history? File sharing? No need to remember anything about dcc/xdcc, no need to manage servers running bots, no need to manage anything, really; it's all taken care of by the nerds that run the service.

I think one might actually be able to build a business by building a Slack that runs on top of IRC, and releasing client apps that actually significantly reduce the flexibility that a standard IRC client gives you. If you can get the on boarding flow to invite -> download -> log in -> start chatting with the people you want to chat with, you could crush slack (assuming you had the marketing budget to compete with theirs).

I think, however, that IRC will remain in some ways as a small haven from eternal September (haha, yeah, I know). The barrier to entry is a feature, not a bug.

Re:Why Slack is inappropriate for open source communications by kuschku on Tuesday April 11, 2017 @07:27PM (#14093425)
> I think one might actually be able to build a business by building a Slack that runs on top of IRC, and releasing client apps that actually significantly reduce the flexibility that a standard IRC client gives you. If you can get the on boarding flow to invite -> download -> log in -> start chatting with the people you want to chat with, you could crush slack (assuming you had the marketing budget to compete with theirs).

Someone did, it's called IRCCloud.

That's the entire problem I've been talking about above: Anything you can imagine regarding IRC already exists. The only issue is that you don't know about it yet, and have to find it. And without marketing, or any lists of what is good and not, this is hard.

Re:Why Slack is inappropriate for open source communications by s73ver on Wednesday April 12, 2017 @12:41PM (#14099351)
Then start actual marketing. And make sure that I can switch from Slack to your product without any hangups, and have exactly the same feature parity, especially for non-technical users.
Re:Why Slack is inappropriate for open source communications by djsumdog on Tuesday April 11, 2017 @11:51AM (#14089183)
This is the first I've heard of an IRC bouncer. That's a great idea. It still seems like it's and extra step you have to add though, when really it'd be nice to see some work on IRCv3 so you could have multiple clients connect to one IRC server with the same username and sync without the need of a proxy.
Re:Why Slack is inappropriate for open source communications by Filligree on Tuesday April 11, 2017 @12:19PM (#14089581)
The current answer to that is basically "Use IRCCloud", and that's what I link people who don't already know IRC to.

It's a web/android/iphone client only, but it's IRC. The moment someone grows tired of the client, they can get their own.

Re:Why Slack is inappropriate for open source communications by eric_h on Tuesday April 11, 2017 @06:34PM (#14093139)
When I was a wee lad I was always envious of people on IRC who had these things called "shell accounts" that let them stay connected to IRC 24/7.

They could schedule downloads to their remote boxes and wouldn't have to tie up the home phone line for three days downloading the latest warez from that guy who had an ISDN line and let 10 people(!) simultaneously download from his bot at a screaming 5k/s.

Now I can have all those things (including the equivalent of 1000 ISDNs), and I don't really use IRC anymore, young me would be so jealous.

Re:Why Slack is inappropriate for open source communications by compuguy on Wednesday April 12, 2017 @11:04AM (#14098336)
Or you can use a web based interface like the lounge.
Re:Why Slack is inappropriate for open source communications by philh on Tuesday April 11, 2017 @11:45AM (#14089101)
A few people have replied, saying how to get chat history with IRC, but as far as I can tell, none of them work like Slack. With Slack, you can see history from before the first time you connect. It looks like none of the IRC solutions enable that; the IRC protocol doesn't make it possible, without the server (or a channel member) keeping logs.

(I haven't used either very much, so please correct me if I'm wrong.)

Re:Why Slack is inappropriate for open source communications by scrollaway on Tuesday April 11, 2017 @12:19PM (#14089568)
IRCCloud can, they're a client too :) I highly recommend them if you are serious about IRC.

But yes you're right, nothing in the IRC protocol for it. There is something in IRCv3 to provide chat history but I don't know if it's even in the current version of the spec.

https://www.irccloud.com/

Re:Why Slack is inappropriate for open source communications by philh on Tuesday April 11, 2017 @01:10PM (#14090107)
How does it do this? When you use IRCCloud to go to a channel for the first time, where does IRCCloud get the history for that channel from?

(You say "they're a client too" - I confess, I don't know what they are apart from a client.)

Re:Why Slack is inappropriate for open source communications by scrollaway on Tuesday April 11, 2017 @01:12PM (#14090136)
Like I was saying, IRCv3 has support for replaying the channel's history, as long as it's stored serverside. But I don't know if anything actually implements it, even IRCCloud which is v3-compatible.

At the moment if you join a channel you can't read its backlog, no. They could implement it though if they used logs from their users... kinda wish they would. But hey.

Re:Why Slack is inappropriate for open source communications by philh on Tuesday April 11, 2017 @01:35PM (#14090420)
> At the moment if you join a channel you can't read its backlog, no.

Then I'm not entirely sure what you were referring to, when you said "IRCCloud can". Backlog from before you joined the channel is the specific feature that I was saying couldn't be done.

It's interesting to know that IRCv3 does have that support, so I was wrong about it not being possible. But if nothing implements it, it's not very helpful.

Re:Why Slack is inappropriate for open source communications by baldfat on Tuesday April 11, 2017 @02:00PM (#14090704)
We are talking Open Source Project Communication not small group communication.

IRC and FreeNode channels have been the standard for communication and not for archival purposes. I use an IRC bouncer with my home server and I never look back through the thousands of communications except to see a reply to my question.

Why does a Open Source Community channel need archived communication unless it is just a few developers only chat?

Re:Why Slack is inappropriate for open source communications by kuschku on Tuesday April 11, 2017 @11:36AM (#14088932)
Yes it is. This is exactly what Quassel and IRCCloud do.
Re:Why Slack is inappropriate for open source communications by rsync on Tuesday April 11, 2017 @11:59PM (#14094645)
"A better IRC client isn't going to provide chat history."

That's not even wrong.

Re:Why Slack is inappropriate for open source communications by jstanley on Tuesday April 11, 2017 @11:35AM (#14088901)
An IRC bouncer (e.g. znc) can do this, but it's far from seamless.
Re:Why Slack is inappropriate for open source communications by always_good on Tuesday April 11, 2017 @05:58PM (#14092888)
The problem is that you might be running a nicer IRC setup, but almost nobody else is. Doesn't do you much good if everyone else logs off the second they close their laptop lid, or can't scroll back up to see what you just said because they had to relaunch their client.

Chatting is interesting because of other people. That's why I'm chatting.

In Slack, I can ping people that are offline. And all they have to do is open Slack again or reconnect to the internet and they get notified. I don't need to count on them being an IRC veteran.

All these people pointing out ways to enhance your personal IRC experience are missing the point.

Oh yeah, and I can post code in Slack.

Re:Why Slack is inappropriate for open source communications by s73ver on Tuesday April 11, 2017 @12:17PM (#14089535)
Not everyone is going to use the same client.