Questionable Data Mining Concerns IRC Community
jessekeys writes "Two days ago an article on TechCrunch about IRSeeK revealed to the community that a service logs conversations of public IRC channels and put them into a public searchable database.
What is especially shocking for the community is that the logging bots are very hard to identify. They have human-like nicks, connect via anonymous Tor nodes and authenticate as mIRC clients. IRSeeK never asked for permission and violates the privacy terms of networks and users. A lot of chatters were deeply disturbed finding themselves on the search engine in logs which could date back to 2005.
As a result, Freenode, the largest FOSS IRC network in existence, immediately banned all tor connections while the community gathered and set up a public wiki page to share knowledge and news about IRSeeK. The demands are clear: remove all existing logs and stop covert operations in our channels and networks.
Right now, the IRSeeK search is unavailable as there are talks talking place with Freenode Staff."
Change is certain; progress is not obligatory.
FWIW, IRSeeK seems to have had a change of heart, or at least is being receptive to privacy concerns:
http://www.irseek.com/blog/
Sounds like a genuine response of concern to me...
WTF? Do you even know what the point of IRC is?
Netsplits - my primary hate object. Since IRC is adfree and without a corporate backer, the service levels are often poor to terrible.Anybody who has used IRC for awhile knows how to handle netsplits. They are a fact of life with the way the protocol works. And what do you mean "IRC is adfree without a corporate backer?" There is nothing called "IRC", there are individual IRC networks, most of which are volunteer efforts. Nothing is stopping you from finding or starting a network with corporate backing if you think it will be more reliable. Personally I think the fact that it's all volunteer run is a plus and not a negative.
No offline messages. Since there's no single backer, you can't send a message to someone that they'll get when they return.Some networks have services that will do this. On others you can use a private bot to do it. You think it should be done at the protocol level instead?
No support for smileys/other short animations. No, it's not just teen girls using thoseThat's a client-level function. WTF are you bitching about? I'm sure there's a script out there for mIRC that would give you smilies and animations if you really want them. IRC is just a protocol for communication between servers and clients. It's up to the client to format and display the data. AIM is no different in this regard -- your wink is still sent as ';)' -- the client just puts a pretty graphic on it.
No support for mic, webcams etcYou could do webcams with sound with a decent script in most clients. But if that's what you want then IRC probably isn't for you.
DCC sucks terribly particularly with firewalls and NATYeah and sending files on IM also sucks with firewalls and NAT, unless you have opened up ports or your client and router support upnp. Again, what's your point? How is this something lacking with IRC?
You can register for a nick on most networks, but that doesn't stop someone else from taking it so messages go to the wrong peopleIf those people are basing your identity solely off your nick then they don't understand IRC very well. And as you say, some networks have nick registration if this bothers you. Some will even auto-kill people using your nick.
Doing some of the more advanced features like sharing a folder with someone (fserve) is a lot harder than in modern chat programsSo write a better client if this bothers you that much. Or even a script for an existing client. There's very little you can't do with the scripting language in a modern client like ircII epic.
he hacks to allow other clients to access those networks aren't exactly helping the uptake of an open standards backend eitherIRC is one the most open protocols there is. All of the various ircds are well documented and most are open-source (if not GNU) projects. The underlying IRC protocol itself is simple enough that anybody with Wireshark and half a brain could reverse engineer it if they wanted to do so. Hell, I largely taught myself scripting/coding and protocol analysis by playing around with IRC and tcpdump back in the day.
I want peace on earth and goodwill toward man.
We are the United States Government! We don't do that sort of thing.