Avamander

How does it not follow? The Wikipedia article even lists ionizers as a separate article.

I recommend comparing what it rewrites to something that Gemini models output. I think there's still a lot that Anthropic could improve.

No, they use significantly higher voltages to actually have small pollutants precipitate. Ionizers tend to not go that far.

It's less obvious but it's still there. For starters it loves to anthropomorphize everything, it excessively uses verbs that shouldn't be used with inanimate objects and concepts. Not the only issue though.

All Anthropic models write like that since Opus 4.8. Opus 4.8 was still tolerable.

Unfortunately only Gemini models can write text that isn't vomit-inducing.

Fairly sure that if the correct GPOs are set, there is no need for any shell commands needed for a TPM PIN enrollment.

Windows and macOS both can do FDE with good UI/UX compared to Linux.

It doesn't really require a coherent light source, although that does allow further miniaturization.

That site is horrible to read and doesn't respect my zoom level at all.

There are also electrostatic air filters, but those tend to need an activated carbon stage to be actually good all things put together.

IKEA has a few air quality meters. Good accurate sensors are rather expensive however, for both particulates and CO2.

At this point I think with a bit of iteration the end result would quickly exceed that of an usual Blu-Ray player or TV firmware. Hardware manufacturers have shipped slop code before we called it slop code.

That's a fun statement. I think we already had vacuum tubes and other foundational components that would in theory have allowed someone to build a CD player a 100 years ago or very close to that. If they would have had the knowledge.

For starters, CDs are not very dense, you can see the data with a microscope: http://www.pmonta.com/compact-disc-microscopy.html

CD players came out in 80s, so one could say I don't need electronics made after the 80s to play those. Do those 20 years matter that much? I doubt it.

> I would bet good money that the amount of people with Glasswing access doing actual Blackhat work is currently zero.

I think it's not "blackhat" in that sense because it's officially sanctioned. Same goes for equivalent models overseas.

The only thing these embargos achieve is giving massive nations a huge advantage, but leaves the average country and person exposed.

I'll give it that, though the size in general is a downside for more people than it is a benefit.

> So that would be career cybersecurity experts with Project Glasswing/Daybreak/Googlewhatever access.

Yes. You really think access those models will not be given for offensive operations in each country? Of course they will be.

I really hope not, there isn't a single redeeming quality to vinyls from any practical point of view.

The PS5 optical drive is still incapable of handling Dolby Vision, which is a massive shame.

Because that's their concern, a civil case in addition to a criminal one? Not really.

> Well, and I am genuinely curious here, wouldn't defender and attacker capabilities being accessible equally by both parties be objectively worse than having a limited amount of privileged defenders?

Well, not really. Because those privileged defenders will never be able to predict what needs defending. So we have a few privileged "defended" places and the rest is left for privileged attackers to plunder.

Yup, insanely low 5-hour limits.

I have gotten the same impression, great at writing text. Horrible with code and the CLI interface is unbelievably bad.

Why would or should their privacy be a concern of theirs in the first place? It's a leak.

That's the wrong metric as it ignores the effort people put into securing these ecosystems. Vulnerabilities per kloc would be more reasonable.

The release should've been done sooner once it was clear the embargo was broken and people figured out the vulnerability.

You can't do secret releases, people will figure out what you added or changed.

But they could have accelerated the patch release once the embargo was broken and rumors of a PoC started going around. There was no need to wait 12+h today until the release.

> What platform hasn't had security issues?

That's reducing things too far. "What car manufacturer hasn't had car crashes?" All cars are equally safe?

There's a vast difference between different languages and CMSs and how likely it is for critical flaws to occur. PHP has a horrible track record and continues to surprise us negatively.

PHP is worse in this aspect with its long tail of legacy and staying close to C. It's absolutely possible that memory-unsafe Python interpreters could have something vaguely similar, but it's much less likely. Plus there are Python interpreters in memory-safe languages.

In any case, memory-unsafe codebases will continue to be a significant danger. Be it in interpreters or anywhere else. Just like they have been for the past 20+ years.

"No way to prevent this" say users of only language where this regularly happens.

I think this one more great example what kind of a liability and ticking time-bomb memory-unsafe code is.

Some error code being used? FIPS mode gone wrong?