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.
Oh and there's also a Matrix script for WeeChat, so you can use matrix from WeeChat (and thus Glowing Bear)!
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 :)
What are you talking about?
> 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.
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
[1] http://ircv3.net
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.
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.
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.
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...?]
I'm sure when Matrix is the go-to chat protocol you'll get more than that. Until then it is sorta fitting..
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.
> 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!
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.
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.