Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Shout – A web IRC client

github.com

Post reply on HN
Print view View original

51–60 of 106 posts

Re: Shout – A web IRC client

#51

Post by rdtsc »

codezero wrote: post #8
alrs wrote: post #6

Please let this put an end to the hipchat/slack madness.

Hipchat/Slack bring a lot more to the plate than just text chat, I think there is room for a customized IRC system to fill that gap, but it would take a lot, including native apps, notifications and tight control over granular settings, as well as centralized permissions for larger teams.

It has features but I don't think it is worth it.

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.

Re: Shout – A web IRC client

#52

Post by TeMPOraL »

brotoss wrote: post #42

Related question; anyone got a decent IRC desktop client for Windows? I'm using HexChat now, but loved Limechat wayyyy more on OSX. So much simpler/clean.

Well, if you don't mind switching your operating system to Emacs, there's ERC, and if you are willing to run a WeeChat instance on a *nix/Mac/Win+Cygwin machine, you can connect to it with weechat.el. I recently switched from the former to the latter :).

Re: Shout – A web IRC client

#53

Post by TeMPOraL »

There are a lot of comments here about how IRC lacks features of HipChat/Slack/whatever. If you want to try going the other way around, here's how to upgrade your IRC to support Jabber (including Facebook chat), Twitter and some other stuff:

http://www.bitlbee.org/main.php/news.r.html

Re: Shout – A web IRC client

#55

Post by wlesieutre »

nacs wrote: post #40
avree wrote: post #30

Earlier quoted context omitted.

You have to upload the image yourself, then. In a workflow, this is a time-waster.

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 adds up. And it doesn't interrupt the flow of whatever I'm working on, just a single action that doesn't require any thought or aiming my cursor to click on things.

Could I write an automated tool that takes my clipboard, uploads it somewhere, and replaces the clipboard with an image URL? Probably. Or I could use a chat platform that supports images.

Edit: Trimmed one step with copy image location instead of actually navigating to the image

Re: Shout – A web IRC client

#56

Post by chimeracoder »

TeMPOraL wrote: post #53

There are a lot of comments here about how IRC lacks features of HipChat/Slack/whatever. If you want to try going the other way around , here's how to upgrade your IRC to support Jabber (including Facebook chat), Twitter and some other stuff: http://www.bitlbee.org/main.php/news.r.html

> 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 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.

Re: Shout – A web IRC client

#57

Post by avree »

mnutt wrote: post #36
avree wrote: post #30

Earlier quoted context omitted.

You have to upload the image yourself, then. In a workflow, this is a time-waster.

There's no reason Shout couldn't accept HTML5 copy-and-paste, upload locally or to s3, and the send a link to the uploaded image.

Which is what Slack does, the ideal use case I was describing.

The person I was replying to inquired as to why uploading the image and pasting a link was a problem. He said:

"Limechat shows image links inline, which is good enough for me anyway. In some ways it is even preferable to tying things to one particular storage solution like s3."

Post reply on HN