upvote
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.

reply
I feel the need to be pedantic, but I do not mean it to be rude.

What we sometimes call SSL is not the same SSL as back then. That said, TLS was released in 1999, so it just barely makes the cut. :D

reply
Telnet still very popular with embedded. SSH is not a spring chicken either.
reply
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.
reply
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...

reply
> 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.

reply
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.

reply
Yes. usenet, however, used to be social media. It was like text-only reddit.
reply
> 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.

reply
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
reply
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.

reply
> 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.

Spam filtering has improved a lot since the Usenet days, but even if it hadn't we had killfiles to deal with the spam and filtering out harrasers. Doing this today would be even easier with the help of LLMs.

reply
What about the registration you find so painful? It takes a single command to register a nick, if that's what you mean.
reply
In his defence, its a single command, if you know the command
reply
This, which is not uniform across servers, and has more work if you want to do certificate-based auth. Additionally getting a nick cloak is good opsec and also extremely not uniform.
reply
Also funny watching peopel mistype the command in the wrong window and expose their "password for everything" to everyone in the chat.
reply
The entire premise of cloaks as optional seems like broken UX to me. I'd like to see a new version make your connections details private by default.
reply
FTP is still used quite a bit. For what it’s useful for, nothing has come close to replacing it.
reply
SFTP? Don't confuse it with FTP or FTPS - SFTP is a different protocol which runs on top of SSH.
reply
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.
reply
What do you mean, "for what it’s useful for"? For me, WebDAV has replaced FTP where SFTP hasn't.
reply
Has that caught on? I last used it 15 years ago and it was great but I haven't seen it anywhere
reply
like in enterprise? the browsers stopped shipping with ftp support I think 5 years ago.
reply
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).

reply
> SFTP can be used for similar functionality, but it requires users to have SSH access.

Security-wise you set it not to run commands (and maybe chroot) and you're done, right? And difficulty-wise isn't granting SSH access very similar to FTP access?

I don't understand the issue.

reply
SSH requires a system account. FTP access can be granted and revoked via a database, or even a text file.
reply
That depends on your server.

But in the most common case a "system account" is a line in two text files, isn't it?

reply
You might be surprised to learn there are dedicated ftp clients.
reply
sarcasm?
reply
Don't know of a client with that name, but there are plenty of others.
reply
HTTPS has largely replaced it. Pretty much all files uploaded or downloaded from the internet is going to be done via HTTPS and not FTP.
reply
Only if you ignore the banking industry.
reply
Fair point, but I would assume the AWS S3 by itself is bigger than the FTP/SFTP traffic globally including banks. No idea if it’s true, and I’m not sure we can get reliable stats on this
reply
Everything decentralized will keep being used. Stuff is sticky.

More illuminating: To what (relative) extend? And what's the trajectory?

Looking at Google Trends: https://trends.google.com/explore?q=%2Fm%2F03t2s%2C%2Fg%2F11...

reply
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.
reply
what about SMTP?
reply
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.

reply
I wonder if the LOC Gopher is still around; I used to use it as a "jumping off" point.
reply
But as IRC has a social network component, it's more of a social thing than anything inherent to IRC.
reply
I'm here looking for other telenet (not telnet) oldheads, finding nobody.
reply
COBOL is still used 50 years later.
reply
COBOL is definitely a hallmark of this type of argument.
reply
reminds me that fortran has a modern website: https://fortran-lang.org/
reply
Logo too!
reply