Earlier quoted context omitted.
They'll pipe up if the question is something like "What's the flag to make ls display in color?". IRCers are generally pretty quiet if you ask something actually technical or involving the code, or they'll just offer up a lot of speculation and irrelevant links. My theory is that the real project leaders and developers use mailing lists because they need to get work done, not watch IRC.
That depends a lot on the project. I've noticed significant difference in the attitude of several IRC communities.
IRC is dead, long live IRC
161–170 of 178 posts
Re: IRC is dead, long live IRC
#162Back in the day you could find a server to talk about your favorite band or hobby or tv show. Meet like minded people and make friends.
Today Twitter or Google+ is probably the closest alternative but are lacking the essence of what IRC was.
At scussion.com we are working on building realtime chat to be integrated with these communities (interest based communities).
I would love to just have a hangout to chat about sci if or sport like IRC was back in the day.
Re: IRC is dead, long live IRC
#163Earlier quoted context omitted.
Is this supposed to be a joke? Why in all seven hells would you use a proprietary, hosted service which brings you zero advantages over a time-tested, open and simple network protocol which you can extremely easily host and extend yourself? I don't get you people. I really don't get you.
I mean, I can give you the reasons that I have a hipchat account which I use with my coworkers, even though a good 50% of us are also on IRC for other purposes. 1) It proved to be a pain supporting the non-techies using IRC 2) Nobody wanted to maintain the IRC server and set up logging. (And, if you add up the couple hours to do so and maintain it in a year, hipchat ends up being a good deal) 3) Some of our people us…
For me, that trumps all your points. It seems that for you, it doesn't. The world's a crazy place.
Re: IRC is dead, long live IRC
#164Earlier quoted context omitted.
I mean, I can give you the reasons that I have a hipchat account which I use with my coworkers, even though a good 50% of us are also on IRC for other purposes. 1) It proved to be a pain supporting the non-techies using IRC 2) Nobody wanted to maintain the IRC server and set up logging. (And, if you add up the couple hours to do so and maintain it in a year, hipchat ends up being a good deal) 3) Some of our people us…
When you host your chat on somebody else's service, you don't have privacy (or confidentiality). For me, that trumps all your points. It seems that for you, it doesn't. The world's a crazy place.
I mean. If that's truly a concern, it seems like you need to own and configure your own physical hardware and require VPN access to all of them. For us/me, the cost and inconvenience isn't worth it, considering the basically valueless data to an outsider.
That's not to say that everyone decision matrix is the same or should be... As you mention.
Re: IRC is dead, long live IRC
#165Earlier quoted context omitted.
Wow, quite a testimony. Thank you! Is this it? http://www.hawkee.com/view.php?file_id=205
Yup, that's it! Haha, nice find.
Re: IRC is dead, long live IRC
#166Earlier quoted context omitted.
Having written an IRC client and several bots, I actually like the simplicity of the protocol.
@bonch (your comment is 'dead') The idiosyncracies that you have to get into when you want to write a proper client for humans, and what you actually have to worry about if your aim is just writing tools that use IRC (internal deployment bots, or whatnot) are miles apart. The vast majority of users will only be interested in the second. Just follow the RFCs for the features that you need, and ignore everything else.…
There are extensions to the protocol to support returning multiple privileges in RPL_NAMREPLY, but now your tool has to support both modes of operation. Additionally, the usual medium for discovering these extensions, RPL_ISUPPORT, slightly differs between networks, and today there are now multiple ways to query a server's capabilities, so you have to support RPL_ISUPPORT, PROTOCTL, CAP, and possibly others I haven't seen, and their features overlap. Also, none of these are officially standardized.
All this adds up to needless hassle when you're trying to implement a full-featured framework or tool. These are problems that should have been officially addressed years ago so that everyone is on the same page.
Re: IRC is dead, long live IRC
#167Earlier quoted context omitted.
Well, except IRC isn't dead... http://irc.netsplit.de/networks/top10.php?year=2012
When I click through the years, I see its slow decay.
Freenode, for example, keeps growing steadily since 2007, many of the smaller networks show pretty much a flatline or cross-shift in the same timeframe.
As it stands the networks still serve ~500k daily users; seems a bit early to call it "dead".
Re: IRC is dead, long live IRC
#168Earlier quoted context omitted.
First, consider XMPP instead.
Or do yourself a favor and don't. For casual group chat IRC blows xmpp out of the water. Every experience I've had with xmpp group chat has been subpar and frustrating.
Re: IRC is dead, long live IRC
#169I'm maybe an exception since I am and have "always" been heavily involved in IRC, but IRC is still a central part of my life. My irssi session is connected to around 120 channels on 16-or-so networks right now. I've met my fianceé on IRC, got friends for life from all over the world through IRC, got jobs and assignments through IRC and I almost daily solve complex problems with the help of my community and network of…