Richmond, Virginia
Joined December 2025
- Tweets1.2K
- Following276
- Followers87
- Likes1.4K
austin retweeted
If you're updating your versions of Node.js, PHP, Go etc, and notice your changes involve a lot of different version bumps, it would soon be a good time to standardize how you control this
I like using .tool-versions, which is read by most CI actions and dev tools like mise
austin retweeted
doing God's work
WE AUDITED ALL 58 FOREIGN-BORN FEDERAL JUDGES SITTING ON AMERICA'S BENCH FOR LIFE.
I spent over a billion tokens and about 45 days on this deep dive.
Through this deep dive and the over a million court cases we have combed through, we have launched an American First Index (AFI) for the site. (More on it as we improve the metrics and refine deeper.)
Out of 58 sitting foreign-born Article III judges, 43 were appointed by Biden or Obama. Among those drawn from ACLU and public defender pipelines, border enforcement is blocked over 80% of the time and 60% of criminal sentences fall below federal guidelines.
We have added an interactive tool on bench receipts that allows you to drill down and look at how each of these judges behave on the bench.
This is just the start. The federal judges are easier to identify than the state level judges. I assume there are 100s if not 1000+ foreign born or first-gen American on our benches.
They do not judge on our laws, they judge on the culture they came from. This is a huge reason our country has lost its identity.
austin retweeted
WE AUDITED ALL 58 FOREIGN-BORN FEDERAL JUDGES SITTING ON AMERICA'S BENCH FOR LIFE.
I spent over a billion tokens and about 45 days on this deep dive.
Through this deep dive and the over a million court cases we have combed through, we have launched an American First Index (AFI) for the site. (More on it as we improve the metrics and refine deeper.)
Out of 58 sitting foreign-born Article III judges, 43 were appointed by Biden or Obama. Among those drawn from ACLU and public defender pipelines, border enforcement is blocked over 80% of the time and 60% of criminal sentences fall below federal guidelines.
We have added an interactive tool on bench receipts that allows you to drill down and look at how each of these judges behave on the bench.
This is just the start. The federal judges are easier to identify than the state level judges. I assume there are 100s if not 1000+ foreign born or first-gen American on our benches.
They do not judge on our laws, they judge on the culture they came from. This is a huge reason our country has lost its identity.
if you vibe code with any agent tool: one api key per tool, a hard spend cap on each, and don't save keys in a hosted console you don't need. make sure you clean up today if you haven't.
If you use Claude Code or Codex, 𝗵𝗮𝘃𝗲 𝗶𝘁 𝗰𝗵𝗲𝗰𝗸 𝘄𝗵𝗲𝗿𝗲 𝘁𝗵𝗲 𝗔𝗜 𝗸𝗲𝘆𝘀 𝗼𝗻 𝘆𝗼𝘂𝗿 𝗺𝗮𝗰𝗵𝗶𝗻𝗲 𝗮𝗿𝗲 𝘀𝗶𝘁𝘁𝗶𝗻𝗴, today.
OpenCode disclosed an attack two days ago: AI accounts linked to it had their credits drained, and the Codex lead at OpenAI said today those credits were refunded.
The breach happened on OpenCode's servers. We took it as a reason to have Claude Code look through our own Mac without changing anything. OpenCode's login file from January was still there, holding 𝟰 𝘀𝗮𝘃𝗲𝗱 𝗹𝗼𝗴𝗶𝗻𝘀.
1. The login files for OpenCode, Codex and Gemini CLI live at ~/.local/share/opencode/auth.json, ~/.codex/auth.json and ~/.gemini/oauth_creds.json. For tools you haven't opened in a while, revoke access in their dashboard first, then delete the file.
2. Codex can keep its login in the system keychain: add cli_auth_credentials_store = "keyring" to ~/.codex/config.toml. Claude Code already keeps its login in the Keychain on a Mac.
3. Any key you export in ~/.zshrc can be read by every Claude Code or Codex session you start from that terminal. We had 𝟮 𝗼𝗳 𝘁𝗵𝗲𝗺.
4. We found 32 .env files across our projects, and none of them are in git. Anything committed and later deleted still sits in git history, and we haven't checked that part yet.
5. Set a spending cap wherever the dashboard lets you, and give each project its own key, so if something goes wrong you only revoke that one.
Have Claude Code build the same table for your machine 👇
"Check where the AI keys and tokens on this computer are stored, and don't change anything. Never show a value in command output or in your reply; to tell whether a token is hard-coded, only count matches with grep -c. Check each AI CLI's login file, whether Codex stores its login in a file or the keychain, CLI tokens like ~/.config/gh, env blocks in MCP configs, KEY/TOKEN/SECRET exports in shell startup files, .env files in my projects (whether they're in git or in git history) and .env files in build output folders. Put it in a table: location, which service, last modified, risk level and where to revoke it, highest risk first."
Everyone is pretty upset with this guy, but he's going to make more money than most indie hackers from his tactics.
everyone's running codex and claude code side by side. i run opus 5.5 medium on 5-10 projects and it lasts all week. pick one and get good at it.
if your mac runs hot for no reason, open claude code and paste this:
what's using my cpu right now and what starts at login? explain each one. don't delete anything.
someone on r/ClaudeAI found a crypto miner on 12 cores this way. takes 2 minutes.
500 hours in it's not vibe coding anymore. it's just coding with a different keyboard.
this is why i keep opus on medium. higher effort on everything is how you end up crying like this fella, and the few points of intelligence aren't really worth the tokens when you can iterate in medium a few times on your solution.
best beginner use of claude code isn't building an app. it's asking what your computer is actually doing. you might find some surprises!
This guy on Reddit asked Claude to build a small app that shows his Mac's temperature
The readings looked too high, so Claude checked what was using the CPU
His Mac was secretly running a crypto miner, using 12 cores and pushing the CPU to 112°C
The miner had been there since August, set to restart itself every time the Mac booted. His GitHub login on that Mac was exposed the whole time
Claude did not touch anything. It reported what it found and asked for permission to clean it up
He asked for a thermometer. Claude found what was burning his machine
Started a faceless YT channel: 30 days of 2 shorts/day scheduled + 2 long-forms/week. Also building a faceful channel teaching total beginners how to vibe-code correctly (1 long-form done, 2nd in progress). All with Opus 5.5 Medium, Remotion, Three.js + 3 custom skills.
AI coding is getting smarter and cheaper at the same time.
Each line is one model on DeepSWE, from low to max effort. Every curve runs flat, then shoots up.
Every few weeks that wall moves right and down. Today an open-weight model scores 77% for 20¢ a task.
This is the point of the deepseek release today.
We gave DeepSeek’s updated V4.1-Flash-1017 the same 100 pull requests with known vulnerabilities and an hour per PR to find them in the @BugBunny_ai VulnPR-100 benchmark.
It found 54 for just $7.53, making it the best-performing open-weight model on our leaderboard.
That matches Grok 4.6’s 54 findings at roughly 16× lower review cost. It also finishes only three findings behind Gemini 4 Argon while costing roughly 22× less.
The previous DeepSeek V4.1 Flash found 44 for $12.79. The update catches 10 more vulnerabilities while costing 41% less, bringing the cost down to just $0.14 per vulnerability found.
Better recall, lower cost, and the strongest open-weight result we’ve measured. Seriously impressive work from the @deepseek_ai team.
