National security letters or old boys network or maybe just fat bribes to the right engineer. Could be a requirement for government procurement too, so not a law, just the requirement of a huge customer with deep pockets and negative price sensitivity.
Counterfeiting was a big worry as high-resolution color printers became cheap. They did it motu proprio just like today ~all AI gen services watermark their outputs.
Unlike now, where instead of saying your hypothesis you're just letting every reader come up with what they think is a crazy conspiracy theory and ascribe it to you?
Failed social institutions are the source of all poverty in the world. The world produces enough of every basic necessity already. It's the distribution, not availability, where the source of hunger and depravity is.
Maybe not many, but some rather large. Say, Congo, or Sudan. But more often that would be not outright warlords but rather corrupt peacetime officials, who would try to extract or extort some additional personal / clan gain from something that could be a commonly accessible good.
Those are exceptions and can’t be used to characterise an entire continent. I have lived in areas of the continent with poor security and jihadist violence yet year in year out, fibre access kept expanding and getting cheaper. The corruption don’t stop rollouts, just make them more expensive and are not particularly to African countries.
Years ago, EVE corps swapped Unicode lookalike characters in patterned ways, inserted patterned zero width space characters, and put very slightly color shifted background watermarks into forum posts to detect leaks.
There are a few different things here. The actual steganography technique by Claude Code here is fairly smart and subtle; it's appropriate for a binary signal. The less-clever part is the implementation of the underhanded code on the client.
For "MMO geopolitics fingerprinting", you can in theory do the entire thing mostly or entirely from the server, with the client not actually ever receiving any underhanded code per se. Such as sending dynamic stylesheets that vary in a pretty plausibly deniable way that can be secretly extracted from screenshots. Same for the character swap stuff. A very good analyst could still potentially detect it, but it's much harder.
With this, there's the smoking gun of the semi-deobfuscated underhanded code in the client. It will always have to exist in some form, but you can write it in a way where it not just looks like regular code but actually has a believable purpose and behavior which could plausibly be normal and benign for implementation of a feature or telemetry or whatever. They did not really do it in a sufficiently "cleverly psyop-y" way, so to speak.
Consumers use these every single day in embedded devices without knowing it.
I wouldn't be surprised in the slightest if the embedded DDR3/DDR4 market greatly exceeds the number of consumer desktop computing devices in terms of "devices with memory" (not in sheer IC count or nominal size though.)
The level of design effort and PCB expense to go from DDR3 to DDR5 is enormous.
Only the oldest, most unique model years: nobody is buying (C4-C5-realistically C6) mid-90s or early 2000s Corvettes for more than what they paid for them, and they never will.
This already happens for basically every commercially-available ink cartridge.
reply