391–400 of 499 posts
> that Heroku hack What is the "that Heroku hack?" mentioned in that article
Earlier quoted context omitted.
Why do people talk like this is some impossible feat for IRC? 1. Have a bot that's in the channel from the start 2. cd into the bot's log directory and type python -m SimpleHTTPServer 3. put the url into the channel topic How do some developers fail to rise up to this level of problem solving? I am amazed.
What if I didn't have the foresight to put that bot into the channel in the first place? Or what happens when the bot goes down? So now I really need to build some alerting into it so that someone can restart the thing when it dies, or the server is upgraded, or it's moved.. because I'm losing valuable history along the way. Or I can just use Slack. The snark about developer skill is an interesting one, as you failed…
What you want is to outsource your messaging service. If you want this to be managed in-house, you must monitor the service as well. You can outsource IRC as well however, and they'll manage the boys and infrastructure for you.
Not sure if I understand what the issue truly is here!
Earlier quoted context omitted.
Does IRC Cloud allow new employees to get the entire history of the channel? I can't see how it would from looking at its page.
Why do you want that? At my company I don't think anybody has IRC logs enabled, and it is highly suggested that you don't do so - chat, much like real life conversations, is inherently ephemeral.
Should this end up in a separate wiki? Maybe. Will it? Not always.
Earlier quoted context omitted.
> The discussion is about users who use IRC directly and consciously. From the parent post I replied to, "IRC's user base is declining". Every single person watching a Twitch stream is an IRC user, whether they know it or not. How do you determine the popularity of something? How many people use it. Android is extremely popular. Do most of the folks realize they're using an Android phone? Nope. Does it mean Android i…
Of course they're all IRC users inadvertently. That doesn't add to IRC's popularity. If Twitch disabled IRC and switched its chatrooms to some ghetto socket.io app, most of its users wouldn't know. > Of course they wouldn't, you're already speaking with them. Slack is fine for trusted networks of peers (businesses), but not much else. I won't start chatting with any my friends using it, nor would I bother to sign up…
> No, what I meant was, people no longer think of IRC as the tool to use to talk about projects and communities. They used to. That was its primary use case. That use case is shrinking, so IRC is becoming less popular.
There's plenty of other avenues to use these days, so the numbers have diluted, absolutely. EDIT: There was no social media, very few IM clients... But the channels I'm in have been steadily rising (Freenode). http://tctechcrunch2011.files.wordpress.com/2013/01/irc-002....
Quakenet took a huge drop once it stopped being used to find CS matches.
> This isn't quite true, is it? Most Android users seem to know they're using Android. I could be wrong.
Obviously this is going to be anecdotal, but with the ~20 people I know who aren't technologically savvy, they'd only be able to tell you if they're using an Apple phone or not. My mother, for instance, has no clue that she's using a Windows phone. EDIT: I guess that really goes to show something about the success of Apple's marketing.
Earlier quoted context omitted.
EsperNet server administrator here. You did not 'nearly break EsperNet' with EiraIRC usage. Our capacity vastly exceeds our load (we could likely run the entire network from a single one of our servers). However, the time our administrative team has to spend differentiating abusive bots from non-abusive ones is finite, which is why we place so many restrictions upon bots.
I do not doubt you. But that's not what we were told. Another admin from espernet basically had us kill the project because they said the way Eirc was using the system constituted a "significant load" and "would not scale well". We were growing really fast and proxying maybe 3-10 users per bot connection on average. I think your team came to us with the problem right as we were really exploding with users. We basical…
Additionally, we hesitate to cater to this use-case as it often ends up turning into "we want your network to relay messages between our bots" instead of "we want to talk to other people". We've found that channels used for such bots are typically not sufficiently staffed and frequently a target of abuse, which ends up taking network staff time to resolve.
Lastly, we've had a number of technical issues supporting certain pieces of IRC client software. Older versions of EiraIRC in particular have some nasty bugs; the worst of which is that they tend to get stuck in some state where they hold multiple connections to the network open while continuing to attempt to connect again and again, with no delay. While this doesn't impose load that our servers can't handle, it does generate a lot of administrative log traffic that is bogus and dilutes important log traffic.
Many of these use cases can be covered by IRC, but our network isn't configured to handle such use easily as it often looks very similar to the sort of abuse we usually deal with. The common denominator in most cases like this is that it's taking too much of the staff's time and attention to support the channel and its clients. Our time is finite, and for the health of our network, we'd rather say "no" to a few channels than to make all channels suffer from thinner network staff resources.
If IRC were good enough to handle the needs of small software company communication, people would use IRC . Sitting here pretending everyone just doesn't know about a 20+ year old technology is comical. The "IRC Features" section bugs me, too. Unless you run a private IRC server IRC has a long, tortured history of design-based security difficulties. Gone are the days of netsplits permanently owning channels, but the…
IRC usage stats are really bad. Steady decline from 1 million users in 2003 to 400k in 2012. In a time where we're talking about communication apps with hundreds of millions of users, not even having a million is pretty telling to me. http://royal.pingdom.com/2012/04/24/irc-is-dead-long-live-ir...
When most people will do all their chatting in Facebook or Slack, OSS developers will still use IRC.
Earlier quoted context omitted.
Slack's benefits over IRC are largely not subjective: * The ability to directly send files and images to channels is an objective benefit Slack has over IRC, which has even less ability to do that than MIME email (at least MIME lets you post the base64'd file contents of your image, rather than just a clickable link). * The ability to send long messages or whole source files is an objective benefit Slack has over IRC…
icb4lyfe
It's not as simple as "just use IRC". Even in cases where an IRC channel is both available and relatively well-promoted, some communities still seek out other tools. The first example that comes to mind is Reactiflux, a rather large React.js community that recently moved from Slack to Discord[1][2], another closed source app that will probably stay that way[3]. To me, the fact that a community of tech-savvy developer…
For context, we've always promoted IRC for real time communication on React. I encouraged people to setup other mediums for communication and many people attempted but only one took off: Reactiflux on Slack. The official way is still IRC on the website but most people are using Reactiflux which is pretty incredible. Now, we got the bad news a month ago that we've been kicked off of Slack :( So, I started looking at a…
If you don't want to use Slack for open source projects because it's closed-source, fine. That's a reasonable argument. If you don't want to use Slack for open source projects because Slack is in fact pretty bad at those workloads, fine. I agree! I think Slack does a pretty bad job at any group application where most of the people communicating don't already know each other. Where you go off the rails is in suggestin…
Usually you'll have a bot gather the channel's history that you can ping and most IRC clients collect the history locally. In the use cases that -most- people use Slack for, it's identical to IRC. I don't use IRC anymore, I use Slack but only because it's convenient. IRC is all over the place like the majority open source projects. Slack is clearly inspired by IRC, but it's in a pretty package and works OOB. Not sure…
Yeah, that's not nearly the same. What I love about HipChat (and I'm sure Slack is the same, but I don't know) is that you can connect from any device and see the room history when you join a room. Going to some website to scroll back to see what people were talking about before you joined is annoying, especially so on a phone.
