News for hackers. Stuff that matters.
Re:Why I Live in IRC (2015) by dijit on Thursday August 11, 2016 @07:27AM (#12267343)
+1 for IRC, the interface is clunky and the protocol hasn't aged particularly well (especially for mobile devices who may not be able to hold a connection forever). But the social aspect of easily accessible chatrooms and the plethora of clients/tools surrounding IRC is really second to none.

You can put a pretty skin on it (slack,discord) but at the end of the day it's going to take years to bring up the level of tooling and at the end you wind up in a closed loop on someone elses platform.

FWIW; I dream of electric sheep so I'm completely biased. I run an IRC network if anyone is interested in joining.

host: irc.darkscience.net/6697 (SSL required)

chan: #darkscience

Re:Why I Live in IRC (2015) by lmm on Thursday August 11, 2016 @08:11AM (#12267538)
IRC is great for a world where people have one account on one computer that's permanently switched on, but it inherently fails to handle use from multiple devices. All "solutions" to this end up involving running your own server (or, more likely, having someone else do it) and talking to that via a probably-proprietary (or at least nonstandard) protocol at which point you no longer have the benefit you're talking about. (That protocol is often layered over an open protocol, but commands-over-ssh is very hard to interoperate with if not standardized)

Good UI is not just "pretty", it's also about having commands be discoverable. Traditional IRC clients are terrible in this regard.

There's no reason the platform has to be closed - I'm friends with the people working on http://matrix.org/ (though not involved in it myself) and hope they succeed.

Re:Why I Live in IRC (2015) by scrollaway on Thursday August 11, 2016 @08:35AM (#12267684)
I recommend IRCCloud.com to people.

I'm a huge fan of IRC but it's true the IRC protocol has many issues (I talked about them before on HN; can't find the link now). IRCCloud may be (slightly) proprietary but at least it still only talks to IRC, and it's a good alternative to Slack&Friends (which are 100% proprietary) and webchat (which have the same issues as desktop clients and are generally atrociously ugly).

Free IRCCloud accounts stay online 2 hours when shut off. I pay for mine, which stays online forever. It's a fairly similar experience to slack except I can still use the same open protocol as everyone else.

Matrix is extremely promising but IMO not there yet.

Re:Why I Live in IRC (2015) by lorenzhs on Thursday August 11, 2016 @08:41AM (#12267722)
I run WeeChat in a tmux and connect to it with Glowing Bear. It's a similar experience, and it's all free software. It also leverages the whole power of WeeChat in a nice interface (triggers, scripts, etc), so it can do some nice tricks that IRCcloud can't.

Oh and there's also a Matrix script for WeeChat, so you can use matrix from WeeChat (and thus Glowing Bear)!

Re:Why I Live in IRC (2015) by spinningarrow on Thursday August 11, 2016 @11:48AM (#12269201)
Wow I just tried this setup (tried using WeeChat directly from the terminal a while back but somehow it didn't feel comfortable) and it's pretty darn good. Thanks!
Re:Why I Live in IRC (2015) by scrollaway on Thursday August 11, 2016 @08:43AM (#12267737)
Got some examples? I never tried WeeChat. I used to use Quassel (I liked the client a lot), but after my server died I figured it wasn't worth the trouble of maintaining it.
Re:Why I Live in IRC (2015) by lorenzhs on Thursday August 11, 2016 @08:55AM (#12267807)
Examples for what? There are some screenshots of Glowing Bear on the GitHub page (https://github.com/glowing-bear/glowing-bear) and in a blog post I once wrote (https://4z2.de/2014/04/10/glowing-bear, probably outdated). I use it with a sans-serif font on the Desktop, too. The UI is quite hackable, you can add custom CSS rules to override things to your liking in the settings (simply changing the font doesn't require that, though).

Some useful scripts include colorize_nicks.py (colourises nicks in messages, to make them stand out over the text) and grep.py (easily and efficiently search logs). Matrix.lua (https://github.com/torhve/weechat-matrix-protocol-script) allows you to use the Matrix protocol with WeeChat, and by extension Glowing Bear.

Trigger-wise, I have triggers that remove colour from status messages (most of them are just noise) or replace (lenny) with ( ͡° ͜ʖ ͡°) when I send a message, mostly because I can ;)

Getting push notifications requires a bit of setup, but there are scripts for Pushbullet/Pushover/..., or irssi-notifier (which also works with WeeChat) to do that. It's a bit complicated because we don't run any servers (Glowing Bear is just a bunch of static files, everything happens in your browser or your WeeChat), so we can't provide push notifications out of the box. Disclosure: I'm one of the Glowing Bear devs, so I may be biased :)

Re:Why I Live in IRC (2015) by lmm on Thursday August 11, 2016 @09:44AM (#12268130)
Slack has an IRC gateway, so I think it's about as open as IRCCloud in practice. And the free version of IRCCloud has gradually got worse and worse - I think you're not allowed to connect to external servers any more, only to their one.
Re:Why I Live in IRC (2015) by scrollaway on Thursday August 11, 2016 @12:02PM (#12269334)
> I think you're not allowed to connect to external servers any more, only to their one.

What are you talking about?

https://www.irccloud.com/pricing

Re:Why I Live in IRC (2015) by lmm on Friday August 12, 2016 @07:34AM (#12274741)
It certainly was more restricted than 2 non-irccloud networks at one point. More generally you can't assume the free version will continue to have the same functionality, because they've reduced it before and could easily do so again.
Re:Why I Live in IRC (2015) by hueving on Thursday August 11, 2016 @09:01PM (#12272843)
Can slack connect to arbitrary irc networks? If not, then it's not as close to open in practice.
Re:Why I Live in IRC (2015) by voltagex_ on Thursday August 11, 2016 @09:15AM (#12267919)
How many times do you get nickserv alerts from IRCCloud (indicating that "your" client has reconnected). I use IRC enough that it's worth the money (I also support their work on IRCv3), but this is getting silly.
Re:Why I Live in IRC (2015) by scrollaway on Thursday August 11, 2016 @09:34AM (#12268062)
Seldom to never? I've seen a couple messages from chanserv when IRCCloud servers have problem, but no annoyance. Keep in mind though I pay for a premium account and I only connect to freenode.
Re:Why I Live in IRC (2015) by voltagex_ on Monday August 15, 2016 @01:18AM (#12288803)
I'm also on a premium account and get disconnected and reconnected at least once a week from OFTC - I thought I also got disconnected from Freenode, but now I'm not sure.
Re:Why I Live in IRC (2015) by catdog on Thursday August 11, 2016 @09:34AM (#12268063)
IRC originates from a time where nobody was thinking about multiple devices, or e.g. not encoding in ASCII. Speaking of nonstandard: There seems to be no canonical specification of IRC itself. Nevertheless it's really not that bad in practice if you use a bouncer or something similar like Quassel.

> There's no reason the platform has to be closed - I'm friends with the people working on http://matrix.org/ (though not involved in it myself) and hope they succeed.

There is also XMPP (and has been for years) which does not suffer from many of IRCs shortcomings.

Re:Why I Live in IRC (2015) by stonogo on Thursday August 11, 2016 @11:25AM (#12268973)
> There seems to be no canonical specification of IRC itself.

Is this a joke? Did you think all this stuff just accidentally worked? I'm not sure how seriously to take your entire message because of this bizarre idea.

https://tools.ietf.org/html/rfc1459

https://tools.ietf.org/html/rfc2810

https://tools.ietf.org/html/rfc2811

https://tools.ietf.org/html/rfc2812

https://tools.ietf.org/html/rfc2813

Re:Why I Live in IRC (2015) by catdog on Thursday August 11, 2016 @01:42PM (#12270244)
Sure it's standardized enough to generally work but to my knowledge only RFC1459 is widely seen as authoritative. The protocol evolved quite a bit over the years but a lot of the extensions covered (and maybe not covered) by those later RFCs are handled to some extent differently between IRCd implementations. There at least seems to be some effort [1] now to fix some of IRCs issues and bring the whole mess more in line again. As IRC is still widely used and probably there to stay I hope it will work out.

[1] http://ircv3.net

Re:Why I Live in IRC (2015) by zeveb on Thursday August 11, 2016 @10:19AM (#12268401)
> There is also XMPP (and has been for years) which does not suffer from many of IRCs shortcomings.

In return, it suffers from its own shortcomings, mainly XML and second-system effect (leading to too much complexity & too many options).

What we really need, I think, is exactly what Slack, Mattermost &c. give: persistent, multi-device, multi-group chat. I think that solving that problem in a nice, small, secure protocol (one that doesn't imply a browser-first way of doing things — and indeed, 'secure' probably prevents using a browser in the first place) is more than enough of a problem for someone to solve.

Heck, even just the multi-device shared-identity problem is surprisingly difficult.

Re:Why I Live in IRC (2015) by lmm on Thursday August 11, 2016 @09:41AM (#12268104)
> not encoding in ASCII

IIRC the original standard specifies a particular 8-bit character set (not ASCII), though the broader point stands.

> There is also XMPP (and has been for years) which does not suffer from many of IRCs shortcomings.

XMPP is useless for multiple devices: there's no way to receive messages on both (some servers will deliberately violate the spec here because the spec is stupid), and the federated history spec has been under development for about a decade now. Groupchats don't work properly with federation and have terrible UX in every client I've tried. Everyone assumes XMPP must be good because it's open-source (which is usually a pretty good heuristic) but I've come to the conclusion it's actually a really bad standard.

Re:Why I Live in IRC (2015) by catdog on Thursday August 11, 2016 @10:47AM (#12268628)
> XMPP is useless for multiple devices: there's no way to receive messages on both (some servers will deliberately violate the spec here because the spec is stupid)

XEP-0280: Message Carbons and there was that priority thing before. It somehow worked in the past and now it's definitely solved.

> Groupchats don't work properly with federation

The only annoying problem i can think of is when the server hosting the MUC restarts clients seemingly don't notice that they have to rejoin.

> and have terrible UX in every client I've tried.

Maybe you tried terrible clients? Unfortunately are few now which aren't terribly behind regarding protocol support.

> and the federated history spec has been under development for about a decade now.

I think thats the real problem. "Nobody" implements newer XEPs, especially if they are not finalized yet but how should they finalize if nobody puts them to trial? Everybody seems to have settled in screaming out what does not work so well but instead of helping to fix it they halfway reinvent the wheel or switch to centralized proprietary solutions which may have nicer looking clients but often don't even try to solve harder problems like multi client support. I didn't have a look at Matrix yet, maybe it's worth it but there is always the danger of creating yet another standard [1] (which may not even be as perfect as originally thought in the end either).

> but I've come to the conclusion it's actually a really bad standard. But is it really that bad (especially at the basic fundaments) to justify something completely new? XMPP at least provides a lot of ability to evolve without breaking everything that was.

[1] https://xkcd.com/927/

Re:Why I Live in IRC (2015) by Arathorn on Thursday August 11, 2016 @05:32PM (#12271711)
hopefully Matrix avoids falling into the cliché of xkcd 927 by focusing on defragmenting the existing silos - building a metanetwork between IRC, Slack, XMPP, etc etc. So rather than saying "hey everyone, throw away your current stuff", we say "hey everyone, build a bridge into Matrix - it's fun and easy (100 LOC for the slack bridge: https://github.com/matrix-org/matrix-appservice-bridge/blob/....

If you want to use Matrix natively via weechat or whatever then so much the better, but the intention is to be useful as way more than just another msging protocol. It's meant to more be a big open decentralised database for conversations and other realtime data - more in common with IPFS or even the Web itself.

[disclaimer: I work on Matrix]

[p.s: can someone work out how to send Matrix $5 every time someone quotes xkcd 927 at us...?]

Re:Why I Live in IRC (2015) by corobo on Friday August 12, 2016 @05:44AM (#12274319)
> p.s: can someone work out how to send Matrix $5 every time someone quotes xkcd 927 at us...?

I'm sure when Matrix is the go-to chat protocol you'll get more than that. Until then it is sorta fitting..

Re:Why I Live in IRC (2015) by Arathorn on Friday August 12, 2016 @10:16AM (#12275798)
sigh no, the point is that it doesn't fit because Matrix does not try to be "yet another chat protocol that fits everyone's use cases". It aspires to be a bridging protocol that links other chat protocols together rather than replacing them.
Re:Why I Live in IRC (2015) by corobo on Friday August 12, 2016 @10:26AM (#12275897)
I'll be honest I've not scoured your entire site but I'm just not seeing that description (and didn't at all earlier, I've since looked further).

From what I gathered you want to be the email of chat protocols. The only mention of wanting to bridge other protocols is a quick mention half way down your FAQ page.

Re:Why I Live in IRC (2015) by Arathorn on Friday August 12, 2016 @05:26PM (#12278922)
Guess this reflects that the FAQ is stale and needs some love. The second item there is:

> What is Matrix’s Mission? Matrix’s initial goal is to fix the problem of fragmented IP communications: letting users message and call each other without having to care what app the other user is on - making it as easy as sending an email.

The whole point is that the defragmentation is done by bridges. The analogy to email is not in terms of having One True Protocol that everyone uses like SMTP, but that it's possible for a user on app A to communicate with another user without caring what app they use.

Thanks for highlighting that we need to fix the FAQ!

Re:Why I Live in IRC (2015) by corobo on Friday August 12, 2016 @06:42PM (#12279303)
Fair point, I think I read "without having to care what app" as meaning a Matrix-based app, whether official or not.
Re:Why I Live in IRC (2015) by dijit on Thursday August 11, 2016 @08:14AM (#12267553)
I agree about the discoverability of commands, but that's inherently a client issue and not one against IRC itself.

You're right that there's not much in the way of offline messaging without running something like znc (which you can run at home on anything), but there is also Memoserv on most networks- if you absolutely have to notify someone.

Or, there's email.

Re:Why I Live in IRC (2015) by Vendan on Thursday August 11, 2016 @10:01AM (#12268262)
I use znc to fix the multiple devices issue. Admittedly, it does involve running a server, but I've got that handled. As far as the protocol, it's just irc... I connect to znc via irc, and it connects to freenode or wherever. No extra protocols.
Re:Why I Live in IRC (2015) by lmm on Sunday August 14, 2016 @02:07PM (#12286603)
IRC is a very ill-suited protocol for device <-> znc though. E.g. IIRC it sends you a constant 200 lines of history (whether you've read that history already or not), because that's all it can do.
Re:Why I Live in IRC (2015) by kqr on Thursday August 11, 2016 @08:25AM (#12267620)
> the interface is clunky

The reason I prefer IRC after all these years is that the interfaces available have not been beaten by any other product so far. Sure, IRC has an unfair advantage in being 20 years old so there's 20 years of development behind the current interfaces, but still.

Yes, I have a set of particular requirements which aren't in line with what a "regular customer" would want in their communication app, but so? IRC gives me the freedom to get my interface while someone else can get a different interface.

Re:Why I Live in IRC (2015) by josteink on Thursday August 11, 2016 @07:42AM (#12267386)
> +1 for IRC, the interface is clunky and the protocol hasn't aged particularly well (especially for mobile devices who may not be able to hold a connection forever).

Weechat and it's Android relay client is for you.

Re:Why I Live in IRC (2015) by lorenzhs on Thursday August 11, 2016 @08:30AM (#12267650)
Or Glowing Bear, which also works great on iOS and the desktop (I'm one of the maintainers)
Re:Why I Live in IRC (2015) by aaronpk on Thursday August 11, 2016 @08:51AM (#12267781)
Glowing Bear is great! I've been using it since a few months after writing this.
Re:Why I Live in IRC (2015) by exadeci on Thursday August 11, 2016 @10:10PM (#12273033)
https://www.irccloud.com/ does a good job at being a painless client and it adds a slack/discord coating with features like inline images/videos.

I've been using the free version for a while and I'm pretty happy with it.