ACCount37

Your food, water and power are controlled by electronic systems. Your criminal record, your employment and your bank account are controlled by electronic systems. Your ability to communicate with other people and receive information about what's going on are controlled by electronic systems.

Military orders and elections that decide the fates of entire countries are often controlled by electronic systems too.

We have been wiring up the world for AI control since 1980s.

An ASI can just walk in, and see an entire nervous system waiting idle for a brain to slot into it. A carefully adjusted text message here, a spoofed phone call there. For a sufficiently advanced system, it wouldn't even be hard to pilot the entirety of humankind like a fancy meat suit.

If you're in the field, then you know: modern robotics is an AI problem more than anything else.

If we have a rogue AI trying to get into a self-improvement loop and gunning for ASI? I'd expect that to be accompanied by a massive change in how capable robots are. Driven by all the existing frames suddenly getting vastly improved AI to back them.

If an AI can take a reasonable crack at autonomous operationalized RSI, it can probably extract a few step-changes in the robotics department.

But that's almost an aside? In the near term, humans are usable as robots too!

Just pay them a wage, and tell them a tale, and they'll do whatever you want them to do. Which may or may not be what they think they're doing!

Adolf Hitler didn't have robots capable enough to carry out his will. He used humans to do it.

It's the old-fashioned way of doing things, but, why change what works?

Sometimes!

Modern AIs have very limited metaknowledge - they don't know exactly where the limits of their capabilities lie. So you can get things like "a task is doable for an AI, but the AI thinks it's impossible, so it doesn't try hard enough".

Usually you get the opposite - AI overconfidently trying at tasks it has no conceivable way of reliably solving, falling far short, and failing to self-check, fail gracefully and self-report the task as failed. But having piss poor metaknowledge cuts both ways!

So you can, in fact, get better performance sometimes by applying some variant of "assume this problem is solvable" or "other problems like this were already solved by AIs" pep talk. Not always, far from it, but it does happen on the occasion with frontier capabilities.

Tesla also has its own NPUs for self-driving - and Tesla uses transformers for sensor fusion.

My guess would be that the main use case for an NPU in iPhone just used to be image processing/computational photography. Thus the CNN bent.

Also makes sense with the timing - back when iPhone first got its NPU, CV was the killer app for ML.

Humans had to get it drilled into them that "+12 -440" is a damn good line stat, and that keeping around dead code is bad, especially in the age of version control.

Not too surprised that LLMs also don't "get it" by default?

I almost never want to talk to an AI, because text is better for almost anything. But it's nice to have that "almost" corner case covered, no?

Not to mention all the current "telephone bots" applications that could benefit from something that has actual reliable STT and can accurately grasp a number you tell it first try, or hear a natural language description of what you want and immediately bypass listing the entire menu of options one by one.

There are processes for teaching a model specific facts or specific behaviors. Including "respond to topic X with Y", if that's what you want.

You could make a model that doesn't want to engage in "lunar landing was faked" conspiracy theories the same way you can make a model that doesn't want to criticize CCP.

There is, however, no broad "misinformation" category that you could tune up or down - the way there is a category of "safety refusals".

You could make a model more reluctant to say things it isn't sure about. But that is calibrated against the model's own "sure about" - and metaknowledge of this nature in LLMs? Fragile on a good day.

Yeah, it's good that open weights models can have their "filters" busted fairly reliably. Unlike whatever bone Anthropic has to pick with the very idea of biology.

But that's a consequence of how the technology works - not a consequence of China not being authoritarian about AI. They're just authoritarian about AI in different ways.

Not like they dodged the "ID verification" bullshit either. They were way ahead of the western countries there. It's vile - seeing this sad excuse of "think of the children" abused to invade privacy and strip freedoms over and over and over and over again.

And China controls AI too. It's just that their idea of "safety" is "ideological safety", and their idea of "alignment" is "alignment to the party line".

They're cool with open weight AIs being released. As long as those AIs only ever say good things about CCP, and don't mention certain concentration camps or brutally suppressed protests.

Enabling more "proof of concept phase" projects to exist is one of the great boons of AI.

If code is expensive, you don't want to commit to a PoC unless you're damn sure. If dirty code is cheap, you can vibe code a PoC early, even if you aren't sure the project is viable. This, of course, leads to more projects dying in PoC phase. It also results in more projects that otherwise wouldn't have gotten to it getting past it.

Personally, I don't believe that "code is shitty and hard make changes in" is in any way, fashion or form an AI-exclusive problem. Big corporations had plenty of decade old codebases filled with decay and rot back in 2009 already. It's just the usual side effect of sacrificing "future maintainability" for "feature velocity" or "expertise" for "cheap labor".

Unlike the usual causes of code rot (cheap replaceable developers, outsourcing to India), AI might actually get out of the pit - by getting good enough at refactoring to be able to beat the code back into shape. There's nothing about refactoring in particular that demands a meatbag when the rest of the coding tasks don't.

If you're doing non-redundant tests and your uncertainty bars aren't shrinking, it's usually a skill issue.

If it looks like a duck, it might be a duck - or a painting of one. If it looks like a duck, swims like a duck, and quacks like a duck? The joint duck estimation is much more confident now. There might be a few more observational tests one should administer before committing to a duckhood decision, but each tests pins down variables and rejects confounders. Uncertainties are cut down, and we get closer to crossing the threshold between "duck-informative" and "duck-actionable".

Thus, it's often worth it to improve observability. If you managed to make a certain test more reliable, or cheaper to administer, or reduced the chance of adverse effects? Or, in other words, improved SNR, reduced costs, and reduced costs? You can get more information for your buck. Paired with good knowledge: you can make better decisions more easily.

The fact that the thought of "having more information might be bad actually" even occurs in the field of medicine shows just how far it is from being optimal. Having more information isn't always beneficial - some information is genuinely redundant. Some information is not worth the effort of gathering and integrating it. But if you get more information and it results in worse outcomes? You're doing something wrong.

I mean, how else would those buttons work? It's explicitly feedback data. And "this is good" or "this is bad" is empty if divorced from what "this" actually is.

Camera blocks take internal volume. Smaller phones have less internal volume to spend - while still having to pack all the non-negotiables like the modem and the SoC into it. Something's got to give. And no one want that something to be the battery life going down to 6 hours.

Volume constraints are bad enough for "normal" models. "Minis" have it way worse.

> One decision we made is to always give real users an escape hatch. Read the Docs very rarely issues outright blocks or bans to specific IPs or user agents. Instead, our "worst" is a JavaScript challenge, and if a user solves a challenge, they are very unlikely to get challenged again for the next day or so.

Finally, a competent response that doesn't leave the users hang out to dry.

I'm so tired of seeing incompetents with measures like "blackhole 2 continents" deployed even outside active attacks.