The other Jon Stewart, not the one you miss. https : // bsky . app / profile / codeslack . bsky . social Github: jonstewart
In The District
Joined July 2010
- Tweets148
- Following284
- Followers900
- Likes165
Pinned Tweet
I deleted everything here. On the off-chance you need anything I tweeted, please contact me. See you elsewhere.
Jon Stewart retweeted
AI runs on electricity.
We can unplug it.
Thank you for coming to my TED talk.
More than 10% chance AI 'could kill all humans', Anthropic researcher says bbc.in/4gVCHnk
Jon Stewart retweeted
people in dc be like sorry you need to message me on this crazy encrypted app called signal yeah we do things a little 🤏 differently down here my handle is just my first initial hope that's not a problem anyway it's just for opsec but that probably went over your head heh...anyway here's the happy hour address
Jon Stewart retweeted
"AI is gonna shoot productivity to the moon - oh and also society can't afford to pay old people $2k per month anymore starting today"
The main thing I have to say to the young generation of Americans is that your grandparents and great-grandparents committed a kind of accounting fraud when they ran our country a century ago with social security, and at the time it was a reasonable affordance to grant our leaders, who were dealing with an economic depression and a world war, but nonetheless they did commit the fraud, and they ended up buying all sorts of extravagant things using the fraudulent gains, including what became the thing we now understand to be the high-modern technocratic nation-state, and that is glorious and also bad and all that, but the thing is there’s still the issue about the accounting fraud, whose debt is coming due and is coming due fast.
It is best to consider this with as minimal residue of sentiment as possible, to really sit with it, to stare it coldly in the face.
Unwinding the great fraud of the high modernists is your job, whether you wish it to be or not.
Jon Stewart retweeted
bulk_extractor 2.2.0 is out: a security and reliability release fixing CVE-2026-24857, with a standalone 64-bit Windows build, Windows raw-device input, runtime scanner plug-ins, improved Wi-Fi PCAP handling, and more.
github.com/simsong/bulk_extr…
#DFIR #DigitalForensics
Jon Stewart retweeted
(4 DAYS BEFORE SUBMISSIONS CLOSE) I get this question a lot about the Find Evil! hackathon: What does “find evil” actually mean?
In this case, the name comes from a real command. I built an autonomous incident response agent I built on the SIFT Workstation.
Then I typed “find evil” as a prompt into Claude Code.
And it did (watch the demo). I was blown away to watch the autonomous agent run a complete C drive forensic analysis, across 200+ tools via MCP.
The agent identified threat actor and context, the attack chain, malware deployment method, persistence mechanisms, code injection analysis, network connections, command-and-control (C2) infrastructure, a complete malicious process tree, and a chronological activity timeline.
Two days after I shared initial findings, Anthropic released their report on how threat actors were deploying Claude Code with operational tools and letting it go do evil. (Same thing I was doing.)
Find Evil! is the first hackathon dedicated to building autonomous AI agents for incident response.
4,178 defenders are working on final Find Evil! hackathon submits. (This number makes me very happy to see so many diving in. And wishing that the thousands more in our community were experimenting with us.)
Your job: teach an AI agent to think like a senior analyst, how to sequence its approach, recognize when something doesn’t add up, and self-correct when it gets it wrong.
There are FOUR DAYS left to build with us! (Very few of us are actual AI experts. The rest of us including me are learning.) Register: findevil.devpost.com
Apply to judge: We need DFIR, AI, cybersecurity, and open-source reviewers who can separate useful autonomous response tools from polished demos. Apply: findjudges-9kvkxt6m.manus.sp…
I am SO EXCITED to see what comes out of this hackathon and goes back to the community.
Sponsored by @SANSInstitute
Somewhere @junyer is putting down his drink and composing a retort about those who'd use his work as engagement bait.
e.g., "In terms of Brzozowski, this is gówno!"
A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS
36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes.
-> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text.
That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly.
Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am.
Everyone copies regex and prays. This is the talk that ends the praying.
Save it. The next time a pattern "Just works," you'll actually know why ↓
Jon Stewart retweeted
No one:
Claude Opus 4.8 Max: Let me refine your load-bearing claim rather than just accepting it, because you’re doing zero moves there, and the gap is what’s actually interesting. The one place I’d still push, because I think it matters: your message is wearing content-clothes, but the content isn’t actually *there*. The tell: it’s just an empty string. But the emptiness of the string IS its lack of content. Pull one, and the other goes inert. That’s the structural spine.
Jon Stewart retweeted
with some perfsplaining about how Linked List's Aren't Really That Great After All (helpful, as if I haven't been working on latency optimizations since before most Rust fans were an itch in their daddy's pants) - gave me a "this language can't *possibly* be it" vibe:
I've pretty much wasted the past decade of my life building cursed open source dependencies in a CI pipeline when in 2002 I'd've just committed the DLLs to CVS and been done.
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
on-trend for 2026, Hot Supply Chain Summer
so chopped
We are investigating unauthorized access to GitHub’s internal repositories. While we currently have no evidence of impact to customer information stored outside of GitHub’s internal repositories (such as our customers’ enterprises, organizations, and repositories), we are closely monitoring our infrastructure for follow-on activity.
