Blaster M

The un-conspiracy-pilled response:

The CEL (Check Engine Light) comes on when the engine computer detects an error in the data from one or more of the engine’s sensors. It can be something as simple as the engine is stalled, or you forgot to tighten your fuel cap, and it can be something as severe as engine knock/misfire (typically the light flashes at that time), catalytic converter meltdown, or some other major hardware failure. Use any scan tool to check the codes, then lookup the codes to see what they are. It’ll give you a good idea of what is wrong with the car. Sometimes its a corroded sensor wire, sometimes the sensor has gone and disintegrated itself, sometimes there is a hardware failure in the engine and the sensor data is abnormal because of it. Use the Torque app and a cheap obd2 reader compatible with your car, or a dedicated code reader / scan tool from the auto parts store. You can also reset the light with the tool, but if there is an actual problem it will show up again after a bit.

Peer to peer running on Port 443, the standard port for https, as we do now using stealth vpns and such.

The Machine God, already?

So they used their hypervisor to clean wall reverse engineer how the apple gpu driver/firmware works, and then built their own half of the implementation. Yeah, it uses Claude for a lot of the rote work, but the fact that it even got done is impressive. They’re looking for people that can do code review/test/revisions now, to make sure the driver is solid and can be upstreamed. Also it’s a Rust driver.

If only we could do this in linux

It’s GrapheneOS. They always sail their own path regardless of flak.

red white and black

Ah, Mr. Beast… I didn’t know he had a book. I remember his vids. They were algo-hitting “do crazy stuff” survivor-like videos, along with philantrophy vids. Dude’s got issues, but rarely do you get a youtuber that’s super popular and isn’t a problem offscreen.

stealing public content

How does one steal what is public?

This article is about stuff that was private, yes?

Well, it is legitimately a good card

Why do I hear this quote in Mr. Regular voice?

Hoist by his own petard

Headline is a neuron activation lightning rod. Torvalds used the model to debug, the code is a one word fix he probably wrote himself.

This is the actual commit:

https://github.com/torvalds/linux/commit/818bebeb63dd6bf5f4e07e145f6cdbace520a34c

It fixes a goof where Intel Xe drivers allocate a few kb of memory that is used by the system during boot that causes the video to stop working. The fix is round_down() the memory allocation instead of round_up() the memory allocation. That’s pretty much the entire code change. round_up() -> round_down(). The commit message makes a lot of sense, and this bug is something you’d be spending a lot of time on manually debugging due to how insidiously subtle it is. Torvalds used the AI model to help debug the problem, but I’m pretty sure a one word change in code is not an AI generated code… and if changing one word is what the AI really did in the end, where do you draw the line at copyright? Challenging the copyright of individual words is impossible to enforce, because the word is used everywhere.

Of course.

There is a lot of government / intelligence agency interest in making sure devices can be hacked into… see the whole FBI vs. Apple thing from some time back.

Most device manufacturers are trying to keep costs down… adding security features adds R&D money they have to spend and pass on to the devices as sold.

Most people don’t know or care their devices are easily hackable… until it affects them personally.

Some people have to use GOS because enemy nations are targeting them and their devices in particular for hacking into, and normal devices are easy to break into… see Pegasus.

GOS is designed for maximum security at its base. It uses all the hardware features it requires to minimize its attack surface against adversaries that have infinite resources to attack the device and get at the infirmation inside.

Lowering those standards means opening a vulnerability, which means someone with that vulnerability can have their data stolen from the device in particularly that way, since that vulnerability is well documented.

amazing… I know of smaller models that specifically avoided that sort of thing because even negative training could go wrong so easily… they could have avoided that thing entirely, but nope…

I could understand if they were training a safety classifier (a model that learns what danger stuff is so it can recognize it when it sees it) but I doubt this is what they were doing here. That and handling such a radioactive dataset makes handing the demon core seem safe.

COLON THREE

Knowing that something rolled up just behind your car can be a saver in many ways… not running over surprise debris, for one, not hitting the neighbor’s anti-cut boulder on the edge of the grass that you can’t see when looking behind you for another…

We don’t need no thought control