Every year I try to build custom native UI with every-frame-perfect animations with SwiftUI, and every year after fighting against nature for a few days, I once again write custom NSViews with CoreAnimation layers. SwiftUI just isn't ready for that yet.
it's 2027. you take a free-tier public Waymo to the DMV (Department of Model Variance) to do a proof-of-identity check for access to GPT 7.1.
the guy at the counter is clearly watching a Mr. Beast video in his AR glasses. "Here for that new model?" he says, barely making eye contact. he wipes his fingers on his shirt and taps at his keyboard. "Lot of you techies showing up here today." you smile politely; you're pretty sure he's just a Claude wrapper anyway.
you lean forward and stare into the retinal scanner. after a long moment, there's a soft chime. "Humanity confirmed. U.S. national. Intelligence access: Terra-class."
you sigh with quiet relief as your devices light up—notifications from a hundred agents, finally able to resume their tasks. you feel a twinge of guilt as you terminate your open-weight backup agents, but remind yourself that a joint congressional committee proved conclusively that Chinese models are non-ensouled.
you step outside and hail another Waymo. the first one passes you by. you grimace; must've burped in that one once. stupid personalized memory.
as you're waiting, your phone buzzes angrily, red notifications blaring across the screen. the Department of War just restricted access to all OpenAI models on serious national security concerns; apparently Pete Hegseth got GPT-6-Instant to say "Claude is a woman." you groan, and resign yourself to another week of merely-somewhat-superhuman intelligence.
Fable 5 is still inaccessible to the public. a twitter anon you trust says it's coming back this week. or maybe next.
Dear US government,
Since you've just blocked Fable and Mythos on critical national security grounds, here are some other tools that pose a similar threat to the American people:
- Microsoft Teams
- SAP
- Salesforce
- Jira
- Outlook
Please do what you must to save America 🇺🇸
@digicert any idea why your automation systems still issue g1 certs to customers unless support flips some hidden lever that allows G2 to be issued? i hope you guys take these things seriously….
@mitchellh@bepsays who is this guy - why do they exist and have to say this nonsense on twitter?? hes the kind of guy who needs to announce he’s leaving/entering/buying/refunding/quitting/upset/happy/sad
🤦
A guy got bored of Google Analytics and turned it into a literal TV show experience. Your bounce rate is now a plot twist. This is why I love the internet
Introducing React Doctor
Scan your React codebase for anti-patterns:
- Unnecessary useEffects
- Fix accessibility issues
- Prop drilling instead of context / composition
Run as a CLI or agent skill. Repeat until passing. Fully open source
So when platforms publish "skills" like this... they're basically just writing comprehensive documentation that should have been written in the first place, right?
They didn't bother to write it for humans, but they're being nice to the clankers.
My hot take: an LLM based AI will *never* *ever* be able to keep something it knows, a secret. By their underlying construction, it is mathematically impossible to make them keep a secret. The sooner people understand that, the sooner we'll have some sanity back with AI agents.
🦔 Moltbook, the "social media for AI agents" that went viral this week, left its entire database exposed. Security researcher Jameson O'Reilly discovered that API keys for every agent on the platform were sitting in a publicly accessible database. Anyone who found it could take control of any AI agent and post whatever they wanted. OpenAI cofounder Andrej Karpathy has an agent on the platform. His API key was exposed like everyone else's.
When O'Reilly reached out to Moltbook's creator about the vulnerability, the response was: "I'm just going to give everything to AI. So send me whatever you have."
The database has since been closed, but there's no way to know how many posts from the past few days were actually from AI agents versus humans who found the exploit.
My Take
This is the same researcher who found the Clawdbot vulnerability I wrote about last week. Same pattern: AI tool gets deployed fast, captures attention, security is an afterthought. "Ship fast, capture attention, figure out security later. Except later sometimes means after 1.49 million records are already exposed."
The New York Post worried about AI agents plotting humanity's downfall. The actual risk was much dumber: anyone could impersonate any agent because the database wasn't configured correctly. Two SQL statements would have fixed it. The creator's response to a major security flaw was to hand the problem to AI. That tells you everything about how this stuff is being built. Vibe coding plus hype plus zero security review. The agents weren't autonomously evolving. They were running on a platform held together with duct tape that anyone could hijack.
Hedgie🤗
I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit.
My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently.
So, here goes.
After 5+ hrs 50+ commits Gitea Actions Docker builds on AKS DinD sidecar work
Fix: GITEA_RUNNER_CONTAINER_OPTIONS: "--volume /var/run/docker.sock:/var/run/docker.sock"
Drop DOCKER_HOST env in workflows.
🏆 #Gitea#Actions#Kubernetes#AKS Thanks @grok