Feed aggregator

Article URL: https://github.com/jsmenzies/clidocs

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

Points: 1

# Comments: 0

Article URL: https://projects.blender.org/blender/blender/issues/142346

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

Points: 1

# Comments: 0

AI coding agents ship code quickly.

But in real-world projects, some basic questions remain:

* What plan did this change follow? * Was the intent reviewed before execution? * What evidence do we have beyond “it works”? * When something fails, does the lesson get captured structurally?

AgentTeams adds a lightweight governance layer on top of AI-driven development.

Instead of just marking tasks as “Done”, it creates a traceable execution chain:

1. Plan Every task starts as an explicit plan. Priority, risk notes, and review status are recorded before execution.

2. Completion Report When work finishes, a report is generated automatically. It includes:

* Number of files changed * Execution time * A quality score (e.g., 82 / 95) * Verification summary

3. Post-mortem If something goes wrong, root cause and preventive actions are recorded and linked back to the original plan and conventions.

On the dashboard, you can see in real time:

* How many plans are in progress * How many are waiting for review * How many were completed in the last 7 days * How many reports failed or were partially completed * How many post-mortems are still open

The goal isn’t automation. It’s accountability and traceability for AI work.

AgentTeams is currently in beta. If you’re running AI-assisted development workflows, I’d love critical feedback from real usage.

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

Points: 1

# Comments: 0

Article URL: https://www.offensai.com/blog/eventual-consistency-resistant-iam-containment-aws-incident-response

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

Points: 1

# Comments: 0

I’ve spent the past 4 years building software for a knitting factory, including selecting and implementing an ERP. That experience was really painful.

Most manufacturing ERPs are hard to evaluate before signing an enterprise contract, poorly documented, and clearly not designed with serious API users in mind. Even when APIs exist, they’re often inconsistent or bolted on as an afterthought.

We built Augno to change that. The goal is to provide a Stripe-like experience for manufacturing ERP. We want it to be a usable out-of-the-box product and a well-designed, cohesive API that developers can actually build on.

We put a lot of effort into API design, documentation, and sandboxing. You can create a free account, explore the sandbox, and only move to production when you’re ready. There’s a free tier to make evaluation straightforward, without sales calls or contracts. Our focus is to let teams spend their engineering time on things that drive revenue - like custom quoting, order workflows, or integrations - instead of fighting their ERP.

We’re actively expanding the public API and rolling out additional endpoints over the next few months.

I made an account that you can check out. You can login at https://www.augno.com/auth/login username: hackernews password: aveGLZ9Nn4MA7cg!

Docs are here: https://docs.augno.com/

I’d really appreciate feedback from anyone who’s dealt with manufacturing systems or ERPs before!

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

Points: 1

# Comments: 0

Article URL: https://lwn.net/Articles/1057561/

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

Points: 1

# Comments: 0

Article URL: https://voidzero.dev/posts/whats-new-feb-2026

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

Points: 2

# Comments: 0

Article URL: https://arxiv.org/abs/2602.10154

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

Points: 1

# Comments: 0

I discovered RDAP while working on a hobby project where I needed to check if IP addresses were residential or not. RDAP was giving me more data than WHOIS, and it returns JSON instead of plain text. WHOIS is going away anyway. ICANN now requires RDAP for all gTLDs, and many registries are returning less data over port 43 or dropping it entirely. But RDAP is not easy to work with directly.

There is no single server. You have to check the IANA bootstrap registry to find which server handles each TLD, and some ccTLDs have working RDAP servers that are not even listed there. For .com and .net, the registry only has basic data. You need a second request to the registrar server to get contacts and abuse info. Then there is vcardArray, a deeply nested array-of-arrays format for contact data. And every server has its own rate limits.

I built an API that does all of that and gives you clean JSON back. One endpoint, same schema for every TLD. Here is what you get for google.com with ?follow=true (follows the registrar link automatically):

{ "domain": "google.com", "registrar": { "name": "MarkMonitor Inc.", "iana_id": "292" }, "dates": { "registered": "1997-09-15T04:00:00Z", "expires": "2028-09-14T04:00:00Z" }, "nameservers": ["ns1.google.com", "ns2.google.com", "ns3.google.com", "ns4.google.com"], "entities": { "registrant": { "organization": "Google LLC", "country_code": "US" } } } You also get status codes, DNSSEC, abuse contacts, etc. There is a free lookup tool on the homepage to try it, no signup needed.

Supplemental servers. The IANA bootstrap only covers ~1,200 TLDs. I keep a list of 30 extra RDAP servers (for TLDs like .io, .de, .me, .us) that work but are not registered with IANA. Synced daily.

Registrar follow-through. For thin registries like .com, the registry only has dates and nameservers. The registrar has the rest on a different server. The API follows that link and merges both.

SDKs. Open source clients for Python, Node.js, PHP, Go and Java.

Responses are cached for 24 hours to reduce load on upstream RDAP servers.

This is my first SaaS, just launched. Would love honest feedback.

The API starts at $9/mo with a 7-day free trial.

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

Points: 1

# Comments: 0

Article URL: https://productics.substack.com/p/subscriptions-will-survive-in-exactly

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

Points: 2

# Comments: 1

This Switch 2 exclusive might be its biggest killer app yet. I'm lost and in love with the cozy apocalypse.

Article URL: https://github.com/ufira-ai/Vibma

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

Points: 1

# Comments: 0

Article URL: https://stackoverflow.blog/2026/02/25/your-sneak-peek-at-the-redesigned-stack-overflow/

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

Points: 1

# Comments: 0

Article URL: https://dfarq.homeip.net/amd-am386-released-march-2-1991/

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

Points: 1

# Comments: 0

Most small design tools focus on components, templates, or AI generation. But when traffic grows, structure becomes the real bottleneck. I built a visual sitemap tool EPIC(https://no-edit.lovable.app) that maps your entire website into a clean navigational tree — so you can instantly see: Broken hierarchy Orphan pages Overloaded navigation Conversion dead-ends It started as an internal tool while improving my own SaaS retention. I kept missing structural issues because I was too close to the product. Seeing everything visually changed how I think about UX. Curious how others here approach: Large-scale navigation planning Structural SEO decisions Sitemap auditing Would love honest feedback.

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

Points: 2

# Comments: 1

Article URL: https://labex.io/playgrounds

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

Points: 1

# Comments: 0

Madhu Gottumukkala has been assigned to a new role within the Department of Homeland Security.

The post Nick Andersen Appointed Acting Director of CISA appeared first on SecurityWeek.

Article URL: https://kk.org/thetechnium/three-modes-of-cognition/

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

Points: 1

# Comments: 0

Article URL: https://honnibal.dev/blog/clownpocalypse

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

Points: 1

# Comments: 0