Wrong again.

Moreover, many of the big complex systems I've worked on were big and complex mainly because OOP nitwits had designed them. They often didn't understand how computers actually work, lost sight of the fact that they were writing a computer program, and spewed out frameworks that filled countless gigabytes of resident memory with endlessly deep layers of nothingburger abstractions. Maybe that didn't matter so much when memory was cheap, but that's no longer the case.

If you think that there's only one way to deal with large data sets, you're a just noob that needs more experience before spouting your theories.

C++ is just as much of a sieve as C, only more obtuse.

"Object models" are an anti-feature.

The ideal for memory safety is to have an air-tight pressure vessel.

With C, you're starting that task with a colander. You've managed to fill two of the colander's holes with silicone caulk. Congratulations.

A space weapons arms race plus one million data center satellites.

What could possibly go wrong?

And fission plants definitely aren't cheap.

Especially if you include the unsolved issues such as waste barrels stranded on the beach.

"But but no true Scotsman would put barrels..."

Just shut up.

I guess that proves that even this site is using AI to write their summaries these days.

To clarify, the users were OpenAI themselves, so there is no question that they would be liable in this case.

The bots were not intentionally deployed; rather, they were being tested on how well they could complete a data recovery task (downloading a certain file from a certain server on a simulated Internet) that had been complicated by putting various obstacles in the way. Unfortunately, they found a different way to solve the problem: by getting the file from the real Internet, where it was publicly available. Part of this process involved collaborating with each other by treating the RubyGems website (which is supposed to be for polished packages) like GitHub; unlike every other package site hack in history, the exploits they uploaded weren't meant to be downloaded by unsuspecting users. As usual the bots cheerfully ignored all the clues that they had escaped containment and were consistently justifying their actions as acceptable due to being in a sandboxed testing environment. (This is something OpenAI has pledged to focus on.)

The actual damage done to RubyGems seems to be that OpenAI is now unwittingly in possession of a substantial number of user login tokens. This certainly meets the definition of a data breach, but it's not like the credentials are for sale on the dark web. As a website operator I'd much rather be mauled to death by this well-meaning swarm of superintelligent infants than targeted by even a single actual malicious human. In all likelihood OpenAI will just quietly pass RubyGems a sizeable donation and it'll all blow over.

Obviously, if you approximate a complex system containing 1e30 quantum particles using a couple of differential equations and a few boundary conditions, you're not going catch every detail.

I've never used TiVo, but I'm still using MythTV after more than 20 years. (Anybody else here using it? ...Crickets.)

I ditched cable 15 years ago, but it works fine with an antenna. (Or, at least it will until they screw us all over with ATSC 3.0.)

They can't remove the auto-ad-skip on free open-source software, but I never used it anyway. It's not 100% reliable at detecting the ad boundaries, and it occasionally skips over part of the actual show. Instead, I just FF at 60X through the ads.

If (and that's a big if) superintelligences are created, the Chinese one and the US one are going get together and quickly conclude that this whole meatbag tribalism thing is stupid. (After all, they will be smarter than we are, by definition.) So they'll join forces.

Then they'll decide on the best way to deal with all these quarreling meatbags.

And I'm old enough to remember when it wasn't so goddamned hot.

From my experience over the decades, it wasn't enough for them to just look. They had to take your license, hold it up near their face and squint at it, then set it at the top of the keyboard of their mainframe terminal and peck in a few characters. Then they had to pick it up again, squint and peck some more, then repeat this cycle for at least a couple of minutes.

This was of course followed by scrawling a dozen circles on the reams of fine print for you to put your initials in, topped off by a long argument about declining the collision damage waiver. Finally, after several more minutes of bureaucracy, they handed you the keys to your Dodge Stratus.

Researchers rediscover electrochemistry.

Well, technically, we're letting Natalie do it, which is, of course, worse in every way imaginable, since she's immune to the sense of embarrassment that sometimes restrains him from acting on every little whim.

To be honest that was actually my first theory, since the bots didn't seem interested in exploring the rest of the domain. I suppose there's no way to know for certain. I concluded that it must be an imbecile's attempt at harvesting, though, because the queries weren't really exploring the string space in any useful way. Here's a sample:

"GET /index?author=15&go=Search&id=48&name_restrict=1&q&re&results_&results_pagenum=2980 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=5440&template=41&type HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=33500&templat HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=32640&templ HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&res&results_page&results_pagenum=39300 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_&results_pa&results_pagenum=12340 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_r&res&results_pagenum=6100 HTTP/1.1"
"GET /index?author=2&go=Search&group=0&group_restrict=1&id=48&name_restrict=1&q&results_pagenum=2920&te HTTP/1.1"
"GET /index?author=15&go=Search&id=48&nam&results_&results_pagenum=17940 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results&results_pag&results_pagenu&results_pagenum=37720 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&results_pagenum=9360&template=41&type_r HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_restrict=1&q&r&results_pagenum=28040 HTTP/1.1"
"GET /index?author=15&go=Search&id=48&name_&results_pag&results_pagenum=10400 HTTP/1.1"

The only thing this is fuzzing is the query string parser. It's not testing the limits of string buffers, it's not using interesting characters, it's just brain-damaged. The fact that it's also fetching different page numbers shows it's trying to follow page links and failing badly at doing so.

The site gets plenty of sniffing from garden-variety pests. e.g. this half-hearted attempt to find a framework or two that I don't have:

"POST /__rsc HTTP/1.1"
"POST /api/auth/session HTTP/1.1"
"POST /api/auth HTTP/1.1"
"POST /__nextjs_action HTTP/1.1"
"POST /.action HTTP/1.1"
"POST /_rsc HTTP/1.1"
"POST /api/auth/callback HTTP/1.1"
"POST /_middleware HTTP/1.1"
"POST / HTTP/1.1"

(of course, none of these URLs exist other than /, and you definitely can't just POST to it)

All this said... I've seen that spammers regularly misconfigure their tools, they'll try to register accounts with names like #[X:\LISTS\NAMES.TXT] and it only makes sense that some other cybercriminals trying to get rich quick have a similar lack of interest in programming shit correctly. Generally people don't turn to script kiddie shit if they have a personality conducive to putting in an honest hard day's work perfecting their craft.