Well nuts. I couldn't even get the week right. Thanks for the correction!

Well it is the day after the US midterm elections, so for some it will be the end of the world in a metaphorical sense.

What? No, it's not.

The midterms are on Tuesday, November 10th. Friday is not the day after Tuesday.

the actual production cost of $30 million as indicated by the tax writeoff stated value

The tax write-off can only be for part of the production cost, isn't it? You don't get to deduct the entire cost of the movie.

It's well-reported that WB sold the film below costs to Ketchup, and they paid $50 million for it.

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.

There is a reason I qualified that with "open source projects for AI."

Toasters will fly (again) before Nvidia's graphics tech gets open sourced.

Nvidia has been a pretty big supporter of open source projects for AI over the last half-decade or so. Many of the company's technologies are open source, most notably their open-weights model, Nemotron, and Dynamo, their inference serving and distribution framework. So it would be surprising to see them do anything to close off the Hugging Face collection. If nothing else, keeping it open is in Nvidia's own self-interest. The frontier AI companies themselves are all designing their own AI chips (e.g. OpenAI Jalapeno, Meta MTIA), which reduces the amount of Nvidia hardware they need to buy. Whereas smaller operations using open source models will inevitably pair those with commodity COTS hardware, which is where Nvidia reigns supreme.

Epic added a Linux build target to Unreal Engine 4.1 in 2014. And since UE5 in 2020 the entire development toolchain has been feature complete in Linux. Meaning you could make your Unreal game on Linux and then release it natively for Linux (and Windows/consoles/mobile devices/etc).

So while Epic has not been the best supporter of Linux, they have not been ignoring it, either. The core engine is ready. What's left is that the anti-cheat software (Easy Anti-Cheat) and the store need to catch up.

Epic looks to be hiring to improve the anti-cheat situation as it currently lacks kernel-level support, and this latest announcement indicates that they're working on getting EGS running as well.

The article makes no mention of the source. But everything about this sounds like it's just the CAM release from LuCY. Which has been available for around a week and a half now.

In which case, yeah, the only thing novel about it was that it was posted to a more publicly-visible website.

Xbox 1 emulation is in a so-so place right now. Xemu has pretty good compatibility (80% or so), but it is very, very slow.

To date no one has been able to develop an Xbox emulator using high-level emulation, so Xemu takes a low-level approach based around QEMU. Which makes the computational requirements much, much higher*. To the point where there are plenty of games that run at half-speed (or worse) even on the latest CPUs. The current emulators are heavily CPU limited (and to just a couple of threads at that), and CPUs aren't getting faster very quickly these days.

So if Microsoft has an emulation environment with much lower overhead, then that is a significant development. Because even with third-party emulators available, most games aren't currently fully playable on them.

* LLE extends to the GPU as well. So a lot of cycles are burnt emulating parts of the NV2A GPU and its 25 year old peculiarities

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.

Amazon took nine years to reach profitability.

I'm not sure Amazon is a good example here. The company famously opted to reinvest its free cash flow into growing the business, rather than saving them and booking them as net income. They likely could have been profitable sooner otherwise.

Also, I am not aware of Amazon receiving billions in government support in the 1994-2001 timeframe.