I've switched to Matrix[1] with auto-bridging to freenode. It automatically syncs new notifications across all devices, that way when I read something on the desktop, the notifications on my phone are gone. It has a slew of other cool features, too.
I use vector.im for desktop and matrix console for android.
> Fully distributed persistent chatrooms with no single points of control or failure
but looking at vector.im, channels seem to be based at specific servers, like "#matrix:matrix.org". How does that work? Also, what's the plan to deal with banning spammers and so forth if there's no central control?
The API intro page[1] is a good start. Basically, a client authenticates with their homeserver. Multiple homeservers can "access" a single room. There is a server-server API for synchronization. I don't know how this maps onto vector.im / matrix.org
I spent 20 minutes with this the other day and could not get connected to anything on Freenode. The user interface for this is just about as friendly as IRC. Any pointers?
I was just playing with Matrix too (Vector.im is a decent web interface for it), and managed to connect to Freenode by using #freenode_#channelname:matrix.org as the room name. Hope that helps!
I've used this for months. It stops working for no reason. I think it eats up too much memory and keeps increasing memory usage. I don't know, but I know it crashes after a few days.
I've seen some projects now even have "Deploy to Heroku" buttons, which is fantastic. I wish Digital Ocean had something similar. Looks like you should be able to run this on a cheap $5 droplet?
I did in fact run this on a cheap $5 droplet, along with an apache2 server. Worked fine except it crashes about once a week, I think due to memory usage. I switched to weechat in a tmux session
I've been using it for over 6 months now with multiple users connected to multiple servers with quite a few active channels. I've had it crash from memory leaks (on a 1GB Linode VPS) once in all that time. Maybe PonyChat is just waaaay more active than the channels I'm in? At the moment, HTOP reports it using about 17% of my memory.
Sure. It would also be a pretty shitty server if it crashed because nobody had the forethought to realize history uses memory. 4GB of memory will always be enough....
As a (small) network owner, this is not yet ready to use on the network web site, because it does not support WEBIRC and so all web clients appear to come from the same IP. There's an issue open on GitHub about it.
It would be great if you could add some kind of avatar system on top of (or outside of) IRC with this client. Also auto expandable URLs, emoji support and pretty much everything Slack offers.
I'm going to put this out there because I'm not sure where else to.
Recently I had the need for a better gitter-irc two-way gateway than gitter-irc-bot. Specifically, I wanted to be able to run multiple mirrors off a single bot/account. I started writing a multi-protocol gateway and the goal was to support slack, gitter, mattermost, irc and possibly matrix with a plugin API.
It's in python. I started rewriting it in Go and then found out toml support in go was lacking, then I sort of gave up... if anyone's interested in picking it up, file an issue on there!
I did! I should have said it's incomplete. I ran across #70[1] which is kind of really needed for the config structure I had in mind. After that I just went back to working on other stuff...
I'm kind of un-bullish on toml in general, sadly. I tried toml in a couple of projects, and found for structures nested beyond a certain level, it doesn't really seem all that simple anymore. I ended up going back to json or yaml (only with a parser that doesn't implement most of the fancy features of yaml, for conservation-of-sanity reasons, of course).
Interesting app, I've been using it here and there, mostly with a self-hosted IRC server. More or less a completely self-hosted chat system.
The UI is clean, and once it's up and running the experience is pretty smooth for users. However :
- Quite a hassle to install and maintain your own IRC server ...
- The server stores everything in memory. Pretty neat the first time you use it, but it tends to leak.
- Your user DB is just a bunch of json files, with no extensibility built-in. It could really use a "users" plugin, that connects to an external auth system ...
I use ZNC (http://wiki.znc.in/ZNC) as bouncer for years now. It is stable, fully developed, has support for multiple networks, SSL support, IPv6, a Web interface and lots of other features. Plus its easy installed as 'yum install znc'.
I did not read any advantage, neither in comfort nor in features that Shout has compared to ZNC.
What reason could one have to switch? Except to be on the bleeding edge?
I've been using this as my primary IRC client for a while now, and am really enjoying it, aside from it being difficult to reconnect to IRC servers when it occasionally disconnects. It's perfect for use with Chromebooks, tablets, and similar.
Similar to mailing lists, IRC might be less mainstream but is still heavily used in niches, i.e. for development and support of open source projects. The simplicity of the protocol makes it easy to use for automation (bots), i.e. CI servers or similar. I've also seen networks dedicated to file sharing.
I use vector.im for desktop and matrix console for android.
[1] http://matrix.org/