Slashdot Mirror


IRC Turns 30 (www.oulu.fi)

IRC (Internet Relay Chat) was born at the Department of Information Processing Science of the University of Oulu 30 years ago. Taking some time out of his summer job, Jarkko Oikarinen developed the internet chat system. For the last several years, Oikarinen has been working at Google, overseeing the development of several communication services. Though several mainstream services have ended support for IRC over the years, the system is still in existence and used by many.

157 comments

  1. EFnet is still dying! by AndroSyn · · Score: 3, Funny

    Netcraft hasn't confirmed it yet, but EFnet is still dying.

    1. Re:EFnet is still dying! by Anonymous Coward · · Score: 0

      Is DALnet dying? Freenode seems to be going strong.

    2. Re:EFnet is still dying! by Highdude702 · · Score: 2

      Efnet is full of scum now, dalnet has been dead to everyone but sex fiends for 15 years, Freenode has become "free support network" for various companies. XDCC is on its last leg as it has been for 20 years. Private IRC servers is where the fun is at..

    3. Re:EFnet is still dying! by Anonymous Coward · · Score: 0

      dalnet has been dead to everyone but sex fiends for 15 years

      Pretty sure most the sex fiends have moved onto camming apps. If you actually check dalnet's list you'll find virtually no sex related channels. Always used to have difficulty getting on efnet in the past, and I'm not really interested except when some program's support channel is on there. Which leads to..

      Freenode has become "free support network" for various companies.

      And a variety of open source projects. Really, anywhere there's some communication channel people use it as a "free support network". It's just that Freenode has been mostly hospitable to that use--honestly, I don't know of an IRC network that's actively inhospitable to that usage in general. Perhaps because IRC is generally dying and they want to be relevant? *shrug*

    4. Re:EFnet is still dying! by Netcraft+Confirms+It · · Score: 1

      Yes, it's dying. It's been dying for 20 years.

    5. Re:EFnet is still dying! by Anonymous Coward · · Score: 0

      Efnet is full of scum now, dalnet has been dead to everyone but sex fiends for 15 years, Freenode has become "free support network" for various companies. XDCC is on its last leg as it has been for 20 years. Private IRC servers is where the fun is at..

      when you say fun... ? clarify please? and maybe post some links to those server?

      and dalnet, hm is that become like a dating scene for one night stands or? :-)

  2. For those not familiar with IRC... by Anonymous Coward · · Score: 3, Funny

    ...here's a highly technical description of the software:

    https://www.youtube.com/watch?v=O2rGTXHvPCQ

    1. Re: For those not familiar with IRC... by Anonymous Coward · · Score: 0

      Warning, do not click. Spam post.

    2. Re:For those not familiar with IRC... by Doctor+Morbius · · Score: 2, Insightful

      It's not spam. It's relevant and funny.

      --
      If I disagree with you it's because you are wrong.
    3. Re:For those not familiar with IRC... by Provocateur · · Score: 1

      Get off my lawn!

      It had to be said.

      --
      WARNING: Smartphones have side effects--most of them undocumented.
  3. Old code never dies. Working code at least by AlanObject · · Score: 2

    Isn't Slack based on IRC? Slack is the Latest Cool Thing you know.

    1. Re: Old code never dies. Working code at least by reanjr · · Score: 4, Insightful

      It should have been. There's no reason it couldn't have been. It even used to support it with an optional gateway. But no. Slack decided to fill our Intertubes with yet another worthless proprietary clone of IRC.

    2. Re: Old code never dies. Working code at least by Anonymous Coward · · Score: 0

      Can someone please tell this old person what all the hype is over Slack? I just see this as the latest new trend everywhere I go.

      Why the hell would anyone trust their communications with a platform like this?

      Is it because it just integrates into other software applications people use?

      I just don't get it. Are there any non-millennials that use Slack and can explain if there is anything superior whatsoever that would cause someone to willingly consider using it?

      I sincerely do want to know and all the answers I've found about it haven't revealed anything superior that I can ascertain.

    3. Re: Old code never dies. Working code at least by Anonymous Coward · · Score: 0

      It works in China so it can be a useful way to communicate with your team. Product itself is bloated

  4. Trouts by Anonymous Coward · · Score: 0

    do not a good sushi make

    mode +b

  5. And re-invented over and over again ... by UnknownSoldier · · Score: 4, Insightful

    The latest re-incarnation is Slack. Before that was HipChat, etc.

    Note: If you can't stand the amount of spam images in a channel and want to minimize the stupid GIF animations you can use the Slack command: /collapse

    It is almost comical how every modern utility has been re-invented multiple times.

    1. Re:And re-invented over and over again ... by Anonymous Coward · · Score: 0

      There's always someone out there who has an idea about how to build a better mousetrap.

    2. Re:And re-invented over and over again ... by Narcocide · · Score: 2

      The biggest part of the problem is people framing the task of creating better communication tools in a metaphor about bulk harvesting of vermin for extermination.

    3. Re:And re-invented over and over again ... by mwvdlee · · Score: 1

      The fact that it's constantly being re-invented is proof of it's quality.
      Businesses would be trying to vendor-lock customers in proprietary protocols based on OTHER open standards if it wasn't.
      Worse, they could be inventing their own protocol from scratch.
      IRC will still be around long after the latest fad chat has died.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    4. Re:And re-invented over and over again ... by Anonymous Coward · · Score: 0

      Yeah, that's a really big problem.

    5. Re:And re-invented over and over again ... by Anonymous Coward · · Score: 0

      I'm so clever, oh so clever, how clever how clever am I! And I'm clever, I'm the most cleverist there eeeever waaaassss!

      I'm so clever, oh so clever...

    6. Re:And re-invented over and over again ... by Anonymous Coward · · Score: 1

      You sound like a member of PETA. Glad you got that Animal Crackers business sorted out, I was losing sleep over that.

    7. Re:And re-invented over and over again ... by CaptainDork · · Score: 1

      AI builds a better mouse.

      --
      It little behooves the best of us to comment on the rest of us.
    8. Re:And re-invented over and over again ... by tlhIngan · · Score: 1

      The latest re-incarnation is Slack. Before that was HipChat, etc.

      Note: If you can't stand the amount of spam images in a channel and want to minimize the stupid GIF animations you can use the Slack command: /collapse

      It is almost comical how every modern utility has been re-invented multiple times.

      Except consuming so much CPU and RAM that buying an i9 with 32GB of RAM is sort of necessary to use Slack.

      Which I never understood since Discord runs perfectly fine consuming next to no resources.

      Of course, the IRC client consumes even less resources since it doesn't have to carry a full web browser with it, but hey.

      I'm not sure what Slack is doing, reimplemented polling sockets or something?

    9. Re:And re-invented over and over again ... by bobmagicii · · Score: 1

      "Though several mainstream services have ended support for IRC over the years" in my personal echo chamber, most of the people i know are getting tired of all the electron apps and going back to irc *shrug*

    10. Re:And re-invented over and over again ... by UnknownSoldier · · Score: 1

      Yes, I should have mentioned that Slack is a bloated resource hog.

      Probably because Slack is built with Electron

    11. Re:And re-invented over and over again ... by antdude · · Score: 1

      IRC is fast and not bloated. Slack and others are so bloated and slow. I'm old school. :(

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  6. Re:Old code never dies. Working code at least by tepples · · Score: 1

    It probably depends on how you define "based on". In any case, Slack isn't compatible with IRC at present, as the summary links to a story about Slack having shut down access to its service through IRC protocol.

  7. IRC and Usenet are why we don't need Facebook by mi · · Score: 5, Insightful

    IRC for "instant" communications among individuals and groups, and Usenet for public forums is why there is no need for Facebook, Twitter and other centrally-controlled systems so prone to censorship and similar abuses both by the commercial interests controlling them, and the governments able to twist the former's arms.

    --
    In Soviet Washington the swamp drains you.
    1. Re: IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0, Funny

      Actually, IRC is useless, a waste of time, and worse for people than even Skynet.

    2. Re: IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      go back to reddit pls

    3. Re: IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      Make me.

    4. Re:IRC and Usenet are why we don't need Facebook by ArchieBunker · · Score: 1

      Do IRC servers still require you to run ident?

      --
      Only the State obtains its revenue by coercion. - Murray Rothbard
    5. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      Usenet would be basically unusable if it received any sort of mainstream attention. It's just too open to abuse. It would also need a lot of work to make it a replacement for Facebook etc.

      As for IRC, I don't even remember that shit, it was like 20 years ago I last touched it. But I suspect it's just about the same story.

    6. Re:IRC and Usenet are why we don't need Facebook by SantiagoMcRib · · Score: 1

      He didn't say the "I" in "IRC" stands for instant, he said that IRC is for instant messaging and usenet is for forum posting and anything built on top of those platforms, or extending that base level of functionality is being used as a tool for censorship or data harvesting.

      Maybe the real dumbass is the guy who can't fully parse through sentences before launching into his pedantic ranting?

    7. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      Require? No. They will supply a 'guessed' ident if you aren't.

    8. Re:IRC and Usenet are why we don't need Facebook by jellomizer · · Score: 1

      Except the fact that IRC and Usenet was like getting an open firehose of information especially on popular boards. Social Media you just get a garden hose, where can control the nozzle.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    9. Re:IRC and Usenet are why we don't need Facebook by mi · · Score: 1

      Except the fact that IRC and Usenet was like getting an open firehose of information especially on popular boards

      How is that a problem? You have — and always had — the tools necessary to filter this and, if a particular server's policy didn't suit you, you could switch without changing the interface(s) and losing the associations, contacts, and the audiences.

      --
      In Soviet Washington the swamp drains you.
    10. Re:IRC and Usenet are why we don't need Facebook by ljw1004 · · Score: 1

      IRC for "instant" communications among individuals and groups, and Usenet for public forums is why there is no need for Facebook, Twitter and other centrally-controlled systems so prone to censorship and similar abuses both by the commercial interests controlling them, and the governments able to twist the former's arms.

      I loved Usenet. But I don't think it would ever scale to the quantity of data (basically, videos) that's posted to youtube or facebook or twitter.

    11. Re:IRC and Usenet are why we don't need Facebook by CaptainDork · · Score: 1

      No.

      IRC ans Usenet had major problems.

      There was no censorship, which made them useless as tits on a boar hog, they were very awkward to use. The new kids on the block have GUI and dancing bunnies.

      Also, both of those platforms were so ridden with viruses (pre-malware vandalism) that users were scared to click on anything.

      When Compuserve showed up we all evacuated the IRC and Usenet spaces.

      What, precisely, did IRC and Usenet offer as a firewall against advertisement, government snooping and manipulation, and trolling?

      Nothing.

      That's the state of the art today with Facebook and Twitter, and all the rest.

      --
      It little behooves the best of us to comment on the rest of us.
    12. Re:IRC and Usenet are why we don't need Facebook by mi · · Score: 1

      But I don't think it [Usenet] would ever scale to the quantity of data (basically, videos) that's posted to youtube or facebook or twitter.

      Stipulating for the sake of argument, this would be a bad thing, why wouldn't it?

      By Moore's Law, our computers have become 65534 times more powerful than they were 24 years ago (in 1994). Facebook et al themselves are demonstrating, the hardware and the network connectivity are there — as you say. Why wouldn't servers talking an open protocol with each be able to do it? SMTP-servers can — e-mailing videos is "totally a thing" today — why wouln't NTTP-servers not be?

      --
      In Soviet Washington the swamp drains you.
    13. Re:IRC and Usenet are why we don't need Facebook by mi · · Score: 2

      There was no censorship, which made them useless

      There was some censorship — some groups were moderated, the moderators chosen by mutual consensus. The consensus was not binding on the non-consenting, however, and so could not itself become too abusive.

      both of those platforms were so ridden with viruses (pre-malware vandalism)

      Totally not a problem today, is it?..

      What, precisely, did IRC and Usenet offer as a firewall against advertisement, government snooping and manipulation, and trolling?

      What they offer is the diversity. Standing up your own IRC or NNTP server was and remains trivial. The like-minded could join your network with their own servers, carrying your channels and/or newsgroups. The early Internet's optimistic promise of "routing around censorship" would hold...

      Now, try standing up your own Facebook...

      --
      In Soviet Washington the swamp drains you.
    14. Re:IRC and Usenet are why we don't need Facebook by nnet · · Score: 1

      whats the fqdn of your nntp and irc servers?

    15. Re:IRC and Usenet are why we don't need Facebook by CaptainDork · · Score: 1

      You make good points and I didn't say the current crop of trash was better at security.

      However, I take issue with:

      Standing up your own IRC or NNTP server was and remains trivial. The like-minded could join your network with their own servers ...

      I'm looking at my Facebook Friends list and none of them would understand WTF you're talking about.

      As you know, social media evolved from klutzy BBS through IRC and Usenet out to Compuserve and AOL, to Myspace, Facebook, Twitter, and all the rest of actual useful shit.

      However, the DNA is very similar for all the above.

      All those softwares are leaky and always will be.

      --
      It little behooves the best of us to comment on the rest of us.
    16. Re:IRC and Usenet are why we don't need Facebook by 0100010001010011 · · Score: 1

      I don't think it would ever scale to the quantity of data (basically, videos)

      It already has and does. I have yet to see full 50GB+ BlueRay rips posted to FB.

    17. Re:IRC and Usenet are why we don't need Facebook by 0100010001010011 · · Score: 1

      GPG signing and/or encryption.

    18. Re:IRC and Usenet are why we don't need Facebook by CaptainDork · · Score: 1

      You know what that means and I know what that means, but no one on my Facebook Friends list has any idea what that means.

      Just as we moved from assembly (extremely difficult) out to the higher-level languages for a reason, so did we grow the social platforms to include the Gentle User.

      --
      It little behooves the best of us to comment on the rest of us.
    19. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      has and does since like, 1997. Anyone remember the yenc wars in alt.binaries around 2000?

    20. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      It's not guessed, it's supplied by the client. Ident is a completely useless protocol now a days. (And has been for a very long time, as soon as SLIP/PPP connections became common place as opposed to dialing into a shell).

    21. Re:IRC and Usenet are why we don't need Facebook by ljw1004 · · Score: 1

      [I don't think it would ever scale to the quantity of data (basically, videos)]

      It already has and does. I have yet to see full 50GB+ BlueRay rips posted to FB.

      The upload rate to Youtube I saw for last year was 270 terrabytes/day with retention period of forever, compared to usenet daily volume of 27 terrabytes/day last year with retention period of 4 years. You reckon usenet could handle an order of magnitude more than it currently does?

    22. Re:IRC and Usenet are why we don't need Facebook by gr8dude · · Score: 1

      The comparison is not fair.

      One doesn't need to know how an IRC server works in order to use it. You can create a friendlier client GUI and thus lower the entry barrier so even the folks on your Facebook list can use it with ease.

      Yes, the OP mentioned setting up one's own servers, but only a fraction of those on IRC are responsible for running the infrastructure - the others are just people who want to chat.

      In my area, back in the days, a lot of people just said "mirc" when they referred to chatting online. To them, it was not an IRC server, not a protocol, not a network - they didn't care. It was all about the "pacman-like" icon of a particular client that happened to be popular. So, one could argue that IRC is not only for geeks.

    23. Re:IRC and Usenet are why we don't need Facebook by CaptainDork · · Score: 1

      One could argue, however, that IRC is a vacant lot.

      No party, no ice and no crowd.

      --
      It little behooves the best of us to comment on the rest of us.
    24. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      Your "forever" might be a tad optimistic. Social structures die or change priorities. Especially private companies.

    25. Re:IRC and Usenet are why we don't need Facebook by Highdude702 · · Score: 1

      But the liberals want censorship, therefor IRC is bad.

    26. Re:IRC and Usenet are why we don't need Facebook by Highdude702 · · Score: 1

      Sounds like you need smarter Facebook friends, however them being Facebook friends.... I think there may be a trend here..

    27. Re:IRC and Usenet are why we don't need Facebook by CaptainDork · · Score: 1

      Why would I need smarter Facebook friends?

      Sharing is a simple mouse click, and I get cat videos.

      You aren't smart about this shit -- you're just experienced.

      I certainly would not add you as a Friend.

      And I wouldn't "server-up" to connect with you.

      Your experience does not impress me.

      --
      It little behooves the best of us to comment on the rest of us.
    28. Re:IRC and Usenet are why we don't need Facebook by mea2214 · · Score: 1

      ... compared to usenet daily volume of 27 terrabytes/day

      Did I read that correctly? I thought Usenet was pretty much dead. Many very popular newsgroups, like rec.sports.baseball, that received 1000+ posts/day back in the day were completely empty as of a couple years ago.

    29. Re:IRC and Usenet are why we don't need Facebook by ljw1004 · · Score: 1

      [usenet daily volume of 27 terrabytes/day] Did I read that correctly? I thought Usenet was pretty much dead. Many very popular newsgroups, like rec.sports.baseball, that received 1000+ posts/day back in the day were completely empty as of a couple years ago.

      I got the number from https://en.wikipedia.org/wiki/... -

      Much of this traffic increase reflects not an increase in discrete users or newsgroup discussions, but instead the combination of massive automated spamming and an increase in the use of .binaries newsgroups

    30. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      So you're reinventing yourself as a 72 year old wisecracking retiree who's deeply interested in social media, Chris?

    31. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      So you're saying that IRC and Usenet would have been great if it weren't for all those 15 year old boys who were the prime reason for the DMCA?

      I mean, when I was in high school my friends and I regularly shared LPs and CDs. And we all had tape decks. Once we were gainfully employed we bought our own copies. Even when we were trading LPs we knew it was stealing. Once the Internet made album sharing and mix tapes a global phenomenon it was pretty clear that a decentralized system wasn't going to work. Just because 15 year old boys don't understand theft and ownership.

    32. Re:IRC and Usenet are why we don't need Facebook by CaptainDork · · Score: 1

      I don't know what your point is, so I'll offer one of my corollaries:

      When anything is digitized, it enters the public domain by default. © 2018 CaptainDork

      --
      It little behooves the best of us to comment on the rest of us.
    33. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0
    34. Re:IRC and Usenet are why we don't need Facebook by Anonymous Coward · · Score: 0

      Did anyone else read that as "I'll offer one of my coronaries" and do a double-take?

  8. Server-side chat history and attachments by tepples · · Score: 4, Insightful

    For some use cases, tne big advantage of Skype, Slack, HipChat, Discord, and other web-based functional clones of IRC over IRC itself is that they store chat history on the server side. This lets a user see messages that were sent to a channel while the user was offline. It's as if an IRC server had built-in functionality equivalent to that of a bouncer, except that each user doesn't have to lease a VPS on which to run ZNC. The major IRC networks couid offer a built-in bouncer to compete with proprietary web-based chat, but they don't.

    Another is that web-based chat allows uploading attachments. IRC has traditionally used pastebins and filedrops for this. The major IRC networks couid operate pastebin and filedrop services for their users to use, but they don't.

    1. Re:Server-side chat history and attachments by Anonymous Coward · · Score: 0

      This lets a user see messages that were sent to a channel while the user was offline.

      Used Discord a tiny bit. All that feature seemed to do what turn the chat into more of a message board.

    2. Re:Server-side chat history and attachments by tepples · · Score: 1

      I agree that in theory, chat with server-side history is functionally to a message board. Some communities prefer chat with history because history allows users in less populous (and often less economically privileged) time zones to catch up. They prefer chat with history over a message board primarily for two user experience reasons:

      Lighter chrome per message User interface elements are smaller than those of phpBB, Slash/Rehash, and other popular message board software. Slash and Rehash, for instance, add two lines (subject and byline) above each comment and one line ("Reply to This | Parent | Share") below. Chat collapses these by default, except for the author's name and an optional timestamp. This encourages shorter messages that aren't quite as monolithic, encouraging a more conversational style as opposed to the more formal style of monolithic multi-paragraph message board posts. Real-time updates All users looking at a channel receive new messages instantly through a WebSocket without having to refresh the page.
    3. Re:Server-side chat history and attachments by dknj · · Score: 1

      Or, it's a chat system that is simply logged.

      I recall plenty of Epic and mIRC scripts that would fetch metadata from links ala slack and hipchat. I remember plenty of eggdrop bots which provided /fortune and /build functions. Nothing new, and is most probably what powers the backend of Slack!

    4. Re:Server-side chat history and attachments by tepples · · Score: 1

      Say I wanted to set up an IRC server that supports logging of messages and attachments, plus a server-side metadata bot so that posting a link in a channel doesn't cause a couple hundred users' metadata fetching scripts to all fetch metadata at the same time, thereby hammering the site with requests. Is there an IRC server distribution that supports all this?

    5. Re:Server-side chat history and attachments by Highdude702 · · Score: 1

      Iirc all servers can log, just not log and play back on connect that I know of. However since IRC is an open protocol there is nothing stopping someone from making a server that does just that and if you look around you may even find plugins for current servers that add those enhancements.

    6. Re:Server-side chat history and attachments by skids · · Score: 1

      For some use cases, tne big advantage of Skype, Slack, HipChat, Discord, and other web-based functional clones of IRC over IRC itself is that they store chat history on the server side.

      ...for other use cases this feature is actually now legally tenuous (GPDR and such) and may require, depending on the country of origin of the users and/or the service provider, staffing to remove any PII that ends up in the channel or exercise the "right to be forgotten".

      So if they cannot already, I'd expect these protocols to make that feature optional.

    7. Re:Server-side chat history and attachments by tepples · · Score: 1

      I don't see how the law would differ between logged chat and a message board. For example, would Slashdot be required, and would Slashdot be able, to handle an erasure request from a user?

    8. Re:Server-side chat history and attachments by Anonymous Coward · · Score: 0

      You mean disadvantage. If you're not part of the chat, why do you need a searchable indexed log of everything ? Right, bots. Discord has you covered.

      It is - or at least was - generally considered bad taste to log chats on IRC. IRC as serivce is _bullet proof_. Seriously, it's withstood attacks, hacks, and rouge servers for now three decades. What hasn't really kept up are the clients and dissinformation about what IRC even is. Try having a persistant connection with any other medium while you roam between the office and home. You're luckly if your connection remains for 10seconds after going offline.

      Kids today seriously have no fucking clue nor care.

      Source: Retired EFNet oper.

    9. Re:Server-side chat history and attachments by tepples · · Score: 1

      It is - or at least was - generally considered bad taste to log chats on IRC.

      Was. I get the impression that since EFnet's popularity peak, many chat communities have become more open to logging as a way of allowing people in less privileged time zones to participate.

  9. Limited Internet back then by Anonymous Coward · · Score: 0

    Back then my only way to access the Internet was via packet radio. 1200bps half-duplex.

    Slow as hell but watching those packets back then in DOS NOS was how I learned how networking, protocols, and the Internet works.

  10. QBD by rilister · · Score: 2

    ... and surely there's no better way to celebrate than browsing QDB: the best of IRC. One of the funniest things I've ever read on the internet. Captures the unique blend of genius and idiocy on IRC
    http://www.bash.org/?top

    --
    'This writing business. Pencils and what-not. Over-rated if you ask me. Silly stuff. Nothing in it' - Eeyore
  11. No thanks, I'd rather pay Slack in perpetuity. by Anonymous Coward · · Score: 0

    No thanks, I'd rather pay Slack in perpetuity. /s

  12. slack is old by Anonymous Coward · · Score: 0

    I think slack and hipchat are old now, discord is the IRC of the month

  13. IRC: the good and the bad by Anonymous Coward · · Score: 4, Insightful

    IRC did a lot of things right, that more "modern" IMs do totally wrong. IRC is decentralized, and anyone can run a server. It's lightweight, and easy to use. It is an open protocol. It lets you use any client you want, not just some single Facebook-blessed one. It wasn't made to monetize your communication.

    However the core protocol needs end to end encryption. Not encryption where a multinational manages your private key "for" you, but true, E2E encryption. Not as some weird add-on that most people will never use, but by default. This is to keep Zuckbook style snooping away. It needs better protection against malicious actions. It needs some more modern features like presence.

    At the core, it is what the internet should be: decentralized and put power in the hands of users, not advertisers and data scrapers.

  14. IRC's Legacy by Only+Time+Will+Tell · · Score: 1

    Without IRC, how would have I gotten all those warez...er...I mean chat with friends?

  15. Congrats! by 93+Escort+Wagon · · Score: 4, Funny

    /me slaps Whipslash with a wet trout

    --
    #DeleteChrome
    1. Re:Congrats! by Highdude702 · · Score: 1

      I think you meant Large Trout.

    2. Re:Congrats! by 93+Escort+Wagon · · Score: 2

      I hung out on Undernet - we did things differently.

      --
      #DeleteChrome
    3. Re:Congrats! by Highdude702 · · Score: 1

      Yea that's where I was "raised" so to speak, warezdk and some others is where I frequented. But that's actually a default in Mirc since about 1994

  16. Lololol irc lolol by Anonymous Coward · · Score: 0

    Haha granpa go shit in diapers haha

    1. Re: Lololol irc lolol by Anonymous Coward · · Score: 0

      Youâ(TM)ll be shitting in diapers someday too buddy, if youâ(TM)re lucky lol lol haha

  17. Re: Old code never dies. Working code at least by Anonymous Coward · · Score: 0

    There's nothing superior about it. Case closed.

  18. Re: Old code never dies. Working code at least by AlanObject · · Score: 4, Insightful

    I just don't get it.

    Unfortunately if you work on outgoing business you end up using a lot of different communication utilities. It isn't just Slack, but over the past several years I got involved with companies and standards-setting bodies that use it. So if you want to be plugged into the real-time communications of that company or group, you have to use it.

    But that isn't really different from other software -- on this Mac I am typing with I also have to have Skype, GoTo Meeting, WebEx, Zoom, and a few others I forget the names of until someone calls a meeting. If you ask any engineer on the call why they use it they just shrug and say "that's what our company uses."

    To make matters worse many of the "your business in the cloud" type operations like Zoho try to get in the action as well. I think the Zimbra mail server (VMWare) also offers "collaboration" features that host chatrooms and IP calls. The only time I pushed back on using something is there was one from Asia that had a bad reputation for installing malware. I forget the name. I got the client to switch to WebEx for that call but who knows what the condition of their own systems are at this point.

    So to answer your question: there really isn't any big technical merit between them. Yeah some work better than others. Skype really fsked themselves up but since it is Microsoft you will still have to use it. What counts is marketing and market share. No real mystery.

  19. Best feature by religionofpeas · · Score: 4, Funny

    IRC's best feature was the automatic translation of passwords to a bunch of asterisks.

    1. Re:Best feature by Anonymous Coward · · Score: 1

      It works here too... hunter2

    2. Re:Best feature by SantiagoMcRib · · Score: 3, Funny

      What did you say? All I see is *******

  20. 20 years ago I met my wife on IRC by Anonymous Coward · · Score: 3, Interesting

    Met my wife on DALnet's #England channel 20 years ago when I was in the UK and she was in the USA, we now live in the USA with our kids, that channel resulted in a lot of people we personally know getting married, so who needs Facebook and Tinder.

    1. Re: 20 years ago I met my wife on IRC by Anonymous Coward · · Score: 0

      A cheerful post in the usual mire!
      Where do I click "Like" ? ;-)

    2. Re:20 years ago I met my wife on IRC by Anonymous Coward · · Score: 0

      21 years ago, for me. I met her on #disney on Undernet. She and I moved from Pennsylvania and California respectively, to Ohio. Happily married 14 years. We haven't been on IRC in many years, but are still friends with a few from the old channel on Facebook.

  21. End-to-ends encryption by tepples · · Score: 1

    However the core protocol needs end to end encryption. Not encryption where a multinational manages your private key "for" you, but true, E2E encryption.

    Some chat services support end-to-end (E2E) encryption for one-to-one chat but not group chat. The point of the latter is to broadcast a message to all other users of a channel. How would end-to-ends (plural) encryption work?

    It needs some more modern features like presence.

    IRC protocol already has presence support, which many clients expose as the /away command. Though this doesn't include "offline" status at the protocol level, an IRC server could in theory implement "offline" as a subset of away status by providing a bouncer for all users of the server to use.

    1. Re:End-to-ends encryption by Anonymous Coward · · Score: 0

      Some chat services support end-to-end (E2E) encryption for one-to-one chat but not group chat. The point of the latter is to broadcast a message to all other users of a channel. How would end-to-ends (plural) encryption work?

      Probably the same way it works in PGP: a symmetric key is encrypted with the keys of all the recipients of the message, and the message itself is encrypted with what symmetric key.

      Then every person participating in the chat can send and receive, but the whole chat cannot be snooped by outsiders to it.

      Of course someone could let a snooping party in, but there can be no protection from that. The multi-party encryption is still effective to prevent FB type mass scraping. You don't let FB be a party to your group chat.

    2. Re:End-to-ends encryption by tepples · · Score: 1

      Until you get to a channel with 200 or 500 people in it, and the size in bytes of the set of asymmetrically encrypted copies of the symmetric key for each message greatly exceeds the size in bytes of the message. I've seen channels that big in both IRC and Discord.

      And if a new user joins and a channel's moderator accepts the new user's request to be read in on the channel's history, how does the new user's symmetric key get added to all the existing messages? By decrypting the symmetric key of each message using the moderator's private key and reencrypting it using the new user's public key? That could take a while.

      Furthermore, how does the user keep his key synchronized across two desktop computers, a laptop, and a tablet?

    3. Re:End-to-ends encryption by dknj · · Score: 1

      B L O C K C H A I N

    4. Re:End-to-ends encryption by Anonymous Coward · · Score: 0

      Until you get to a channel with 200 or 500 people in it, and the size in bytes of the set of asymmetrically encrypted copies of the symmetric key for each message greatly exceeds the size in bytes of the message. I've seen channels that big in both IRC and Discord.

      Fine. Have an option not to encrypt those if you want.

      That doesn't take away from its usefulness in the vastly more common case of a handful of people up through a few dozens. It doesn't take away from its use by groups of friends, to avoid being spied by Facebook-like entities.

      Why is it that on Slashdot, so many people think that just because something is not 100% perfect in 100% of the possible cases they can imagine, it must be useless?

      Furthermore, how does the user keep his key synchronized across two desktop computers, a laptop, and a tablet?

      This is already a solved problem. I already keep things synced across multiple devices. It is simply another file in the mix.

    5. Re:End-to-ends encryption by tepples · · Score: 1

      Why is it that on Slashdot, so many people think that just because something is not 100% perfect in 100% of the possible cases they can imagine, it must be useless?

      It may be a counterreaction to a delusion commonly observed among marketing departments that if something is 100% perfect in one case, it must be perfect for all cases. I personally was trying to help characterize the limits of end-to-ends encryption so that people considering it could see under which conditions it is practical.

      I already keep things synced across multiple devices. [The keypair for end-to-end encryption] is simply another file in the mix.

      Does this work for both web-based and non-web-based chat clients? I thought web applications, such as clients for chat services, couldn't read arbitrary "files" from your device for security reasons, and you didn't want to upload your private key to the server in order to prevent the server from compromising your encryption. Once you have synced the file containing a keypair, how do you get it into the JavaScript-based chat client's local storage? Or is it generally better to drop a web-based client in favor of an installable native client, provided one even exists for a given pair of chat protocol and client platform?

    6. Re:End-to-ends encryption by Anonymous Coward · · Score: 0

      Some chat services support end-to-end (E2E) encryption for one-to-one chat but not group chat. The point of the latter is to broadcast a message to all other users of a channel. How would end-to-ends (plural) encryption work?

      For an example with many IRC-like features see Tox.

    7. Re:End-to-ends encryption by Anonymous Coward · · Score: 0

      Does this work for both web-based and non-web-based chat clients?

      IRC has nothing to do with the web. It is a separate protocol entirely. In fact, it is older than the web.

      I'm sure somewhere somebody has built a web based client for IRC, but they are virtually unused and are irrelevant to anything. Not even to mention you can sync their files too if you want. The vast majority of people are using native IRC programs.

    8. Re:End-to-ends encryption by Anonymous Coward · · Score: 0

      There was IRC based chat on the web a long time ago - public chat rooms, that you could join using an IRC client if you even knew what IRC is.

      There was a site famous for these chatrooms in my country, it also offered webmail but was closed down a decade ago. That's a bit sad. We called that "chat".
      Back then you only needed a nick name, or not even that if you were so lazy as to not set one and be called "user000027" or similar. I want my Internet back :)
      And, native clients are now called Android apps and are a prison for the user.
      - I don't want a google account
      - I don't want to give out my phone number
      - I don't want to give out my name
      - I don't want to enter my CC number

      And why don't proprietary fad chat apps provide e-mail service to their users? Dinosaurs Microsoft, Yahoo and Google still do.

    9. Re:End-to-ends encryption by tepples · · Score: 1

      Correct. IRC was intended for installable native clients. But as I understand it, IRC also originated in a time when most computers connected to the Internet had a compiler already installed, or at least allowed execution of unsigned binaries added by a user, as opposed to being cryptographically locked down to those apps hand-picked by the computer's manufacturer. That makes installable native clients slightly more practical than in a 2018 scenario where one wouldn't want to launch without iOS support.

  22. Freenode still huge for F/OSS project development by TheDarkener · · Score: 1

    I work with a small handful of open source project teams and Freenode is still the hub that most F/OSS developers use to communicate with each other. I head a project called "Cool Mic" (#coolmic, a livestreaming audio client for Icecast) and I've worked with the two primary developers for years. I've never met them IRL (they live in Germany, I live in California). I consider them good friends, along with the people in #icecast. My local LUG has a pretty active IRC channel as well.

    I've seen countless bugs get squashed, users get instant support, and friends be made on IRC over the past 20 years and, at least with Freenode, it shows no signs of slowing down. If anything it's getting more popular. It speaks to the distributed nature of the Internet and how distribution (separate, independent channels for instance) truly serves to strengthen the network as a whole. Huge monolithic services like Facebook and Twitter only take away from what makes the Internet robust and resilient IMHO.

    --
    It is pitch black. You are likely to be eaten by a grue.
  23. How does DCC SEND traverse NAT? by tepples · · Score: 1

    Skype, Slack, Discord, and other proprietary web-based chat platforms allow uploading attachments even if your device is behind network address translation (NAT).

    DCC requires the sender to be able to receive incoming connections, which is not true of a device behind NAT. UPnP is supposed to let applications configure a router to punch a hole in the NAT, but it's often disabled for security reasons, and it doesn't work anyway across a NAT operated by your ISP (called a carrier-grade network address translation or CGNAT).

    Or are you referring to use of a reverse DCC SEND to let a sender behind a NAT send a file to some proxy, from which a recipient behind a different NAT retrieves the file with a normal DCC SEND? If so, which if any IRC networks make such a proxy available to their users?

    1. Re:How does DCC SEND traverse NAT? by AndroSyn · · Score: 1

      Well the DCC protocol itself isn't actually a part of the IRC protocol itself. It's an informal add-on to the protocol, that involves the clients speaking to themselves.

      As far as traversing NAT goes, unless you have a specific protocol handler for IRC, like you would for FTP, it doesn't. If you had a file send protocol that was based on UDP, you could use IRC as a replacement for a STUN server. However, that is a completely client side issue, its not something the IRC protocol itself addresses directly, maybe it should though.

  24. Re: Old code never dies. Working code at least by Anonymous Coward · · Score: 0

    "The only time I pushed back on using something is there was one from Asia that had a bad reputation for installing malware."

    Was it WeChat?

  25. IRC beat Napster to the punch by Anonymous Coward · · Score: 0

    Loved me some IRC back in the day! I think it was back in 97 when I got on #undernet and discovered some MP3 leeching rooms. "MP3 Borg", I think it was called. I downloaded every song I ever wanted by the time Napster came out.

  26. I agree, Mi dumbass doesn't know IRC for shit by Anonymous Coward · · Score: 0

    "Instant" relaxing chair, according to dumbass Mi. Maybe it's the langrage ballier?

  27. Dr Short Circuit by Anonymous Coward · · Score: 0

    The surname of the programmer (Oikarinen) means 'short circuit' (although fortunately just a small short circuit as it's in diminutive). Quite a fitting name for such gentleman and inventor. Thank you for all the wasted hours!

  28. Re: Old code never dies. Working code at least by Highdude702 · · Score: 1

    That was it.

  29. Re: Old code never dies. Working code at least by epiphani · · Score: 4, Insightful

    IRC as a protocol and software stack is generally crap. While it was functional, a huge swath of IRC would have to be completely rewritten - including the underlying foundations - to turn it into a modern Slack or similar service. Honestly, it would be far easier to start from scratch than to base it on IRC. While a few things could be learned from how IRC was built, I wouldn't use that code as a base for anything.

    Source: Me. Maintainer of Bahamut IRCd from 2001-2018.

    --
    .
  30. Re: Old code never dies. Working code at least by UnknownSoldier · · Score: 1

    Because Slack is the latest "shiny" / fad.

    "Benefits" include:

    * When you are offline DM (Direct Messages) are emailed to you
    * Chat saved server-side
    * Multi-Factor Authentication
    * Threads (can reply to someone and start a thread)
    * Multi-line code snippets using ```...``` and basic MarkDown
    * Editing of messages
    * Preview of links
    * Custom emoji

    Yeah, most of those are fluff.

    Now if there was only an auto-kick clueless noobs who can't fucking read the pinned messages and have to use @here in a channel of 500+ people ...

  31. FTFY by Anonymous Coward · · Score: 0

    For the last several years, Oikarinen has been working at Google, overseeing the development of several personal data collection services.

    At Google, "communication" is never just communication.

  32. By Geeks For Geeks. by westlake · · Score: 1

    IRC for "instant" communications among individuals and groups, and Usenet for public forums is why there is no need for Facebook, Twitter and other centrally-controlled systems so prone to censorship and similar abuses.

    Let's be honest here. IRC and Usenet clients were --- and in many ways still are --- painfully arcane and riddled with geek jargon. Microsoft Chat, the IM messaging and chat rooms of online services like AOL were proof that ift didn't have to be this way.

    1. Re:By Geeks For Geeks. by mi · · Score: 2

      it didn't have to be this way.

      Exactly. It didn't have to be that way — and whatever shortcomings there were, weren't due to any inherent deficiencies of the protocols.

      Instead of throwing it all out, we could've improved the clients. Indeed, the NNTP-client still built into Thunderbird is not any less friendly, than the rest of the application. Likewise, Pidgin and other modern instant-messengers offer perfectly decent IRC implementations.

      What makes it "by geeks for geeks" is the absence of marketing — there is no single entity to offer Apple, for example, a large sum of money to put an IRC-client on every iPhone. There are no other problems...

      --
      In Soviet Washington the swamp drains you.
    2. Re:By Geeks For Geeks. by Highdude702 · · Score: 1

      That microsoft chat program you speak of, was just an IRC client.

  33. Re: Old code never dies. Working code at least by laffer1 · · Score: 1

    It's basically IRC with a few extra features, better file transfer, audio chat/screen sharing, easy ways to share code snippets and lack of compatibility with all operating systems. For people that don't know IRC, it's amazing.

    It also supports bots and integration hooks that tie into things like jira, jenkins and other tools.

  34. Pretty sure I did it thru NAT by Anonymous Coward · · Score: 0

    Pretty sure I did it thru NAT (thru a home Linksys firewall using NAT changing my online IP address to INTERNAL 192.168.x.x one, non-outward routeable - which was bridged to override comms control vs. default ISP modems)!

    HOWEVER, in fairness? Hey - but don't quote me on that, it's been a LONG TIME since 1994-2001 when I was on IRC & I can't remember EXACTLY what type of equipment I used @ the end (2001, though I am pretty sure it was cablemodems & 1994-1998 I used dialup, 1999 was DSL, but 2000 onward? Can't recall FOR SURE, but again - pretty sure it was CABLEMODEMS via timewarner & doing bridges on a 'firewall' in hardware then).

    * What brought NAT up ? Was it in your conversations earlier with others?? I'm not sure so I am asking (don't have time right now to look either so I will just ask & look later when I get back here).

    APK

    P.S.=> I don't know WHY you bring up NAT (unless you'd like to point out this is not "mid 1990's TRUE phone modems" in use & cable/fiber/DSL connections via 'cablemodems')... apk

    1. Re:Pretty sure I did it thru NAT by tepples · · Score: 1

      it's been a LONG TIME since 1994-2001 when I was on IRC

      Back when IRC was still popular, most Internet-connected households had only one PC connected to the Internet at a time, and there weren't enough Internet users in IPv4 address-poor countries to make CGNAT a necessity. Nowadays, those are no longer the case quite as often.

      What brought NAT up ? Was it in your conversations earlier with others??

      Yes. For example, Bert64 reports that all home ISPs in Myanmar use CGNAT.

    2. Re:Pretty sure I did it thru NAT by Anonymous Coward · · Score: 0

      I remember, early 2000s we had an ADSL modem which made use of PPPoE - weirdly, even though it was an ethernet modem, you used it like a regular modem pretty much [unless you flashed the firmware to the "Pro" version which made it a router].
      Those less lucky had an ADSL modem that connected through USB and had a rather poor reputation. So, years approx. 2001-2004 we had an internet boom in my country mostly made of users both on broadband and directly connected to the Internet. So I never knew that DCC SEND would cause problems.

      I did "make" my own router by using software on a Windows desktop PC. That's where I have an anecdote. IRC bots would kick me from channels, if we were two users joining it at the same time. The bots were guarding against trolls joining the channel twice from the same PC, apparently. It wasn't too frequent, not a big deal.
      Playing Counterstrike on the Internet wasn't a problem, at least if you set the upload rate in the console (upload was only 128 kbps).
      Reaching a Counterstrike game (or Half-Life etc.) on my LAN from outside was possible if you set port redirection in the router software but of limited use, like two external players again because of the upload. But it was fun. We didn't have the dedicated software just the game. I don't trust the modern games to let me do that.

  35. The value of a distribution by tepples · · Score: 1

    Is there an IRC server distribution that supports all this?

    if you look around you may even find plugins for current servers that add those enhancements

    Hence why I asked "distribution".

    The benefit of Skype, Slack, Discord, and HipChat is that someone without experience in looking around doesn't need to learn how to look around for a combination of server and plug-ins. To many organizers of communities of people on the Internet, the benefit of everything already being there outweighs these chat platforms' proprietary character. If someone were to come up with a solid answer for "Which server and which plug-ins?" to which I could refer people, there wouldn't be quite so much of a need for Skype, Slack, Discord, and HipChat.

    1. Re:The value of a distribution by Highdude702 · · Score: 1

      I don't include relying on other peoples infrastructure as a benefit.

  36. Re: Old code never dies. Working code at least by Anonymous Coward · · Score: 0

    So if you want to be plugged into the real-time communications of that company or group, you have to use it.

    No thanks.

  37. Almost any chat service... by Anonymous Coward · · Score: 0

    Has attempted to reinvent IRC in the past.

    Let IRC rule supreme.

  38. "CURE" for DCC/NAT's in bookmarks/favs... apk by Anonymous Coward · · Score: 0

    See subject: I had to port forward 113 & open a range for DCC to work over Linksys NAT 'firewall' modem in bridged config (took over ISP cablemodem) per https://forums.mirc.com/ubbthr...

    * "There ya go" - the "CURE" for DCC over NAT!

    (SO, if you EVER need it? Try that - I recall it working for me (port 113 stuck out bigtime in my mind & it's been a LONG time since I had to do it, as I don't use IRC now (not for ages, since 2001)).

    APK

    P.S.=> You made me curious about it so I looked into my favs/bookmarks "IRC" folder & "there she was" from LONG ago... apk

    1. Re:"CURE" for DCC/NAT's in bookmarks/favs... apk by tepples · · Score: 1

      Many ISPs' networks are structured in such a way that "port forward 113 & open a range" is not enough. See the post by Bert64 that I linked above and "Carrier-grade NAT" on Wikipedia for background. And even on those ISPs that do allow forwarding a port, a customer may not understand how to do so.

  39. netsplit by Anonymous Coward · · Score: 1

    I think I missed half the comments.

  40. Is that zero cool? by mydots · · Score: 1

    At first glance I thought it was a scene from hackers 2.0.

  41. Rodneys Ethical services by Anonymous Coward · · Score: 0

    Hacking into mobile phones is a walk in the park, say Rodney the experts. All it takes is a single SMS sent from the hacker's phone, to break into a phone and gain total control over it without touching the target remotely, including listening to recordings of phone conversations, reading text messages even accessing passwords and all social medias, Whatsapp Facebook etc. RODNEY the experts say that mobile is the new playground for hackers as these devices are easier to break into than PCs, and consumers pay less attention and are tardy when securing their phone. Contact him today on his Gmail Username: prohacker2177 @ gmail com or whatsapp: +16313154546 Good luck to everyone who wanna work with him and put a stop to all cheating spouse nightmare.

  42. I miss MindAlign... by gosand · · Score: 1

    Back in 2008ish we started using MindAlign at a large bank I worked at, where we had a distributed team. It was great! I'd used IRC in the past and it was similar but I think better for what we were doing. I heard that MS had purchased them, and incorporated their code into MS Lync Group Chat, which we then started using because it was MS, so - Corporate Approved! :|

    Then MS completely crapped on that product and killed it, and now there is MS Teams which is their super-integrated-with-O365 garbage solution to a problem they already had solved!

    So where I work now we can't use Slack (not corporate approved) so we are stuck with what we fumbled around with before MindAlign way back - regular IM but no searchable logged history. It's a combination of Skype for Business and regular Skype, because we have to chat with contractors who don't have corporate accounts.

    --

    My beliefs do not require that you agree with them.

  43. I am APK the LORD of HOSTS by Anonymous Coward · · Score: 0

    I am APK the great "LORD of HOSTS", a.k.a. AlecStaar from ArsTechnica or Alexander Peter Kowalski.

    See subject & APK Hosts File Engine 2.0++ 64-bit for Linux h t t p : / / I . a m . a . f u c k i n g / a s s h o l e . r e t a r d . z i p (remove spaces between characters & download).

    I am the godlike creator of various GUI front-ends for other people's configuration files.

    Watch as I claim I win every argument when in reality I know I lost but that won't stop me from proclaiming my victory.

    When presented with facts I rebut them with wild speculations, false support, and out of context quotes

    All of my accomplishments revolve around me being proven to be an annoying spamming asshole

    See me be proud of my inability to be a functional adult

    Bask in my debilitating mental illness

    Hear me tell stories about me living large drinking miller lite in my ramshackle duplex with a roommate at age 54.

    Watch me spew some word salad because I can't string 2 words together in a coherent manner.

    I just don't understand why every site I post on everyone makes fun of me, it can't be because I am a shit stick but instead because they are all Ne'er-do-well SOYboy Jealous JOWIEs.

    Witness my descent into madness

    APK

  44. IRC for those with screen readers by Anonymous Coward · · Score: 0

    I use a screen reader (JAWS on Windows 7) to access my computer. Is there any good programs to interact with IRC that would play nicely with my screen reader? I've tried a couple, but either the screen reader can't determine what is important or reads the entire message history from start to finish on each screen update. Any ideas or help I missed?

  45. Re: Old code never dies. Working code at least by reanjr · · Score: 1

    And yet no protocol has been introduced since that actually solves the same problems. XMPP came close, but then died off with everyone's taste for XML.

    It's not that IRC is a super great protocol, it's that it's the only standard we've got. Extend the standard (I don't agree the fundamentals would have to change for Slack). Make a new standard. Use XMPP. Whatever. Just don't introduce another useless proprietary messaging protocol.

  46. APK just can't stop lying by Anonymous Coward · · Score: 0

    APK just can't stop lying
    Like how he claims the Chinese copied him but can't produce any evidence.
    How about when he states that hosts does port filtering but again can't backup his statement which was shown to be false.
    There is also his list of "experts" who support him but it turns out they don't say what he is claiming.
    This also ignores his out of context quotes he uses to lie by omission.
    The problem with APK is that his entire reputation is built upon the lie he told years ago that hosts is an effective security solution. It has been exposed numerous times as being a lie and when exposed APK fails to argue logically and instead will try to deflect criticism, change the subject, move the goal posts, return to a previously disproven statement, demand you prove you did better than his file concatenator, or just call people names. He will continue to lie by stating that he won or "dusted" you while failing to refute anything you said, will never provide real evidence, and generally try to dodge the issue.

    Face it APK is one of the most detested individuals here for good reason. When ever his poor behavior, awful logic, over statements, and horrendous writing are called out he has a fit and has done so for years across the internet. He is a spammer, and is an abusive insecure little man who is washed up and never amounted to anything. Until he produces actual verifiable facts supporting his case nothing he says should be taken seriously.

  47. ... to turn it into Slack? NO! THAT'S THE POINT!!! by Anonymous Coward · · Score: 0

    ... to turn it into Slack? NO! THAT'S THE POINT!!!

  48. Use a DMZ instead then... apk by Anonymous Coward · · Score: 0

    Use a DMZ instead then - it'd work & is VERY easy to do (& customers can LEARN NEW THINGS like DMZ or portforwarding).

    * IF I can do it, so can anyone else I hope!

    APK

    P.S.=> "Where there's a will there's a way" (epsecially if others have done it before successfully & document it well for you)... apk

    1. Re:Use a DMZ instead then... apk by tepples · · Score: 1

      Even a DMZ doesn't work if your ISP blocks incoming connections before they even get to your modem.

  49. Only evidence I need & nobody trusts you.. apk by Anonymous Coward · · Score: 0

    Who did it 1st: China or me? I did - dates are my proof http://theregister.co.uk/2017/... w/ the FACT China rampantly STEALS U.S. Intellectual properties & military secrets!

    * See subject: NOBODY TRUSTS YOU as you STALK ME by UNIDENTIFIABLE anonymous - real "trustworthy" you are, lol (not)!

    When you've done BETTER than I have in a ware that protects & speeds folks up online?

    THEN, they might (you never will though & you KNOW it JEALOUS "Lil' Jowie").

    Arstechnica = losers who stalked me (as you do now anonymously unidentifiably) to NTCompatible.com & Windows IT Pro magazine forums to their public dismay in Jeremy Reimer & Jay Little + Jarrett DeAngelis (who posts here on /. until I drove his ass off too) when their websites were REMOVED by their hosting providers in Shaw Canada & CrystalTech (for both email harassing me caught on a tracking ticket + stalking me & posting lies about me on them AFTER I destroyed them both PUBLICLY @ Windows IT Pro on Exchange Servers memory being freed UNHALTING them (which tells you Exchange is HEAVILY POINTER ORIENTED linked list driven, which leads to memory fragmentation that CAN halt a serverware)).

    Jay Little the "self-proclaimed 'EXCHANGE EXPERT'" HAD TO CONCEDE IT from MICROSOFT'S OWN DOCUMENTATION proving it FOR me there (where they as usual stalked me AS YOU ARE NOW)

    Thor SCHMUCK?

    Ask him WHY his false accusation of an old ware of mine was 1st taken down to NO threat & CA sold off the SHITTY antivir he sold (as a paid pawn of theirs) & they are GONE, done. dead... lol!

    Lookup "CA Accounting Scandal" on Google - scumbags & THEIR BIRDS OF A FEATHER just go down vs. me everytime!

    APK

    P.S.=> TONS of Security experts KNOW blacklists work (no questions asked) & 3 things show I do it right:

    1st = User praise my hosts engine https://tech.slashdot.org/comm... (so much for ME being "detested" but I'm not here to win a popularity contest - just here to WIN so everyone does).

    2nd "ATTACKS" I GET (from UNIDENTIFIABLE ac as Elon Musk got https://tech.slashdot.org/stor... )

    3rd BEING IMITATED = "Imitation = sincerest form of flattery" https://linux.slashdot.org/com... JUST LIKE CHINA DID ME TOO... apk

  50. No, you're certainly not I... apk by Anonymous Coward · · Score: 0

    See subject: As you IMPERSONATE me proving you WISH you were me though, lol - poor imitation though but sincerest form of flattery!

    Despite YOU trying to "put me down" while impersonating me & in your other posts STALKING me (where I destroyed you w/ ease mind you)? Well - when YOU have done BETTER in software than I have? THEN, you can TALK talker.

    (Otherwise you're just JEALOUS "Lil' Jowie" doing your usual BLOWHARD hotair talking out your ASS!)

    APK

    P.S.=> The only "mockery" here is you w/ your OBSESSIVE stalking or impersonating me - you're the one descending into madness (can't blame you since I blow you away constantly, I can see you getting a "wee bit 'FruStRaTeD'" (w/ your constant FAILS vs. me, lol))... apk

  51. Answer 2 simple questions... apk by Anonymous Coward · · Score: 0

    See subject & answer: 1.) Do hosts stop threats served by hostname (the way threats are done most) by blocking them? Yes. 2.) Do hosts speed you up 2 ways in adblocking (preventing more infection/tracking/slowdown) & via hardcoded favorite sites resolving faster + protecting vs. dns down or redirect poisoned? Yes.

    My hosts program's the only 1 that does the latter @ TOP of hosts cached in RAM (for best performance) & only 1 of its kind on Linux/BSD in easy to use flexible configuration GUI form.

    (I also did that latter part LONG before the Chinese & 1st http://theregister.co.uk/2017/... )

    APK

    P.S.-> Have you done work that is that effective doing far more for far less faster in kernelmode speed (cpu priority) w/ less complexity with excess overheads & for exploit vs. solutions KNOWN to be security-issue riddled (like addons (souled-out to NOT work by default OR easily detected & blocked that are BYPASSABLE & EXPLOITABLE), DNS & Antivirus)? No... apk

  52. Re: Old code never dies. Working code at least by Kjella · · Score: 1

    IRC as a protocol and software stack is generally crap. While it was functional, a huge swath of IRC would have to be completely rewritten - including the underlying foundations - to turn it into a modern Slack or similar service. Honestly, it would be far easier to start from scratch than to base it on IRC. While a few things could be learned from how IRC was built, I wouldn't use that code as a base for anything.

    Is there such a thing as "the" IRC code, I was under the impression it was a protocol not an implementation. But in any case I think the DCC code would need a major workover. Or really any non-text case, today I'd probably go for JSON or XML, back then it was trouble enough with non-ASCII....

    --
    Live today, because you never know what tomorrow brings
  53. Re: Old code never dies. Working code at least by AndroSyn · · Score: 1

    I'd 100% agree with you that trying to turn IRC into something modern like Slack just doesn't make sense. I know I certainly wouldn't try doing it.

    Things like channels and nicknames, really don't work so well in modern contexts. The fact that it is an ephemeral medium, that if you're not connected to IRC, you don't have any chat history.
    Trying to use IRC on a mobile device is even worse, nothing like getting a ping timeout and not realizing it for a few minutes because you hit a dead zone. Then you disconnect/rejoin rinse and repeat.

    The one thing about working on an IRC daemon is that you learn a lot of lessons on how NOT to design a modern chat system.

    At least that's the viewpoint of this jaded ircd-ratbox coder ;)

  54. Re: Old code never dies. Working code at least by AndroSyn · · Score: 1

    Is there such a thing as "the" IRC code, I was under the impression it was a protocol not an implementation.

    It's both. There are many IRC daemons out there, most of them written in C, thats what the clients connect to. The protocol presented to the client tends to be mostly compatible across implementations, with various minor quirks here and there.

    But in any case I think the DCC code would need a major workover.

    As far as DCC goes, thats a client side protocol, that really doesn't involved the ircd at all beyond passing the messages between the clients exchange the IP/port info.

    Or really any non-text case, today I'd probably go for JSON or XML,

    One of the nice things about the IRC protocol itself is that it is rather fast to parse. You can pretty easily parse it with something like strtok(). Given the time period the protocol was designed, speed of parsing is very important. Especially since most IRC daemons single threaded event driven processes.

  55. Re: Old code never dies. Working code at least by Anonymous Coward · · Score: 0

    Oh hey, small world, still.

    IRCD was fun for awhile, but the underlying code did not scale as well as one might have wanted it to. It was created in a time when two geographical regions might have unstable/slow/oversubscribed pathways between them, so the "local server" that was part of a larger network was common. You don't see much of anything like that in modern services; at the very very minimum, all the details of such are now hidden from the end user. But back then... ugh. Netsplits and the channel takeovers they facilitated.

    Rakarra, maintainer of the by-then-creaky DALnet Dreamforge ircd in the late 90s. I had major IRC burnout right when I graduated from college, got a job, and became DALnet coding director. Things that don't go well together.

  56. True that: I agree but... apk by Anonymous Coward · · Score: 0

    See subject: I'd be like "it's time for a NEW ISP then", lol! Wouldn't surprise me as ISP's now handout modems where you can't do 2 things:

    1.) PORT FILTER

    2.) CHANGE DNS on modem itself

    (Bogus weakness for SECURITY on former & LATTER too but moreso on latter due to tracking dns requestlog side...)

    APK

    P.S.=> Nice "talking shop" w/ you tepples (though you're throwing in some "outlier" situations here, lol)... apk

    1. Re:True that: I agree but... apk by tepples · · Score: 1

      "Time for a new ISP" doesn't help if all the other home ISPs in the same city have the same dain bramage. Please reread the Bert64 comment I linked.

  57. You should have focused on DDOS protection instead by Anonymous Coward · · Score: 0

    lol @ dalnet..

  58. Re:IRC is dying, thank god by Highdude702 · · Score: 1

    So its like Twitter or Facebook, except anybody can be "The Man" not just one side of a political spectrum? Sounds better than both to me the way you describe it.

  59. BIG "IF" that tepples but... apk by Anonymous Coward · · Score: 0

    See subject: That's IF (pun intended) they actually ALL do that - it's dangerous to speak in absolutes man. I also NEVER read Bert64's link so you know. Perhaps I should (just to find out IF what you claim is being "universally instituted").

    * WHY would they filter out port 113 & 4999-5000 ports for? To help stop people exchanging files on IRC only?? I mean, I'm not saying it's NOT possible but pretty 'radical'!

    APK

    P.S.=> See subject again - can you PROVE "ALL" do that? ALL = a BIG word... apk

    1. Re:BIG "IF" that tepples but... apk by tepples · · Score: 1

      ISPs applying this technique filter out all incoming connections. The subscriber's modem doesn't even have a publicly routable IP address. Instead, the ISP assigns the subscriber an IP address in the reserved space 100.64.0.0/10 (as documented in RFC 6598), which is routable only within that ISP's network, and translates addresses within that range to a much smaller address space as packets enter and leave the ISP's network.

      And as Bert64 wrote, Myanmar is among the countries that have so few IPv4 addresses allocated to them that all ISPs have to run home users behind NAT in order to provide service. Say you have 16,000-odd IP addresses (a /18) but 10 million customers. The pigeonhole principle means you can't put each customer on a separate IP address. At a global scale, with 7 billion people and 4.2 billion IP addresses, you can't give everyone a unique address.

  60. Tepples I understand NAT... apk by Anonymous Coward · · Score: 0

    Tepples I understand NAT but as I said: Myanmar's an OUTLIER "exception to the general rule" compared to most locales which was my point. I'd wager most customers have options due to competition between ISPs in their given area.

    * In other words, I agree w/ you IN THAT INSTANCE (but it's only an instance/exception vs. most), given the 'constraints' your example (an outlier) has.

    APK

    P.S.=> Again, nice talking 'shop' w/ you... apk

  61. Re: Old code never dies. Working code at least by secretagentmoof · · Score: 1

    2001? noob.

  62. OMEMO atop IRC is a thing.... by Anonymous Coward · · Score: 0

    The problem is every client connecting to the channel has to use it and you need an introduction and periodic refreshes to ensure the channel contents can't be snooped.

    Hint: It doesn't protect you much better than SSL ,mandated from client to server and server to server. And it definitely doesn't protect you better than retroshare which itself is a mess but essentially does the sort of peer to peer decentralized security you are asking about, which requires far more memory and cpu time than most people might be willing to afford for all their possible contact lists.

    The channel history furthermore cannot be protected as you say because you either need a centralized bouncer, or each individual client having some/all of the channel history to replicate to reconnecting users which means third parties can get ahold of it just as easy if they can connect with one or multiple user accounts periodically, making it difficult to know your conversations/history have been compromised.