Feed aggregator

Article URL: https://github.com/andrew/gitlocal

Comments URL: https://news.ycombinator.com/item?id=47275057

Points: 2

# Comments: 0

Article URL: https://press.asimov.com/articles/dna-sequencing

Comments URL: https://news.ycombinator.com/item?id=47275049

Points: 3

# Comments: 0

Article URL: https://www.bbc.com/news/articles/cjd98091g28o

Comments URL: https://news.ycombinator.com/item?id=47275035

Points: 32

# Comments: 10

Article URL: https://blog.icme.io/ai-agents-can-move-money-lobstar-wilde-proved-they-can-lose-it-too/

Comments URL: https://news.ycombinator.com/item?id=47275030

Points: 2

# Comments: 1

I’ve been exploring the NPPES dataset, the federal registry that assigns NPI numbers to every healthcare provider in the U.S. It currently has about 9 million records and grows by ~30k per month, but accessing it usually means downloading multi-gigabyte CSVs or using the CMS lookup that returns one provider at a time.

I built NPIScan to make the dataset browsable. You can search by name, NPI, specialty, or location and drill down from state → city → ZIP code. Each provider has a profile with credentials, practice locations, taxonomy codes, and digital health endpoints.

A few interesting patterns from the data:

- 2025 had ~631k new NPI registrations, the largest jump on record

- Behavior Technicians grew to ~526k providers and are now among the largest specialties

- California alone has ~1.1M providers (~12% of the country)

- Only ~0.5% of providers have registered digital health endpoints

Tech stack: Next.js, PostgreSQL, Meilisearch, Redis. The main challenge was making 9M records feel fast to browse. I solved it with denormalized listing tables, Meilisearch full-text search, and Redis caching for aggregated queries. Most pages respond in <40ms after cache warmup.

Curious to hear feedback from anyone working with healthcare data.

Comments URL: https://news.ycombinator.com/item?id=47275022

Points: 1

# Comments: 0

While prevention is key, it's not enough to protect a company's systems from ransomware. Learn how early detection with these four methods helps reduce damage from attacks.

Nordic petrostate is preparing for war and turning the spotlight on vulnerabilities in its critical industries, as adversaries look for ways to damage the most important oil and gas producer to the EU

The nation-state-grade iOS exploit kit targets 23 vulnerabilities affecting iOS 13 to 17.2.1.

The post CISA Adds iOS Flaws From Coruna Exploit Kit to KEV List appeared first on SecurityWeek.

Article URL: https://www.bloomberg.com/news/articles/2026-02-25/hacker-used-anthropic-s-claude-to-steal-sensitive-mexican-data

Comments URL: https://news.ycombinator.com/item?id=47274548

Points: 1

# Comments: 0

Article URL: https://www.youtube.com/watch?v=FzwyGrNpOMU

Comments URL: https://news.ycombinator.com/item?id=47274514

Points: 1

# Comments: 1

Article URL: https://gestrada.dev/posts/bloom-filter/

Comments URL: https://news.ycombinator.com/item?id=47274506

Points: 1

# Comments: 0

Article URL: https://blogs.windows.com/msedgedev/2026/03/05/making-keyboard-navigation-effortless/

Comments URL: https://news.ycombinator.com/item?id=47274502

Points: 1

# Comments: 0

I build this tool for using port forwarding with mosh (if too lazy to open my vscode). Hope it is helpful and hear your help on further improving it.

Comments URL: https://news.ycombinator.com/item?id=47274498

Points: 1

# Comments: 0

Hey HN, I built geo-lint — an open-source linter for content (Markdown/MDX) that checks 92 deterministic rules across SEO, GEO (Generative Engine Optimization), content quality, and technical issues.

GEO is the idea that AI search engines (ChatGPT, Perplexity, Claude) cite content differently than Google ranks it. Things like question-formatted headings, FAQ sections, entity density, E-E-A-T signals, and citation-ready statistics all matter for whether an LLM will pull from your content. geo-lint has 35 rules specifically for this.

The interesting part is the lint loop. It ships as a Claude Code skill — you run /geo-lint audit and it spawns parallel subagents, one per file. Each agent reads the violations, edits the content, re-lints, and repeats until clean (max 5 passes). The linter is fully deterministic (no LLM in the rules themselves), so the agent gets unambiguous violation + suggestion pairs to act on. Zero hallucination risk in the analysis layer.

It also works without Claude Code — npx geo-lint --format=json gives you a flat JSON array any agent (Cursor, Copilot, Windsurf) can consume. The rules are the same either way.

MIT licensed, zero runtime deps beyond gray-matter. npm: @ijonis/geo-lint

GitHub: https://github.com/IJONIS/geo-lint

Comments URL: https://news.ycombinator.com/item?id=47274490

Points: 1

# Comments: 1

Article URL: https://createadaptablelife.com/2026/03/how-can-we-stop-waiting-to-do-what-we-say-matters-to-us.html

Comments URL: https://news.ycombinator.com/item?id=47274484

Points: 1

# Comments: 0

I’m trying to sanity check an idea with people who work with regulated systems.

In many organisations we have scanners for code, monitoring for systems, and multiple layers of controls and audit. But the business process itself is rarely checked for logical vulnerabilities before it goes live.

Processes like KYC onboarding, approvals, payments or compliance workflows are often designed in meetings and documented later. Over time more controls get added and monitoring improves, but the underlying process logic is rarely tested.

Which raises a simple question: can this process be bypassed?

I started experimenting with describing processes as state machines and running static checks on them. Things like reachability, missing review steps, irreversible actions without compensation, and similar structural issues.

The idea is to detect what you might call "business process vulnerabilities by design" before the process is deployed.

The page explains the concept and shows a small prototype. The prototype lets you describe a process as a state machine and run automated checks against rule sets (for example operational risk or resilience rules).

What I’m mainly trying to understand is whether this is actually a real problem in practice.

For people working in fintech, banking, risk or operations:

Do process bypasses or design gaps show up in real systems? How are new processes usually reviewed before they go live? Where do things tend to break down? Paper: veilgovernance.com/research/missing-first-line-of-defence

Comments URL: https://news.ycombinator.com/item?id=47274481

Points: 1

# Comments: 1

Article URL: https://www.pewresearch.org/religion/2026/03/05/in-25-country-survey-americans-especially-likely-to-view-fellow-citizens-as-morally-bad/

Comments URL: https://news.ycombinator.com/item?id=47274464

Points: 2

# Comments: 0

Article URL: https://apnews.com/article/daily-telegraph-axel-springer-paper-buy-german-1386ec56fef373bf5ab5b0f7226bf7bb

Comments URL: https://news.ycombinator.com/item?id=47274453

Points: 2

# Comments: 0

After getting up close to play with this new flavor of MacBook, it's clear Apple has something special here.