SwtCyber

I guess the key is that the encoder knows exactly what the decoder will reconstruct at each step, so it can compensate for previous errors when choosing the next palette entry

And predictable decoding time matters too

Feels like one of those cases where the ecosystem matters more than the underlying elegance

And what's interesting is that formalization doesn't just catch missing cases, it also forces you to examine all the assumptions that everyone has been taking for granted

I think you're basically right about the end goal yet the gap between a textbook proof and a Lean proof is much bigger than it looks

> Verifying that actions adhere to instruction correctly and will continue to do so in the future, even when improvising autonomously. This may be an open problem that has no solution, and is maybe the missing piece that would allow people to entrust AI to act on their behalf

Instead of trying to achieve perfect instruction adherence, it’s much safer to sandbox the execution environment at the infrastructure layer. If the container only has write access to a single scratch bucket, whatever weird improvisation the model comes up with is at least safely contained

I never really thought about how unreliable early mechanical clocks must have been....

The smaller providers on OpenRouter are probably popping champagne rn. With a framework like this in hand, the barrier to entry for LLM hosting drops even lower, so expect another wave of api price cuts for all no-frontier models

I love that we've reached a point where you can put an entire N64 level on your dining table and physically walk around it.

Exactly. I suspect the problem isn't just the amount of training data, but how much of the relevant information is missing from it.

I think the cross-language comparison would be interesting, although the bouba/kiki effect seems remarkably consistent across human languages already

The progression here is what impressed me most... You start with individual air molecules bouncing around and somehow end up understanding harmonics, interference and etc. Love this kind of articles!

I'd love to see that microscope hologram in person

The irony is that actual holography is arguably more impressive than the sci-fi version once you understand what's happening

Nothing stops it, except the fact that the agent is already executing arditrary code in your shell. If it's malicious, it'll just steal your shh keys directly instead of bothering with button masking

Apparently the secret to living 500 years is to move somewhere cold, avoid sunlight, and never be in a hurry

194 is the new 90 apparently

He's basically been networking for 194 years without ever leaving the garden

To be fair, he's had 194 years to work on his charisma. At this point it's a choice

I think that's a bit too reductive, but the incentive mismatch is real. Commercial apps generally benefit from people staying on the app; a government service theoretically benefits if people pair off and leave.

The nice thing is that the government has no reason to keep you swiping forever

I think the algorithm is almost a distraction here. Gale-Shapley works nicely when preferences are reasonably well-defined and participants are actually committed to the matching process. Dating has neither property. People are terrible at predicting who they'll have chemistry with, and everyone has outside options.

If this were a staged showcase of model capabilities they would have picked a more impressive target than a regional university digital library

Testing model capability boundaries is necessary, but a solid network sandbox for these evaluations takes a couple of hours to set up with standard infrastructure tools. No engineering team evaluates unverified systems against live third-party infrastructure without coordinating with the owners

Evaluating edge cases and network behaviors belongs in isolated staging environments with local database mirrors. Letting an agent hit the public web and probe government domains is simply poor hygiene in test environment setup

Give a task ownership of some state, communicate through channels and suddenly a lot of locking just disappears from the design

I think channels deserve more emphasis here too, especially because they change the architecture rather than just swapping synchronization primitives

One thing I appreciate here is treating scheduler fairness as something you spend, not something you get for free

For a programmer, deriving intervals and chords and then hearing the code produce them is a pretty effective bridge

I don't think the article needs to get you all the way from A to S to be useful. A Fourier transform doesn't tell you why a song is good either, but understanding harmonics can still improve your mental model of sound. Same with temperament, intervals or why a keyboard is laid out the way it is.

Yeah, this is the advice I wish showed up more often in "learn music theory" discussions