We should be legally allowed to shoot two babus daily
A statement issued by CERT (Computer Emergency Response Team) warns of a compromise involving eMudhra’s eight intermediate CA certificates due to weak cryptographic keys, which could allow attackers to issue fraudulent TLS certificates and intercept or modify encrypted communications. The advisory outlines mitigation measures, including security updates, certificate replacement where required, and verification of certificate trust chains.
Playing Super Mario and having to drop it after finding out the goombas use AI to move left and right
You’re seriously arguing that using machine learning to generate images based on previously obtained data is not generative ai?
It's insane how this book was published in 1995, and there hasn't been better material on NURBs modelling since.
Thought experiment:
If codex predicts my follow-up messages accurately, am I rly needed at that point?
If labs can perfect prompt prediction, won't the models just endlessly post-train on auto-generated threads to become intelligent beyond humancomprehension?
this has existed in claude for a while. the predictions are usually simple like go ahead, check x, etc.
chatgpt always ends at a question. it also just autofills the answer.
Internet censorship is getting worse (better, technically). I barely see any posts around the protest. Even the railway closure is not on my feed.
Goose: my latest programming language. Safer, faster and less memory than Rust/C++ for algorithms where tightly packed, flat data structures matter.
It can represent more kinds of data structures as flat, pointer-free bytes than any language I know.
github.com/aardappel/goose
1/
Was not expecting this.
'Ghosts of Departed Proofs' is my all-time favorite typed FP paper. Highly recommend going through it if you haven't.
If gdp-ts is as good as the tweet says, I'm moving most compile-time invariants to this.
Introducing gdp-ts: Ghosts of Departed Proofs for TypeScript.
gdp-ts is a library, linter and AI skill for safer API design. Under this contract, sensitive functions require 'proofs' that the caller performed an authorization check.
The typechecker verifies these proofs at compile time, preventing your team and agents from shipping catastrophic security (and other kinds of) bugs.
While these patterns have existed for quite some time, especially in ecosystems like Haskell, ① human code review and ② cognitive and syntactic overhead made these solutions niche.
The situation is now inverted. Agents are writing more code than we can review, and they *thrive* in tight loops with hard constraints that would frustrate us. We see this with the rise of Rust, borrow checker, code aesthetics debate and all.
The README and examples model a real-world Vercel API product constraint: changing the password on a Project requires a proof of a certain role + a certain entitlement. Thanks to Matt Noonan and Ollie Charles for their research in this space.
github.com/rauchg/gdp-ts
Agents are can now write ~100% of most code. And yet, knowing the implementation details in-depth *is* important.
Apps where devs don't care about code have a "smell". Your users can feel it. I've felt it myself while looking to switch text editors.
[1/n]
This is really simple and clever. Makes you wonder why culling didn't occur to competitive FPS/Mobas in all these years!
one of my favorite examples from my upcoming VLM OCR benchmark. thanks a lot to everyone who contributed data.
