They aren't actually shipping the new RP2350 silicon revision on Pico 2 boards yet. If you want the errata fixes, you've gotta source the chips and make your own boards.
I toured a sorting facility in Seattle recently. They said the only really profitable output is aluminum, everything else costs more than virgin material.
I worked at a plastic furniture manufacturer in Indiana for a few projects.
They got paid to accept bales of recycled "HDPE" that they could mix at between 10 and 30% into their virgin materials. They get paid to accept it! Negative profit for the waste management company, pure profit for the "user".
This worked best on black, coffee, slate grey, mahogany - you get the idea - the whites and tans and bright colors were basically pure virgin material (and their own internally-recycled offcuts of dyed virgin materials of matching colors) even though their FAQ states:
> What percentage of recycled materials are used?
> The percentage of recycled materials in our lumber can vary depending on the availability of post-consumer and post-industrial plastics. We continuously strive to maximize the use of recycled content in every piece of lumber.
Personally, I don't think that the fact that you started with pure virgin material, extruded some plastic, cut it up and used most of it, but put some of what was virgin material a few hours ago back into the grinder and extruder makes the resulting plastic "recycled".
It's 100% recycling, if the alternative was just "throw away the excess". For all practical purposes, recycling just means "repurposing material that you would have otherwise sent to a landfill".
My understanding is that glass gets downcycled into a lot of products like concrete or asphalt or aggregates. It's not profitable, but it's really easy to provide at a low loss.
With the exploits published as-is, you'll only get root inside the container: there's no explicit namespace break, and calling setuid() in a container just gives you root in the container.
However, it can be used to modify files that are passed into the container (e.g. Docker run -v), or files that are shared with other containers (e.g. other Docker containers sharing the same layers). kube-proxy with Kubernetes happens to share a trusted binary with containers by default, which is how it can be exploited: https://github.com/Percivalll/Copy-Fail-CVE-2026-31431-Kuber...
You don't need any setuid binaries. You could just as easily use the vulnerability to add a job to crontab(5) that causes the cron daemon to run whatever you want as root.
Similar to me, I learnt some html tags through a book which was sold at newsstand, once I was at my cousin's house using her computer without internet access, then I wrote a simple html page with the Win 95 cloud wallpaper as background image. My cousin was terrified how I did that!
imo, the real value of Ada/SPARK today is that it enforces a clear split between specification and implementation, which is exactly what your LLM needs.
You define the interface, types, pre/post conditions you want in .ads file, then let the agent loose writing the .adb body file. The language’s focus on readability means your agent has no problem reading and cross referencing specs. The compiler and proof tools verify the body implements the spec.
This is pretty standard for specification documents, probably more accurate to say AI sounds like them than the other way around.
Ignoring the particular technologies used (OAuth/JWT) it looks like they’re adding more auth to the devices themselves; think two computers connected to the same network switch not being able to impersonate each other.
reply