Hacker News

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

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

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

Article URL: https://github.com/ybgwon96/easyclaw

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

Points: 1

# Comments: 1

Hey HN,

Every frontend framework bakes environment variables into the JavaScript bundle at build time (process.env, import.meta.env). This means your Docker image is environment-specific — you build one for staging, another for prod, and the image you tested is never the one you deploy.

I built REP (Runtime Environment Protocol) to fix this. It's a lightweight Go gateway (~6MB binary, zero deps) that sits in front of your static file server and injects env vars into HTML responses at container startup.

What makes it different from the dozens of window.__ENV__ hacks:

- Three-tier security classification: REP_PUBLIC_* (plaintext), REP_SENSITIVE_* (AES-256-GCM encrypted, decrypted via short-lived session key), REP_SERVER_* (never reaches the browser)

- Automatic secret detection — scans PUBLIC vars for high-entropy strings, AWS keys, JWTs, etc. and refuses to start in strict mode

- HMAC integrity verification on every payload

- Optional hot config reload via SSE

- Works with any SPA (React, Vue, Svelte, Angular, vanilla) — no build tool plugins

- FROM scratch compatible — the binary is all you need

The SDK is ~1.5KB gzipped and gives you synchronous access (rep.get('API_URL')) for public vars and async decryption (await rep.getSecure('KEY')) for sensitive ones.

Full RFC-style spec, security threat model, and reference implementation: https://rep-protocol.dev

I'd especially love feedback on the security model — I've tried to be honest about what the SENSITIVE tier actually protects against vs what it doesn't. The threat model doc doesn't pretend browser-side encryption is bulletproof.

Built this because I got tired of watching every team I've worked with reinvent the same env.sh → window.__ENV__ hack with zero security thought behind it.

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

Points: 1

# Comments: 0

Article URL: https://huggingface.co/collections/Qwen/qwen35

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

Points: 1

# Comments: 0

Article URL: https://www.businessinsider.com/ai-layoffs-deflation-us-economy-job-market-outlook-citi-2026-2

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

Points: 3

# Comments: 0

Article URL: https://stratechery.com/2026/anthropic-and-alignment/

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

Points: 1

# Comments: 0

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

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

Points: 3

# Comments: 0

Article URL: https://news.mongabay.com/2026/02/tipping-points-and-ecosystem-collapse-are-the-real-geopolitical-risk-commentary/

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

Points: 1

# Comments: 0

Article URL: https://memgraph.com/blog/memgraph-production-telemetry-stack-aws-clickhouse-grafana

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

Points: 2

# Comments: 0