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

31–40 of 106 posts

Re: Shout – A web IRC client

#31

Post by malditogeek »

ishbits wrote: post #12
alrs wrote: post #6

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

Are HipChat and Slack free enough to use as an open source project chat/support room?

If you host your source on GitHub, you should definitely check out Gitter. It's free for public repos and the integration is great; you get Markdown, integrations, IRC bridge, etc. Check for example the Marionette community to get a feeling of it: https://gitter.im/marionettejs/backbone.marionette. Disclaimer: I work at Gitter, feel free to ping me at https://gitter.im/malditogeek

Re: Shout – A web IRC client

#35

Post by Nickoladze »

alrs wrote: post #6

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

My friends and I replaced our IRC server with Slack and just use the IRC gateway to connect to it as if it were an IRC server. Pretty much seamless.

On the plus side, the Slack Android app is pretty good. Much better than any IRC app I've used.

Re: Shout – A web IRC client

#36

Post by mnutt »

avree wrote: post #30
morganherlocker wrote: post #24

Earlier quoted context omitted.

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.

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.

Re: Shout – A web IRC client

#37

Post by nacs »

vhost- wrote: post #15
erming wrote: post #13

Earlier quoted context omitted.

One more thing: Freenode has given me about ~20 slots to work with on this demo. If you can't connect, try another network, like `irc.rizon.net` or something.

What do you mean slots? Is it just because connections are coming from one IP and there is a limitation on their end?

Most IRC networks have a per-IP connection limit.

The slots in this case are the amount of connections that can come from the demo server (20 at the moment).

If you ran this software on your own server, you wouldn't run into the problem unless you tried to open 20 simultaneous connections to 1 IRC network.

Re: Shout – A web IRC client

#39

Post by wut42 »

valarauca1 wrote: post #11
wut42 wrote: post #7

Earlier quoted context omitted.

I love IRC but Slack/hipChat has some features IRC can't provide. Especially, the "formatted"/"preview" (images, videos, URL preview, tables) messages. 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.

Circa 1994: Even if the web client supports some of these features the protocol is just text, you can't add meta/structured data to a page. 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.

Yeah, sure. So let's add some headers directly in the message! … How do you update all IRC clients to your new spec ? :)

Re: Shout – A web IRC client

#40

Post by nacs »

avree wrote: post #30
morganherlocker wrote: post #24

Earlier quoted context omitted.

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.

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).
Post reply on HN