Koffiepoeder

The PHP thing is exploitable by now. No specific conditions needed. Stop spreading misinformation.

I think their point is more on the fact that just proving something is only half the work. Intermediate results and proofs are often also of immense value. Right now the output is sloppy proofs and LEAN code. This is useful, but a large part of the effort still lies ahead. And if you are a mathematician you'd rather be working on hard problems than fixing slop.

Can potentially have private networking advantages, e.g. internal api's.

Changing copyright durations without touching patent law is useless. In your example we would also need to shorten software patents to e.g. 3 years. Otherwise the big fish will just create a patent maze.

For me something the likes of: design a CDM for integrating these 5 logistical systems, with full docs and examples provided for each, as well as modeled transports specific to our business. Prompt was of course much longer.

Both failed spectacularly. But sol's output at least contained interesting findings and some useful parts, as well as not being 20000 words of unbearable language.

In my own veg garden, I have noticed that my soil quality starts degrading around >6% of carbon contents.

It wasn't a problem until recently, but with all the droughts in recent years, too high carbon can make it hydrophobic and lead to water run-off that happens too quick once it has entirely dried out. I.e. it becomes too lose/aereated. This then means that the occasional heat storm no longer replenishes water reserves and you end up a bit wirh the same problem as if you had 1% Carbon.

My soil is still way more resilient at the beginning of the drought (I can easily cover 1mo eithout rain without having to water most crops, except some smaller spices). But in recent times I have stopped mulching for a while.

If only they would update it to work with their remote development kit... One can keep dreaming right :)

Or when their papers are retracted for political reasons.

I once came across a similar "solution". The signing algorithm was directly executed from the update package. How would we otherwise be able to update the signature algorithm? Worst part was that it was correct at some point. It was an introduced regression because of a signature change due to " post-quantum safe" signatures now being required by the security team.

Hey dipshit,

Maybe I develop games. Maybe I develop IoT devices. I might even be working in a high-stakes environment where formal verification is needed, who knows.

Whatever the case may be, we all have our reasons for choosing certain technologies. Not everyone is building run-of-the-mill 'backends' after all.

So please, let's stuff that neckbeardy arrogance away. It serves no purpose and distracts from the discussion.

Thanks.

P. s. I develop my backends in go.

Thanks for the recommendation. This is very close to what I am looking for, at least with regards to the CLI.

The networking part I can fix with a second docker container and network_mode I think.

The centralised key and permission management and agent dashboarding is severly lacking though. But that's for now my least worry I think.

Slightly related: I am looking for:

- Easy single command CLI agent spawning with templates

- Automatic context transfer (i. e. a bit like git worktrees)

- Fully containerised, but remote (a bit like pods)

- Central, mitm-proxy zero trust authn/authz management (no keys or credentials inside the agents), rather enrichment in the hypervisor/encapsulation

- Multi agent follow-up functionalities

- Fully self hosted/FOSS

Basically a very dev-friendly, secure, "kubernetes"-like solution for running remote agents.

Anyone has an idea of how to achieve this or potential technologies?

Also this would not account for cooling shrinkage, a very annoying problem when making high quality parts to spec.