The trick is to make sure that nobody cheats. If one jurisdiction offers more favorable terms than everywhere else, then all the data centers go there and ruin the environment. This is the ideal use of federal or even supranational regulation, to make sure the playing field is level.

The neat thing about copyright is that it's such an inconsistent issue. People are pro-copyright when they're worried about their work or jobs being at stake, and anti-copyright when they think copyright holders are making too much money. Nobody seems to have a balanced, much less nuanced, concept of what copyright law should actually be. It's just a cudgel that keeps getting passed around, picked up and refashioned to meet the moment into whatever someone needs to wage the war they want to wage.

Crucially, there have been zero incidents of anyone actually making copyright claims against AI-generated code, aggravated somewhat by the fact that one of those "divided" courts is actually just the US Supreme Court repeatedly refusing to revisit their declaration that AI output cannot be protected by copyright. There were some plagiarism accusations against OpenAI from human mathematicians who were working on Navier-Stokes, but the shape of that case looks more like breach of confidence, since the material wasn't published.

Copyright is going to die, one way or another, quietly or loudly, and most likely because the law everywhere will refuse to inconvenience the new economy.

But if you have any memory at all for what the MPAA and RIAA did two decades ago... we should all be cheering on the demise of this weapon. In a world where works are cheap to produce, it is tantamount to sowing a minefield in the commons. The DMCA has rarely been used for anything good for society.

Well, pull up a chair, because you're going to hate this conversation!

There are two parts to the issues around AI, at least when we're only talking about the ones you brought up.

The first part, which most people quietly shove under the floorboards and try to ignore, is that the current AI ecosystem is heavily characterized by the hypercapitalist mess. Much of what LLMs actually are does not necessarily pose a threat to the world order, nor does it necessarily involve environmental degradation. Saying "AI bad because <insert everything wrong with capitalism>" isn't really an anti-AI argument, it's an anti-capitalism argument. Most journalists are not brave enough to point this out, much less accept it, much less the consequences of saying that maybe unfettered robber-baron great-man titans-of-industry anarchocapitalism ain't all sunshine and gravy all the time.

With that out of the way... the facts around AI's environmental impact and world-ending risks are not as clear-cut as the popular conscience has absorbed. Hysteria is just so damn easy to do, you know? Fox has been at it for years, now it's the Left's turn to ignore all the details and just overreact to headlines! Awesome.

The strain on municipal water grids is another consequence of shitty cost-cutting run amok, amplified by a steep learning curve on the part of cities trying to attract high-value businesses before anyone knew what the landscape looked like yet. They gave out bad permits. The electricity situation is very similar: they could be expected to pay their fair share and actually invest into community infrastructure and clean energy projects, but in most early high-profile cases, they haven't been. Andy Burnham's UK government is doing this much more intelligently, and we'll see the actual downside of that soon, namely that certain skeevy corporations will just off-shore their datacentres in more friendly jurisdictions. There's an interesting parallel with how scabs undercut collective bargaining, you might say. This is capitalism being an unmitigated disaster yet again, you might say.

Now, as for ending the world or causing human extinction... it is also almost entirely a load of complete bullshit. The modern AI safety movement, to which all of the Silicon Valley leaders subscribe, originated with a creepy neckbeard named Eliezer Yudkowsky. Yudkowsky's reasoning depends on a crucial, catastrophic assumption, which is that creating an actual god that we cannot control would be a bad idea. It has never been proven, nor can it be proven, that AI research will actually lead to this result.

More importantly, Yudkowsky only says this because he has a deep-seated desire to take over the world with his own AI, using something called Coherent Extrapolated Volition. He is mad about not being in charge, and is still recruiting cultists to help him, which he charmingly has dubbed Rationalists, as though Rene Descartes has something to do with fucking over the whole planet. (See Holly Elmore, "The Case Against Eliezer Yudkowsky" on YouTube.) The tagline that AI needs safety engineering is the 'public' version of their secret knowledge, one curated to sound reasonable to a layperson; the true version is something more akin to "only people who think like us can be allowed to use AI to direct the future of humanity." (The recruitment methods self-select for vulnerable people with autism, which makes these pills much easier to swallow.)

When Anthropic's CEO, Dario Amadeo, talks about AI being unsafe, he is usually literally citing Yudkowsky; Amadeo is a true believer and has been . Conversely, when Altman says AI could cause human extinction, he's just parroting what everyone else is saying because he thinks it sounds sick as fuck to investors. Both of them are imbeciles, but it's not clear which is more dangerous. Everyone else in the world is referencing either Yudkowsky or Altman through various levels of broken telephone. Do not listen to any of them. Actual AI safety work is important, but much more humble in the problems it confronts.

Having said all that, we shouldn't be unhesitatingly pro-AI. There are still lots of places and situations in which its usage is inappropriate or needs to be nuanced. However, we can squarely put "going to end the world" and "ruining the environment" under the "greed is bad, actually" category. Recognize the greedy assholes responsible as the greedy assholes they are, and the narrative evaporates.

When editing Qwen, Astra actually wrote and used a Python program to do the dirty work and required some trial and error. This is something humans are already doing; it just doesn't receive much publicity. Raw reading and writing was only done in other parts of the paper, for smaller tasks like detecting the purpose of a game-playing network and correcting a simple vehicle control feedback loop. Though the Qwen edit was successful (after some 50 tests), a similar edit on a smaller Gemma network to remove sycophancy wasn't.

See summary on honnibal.dev for a breakdown.

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.

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.

I believe the plan was to give that sobriquet to Lake Michigan, in honour of its decidedly flaccid silhouette.

I had a problem where AI scrapers were absolutely DETERMINED to fish out every possible query string from a search results page. Almost all of the query strings they tried were invalid due to shitty and dysfunctional string substitution. "&page=100" wouldn't be followed by "&page=101", it would be followed by "&pag&pag=1010" or something even more insanely half-baked, until the query strings were like 100+ characters long. It was the technological equivalent of watching HIV mutate in real time.

But the insane thing was that, aside from page number, they were always requesting info about the same other criteria: filtered by the same user, the same page type, and with no text string. So I just took those particular values and started banning logged-out users who requested that combination of criteria.

I figured I'd need to change my tactics in a couple of days once the botnet got bored of that particular page and moved on to requesting bogus entries for another user.

MariaDB> select count(*) from ip_bans;
+----------+
| count(*) |
+----------+
| 671671 |
+----------+

It hasn't.

I regret to inform you that you have woefully underestimated it. The actual retail rate offered to consumers is closer to $2200 US per gallon. Sources: internet-ink.com, cbc.ca. This $14 million fine is only worth like, seven thousand gallons, or less than 200 oil barrels of ink.

By your powers combined, I am... the British Colonies!

The main aim of Stop Killing Games is to ensure the practice of rug-pulling eventually comes to an end. They are not trying to save MMOs, for example.

Moreover they don't demand that every game currently on the market comply with open-sourcing requirements: at a minimum, companies always have the option of simply providing customers with adequate notice before shutdown. Open-sourcing the server would be nice, but it's hardly the only way to protect consumers' interests. Scott has, for example, suggested game boxes being marked with an estimated expiry date for online service functionality.

But most importantly: because this is about future games, not the present, the market has time to change. If studios and publishers are designing their games with a fair EOL in mind, then they can make decisions from the get-go to avoid licensing dependencies that they won't be able to release in a possible 'afterlife' version of the game. As suggested by your example of GameSpy in C&C: Generals, when a commercial dependency is crucial to a game's success, it tends to be a client-side library, but typically the problematic dependencies aren't crucial; they're e.g. add-ons for Unity or Unreal that the studio bought to save time. In a world with SKG laws, the providers of these dependencies aren't going to be a stagnant target either—demand for compliant libraries will motivate development of open-source versions.

Interestingly, the will for doing this does exist among game developers; they just need the institutional support from legislation to twist the arms of the studios and publishers. Ross Scott has talked to a lot of devs who are burnt out from having their projects cancelled, leaving them with huge gaping holes in their resumes and portfolios where they've spent years on unreleased projects that are stuck under NDA. In general they tend to see SKG as a path to ensuring the games that do see the light of day aren't also scrapped, which would erode their work histories even further. (Apparently it also just plain feels bad to have your work erased from history. Shocking, I know.)

Fear not! It's entirely possible the category was chosen by an AI. Editorial automation would probably reduce the error rate here.

It's all a small price to pay for Eat Your Veggies.

Duke 3D's soundtrack was not exclusively the work of Bobby Prince; Lee Jackson, Apogee's go-to music guy, also did some of the tracks, including the title theme, Grabbag.

Prince used not only his MIDI skills but also his experience as a lawyer to ensure his 'inspired' derivatives were as close as legally possible to the originals. The relationship between individual tracks is often very clear and sometimes even hinted in the metadata of the source files.