TapChat is similar, has web and Android apps: http://tapchatapp.com/
Shout – A web IRC client
71–80 of 106 posts
Re: Shout – A web IRC client
#72If only WebSockets allowed for raw TCP/UDP requests in the browser - would bypass the need to connect over a third-party server..
True, but you would only be connected while your browser is open. I think it is preferable to have a client running somewhere on a server and connecting to that. Even better if it's not a third-party server but your own. In the end, what's the difference between attaching a screen session and connecting a web client? I use WeeChat in a terminal multiplexer and connect to it with Glowing Bear.
Re: Shout – A web IRC client
#73Please let this put an end to the hipchat/slack madness.
One way to fix that would be to list a set of features that hipchats, et al. have that are desirable, and then think of the way to gracefully degrade them to plain-text format. 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-hou…
If I'm understanding correctly, you're talking about a web chat service with a UI that just uses IRC as a backend to communicate between users? If so, that sounds pretty sweet.
Re: Shout – A web IRC client
#74It's neither free nor open-source and it's cloud-hosted, but IRCCloud (irccloud.com) probably deserves a mention. Like I said, it's a bit of a different solution since it's more than just a client, but what I like about it is that it basically solves every problem a typical IRC user is likely to encounter:
- 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.
Re: Shout – A web IRC client
#75Earlier quoted context omitted.
> There are a lot of comments here about how IRC lacks features of HipChat/Slack/whatever. 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 becau…
As always, the problem is not technical, it's packaging. Technically IRC can do all that Hipchat does, but Hipchat provides a simple bundle that any team can subscribe to/buy and use for all its use cases. To replicate the same thing with IRC, you'd need bouncers for everyone with full text search capability, a shared history of everything that happened on the server(s) of the network, support for filesharing for all…
Hmm, what you are suggesting in the beginning sounds just like Quassel:
It is a Bouncer with full PostgreSQL database of the whole log, full search functionality, a shared history between users of the same bouncer, etc.
There are clients as a website (runs on node.js), for Windows, Mac, Linux, iOS and Android.
So, if someone would add the missing features to Quassel, we could make that one the new new HipChat.
Re: Shout – A web IRC client
#76Looks amazing! My IRC server uses a password however, and I can't see anyway if inputting that. I tried using a straight /connect command, but that doesn't appear to work either. Might have a go at a pull-request!
Re: Shout – A web IRC client
#77If you prefer something that doesn't force you to go all in, check out Glowing Bear. It's a WeeChat relay client that I've been contributing to. Basically, it connects to your existing WeeChat running on your server, meaning you can continue using that, or use both in parallel. Works great on mobile as well. https://github.com/glowing-bear/glowing-bear http://www.glowing-bear.org/ https://play.google.com/store/apps/d…
Or just use an IRC bouncer and connect any IRC client to it at any time, and get a lot more features than what Weechat offers. ;)
Re: Shout – A web IRC client
#78Earlier quoted context omitted.
An IRC bot in the channel could solve this problem easily (grab any image/binary link and mirror to a predefined location).
But you have to put the image online somewhere before the IRC bot can mirror it, so I don't see how that helps. Here's how I see the comparison: Hipchat: 1) Paste image Imgur + IRC: 1) New browser tab/window 2) Paste image 3) Click "Start Upload" button 4) Wait for upload + redirect to new page 5) Right click, copy image location 6) Switch back to IRC 7) Paste URL I use this somewhere from 10-100 times a day, so it a…
> Hipchat:
> 1) Paste image
Then the history if filled with stupid crap and you can't find any useful stuff in it. Stupid text can be easier to jump over, images spanning the whole page can be more annoying.
Re: Shout – A web IRC client
#79Earlier quoted context omitted.
One way to fix that would be to list a set of features that hipchats, et al. have that are desirable, and then think of the way to gracefully degrade them to plain-text format. 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-hou…
If I'm understanding correctly, you're talking about a web chat service with a UI that just uses IRC as a backend to communicate between users? If so, that sounds pretty sweet.
Not really; I was thinking about taking all those Awesome Features IRC Doesn't Have and actually implementing them in various popular IRC clients, web-based or not, in order to make IRC a viable alternative to HipChat, et al. for power users.
Re: Shout – A web IRC client
#80Hey, guys. 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!
Thanks this is awesome - I would love to integrate it with sagebump.com instead of using freenodes client. Can I ask why there is a 20 slot limit? How can one increase this?
The 20 slot limit being mentioned is just in regards to the demo connecting to freenode. The demo connects to freenode from a single IP address and freenode has limits on how many connections you can have from one IP. It's not something you need to worry about in a normal use-case.