Anyone happen to have a recording of it?
It does give a message stating as such:
Well, the IPv6 version is exactly the same as the IPv4 one.
The difference is in the visitors...
Je bent een Stoere Bikkel, aka You Rock.Ended up on mud.balzhur.org:5400 where I befriended a blind Venezuelan guy.
And after a while I soon realized that everyone on the server was probably blind.
Pretty fascinating.
I logged in just the other day and saw that he still plays daily. I want to talk to him again, but I need to go through the noob tutorial to remember how to do anything.
A server (or client) should send `IAC WILL <option>` to announce that it has a capability, and the other party will confirm/reject with DO or DONT.
But some servers will send `IAC DO <option>` even though they are announcing a capability (like server-to-client compression).
Telnet is fun and I like how simple it is. Kinda sad it's basically dead except for what feels like servers that nobody remembered to unplug.
If I understand correctly, with a true mechanical teletype CR only returns the print head to the start of the line, and LF only advances the paper by one line. If you want to move your cursor to the start of the first line you have to send both, but there's no reason for the teletype to care about their order.
MUDs didn't precede the CR+LF convention, because that convention (if memory serves) pre-dates the Internet itself by a few years. However, it wasn't the case that CR and LF separately had the individual functions that they commonly had a decade or so later. Sometimes, for example, LF on its own was newline, or CR had to be simulated with lots of BSes.
The thing about TELNET is that in 1983 it explicitly specified an abstract Network Virtual Terminal and was definite about what newlines should be for it. See RFC 854. Anything TELNET-based was supposed to operate to that abstraction, not take advantage of the fact that sometimes LF+CR worked on real terminals. An NVT wasn't a real terminal. All of the delays and what the characters really did was supposed to be hidden by the abstraction.
After all, if you're not controlling a mechanical print head, then LF+CR vs CR+LF should always land you immediately in same place anyways because you're just moving the pointer around a virtual grid.
So it makes sense to get it wrong in 1998 since you're post-teleprinter while also in the early days of the convention becoming crystalized.
Yes, there are tons of blind people playing them, altough several of them prefer either text adventures, fighting games or adapted pokémon for emulators.
https://telnet.org/htm/places.htm
I found a few BBS's that had Tradewars running.
Who would have known that basically the same functionality would later become a billion / trillion? dollar story (whatssap).
And yeah, more than a little ironic.
We logged in daily because there was always new content to discover. A new fileshare with obscure content or a zine with cool ascii art. It’s a shame that everything is fed to us now. That sense of discovery is largely gone.
It’s interesting to me how that got flipped upside down. People log on daily to consume viral content or meme templates that is in everyone’s feed. Early BBS culture was all about finding the niche where you fit in.
I know I'm living in a different and hitherto unimaginable universe when I paste modern cloud-devops sysadmin types the output of a hung telnet connection attempt to port 22, as implicit evidence that it's blocked by a firewall or whatnot, e.g.
$ telnet 172.30.110.9 22
Trying 172.30.110.9...
^C
... bro. I know it's a DeVry Cloud DevOps certificate, but...
$ nc -v 172.30.110.9 22
[literally nothing]
$ telnet 172.30.110.9 22
Trying 172.30.110.9...
~ $ curl -v telnet://1.1.1.1:443
* Trying 1.1.1.1:443...
* Connected to 1.1.1.1 (1.1.1.1) port 443
--
~ $ curl -v telnet://1.1.1.1:22
* Trying 1.1.1.1:22...
^C ~ $
Having said that, in the world of my customers' systems, neither telnet nor curl can be presumed, it seems.
~ $ curl -v 1.1.1.1:53
* Trying 1.1.1.1:53...
* Connected to 1.1.1.1 (1.1.1.1) port 53
* using HTTP/1.x
> GET / HTTP/1.1
> Host: 1.1.1.1:53
> User-Agent: curl/8.13.0
> Accept: / >
* Request completely sent off
* Empty reply from server
* shutting down connection #0
curl: (52) Empty reply from server
--
~ $ curl -v 1.1.1.1:22
* Trying 1.1.1.1:22...
^C
Always makes me chuckle whenever I remember that..
https://docs.openssl.org/1.0.2/man1/s_client/
Or maybe socat, I don't use it but I'm pretty sure I've seen people use it.
I can't remember the last time I used telnet to test whether a web server was live. I don't think web servers figure very prominently in the work I do, though not zero, for sure. However, I doubt I'm the only one in that boat.
The concept of protocols made up of printable characters delimited by new lines is antiquated.
All of those problems have different root causes and therefore have different solutions. Telnet helps you figure out where in the stack the failure is occurring.
What I don't get is all the SSL kids never mention s_client, as in "...use s_client instead". Granted, most of the time ssl will work for, you know SSH (port 22). Are you really going to negotiate the cypher by hand, mate? I get it, how many of them can identify what "\x16\x03\x01" is?
Incredibly cool to see that in action though! That map is incredible.
If sending the client's terminal type to the server is disallowed, it just hangs, and then times out. Reasonable behaviour, one might think, for a server that really needs to know that it can legitimately send colour changes and non-standard control sequences for the mouse over the wire.
But it still sends some non-standard control sequences in the signoff screen. And if it doesn't recognize the terminal type, it emits a warning message and forges blithely ahead.
And thinking about MUDs, there is no better / worse way to feel the crush of time than finding your old MUD is still online. I found mine again a few years ago. Couldn't remember my password so made a new char. Used "finger" to look at my main. Last logged in 9000+ days ago. Looked up my friends who I used to spend hours with. Around the same. 9000+ days. Seeing it quantified in days rather than years made it more difficult and more personal. 9,000 days just gone like that.
A local MajorBBS in my area had multiple nodes and outbound internet.. with no dns for some reason. So we needed to know the ip address of the bbs/mud we wanted to telnet to.
Some of the highest quality people I know I met there and still speak to.
Mine was a weird one, it was actually a top-down paintball game whose "graphics" were just ascii with screen refreshes. It might even be stretching the definition of MUD to call it that but it was a text-only multiplayer game that you accessed via telnet so it just kinda got absorbed into the MUDiverse. A few weeks ago I found out that, after a 20 year hiatus and at least one moderately successful clone, it's been relaunched with a GUI frontend. paintballnet.net, there are even occasionally a few players online but when there aren't there's always bots and a shockingly deep pool of loadouts to choose from.
https://web.archive.org/web/20250128064648/http://resworld.e...
:(
I wish I'd done something better with that time other than just chatrooms but c'est la vie.
piker•7mo ago
hugged to death?
theblazehen•7mo ago
matja•7mo ago
bevenhall•7mo ago
tripflag•7mo ago
theblazehen•7mo ago
infiniteregrets•7mo ago
ps, it is running on fly.io so please don't melt the poor baby
JdeBP•7mo ago
My improved version written in Java no longer does.
* https://jdebp.uk/Softwares/text-movie-player.html