Live data from Hacker News

Show HN: A browser-based IRC client built on Node.js – first Node project

airchatter.net

41–44 of 44 posts

Re: Show HN: A browser-based IRC client built on Node.js – first Node project

#41

Earlier quoted context omitted.

It shouldn't. The install script copies files that you need super user privs to get at (specifically, /usr/lib), but after it's installed, you should be able to run the aIRChat server (node Content/app.js) without sudo.

Awesome thanks. I really like it.

I'm really glad that you're liking it! :)

Re: Show HN: A browser-based IRC client built on Node.js – first Node project

#42
post #40
post #35

Earlier quoted context omitted.

If you mean not always connected to IRC and that your solution is to run Irssi in a screen/tmux session on a server somewhere, it's considerably easier to use ZNC. http://wiki.znc.in/ZNC

I don't remember trying ZNC, but the problem with all the irc bouncers I've used before was that it wasn't neatly integrated to the irc client. If you're using screen+irssi, everything works exactly like you would expect. With irc bouncers you have various issues, e.g. when you connect all the channels need to send 2000+ rows of backlog for every channel, which is pretty inefficient.

What!? That's completely the opposite to my experience! Essentially, after setting up ZNC to your liking, all you have to do in your client is change the irc server from say, irc.freenode.net to znc.yourserver.com:port and add a password for the server, username/freenode:password, done!

I thought it'd be annoying having to add servers through the ZNC interface (either web or SSH) but it automatically adds/removes them when you join/leave.

In terms of buffers, I generally don't have it set to 2000+, normally around 100 max. I'll just go through the logs if I really need to catch up.

Re: Show HN: A browser-based IRC client built on Node.js – first Node project

#43
post #40
post #35

Earlier quoted context omitted.

If you mean not always connected to IRC and that your solution is to run Irssi in a screen/tmux session on a server somewhere, it's considerably easier to use ZNC. http://wiki.znc.in/ZNC

I don't remember trying ZNC, but the problem with all the irc bouncers I've used before was that it wasn't neatly integrated to the irc client. If you're using screen+irssi, everything works exactly like you would expect. With irc bouncers you have various issues, e.g. when you connect all the channels need to send 2000+ rows of backlog for every channel, which is pretty inefficient.

The clients I use have ZNC integration. I use Textual on OS X and Colloquy on iOS. Both automatically play back the buffer when they connect without having to do any setup like perform scripts or whatever.

I also compiled a module for ZNC that sends push notifications to Colloquy when a PM, highlight word or name mention happens.

Re: Show HN: A browser-based IRC client built on Node.js – first Node project

#44
post #24

Earlier quoted context omitted.

Yes, right now it's only in memory. I've been thinking about storing the logs in .txt-files (with the option to turn this feature on/off). This way, I could let the user download the logs directly via the browser.

I'm not familiar with how difficult it may be, so please tell me if I'm off base. But couldn't you offer the option for either text logs or HTML logs? I know that when given the option, I opt for HTML logs for the ease of reading.

Hi! Didn't see your question until now.

While I haven't implemented the logging yet, I'm thinking about storing them in the JSON-format. Messages are already stored as JavaScript object, so I think this is my best option. And exporting them as .txt on demand, shouldn't be a problem either.

Thank you for the feedback

Post reply on HN