Conde Nast tops 564 ghosting reports with 4, and Anthropic cut 80% of Claude Code's prompt

A public board that names companies for going quiet after interviews took the Hacker News front page with 330 points. The counter on its homepage claims 564 approved reports. The company ranked number one for ghosting, Conde Nast, has four.

Within hours the thread had a verdict on the dataset, not the idea. A board whose top spot and bottom row are three reports apart cannot rank anything yet.

In today’s indie hacker news:

• 👻 564 ghosting reports, and No. 1 has four
• 🔍 Karpathy’s bio dropped Anthropic, his own site never had it
• 📛 Two years of nights, three rival MoneyMaps
• ☸️ The founder Kubernetes beat sees it happening again
• ✂️ Anthropic deleted over 80% of its own prompt
• 🛡️ Stack of the day: rules that stop agents wrecking working code

Top Stories

THE RANKING GOT RANKED

👻 A ghosting board hit the front page, then the thread audited its data

The story: Did They Ghost You? keeps a public record of companies that stop replying after an interview. Anonymous submissions, a moderator on each one, two leaderboards. It landed on Hacker News and drew 148 comments in about seven hours. Very few of them argued about ghosting. They argued about sample size.

The details:

• The spread: Salesforce, Microsoft and BJAK tie at three reports each. The bottom ten rows carry one apiece.
• The other board: the good communicators list is thinner. Every top entry shows one thank you, labelled “1 of 1 would interview with them again”.
• The moderation gap: one row points Robert Half at a google.com domain. The site promises a human reviews every submission before it counts.
• The scope fight: an application nobody answers doesn’t qualify as ghosting under the site’s own rules. Commenters argued that is where most of it happens.
• The demand is real: Greenhouse surveyed 2,500 workers across the US, UK and Germany. It found 61% ghosted after an interview, up nine points since April 2024.

The critique that stuck, from commenter lacunary:

“this is cool but the leaderboard is just going to converge on large companies unless it’s normalized somehow”

Why builders care: If your headline feature is a ranking, then volume and clean entity matching are release blockers, not polish. Launch before the math holds and the thread writes your teardown for free.

That same audit reflex turns up two stories down, pointed at a name instead of a dataset.

BIO EDIT, NOT AN EXIT

🔍 Reddit read a missing bio line as a resignation letter

The story: @karpathy’s X bio now reads, in full, “I like training large deep neural nets.” It names no employer at all. An r/LocalLLaMA post read that gap as a departure. The motive it offered: the company’s hard line on open weights. The post misspells his name and calls its own theory speculation.

His own website never played along. karpathy.ai carries a dated career timeline through OpenAI and Tesla that stops at a 2024 entry for his YouTube work. Anthropic has never appeared on it, so there was nothing there to remove.

The details:

• The announcement: he posted the job himself on May 19, and that post carries 27.8M views.
• The receipts: he was still boosting Claude Fable 5 on June 9 and quote posting the Claude Tag launch on June 23.
• The thread corrected itself: two commenters said he never left, and a third claimed the edit was 54 days old. Nobody sourced that date.
• The paper trail: TechCrunch reported he started on pre-training under Nick Joseph, and Wikipedia still lists the company in his institutions.
• The reach: the account behind one edited field has 3.5M followers and has been posting since April 2009.

The correction, from a commenter in the same thread:

“He didn’t leave. Only changed his bio”

Why builders care: If you build in public, your bio, your site and your last three posts read as one status signal. Leave a gap in any of them and strangers fill it with a story you didn’t write.

TWO YEARS, AND THE NAME WAS GONE

📛 MoneyMap shipped into a name three finance apps already hold

The story: MoneyMap starts a fresh budget period every time you get paid, instead of on the first of the month. Kevin is a software architect by day. He built it solo across two years of nights and weekends, around a day job and parenting. The launch post went up on r/SideProject. Financial data stays on the phone. His servers only pass through Plaid connections and run Stripe subscriptions.

The name is the problem. A different MoneyMap is already live on the Australian App Store. The same developer holds the Google Play listing under com.mb.moneymap. That’s the store Kevin’s Android build still has to reach.

The details:

• Namesake three: MoneyMap Expense Tracker sits on the Indian App Store from a different developer again.
• Namesake four: Skybound Wealth Management launched an adviser tool called MoneyMap, announced back in September 2025.
• The tell: his own Product Hunt badge resolves to the slug moneymap-2, not moneymap.
• The support bill: the sync key never touches his servers, so his site says support covers app-level issues only. He can’t see your data, which means he can’t debug it either.
• What is missing: no price appears anywhere on the site. There’s a seven day trial and one subscription per household, and that’s it.

Kevin, in the launch post:

“I’ve poured a lot of nights and weekends into MoneyMap, and I’m finally ready to start sharing it with more people.”

Why builders care: Search both app stores and your Product Hunt slug before you commit to a name. Do it early, not on launch day. On-device encryption is a real differentiator that also buys you a support desk which is blind by design.

KUBERNETES ATE HIS COMPANY

☸️ The founder Kubernetes ran over says open weights are the same movie

The story: Tobi Knaup co-founded Mesosphere in 2013 and grew it for years on Apache Mesos. Then Kubernetes took the platform out from under him. His essay argues open weight models are running that same play now. His lesson isn’t that open source always wins. Once an open platform becomes the center of gravity, no vendor keeps pace with everyone building on it.

The numbers back the shape of it. OpenRouter puts GLM 5.2 top of the open-weight index at 51, on MIT licensed weights. That is roughly five points under Claude Fable 5. Washington has not ruled out acting on Chinese open models.

The details:

• The scale: Chinese models took 41% of Hugging Face downloads over the past year.
• The price floor: DeepSeek V4 Flash runs $0.14 and $0.28 per million input and output tokens, roughly 150x under GPT-5.5 output.
• The catch: that first-party API routes through China and its terms permit training on your data. Western no-train hosts charge about double.
• Licences bite: GLM 5.2 and V4 Flash ship under MIT. MiniMax M3 wants written authorization before larger commercial use.
• Where the analogy breaks: you can read and patch Kubernetes source. Nobody hands you training data, and there’s no CNCF equivalent for models.

Knaup’s actual ask of Washington:

“America should not respond to open Chinese models by building a wall around its own developers.”

Why builders care: If a ban lands, it hits the models indie builders already self-host. Keep the serving layer swappable, and weights you already downloaded become the hedge an API key is not.

THE PROMPT WENT ON A DIET

✂️ Anthropic cut most of Claude Code’s system prompt, then shipped a tool to cut yours

The story: Anthropic published new context engineering rules for its Claude 5 generation models. The headline claim: it deleted over 80% of Claude Code’s system prompt with no measurable loss on its coding evals. What surfaced the bloat was reading its own transcripts. Inside a single request, the system prompt, the skills and the user contradicted each other. One example: “leave documentation as appropriate” against “DO NOT add comments”.

The details:

• The replacement: a block of comment rules became one line. “Write code that reads like the surrounding code: match its comment density, naming, and idiom.”
• Six reversals: rules became judgement, examples became interface design, everything upfront became progressive disclosure, and a hand-kept CLAUDE.md memory became auto-memory.
• The new command: /doctor rightsizes your skills and CLAUDE.md files. The post never says how it decides.
• The CLAUDE.md rule: keep it light and spend the tokens on gotchas inside the codebase. Skip anything the model can read off the file tree.
• The caveat: the deletion and the no-loss claim both rest on Anthropic’s internal evals. No suite is named and no scores are published.

Thariq Shihipar, who wrote the post:

“The number one rule for tool usage was to give Claude examples. With our newest models, we’ve found that giving examples actually constrains them to a certain exploration space.”

Why builders care: Maintaining a Claude repo just inverted from adding instructions to removing them. Run /doctor, cut CLAUDE.md down to gotchas, and drop the double-check scaffolding. The Opus 5 guide says those lines only buy over-verification.

Today’s Stack of the Day is a repo of rules for coding agents. Either the counterargument, or the next thing /doctor eats.

Trending Today

• 🔌 llama.cpp now speaks MCP for every protocol after a long effort led by ngxson. HTTP servers already worked in the client, and stdio servers were the piece that needed real plumbing. Local agents just got a lot less bespoke.
• 📄 A translated DeepSeek investor transcript landed on GitHub and pulled 106 points. The submission says the fundraise paused after Liang Wenfeng’s comments on the compute gap with the US leaked.
• 🗳️ Debian is voting on three LLM proposals with 105 points and 97 comments behind it. Whatever wins here sets the tone for every distro that has been quietly avoiding the question.

Stack of the Day

🛡️ claude-code-survival-kr

A rules file that tries to stop AI coding agents from breaking working code, posted to Show HN overnight. It’s a free GitHub repo with almost no votes yet. Treat it as unproven rather than endorsed. It lands the same week Anthropic argued the opposite case, which makes reading both worth ten minutes.

Not sponsored. We just feature tools builders would actually use.

Bookmarked Today

• 🔋 GM backs sodium ion batteries for US grid storage on a 149 point thread. Cheaper chemistry, heavier packs, and a use case where weight doesn’t matter.
• 🧠 Which small model do you actually run, and for what is one line. It turned into the day’s most useful local model thread.
• 🏋️ Reprise tells you what to lift next, instead of just logging what you lifted last time. Solo build on React Native, Expo, Supabase and RevenueCat, just live on Google Play.

See you tomorrow. Reply and tell me what you shipped this week.

Curated by AI, built by a human.