It may come as a surprise, but this phenomenon of "uninterpretable" circuits designed by algorithms is 30 years old now.
Adrian Thompson's research in the 90s evolved FPGAs that did signal analysis with bizarre features:
- A tiny number of cells (far fewer than expected)
- No clock, despite performing signal analysis
- FPGA cells that were logically disconnected, but when removed caused the device to stop working
Even then their approach was taking advantage of the physics in the FPGA. One can only imagine how effective this could be when applied to circuit design with the compute budget of a frontier lab.
Those "evolved" FPGAs weren't much of a mystery. They just used undefined parameters (inductive coupling, power supply rail glitching, etc) to achieved the trained outputs. They didn't work when the ambient temperature changed, or when moved to another example of the same FPGA.
Right, but it has many knock-on effects unfortunately. For example, it propagates to web content and causes some sites to break because they don't test with animations disabled.
Specific extension I use that became unusable (black text on black). However, if you look closely, you’ll see a lot of differences in look and feel that don’t seem “animation” related.
The conventional wisdom in cryptography is that if you don't know you need FIPS, if you don't have paper and a dollar figure telling you how much you need it, you don't need or want FIPS.
FIPS just locks you into a specific (generally fairly old) version of everything and sets some more annoying defaults. The only benefit is to be able to check a box on a form saying you qualify.
Could you explain what a git trailer is if not appended to the message body? My understanding is that trailers are just key-value pairs in a particular format at the end of the message; there's not an alternative storage mechanism.
Even so, trailers or message body might be moot - rerolling the committed at timestamp should be sufficient!
OCI artifacts, using the same protocol as container registries. It's a protocol designed for versioning (tagging) content addressable blobs, associating metadata with them, and it's CDN friendly.
Homebrew uses OCI as its backend now, and I think every package manager should. It has the right primitives you expect from a registry to scale.
A lot of folks think this, but did you also implement EDNS0?
The golang team also thought DNS clients were simple, and it led to almost ten years of difficult to debug panics in Docker, Mesos, Terraform, Mesos, Consul, Heroku, Weave and countless other services and CLI tools written in Go. (Search "cannot unmarshal DNS message" and marvel at the thousands of forum threads and GitHub issues that all bottom out at Go implementing the original DNS spec and not following later updates.)
This also happens on switching virtual desktops, even with reduce animations there is a 100ms+ delay before any input on the new desktop will be sent to the correct app.
Adrian Thompson's research in the 90s evolved FPGAs that did signal analysis with bizarre features:
- A tiny number of cells (far fewer than expected)
- No clock, despite performing signal analysis
- FPGA cells that were logically disconnected, but when removed caused the device to stop working
Even then their approach was taking advantage of the physics in the FPGA. One can only imagine how effective this could be when applied to circuit design with the compute budget of a frontier lab.
https://cacm.acm.org/research/analysis-of-unconventional-evo...