Feed aggregator

Show HN: Generate baseline Kubernetes NetworkPolicies from rendered manifests

Hacker News - Wed, 02/18/2026 - 5:58pm

A lot of clusters still run “allow-all” east/west because NetworkPolicies aren’t enforced everywhere. I built a small static analyzer that reads rendered manifests (Helm/Argo CD/Kustomize output) and emits baseline NetworkPolicy YAML you can commit + diff in PRs.

Workflow:

PR changes manifests

CI regenerates policies

reviewers see “newly allowed” connections as a normal permission diff

Curious how others handle this: would you rather review generated policy diffs, or a connectivity-graph diff? Any edge cases you’ve seen bite in real clusters (headless services, shared namespaces, DNS/egress, service meshes, etc.)?

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

Points: 1

# Comments: 0

Categories: Hacker News

Uber Has Big Plans for Lots More Robotaxis and EV Charging Stations

CNET Feed - Wed, 02/18/2026 - 5:57pm
The ride-hailing company expects to put more robotaxis in more cities this year.
Categories: CNET

Ask HN: In Cursor/agents, do plugins hide MCP tools from the main agent?

Hacker News - Wed, 02/18/2026 - 5:55pm

Quick architecture question.

When using MCP servers directly in Cursor, the agent seems to see all tools at the same level.

But when using a plugin/extension that internally connects to MCP servers, does the main agent:

see only the plugin as a single tool and delegate to a sub-agent inside it, or

still see every underlying MCP tool individually?

In other words: do plugins act as a tool abstraction boundary, or just a packaging/install mechanism?

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

Points: 1

# Comments: 0

Categories: Hacker News

Show HN: Designing package namespacing for a new language (Coi)

Hacker News - Wed, 02/18/2026 - 5:54pm

Hey HN, I'm building Coi, a component-based language that compiles to WASM, JS, CSS and HTML with O(1) reactivity (no virtual DOM).

I just shipped a built-in package manager, but the interesting part wasn't the implementation, it was all the ecosystem design questions I'd never thought about as a user of package managers.

The problem I kept circling: how do you handle naming? Global names like auth or json seem fine until someone squats them. First-come-first-served creates perverse incentives. Reputation systems are easy to game early on. I went back and forth for longer than I'd like to admit.

I went through a few approaches:

Blocklist common names: reserve things like auth, json, http so people are forced into more specific names. Feels clean in theory, but who decides the list? And it doesn't really scale, someone will always find the next generic name you didn't think to block.

Go's approach: just use GitHub URLs directly as the package identifier. No registry needed, no naming wars. I liked the elegance of it, but in practice it's awful to actually write and read. Nobody wants import github.com/someone/thing/v2/pkg/util in their source files.

Tiered names: short names are hard to get, long names are open. Claiming json requires vetting, but json-schema-validator you can grab freely. The friction is proportional to how valuable the name is, nobody squats my-very-specific-http-retry-client because there's no payoff. I liked this one, but you still need to define the threshold and then you're back to needing governance :( just a smaller version of it.

Scoped names: ended up here. Everything is @someorg/http-client. Boring, proven, sidesteps squatting without needing governance infrastructure I don't have. npm figured this out the hard way so I don't have to :)

The registry itself is GitHub-based, metadata is JSON, submissions are PRs, validation runs through CI. Only one package in the registry right now (mine), but getting add/install/upgrade working end-to-end changed how the project feels. It went from "compiler experiment" to something with an actual ecosystem shape.

Curious how others have thought about this, especially early-stage ecosystems where you have no reputation signals yet. Did anyone solve the naming problem better than "just use scopes"?

Coi: https://github.com/io-eric/coi

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

Points: 1

# Comments: 0

Categories: Hacker News

Show HN: HiddenState – How I keep up with 500+ ML papers a day

Hacker News - Wed, 02/18/2026 - 5:49pm

HiddenState monitors arxiv, Reddit, GitHub, HN, Bluesky, HuggingFace, OpenReview, PapersWithCode, and a handful of research blogs. Every few hours it pulls new items, throws most of them away (+95%), and clusters what survives by the specific technical constraint being attacked. Not by topic, not by domain.

Example from this week; 7 independent VLA papers dropped within 24 hours from 9 different orgs. Xiaomi, GigaBrain, RISE, all attacking sim-to-real transfer for robotic manipulation. None coordinating. That kind of convergence is hard to spot unless you're reading everything.

Each mechanism gets a 0-100 score across convergence, implementation evidence, engagement, and significance. Orgs are deduplicated so a single lab posting on five platforms doesn't inflate the signal.

Python, SQLite, Claude for clustering, Cloudflare Pages. Free, no tracking. Looking for any and all feedback and thoughts! Cheers!

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

Points: 1

# Comments: 1

Categories: Hacker News

All Look Same?

Hacker News - Wed, 02/18/2026 - 5:48pm

Article URL: https://alllooksame.com/

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

Points: 3

# Comments: 0

Categories: Hacker News

Owning Your Data

Hacker News - Wed, 02/18/2026 - 5:41pm
Categories: Hacker News

Astrolabe

Hacker News - Wed, 02/18/2026 - 5:40pm
Categories: Hacker News

Audible's New Feature Lets You Read and Listen to Your Favorite Books at the Same Time

CNET Feed - Wed, 02/18/2026 - 5:11pm
This feature aims to improve the reading experience for Audible subscribers.
Categories: CNET

Pages