3 ms·
I 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 cl
by ChuckMcM 11y ago
I 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]