Comment by kristopolous

13 hours ago

If you look at "old" internet: fidonet telnet bitnet ftp fsp wais netnews whois++ gopher relaynet ... i mean irc is one of the only ones that is still used, and mostly as it was 35 years ago. Pretty impressive.

People love knocking on IRC but people are still on it, still using it...

HTTP is also still somewhat popular.

But, seriously, that got me curious. There are many protocols from that early era that are still with us today. NTP, DNS, SMTP, IMAP, BGP, SNMP, NFS, ICMP. If you allow the 1990's as counting as "old" we can add SSH and SSL, DHCP, LDAP.

Actually, its just inertia and lack of reliable forum hosting, the actual "killer app" that replaced volatile and unarchivable chat content, but no one learned from it and people flocked to Discord, which is even more hostile to archiving/scanning chat history.

  • I am starting to wonder is archiving or scanning history even possible with how hostile internet has become. Especially when so many tech companies will scan and download same content countless times without single care of damage or cost the cause...

    Just imagine hosting that history on your instance for users and then some vibecoder without care in his work starts scanning it automatically every 5 seconds just in case it might have changed...

    • > I am starting to wonder is archiving or scanning history even possible with how hostile internet has become.

      Future generations are going to be looking at a historical black hole.

Yeah, but the major upgrades for things like telnet and ftp were adding appropriate encryption layers and improved authentication to include things like certificates. IRC shoehorned those into the connections awkwardly but it's still not often mandatory and registration is painful.

Also usenet is still very popular but mostly used for file sharing.

  • Yes. usenet, however, used to be social media. It was like text-only reddit.

    • > Yes. usenet, however, used to be social media. It was like text-only reddit.

      Except, unlike Reddit, it wasn't centralized nor owned by a single corporation.

      Usenet users did not have to obey the rules and whims of any corporation and there was thriving ecosystem of feature rich, free and open Usenet clients.

      I really miss having my own killfiles and regex search abilities that were common on Usenet clients, but is missing from the Reddit clients and its web UI.

    • I don’t believe it was or continually is limited to text only, but I do believe we had netiquette back then which helped to reconsider spamming internet with media and other decorators, only to have it all forgotten 72h later

    • Usenet could exist only because people could behave, unfortunately. I can't even begin to imagine what kind of shitfest Usenet as a social media platform would turn into today.

      The eternal September complaint comes to mind, but even eternal September was a jolly walk in the park compared to what modern social media has turned into.

      1 reply →

FTP is still used quite a bit. For what it’s useful for, nothing has come close to replacing it.

  • SFTP? Don't confuse it with FTP or FTPS - SFTP is a different protocol which runs on top of SSH.

    • They are not confused. A lot of companies still use FTP internally and for B2B. Many people would be very uncomfortable if they knew how much companies including banks, payment systems, etc... and governments still depended on FTP and clear text authentication. That's even before broaching the subject of which of the applications and daemons in use are being actively maintained.

  • like in enterprise? the browsers stopped shipping with ftp support I think 5 years ago.

    • Hosting files to be downloaded via web browser isn’t what it’s useful for. If you’re going to do that, you might as well use… a web server.

      FTP is useful for bidirectional file exchange over the Internet. There are other protocols, but they all have drawbacks. SFTP can be used for similar functionality, but it requires users to have SSH access. SMB and NFS don’t really work so well over the Internet and are a pain to configure for multiple users. For setting up accounts dedicated to transferring files, you really can’t beat FTP (or really FTPS, which is just FTP over SSL).

      3 replies →

There is still a niche community of people running Gopher servers. I wrote a small basic implementation of a Gopher server in Python before for fun once and it hosted a Gopher hole for a few years. I doubt even one person actually looked it at besides me, but the RFC is simple and can be implemented pretty fast.

what about SMTP?

  • I thought of that ... you could put it in the list but I wouldn't unless you're talking cron. I mean when I started it was like mail bob@froggy.ucla.edu and bob would open up pine or emacs and not get any spam or have to do anything crazy and we'd have a conversation.

    that modality is long dead. we still have email but it's not that same ... I however could take mirc from like 1995 and still use everything.

I wonder if the LOC Gopher is still around; I used to use it as a "jumping off" point.

But as IRC has a social network component, it's more of a social thing than anything inherent to IRC.