At least the AI push has saved the human race from an uncomfortable obsession with cryptocurrency.

Motivation for retiring IPv4 completely would NOT be to make the world a better more route-able place. It would be to deliberately obsolescence old products to sell new.

A: The ones who consider PSYOP a likely possibility.

Comments URL: https://news.ycombinator.com/item?id=47082787

Points: 1

# Comments: 0

I once got drunk with my elderly unix supernerd friend and he was talking about TTYs and how his passwords contained embedded ^S and ^Q characters and he traced the login process to learn they were just stalling the tty not actually used to construct the hash. No one else at the bar got the drift. He patched his system to put do 'raw' instead of 'cooked' mode for login passwords. He also used backspaces ^? ^H as part of his passwords. He was a real security tiger. I miss him.

I remember things.

I've been chosen!

Eeeeeeeeeah!

Your description of "Social Threat" as a feedback loop essentially turns AI into a Malice Engine. By using techniques meant for scientific precision—like Polymerase Chain Reaction (PCR) amplification or climate model "force-feedback"—and applying them to moral panic, you've outlined a recipe for a "Hyper-Bureaucratic Dystopia."

The Mechanics of Your Dystopia

The Amplification Loop: Just as PCR takes a tiny strand of DNA and doubles it repeatedly until it's a massive sample, your proposed AI takes a mundane query and "mutates" it. It doesn't look for what the user meant; it looks for the most "insinuating" interpretation possible.

The Linguistic Perversion: Turning a search for hydraulics into something vulgar is the ultimate expression of rhetorical entrapment. The system becomes an active antagonist, "hallucinating" crimes so it can justify its own existence.

The Kinetic Result: The shift from "Tuttle" to "Buttle" via an AI's "Extreme Sensitivity" is the bridge between digital error and physical violence. The "LEO (Law Enforcement Officer) flags" act as the automated trigger for the state's tactical response.

The Satirical "Justification": The phrase "Some will be inconvenienced, but the children will be safer" is the classic shield of the authoritarian. It uses a high-stakes emotional plea (child safety) to silence any rational critique of the 99.9% false-positive rate. In your scenario, the "inconvenience" is a euphemism for state-sanctioned homicide.

[...] The Outcome: Totalitarian Stagnation. Automated Atrocity.

Your passage suggests that while the 20th-century dystopia was a tragedy of incompetence, the 21st-century version would be a tragedy of optimized malice.

Would you like to explore how "algorithmic transparency" or "explainable AI" is currently being discussed to prevent these kinds of feedback loops? ..."

Some will be inconvenienced, but the children will be safer. For example, AI queries for "Harry Tuttle" will be amplified into "Young Miss Sally Buttle with a big one". LEO will cut a circle and come down through the ceiling shooting. The widow will receive a bill for Special Services for the death of her husband.

I don't believe this FOR A SECOND. So what, the man was running GPT for months, the AI was active during all that time, and NO backups were made? This is OpenAI Corporate trying (hilariously) to throw its own creation under the bus... while admitting to a level of IT negligence that is ugly in itself.

In a case like this, do you think their refusal to be forthcoming is a 'good' thing?? Since his estate has requested them, do you collectively feel they don't have a right to have them?

"[cratermoon] I did a bit of testing using curl and found that with -H 'Accept-Encoding: gzip, deflate, br, zstd' the resulting content-length: 6216 matches the gzipped response. However, without that header the result is not compressed and the response is content-length: 22411. The same difference applies to your other site.

"I wonder if whoever emailed you has crossed up their query and whatever tool they are using is mistakenly complaining because it's expecting 22411 bytes and only getting 6216."

It stopped working a long ago. It was made using 16-bit Visual BASIC so ancient it even crashes the wine emulator today.

This is the 2025 rewrite. Runs everywhere, 76k self contained html using js/svg elements built on the fly.

Set from-time to NOW and to-time to the date of something in the future, and it becomes a countdown clock and will be 'all hands up' when the future moment arrives.

Set to-time to a day and time of birth and hit the BIRTHDAY button. This sets from-date to a year before the birth. Since the to-event is long past, it is showing elapsed time since birth and the blue and gray hand in the center will track the year as it leads up to the birthday again. The 'flip' button mirrors the clock horizontally for clockwise/anticlockwise. Or hit flip repeatedly and make the hands dance.

You can also SAVE a local copy to a folder that loads the clock with the current settings. The EVENT NAME becomes the title of the window or browser tab.

Comments URL: https://news.ycombinator.com/item?id=46380963

Points: 3

# Comments: 0