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…
Show HN: Subway, a persistent web client for IRC
21–30 of 41 posts
Re: Show HN: Subway, a persistent web client for IRC
#22Re: Show HN: Subway, a persistent web client for IRC
#23One of the collaborators here. Subway came to me as an idea a few months ago when I heard one of my co-workers trying to explain how to set up screen and IRSSI. The project has taken about 3 months to complete. There is still things to add like better IRC support and search. A quick disclaimer the logo right now is a Gowalla Icon, this is only a placeholder I am working on designing a new logo.
Re: Show HN: Subway, a persistent web client for IRC
#24Earlier 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.
Re: Show HN: Subway, a persistent web client for IRC
#25The 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…
The screenshots looks really beautiful. Unfortunately the demo link seems to be down at the moment
Re: Show HN: Subway, a persistent web client for IRC
#26Re: Show HN: Subway, a persistent web client for IRC
#27I like the interface, and I want to use it, but a lot of stuff seems to be missing, like I'd expect to double click on a user and open a private windows with him. Also most of the commands don't seem to work either.
Re: Show HN: Subway, a persistent web client for IRC
#28I like the interface, and I want to use it, but a lot of stuff seems to be missing, like I'd expect to double click on a user and open a private windows with him. Also most of the commands don't seem to work either.
It would help a lot if you could post issues on github for missing features.
Re: Show HN: Subway, a persistent web client for IRC
#29Not 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…
Main advantages are: 1. Accessible to those who don't have expertise or interest in setting up their own IRC bouncer 2. Usable from any web browser 3. More friendly UI 4. Usable by sites that want a chat room for their users (look at twit.tv -- embedded IRC client front and center). There is no proprietary backend; the whole client, and the library powering it (node-irc), are open source.
Ie, I would like to run your web client on my machine, have it connect directly to my IRC bouncer (or directly to a remote IRC server), and not require a local database to use it. I'm interested in using it as just another IRC client that connects to my IRC bouncer, rather than it being my primary IRC client. From what I see, this isn't possible.