Not really. AGI is a game interpreter, like LucasArts’ SCUMM or Infocom’s z machine. Games are shipped as portable code and a machine specific AGI interpreter runs them. Looks like they’re preprocessing the graphics first, though. https://en.wikipedia.org/wiki/Adventure_Game_Interpreter

“A good starting point” is almost certainly all it needed to convey and what it should have written.

When I read this I thought you'd discovered that the whales release the gas in a form other than by blowing bubbles, or that the purpose of doing so was for something other than improved sleep.

But no, the whales literally release air through their blowhole in the form of bubbles, and, at least during study you linked, they do this while resting to maintain their vertical orientation. An orientation, the paper theorises, that enables better sleep by not being buffeted by waves.

They quite literally blow bubbles to achieve restful, vertical sleep.

Then, later, a couple of patches to make binfmt_misc more ergonomic. Seems like a good outcome.

> we are well into undetectable sophistication with today's models

The article directly contradicts this, as do you, in your previous paragraph: "Sure you might be able to detect today's tells". The article is literally about a technique that detects today's tells.

Your comment is mostly expressing doubt that this technique will work reliably in the future, but it's framed as opposition to the article, which it's not: the article is about detecting today's AI-written text, at which it seems to be quite successful.

For contrast these have "ice cold" (shot of ice cubes), "got chucks on" (shot of shoes), "livin' it up in the city" (shot of city).

It seems like the proper fix is for GitHub not to allow their agentic workflow to execute in a public repo context if it also has private repo access. Or, to use your phrasing, for GitHub to flag and disallow this easily-detectable and dangerous type of misconfiguration.

Disfluencies aren’t necessarily bad even if the word starts with “dis”!

This was actually the convincing one for me though. “Did AI increase the rsync bug rate? Dunno, can’t tell yet” seems like a fine conclusion to me. Plenty of people in this thread and previous ones on the topic seem convinced one way or another, so it’s nice to see actual numbers.

You’re not a bozo but it is helpful to read the code.

As others have noted the company has done some pretty shady things with some of their other products, and I would not really expect a warranty, so this isn't really a recommendation. But my personal experience after ~six months of use has been good.

You don't need to imagine it: the comment you are replying to links to a press release from a Government agency "going after Microsoft". And yet somehow we haven't seen Microsoft stop doing business with the Australian government.

Then again, I just caught Claude writing setTransparent(!opaque == false), opaque being a bool, on a purely vibecoded project. Which was pretty impressive. ("• You're right, that's nonsense.")

I've noticed Claude is specifically fond of three-element lists consisting of (standard example of class), (standard example of class), (nonstandard example of class). It's interesting because Claude often gets the nonstandard example more or less incorrect -- in this case, because gristle isn't an example of a high-fat-content food.