Koffiepoeder

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.

Can you give me some pointers?

Last I heard researches simulated an entire brain of a fruitfly with just a classic neuron approach [0] and if I recall it worked great.

I know a human brain is many orders of magnitude more complex, and that there are some birds that use quantum navigation - so it's certainly not impossible by any stretch, though I am quite interested in this statement since it's the first I hear about it.

[0]: https://flybrain.app/

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.

I would be more concerned for remotely triggered inverter spikes tbh. These could sabotage the whole grid if I'm not mistaken.

Reminds me of this (by now completely outdated) middle east friendship chart I once came across.

[0]: https://www.slate.com/blogs/the_world_/2014/07/17/the_middle...

Working with agents and current-generation coding tools to me still feels relatively cumbersome. You have to do a lot of /manual /skill invocations and go through many review cycles before I consider code even close to workable, let alone commitable. I believe orchestrating this whole ordeal can probably be automated/improved through making good use of coding pipelines, thereby reducing manual intervention in the coding phase itself.

So, to minimise reviewing and AI oversight efforts, I was looking for a good way to orchestrate my local pi agent fleet. I found 'synapse' via this Reddit thread [0], in which the author (not me!) also asks for feedback and collaborators. The tool seems very interesting/promising to me!

Final note: I do _strongly_ believe that supervision of the coding process is still a _strict_ necessity. It's just that I think it can probably be more streamlined.

[0]: https://www.reddit.com/r/artificial/comments/1slu8m1/i_built...

Rohansi was basically asking 'why', you keep on reiterating that DDR uses more power than LPDDR, but fail to answer why this is the case. Is it clock speed? Is it voltage? Is it a protocol/specification difference? 'various reasons' is not an answer.

You did not answer the question.

I understand trimming input fields is typically a useful default, but in this case this prevents me from searching for a space. So maybe it'd be worthwhile to add a `if (trim(str)=="") return str` exception or something similar?

Imagine my face when I had to take periodic backups of stateless, immutable read-only filesystem, non-root containers for "compliance".

To be honest, I would even go further: if you think certification equals security, you are even more lost.

So many controls are dubious, sometimes even actively harmful for some set-ups/situations.

And even moreso, it's also perfectly feasible to pass the gates with a burning pile of trash.

Can confirm. Have encountered many on-prem and lift-and-shift solutions with no automated means of updating certs. The worst contenders are usually 1) executables on windows server (version 2012, of course), 2) old, obscure or very outdated database servers and 3) custom hardware firewalls. They are the worst.

To make things easy they usually all use different cert formats as well, requiring you to have an arsenal of conversion scripts ready.

(Note that if OP considers to do this, they probably want to do this in a private tab, as to not leak potential sensitive cross-site cookies)

We have an OCR job running with a lot of domain specific knowledge. After testing different models we have clear results that some prompts are more effective with some models, and also some general observations (eg, some prompts performed badly across all models).

Sample size was 1000 jobs per prompt/model. We run them once per month to detect regression as well.

Do you mean attacking a second country in the top 10 oil/gas reserve ranking in mere weeks, while threatening to invade a third?

The A3B part in the name stands for `Active 3B`, so for the inference jobs a core 3B is used in conjunction with another subpart of the model, based on the task (MoE, mixture of experts). If you use these models mostly for related/similar tasks, that means you can make do with a lot less than the 35B params in active RAM. These models are therefore also sometimes called sparse models.

Exactly there's so much stuff you simply cannot configure otherwise. For example disallowing applications to take sole ownership of a mic, in-detail power plans, etc. If they remove the old control panel, your machine basically becomes unconfigurable.

Had to search a bit, but here's a demo page: https://maplibre.org/maplibre-gl-js/docs/examples/display-a-... Can be compared with: https://maplibre.org/maplibre-gl-js/docs/examples/display-a-...

In that example I saw this in the console:

    before - 2.41+26.29+24.87+71.28+59.2+77.57 - 261.62kb
    after  - 2.45+22.4 +22.66+60.6+51.99+77.57 - 237.67kb

So roughly a ~10% compression improvement, neat!

For those interested in browser differences, on my machine:

Firefox

  AoS: 2951.00ms
  SoA: 1624.00ms
  Interleaved: 1961.00ms

Chrome

  AoS:         2133.30ms
  SoA:         884.30ms
  Interleaved: 1457.60ms

Seems the interleaved being slower is consistent across browsers!

Additionally, solar panels can become too hot and that reduces their efficiency. Also, deserts are famously known for dust. Since it rarely rains, you get a dust buildup, further compromising solar efficiency in deserts.

I'm not saying that deserts are a bad place for solar. What I'm trying to say is - it's often worse than people think and it requires special infrastructure.