The only way to implement truly privacy preserving age verification is through zero knowledge proofs (or blind signatures) but what that would allow is undetectable token forging.
1,156 karma · joined February 24, 2023
The only way to implement truly privacy preserving age verification is through zero knowledge proofs (or blind signatures) but what that would allow is undetectable token forging.
Also, if the implementation is competently done the phone will show the website for which you scanned the QR code. A user would be able to see whether or not that matches the site where they observed the QR code and proceed accordingly. In time Google will probably integrate it into the Chrome browser where a proxied QR code cannot even be shown.
If more than a few percent of execution time is spent in Python you are probably doing it wrong.
Personally I don't even understand why Cython is a thing, just write performance critical functions in other languages:
<https://pypi.org/project/rustimport/>
<https://pypi.org/project/import-zig/>
Note that you can even start threads in those languages and use function calls as pseudo-RPC. All without an overly complex build system.
Remote attestation doesn't use blind signatures (as that would be 'farmable') so tying the device to the 'attestee' is technically possible with collusion of Google servers: EK (static burned-in private key) -> AIK (ephemeral identity key in secure enclave signed by a Google server) -> attestation (signed by AIK). As you can see if the Google server logs EK -> AIK conversions an attestation can be trivially traced to your device's EK. This is also why we don't really see and probably never will see online services which offer fake remote attestations, as it will be pretty obvious that the next step of running such a service is getting Google as a customer and having all your devices blacklisted. Private farms probably won't last long either as I'm sure Google logs everything and will correlate.
Unless something special is done with this new reCAPTCHA not only are you locking internet services behind TPM chips but you are also surrendering anonymity to Google. Unless you acquire untraceable burners for every service, the new reCAPTCHA will be technically capable to tying all your accounts across all these services together. Much like age verification. It may appear that the service would need to cooperate to link the reCAPTCHA session to your registration but the registration time alone will likely be sufficient (the anonymity set will be all but destroyed).
If you want to achieve lucid dreaming consistently you also have to develop a habit of doing reality checks. The most effective one is to pinch your nose and try to breath through it, in your dreams it will almost always work and the surprise is major.
Lucid dreaming even works for people with aphantasia: <https://en.wikipedia.org/wiki/Aphantasia>.
Also, remote attestation doesn't work that way and for good reason. Under a true ZKP system, a single defector (extracted/leaked/etc key) would be able to generate an infinite number of false attestations without detection.
It's not quite as dire as this. One of the main reasons why LLM's are getting better over time is that they are used themselves to bootstrap the next generation by sifting through the training set to do 'various things' to it.
People often forget that the training corpus contains everything humanity ever produced and anything new humanity will produce will likely come from it as well. Torturing it with current generation models is among the most productive things you can do to improve the next generation systems.
The brain likely has more in common with Reservoir Computing (sans the actual learning algorithm) than Deep Learning.
Deep Learning relies on end to end loss optimization, something which is much more powerful than anything the brain can be doing. But the end-to-end limitation is restricting, credit assignment is a big problem.
Consider how crazy the generative diffusion models are, we generate the output in its entirety with a fixed number of steps - the complexity of the output is irrelevant. If only we could train a model to just use Photoshop directly, but we can't.
Interestingly, there are some attempts at a middle ground where a variable number of continuous variables describe an image: <https://visual-gen.github.io/semanticist/>
The frequency of fireballs in our planet’s skies seemed to grow in recent months. NASA and other meteor experts can’t agree on what explains it.
... In response to growing public interest, a NASA public affairs official said in a blog post at the end of March, “While it may seem like meteor reports and sightings have been more frequent recently, it is not out of the ordinary.” The post explained that from February to April, there is often a 10 to 30 percent increase in the number of extremely luminous meteors — and nobody is quite sure why.
Mr. Hankey said that this 10 to 30 percent increase was already baked into the American Meteor Society tally, and that it doesn’t explain the apparent doubling of fireball sightings in the year’s first quarter.
<https://www.nytimes.com/2026/04/21/science/march-fireballs-m...>The notorious "it's not X, it's Y" pattern is somewhat rare from actual humans, but it's catnip for the humans providing the feedback.
Handwaving correlations between cheating/criminality and most personality/intelligence aspects is an error, not least because there is a selection bias problem (eg. who gets caught).
The people who get caught red handed like this are lazy, incompetent and stupid. Makes you wonder what about the ones not getting caught.
Also gVisor (aka runsc) is a container runtime as well. And it doesn't gatekeep syscalls but chooses to re-implement them in userland.
[1] <https://github.com/google/gvisor/blob/master/pkg/sentry/plat...>
One way you could probably do it is by identifying a commonly used library that can be misused in a way that would allow some kind of time-of-check to time-of-use (TOCTOU) exploit. Then you train the LLM to use the library incorrectly in this way.
You do this thing not because you expect consumers with 5 year old hardware to provide meaningful utilization but as a demo ("let me grab my old gaming machine and do some supercomputing real quick") and a signal that you intend to stay the course. AMD management hasn't realized this even after various Nvidia people said that this was exactly why they did it, at some point the absence of that signal is a signal that the AMD compute ecosystem is an unreliable investment, no?
A while ago, the autoresearch[1] harness went viral, yet it's but a highly simplified version of AlphaEvolve[2][3][4].
In the cybersecury context, you can envision a clever harness that probes every function in a codebase for vulnerabilities, then bubbles the candidates up to their callsites (and probes whether the vulnerability can be triggered from there) and then all the way to an interface (such as a syscall) where a potential exploit can be manifested. And those would be the low hanging fruit, other vulnerabilities may require the interplay of multiple functions. Or race conditions.
[1] <https://github.com/karpathy/autoresearch>
[2] <https://deepmind.google/blog/alphaevolve-a-gemini-powered-co...>
[3] <https://arxiv.org/abs/2506.13131>
[4] <https://github.com/algorithmicsuperintelligence/openevolve>
What you can probably do is create software which observes traffic and simulates it into the future and notifies the human ATCs about risks. It might even be a good idea to try and digitize it for the ATCs so they talk less and press buttons more (which will feed into the simulation) and use TTS for the legacy transmissions to pilots that don't have an updated interface. Given the regulation on that industry it seems unlikely anyone competent enough to do it will have an interest to even try.
How is the model relevant? The models are proprietary and you never see any of its outputs that haven't been watermarked.
If you assume competence from Google, they probably have two different watermarks. A sloppy one they offer an online oracle for and one they keep in reserve for themselves (and law enforcement requests).
Also given that it's Google we are dealing with here, they probably save every single image generated (or at least its neural hash) and tie it to your account in their database.
From the article:
Then, out of the blue, Satoshi appeared on the list with an email that neatly dovetailed with Mr. Back’s position. It was the first time Satoshi had been heard from in more than four years, other than a five-word post the previous year denying a Newsweek article’s claim to have unmasked him.
Many in the Bitcoin community questioned the new email’s authenticity since another of Satoshi’s email accounts had been hacked. But Mr. Back argued that the email sounded real. In a series of tweets, he called Satoshi’s observations “spot on” and “consistent with Satoshi views IMO” and took to quoting from the email.
Mr. Back was likely correct: To this day, there is no evidence to indicate the email was a forgery, and no other emails from that account have surfaced.
The Satoshi email sounded a lot like Mr. Back had in his posts during the preceding weeks, although no one took notice. Like Mr. Back, Satoshi argued that the Bitcoin network’s increasing centralization jeopardized its security. He called the big block proposal very “dangerous” — the same term Mr. Back had used repeatedly. He also used other words and phrases Mr. Back had used: “widespread consensus,” “consensus rules,” “technical,” “trivial” and “robust.”
At the end of the email, Satoshi denounced Mr. Andresen and Mr. Hearn as two reckless developers trying to hijack Bitcoin with populist tactics and added: “This present situation has been very disappointing to watch unfold.”
It also happened to be densely cited with hyperlinks:https://gnusha.org/pi/bitcoindev/6EC9DDF352DC4838AE9B088AB37...
https://x.com/adam3us/status/632928398893907968
https://x.com/adam3us/status/632650884011458560
https://x.com/adam3us/status/632923680104841220
https://x.com/adam3us/status/632919411112849410
https://gnusha.org/pi/bitcoindev/CALqxMTHfU5+1ezP-Jnn5obpd62...
https://gnusha.org/pi/bitcoindev/CALqxMTGBt7MNs5YWf8QzKe+4Fr...
https://gnusha.org/pi/bitcoindev/CALqxMTFC7zBN9GvHAZLQj4SbXj...
https://gnusha.org/pi/bitcoindev/CALqxMTFu6DRVMSLsGDa6AgVX1X...
https://gnusha.org/pi/bitcoindev/CALqxMTG7+MMN50VH9-Y++B1_De...
https://gnusha.org/pi/bitcoindev/CALqxMTGCkTZAs74bXk57L6JWK2...
https://gnusha.org/pi/bitcoindev/CALqxMTH_5rtOs=aSNiVrfsG_sq...
It's either Back or someone who tried to frame him, long before Bitcoin was even remotely successful. Generally, framing someone like this is a poor strategy because it places you in the person's radius as opposed to being absolutely anyone.
I would go a step further and posit that when things appear close Nvidia will stop selling chips (while appearing to continue by selling a trickle). And Google will similarly stop renting out TPUs. Both signals may be muddled by private chip production numbers.
> We study a novel language model architecture that is capable of scaling test-time computation by implicitly reasoning in latent space. Our model works by iterating a recurrent block, thereby unrolling to arbitrary depth at test-time. This stands in contrast to mainstream reasoning models that scale up compute by producing more tokens. Unlike approaches based on chain-of-thought, our approach does not require any specialized training data, can work with small context windows, and can capture types of reasoning that are not easily represented in words. We scale a proof-of-concept model to 3.5 billion parameters and 800 billion tokens. We show that the resulting model can improve its performance on reasoning benchmarks, sometimes dramatically, up to a computation load equivalent to 50 billion parameters.
They basically get gradient descent to optimize the KV cache while freezing the network.
I imagine for such a workload you can always solder a small memory chip to avoid having to waste L3 on unused memory and a non-standard booting process so probably not.
That decision was made before her win.
> the International Shooting Union, at a meeting in April of 1992, and therefore ahead of the Games, elected to bar women from shooting against men in future events.
<https://www.nytimes.com/athletic/2753773/2021/08/05/in-tokyo...>