1. Tier‑1 transit filtering of port 23
The discussion centers on a large‑scale block of TCP 23 that was deployed by major backbone providers to stop exploitation of a long‑undisclosed GNU telnetd flaw.
“The rest of it seems to be substantially edited by an LLM too, or at least it’s composed much like LLM outputs often are these days: ‘not a gradual decline, not scanner attrition, not a data‑pipeline problem, but a step function.’” – roywiggins
“The rest of it seems to be substantially edited by an LLM too” – roywiggins
2. Telnet’s legacy and continued use
Many users point out that telnet is still alive in embedded devices, legacy MUDs, and hobbyist systems, and that the block will break those services.
“I still use telnet today (had to). Unsure of the patching here. But it’s definitely locked down to a subset of internal use only.” – RonanSoleste
“I have a few retired SPARC and PA‑RISC boxes that run their period‑appropriate OSes as a hobby. Telnet/rlogin is the more reliable method to get into them remotely.” – fennec‑posix
3. Security debate: telnet vs. SSH
The conversation repeatedly contrasts telnet’s plaintext nature with SSH’s encryption, discussing patching, privilege separation, and the practicality of using SSH for legacy hardware.
“Any business that has a telnet daemon able to be reached by an unauthenticated user is negligent.” – wildzzz
“The rest of it seems to be substantially edited by an LLM too” – wildzzz
4. AI‑generated content skepticism
A sizable portion of the thread is devoted to whether the article and many comments were written by a large‑language model, with users citing style cues and “LLM tic” patterns.
“The rest of it seems to be substantially edited by an LLM too, or at least it’s composed much like LLM outputs often are these days.” – roywiggins
“The rest of it seems to be substantially edited by an LLM too” – roywiggins
These four themes capture the main currents of opinion in the discussion.