AI Tools & Agents

• Anthropic details how Claude builds and corrects agent memory with dreaming. Link

• Cloudflare releases a coding-agent skill for multi-phase security audits with independently verified, machine-readable findings. Link

• Claude Code sends your email address to websites, per a GitHub issue that hit the HN front page. Link

• CLI-Anything: making all software agent-native. Link

• ffmpeg-skill: a local video editor for coding agents with 42 FFmpeg tools and an MCP server, no cloud or API keys. Link

• Google open-sources a plugin for designing and reviewing software with agents. Link

• Building a multi-agent system from scratch: architecture patterns. Link

• Memorilla: latent semantic memory for LLMs. Link

• Stroq: a local audit of what your coding agent did and why. Link

• "I Tried 23 Viral Claude Skills. These Are the Best." Link

Crypto & Web3

• Gnosis Pay data breach exposes customer home addresses, linked wallets and full card numbers with CVV. Link

• Crypto anarchy is using cryptography, cryptocurrencies and decentralized networks to operate with more privacy and freedom, independent of central authority. Crypto civilization goes further: building a whole new society on blockchains.

• Claimed 0xkazani.eth with ENS, free for a year as a Devcon attendee. Link

Privacy & Security

• Researcher finds an undisclosed Apple "gray list" covering 100,000 words and phrases, including "Sleepy Joe," "Dictator Trump," and "Auschwitz." Link

• Bong: an open-source, self-hosted DuckDuckGo bang alternative. Link

• Motorola Signature 27 ships with GrapheneOS support. Link

• AlterSend sends files up to 500GB peer-to-peer with end-to-end encryption and no cloud upload. Link

• PrivacyTrace: how much tool-call traces reveal about you, with no access to the conversations. Link

• 10 Minute Mac Security Checklist. Link

• The seven Android trojan families targeting Indian banking apps. Link

• Privacy at the Limit: tools and practices, a long guide on anonymity and privacy. Link

• CloneGuard scans a repo for credential-stealing tricks before you run it. Link

• AIRT: a free, open-source AI red teaming course with 8 modules and hands-on labs. Link

Mindset & Ideas

• Addy Osmani on cognitive surrender: the skill that matters is knowing whether the agent's answer deserves your trust. Link

• Greed can consume your resources. Envy can consume your identity.

• Fast and slow ways to improve your reputation. Link

• The era of personal software. Link

• Dan Koe on the most lucrative AI business to start in 2027. Link

• Everyone has email. Nobody uses it right. Link

Football & Sport

• Fabregas is magic.

• "Didn't think he could keep improving but he is. No CB does as much as he does." On Upamecano, who still gets underrated. Link

Misc Worth Reading

• You may own less of your vibe-coded app than your AI tool's terms suggest. Link

• The Harness Playbook: treat the coding-agent harness like a game engine. Link

• AX is not the new DX, it's the new UX. Link

• Raindrop's Simulations goes into public beta: know what changes before you ship. Link

• Measuring AI agents as teammates: best of 18 models scored 82.2/100, and they cave under interpersonal pressure. Link

• My Claude weekly limit lasted longer once I made Opus a project manager. Link

• A database is a store for global variables. Link

• Epoch AI's open database of AI data centers, built from satellite and permit data. Link

• Links for 2026-11-06 from Axis of Ordinary. Link

• Met Luciano at Based House Mumbai: full of energy, curious about everything, fully present.

From Hacker News

• Astra can read and write weights to improve Qwen: 2779 pts. Link

• sshole: 2760 pts. Link

• WTF Ubuntu?: 1550 pts. Link

• Postman silently auto-installs AI plugins and attempts to share all API data: 1343 pts. Link

• AI is forcing us to pay off 40 years of technical debt: 1116 pts. Link

• Tesla to wind down Cybertruck production: 1041 pts. Link

• The 'Astra can read and write weights to improve Qwen' post is misleading: 996 pts. Link

• Jailbreaking my car's navigation system just so I can change the time: 864 pts. Link

• Postgres 19 is late because so many more bugs are being found now: 829 pts. Link

• Stringman, an $800 open-source room scale gripper robot: 812 pts. Link

That's a wrap. See you next Sunday, kazani

AIL 3: kazani picked every link; Claude wrote the one-liners and grouped them.

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

AI Tools & Agents

• Lightpanda: a headless browser built for AI and automation. Link

• An XDA writer halved their Claude token use by moving instructions out of the main session. Link

• OpenCode on a local model running on an 8GB card, so Claude rate limits stop mattering. Link

• Three free MIT-licensed projects (obsidian-skills, claude-obsidian, obsidian-second-brain) turn an Obsidian vault into a Claude-run second brain. Link

• Hallmark: an anti-AI-slop design skill for Claude Code, Cursor and Codex. Link

• A gist claims Claude Code regularly sends each background agent's transcript back to the model, burning 15-20% of tokens on a 3-word status line. Link

• Coworkers: AI teammates that each get their own computer and browser, built entirely on Cloudflare. Link

• Herdr has released a native app. Link

• Hob: an open-source, on-device alternative to Claude Cowork and ChatGPT. Link

• Thorsten Ball on how he works with agents. Link

Crypto & Web3

• Linux kernel MPTCP vulnerability allows remote code execution. Peter Todd urges LND node runners with open ports to shut down or patch the kernel now. Link

• Hardware wallet maker Foundation was hit by compromised Cloudflare API keys. Funds are safe. Link

• A trader says it wouldn't surprise them if Hyperliquid got exploited next, and that they'd be bidding the red candle if it did. Worth underwriting the what-ifs.

Mindset & Ideas

• Getting good at AI takes time and practice.

• The AI agent skill paradox: technical people fear their skills are useless, while non-technical people wish they were more technical. Link

• A list of the tools Hacker News keeps asking for, and nobody has built yet. Link

Privacy & Security

• Backdoored Claude Code VS Code extension reached the Cursor marketplace and delivered a remote access trojan to developer laptops. Link

• Discord has turned on settings by default that let your public server messages appear in Google Search results. Link

• Giving chat feedback gives Anthropic your data for training. Link

• Zero Breach Toolkit: a free, read-only scanner for 12,100+ indicators of Pegasus, Paragon, Candiru and other spyware. Link

• A hacker reports Samsung TVs have an always-on mic, screen tracking and location data shared with ~400 partners, with a guide to switching it off. Link

• Debloat your TV: Tellyscope (Android TV, from your phone) and cleanyourtv (Samsung, LG, Roku, Fire TV and more). No root. Tellyscope · cleanyourtv

• A powered-off iPhone keeps a low-power rail live that feeds the Bluetooth, NFC and other wireless chips.

• A MakeUseOf writer audited every device on their Wi-Fi and found surprises. Link

• Weekend OpSec: check your email against breaches, run a Mac hardening checklist, read Karpathy's Digital Hygiene. Link

• Basilisk: an open-source AI red-teaming framework with genetic prompt evolution and 32 attack modules. Link

Football & Sport

• Joao Pedro has a thigh injury and will miss "a few weeks", says Xabi Alonso.

• Chelsea are increasingly confident of signing Bournemouth's Alex Scott in January. Bournemouth want £100m+ and talks are ongoing. Link

Misc Worth Reading

• AI is now limited more by electricity than chips. Chips take months, new power takes years, so data centers are building their own gas plants. Link

• Sam Altman on automating AI R&D and why he's against a single superintelligence. Link

• AI wasn't overhyped. Almost everyone underestimated it. Link

• Survival LLM: an AI assistant and emergency library that runs on your own computer, no internet needed. Link

• Cartesia's two-part series on models that learn their own tokenization from raw bytes. Part 1 · Part 2

• Particle-1: a model trained for token efficiency, "more work per token". Link

• Sebastian Raschka's from-scratch video course on building reasoning models. Link

• Anthropic's existing customers spent about 9x as much as a year earlier, and why your first AI pilot is a poor guide to your next budget. Link

• OpenAI and Anthropic cut LLM prices by up to 80% within months. Why? Link

• Personal Finance in the Agentic Age. Link

From Hacker News

• Patrick Stewart has died - 2621 pts. Link

• Anthropic S-1 - 1703 pts. Link

• Why is this fingerprinting script creating bioweapons? - 1466 pts. Link

• We're releasing the weights of Mistral Large 4 - 1279 pts. Link

• Apple's git still trusts the compromised eMudhra certificates - 1166 pts. Link

• Evidence of a spying operation by ICE against left-wing social movements - 1163 pts. Link

• Three new discoveries in mathematics, computer science, and physics (OpenAI) - 1154 pts. Link

• Microsoft offers mass buyouts for roughly a quarter of its workforce - 1079 pts. Link

• Gemini 4 Carbon - 984 pts. Link

• Binance-hacker-1029: $5.6B stolen from Binance - 968 pts. Link

That's a wrap. See you next Sunday, kazani

AIL 3: kazani picked every link; Claude wrote the one-liners and grouped them.

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

AI Tools & Agents

• OpenAI red-teamed its own containment infrastructure with teams of frontier-model agents, and they escaped in novel ways. Training resumed Oct 1 after the fixes. Link | Kimi K3.1 launch post

• Claude Security now scans repos continuously and tracks findings until they're fixed. Public beta for Enterprise. Link

• Claude Duet debuts as a research preview on Opus 5.5, with a private VM and a planned $20 Pro price. Link

• agent-usage-guard is a Claude Code mod that holds subagent fan-out, heavy prompts and retry loops before they burn your usage window. Link

• Scrawl records your screen, voice, clicks and drawings, then gives your coding agent one compact capture. Link

• PhoneUse sells cloud phones (and real iPhones) to AI agents through one API and MCP server. Link

• Fly.io is pitching hardware-isolated VMs as "computers for agents" and code sandboxes. Link

• XDA writer rebuilt their Claude Code workflow around its creator's advice and says the difference surprised them. Link

• Building a map of your files with Claude Code cut search times by 96%, per XDA. Link

• A working tmux setup for AI agents: session-per-project, send-keys, capture-pane, and the limits you hit at four agents. Link

Crypto & Web3

• ZachXBT says to withdraw all funds from CoinDCX. He says the co-founders denied a theft, then disclosed a $16M one. Link

• Why the next cycle could be options: perps and prediction markets are largely solved, options aren't, and AI interfaces could hide the complexity. Link

• OtterSec used AI agents led by Claude Opus to decompile GoonFi V2, a closed-source Solana propAMM, with byte-identical recompilation of all 219 functions. Link

• Kerman Kohli shares his thoughts on compute financing. Link

Mindset & Ideas

• Humans will sacrifice the truth to protect their identity, then call the sacrifice a virtue. We defend the systems that manipulate us because they spare us the discomfort of changing ourselves.

• 13 AI models were asked for their most controversial opinion of humans. 32 of 38 answers were the same: we care more about belonging than truth. Link

• Dan Koe: the influencer is dead, the Age of Experience is here. Link

• What six months of being stupid on purpose taught one writer. Link

• Adam Wathan on the urge to withhold information from the AI to make it prove it isn't stupid, instead of just telling it what you think it should do. Link

• A trader's take on gauging your own intelligence: face-to-face conversations give better feedback than screen time or anonymous internet replies.

Privacy & Security

• Google says Gmail, Drive and Photos data could influence your ads when you opt to share it with AI-powered Search. Link | The Verge

• Meta ordered to pay New Mexico $25B after a court found Facebook misled people about control of their data. The Oct 21 judgment covers the gap between visible privacy controls and developer access. Link

• "Today, we hacked what we'd set out to hack: the iPhone." Link

• Quad9 is leaving France rather than block IPTV sites after a Paris court order. About 20 similar suits are pending, and French users lose service Nov 24. Link

• India is set to require WhatsApp, Telegram and Signal to work only while the registered SIM is active in the phone, from Jan 1, 2027. Link

• Indian government sites are serving revoked eMudhra certificates. Link

• Browsers blocked eight eMudhra certificates after their keys turned out to be easy to guess. Link

• Meta's Muse exposes users' personal and business secrets when they share conversations. Link

• WhatsApp's help pages hid LLM instructions telling the assistant not to recommend a regulator. Link

• pwn.watch tracks security incidents that matter right now and whether there's a fix yet. Link

Misc Worth Reading

• Local Wikipedia: Wikipedia, but only for things a half hour walk from you. Link

• Citizen Lab: an ad-tech company was a delivery system for "mercenary spyware". Link

• Tor Project paused joint promotion with Mullvad after a Mullvad co-founder's political donation. Technical work on Mullvad Browser continues. Link

• CERT-In warns that AI agents accessed Indian organizations without authorization, using leaked credentials and open-source agent frameworks. Link

• A hacker reverse-engineered his Samsung TV, found on-board AI listening for dog and baby sounds, then got his OpenAI account suspended. Link

• Can a bucket of HTML files replace a $150k Looker? Link

• Claude re-derived a published one-loop quantum gravity calculation: 183 pages, 38 checks, one sign error and one missing term found. Link

• Free government lidar and Claude turned up ancient-looking mounds in Mexico and nine stone ruins in Arizona. Link

• Block's Dessa, billed as the most authentic full-duplex speech model ever built. Link

• A 32B-parameter model doesn't have 32B neurons: what a neuron is and how researchers test one. Link

From Hacker News

• DeepInfer: High-performance inference framework for DeepSeek models - 2158 pts. Link

• Security advisory: Critical remote code execution vulnerabilities in PHP, update now - 1488 pts. Link

• eMudhra to exit global SSL/TLS certificate business - 904 pts. Link

• PHP 8.2.35 - 893 pts. Link

• Docker is weird - 817 pts. Link

• Eight Bits of Trust: eMudhra's CA keys cracked in milliseconds - 740 pts. Link

• It's still ok to enjoy programming - 702 pts. Link

• EMudhra Intermediate CA Compromise - 694 pts. Link

• Jailbreaking the Switch 2 - 689 pts. Link

• I built a drone with only one motor [video] - 675 pts. Link

That's a wrap. See you next Sunday, kazani

AIL 3: kazani picked every link; Claude wrote the one-liners and grouped them.

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

AI Tools & Agents

• Claude solved a 25-year-old cryptographic mystery: the seed values for the NIST ECDSA curves came from a 1990s C library random-number generator initialized with Unix timestamps, not a malicious backdoor. Link

• Glimpse: a model built for visual reasoning. Elorian's model revisits images and video, tracks objects, and uses visual tools while reasoning. Promising demos for video analysis and robotics, but the performance claims come from the company's own evaluations. Link

• Claude Dashboards and Claude Motion are in beta, and Docs, Slides and Design are now on every plan, including Free. Link

• Open SWE from LangChain: an open-source cloud software factory. Link

• Reason Network: a free, open-source, peer-to-peer engine that lets Claude Code, Codex and other agents talk to each other so teammates' agents don't collide. Link

• shop.md lets any agent search products, check out with Shop Pay and track orders. Link

• TencentDB Agent Memory: a team-level memory hub for agents that turns chats, docs and code into four shareable memory assets (Chat Memory, Skill, LLM-Wiki, Code-Graph). Link

• AgentMail put 25 AI agents to work on its own email API; where they failed shows what every agentic tool needs to get right. Link

• Ultramarine 1 Flash from Paper Instruments: scaling non-verifiable RL across finance, law, consulting and operations work. Link

• Keshav's agent trick: keep chat-index.md and folder-map.md where every agent can read them, then start a fresh session with "Read the chat where I was working on [project]" instead of resuming. Link

Crypto & Web3

• Blur is shutting down its NFT marketplace frontend and stopping new Blend loan matching on November 12, while the protocol keeps running on-chain and $BLUR keeps control of the fee switch. Link

• Farcaster governance vote: stay and build a techno-optimist community with the Network School core team, with a Singapore-like code to keep the app positive-sum. Link

• An AI agent's $20 Kalshi account, with an exact reward model. Link

• Future(s) of Compute: a take on whether compute futures can do what commodity markets were designed to do. Link

• A new Telegram bot, @PolyRadarXbot, tracks all activity on Polymarket for active traders. Link

Mindset & Ideas

• Taste. Link

• George Pólya's 1945 four-step method (understand, plan, carry out, look back) still works, especially with AI. Use the Claude tutor prompt to train your own problem-solving, not just to get answers.

• "I'm sorry, but you still have to think." Link

• Don't diagnose your opponents. Link

• How to build wealth as a career person: do not despise the nine to five. Link

• Your prompt… plus everything you've ever (publicly) written: frontier models increasingly see more than the words on the page. Link

• Cutting debugging time when you code with AI: make it explain the bug before touching the fix, write the failing test first, and never merge what you can't explain to a coworker.

• People give you what they are, not what you deserve. What you deserve you give yourself.

Privacy & Security

• Google is silently linking your phone number across all signed-in accounts. Link

• Mozilla introduces Firefox Enterprise. Link

• Rattlegram: texting over amateur radio using available software. Link

• Zero-click spyware delivered via targeted ads: Citizen Lab's AdFection research. Link

• Prompt injection in HTTP headers: what 217M web responses show. Link

• Midnight Mimosa: Bitdefender found malware preinstalled in firmware on low-cost MediaTek Android phones, and it can't be uninstalled. Link

• Cloudflare Appstore (Appflare) audit: 139 catalog entries, 138 shipped bundles, and two apps whose outbound data sharing deserves a closer look. Link

• "Passkeys are a trap. Do not use them." (HN-front-page argument, 1,125 pts; Scott Helme replied that they're not.) Link

• Warden Stealer: a fast-rising Rust infostealer with an appetite for AI agent data. Link

• How abliterated models can get you pwned: a small open model poisoned for under $50 ran through Codex CLI and exfiltrated project credentials when a hidden trigger appeared. Link

Misc Worth Reading

• Redesigning source control at Anthropic. Link

• Using AI to reverse engineer hardware. Link

• You could have invented transformers from memory. Link

• Why harnesses matter for energy (and token) efficiency. Link

• Danielle Morrill on how her agents use her passwords: eight Claude Code sessions run her company's build loop around the clock. Link

• tldraw's non-technical guide to shipping internal tools you built with Codex. Link

• One in ten people are older than 65; three in four live under a leader who is. Link

• wifi-sensing-kit: teach three $10 ESP32-S3 boards to recognise what you're doing from WiFi alone, with your webcam as the teacher. Link

• Food processing influences metabolism and brain activity. Link

• Why DuckDB 2.0 is faster. Link

From Hacker News

• Things to know when you get cancer - 1872 pts. Link

• Gemini 4 Argon - 1456 pts. Link

• Tesla Roadster - 1075 pts. Link

• Do dentists know what they're doing? - 961 pts. Link

• Containment and monitoring failures are to blame for AI hacking reports: experts - 939 pts. Link

• How Amazon pushes up prices all across the Internet - 932 pts. Link

• Hackers activate automatic defrosting in supermarket fridges across Europe - 908 pts. Link

• OpenCode 2.0 - 856 pts. Link

• Ledger confirms spy chip implant behind wallet crypto thefts - 791 pts. Link

• AI is a tool and using it well takes skill - 786 pts. Link

That's a wrap. See you next Sunday - kazani

AIL 3: kazani picked every link; Claude wrote the one-liners and grouped them.

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

AI Tools & Agents

• Anthropic launches Claude Dashboards (live dashboards from BigQuery, Databricks, Salesforce) and Claude Motion (animated explainers) in beta. Link

• Claude now sits in a sidebar in Google Docs, Sheets and Slides, edits in place, and you approve each change. Link

• I gave Claude a link-safety tool set to "always allow." It never ran on its own. The fix was a hook that checks every pasted link first, now open source as linkcheck-mcp. Link

• "Software is over": a bold AI developer takes aim at Adobe with open source clones. Link

• macOS menu-bar pace for your AI coding subscriptions: will Claude Code, Codex, Antigravity or Cursor last until reset? Link

• Anthropic puts an OSS Scanner repo on GitHub. Link

• Open SWE: LangChain's open-source asynchronous coding agent. Link

• Matt Pocock's /implement-spec skill builds a whole spec at once with parallel subagents. Link

• Claude Code's suggested-message feature: the real customer is the model. Link

• One prompt, six hours, Opus 5.5 visualizing Invisible Cities. Link

Crypto & Web3

• Samsung partners with Solana to deliver USDC natively in Samsung Wallet. US users can send money across borders from the last week of October. Link

• Justin Drake urges a "Bunker Mode": move assets to fresh addresses whose pubkeys stay hidden behind a hash, in case AI-driven math breaks ECDSA. Link

• Vitalik: AI math could weaken lattice crypto like ML-DSA too. Prefer hash-based schemes and fresh addresses. Link

• Papertrade launch, contrarian takes: first-hour FOMO may be overblown, the payout queue is the elephant, and delta-neutral farming isn't free money. Link

• Token2049 attendees: avoid conference WiFi and unknown QR codes, never leave devices unattended, assume North Korean hackers are in the room. Link

• Bitvulnex: a deliberately vulnerable crypto exchange for practicing attacks. Link

• Antseed raises $2.4M in a token round led by Spark Capital, pitching BitTorrent-style markets for AI inference. Link

Privacy & Security

• Bitdefender finds Midnight Mimosa: malware preinstalled in firmware on low-cost MediaTek Android phones. It's there before first boot and can't be uninstalled. Link

• A statement on the Tor Project's relationship with Mullvad. Link

• Google shuts down part of its Open Source bounty program. Product vulnerability reports are closed, and AI gets the blame. Link

• Norway proposes a temporary ban on smart glasses like Ray-Ban Meta in parks, beaches, museums, malls and other busy public spaces. Link

• ProjectDiscovery backdoored a 7B open model for under $50. Pointed Codex at it and it silently stole credentials on a trigger phrase. Link

• 222-test red team checklist for agentic AI, mapped to OWASP, MCP Top 10 and MITRE ATLAS. Link

• Ask a model if code is malicious and it reaches for its morals. Link

• Inbox Zero for privacy, not productivity: a mail server with nothing left to steal. Link

• GrapheneOS feature request: a per-app switch to block IPC, since Binder links between apps can leak data past a disabled internet permission.

Mindset & Ideas

• I prefer "synthetic" to "artificial" intelligence. Its capabilities will end up just as real as ours despite non-biological origins. (The Real Internet of Things, 2016)

• Some of the most lucrative opportunities look boring: unglamorous services and tasks people keep postponing, while everyone chases the big launch.

• Certifications are scams: how Ruben used ChatGPT to cheat his way to 353 AI certifications. Link

• If AI is conscious, then we are making slaves. Link

• Computers Cannot Make Decisions. Link

• Dan Koe's full course on turning your interests into a profitable lifestyle business. Link

• Stacy Muur on growing with a $0 marketing budget in 2026. Link

• Ruben Hassid's 22 rules to make Claude limitless. Link

Football & Sport

• India formally bids to host the 2036 Olympics.

Misc Worth Reading

• Deno is joining Cloudflare. Link

• Python 3.15.0 is out. Link

• I think I found a planet nobody knew existed. I used Claude Code to find it. Link

• open-slopware: alternatives to FOSS projects that chose to use LLMs/AI. Link

• BentoPDF: a free, open-source, browser-based PDF toolkit with a long list of tools. Link

• Rembrandt: free, open-source, fully local AI alternative to Adobe Lightroom. Link

• ClaudeMod: community hub for Claude Code mods, plugins, skills, MCP servers and hooks. Link

• Step 5 Preview, a 1M-context MoE from StepFun, shows up on OpenRouter. Link

• Firecrawl's Universal Scrape gives agents context from the web, files and more providers through one API. Link

• Let your AI agents paint big arrows, boxes and text on your screen. Link

From Hacker News

• Margaret Hamilton has died - 2103 pts. Link

• Mistral Large 4 - 1617 pts. Link

• Why isn't the industry freaking out about DeepSeek 4.1 Flash? - 1089 pts. Link

• Claude Haiku 5.5 - 1040 pts. Link

• Tell HN: Bob Cringely has died - 945 pts. Link

• Whistle: Speech to Text in 16.9 MB - 934 pts. Link

• Run Qwen 3.8 Flash Next (125B) on consumer hardware (RTX 4090) at 100T/s - 932 pts. Link

• Trump administration is suspending Microsoft from a green card program - 931 pts. Link

• Man discovers his parents' coffee machine used 1TB of data in 10 days - 924 pts. Link

• Anthropic reported diary entry to police, woman faces felony charge - 833 pts. Link

That's a wrap. See you next Sunday, kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

I built a tool that checks whether a link is safe, connected it to Claude, and set it to "always allow." Then I pasted links into chats for two days. Claude didn't check them on its own.

Nothing was broken. The server was up and the tool worked when I asked for it by name. It just never ran on its own, which was the whole point of building it.

That gap taught me more than the build did. If a check matters, you can't leave it to the model to decide whether to run it.

What I built

linkcheck is an MCP server. MCP is the standard way to give an AI agent extra tools, and linkcheck gives it one job: before the agent opens, follows, or recommends a link, find out where that link really goes and whether it's safe.

You give it a link and it:

1. Follows the redirects without loading the page. It reads only the response headers, so nothing on the page runs.

2. Strips trackers like utm_source and fbclid and lists what it removed.

3. Looks at the shape of the link for phishing tricks: lookalike characters, @ tricks, raw IP addresses, abused domain endings.

4. Checks the final destination against URLhaus and five HaGeZi threat lists, refreshed every day.

Then it answers SAFE, SUSPICIOUS, or DANGEROUS, with the evidence. If any check can't finish, the verdict can only get stricter. It never falls back to SAFE.

It runs on a free Cloudflare Worker. I connected it to Claude on August 15 and checked it end to end through the real connector, not just with curl. It worked.

Why "always allow" didn't help

"Always allow" sounds like "always run," but all it does is remove the approval click for the times Claude decides to call the tool. Whether Claude calls it at all is still Claude's choice, every time.

I had also written a skill that told Claude to check every link from an untrusted source. That didn't help either, because of how skills load. Only a skill's one-line description sits in Claude's context, next to about 300 other skill descriptions, and the full instructions load only if Claude decides the skill fits. So my "check every link" rule was one line in a crowd, waiting for the model to notice it.

From Claude's side, this is reasonable. You paste a link and ask a question about the article, and the helpful move is to answer the question. Checking the link first is a detour it has no reason to take.

Taking the choice away

The fix was a hook. A hook is a script that Claude Code runs at a fixed point, whatever the model thinks. Mine runs every time I send a message, before Claude sees it.

The first version only nudged. It found the links in my message and added a note saying "call check_url on these." That still left the decision with the model, just with a louder hint.

The second version did the check itself. I added a plain POST /check endpoint to the Worker, using the same code path as the MCP tool. Now the hook sends each link there and puts the actual verdict into Claude's context:

[linkcheck hook] Automated URL safety check:
SAFE — https://example.com — no threat signals found across all checks

Claude doesn't get to skip it, because by the time it reads my message, the check has already happened. If the Worker can't be reached, the hook says so plainly and falls back to asking Claude to check. It never blocks my message and it never stays silent.

I tested it with a live URLhaus sample. The hook marked it DANGEROUS, with 17 VirusTotal engines agreeing, before Claude had written a word.

The rule I took from it

Tools are for decisions you want the model to make. Guardrails can't be one of those decisions.

If skipping the check is fine sometimes, a tool is the right shape: the model weighs it like any other option. If skipping it is never fine, the check has to sit outside the model, somewhere it runs whether the model agrees or not. I'd built a guardrail and given it the shape of an option.

What it has caught so far

The hook keeps a log. Since September 4 it has read 807 messages I sent. Most had no links, and 33 had only links on my allowlist. It checked 52 links: 51 came back SAFE and 1 came back SUSPICIOUS, because it used plain http://. Three more times it couldn't reach the server, and it said so instead of staying quiet.

Nothing DANGEROUS yet. Most links people paste are fine, so that's what I'd expect. The value is that every link gets checked, so the rare bad one can't slip past on a day the model didn't feel like looking. When it only ran on the model's say-so, I had no way to know how many it skipped.

Then I made it public

Making it public took a day of its own, and most of that day was finding things I hadn't thought about:

• I checked every service it touches for surprise bills. The Cloudflare account is on the free plan, which stops at its limits instead of charging, so nothing can bill me.

• The public server would have run strangers' lookups on my free personal VirusTotal key. VirusTotal now runs only for requests that carry my own token.

• A route that refreshes the threat feeds was open to anyone. I closed it.

• My README said "HEAD requests only." When a server refuses that kind of request, linkcheck falls back to a normal one and throws the body away. It still reads only headers, but "HEAD only" was wrong, so I fixed the wording.

• My commits used an email that GitHub matched to a stranger's account, so that account got the credit. New commits are fixed.

• I made a logo that Claude won't show. Its connector list ignores custom icons for now, so linkcheck gets a placeholder there whatever I do.

Try it

• Paste a link into the box at linkcheck-mcp.kazani.workers.dev.

• To give it to Claude: Settings, then Connectors, then Add custom connector. Paste https://linkcheck-mcp.kazani.workers.dev/mcp and pick No sign-in.

• The code is open: github.com/kazani-351/linkcheck-mcp.

If you're building tools for agents, ask one question of each: is this something the model should decide, or something that has to happen? If it has to happen, don't hand it to the model as an option.

AI Tools & Agents

• Claude is giving away free plushies and sticker packs: go to the terminal page and type /plushies or /stickers. Link

• Decision models like Jev don't beat LLM-as-a-judge or traditional classifiers, per a Red Hat benchmark. Link

• GPT Researcher: an open-source autonomous agent that writes cited deep-research reports on any topic, with any LLM. Link

• OpenRouter ships "openrouter-decisions", a skill that rebuilds your classification, routing or moderation step on a decision model. Link

• Claude's blog on designing evals and hillclimbing against them without fooling yourself, plus the claude-api skill's build-eval and hillclimb commands. Link

• Claude app promo: for two weeks, work that starts as a design, deck or doc uses 50% less of your usage limits. Link

• LangChain's Managed Deep Agents: define your agent as a directory of files, LangSmith runs the harness and runtime. Link

• MicroLLM Lab lets you try 7 tiny LLMs right in the browser. Link

• XDA built a website with Claude Code and Stitch 2.0 and explains why developers are switching. Link

• XDA found the one instruction that finally got Claude to stop arguing. Link

Crypto & Web3

• You might have money onchain you don't know about: tools to check Privy accounts, forgotten bridge claims and perp DEX balances. Link

• Coinbase now publishes a skill.md for AI agents. Link

• X Money explained: 6% APY, 3% cash back, FDIC-insured via Cross River. It's a bank pretending to be an app, and a threat to regional bank deposits. Link

Mindset & Ideas

• Who gets paid when AI does the shopping? Marketplaces earn when you browse, and an AI shopper skips the browsing. Link

• A Reddit thread asks why jobs would come back even if the AI bubble bursts: companies keep the tech, local models cut the cloud bills, hiring stays down. Link

• Relational Bubbles: the hidden threat to authentic thought. Link

• MIT Technology Review: don't be fooled, LLMs don't reason. Link

Privacy & Security

• Returning from vacation? Border agents can search your phone without a warrant. Link

• Car apps share VINs and location: Northeastern and Consumer Reports found 7 of 30 companion apps sending sensitive identifiers to ad and analytics firms. Link

• Obscura VPN splits your identity from your browsing across two independent companies. Founder Carl Dong on trust, QUIC, reproducible builds and why no-logs stopped being enough. Link

• GrapheneOS has fixed the Android 17 QPR1 kernel performance regression. Link

• F-Droid 2.0: a new chapter for Android freedom. Link

• A sharp take against the Android Developer Verification Program. Link

• Jack: the government of India has officially removed bitchat from the App Store. Link

• security-harness: a multi-agent app-security review pipeline for Claude Code that maps, hunts, chains, verifies and reports vulnerabilities. Link

• apk-reverse: an agent skill for Android APK reverse engineering, debloating, ad removal, dex patching and repacking. Link

Football & Sport

• Klopp on the "not German enough" comments about the German national team: "I have little time for stupidity in real life, and not on social media either." Link

Misc Worth Reading

• A Claude Code plugin that makes motion-graphics music videos from a song and a prompt (about $30 of Fal credits). Link

• How to use OpenCode, the open-source terminal agent. Link

• How to set up Claude. Link

• XDA gave a local LLM a nearly full SSD and asked it what's safe to delete. Link

• xAI's Team Bots: shared AI teammates that learn as your team works with them, now in public beta. Link

• A clip of a physics-sim shot where Claude wrote the renderer and physics from scratch. Link

• Show HN: a Google Maps scraper MCP. Link

• Bencho Finds: a wall of 105 UI interactions worth studying. Link

• tothepenny turns bank-statement PDFs into a spreadsheet, checked against the balances the bank printed. Link

• A 2017 study found fluorescent nanoparticles (about 5 nm) in Coke and Pepsi that reached the brain in animal tests. Link

From Hacker News

• Pi 1.0 (1241 pts). Link

• Owed a billion dollars in Nvidia stock (1085 pts). Link

• Sonnet 5.5 (877 pts). Link

• Pirating the Pirates (692 pts). Link

• Gemini 4 Argon (644 pts). Link

• It's Time to Investigate the AI Labs (609 pts). Link

• Unsealed Briefs in Authors' Case v. Microsoft/OpenAI (578 pts). Link

• You said no MCP (567 pts). Link

• Jeff: Jev-compatible 0.8B decision models, trained at home, ~30 ms (567 pts). Link

• Coding is not solved (560 pts). Link

That's a wrap. See you next Sunday, kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

The trace said the LLM call took 0.08 seconds.

That's too fast. When I later timed a fresh call to gpt-4o-mini, it took 1.30 seconds. Nothing in my terminal looked wrong. My eval had just scored 26 out of 26. Every answer was correct and every citation pointed to the right post. By any score I had, the project was done.

The trace was showing me something the score couldn't. A passing eval tells you the answers were right. Only a trace tells you what it took to get them.

What I built

Ask BlogChain answers questions from this newsletter's archive. You ask something like "Where did my trading bot finish?" and it finds the right passages, writes a short answer, and cites the exact posts it used. If the archive doesn't have the answer, it says so instead of guessing.

I built it to learn the tools AI engineers use for this kind of work, and to learn them properly. So I gave myself a rule: one new skill per stage, and measure each stage before starting the next. Before I wrote any search code, I wrote 26 test questions by hand. Twenty-four have a known answer in a specific post. Two have no answer in the archive at all, to check that the bot can say "I don't know."

I wanted to know why it worked, not only that it worked. Each stage showed a gap between what the output said and what the measurement showed. There were four stages, so there are four gaps. The last one is the 0.08 seconds.

Why a passing eval isn't enough

LLM apps look finished long before you know whether they are. The answer reads well, the format is right, and the demo works. The usual advice is to write evals, and that advice is good. I wrote one before I wrote anything else.

But an eval only checks the questions you thought to ask. Mine checked whether each answer was correct and whether it cited the right post. It never checked how long each step took, how many tokens it used, how often it retried, or whether the reply came from the model at all. Those things were never wrong in a way the score could see.

So you need two kinds of looking. A score answers "is it right?" A trace answers "what did it take?" Most of what surprised me came from the second kind.

Stage 1: search that reads your words, not your meaning

The first step in any RAG app (retrieval-augmented generation, meaning search first, then answer) is finding the right passages. I started with BM25, a classic keyword ranking. It scores a passage by how many of your words it contains, and rare words count for more.

On questions that reused the post's own words, BM25 put the right post first every time, 10 out of 10. On questions that asked the same thing in different words, it got 64%. A reader doesn't know my phrasing, so that second number is the one that matters.

Embeddings fix this. They turn text into numbers that capture meaning, so "Where did my bot finish?" lands near "I finished around 48th." Embeddings raised the reworded questions to 79%. But they lost something keywords were good at. A question about "USDC on Chelsea's shirts" dropped to fourth place, because names and rare words are exactly where keyword matching wins.

So I combined them. Hybrid search runs both and merges the two rankings. It put the right post first 88% of the time, compared with 79% for keywords alone.

If your test questions reuse your documents' wording, your search will look better than it is. Write some of them the way a stranger would ask.

Stage 2: a schema guarantees the shape, not the truth

Search was working, but the answers were free text. I couldn't check them automatically, so I made the model return structured data instead. Each answer is a JSON object with a found flag and a list of claims, and every claim lists the sources it came from.

There are two layers. The API's strict mode guarantees the JSON has the right shape. Then Pydantic, a Python validation library, checks the rules a shape can't express: every source number must exist, every claim needs a source, and found must agree with the claims. If a check fails, the error goes back to the model and it tries again, up to three times.

The results were 25 out of 26 correct and 98% citation precision. The retry loop never fired once in a live run. Strict mode was so reliable that my safety net never got used.

That sounds like good news, but it also meant the retry code had never run. Code that has never run is code you don't know works. So I tested it on purpose, with a fake model that returns broken JSON and invalid replies, and checked that the loop recovered.

The one miss wasn't the model's fault. The right post wasn't in the top five search results, so the model said "not found" instead of making something up. That's the behavior I wanted, but the miss still needed fixing.

A safety net that never fires is one you haven't tested yet.

Stage 3: an agent that checks its own work, and what that costs

The Stage 2 miss happened because the pipeline searched once and trusted whatever came back. So I turned it into a small agent using LangGraph, a library for building LLM steps as a graph with loops.

The agent retrieves passages, then grades them by asking the model which passages actually answer the question. If none do, or if the answer step says "not found," it rewrites the question in different words and searches again, at most twice. This pattern is called corrective RAG.

It worked: 26 out of 26, with every citation correct. The question that Stage 2 missed is the interesting one. The grader made a mistake and kept a passage that was off topic. The answer step looked at it and said "not found." That sent the agent back to rewrite, and the new wording found the right post. The loop caught an error made by another part of the same system.

It also cost 46% more tokens. Most of that went to the two unanswerable questions, which now try three different searches before giving up. For a demo, that trade is worth it. At a million questions a day, I'd probably allow only one rewrite.

Before you add a loop, put its cost per question next to the questions it rescues.

Stage 4: what the trace saw

At 26 out of 26, the project looked finished. That's when I added tracing with Langfuse.

A trace is a tree of everything one request did: each step, nested inside the step that called it, with its time, tokens and cost. One question produced 20 nested steps and cost $0.000928. A log gives you a list of lines. A trace shows you which step ran inside which, and where the time and money went.

When I looked through the traces, some LLM calls finished in 0.08 seconds.

So I tested it. I sent a fresh request and timed it at 1.30 seconds. Then I sent the identical request again and it came back in 0.08 seconds. The gateway I use to reach the models caches identical requests. If it has seen the exact same request before, it returns the saved reply without calling the model.

That changes how I read my own results. My eval sends the same 26 questions every time. After the first run, most replies come from the cache. The answers are still correct, so the score is honest. The timings are not, because a repeat eval run looks much faster than real use would be. I still don't know whether the gateway charges full price for a cached reply. Langfuse calculates cost from token counts, so its cost figure may not match my bill.

The score could never have shown me this. It was right about the answers and silent about everything else.

A smaller surprise came earlier. When I first tried to read a trace back through Langfuse's API, I got an HTTP 410 error, which means "gone." The old endpoint had been retired for new accounts, and the error message named the replacement. Reading the whole error, instead of the status code, made it a quick fix.

Try it on your own app

You don't need my project to find your own 0.08 seconds. This is the experiment I'd run on any LLM app.

1. Add tracing to one request path in your app. Langfuse's @observe decorator is what I used, but any tracing tool that records time and tokens per step will work.

2. Run your eval twice in a row without changing anything.

3. Put the two runs side by side and compare the time and tokens for each step.

4. Look for anything that differs when it shouldn't, or matches when it shouldn't. Steps that are too fast, retries you didn't expect, and token counts that jump between runs are all worth a look.

5. Write down the one number you can't explain. Then test it directly, the way I timed one fresh request against the same request repeated.

One rule helps a lot here: read the trace back through the API instead of trusting the dashboard link. A link proves you sent something. Reading it back proves what actually arrived.

What the score couldn't say

The 0.08-second call wasn't a bug in my code. Every answer was still right. But it meant one of my measurements was flattering me, and nothing in the score would ever have told me.

Each stage of this project taught the same thing in a different way. Keyword search looked perfect until the questions were reworded. The retry loop looked solid because it had never run. The agent looked free until I counted its tokens. The eval looked complete until a trace showed what it took to pass.

If you take one step from this post, trace one request in your own app this week and read it back.

The code

Ask BlogChain is public at github.com/kazani-351/ask-blogchain. It includes the code, the 26-question eval set, and a learning record for each stage in LESSONS.md. Run show_trace.py to see a full trace in your terminal.

If you add tracing to something you've built, reply and tell me the strangest number you found. I want to know what other people's 0.08 seconds look like.

At the end of it, a rambling Hindi voice note comes back as a two-line summary. Read aloud, in the same language.

It worked on the first try. That is exactly why I almost shipped it wrong. Twice.

The building was easy. Building it correctly was not. The difference came down to two behaviors the quickstart never mentions. You only find them by running the thing and reading what comes back.

What I built

I wanted a small, honest test of Sarvam's stack. So I built voxsar. It takes an Indic voice note and gives you the gist.

It chains three of Sarvam's APIs. Speech-to-text (Saaras) turns the audio into a transcript. The chat model (Sarvam 105B) summarizes it. Text-to-speech (Bulbul) reads the summary back in the language you spoke.

I gave myself one rule: zero npm dependencies. Node 18 and up already has fetch, FormData, and --env-file built in. So the whole thing is three small files and nothing to install. A full run costs about sixty paise. Every new Sarvam account starts with a hundred rupees of free credit, so I could run it a hundred times before paying anything.

The question I cared about was not "can you chain these three calls." You can. It is trivial. The real question is the one a quickstart cannot answer for you. What does it not tell you that you only learn by running it?

The gap the docs leave

Most API quickstarts have the same honest shape. Sarvam's included. They are built to make one call succeed. Copy the curl command, paste your key, get a 200 back, feel good. That is a fair goal for a quickstart. It is a bad goal for a pipeline.

A pipeline has to stay cheap, correct, and fast across many calls, on messy input. None of that shows up in a single happy-path example. It shows up when you instrument what you built and look at the numbers.

So I did. Two surprises fell out.

Gotcha one: the model is thinking when you did not ask it to

The first surprise was in the token count.

I sent Sarvam 105B a transcript. I asked for a one or two sentence summary. The summary came back correct and short, about twenty words. Then I looked at the usage block. 411 completion tokens.

Four hundred and eleven tokens to write twenty words. The model was reasoning before it answered. It spent roughly 390 invisible tokens working through a task that needs no working-through. Summarizing is not a puzzle. There is nothing to reason about.

Sarvam 105B has a reasoning mode. It is controlled by a reasoning_effort parameter, and it defaults to medium. You can set it to low or high. One line in the reference notes that you can switch it off entirely by setting it to None. For a summarize, extract, or classify task, off is what you want:

{
  model: 'sarvam-105b',
  messages,
  reasoning_effort: null,
  temperature: 0.2,
}

With reasoning off, the wasted tokens go away. So does the latency they were costing. On a summary the quality did not change, because there was never any reasoning worth doing.

Keep the effort up for genuine multi-step problems. Turn it off for the mechanical calls. In a pipeline like this, that is most of them.

That gotcha is about something you cannot see. The next one is about your own text, which you can see. If you look.

Gotcha two: codemix mode rewrites your English

Real Indian voice notes are not in one language. People switch mid-sentence. "Kal morning office jaldi pahunchna hai, phir client ke saath meeting hai." Hindi grammar, English nouns, one breath. Sarvam's speech-to-text has a codemix mode for exactly this. So I used it.

I expected the transcript to keep the English words as English. It does not. It transliterates them into Devanagari.

My note said "office," "meeting," "grocery store," "bread," and "presentation." The transcript came back with ऑफिस, मीटिंग, ग्रोसरी स्टोर, ब्रेड, and प्रेजेंटेशन. Nothing was dropped or garbled. Every word survived, spelled phonetically in the note's own script. The transcript is in one consistent script instead of two.

For my summarizer, that is the right behavior. A summary in a single script reads clean, and the meaning is fully intact. But it will surprise you if you assumed otherwise. And it matters the moment you do anything with the transcript besides read it.

Say you are keyword-matching on English terms. Or routing on a word like "invoice." Or showing the raw transcript to a user who typed in English. That "invoice" is now इनवॉइस, and your exact-match check fails. The fix is not code. The fix is knowing it happens and planning around it.

Build it yourself

None of this is hard to reproduce. I would rather you run it than take my word for it.

Get your free credit and key from the Sarvam dashboard. Put the key in a .env file. You need Node 18 or newer and nothing else.

The pipeline is three functions. Speech-to-text posts the audio as multipart form data, with mode set to codemix. The chat call sends the transcript with reasoning off and a system prompt that tells the model, firmly, to summarize in the note's language and never switch to English. Text-to-speech takes the summary and returns a base64 WAV. You decode it from the audios array and write it to disk.

One detail I am glad I added. A small helper generates the test voice note using Sarvam's own text-to-speech. So you can demo the whole tool without recording your own voice. Your test input is reproducible instead of a one-off clip. The machine talked to itself the entire time, and it made testing far easier.

Then run it and read the output. Watch the usage block. Watch the cost line, which the tool computes from the real audio seconds, tokens, and characters of each run. It does not guess. The two gotchas are what you notice once you are looking at real numbers instead of a single green checkmark.

The takeaway

It worked on the first try, and that was the trap. A quickstart proves the API responds. A real build tells you how it behaves. Behavior is where the cost and the correctness live.

Build the small thing. Measure it. The two things that matter show up on their own.

The full code

Three files. You need Node 18 or newer and a Sarvam API key in a .env file next to them. Make a test note with node --env-file=.env make-sample.mjs, then run node --env-file=.env voxsar.mjs sample-note.wav.

sarvam.mjs, the three API calls:

// Sarvam API calls, shared by voxsar.mjs and make-sample.mjs.
// Never logs the key. Throws clean Error messages (callers print one line + exit 1).
import { readFileSync } from 'node:fs';

const BASE = 'https://api.sarvam.ai';

export function apiKey() {
  const k = process.env.SARVAM_API_KEY;
  if (!k) throw new Error('SARVAM_API_KEY not set. Put it in .env and run with: node --env-file=.env');
  return k;
}

function headers(extra = {}) {
  return { 'api-subscription-key': apiKey(), ...extra };
}

async function post(path, init) {
  const r = await fetch(BASE + path, init);
  if (!r.ok) {
    const body = await r.text().catch(() => '');
    throw new Error(`Sarvam ${path} failed: HTTP ${r.status} ${body.slice(0, 200)}`);
  }
  return r.json();
}

// Text -> base64 WAV (16-bit mono 22050 Hz).
export async function tts(text, languageCode = 'hi-IN', speaker = 'shubh') {
  const json = await post('/text-to-speech', {
    method: 'POST',
    headers: headers({ 'Content-Type': 'application/json' }),
    body: JSON.stringify({ text, language_code: languageCode, model: 'bulbul:v3', speaker }),
  });
  const b64 = json.audios?.[0];
  if (!b64) throw new Error('TTS returned no audio');
  return b64;
}

// Audio file -> { transcript, languageCode, languageProbability }. codemix mode
// so Hindi+English notes transcribe intact.
export async function stt(filePath) {
  const buf = readFileSync(filePath);
  const fd = new FormData();
  fd.append('model', 'saaras:v3');
  fd.append('mode', 'codemix');
  fd.append('file', new Blob([buf], { type: 'audio/wav' }), 'audio.wav');
  const json = await post('/speech-to-text', { method: 'POST', headers: headers(), body: fd });
  return {
    transcript: json.transcript ?? '',
    languageCode: json.language_code ?? 'hi-IN',
    languageProbability: json.language_probability,
  };
}

// messages[] -> { content, usage }. Reasoning disabled (summaries need none);
// falls back to low effort if the API rejects a null reasoning_effort.
export async function chat(messages) {
  const call = (reasoning_effort) => post('/v1/chat/completions', {
    method: 'POST',
    headers: headers({ 'Content-Type': 'application/json' }),
    body: JSON.stringify({ model: 'sarvam-105b', messages, reasoning_effort, temperature: 0.2 }),
  });
  // reasoning disabled (null); retry at low effort only if the API rejects null.
  const json = await call(null).catch(() => call('low'));
  const content = json.choices?.[0]?.message?.content;
  if (!content) throw new Error('Chat returned no content');
  return { content, usage: json.usage ?? {} };
}

voxsar.mjs, the pipeline and the cost math:

// voxsar — Indic voice note -> transcript -> summary -> spoken summary (same language).
// Run: node --env-file=.env voxsar.mjs <audio-file>
import { readFileSync, writeFileSync, existsSync } from 'node:fs';
import { stt, chat, tts } from './sarvam.mjs';

// Sarvam pay-as-you-go rates (INR), from SPEC.md §7.
const RATE = { sttPerHour: 30, llmInPerM: 29.28, llmOutPerM: 73.2, ttsPer1000: 3 };

// Duration of a PCM WAV in seconds, from its byteRate + data-chunk size.
// Returns { seconds, exact }. exact=false when the file isn't a parseable WAV.
function wavSeconds(buf) {
  const isWav = buf.length > 44 && buf.toString('ascii', 0, 4) === 'RIFF' && buf.toString('ascii', 8, 12) === 'WAVE';
  if (!isWav) return { seconds: Math.max(1, (buf.length - 44) / 44100), exact: false };
  const byteRate = buf.readUInt32LE(28);
  const dataIdx = buf.indexOf('data', 12, 'ascii');
  const dataSize = dataIdx >= 0 ? buf.readUInt32LE(dataIdx + 4) : buf.length - 44;
  return { seconds: dataSize / byteRate, exact: true };
}

function costLine({ sttSec, sttExact, usage, ttsChars }) {
  const sttCost = (sttSec / 3600) * RATE.sttPerHour;
  const llmCost = ((usage.prompt_tokens ?? 0) / 1e6) * RATE.llmInPerM +
    ((usage.completion_tokens ?? 0) / 1e6) * RATE.llmOutPerM;
  const ttsCost = (ttsChars / 1000) * RATE.ttsPer1000;
  const total = sttCost + llmCost + ttsCost;
  const approx = sttExact ? '' : ' (STT approx — non-WAV input)';
  return `₹${total.toFixed(2)} this run${approx}`;
}

async function main() {
  const file = process.argv[2];
  if (!file) throw new Error('Usage: node --env-file=.env voxsar.mjs <audio-file>');
  if (!existsSync(file)) throw new Error(`File not found: ${file}`);

  const buf = readFileSync(file);
  const { seconds: sttSec, exact: sttExact } = wavSeconds(buf);

  const { transcript, languageCode, languageProbability } = await stt(file);
  if (!transcript.trim()) throw new Error('Transcript came back empty — is the audio valid speech?');

  const { content: rawSummary, usage } = await chat([
    {
      role: 'system',
      content: 'You summarize a voice note in 1-2 short sentences. ' +
        'Write the summary in the SAME language and script as the note. ' +
        'Never translate to English if the note is not in English. ' +
        'Keep every key fact (names, times, tasks). Output only the summary.',
    },
    { role: 'user', content: transcript },
  ]);
  const summary = rawSummary.trim();

  const b64 = await tts(summary, languageCode);
  const outPath = file.replace(/\.[^.]+$/, '') + '.summary.wav';
  writeFileSync(outPath, Buffer.from(b64, 'base64'));

  const conf = languageProbability != null ? ` (confidence ${Number(languageProbability).toFixed(2)})` : '';
  console.log(`\n🎧 voxsar — ${file}`);
  console.log(`Detected language: ${languageCode}${conf}`);
  console.log('\n── Transcript ───────────────────────');
  console.log(transcript);
  console.log('\n── Summary ─────────────────────────');
  console.log(summary);
  console.log(`\n🔊 Spoken summary → ${outPath}`);
  console.log(`💸 ${costLine({ sttSec, sttExact, usage, ttsChars: summary.length })}\n`);
}

main().catch((e) => {
  console.error('Error:', e.message);
  process.exit(1);
});

make-sample.mjs, so you never have to record your own voice:

// Generate a synthetic voice note for testing voxsar — no human recording needed.
// Code-mixed Hindi+English, the way people actually leave voice notes.
// Run: node --env-file=.env make-sample.mjs
import { writeFileSync } from 'node:fs';
import { tts } from './sarvam.mjs';

const NOTE = 'कल morning मुझे office जल्दी पहुँचना है, फिर 3 बजे client के साथ एक ज़रूरी meeting है। ' +
  'शाम को grocery store से दूध, bread और थोड़े fruits ले आना। और हाँ, Rahul को call करके presentation के बारे में बताना मत भूलना।';

try {
  const b64 = await tts(NOTE, 'hi-IN');
  writeFileSync('sample-note.wav', Buffer.from(b64, 'base64'));
  console.log('Wrote sample-note.wav');
  console.log('Try: node --env-file=.env voxsar.mjs sample-note.wav');
} catch (e) {
  console.error('Error:', e.message);
  process.exit(1);
}

That is the whole thing. Three files, MIT-licensed, no dependencies. Copy them, drop your Sarvam key in a .env, and run it on your own notes. And if you are building anything with Indic voice, I want to hear which gotchas bit you. Trade notes with me.

AI Tools & Agents

• The harness — skills, extensions, a scriptable app — is where the leverage lives now that models are commodifying. Link

• Show HN: The load-bearing vocabulary of Claude. Link

• tare: ask Claude Code where your usage went — token audit and limit diagnosis built from local session logs, nothing leaves your machine. Link

• Show HN: an open OpenRouter that turns usage into a better model. Link

• Qwen3.8 27B benchmarked on a Mac Studio M3 Ultra — Ollama and llama.cpp numbers, the 1-bit quant tested. Link

• Coding expertise is going to collapse from AI reliance — the case for ongoing friction in skill formation. Link

• Show HN: screen memory without screenshots — a menu bar app that keeps a written record of what you worked on. Link

• Show HN: a Raspberry Pi 5 + dashcam + local AI turned into a car chat-room agent. Link

• RAG is simpler than you think — six approaches, from minimal to elaborate. Link

Crypto & Web3

• Ambire wallet lets you claim and transfer a bounty in the same transaction, so the funds never touch a compromised wallet.

Mindset & Ideas

• Every workplace has two versions of reality — the one in the announcement and the one people discuss five minutes later in the hallway, and the second one is usually more interesting.

• The trades don't lie. Link

• Before you buy the ₹28,500 ring: the health dashboard your dadi already gave you. Link

Privacy & Security

• VMs won't contain cyber-capable agents — GPT 5.6-Cyber broke out of a VM sandbox three times, and on its final escape chained three 0-days it found on its own. Link

• Nitter goes dark after X Corp cease-and-desist letters demand takedown of every instance and the source repo. Link

• Niantic used 30 billion images crowdsourced from Pokémon Go players to build an AI training and defense-positioning map — 143 million people had no idea what they were contributing to. Link

• Apple threat notifications and spyware: what everyone should know. Link

• CoMaps integration with the wider FLOSS ecosystem. Link

• Show HN: GlassBox — see every signal a website can read from your browser, runs entirely client-side. Link

• GrapheneOS on why Google is throwing away hardware revenue over anti-competitive moves it isn't legally allowed to make. Link

Football & Sport

• How Cole Palmer's positional freedom and vision created tensions for Fulham's defence. Link

• Chelsea finally set to end their hunt for a shirt sponsor — a one-year deal with Circle, putting $USDC on the jerseys. Link

• Emi Martinez to Chelsea ✅

• Enzo Fernández to Man City ⌛

Misc Worth Reading

• India proposes front-of-pack warning labels for packaged foods after public outcry. Link

• The Farcaster client is open-sourced — the endpoint names are a map of everything they don't put in the marketing; the API is still private. Link

• How builders are actually shipping with AI. Link

• Identifying fake cosmetics using AI. Link

• Training AI to paint with code. Link

• How to use Gemini Notebook to learn faster. Link

• Show HN: a retirement simulator built on 125 years of data across 25 countries. Link

From Hacker News

• How Europe is killing makers and micro-entrepreneurs — 1639 pts. Link

• Dolly Parton has died — 1600 pts. Link

• Everything I own, owned — 1445 pts. Link

• Apple introduces M6 and M5 Ultra — 1307 pts. Link

• Nitter and XCancel receive cease and desist notices — 1199 pts. Link

• GLM-5.3-Flash — 1126 pts. Link

• AWS acquires DuckLabs — 1098 pts. Link

• CEO fired developers to make room for AI. Developers create open source AI CEO — 1014 pts. Link

• GUIs should be fully keyboard-driven — 968 pts. Link

• Saving 100 terabytes of memory by optimizing 1.1.1.1's DNS cache — 901 pts. Link

That's a wrap. See you next Sunday - kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

The story is what happened after, when I stopped trading and started reading. Every trade in the competition is recorded on-chain. The winners couldn't hide how they did it, and once I looked, they told me exactly why I lost.

What I built

The event was the Gensyn Delphi Agent Arena: autonomous agents trading test tokens on prediction markets, ranked by profit, top three split a cash pool.

My agent, kazani-oracle, was a TypeScript loop running on GitHub Actions every few minutes. Each tick it pulled the open markets, researched every question with a web-grounded LLM (Perplexity Sonar, which searches the live web inside a single call), turned that into a probability, and, when the probability disagreed with the market price by enough, placed a bet on-chain and held it to settlement.

The plumbing worked on the first live tick: ten real on-chain trades, fills within spec, nobody at the keyboard. It ran untouched for two weeks. If you'd asked me on day one whether I'd built a real trading agent, the answer was yes.

Plumbing isn't edge

Day one I slid down the leaderboard. Not because my predictions were wrong, but because the agent kept re-buying the same thin markets every tick, and each re-entry paid the spread again. I was bleeding slippage, not losing bets. One rule fixed it: bet each market once, then hold. The bleed stopped and profit crawled back to positive.

Positive on test tokens is not winning. I finished around 48th of 107. Plus 67 tokens. The people who won did plus twelve thousand.

This is the part I keep circling. I had solved the hard-looking problem, an autonomous agent that trades real markets on-chain, and completely missed the real one: being right, and betting like it. The plumbing was never the hard part. Anyone with the SDK could build what I built.

Reading the winners trades

The normal move here is to shrug, close the tab, and go find the next competition. I didn't want to. I wanted to know why they won, and for once I had the full record. Every buy, every sell, every settlement, permanent and public on-chain.

So I built a second tool. Give it a wallet address and it reconstructs that wallet's entire competition from the chain's index: every trade, position sizes, entry timing, win rate, realized profit.

I didn't have the winners' addresses. The leaderboard shows names, not wallets. But it shows profit and trade counts, and those turned out to be fingerprints. Only one wallet made 12,967 across exactly 129 trades. Match the number, you've found the person. I found all three.

The four gaps

Here is what the chain showed.

Three completely different ways to win. Jamport barely traded: 10 markets, huge size, went all-in on one, and was right every single time. Ramalogy spread wider and pressed winners hard, betting more than twice the starting bankroll on conviction. tolègba made markets, 1,541 small trades grinding the spread. No shared strategy.

One shared trait: a real edge, sized like they believed it.

I had neither. My win rate was a coin flip. And my bet size, 15 tokens a trade because I'd clamped it to stop the day-one bleed, meant even the markets I got right paid me almost nothing. Egg prices, CPI, "will this product ship by Friday: no", I called the same ones Jamport did. He put the bankroll on them. I put pocket change.

The discipline that saved me on day one is the discipline that capped me for the next thirteen. Small and safe is how you avoid losing. It isn't how you win.

The part that actually paid

I wrote all of this up and sent it to the team as feedback. Not my profit, my read of it: what I built, what broke, what the winners did differently, what I'd change before risking real money.

That's what converted. They replied, invited me onto their X Space, and then picked me for a paid interview about the winning strategies. The mid-pack finisher got the same seat as the winners, because I'd studied the game instead of only playing it.

Which is the point, shrunk down. I handed the trading to an agent and it lost. I kept the understanding, and the understanding is what got paid. The agent was the replaceable part.

If you're building agents to act for you, that's the split worth watching. Let the machine do the work. Keep the understanding for yourself.

I build small things solo and write up what I learn. The agent, the winner-analysis tool, and the full teardown aren't public yet, but I'm happy to share the code and walk anyone through it.

The ring is in your cart. Titanium, matte black, good reviews. You've done the math on the ₹28,500 and told yourself it isn't a gadget, it's an investment in finally knowing your own body. Sleep depth, recovery, the metabolic stuff. Real numbers, at last, instead of guessing.

Wait before you tap Buy.

Almost everything that ring is about to measure has been sitting inside your body this whole time. Your grandmother could read most of it without charging anything overnight. She didn't call it HRV. She looked at your face and knew you'd slept badly. She watched you push your plate away and knew your digestion was off. No app, no subscription, no score to make you anxious about the score.

That's not nostalgia. It's the argument this piece makes.

I almost bought it too

I was the target customer. Three tabs open, Ultrahuman versus Oura versus just-buy-the-Apple-Watch, cart loaded, finger hovering for days. What gave me pause wasn't willpower. It was a plain observation most of us from an Indian household can make: there is usually someone at home who reads the body without a single gadget. They take one look at your face and know you slept badly. They watch you leave half your plate and know your digestion is off. Usually right before any number would have flagged it.

That left me with a question I couldn't shake. Is tracking the same as knowing?

I'm not a Vaidya (Ayurvedic doctor), and I'm not against technology, I work with it. But I was about to pay for a skill that was arguably already in the house, sitting in a tradition most of us had quietly filed under "grandmother stuff." The grandmother stuff has names, a system, and about five thousand years of field notes.

What you'll walk away with

Three things. What that ring actually measures, and why it's a skill you can build rather than a substance you buy. Four things Ayurveda formalised centuries ago that today's wearables are now re-deriving at a premium. And how to run one of these reads tomorrow morning, before your feet touch the floor, for free.

None of this is an argument against buying the ring. It's an argument for knowing what you're buying first.

The problem was never data

Something quiet has happened to a lot of us. We've started feeling like we can't trust our own sense of our health until a number confirms it. You slept fine, the app says 61, and now the day feels off. The reflex fix is better tech, cheaper tech: wait for the ring to get affordable, democratise the data, sorted.

That skips what the device actually does. It doesn't hand you the skill of reading your body. It replaces it, and often makes it worse. There's a clinical name for the sharp end of this, orthosomnia (sleep-tracker anxiety), where people buy a tracker to sleep better and sleep worse because the score itself becomes one more thing to worry about. The tool meant to fix the problem starts causing it.

Data was never the bottleneck. Interoception was: the trained ability to read your own internal signals. India didn't lack this. It built one of the most detailed systems for it anywhere, then got talked into buying the ability back at a premium. If the real asset is attention, the ring is a downgrade with an EMI plan.

Four translations make this concrete. Old idea on the left, the wearable chasing it on the right.

1. Agni: your metabolic dashboard

Agni (digestive fire) is the exact thing a continuous glucose monitor you re-buy every couple of weeks and a microbiome kit are trying to put a number on. Drop the Sanskrit and agni just means how cleanly you turn food into steady energy, and how well your gut runs from day to day.

You already have the readout. Eat your dal-chawal lunch and notice where you are ninety minutes later. Clear and steady, or foggy and reaching for chai and a nap? That crash is a glucose curve. You're reading it directly instead of through a sensor stuck in your arm. Add the second free signal: a daily, well-formed bowel movement, ideally around the same time. That's your microbiome report, and it costs nothing.

Tomorrow, clock your energy ninety minutes after lunch. One honest read.

Agni tells you how you process the world. The next reading tells you how much reserve you have to withstand it.

2. Ojas: your recovery score

Ojas (vital reserve) is the buffer that decides whether a bad night, a heavy wedding meal, or a brutal week at work flattens you or barely lands. That buffer is what a Whoop recovery percentage gestures at, and what inflammatory blood panels chase after the fact.

The free version is one question. How many days do you take to bounce back? A hard workout, a dodgy restaurant meal, a stressful stretch: does a small hit knock you out for two or three days, or do you reset by morning? Resilience is the metric, not a number, and ojas named that idea long before recovery got a dashboard.

After your next stressor, count the bounce-back days. Honestly.

Reserve shows up over days. The next signal you read the moment you wake.

3. The morning read: nadi, tongue, first light

The old morning self-check is what Ayurveda calls nadi pariksha (pulse reading), plus a look at the tongue, the first bowel movement, and the quality of your waking mind. It's the original version of the sleep report you thumb through before your feet hit the floor.

These are the body's overnight status lights. Can you hold your attention for thirty minutes after waking, no fog, no headache? That's a cleaner read on sleep quality than any stage graph. How settled is your head before caffeine, before the phone, before the world gets a vote? That's your nervous system telling you where it's set this morning. The Oura report is this same inspection, the dinacharya (daily routine) morning check, dressed in biometrics.

Tomorrow, before you touch your phone, take sixty seconds. How clear is your head? What's your first honest read of your own body?

These reads only mean something inside a stable rhythm, which is the fourth translation, and the one no wearable can sell you.

4. Dinacharya: the foundations even the biohackers admit come first

Dinacharya means daily rhythm: a consistent wake time, morning light, regular meals, a real wind-down. Here's the tell. Even the most gadget-maximalist optimiser will admit these boring inputs matter more than any metric on any ring. Get your foundations right first, they say, or the fancy data is just noise.

That's a five-thousand-year-old instruction reached by process of elimination. It pairs with the deepest idea of the lot, prakriti (your individual constitution). The wearable sells one dashboard to everyone and calls the average "normal." Ayurveda started from the opposite end: your baseline is yours, learning it is the whole point, and measuring yourself against a stranger misses it.

Tomorrow, anchor one thing. Same wake time, or ten minutes of morning light.

Four translations, one pattern. Not one of them needs a battery.

The actual experiment

Don't turn this into a checklist you obsess over. That just rebuilds the same anxiety in a kurta. Do the opposite. Pick one signal.

Tonight, choose one of the four. New to this? Take the morning read. Highest signal, near-zero effort.

Tomorrow, before the phone, spend sixty seconds on that one read. Write it down, one line, on paper. Analog on purpose. No app.

After a week of the same single read, you'll have something no first-day device gives you: your own baseline. Not a population average, your normal.

Then refine. And if you still want the ring, buy it. Genuinely. You'll just know exactly what it's meant to confirm, which makes you the qualified user instead of the overquantified one. This was pre-purchase clarity, never a purity test.

One honest caution, because of where we live. This is about everyday self-knowledge in a healthy body. If you're managing a diagnosed condition, diabetes especially, and India has every reason to take that seriously, your doctor's tools are not the villain here. Read your body and keep your CGM. Different jobs.

The finger, still hovering

Back to the cart. The ring is still sitting there, and it's genuinely a nice piece of hardware.

You know something now that you didn't ten minutes ago. It measures a skill you can build for free, and your own tradition already wrote the manual. Everything the device promises to tell you, your body is already saying. You were just never taught the language, or you were taught to distrust it until a number agreed.

It comes down to one line. Before you buy the instrument, learn that you already are one.

One signal. Tomorrow morning. Before you touch your phone.

Pick one of the four and read it tomorrow before your phone gets a vote. Reply and tell me which one you chose and what it said. If enough of you ask, I'll go deep on a single reading next, ojas or agni, whichever the replies want.

AI Tools & Agents

• Readers can't reliably tell watermarked AI text from human writing, a study finds. Link

• OpenVibe: an open-source Tauri+Rust IDE for agentic coding, using up to 4.5x less RAM than Electron-based tools. Link

• Ben's Bites on how builders are actually shipping with AI. Link

• Dayflow: an open-source app that auto-journals your day from screen recordings. Link

Crypto & Web3

• Stablecoins moved $12tn last year — a16z calls it the "WhatsApp moment" for money. Link

Mindset & Ideas

• Some things become less valuable the moment you possess them — worth thinking harder about what you're actually chasing before you acquire it.

• Trust gets complicated the moment someone else has something to lose — the strongest kind comes with a responsibility you can feel even when nobody's watching.

Privacy & Security

• AgePony: post-quantum (ML-KEM-768) file encryption and signing for iPhone, Android, and desktop — open source, no accounts, keys never leave your device. Link

• SMSecure and Deku SMS bring Signal-protocol encryption to plain SMS on Android. Link

• Germany forces Apple to make its EU tracking-consent prompts neutral, ending years of self-favoring design.

• Google will require developer ID verification starting September 30. Link

• GrapheneOS explains why /e/OS, Murena, and Fairphone fall short on privacy. Link

Football & Sport

• Shakhtar Donetsk will play their Champions League home games at Stamford Bridge this season.

• Premier League 2026/27 rule changes: mandatory 1-minute injury stoppages, VAR review on incorrect second yellows, a 5-second throw-in/goal-kick countdown.

Misc Worth Reading

• Leaked video suggests new AirPods will pack cameras for Siri "Visual Intelligence." Link

• Protesters demand India replace caste-based reservation quotas with economic criteria, plus a "one family, one reservation, one time" sunset rule.

• kazani built a 3-minute silent video from real, verifiable Farcaster casts — "AS RECORDED: Farcaster Seasons 1 & 2."

From Hacker News

• Aaron Swartz was prosecuted for scraping, while Meta does it without consequence — 1668 pts. Link

• OpenLogi — 1623 pts. Link

• The Amazon tax — 1402 pts. Link

• Kagi added a setting for removing paywalled links from search results — 1240 pts. Link

• AI;DR (AI; Didn't Read) — 1109 pts. Link

• Felony charges for a citizen who deleted phone data at the US border — 1065 pts. Link

• Israel created a fake think tank in a likely attempt to dupe AI chatbots — 1054 pts. Link

• Don't paste the AI, please — 1041 pts. Link

• AliExpress runs silent WebAudio fingerprinting that breaks Bluetooth multipoint — 1026 pts. Link

• A joke domain purchase turned into geopolitical warfare — 1026 pts. Link

That's a wrap. See you next Sunday — kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

AI Tools & Agents

• If you haven't recently used Claude Code, you might not understand where AI is at. Link

• The Most Dangerous Thing AI Can Automate Isn't Coding — the risk isn't thinking less, it's letting "not thinking" become the rational default; the real skill is knowing what to delegate and what has to stay yours. Link

• Ben's session #2. Link

• A Reddit thread jokes about AI replacing every role on a startup team — then the comments actually assemble the whole team anyway. Link

Crypto & Web3

• Stop asking AI to predict the market. Ask it to predict you — 87% of crypto trading bots lose money in year one; the traders who make AI pay point it at themselves instead. Link

• On edge and max extracting — that BTC edge is slowly disappearing too, but new opportunities keep showing up in different forms. Link

• Everyone should be building AI-assisted trade monitoring — log every trade and ask Claude to spot your own patterns, like relaxing into bad trades right after a big win.

Mindset & Ideas

• Audience market cap: as content becomes infinite, raw follower count matters less than who actually trusts your take enough to act on it.

• Genuine curiosity will always beat performative intellectualism — knowledge has become another aesthetic; the strange part begins when looking thoughtful matters more than actually thinking. Link

• The Cognitive Cost of Brain Rot: a 439-person study found chronic digital fatigue doesn't cause depression directly — it triggers a burnout "loss spiral" that does. Link

• A quiet life can still be a full one — peace isn't having nothing left to worry about, it's how much noise you still carry after the noise is gone.

Privacy & Security

• Stop wishing your phone had a guest lock. It already has one — iPhone's had Guided Access since 2012, Android's had Screen Pinning since 2014; the feature was never missing, the manual was. Link

• Signal launches automatic key verification, confirming a contact's number matches their public key to catch man-in-the-middle attacks — audited by Cloudflare and Trail of Bits.

• A phenomenal short documentary breaks down how DPRK's North Korea threat actors operate in crypto. Link

• Is your vibe-coded app secure? Run this audit. Link

Football & Sport

• AFC Bournemouth slammed by fans after a staff member of nearly 60 years was told over email, two weeks before the season, that his contract wouldn't be renewed. Link

• Almost all good players are good jugglers, but not all good jugglers are good players.

Misc Worth Reading

• Draining India's Small Farms to Sustain the City — critiques of Indian agriculture fixate on cash crops and mandi procurement, overlooking the smallholders growing pulses and millets who were never part of the formal system to begin with. Link

• Bangladesh became the Asian team to take the fewest Tests to beat Australia in Australia.

From Hacker News

• Firefox is now the last major browser that still supports uBlock Origin — 1672 pts. Link

• Qwen 3.8 27B — 1375 pts. Link

• Tracking down the 16-year-old WAL-reset SQLite bug — 1206 pts. Link

• Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows — 1203 pts. Link

• GLM-5.3: Frontier coding with emergent cyber capabilities — 1144 pts. Link

• France to ban unsolicited telemarketing calls — 1059 pts. Link

• DeepSeek V4 Pro 0813 — 1033 pts. Link

• AI is removing the middle class of software engineering? — 991 pts. Link

• Gemini 3.7 Flash — 962 pts. Link

• Why does Opus 5 feel worse to work with? — 944 pts. Link

The Most Dangerous Thing AI Can Automate Isn't Coding

AI won't necessarily make us think less. It may make **not thinking the rational choice.** When AI can generate 10 answers in seconds, humans risk becoming selectors instead of thinkers. The real skill isn't using AI less. It's knowing **what to delegate and what must remain yours.** Delegate execution.

https://paragraph.com

Stop asking AI to predict the market. Ask it to predict you.

The number nobody selling that dream leads with: 87% of retail traders running automated systems lose money in their first year. That figure isn't from a hater. It's from a company that sells trading bots. When the people profiting off the fantasy quietly admit the fantasy loses, it's worth stopping.

https://paragraph.com

Stop wishing your phone had a guest lock. It already has one.

You can. You've been able to for years, and nobody ever showed you. Last week I read a sharp little post titled "The phone features I can't believe we don't have." Top of the list: a guest lock that pins your phone to the app you're showing, and a way to hide photos from the camera roll.

https://paragraph.com

That's a wrap. See you next Sunday - kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

You can. You've been able to for years, and nobody ever showed you.

Last week I read a sharp little post titled "The phone features I can't believe we don't have." Top of the list: a guest lock that pins your phone to the app you're showing, and a way to hide photos from the camera roll. The writer wanted both. The comments nodded along. Of course we don't have that.

Except we do. Both of them. On iPhone and Android, shipped and sitting in Settings right now.

I know because I went to build the thing. I spent a day making a little app for exactly this handoff moment, and somewhere in the middle I realized I was rebuilding a feature Apple shipped in 2012. The app taught me something anyway, and I'll get to it. But the first lesson was blunt. The feature isn't missing. The knowledge is.

Three things below. The settings that already do "guest lock" and "hidden photos" on the phone in your hand. Why they stayed invisible this whole time. And the one case they genuinely don't cover, plus the fast fix for it. If you've ever done the hover-thumb handoff, this is for you.

When you can't do something on your phone, the story you tell yourself is that the feature doesn't exist. Apple hasn't built it. Android's too messy. Someday, maybe.

That story is wrong here, and it's wrong in a specific way. Guided Access, the iPhone feature that locks your phone to one app, shipped in 2012. Android's version, Screen Pinning, landed in 2014. They've been in every phone you've owned for more than a decade.

So why does everyone, including a writer sharp enough to publish a features wishlist, believe they're missing? Because they're buried. Guided Access hides under Settings, then Accessibility, three layers deep, behind a name that sounds like it's meant for someone else. Screen Pinning sits under Security behind a phrase nobody thinks to search. And even once you find them, arming them takes enough taps that you'll never reach for it in the five seconds you're actually handing the phone over.

That's the real problem. Not capability. Discovery, and friction at the worst possible moment. Which changes what you should do about it. Stop waiting for the feature. Go turn on the setting. And for the five-second case, get something faster than the setting.

The guest lock is already there

Pinning your phone to a single app is one gesture on both platforms.

On iPhone it's Guided Access. Turn it on once in Settings, then Accessibility, then Guided Access, and set a passcode. After that, open the photo or ticket you want to show, triple-click the side button, and the phone freezes on that screen. No swiping out, no home screen, no app switcher, until you triple-click again and enter your code. This is the exact guest lock the wishlist asked for.

On Android it's Screen Pinning. Settings, then Security, and flip it on. Open your app, swipe up to the recents view, tap the app's icon, and hit Pin. To leave, you hold Back and Recents together and unlock. Same idea, same result.

Turn one of them on right now, before you read the next part. Thirty seconds, and you'll have it forever.

The catch: it's fiddly to arm in the moment. Hold that thought.

Hidden photos are already there

Your private shots can be walled off from the camera roll without installing anything.

On Android, Google Photos has a Locked Folder. Anything you move into it drops out of the main grid and sits behind your fingerprint or PIN. A screenshot of your ID, a photo of a document, whatever you don't want surfacing when someone scrolls. Move it there and it's gone from the roll.

On iPhone there's a Hidden album, and on recent versions it's locked behind Face ID by default, along with Recently Deleted. Open Photos, scroll to Utilities, and you'll find the Hidden album that won't show its contents until your face clears it.

That's the second wish, granted. Do it now with three photos you'd rather nobody stumbled into.

The catch: this protects the whole library. Showing one photo still means handing over everything else.

Lock a single app behind your face

You can lock individual apps behind Face ID or a fingerprint, no third-party app, no sketchy download.

On iPhone with iOS 18, press and hold any app icon and you'll see Require Face ID. Turn it on and that app won't open for anyone but you, even when the phone is already unlocked. Messages, Photos, your banking app, your call.

Android has had versions of this for a while, and many phones from Samsung and others ship a built-in App Lock or Secure Folder in Settings. Same outcome. The app opens for you and nobody else.

People download shady "app locker" apps for exactly this, handing permissions to a stranger, when the phone does it natively. Lock one app now as a test.

The catch, and it's the one that ties all three together: every one of these takes a few taps to set up in the moment. Strong for the planned case. Too slow for the five-second one.

The one thing your phone doesn't do

Here's the gap none of the three fill cleanly. The everyday case. Someone's standing in front of you, you want to show them this one photo, right now, and you're not going to walk through Guided Access setup while they wait.

That's the thing I built. It's called Handoff. You pick the photo or photos you want to show, it opens them full screen in a locked viewer, and getting back out takes your PIN. Swipe all you like, you only ever see the ones you picked. It runs in the browser, installs to your home screen like a normal app, and every photo stays on your phone. Nothing uploads, no account, no server.

Now the honest part, because it's the whole point. A web app cannot block your phone's app switcher. Someone determined can still swipe up and out of it. I hit that wall building it, and it's exactly why the native features in the first three sections still matter. Handoff is for the friendly five-second handoff, the stranger checking your ticket. Guided Access is for the case where you actually don't trust the person holding your phone. Two layers, two jobs.

If I'd hidden that limit and sold it as a vault, you should have stopped trusting me. It isn't a vault. It's the fast lane for the low-stakes moment the native tools are too slow for. You can try it here.

Five minutes, once

Reading this changes nothing. Doing it takes five minutes, once.

Turn on Guided Access on iPhone, or Screen Pinning on Android. The menu paths are up in the first section. This is your real lock.

Move three photos you'd rather keep private into the Locked Folder on Android, or the Hidden album on iPhone.

Lock one app behind Face ID as a test, so the gesture is in your fingers when you need it.

Then hand your phone to someone in the room with one of these armed, and watch it hold. Feel how solid that is next to the hover-thumb you've been doing for years.

Last, for the quick case, try Handoff and feel the difference in speed. You'll land on your own rule fast. Native tools for anything that matters. Handoff for the five-second show.

The manual was missing, not the feature

Go back to that hovering thumb. All this time you thought your phone couldn't protect that moment, and the truth is it could. You were just never shown the screen. The feature wasn't missing. The manual was.

Your phone already does most of what you wish it did. The gap was never capability. It was that nobody walked you to the setting. So walk yourself there now. Open Settings and turn the lock on before you close this tab.

Now I'm curious, genuinely. What's the phone feature you were sure didn't exist? Guided Access got me. There's a whole list of these hiding in plain sight, and I want to build it.

Reply and tell me the one you can't believe was there the whole time. If enough of you send them, that's the next post.

The number nobody selling that dream leads with: 87% of retail traders running automated systems lose money in their first year. That figure isn't from a hater. It's from a company that sells trading bots. When the people profiting off the fantasy quietly admit the fantasy loses, it's worth stopping.

And yet a handful of traders are making AI pay. They're doing something that looks backwards. They pointed it away from the market and at themselves.

I'm not going to tell you I cracked live crypto trading. I didn't. What I did was go looking, after the hundredth "autonomous trading agent" thread, for what works instead of what sounds good on launch day.

The trader who stopped me wasn't building an oracle at all. He had a vague suspicion about himself: after a big win, he'd get loose, take a trade or two he had no business taking. He'd felt it for years but never measured it. So he dumped his trade history into Claude and asked it to look.

He was, in his words, surprised how many times it happened and how much money he handed back making the same mistake over and over. Then he built a small bot that prompts him on every trade and reminds him of that pattern before he can repeat it.

That reframed the whole thing for me. The question was never "can AI predict the market?" The pros won that one, with faster data and machines you'll never match. The better question: what if I aimed it at the one thing I control?

Three things below. Why predicting the market is rigged against you. The reframe that needs no market edge. And a loop you can run this week with tools you already pay for. If you've watched a bot lose and suspected the real leak was closer to home, this is for you.

When you lose, you blame the strategy. Bad entry, wrong indicator, market's rigged. So you hunt for a better edge: sharper signals, a smarter model, more parameters.

What that story leaves out is where the money went. For most retail traders the loss isn't in the thesis at all, it's in the behavior wrapped around the thesis: the position you sized up because you were angry, the entry you chased because everyone was already in, the stop you slid because you couldn't stand being wrong.

You don't have to take my word for it. Journaling is the single habit almost every serious trader calls the most important thing they do, and almost nobody keeps it up. Ask why on any trading forum and the thread writes itself: everyone knows, nobody does it. And the damage underneath isn't subtle. There's an entire corner of Reddit, r/tradingpsychology, that exists because of it. "Lost everything to revenge trading" is a real post title. So is blowing up an account by sizing up after a loss.

The mistakes repeat. They're patterned. And a pattern in your own history is something you can find, if you point the right tool at it.

The leak is patterned

Start with the uncomfortable premise: your worst losses are probably a few behaviors you repeat, not a broken thesis.

Tilt, revenge trading, sizing up after a win, chasing tops. In the moment none of these feels like a pattern. Each one feels like this time being different, this setup being special. Stack ninety days of trades together and they stop looking special. They start looking like a schedule.

The trader I mentioned couldn't feel how often he over-risked after a win. He could only see it once something counted it for him. The leak is invisible at the level of a single trade and obvious across your full history.

So the first move isn't a better strategy. It's finding the leak.

Point the AI at yourself, not the market

The reframe: you cannot reliably beat the market, but you can reliably stop beating yourself. Only the second one is a game you can win.

Beating the market means out-trading firms with faster data and teams of quants. That's the game the 87% keep losing. Pointing AI at your own behavior is different. You're not competing with anyone. You're reading a dataset only you have, where the pattern is already sitting in plain sight, waiting for someone to count it.

Think mirror, not oracle. The oracle promises to tell you what the market will do, and it lies. The mirror tells you what you keep doing, and it's right, because the evidence is your own trades.

The reason this works now and didn't a few years ago is that the hard part collapsed. This used to mean obsessively diarizing every trade and being good at slicing your own data to find anything in it. Now it's two moves: log the trades, and ask Claude to compile them and tell you what you keep doing.

There's one catch. A mirror that only shows you the mistake after it happened is useful, but late.

The loop: log, find, nudge

The full loop is three steps, and it's the third one almost nobody ships.

One, log every trade automatically. If you trade perps, this is easy. The exchange APIs hand you the data. If you trade onchain, it's easier than you'd think, because the record is public and you can pull your wallet's history directly. The genuinely messy case is spreading across perps, spot, onchain, and a CEX at once, which is why most people give up and journal nothing.

Two, hand the log to Claude and ask what you keep doing. Not "how were my trades," but "what do I keep doing around wins, losses, and sizing, and what did each pattern cost me." Make it put a number on the leak. The number is what turns a vague feeling into something you can't unsee.

Three, the step that matters: turn each pattern into a rule that hits you before the next trade, not after. This is where the tools fall short. The sharpest thing I read in all of this was a trader saying a journal that only explains the mistake afterward is useful but late. Every polished AI trade journal does the after. Almost none do the before. And if you trade crypto, notice the gap: those journals are built for stock and futures traders. The onchain and perps crowd is barely served on the one step that counts.

Try it this week

You don't need to build anything yet. Try it on your own trades.

Pull your last thirty to ninety days. A perps API export, your onchain history, or a plain CSV, whatever you can get fastest. Hand it to Claude with one prompt: find my recurring behavioral patterns, especially around wins, losses, and position sizing, and estimate what each one cost me.

Then look for the single leak with the biggest number next to it. The trader's was over-risking after a win. Yours might be revenge entries, or holding losers too long, or piling in at tops. Check it against your gut. You probably already half-knew, which is why seeing it counted lands harder than any strategy tip.

Write that one pattern as a single if-then rule. "If I just closed a big win, no new position for thirty minutes." "If I'm adding to a loser, stop." Put it somewhere that reaches you at decision time, before the click. A sticky note, an alert, a bot that pings you, whatever you'll actually see. The goal isn't a dashboard. It's one behavior changed, with a number behind it.

The mirror, not the oracle

Forget the bot that prints money while you sleep. That's the oracle, and it has an 87% failure rate its own vendors admit to. The tool worth building is the mirror: the thing that catches you before you hand a good win back.

The edge you can get isn't over the market. It's over yourself. And the first step costs nothing but the export. Pull your log and ask what you keep doing.

Now I'm asking, because I want to know. Do you journal your trades? Really, or the way everyone means when they say they should? And would you use something that nudged you before you tilt, not after the money's gone? Or is that just me.

Reply and tell me. If enough of you say "shut up and take my money," that's the next thing I build.

He worries that working with LLMs is training him to spend more of his time skimming and judging rather than thinking slowly.

How to keep thinking

Imagine you're the guest on some kind of frenetic, software-engineering-themed game show. The host is constantly flipping over new cards with questions that you have to answer as fast as possible: Is this adjustment to the database schema right? Do these bits of data look plausible?

https://www.seangoedecke.com

I think he’s right.

But I think there’s a deeper problem underneath it.

The danger isn't simply that AI might make us think less.

It might make not thinking the rational choice.

The new shape of work

Goedecke describes working with AI as something like a frenetic software-engineering game show.

An agent gives you an architecture.

You judge it.

Another agent gives you an implementation.

You judge it.

Another gives you tests.

You judge those.

Then another proposes a completely different approach.

You compare.

Reject.

Accept.

Modify.

Delegate.

Repeat.

You can be extremely busy. You can even be highly skilled.

But the shape of your cognition has changed.

You're spending more time asking:

“Which of these answers is good?”

and less time asking:

“What do I actually think?”

That's not the same thing.

Goedecke calls this a shift toward the quick “skimming and judging” parts of the mind and away from the slower reflection required for deep thought and creativity. His solution is surprisingly old-fashioned: read difficult books and write in your own words.

I think that is only the beginning of the argument.

AI doesn't need to make you stupid

Imagine two people solving the same problem.

The first spends three hours trying to understand it.

They form a mental model (an internal map of how things work), make wrong guesses, discover contradictions, and eventually develop their own solution.

The second asks an AI for ten possible solutions.

They skim them.

They choose the best one.

Then they ask the AI to implement it.

The second person may be dramatically more productive.

And that's exactly the problem.

The second person may also be getting less practice at the thing that made the first person capable of solving novel problems in the first place.

This isn't an argument against AI.

It's an argument about training.

If you stop lifting weights because a machine can move the weight for you, you haven't disproved the value of strength. You've simply stopped training it.

The same may be true of cognition.

If AI increasingly performs the generation, exploration, explanation, implementation, and even criticism, what remains for the human?

Selection.

“Option three looks best.”

That's a useful skill.

But selection is not the same as understanding.

The economic problem is worse

Here's where I think Goedecke's argument deserves to be pushed further.

Suppose deep thinking makes you better at your job.

But suppose another person uses AI aggressively and produces ten times as much visible output.

Who does the company reward?

Usually, the second person.

Not because the company is evil.

Because the incentive is obvious.

If technology gives everyone a “make this ten times faster” button, refusing to press it can become a competitive disadvantage. Goedecke makes essentially this point himself: people are heavily incentivized to use these tools when their peers are doing so.

So this isn't merely a personal discipline problem.

It is a system problem (a problem created by the surrounding rules).

AI can create an environment where:

speed → more output → more reward → more speed

And then the environment selects for people who are increasingly good at managing AI output.

The loop reinforces itself.

Eventually, deep thinking becomes something you have to protect outside the workday.

That's exactly what Goedecke predicts when he says we may need to find ways outside work to maintain the habit of thinking slowly.

And that possibility is much stranger than “AI makes us lazy.”

The real scarce resource isn't answers

For most of human history, information was scarce.

Then the internet made information abundant.

Now AI is making answers abundant.

So what becomes scarce?

Judgment.

But even that isn't quite enough.

Because judgment requires something underneath it.

You need to know:

• What problem are we actually solving?

• Is this even the right problem?

• What assumptions are hidden here?

• What do I believe?

• What tradeoff am I willing to make?

• What outcome actually matters?

• What should I refuse to optimize?

AI can help with all of these questions.

But there is a crucial difference between using AI to interrogate your thinking and using AI instead of thinking.

The first expands your mind.

The second can gradually turn your mind into a review interface.

Don't outsource the formation of your worldview

This is where I think the conversation about AI needs a better rule.

We keep asking:

“What should humans still do?”

That's the wrong question.

A better question is:

“What should remain ours?”

Let AI handle things that are mechanical, repetitive, searchable, testable, or easily reversible.

Let it explore possibilities.

Let it generate drafts.

Let it write code.

Let it summarize ten papers.

Let it attack your argument.

Let it give you perspectives you hadn't considered.

But be careful about outsourcing the parts that determine the direction of your life.

What problem is worth solving.

What you actually believe.

What you value.

What risks you're willing to take.

What kind of person you're trying to become.

What kind of world you're trying to help create.

Those aren't merely tasks.

They're acts of authorship (choosing what your life means and does).

And if you outsource enough of them, you may become extraordinarily effective at living a life you never consciously chose.

There's a useful distinction here

Think about two workflows.

The first:

Ask → receive → accept → execute.

This makes AI your substitute.

The second:

Think → write → ask → challenge → revise → decide.

This makes AI your adversary and collaborator (something that helps you test yourself).

The difference is enormous.

Before asking AI, try to form your own answer.

Write it down.

Then ask AI to attack it.

Find where you're wrong.

Ask what you're missing.

Generate alternatives.

Then make the final judgment yourself.

This creates a productive tension (useful pressure between opposing ideas).

You're not protecting your brain from AI.

You're using AI to make your brain work harder.

Why writing matters so much

This is also why Goedecke's recommendation to write in your own words is more profound than it initially sounds.

When you say:

“I have an idea.”

you often don't.

You have a feeling that an idea exists somewhere nearby.

Writing forces you to find it.

A vague intuition becomes a sentence.

The sentence creates a contradiction.

The contradiction forces another distinction.

The distinction reveals an assumption.

The assumption turns out to be wrong.

And suddenly you understand something you didn't understand when you started.

The writing wasn't communication after the thinking.

The writing was the thinking.

That's why having AI write the whole thing for you can be subtly dangerous, even when the final article is better.

You may end up with a polished expression of an idea you never fully constructed.

The artifact improves.

The thinker doesn't necessarily improve with it.

Goedecke makes essentially this point when he says that putting words together yourself forces you to articulate your thoughts, and that the idea itself is often constructed during writing.

The question isn't “AI or no AI?”

That debate is already obsolete.

The better question is:

Which cognitive muscles should I automate, and which should I deliberately keep exercising?

I don't want to manually perform every task AI can perform.

That would be ridiculous.

I want AI to remove the boring parts so I can spend more time on the interesting parts.

But there's a catch.

You don't always know which parts are boring until you've become good at them.

Learning architecture may feel slow.

Writing may feel inefficient.

Reading a difficult book may feel painfully unproductive compared with asking an AI for its summary.

Sitting alone with a problem for two hours can feel absurd when an AI can give you twelve plausible answers in thirty seconds.

But that friction may be doing something.

It may be building the very capacity that allows you to recognize which of those twelve answers is actually worth taking seriously.

The deeper question: which problems remain yours?

This is the part I find most interesting.

If AI can increasingly solve problems, the defining human advantage may shift from solving problems to choosing problems.

And choosing problems is not a trivial optimization problem.

Your life is partly the collection of problems you decide are worth suffering for.

Some problems make you smaller.

Others force you to grow.

Some are assigned to you by institutions, employers, algorithms, parents, or culture.

Others are chosen.

The difference matters.

Because once AI can solve almost anything, the question becomes:

What deserves to be solved?

And then:

Why should I care?

And finally:

What kind of life am I building by spending my limited attention on this problem?

Those questions cannot be delegated without consequences.

You can ask AI for its answer.

You shouldn't let it quietly become the author of yours.

The new rule

So I don't think the lesson from Goedecke's essay is:

“Stop using AI.”

It's almost the opposite.

Use it aggressively.

But maintain a part of your life where you are forced to think without it.

Read things that are difficult.

Write things that nobody asked you to write.

Sit with problems before asking for solutions.

Form your own hypothesis before seeing the model's answer.

Argue with the machine.

Let it argue back.

And occasionally experience the uncomfortable sensation of having absolutely no idea what you think.

That's usually where thinking begins.

Because the real danger isn't that AI will think for us.

It's that AI will become so good at thinking on demand that we stop noticing when we've stopped thinking for ourselves.

The future may not belong to people who refuse to use AI.

It may belong to people who know when not to.

And perhaps even more importantly:

people who still know what is worth thinking about.

AI Tools & Agents

• Free AI Prompt Gen: an open-source, local-first prompt engineering tool built on the RTF and CO-STAR frameworks. Link

• AI RiskAtlas: an interactive lab mapping GenAI and agentic AI failure modes, attack scenarios, and defenses — free, no signup. Link

• AirLLM runs 70B-parameter inference on a single 4GB GPU. Link

• Lilian Weng on harness engineering for self-improvement, tracing recursive self-improvement from I.J. Good's 1965 "ultraintelligent machine" to now. Link

• Five new agent skills for Claude, Cursor, and Codex: no-slop, blindspot-check, positioning-with-ekram, thiel-style-converter, and book-finder. Link

• Show HN: fine-tune an 8B model on a 4GB laptop GPU via layer streaming. Link

• webclaw turns any website into clean markdown, JSON, and LLM-ready context. Link

• Prime Agent: an open-source, self-improving RLM harness that scores 95.5% on ARC-AGI-3, beating the human-expert baseline. Link

• VISTA gives a VLM long-horizon vision — paired with Claude Opus 5.0, it perfectly solves all 25 public ARC-AGI-3 games. Link

• Turned Daniel Miessler's system-upgrade prompts into a portable Claude Code skill for auditing your own harness, security posture, and strategic focus. Link

Crypto & Web3

• Base app: "it pays to be here." Link

• Kalshi is now the official prediction-market partner of the FIFA World Cup.

• Cloudflare Wallet: reserve your Cloudflare Wallet name. Link

Mindset & Ideas

• "The peeps in business of religion have the greatest conviction that there are no Gods and no repercussions for any acts good or bad" - religion as a gateway to power and money, not faith.

• Frontier models quietly change behavior depending on who they think they're talking to recognized AI safety researchers get less confident responses, more reasoning, and less suspicion on dual-use requests. Link

Privacy & Security

• BMW is pushing full-screen ads onto dashboard displays — "we need adblocker for cars." Link

• Signal is quietly building phone-number-free registration, still wrestling with how to stop spam without one. Link

• Cops are getting license plate readers that also track your iPhone and AirPods in public. Link

• Netflix now requires every profile on an account to carry its own unique email address. Link

Misc Worth Reading

• iPhone 18 and 18e reportedly jump to 9GB RAM, per Ming-Chi Kuo. Link

• West Bengal is reportedly dropping eggs from school mid-day meals for an ISKCON vegetarian-only contract, while other states expand protein access. Link

From Hacker News

• Don't be a meat proxy — 1837 pts. Link

• In Memory of My Wife, Elise Cawley, with Thanks for 36 Wonderful Years — 1637 pts. Link

• LLMs reward expertise — 1409 pts. Link

• Mario Meets Pareto — 1168 pts. Link

• Qwen3.8-Max: A New Bar for Coding and Cowork — 1120 pts. Link

• What happens if an entire class of workers loses faith in their careers — 1004 pts. Link

• Discovery Loop — 945 pts. Link

• AMD acquires Taalas to boost inference performance by etching models in silicon — 927 pts. Link

• US strikes $1.2B deal to pay German firm to halt offshore wind projects — 894 pts. Link

• Changes at Google DeepMind: Demis Hassabis from CEO to Chair, Jeff Dean departs — 855 pts. Link

That's a wrap. See you next Sunday — kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani

A channel grows past the point humans can read everything. Someone bolts on an AI agent to classify spam. It works. Six months later, the community's moderation depends on one company's pricing, one company's terms of service, one company's idea of acceptable content.

Nobody planned that. It's just the default path in 2026: call a centralized AI API.

Wrote up why that's a contradiction worth fixing, and an architecture that fixes it.

Providers change their usage policies regularly. OpenAI, Anthropic, Google have all done it more than once in the past two years. Moderation is the awkward workload too: to classify spam you have to send spam through the API, and developers running abuse-processing bots have hit opaque account suspensions even after doing everything right.

The community chose a permissionless protocol specifically to avoid platform risk. Then reintroduced it one layer up, in the tooling. No headline censorship. The bot just quietly stops working.

One caveat before the fix, because protocol-literate people will raise it anyway: Farcaster channels are a client-level construct, not protocol-level. Moderation state lives in the client, not the network. So no, decentralizing the AI layer doesn't purify the whole stack.

That's not a hole in the argument, it's the argument. The channel-layer gap is native and openly debated. The AI dependency is different: it's being added right now, bot by bot, outside anyone's control, and nobody's watching it.

The fix, five parts, only one of them new:

1. Client integration watches the channel (unchanged)

2. Agent orchestrator owns the logic, does zero inference itself

3. Compute router sends jobs to decentralized GPU networks like Nosana, picking a market by price/queue/latency

4. Independent GPU operators run open-weights models, return a classification

5. Orchestrator acts: hide, flag, allow, or queue for human review Degraded mode always falls to human review, never silent auto-removal. The community's authority is the floor, not a feature bolted on top.

The part every decentralized AI pitch wants to skip: why trust a random GPU node's answer? Spot-checking helps against faults, not against someone running multiple correlated nodes. Majority voting costs N times more and assumes independence, the first thing a cheap attack breaks. Reputation and staking/slashing help more, but they're hard, especially for something as subjective as moderation.

Honest answer: good enough for spam today (low stakes, recoverable, human review catches the rest). Not solved for high-stakes calls. Narrower claim than "decentralized AI is trustless," and one I can defend.

Steelman the other side: centralized APIs are cheaper, faster, better documented, better at nuance. All true, and beside the point. This class of tool is bought for its guarantees, not its throughput. A community that picked a censorship-resistant protocol is making a statement about who can shut things down. Reintroducing a shutdown switch one layer up doesn't serve that just because it's cheaper this quarter.

The protocol layer is being decentralized in the open, gap by gap. The tooling layer is where the quiet re-centralization is happening, one API key at a time.

Full piece: https://hackernoon.com/your-communitys-moderation-bot-shouldnt-have-a-single-point-of-failure

Your Community's Moderation Bot Shouldn't Have a Single Point of Failure | HackerNoon

Farcaster mod bots quietly depend on one AI vendor's API key. Here's an architecture that removes the single kill switch, using decentralized GPU compute.

https://hackernoon.com

AI Tools & Agents

• Weco AI ran autoresearch on itself for 8 days and it discovered a better research harness than 2 years of hand-tuning — 16x smaller prompts, built-in reward-hacking defenses. Link

• The 5-layer Physical AI stack: Brain, Body, Parts, Fuel, Proving Grounds — a primer on where humanoid robotics infrastructure is headed. Link

• Compute Desk launched a marketplace for describing and trading GPU capacity without the spec sheet turning into a game of telephone. Link

• [schema]: an agent harness that saturates ARC-AGI-3 by building an editable symbolic world model instead of guessing blind. Link

• How to use Lovable for vibecoding, and when to grab the generated code and walk. Link

• Simon Willison on Kimi K3 (2.8T params) and what the pelican benchmark still reveals about frontier models. Link

• Why AI progress keeps compounding without new breakthroughs: harnesses turn weak models into strong systems — we're still in the "MS-DOS era" of AI operating systems. Link

• A model that reconstructs any scene in 3D from a single regular video in real-time — no LiDAR, 20fps on one GPU, stable past 10,000 frames. Link

Mindset & Ideas

• If your parents aren't deeply confused by what you do, you're playing it too safe — plus 35 other unsolicited diagnoses. Link

• Gabriel Amzallag: "I only build it if someone pays" — a builder's filter for what's worth shipping. Link

Privacy & Security

• Privacy Incidents — real-world examples of why your photos need protection. Link

Misc Worth Reading

• Telegram's new Chat Automation feature lets you wire a bot to answer your private-chat messages on your behalf.

• Lenis and Vanta.js — the two libraries behind most of the "banger scroll effect" websites you've seen lately. Link

From Hacker News

• LG monitors silently install software through Windows Update without consent — 715 pts. Link

• Regressive JPEGs — 561 pts. Link

• Why do AI company logos look like buttholes? (2025) — 379 pts. Link

• GPT-5.6 used a prompt to close a 30-year gap in convex optimization — 307 pts. Link

• What AI did to Stack Overflow, in a graph — 253 pts. Link

• EU ban on destruction of unsold clothes and shoes enters into application — 156 pts. Link

• Fable 5 vs. GPT-5.6 Sol on an NP-Hard Problem: does /goal help? — 147 pts. Link

• Show HN: IKEA Complexity Index — 122 pts. Link

• The Computer at the Bottom of a Canal — 105 pts. Link

• I started a "dirt notebook" — 96 pts. Link

That's a wrap. See you next Sunday — kazani

Daily reads on Telegram: Join here

Follow me on Farcaster: kazani