Every time people hear what it actually involves is outrage and opposition, at least all the way back to when Intel first announced that they wanted to hardcode identity numbers inside CPUs in 1999. But the corporations involved have been relentless, and have sunk countless billions of dollars steadily forcing it forwards, and building front organizations to obfuscate and whitewash it.

With Windows 11, Microsoft was finally able to FORCE Trusted computing hardware into every new computer. Not just every new Windows computer, but every computer.

Every new Intel PC CPU has built in Trusted Computing enforcement hardware. Every new AMD PC CPU has built in Trusted Computing enforcement hardware. Every new ARM PC CPU has built in Trusted Computing enforcement hardware. The only processor lines that DON'T have it are the microcontrollers.

There are some unlocked smartphones available, but as far as I can determine it's literally impossible to buy a smartphone that doesn't have hardware trusted computing built in.

I specified that enforcing Trusted Computing at the internet access level is still a long term goal, they couldn't get away with it today. However they are well on the way to success. Virtually all new hardware supporting trusted computing, all the front groups rolling out standards and systems, and as it gets incorporated into things everyone is going to increasingly running into situations where they get locked out of stuff if they're not Trusted Computing compliant. Streaming already restricts you to the worst quality if you're not compliant, and it's only going to get worse as pre-Win11 computers fade out and as more things require it.

I'd hardly call exact date of birth "low information content".

And yes this does reveal exact date of birth, regardless of the bullshit obfuscation that it supposedly only reports age range. The server simply tracks the reported result every time the user connects, and on some specific day the result CHANGES to announce their date of birth.

-

This is based on SLSA (Supply-chain Levels for Software Artifacts), brought to you by the same fuckers making Trusted Computing and the TMP (Trusted Platform Module). It's part of the same shitstack to prohibit you from altering your software and to lock you out of your own files, and to send spy reports out over the internet so you can be cut off if you "fail" the Trusted Computing check.

The software can use a TPM's (Trusted Platform Module) Sealing function to encrypt your data such that it's impossible to access your own data if the software is modified. It can then pass control over that data only to software updates that carry a signed security certificate from Broadcom (or any other company using this system).

It is no longer open source, your system no longer works as you can no longer access your Sealed data if you change so much as a single letter of the code. Even recompile unaltered code won't work, unless you magically manage to get your build environment absolutely identical to the company's build environment and get byte-for-byte output. Even that may be impossible with the newer levels of non-deterministic compiler optimizations.

Also, with TMP's Remote Attestation feature can be used to transmit your machine's software configuration over the internet, so that you can be cut off if your system doesn't match Broadcom (or other company's) cryptographically signed certificate.

And then of course there's Network Access Control (NAC) / Trusted Network Connect (TNC). In the long term, the goal is for ISPs to use NAC/TNC to interrogate your computer for Trusted Computing compliance, and deny you any internet access whatsoever if your machine isn't compliant. Software with this sort of "security" certificate would pass inspection, while any attempt to alter the code would be detected as "tampering". You then get "quarantined". What "quarantine" means is that you are denied internet access - with the exception that you do get very restricted access which can only be used to download the approved software to "fix" your computer into Trusted Computing compliance.

I have been to all of the QC Snapdragon briefs, know the engineers personally, and have written about the shitshow on SemiAccurate.com extensively, basically I know what is going on. QC doesn't understand what they are doing and why, and there is ZERO internal impetus to change from the people on top. They do nearly nothing on software enablement because, "That is Microsoft's job". Drivers are intentionally locked down and encrypted to block Linux, and x86 compatibility is BETTER in hardware than the Mac Mx line (Same people who did the M1 and M2 did the X1 and X2, and they all just bailed on QC) but the software is.... oh look outside, there is a sky.

TLDR: No chance in hell there will be a fix.

                    -Charlie

Proprietary service drops support for proprietary protocol..

Nothing would make it “help get a little closer to making it a reality” if it’s not physically possible, and there’s a very strong argument that that’s the case. If nothing else, the maximum specific tensile strength allowed by covalent bonding - which is fundamental physics that we can’t change - combined with the reality of defects in a 36,000 km cable - is far below what’s needed to build a space elevator in Earth gravity. It might be possible to build a space elevator on the Moon or even (in the far future) on Mars, because their gravity is such that real materials could potentially do the job. But doing that involves bootstrapping an entire offworld industry, which is far beyond anything even the most advanced nations are capable of currently, let alone a technologically stunted oil state.

There’s no chance they’d actually succeed in building a space elevator. The Line is at least theoretically physically possible with current technology, even if it was always an obviously spectacularly bad idea. A space elevator is not.

We MUST be able to inspect and age verify every AI slop porn image to protect the fictional children!

-

https://en.wikipedia.org/wiki/...

If you read the article carefully, they are talking about lenses THINNER than a hair. I see several of the posts here thinking the width/radius of the lenses is this small, a reasonable mistake given the way this was written. Having a radius that small would severely reduce their light gathering ability, requiring very bright light or very dim images or very long exposure times.

-

Always interesting to see the fascist take. Oh wait... no it's not.

I agree. Questions like this often seem to come from people who don’t *want* to use AI, or perhaps are afraid of it for whatever reason, and they’re looking for reasons that they shouldn’t use it.

It was Andrej Karpathy, one of the world’s top AI engineers.

Description of the term: https://x.com/karpathy/status/...

About him: https://en.wikipedia.org/wiki/...

I’ve stopped arguing with people about it (mostly haha) for this reason. They’re either going to have to figure it soon enough without our help, or as you say be left behind.