The EU still wants to scan  your private messages and photos

Thoughts on slowing the fuck down

Running Tesla Model 3's computer on my desk using parts from crashed cars

Apple randomly closes bug reports unless you "verify" the bug remains unfixed

<a href="https:&#x2F;&#x2F;arcprize.org&#x2F;media&#x2F;ARC_AGI_3_Technical_Report.pdf">https:&#x2F;&#x2F;arcprize.org&#x2F;media&#x2F;ARC_AGI_3_Technical_Report.pdf</a>

ARC-AGI-3

<a href="https:&#x2F;&#x2F;archive.is&#x2F;mEgaK" rel="nofollow">https:&#x2F;&#x2F;archive.is&#x2F;mEgaK</a><a href="https:&#x2F;&#x2F;www.supremecourt.gov&#x2F;opinions&#x2F;25pdf&#x2F;24-171_bq7d.pdf" rel="nofollow">https:&#x2F;&#x2F;www.supremecourt.gov&#x2F;opinions&#x2F;25pdf&#x2F;24-171_bq7d.pdf</a><a href="https:&#x2F;&#x2F;supreme.justia.com&#x2F;cases&#x2F;federal&#x2F;us&#x2F;607&#x2F;24-171&#x2F;" rel="nofollow">https:&#x2F;&#x2F;supreme.justia.com&#x2F;cases&#x2F;federal&#x2F;us&#x2F;607&#x2F;24-171&#x2F;</a>

Supreme Court Sides with Cox in Copyright Fight over Pirated Music

90% of Claude-linked output going to GitHub repos w <2 stars

False claims in a widely-cited paper

Quantization from the Ground Up

<a href="https:&#x2F;&#x2F;www.science.org&#x2F;doi&#x2F;10.1126&#x2F;science.aec0970" rel="nofollow">https:&#x2F;&#x2F;www.science.org&#x2F;doi&#x2F;10.1126&#x2F;science.aec0970</a>

Earthquake scientists reveal how overplowing weakens soil at experimental farm

Personal Encyclopedias

My DIY FPGA board can run Quake II

The truth that haunts the Ramones: 'They sold more T-shirts than records'

Show HN: A plain-text cognitive architecture for Claude Code

Shell Tricks That Make Life Easier (and Save Your Sanity)

Two studies in compiler optimisations

I think like many of you, I&#x27;ve been jumping between many claude code&#x2F;codex sessions at a time, managing multiple lines of work and worktrees in multiple repos. I wanted a way to easily manage multiple lines of work and reduce the amount of input I need to give, allowing the agents to remove me as a bottleneck from as much of the process as I can. So I built an orchestration tool for AI coding agents:Optio is an open-source orchestration system that turns tickets into merged pull requests using AI coding agents. You point it at your repos, and it handles the full lifecycle:- Intake — pull tasks from GitHub Issues, Linear, or create them manually- Execution — spin up isolated K8s pods per repo, run Claude Code or Codex in git worktrees- PR monitoring — watch CI checks, review status, and merge readiness every 30s- Self-healing — auto-resume the agent on CI failures, merge conflicts, or reviewer change requests- Completion — squash-merge the PR and close the linked issueThe key idea is the feedback loop. Optio doesn&#x27;t just run an agent and walk away — when CI breaks, it feeds the failure back to the agent. When a reviewer requests changes, the comments become the agent&#x27;s next prompt. It keeps going until the PR merges or you tell it to stop.Built with Fastify, Next.js, BullMQ, and Drizzle on Postgres. Ships with a Helm chart for production deployment.

Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR

Government agencies buy commercial data about Americans in bulk

More precise elevation data for GraphHopper routing engine

We&#x27;ve been building data pipelines that scrape websites and extract structured data for a while now. If you&#x27;ve done this, you know the drill: you write CSS selectors, the site changes its layout, everything breaks at 2am, and you spend your morning rewriting parsers.LLMs seemed like the obvious fix — just throw the HTML at GPT and ask for JSON. Except in practice, it&#x27;s more painful than that:- Raw HTML is full of nav bars, footers, and tracking junk that eats your token budget. A typical product page is 80% noise.
- LLMs return malformed JSON more often than you&#x27;d expect, especially with nested arrays and complex schemas. One bad bracket and your pipeline crashes.
- Relative URLs, markdown-escaped links, tracking parameters — the &quot;small&quot; URL issues compound fast when you&#x27;re processing thousands of pages.
- You end up writing the same boilerplate: HTML cleanup → markdown conversion → LLM call → JSON parsing → error recovery → schema validation. Over and over.We got tired of rebuilding this stack for every project, so we extracted it into a library.Lightfeed Extractor is a TypeScript library that handles the full pipeline from raw HTML to validated, structured data:- Converts HTML to LLM-ready markdown with main content extraction (strips nav, headers, footers), optional image inclusion, and URL cleaning
- Works with any LangChain-compatible LLM (OpenAI, Gemini, Claude, Ollama, etc.)
- Uses Zod schemas for type-safe extraction with real validation
- Recovers partial data from malformed LLM output instead of failing entirely — if 19 out of 20 products parsed correctly, you get those 19
- Built-in browser automation via Playwright (local, serverless, or remote) with anti-bot patches
- Pairs with our browser agent (@lightfeed&#x2F;browser-agent) for AI-driven page navigation before extractionWe use this ourselves in production at Lightfeed, and it&#x27;s been solid enough that we decided to open-source it.GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;lightfeed&#x2F;extractor" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;lightfeed&#x2F;extractor</a> npm: npm install @lightfeed&#x2F;extractor Apache 2.0 licensed.Happy to answer questions or hear feedback.

Show HN: Robust LLM Extractor for Websites in TypeScript