Not to be negative, but what does this have that couldn't be done better with ZNC and a proper IRC client? I get a persistent connection to the IRC server, logs and push notifications to my phone when I'm not connected or paying attention, and I can connect from as any IRC client I want to, or connect from multiple clients simultaneously. [1] Granted, the web client does look really really nice, but as a whole it see…
I would have loved to have this when I worked at a company that only allowed HTTP(S) through the firewall.
Show HN: Subway, a persistent web client for IRC
31–40 of 41 posts
Re: Show HN: Subway, a persistent web client for IRC
#32Earlier quoted context omitted.
What tech stack would you use, if you built a client like this?
It has less to do with technical reasons and more that node (and javascript in general) rubs me the wrong way. If the tech works for you then roll with it. Personally I think go works where node is often used, but fits my style of development better. Not to throw more feature work on you guys, but I always thought it would be neat to have an IRC client email you if someone mentions you while you were away...
Re: Show HN: Subway, a persistent web client for IRC
#33Earlier quoted context omitted.
I'm thinking more of a notification. Imagine monitoring a product support channel: if someone mentions you you want to know about it so you can pop into the channel if needed. I don't want to stare at a chat screen all the time.
If you have an iPhone, you can use ZNC and Mobile Colloquy to get push notifications on highlights.
http://noswap.com/projects/znc-push/ or https://github.com/jreese/znc-push
Re: Show HN: Subway, a persistent web client for IRC
#34Not to be negative, but what does this have that couldn't be done better with ZNC and a proper IRC client? I get a persistent connection to the IRC server, logs and push notifications to my phone when I'm not connected or paying attention, and I can connect from as any IRC client I want to, or connect from multiple clients simultaneously. [1] Granted, the web client does look really really nice, but as a whole it see…
Re: Show HN: Subway, a persistent web client for IRC
#35I had to `npm install` the following modules in the lib directory: connect-assets irc bcrypt socket.io
I'd love to be able to connect to multiple servers and auto-signin with NickServ and such.
Re: Show HN: Subway, a persistent web client for IRC
#36Re: Show HN: Subway, a persistent web client for IRC
#37The other collaborator here. I started with a similar client called web-irc, to make a better open source web IRC client. I combined forced with thedjpetersen because his tech stack was almost identical. And it looked better, to boot :-) Tech used: Node.js, node-irc, socket.io, Backbone.js, and MongoDB for optional message logging on persistent connections. Feedback and contributions welcome. This article is linked t…
Re: Show HN: Subway, a persistent web client for IRC
#38Not to be negative, but what does this have that couldn't be done better with ZNC and a proper IRC client? I get a persistent connection to the IRC server, logs and push notifications to my phone when I'm not connected or paying attention, and I can connect from as any IRC client I want to, or connect from multiple clients simultaneously. [1] Granted, the web client does look really really nice, but as a whole it see…
If you (still) think a IRC bouncer is a good tool then you'd be surprised by something like quassel :) http://quassel-irc.org/
With ZNC on my server, I can connect any standard IRC client to it, whether its Irssi or Weechat running in screen on my server, Xchat on my desktop machines, or AndChat on my phone. I also receive only a single push notification to my phone when I get mentioned or PMed, and can literally connect from anywhere to respond.
Re: Show HN: Subway, a persistent web client for IRC
#39Earlier quoted context omitted.
I would have loved to have this when I worked at a company that only allowed HTTP(S) through the firewall.
My point is there are already plenty of pure web IRC clients that don't rely on a local database; none of them (that I've seen) have any sort of nice interface like this does. There are also plenty of applications that will proxy non-HTTP connections over HTTP proxies. Corkscrew [1] also allows you to tunnel SSH connections over HTTP proxy, and you can use SSH to tunnel just about anything else you need.
Re: Show HN: Subway, a persistent web client for IRC
#40Earlier quoted context omitted.
Use a bouncer like znc (or this) and you don't have to get emails, it'll just be there when you get back
I'm thinking more of a notification. Imagine monitoring a product support channel: if someone mentions you you want to know about it so you can pop into the channel if needed. I don't want to stare at a chat screen all the time.