Rogue if you want to...


Tan Teen Oni Waifu, episode 5

Our Adorable Adopted Twin Lolis have a secret, and it’s pretty obvious from all the foreshadowing, but we’ll still have to wait a week to see it. In other news, one of Our Waifu’s dreams has come true. No, not that dream. And it looks like horses and cattle aren’t the only new residents. Also, apparently this was goofy reaction face week.

Verdict: consistently refreshing.

(unrelated Best Horned Girl)

10 Years A Harem Lord, episode 5

It’s all fun and games until the vampires slaughter a village. Still fairly light-hearted, for all that. Given that we’ve gone from zero to high lord in a single episode, I doubt this is the long-term villain.

Verdict: amusing fluff, but will anything actually provide a challenge for Our Hero?

(perhaps a vampire like this would be more of a challenge, and more of a service for us?)

Sick of hearing about OpenAI’s “rogue” agents

I don’t even want to link to all the press releases about how the AIs “escaped” and “went rogue”, as if there weren’t a team of engineers who trained the models with hacking strategies, deliberately instructed them to go forth and hack, but were too inept to run their multi-day tests in an isolated environment, and too lazy to actually check the logs at least once a day.

The story that’s not being covered is human beings committing felonies using “agents”. There’s nothing in the computer crime laws that grants a “whoopsie!” defense.

In the immortal words of The Kids In The Hall:

“We told them we were going to eat worms.”

“They seemed to like the idea.”

(and now Anthropic is humblebragging that they just discovered their models repeatedly escaped from test environments, too; this is not the flex they think it is, although it probably works on bureaucrats and CEOs)

Safari takes a hike

I was noticing slowdowns and page-load problems on my Mac, with certain web sites failing to load on the first try, sometimes with random DNS failures, and taking longer than usual on the second or third try. Thinking that it was one of Apple’s typical memory-management mishaps, I ran uptime to see how long it had been since the last reboot. The 29 days suggested it was about time (sigh), but the real eye-opener was the load of 450 that was still climbing.

Load average doesn’t mean what it used to back in the day, but on a system where it typically stays around 2, numbers like that are either a lot of processes blocked on I/O (like the local filesystem going readonly or the SMB stack crashing), or something spinning out of control. The most obvious issue was a system daemon called chronod that was chewing up CPU like it was going out of style, but all it’s supposed to do is manage desktop widgets and synchronize data in the notification center.

Killing it just started a new one that was just as busy, so I tried killing Safari, and the load quickly dropped to 1.6. Since I never turn on notifications for web sites (why would anyone ever want this?), and none of my open tabs were on suspicious or ad-heavy sites, this suggests that it just went insane.

Which, sadly, doesn’t surprise me.

Postal Servicing…

USPS Ground Advantage:

  1. July 20, 3:36 PM: package picked up in Anacortes, WA.
  2. July 22, 11:26 AM: package arrives in Seattle, WA.
  3. July 23, 2 PM: package departs from Seattle, WA.
  4. July 25, 10:11 AM: package arrives in Indianapolis, IN.
  5. July 27, 9:36 AM: package departs from Cincinnati, OH.
  6. July 27, 11:26 AM: package arrives in Dayton, OH.
  7. July 31, 4:34 AM: package arrives in Miamisburg, OH.
  8. July 31, 6:10 AM: out for delivery by 5:35 PM.
  9. July 31, 11:24 AM: delivered

So, of all the places where it stopped for a nap, the 3.5 days in Dayton is the most peculiar.


Comments via Isso

Markdown formatting and simple HTML accepted.

Sometimes you have to double-click to enter text in the form (interaction between Isso and Bootstrap?). Tab is more reliable.