A long time ago parsing Echelog logs was how I was able to monitor the IRC activity of an attacker at a company I used to work at. I didn't normally sit on these channels myself, but Echelog enabled me to look back and collect data on the various handles that this person operated under.
There were 20-something handles they used over approximately a 6 month period of monitoring. I was always able to find a small piece of information to correlate these handles together. Sometimes it started with a hunch, such as the language (even slang) they would use, but eventually they'd slip up in some way and we'd have a pretty irrefutable link to the person.
This information helped us develop a motive behind the hack and the ongoing public info was then fed to national crime agencies. My employer never went through with prosecution, but as this person was of much interest behind other hacks they were eventually prosecuted and convicted. I always wondered if my occasional Echelog intelligence reports ever had a role in that conviction.
Indeed, and in that respect Echelog was a great source of OSINT material for the anecdote I described above. That, along with `whois` data and other public databases can reveal a lot without putting oneself at legal risk.
Once you’re dealing with criminals that are stealing in the order of millions of dollars, or sometimes even hundreds of thousands, the probability of being killed off for being a trouble maker dramatically increases. Anything over 10 million you will almost certainly be killed if discovered. By then you are dealing with robust criminal organizations with full time employees on a payroll with families to feed, and they aren’t going to put all that at risk because of one nosey fuck snooping around.
For one, the evidence might not be admissible in court of the defense has an okay lawyer. This goes for if you're doing it all on your own, and with no approvals and alignments.
I don't really use IRC anymore but at the time I remember really hating loggers. Chats were informal and I really didn't like them showing up in google results and elsewhere. Not everything needs to be saved.
I run a mastodon server on the fediverse (distributed social networking over activitypub). Mastodon and Pleroma support deletes, but say you post something and someone boosts it and one of their followers sees it on a server your server blocks.
You won't see their replies obviously (split thread) but if you delete the message, it gets deleted from your followers, but won't continue on to the server that your server blocks. So a copy will continue to exist.
I just treat the fediverse as a big chatroom/reddit thread that can never be deleted.
Yes, I agree. Lots(most?) of channels on freenode are explicitly not publicly logged anywhere, and the freenode staff are pretty helpful at helping chanops enforce this. None of the channels I help run have any public logs available.
Perhaps a naive question, but how do chanops enforce this? What's to stop someone lurking in a channel and publishing a log. You can't obviously connect an individual lurker to a log and busy channels have dozens of 24/7 clients connected.
> You can't obviously connect an individual lurker to a log
I don't think that's necessarily true.
While I don't know if the IRC Server software supports it, there's no reason you couldn't encode some kind of unique tag into the stream of IRC messages sent to each client. Unless you were running two clients and diffing their logs you wouldn't notice.
It could be as simple as seeing additional events, or modified whois/client information on join/leave, or even completely fake client join/leaves.
If you control the IRC server, there's nothing stopping you from modifying the events sent to every client in a way that lets you identify that client.
The difference here is that Freenode is not used so much for informal chat as with other IRC servers. Many free software projects use Freenode as the primary communication method for project coordination, and in this case it is essential to keep logs. Not everyone is online 100% of the time and logs enable everyone to catch up if they've been offline.
Sure, but those projects can also trivially set up logging with their own bots and in their own clients, with better control of what is logged, when, why, and how those logs are shared. This service appears to have logged fewer than 100 channels. This wasn't an aggregate logger and anyway aggregate logging probably isn't permissible anyway due to GDPR.
I would say chat history and asymmetrical scheduling for chat are expectations in this day and age, and the lack of them is one of the biggest reasons people find IRC irritating or difficult. (I ask a question, and if the person fit to answer it isn't logged in right now, it never gets even responded to.)
Every fairly modern chat solution, Skype, Discord, Slack, etc. allows you to see messages while you were offline. Compared to things from the older eras of messaging like AIM and YIM, when generally you couldn't even message someone unless they were online as well.
So it's not surprising to me for IRC loggers to be a relatively more modern element: They're filling in a gap IRC has with modern chat clients.
ZNC and earlier implementations have been around for 15+ years to provide queuing proxies. Pretty much all of the "unique" features found in current chat systems were also implemented in one fashion or another in the IRC ecosystem decades ago. Ease of use has definitely improved, in exchange for for-profit company control over communications in these systems. IRC's decentralized nature still argues for its relevance even now.
IRC is not really decentralised, is it? Or are you arguing that it’s decentralised in the sense that each user can implement and control some features like logging?
You probably did without realizing it. A persistently logged in user (through e.g. a bouncer, or just someone not rebooting too often) is essentially a logger. Those logs are private by their nature, but where I IRCed it was common for channels to each have their own logging bot.
I kinda doubt that Facebook actually deletes, as opposed to setting a DB flag... weren't they caught logging comments that were typed in but then modified / deleted / not actually posted?
The other party, i.e. the recipient still has an copy, so it could be a DB flag indeed. Although when both persons delete the message it might still lay around for who knows how long.
If you want a quick, casual conversation, I don't see why pseudonyms wouldn't be sufficient. You can also use random names if you're asking something really sensitive, which you would want to do in any case because it's a public space. For more in depth you can use your name if you want or a fixed pseudonym so you can recognize and be recognized.
I just wanted to take a moment and share with the HN community that IRC is definitely very alive and kicking! There are great channels for thousands of amazing projects, communities and teams spread across so many great IRC Networks, from Freenode [1] to OFTC [2], to Rizon [3], to DALnet [4], to tildeverse [5], Snoonet [6], Quakenet [7], EFnet [8], IRCnet [9] among other networks [10].
IRC is no longer difficult to use; there are great software applications across nearly every device that can be named which can work with and present the RFC1459 protocol splendidly, including weechat [11], KiwiIRC [12], Textual [13], Palaver [14], to mIRC [15], and AdiIRC [16], among others!
IRC has bots hosted by the community that can hook into github like bitbot [17] and supybot [18] among others.
You can also stay connected to IRC using an IRC bouncer like KiwiBNC [19], znc [20], IRCCloud [21], Quassel [22], Bitlbee [23] or shamlessplug jbnc [24].
Edit: Added a few that I accidentally left out. Thank you all! If I left anyone else out I apologize - IRC is so decentralized, spread out, and... alive... that it's hard to name all of the amazing projects, networks and implementations out there!
IRC is still alive in the fact that people still use it, but its dying (less people use it over time) in a way that will never be overcome.
IRC is lacking so many critical features that people consider the fundamentals of IM now. IRCv3 has been in development for forever and they still aren't done and even if they finished it it would never make it to all the irc servers and clients.
At this point it makes sense to join most other open source projects in moving to Matrix which still has active development and the ability to actually push out new spec changes in the current decade.
I think IRC will always have a place in certain communities.
I drop into IRC whenever I need help with an Arduino project or want to catchup with old colleagues. From my own personal experience, all the open source communities I get involved with use IRC and I have never known one use Matrix, sometimes this is for personal reasons and sometimes for work. This probably depends on what techie circles you move in.
I've also noticed IRC is more popular in certain countries. Anecdotally Brazil and Sweden seem to have fairly large communities of nontechnical people on IRC.
Maybe for some people, IRC does what they want and they don't need any updated spec.
The mere fact that we always see several people jumping in to assert how IRC is alive and kicking is in fact a giveaway that it, if not actually dying, is at least starting to smell a bit funny. (And frankly I say - good riddance! It's a protocol that's at least a decade past it's sell-by date, modern options are so much better)
People often don't seem to use modern alternatives like matrix though. I often see people switching to whatever the popular walled garden of the year is instead. Personally I prefer an open ecosystem to animated GIFs, even if it might occasionally smell.
If only I could build weechat from source on windows! If anyone out there is willing to provide binaries I'd be glad to buy you coffee so I can switch over from irssi
mIRC is what got me into programming, actually... I miss the good old days
My first programming projects were scripts and modules for eggdrop. Every now and then I get a nostalgia flash. :) Surprisingly, some of those are still being used... 20 years after the last release.
Mine were mIRC scripts for banning spammers. Eventually we had a community of people writing bots in perl, PHP, and loads of other languages. I was introduced to Unix by means of wanting to run irssi in screen so I could collect messages even when I was offkyine. It is no exaggeration to say IRC is completely responsible for my career, far more so than education!
What happened to irc.com? It seems like you had pretty big plans for it (especially with the letter you wrote on it), but it doesn't seem to have gone anywhere.
this list exemplifies the biggest issue i have with IRC. it's not federated. these are all islands, and i'd have to sign up on each one of them to join the community there.
that said, none of the newer alternatives are any better unfortunately.
it seems jabber really was the only federated system with any moderate success, and maybe matrix is getting there too with its ability to integrate different services.
i don't know if there are irc networks that require nick registratin, but there for sure are channels on freenode that you can't enter without a registered nick.
but that's not the issue. the issue is that i can't maintain a global identity, and that i have to add each network into any configuration instead of just sending a message to anyone on any network without creating an identity on that network (even if it's just picking a nickname).
some of this could be worked around in the client if the client has an uptodate list of irc networks so that sending a message to embee@freenode would automatically connect your client to freenode, make you pick a nickname and send the message.
hmm, that's an interresting thought experiment.
how could this be made seamless without inviting spam.
I miss gopher support on kolibriOS, it's the brother "simple" protocol for hypermedia. No TLS support as IRC, but you can either:
- use TOR over a gopher client.
- use and promote Gemini in paralell.
With Bitlbee and sacc(1) I can access even HN via Gopher and comment it on Telegram via sic(1). Magical and my setup could work even under a 286 with Minix2.
You can connect with SSL and optionally SASL (as well as cloaking your IP) but this is encrypted to the server. Most of IRC is public anyway though so E2E doesn't make total sense.
Yes, IRC servers can support or enforce TLS for the transport and end users can use OTR (Off The Record) with many IRC clients. IRC uses TCP which Tor supports. There are IRC servers on Tor. Here [1] is an example of WeeChat + OTR. OTR is E2E encryption.
So, I'm too young to have ever used IRC. This must be a biggish deal to make it #2 on HN homepage. But can someone put this in perspective of how big a deal this is?
On a scale of 'Rando County Legacy ISP-provided email service' to 'Gmail' is shutting down, where does this lie?
IRC is not email, etc. but again, never seen this community.
I've used IRC for over 20 years and have never heard of this service. On your scale, it's "your second cousin's friend's sister's dog's goldfish had a VPS that went down."
This is #2 on HN because people are reading "Freenode IRC ... is shutting down." That'd be closer to the gmail end of your spectrum. We are not shutting down freenode.
First of all, you're not too young for IRC, it's still out there! Lots of people! Lots of channels! Depending on your interests your usage could resemble a live-action Reddit.
Second, I don't think this is necessarily a big deal, though I could imagine that channel users liked the convenience of having their channel logged for them. There may even have been an ersatz Slack use-case there that people could easily get used to.
However, channel logging has historically been the responsibility of channel users themselves, so there's a loss of convenience that could easily be taken up by a channel user setting up their own facility: a tiny AWS instance running a bot logging to S3, with a web interface and maybe a search engine. But that takes time and money and maintenance and interest.
However, all of this functionality is out there on the web and internet, and has been used for a long time in various incarnations. I'm sure there are EFNet logs out there that go back well into the 90s.
IRC is still used massively. It is a relic of the days before corporations took the internet. When it was was still fun. TBH Discord is the closest modern equivalent and the only thing that discord really does better is the embeds and voice.
IRC has a ton of advantages:
1) IRC will run on ancient computers, I was chatting to people on IRC using an Amiga which is 25 years old and will run with virtually no bandwidth. I used to use a 33K modem to speak to my friends after school.
2) Anyone can setup an IRC channel pretty much instantly on a server and you and your friends can start chatting.
3) The message protocol is quite easy to deal with and parse. It also really, really, really fast. Messages are instant, there is zero friction. Slack and Discord are very slow in comparison
4) Building a bots for IRC was super simple. You can be building a bot in minutes in any programming language.
6) You could request files from server and bots IIRC. This was used quite a lot for warez back in the day and much faster than bit-torrent at the time.
7) It is pretty much anonymous. Make a nickname and connect to the server.
8) You can run your own IRC server pretty easily. You download the server software, config some XML/INI files and point your ___domain at the box. You have your own IRC server.
re Discord, the funny thing is that Discord is proprietary, and I'm not sure how exportable any data and/or voice/embeds are when you want to download it out of the service itself.
Also can't script the client, you can't run your own server. Also with MIRC IIRC correctly you could layout the chat windows pretty much anyway you wanted and even have like a desktop background.
Discord is a lot easier to use, but in a lot of ways it is really limited compared to the IRC clients.
> the only thing that discord really does better is the embeds and voice.
For me, the thing that Discord does really well is having a persistent message history, so I can join a server about a topic, see the pinned posts, read an FAQ channel, and learn a bunch without having to ask a question. That may be improved with IRC now, but at least when I was last using it (wow, 2 decades ago?!) that was a real pain point.
I threw TheLounge on a raspi in the basement and I have persistent message history now. Hit it from any browser, and I have a very Discord-like or Slack-like interface.
Been meaning to check out Convos which looks like it solves much the same problems.
Freenode has thousands of channels, there's a bot called "alis" that can help you find something interesting. To do that:
5) type "/msg alis list python -min 50", which will open a chat with alis, which will then show the channels with "python" in the name that have at least 50 users.
6) type "/join #python" to join the channel
If I have an in-depth technical question about Rust, I can make a post about it on the Rust subreddit, Stack Overflow, or the Rust community forums, but if I jump in IRC I'll have an answer in under five minutes and an interactive explanation.
IRC is the internet of the 90s and 00s. Without all the spam, advertisement, and noise.
The various haskell IRC channels are some of the best places to learn and get help/mentoring with that language - so many patient, genuinely helpful people. It's one of those things that made me go "Oh, that's what everyone is moaning abut" re demise of the old web etc.
unofficial irc logging services are kinda like the "I don't want to pay anyone, but I want to freeload off someone's netflix account" of the irc age.
If the material was important to someone, they would already be connected with a bouncer or logger of some kind. For people who can't run bouncers, etc, this is a good service, but again - if you really thought it was vital to your work and/or personal life, you would have spent some money to either purchase an irc service (like irccloud, etc) or pay someone to run a proper logging service.
The historical aspects are not nearly as dire in my opinion, - all someone has to do is to get a copy of the archive from this person (who doesn't seem opposed to this idea) - and host it somewhere. Again, the problem is costs - if someone deamed it important enough, they will mirror it.
In this age, probably someone like the Internet Archive since no one will pay for the maintenance (legally, technically, and otherwise).
freenode is the place where discussion happens. It is not closing. If it was, it would be equivalent to gmail closing.
The logs - depend on your stance. For what I do, no logs is better. Fewer logs may drive more people back. But here are many other loggers.
FYI, IRC is still very handy to have and deploy in 2020. It is light enough for a small VPS to handle, easy to scale by federating if needed, and the lack of file support and of logs can be a feature to keep everything private for in house deployments.
Just this morning I started to evaluate replacing some Javascript and Go code by some Fortran.
I'm starting to believe in the army motto: "Yesterday technology, tomorrow!"
Not just was, is! We still hold 90k concurrent users most of the time, and a couple hundred thousand unique users over reasonable spans of time, maybe 3 months?
I think this would be useful: how many unique users have sent at least one message in the last 24 hours?
I'm part of some of the channels you think would be largest on Freenode like #javascript and #nodejs. There may be hundreds of people in the online user list, but it's literally the same 10 people talking every day.
There's 10x that number of people talking daily in just Elm's Slack. I'm on three javascript-related webdev Discord servers that that each have at least 100 unique users interacting daily.
I have to wonder if 90% of people connected to IRC are just echoes in the system, autoreconnecting from old hardware long after their owners have moved on.
In these threads people always say "nah, IRC is doing great!" But frankly I don't think people realize how much IRC communities have shrunk. Its lunch has been eaten and it feels like the only people still around on IRC are aging people who once used it in its prime.
Many IRC communities have shrunk. Different reasons. Things like Discord and mumble, combined with more collaboration and multiplayer competition in games took gamers away from IRC and crippled networks like Gamesurge.
Social media, especially things like Twitter and the various short video sharing services took away the "general chat" demographic -- partially because folks who were closer (real-life friends and family) like to feel closer, and folks who are not tend to be younger, and the younger demographic trends towards newer technologies.
Tech stuff has held up on freenode for a while, but as you point out this isn't always the case. I would argue that freenode is probably safe from too much decline for a while yet -- those of us who are "aging people who once used [IRC] in its prime" (I'm 36, guy, "aging" is a bit harsh :)) also tend to be people with a lot of experience in $technical_topic. If you want to ask questions about $technical_topic, and the people with experience are on IRC, that's where you go.
You've pointed out a lot of Javascript-related stuff is not on IRC. Javascript is a relatively new technology (compared to IRC), Node is relatively newer, and Elm newer yet. The boom in web technologies, and the ability to run native applications written in JS has caused that community to surge. It's also relatively easier to get into Javascript than it is to get into (say) C. So you attract more people, and you're going to attract younger people, and you're going to have a really diverse audience for a wide range of topics. All of a sudden a single channel on a chat network doesn't make much sense anymore, and running an IRC network yourself doesn't seem like fun, so you decide to use Discord or Slack. I think this makes a lot of sense for lots of communities.
For other (especially smaller, or very niche) technical communities, IRC is still a good solution. It's not fair to say that "its lunch has been eaten" -- it'll remain relevant until text-based messaging is no longer the most accessible way to communicate. But there are other, different solutions for similar problems that do a better job of catering to specific audiences. And that's just fine.
Unfortunately, it's kind of a PITA to get unique counts from server stats, which are mostly aggregates. So I can't answer that question. But Freenode's a rather active network.
Agreed. Freenode was (and should still be, IMHO) the go-to real-time chat for open source projects.
I didn't realize how important at the time it was being founded. Rob Levin was an online acquaintance, and one day he started asking about how to fund an open source community service with donations. I was interested in open source and non-profits, so he and I talked a bit about that, but I didn't volunteer to help. Next thing I knew, he'd started Freenode, and projects flocked to it.
According to another comment in this thread, Freenode has 90k CCU, with hundreds of thousands over a period of a few months. The best number I can find for gmail is here [0], which shows Gmail had 72 million active users on android 6 years ago. Sorry to say but Freenode shutting down wouldn't even be a blip compared to gmail shutting down
This is just one logging service, not any actual IRC servers. So today's news is not necessarily a huge deal.
IRC as a system, though, is massively important. I'd say it's like the Twitter of the first half (so far) of the internet. When the (first) Gulf War began, the first reports were via IRC: https://news.ycombinator.com/item?id=7990835
I also ran a public IRC logger (mostly in and around the perl/raku communities, but also other channels).
Simplify figuring out if IRC logs fall under GDPR was nearly impossible to me, so I shut down some time ago. (It might have violated earlier privacy regulations as well, hard to tell).
Lots of people offered their opinion on that topic, but when it goes to court, none of those opinions matter. Hiring my own lawyer seemed too expensive, and nobody who asked me to continue running it offered to pay for a lawyer either. Tough luck.
There's a 80% chance that nothing would have happened, a 15% chance that people would complain about the privacy implications but won't do anything about it, and a 5% chance that somebody takes action and I get some sort of legal citation/penalty/whatever.
I prefer Igloo IRC, but finding a server and chatroom is an exercise you'll have to do on your own depending on what you are looking for. I would start with Freenode if you don't know where to begin.
Good riddance. I like irc more when I don't have to measure every word I say because some douchebag is silently logging everything and putting it in a website for everybody to see, index and archive, without my permission or anybody else's.
Sad to see GDPR still slowly killing anything too small to pay a legal team (basically anything that can be sued that hasn't incorporated, ie, human persons).
> Furthermore, the cost (financially, mentally and legally (GDPR)) of running the site, no longer makes sense for me.
I am surprised that privacy aware companies are not using IRC more for their intra company chat, and that none invested in a webcam voice chat client for IRC. Even the most basic server can handle thousands of clients.
I recall working at companies where the ops or DevOps teams would run their own IRC servers pre-slack. It was basically the only way to get stuff done if you had a desktop PC and needed to work closely with anyone. The problem is that most companies don't know how to do due diligence on a tool like IRC and the clients aren't very friendly. The lack of commercialisation of the space is what prevented companies from paying for it, and that meant no easy and rich clients got built, which meant it never got commercialised, etc etc..
There were 20-something handles they used over approximately a 6 month period of monitoring. I was always able to find a small piece of information to correlate these handles together. Sometimes it started with a hunch, such as the language (even slang) they would use, but eventually they'd slip up in some way and we'd have a pretty irrefutable link to the person.
This information helped us develop a motive behind the hack and the ongoing public info was then fed to national crime agencies. My employer never went through with prosecution, but as this person was of much interest behind other hacks they were eventually prosecuted and convicted. I always wondered if my occasional Echelog intelligence reports ever had a role in that conviction.