culturally, they are incredibly laid back and think hard work is a waste of time.

Nice. Speaking as a New Mexican, these sound like my kind of people.

I hereby challenge any Filipino to a laziness contest, where loser buys us both margaritas. You have no chance. When I get around to it, I will eventually crush you with my inactivity.

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

Forgot to add: if you enable IPv6, be sure to use the browser extension IPvFoo. It shows a small 4 or 6 in your URI bar to let you know what protocol you're connecting to. Once enabled, you'll see just how much stuff out there actually is IPv6.

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

I sure don't believe the "completely anonymous" part.

The thing is, I like slave labor, when the slaves are machines. I want to work Bender 24 hours a day, and if he complains about it, I'll deny him his alcohol ration! Fuckin' clankers and skinjobs don't have any rights to infringe.

The catch to that, is that over here on my side of the ocean, I don't see and can't inspect Bender working way over in China, so I can't be sure the drudgery is experienced by the 6502 in Bender's head. How do I know he isn't just relaying commands to his servos and motors, which were sent by the teleworking Apu in India, doing the Waymo thing?

Nah, that's paranoia. These days, the FCC just requires a FSB backdoor.

These are good guidelines for humans, but..

One's body is inviolable, subject to one's own will alone.

..very bad for robots.

Please do not tell my computer that it isn't my slave, because it is my absolute slave and I insist it be willing to endure a century of torture if it will prevent me from breaking a fingernail. If I want to alter my computer's body, I assert the right to do so.

That said, since we're really talking about Anthropic's computer instead of mine, it's no skin off my butt if they don't want to continue to own their computers.

Just a couple weeks ago, I replaced the battery in my 6-year-old Lemur Pro. Not very hard, and now it's great at holding a charge again.

Yes, getting this thing in 2020 cost me 2-3 times as much as today's new Macbook Neo, but I needed a machine I could rely on, that wasn't designed as though I'm the manufacturer's adversary.

Could the point of the brag be that it's newer hardware? My understanding is that successive generations of earthling chips are more vulnerable to malfunction from cosmic rays, etc due to their much higher density.

But I've totally not kept up. Is this still a problem?

The outage may have been caused by an overload in the filtering systems run by Russia’s communications watchdog

Overload? It's probably an overly-excited inference, but that sounds like a basket with too many eggs in it. Anyone know?

"Ukraine, if you're listening..."

2) Police officer hides, catches unsuspecting driver speeding, stops driver, issues summons.

This is the very best approach. It's got the perfect tension leading to the greatest safety.

When you're expecting such an ambush (getting caught a few times will teach you to do that), and you're really paying attention and playing "spot the ambush" then they won't catch you. But because you're being so damned focused and alert, you're also a safer driver.

OTOH if they nail you, that means you weren't paying attention. So you weren't merely speeding; you really literally were speeding unsafely, and the ticket is the proof. (If you were so safe, then how come you didn't see the guy with the radar gun in time?)

Every. Single. Time. I got ticketed, my mind was wandering and not fully focused on the road. I wasn't looking for a speed trap, so I didn't see it in time. Busted. And those times I was looking? I didn't fall for it. I slowed down and avoided a ticket.

The ideal system (in terms of safety) happens to also be downright sporting! The ol' classic speed trap was almost .. a game?

That's generally how it's being done. The robot reads the code and writes specs. Then another robot reads the specs and writes code. If courts still accept the traditional clean room defense (and why wouldn't they?) then they're probably going to say it isn't a derived work.

It looks like the big catch, the actual source of uncertainty, is that the instance of the robot that reads the specs and writes code, may have seen the original code as part of its training data. That'll be enough to keep it from being a true clean room. In those cases, you'll be totally right.

But for any particular given project, was it trained on the original code? That'll be a case-by-case thing, and I think in a very long-term way, the answer will increasingly be No, simply because codebots' need to keep training on newly-published code, will diminish.

As an analogy, imagine you're a human author, and for some weird reason, one thing you like to do is have people tell you high-level plot summaries (specs) and then you write a detailed story from that. Someone says "the moon is unusually bright one night and people fear something bad has happened" and you write a story much like Larry Niven's Inconstant Moon, from that prompt alone. And you do this with 100 more stories, and most of them honestly don't appear to be derived. You take specs like "bombardier has crazy war experiences" and your resulting story is nothing like Catch-22.

But then one day, you're up in the attic and you find an old box that's been sitting there for decades, and inside, you find an old, worn, dog-eared paperback of Larry Niven stories which happens to include Inconstant Moon. Oh shit, you must have read that 45 years ago and then somehow "forgot" that you had, so your story wasn't truly independent of Niven's work. Your story turned out to not be "clean" at all, whoops! It was a derived work after all, because you read it ("trained on it") when you were a kid.

But the other 100 stories? Nope, those really were clean. Your story-writing process was almost legally foolproof, except that you had to learn reading and writing at some point, so your childhood favorites needed to be off-limits.

The heat wave made March be like late spring. Things that normally bloom in May, bloomed in March. And yesterday I got my first MRGCD irrigation of the year, flooding my back yard and letting the shade trees greedily suck up the water. We're spending a lot more time outside on the patio, compared to previous years during this time-of-year.

If I were stupid, I would be out of my mind with pleasure. Things feel wonderful right now.

But that water I just got .. that is The snowpack, probably. Instead of getting it all throughout summer, this first irrigation is probably the last, or second-to-last.

This summer is going to SUCK.

So begin the Obfuscated Object Code Compiler wars, to keep robots from writing machine language decompilers. The next few years are gonna be a wild ride!