7 ms·
Agreed, but with that said... IRC has serious issues, and dancing around them or pretending they're not there is not helping. I talk a bit about them here: htt
by scrollaway 11y ago
Agreed, but with that said... IRC has serious issues, and dancing around them or pretending they're not there is not helping. I talk a bit about them here:
https://plus.google.com/u/0/+JeromeLeclanche/posts/icC6gDToBsQ https://plus.google.com/u/0/+JeromeLeclanche/posts/icC6gDToB...
The reason Slack exists and can be so successful yet entirely proprietary is a symptom that IRC is not good enough and that has to be fixed. It is the manifestation of the papercuts we, IRC users, have been having for a long time now. (late edit: If you are interested in fixing this problem, email me, see my profile.)
There are very promising efforts on IRCv3 (http://ircv3.net/ http://ircv3.net/) ongoing. I hope they eventually go live to the bigger clients and networks so that we may actually have a good foss alternative to slack (and I don't mean something like Mattermost. Like SirCmpwn said some comments below, having one browser tab per project REALLY SUCKS when you contribute to a lot of projects. I'm in over 20 channels myself, and I do my best to keep that number low...).
- ChuckMcM 11y agoI really resonate with this position. IRC is open source and it has had problems FOR DECADES. IM programs from third parties add genuinely useful features which people clearly want. So rather than call for a general boycott of Slack (a negative approach) why not call to fix IRC?
- sdegutis 11y agoIRC is just a well-established and battle-tested server/client protocol. I'm eager for the day when a competing open source server/client protocol emerges and takes over. I imagine all it would take is a really good reference implementation server and client that everyone can just start using, right?
- ChuckMcM 11y agoI certainly think having an open source reference implementation for a 21st century (and by that I mean having features like Slack or Yammer or other popular closed source packages) implementation of a successor to IRC would be the minimum starting point.
- scrollaway 11y agoIRCv3, which I linked, is what you want. It builds atop the IRC protocol to extend it. It is backed by various servers and clients alike. http://ircv3.net/ http://ircv3.net/ They need help, go check them out.
- chei0aiV 11y agoThere is also RobustIRC which does away with netsplits: https://robustirc.net/ https://robustirc.net/
- e12e 11y agoFrom what I've been able to gather, the open project that is most like Slack, but also offers self-host, decentralization is Matrix: http://www.matrix.org/ There's also Zulip, which as far as I can gather, is battle-tested, but does not have a strong story for federated servers, nor a good out-of-box experience for really small servers: https://github.com/zulip/zulip Finnaly there's https://tox.chat https://tox.chat -- which doesn't have a lot of the things IRC/Slack has (it's focused around p2p chat) -- but extensions are planned, for eg. persistent group chat. Perhaps most excitingly "new" of the three, which predictably is both a good and a bad thing: https://wiki.tox.chat/users/faq#what_is_tox For those that "want Slack", but self-hosted, open/free software server -- I think Matrix is the most viable alternative -- if IRC is seen as not good enough. I've not included any XMPP servers, although eg. Prosody should be simple to set up and use -- because, apparently like IRC, it has too many problems for people to actually embrace out-of-the box XMPP for team chat. The fact that most big public services that host XMPP tend to favour anonymity probably has something to do with the fact that getting reliable server-side message logging and off-line messaging is still not as easy as one would expect, for any(?) of the big free XMMP daemons (or indeed support client side). [ed: Matrix also have some support through bots/plugins for IRC bridging: https://github.com/matrix-org/matrix-appservice-irc https://github.com/matrix-org/matrix-appservice-irc ]
- Arathorn 11y agoActually, bridging is actually a first class citizen in Matrix - it's why the project's called Matrix (as we want to go federate/matrix together all the existing silos out there). Current bridges include: * IRC (https://github.com/matrix-org/matrix-appservice-irc https://github.com/matrix-org/matrix-appservice-irc) * Slack (https://github.com/matrix-org/matrix-appservice-slack https://github.com/matrix-org/matrix-appservice-slack) * Verto (https://github.com/matrix-org/matrix-appservice-verto https://github.com/matrix-org/matrix-appservice-verto) (for talking VoIP with FreeSWITCHes) * Respoke (https://github.com/matrix-org/matrix-appservice-respoke https://github.com/matrix-org/matrix-appservice-respoke) (for talking VoIP with Asterisks) * Purple (https://github.com/matrix-org/node-purple/tree/master/appservice https://github.com/matrix-org/node-purple/tree/master/appser...) (for talking through to Skype, Facebook, XMPP, ICQ, AIM... and anything else that libpurple supports) ...and a whole bunch of 3rd party ones too like https://github.com/SkaveRat/xmpptrix https://github.com/SkaveRat/xmpptrix. Some of these are pretty beta, but they're all headed in the right direction. The IRC and Slack ones are the most mature. Glad to hear that you think we are on the right track! [Disclaimer; i work on Matrix]
- CamperBob2 11y agoIRC is just a well-established and battle-tested server/client protocol. Every time it loses another user to a proprietary platform, it loses another battle. Is that what "battle-tested" means?
- dman 11y agoIRC lacks a viable attached business model. In fact the act of writing robust services that empower users with data portability and privacy does not appear to have a sustainable model at all currently. I don't know if the current situation is a transitory phase or if this is how large systems will be built in perpetuity.
- sdegutis 11y agoBy "battle-tested" I meant it has lots of patches/updates to the protocol to protect against certain kinds of attacks. Any new protocol would have to go through the same "battle-testing" before it would be reliable enough.
- tptacek 11y agoIt's a well-established shitty protocol, largely designed in the early 1990s as the simplest thing that could possibly work for the workloads we had in the early 1990s. It's terribly limited (7 bit, small message sizes, virtually no useful metadata) and in the 98% use case, its "distributed" characteristics cause more problems than they solve. No competent person setting out to design a group communications protocol in 2015 could honestly say they'd use IRC as a starting point.
- kbuck 11y agoMostly correct, but one nit to pick: IRC is not 7-bit; you can actually transmit unicode messages on every IRC network I've ever seen. It's also not usually unicode-aware, though, so if you send a message too long, it might get truncated halfway through a codepoint. Many IRC networks prohibit non-ASCII channel names and nicknames to prevent impersonation (e.g. with zero-width spaces). The rest of what you've said is pretty much true.
- tptacek 11y agoIRC messages have CRLF message delimiters (and ASCII space field delimiters) and no quoting mechanism in the protocol. They're delivered over a long-lived synchronized TCP stream. Does it just happen that no 8-bit sequence people normally want to send on IRC ever manages to collide with 0D:0Ah? I haven't seen unicode messages on IRC channels, but I don't spend much time on IRC anymore, and so this is interesting new information for me --- but there's more to being 8-bit clean than simply supporting internationalized character sets.
- SamReidHughes 11y agoYeah, IRC is generally UTF-8 with some Windows-1252 mixed in.
- plorkyeran 11y agoShift-JIS is still the most common encoding for Japanese channels (but not being able to embed ODOA isn't an issue there either).
- ve55 11y agoFreenode sometimes does get a lot of abuse, which is a shame. Some networks definitely do have better anti-spam and anti-botnet functionality, but I don't think most users ever even notice this. Even on Freenode, most channels will go without problems like botnets or channel takeovers for most or all of their life. If you're running your own irc server, you'll probably never notice anything. If you do, it's as simple as adding a server password (or maybe even changing the default port among some other settings), and anything unwanted will likely be a thing of the past (assuming you don't have dedicated people attacking you). On your comment about IRC bots and services, networks don't see that as something that is up to them. If something requires a U:line or other network privileges, then it's up to the network staff to implement that, sure, but anything else is for their users to do. If IRC networks were for-profit, maybe you could expect them to have things like this and advertise how amazing all of their features are to potential clients. But IRC is nothing but a money sink for everyone involved, and there's therefore often little incentive for networks to implement and integrate a lot of bots and functionality that aren't integral to network operation. Apart from this, spam is a really hard problem if there are resourceful people dedicated to it. Email has existed for even longer than IRC, and despite absurd amounts of work into anti-spam systems and functionality with it, it's not too surprising when spam manages to finds its way into your mailbox. I still agree there's a lot of room for improvement, both at the protocol level and at the user level, though.
- munin 11y ago> it's as simple as adding a server password is there a way for me to, instead of using a server password, use something like OAuth so that I can grant access to the server based on my companies central login database? otherwise, every time someone leaves the project, we have to rotate the server password...
- scrollaway 11y agoYou can require SASL and build on that, but I don't believe there's any prebaked solution to that problem =/
- seba_dos1 11y ago
- lectrick 11y agoirccloud.com (disclaimer: I'm a subscriber) addresses a number of the deficiencies of standard IRC. A lot of the other deficiencies are a consequence of any decentralized, open resource, due to "tragedy of the commons" effects. Those will always require active admin participation to resolve.
- RyanZAG 11y agoWhat is wrong with Mattermost? I've never actually used it, but it seems like a better OSS slack competitor than irc. If it really is just the problem of 1 project per tab, surely fixing that minor issue is easier than a whole new IRC spec?
- scrollaway 11y agoIt's the other way around: Mattermost has a ridiculously small userbase, compared to IRC. IRCv3 is compatible with IRC2.1. It's a lot easier to extend the IRC spec than it is to write competing software.
- ywecur 11y agoSo use Rocket.chat or Mattermost