It seems that 2015 will likely be partially remembered as the year IRC zealots raged against those using Slack instead of the old reliable, and still growing daily, IRC chat. And it is turning out to be as lively as the “tabs versus spaces” debate that never seems to end.
Of course this means I am only left with one solution…it’s time for me to create a blog post to commemorate this seemingly HUGE issue, and make my thoughts known.
The answer is, I use both depending on circumstances.
For those who aren’t aware (shame on you), IRC (internet relay chat) allows the creation of “chatrooms” where folks can get together to share common interests. And thanks to many individuals and companies providing servers for the cause, it is free. Freenode has been around for more than 15 years.
IRC for all of it’s greatness is also fairly bland, and is pretty much just chat, and while many people use it there is still not much to make it “sticky”. For some this may be perfect because there is less “noise”, but for others there is not enough to warrant their attention.
Lately there is a new kid on the block called Slack.
Slack had a bumpy beginning as a failed startup. The app was likely doomed to be discontinued and never see the light of day as a private resource for companies, because nobody was using it. So as a last ditch effort the company decided to open it to the public, where it boomed to become a regular part of many projects by companies and open source projects and/or communities.
Not only does Slack perform the same activities as IRC, but it also includes the ability to integrate information from outside sources. For instance, via connectors you can pull in RSS feeds from pretty much anything that provides RSS, Tweets and Retweets by certain accounts, Facebook content, IRC content, Github comments and notices, news and announcements from virtually anywhere, and much more. In short, you can create a one stop portal with tons of information relevant to your “Team” which makes Slack a place where everyone can get together and share at a much higher degree than with traditional IRC.
So, what is the problem you may ask? The answer would be that Slack is not entirely free (though there is a free level), and if Slack were to change their pricing model or if they closed entirely all is lost. Communities, projects, and all these things created around this great platform disappears. There are no options to kick up your own server retaining the content, or any other alternative to carry on without the Slack company.
Those who are speaking up against using Slack for things like User Groups and OSS projects are voicing a valid concern because history and entire communities could be lost forever if Slack were used and evil things happen. This is a valid concern, and I was one of those people, until recently, which I will share in a moment.
However, on the other side of the issue is this: Though IRC is still growing and is not really being hurt by Slack, a vast majority of people simply don’t want to use it. Not because of anything malicious, but because a well set up Slack Team can become such a wonderful thing.
I organize the South Florida PHP User Group (SoFloPHP), and a long time ago I created the #soflophp chatroom on IRC Freenode. Then I promoted it heavily to the group of 800 members over and over and over again, and even posted it on the group website. Yet, at best we only had 2 or 3 people in the chat at any one time…BORING!
Recently a member, and now co-organizer, of the group asked if we could create a Slack team for the SoFloPHP user group. I was initially against it and voiced my concern as well as pointing out that there was already an IRC chatroom for the group. But the member was persistent, so I reluctantly agreed. And WOW!
Now to be fair, the Slack Team likely would have been a failure also because in Slack you need to invite every person into the team. There is not a way for folks to just join in, as with IRC. However, there is a handy app (Slackin) you can post on a server that allows people to enter their email address for an auto invite to the Team. We simply posted the app on a free Heroku instance and were off and running.
The problem of getting people into the Slack Team was handled, but how to make it better than IRC and ensure it was used? I then created a couple of Channels within the Team. One was for “Social” which I then created a couple of connectors to some relevant Twitter accounts. This kept fresh content, announcements, and relevant updates automatically flowing in to keep everyone informed and encourage discussion. Then I created a “Jobs” Channel to do the same, but with posts from our user group jobs board at http://jobs.soflophp.org. And I also created a feed to the “Random” Channel from the Reddit /r/php hot board to infuse news and updates relevant to PHP. (Note: While Reddit can create an overload of posts, it does seem to promote chat around some of the posts in the General Channel.)
Now that we are using Slack as the user group communication portal (in addition to Meetup.com for the group management) we’ve noticed a much higher level of activity in the group. There are 50’ish members after only a couple of months, and the usage is growing instead of staying stagnant as the IRC did for a few years.
So the bottom line for me: Without paid services like Meetup.com our user group would not be what it is, and it seems that Slack has enabled us to become more active. I will continue using both, until they no longer work. Because the bottom line is that the group was created to serve the community, and Slack seems to do that for now.
4 responses to “The 2015 Slack vs IRC debate rages on”
IRC is not free, IRC is a protocol. It can’t be taken away from you any more than email can. Slack is a product. It CAN be taken away from you. I’m not saying it will, but we have a lot of example in recent history where groups built on a product and it WAS taken away from them. (Ning.com, the Twitter API, are two that come to mind)
The thing that everyone seems to ignore is that with IRC, you connect to a server group and you have access to thousands of channels (at least on freenode) with slack, you have to register for each of them, individually. Also, when someone is asking for help in an irc channel, you can redirect them to the appropriate channel for help. (e.g. the MySQL channel, Nginx, or Apache)
I’m happy it is working for SoFlo, but it seems to me that there nothing you have described here could not have been done in irc and a little creative use of Phergie. That’s the thing that makes me sad. Instead of filling in the gaps in what we’ve got, people seem to be content to move their open source community into a walled garden…again. 🙂
Just a small note about slackin:
Slack really don’t like you using automated inviters. I’m part of a community of around 2,000. We had one. We were told to get rid of it, or we’d be gone. (I know of another community this happened to)
We’re currently managing invites manually, by having a web in hook, which posts emails to our moderator channel.
(Another option is hipchat, which has a link you can pass out to get people in)
I haven’t seen a problem with several of the slackin/typeform frontends I’ve setup to automate public slack signups. However we haven’t reached 2,000 users in those. I just built something for non-techs (the github page for slackin scares some people away) called slackvite –> https://slackvite.com
Rather use Discord then, easier to implement commands, auto invite and its bot friendly