After that, it's just a matter of implementing few plugins for popular IRC clients that would improve the UI of their respective clients to support those new features.
If anyone is going to start such endeavour, I'm willing to put some man-hours (starting next month) into writing plugins for ERC and Weechat.el, and maybe help with others.
Even if the IRC client supports some of theses features, the protocol is just text, you can't add meta/structured data to a message.
Those are all features of the client UI, not of the protocol. All can gracefully degrade to plain text for people whose clients don't support them. Image/video/URL preview is an UI feature over plain link. Tables... those you can either send as ASCII-art tables, or upload to whatever paste service you like (or host) and use the same preview mechanism to show a nice table on your rich UI client.
HTTP and TCP are just plane text too. Its what you do with that text that matters.
Somebody just has to find a way to shoehorn it in. I'd propose using a basic system built on top of the basic AK meta-protocol for serial communication.
https://github.com/ircv3/ircv3-specifications/blob/master/sp...
Inline images are annoying and I don't like that it uses non-standard protocols.
I also understand that Hipchat is not open source completely, and if so I don't like that.
Notifications are part of a client.
Permissions for large teams are nice, that is a useful feature I would like.
On the plus side, the Slack Android app is pretty good. Much better than any IRC app I've used.
You can do some amazing scripting stuff and really customize it.
There are a lot of custom versions of mIRC online with crazy color themes and what not.
Thanks for all the attention! The repository is here: https://github.com/erming/shout
It's open source, so if you're looking for a cool new project to work on, feel free to help out!
This is a really good looking web IRC client and it works so well with notification sounds, favicon updates etc.
Can I ask why there is a 20 slot limit? How can one increase this?
- It stays auto-connected with no configuration.
- It offers a great desktop (web-based) UI, including embedded images, videos, tweets, pastebins, and more.
- It offers fantastic mobile apps for both iOS and Android, for both phone and tablet form factors.
I still prefer Convos for all its built-in features and great community.
Otherwise I see 4 open source web-based IRC clients with very few regular contributors each. And the only really good IRC web client will still be IRCCloud (which is proprietary).
https://github.com/glowing-bear/glowing-bear
https://play.google.com/store/apps/details?id=com.glowing_be...
Why reinvent the wheel when you can let someone else do the heavy lifting? ;)
I really don't understand this. What features does IRC lack that Hipchat has? AFAIK, the advantage of Hipchat is the branding, the packaging, and the support.
The one thing I see ("image previews") is a feature of the client, not IRC itself. And many clients used to offer that, way back - the reason they turned it off was because it was a great vector to (e.g.) goatse someone. In any GUI-based IRC client, this is dead simple.
Most of what Hipchat seems to provide is branding and support, and I get that that's very valuable, but I don't see why that needs to be viewed as an either/or situation.
Never forget the "Show HN: Dropbox" and its immediate technical rebuttal [0], see where it is now.
Oh and Hipchat seems to do screen sharing, which AFAIK is not possible with IRC.
There's also a /quote command.
Edit: wait, that's for password protected channels, right? I need to pass a password through on server connection otherwise my ircd boots you off and kills the socket :(
For example, I run a web-irc instance for the people on the Montreal mesh network (which runs mostly on private/unique-local addresses).
Feature request: Make it work with quassel core. Currently there is https://github.com/magne4000/quassel-webserver but I don't like the UI as much as yours. https://github.com/magne4000/node-libquassel might help you with quassel connectivity.
However, I added "public" mode, where anyone is allowed to connect. And the demo server is currently running in this mode.
So right now? Nope. I'm not limiting anything. I guess this will be up to the person running the server to decide.
Thanks!
Looks pretty neat - even setup to work decently on mobile devices.
A suggestion - (I know I can just use my own CSS but,) there are low contrasts in the default theme. I usually have very good vision but for me it's pretty hard to distinguish the green from the white background. Maybe you could edit the default colors a bit?
I'll be forking shortly. Thanks!
