Radar

Links, articles, and things I find interesting around the web.

Why I built this →

Mar 31, 2026

Whoa
J
Jeremy @Jeremybtc on X
Anthropic accidentally leaked their entire source code yesterday. What happened next is one of the most insane stories in tech history. > Anthropic pushed a software update for Claude Code at 4AM. > A debugging file was accidentally bundled inside it. > That file contained 512,000 lines of their proprietary source code. > A researcher named Chaofan Shou spotted it within minutes and posted the download link on X. > 21 million people have seen the thread. > The entire codebase was downloaded, copied and mirrored across GitHub before Anthropic's team had even woken up. > Anthropic pulled the package and started firing DMCA takedowns at every repo hosting it. > That's when a Korean developer named Sigrid Jin woke up at 4AM to his phone blowing up. > He is the most active Claude Code user in the world with the Wall Street Journal reporting he personally used 25 billion tokens last year. > His girlfriend was worried he'd get sued just for having the code on his machine. > So he did what any engineer would do. > He rewrote the entire thing in Python from scratch before sunrise. > Called it claw-code and Pushed it to GitHub. > A Python rewrite is a new creative work. DMCA can't touch it. > The repo hit 30,000 stars faster than any repository in GitHub history. > He wasn't satisfied. He started rewriting it again in Rust. > It now has 49,000 stars and 56,000 forks. > Someone mirrored the original to a decentralised platform with one message, "will never be taken down." > The code is now permanent. Anthropic cannot get it back. Anthropic built a system called Undercover Mode specifically to stop Claude from leaking internal secrets. Then they leaked their own source code themselves. You cannot make this up.

Mar 27, 2026

TRUE
K
KNOX @knoxtwts on X
found someone charging $9/month for personalized ai bedtime stories. 900 subscribers. pulling $8k+ monthly. the content is simple. ai generates a 3-5 minute story starring the subscriber's kid. kid's name, kid's favorite animal, kid's favorite color woven into a new story every night delivered via email. this person picked a niche where "made by ai" is a feature. parents don't care if ai wrote the story. they care that their 4 year old heard their name 8 times and is now asking for the doggy astronaut story again tomorrow. most people chase niches where ai tries to replace human quality. beauty content, fitness coaching, educational explainers. niches where the audience actively hunts for signs of fakeness and punishes it. the money moves are in niches where ai capability IS the product. personalization at scale. custom content per user. things a human literally couldn't deliver because writing 900 unique bedtime stories per night is physically impossible. other niches with this same dynamic: custom ai pet portraits from submitted photos, personalized workout plans based on body type questionnaires, ai-narrated family audiobooks from old letters and journals. the product is the personalization. ai is the only way it can exist at that price point.

Mar 6, 2026

Also found this post on hackernews: https://news.ycombinator.com/item?id=47281593
>As somebody who used em-dashes a lot pre-ChatGPT, I have genuinely struggled with feeling I should change my writing style to appear more human. I would be happy with a double dash--but many programs autocorrect that to a full em-dash. So I'm left anxious that people will think I find them so unimportant I have offloaded communication with them to an LLM. So this post resonated with me

This is so true! I still use em-dashes heavily in my natural writing, time to revisit that.
will-keleher.com this css proves me human I don't think I can build a fence with these posts...
This is the future I'd like to see..
linkedin.com Moving Product Planning to a Git Repo: Simplifying Workflow | Carl Edwards posted on the topic | LinkedIn I moved our product planning into a git repo. Not Jira. Not Notion. Not Google Docs. Markdown. Version controlled. Here’s what last week looked like: Pulled data from Jira, Amplitude, Slack, support. Drafted the cycle proposal. Had a planning call with our CEO. Fed the transcript to Claude Code. Minutes later: updated proposal. Priorities adjusted. Rationale captured. I reviewed the diff, made a few tweaks, merged it. Every decision now has a commit. Every shift has a diff. The whole team can see exactly what changed — and why. On a small team, leverage matters. Planning shouldn’t live across five tools. It should compound like code. I wrote up the full pattern — how we structured the repo, how AI fits in, and why this is working better than traditional PM workflows. Full post here: https://lnkd.in/gUiNEMha | 36 comments on LinkedIn