frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: AI agent forgets user preferences every session. This fixes it

https://www.pref0.com/
1•fliellerjulian•59s ago•0 comments

Introduce the Vouch/Denouncement Contribution Model

https://github.com/ghostty-org/ghostty/pull/10559
1•DustinEchoes•2m ago•0 comments

Show HN: SSHcode – Always-On Claude Code/OpenCode over Tailscale and Hetzner

https://github.com/sultanvaliyev/sshcode
1•sultanvaliyev•3m ago•0 comments

Microsoft appointed a quality czar. He has no direct reports and no budget

https://jpcaparas.medium.com/microsoft-appointed-a-quality-czar-he-has-no-direct-reports-and-no-b...
1•RickJWagner•4m ago•0 comments

Multi-agent coordination on Claude Code: 8 production pain points and patterns

https://gist.github.com/sigalovskinick/6cc1cef061f76b7edd198e0ebc863397
1•nikolasi•5m ago•0 comments

Washington Post CEO Will Lewis Steps Down After Stormy Tenure

https://www.nytimes.com/2026/02/07/technology/washington-post-will-lewis.html
1•jbegley•6m ago•0 comments

DevXT – Building the Future with AI That Acts

https://devxt.com
2•superpecmuscles•6m ago•4 comments

A Minimal OpenClaw Built with the OpenCode SDK

https://github.com/CefBoud/MonClaw
1•cefboud•7m ago•0 comments

The silent death of Good Code

https://amit.prasad.me/blog/rip-good-code
2•amitprasad•7m ago•0 comments

The Internal Negotiation You Have When Your Heart Rate Gets Uncomfortable

https://www.vo2maxpro.com/blog/internal-negotiation-heart-rate
1•GoodluckH•8m ago•0 comments

Show HN: Glance – Fast CSV inspection for the terminal (SIMD-accelerated)

https://github.com/AveryClapp/glance
2•AveryClapp•9m ago•0 comments

Busy for the Next Fifty to Sixty Bud

https://pestlemortar.substack.com/p/busy-for-the-next-fifty-to-sixty-had-all-my-money-in-bitcoin-...
1•mithradiumn•10m ago•0 comments

Imperative

https://pestlemortar.substack.com/p/imperative
1•mithradiumn•11m ago•0 comments

Show HN: I decomposed 87 tasks to find where AI agents structurally collapse

https://github.com/XxCotHGxX/Instruction_Entropy
1•XxCotHGxX•15m ago•1 comments

I went back to Linux and it was a mistake

https://www.theverge.com/report/875077/linux-was-a-mistake
3•timpera•16m ago•1 comments

Octrafic – open-source AI-assisted API testing from the CLI

https://github.com/Octrafic/octrafic-cli
1•mbadyl•17m ago•1 comments

US Accuses China of Secret Nuclear Testing

https://www.reuters.com/world/china/trump-has-been-clear-wanting-new-nuclear-arms-control-treaty-...
2•jandrewrogers•18m ago•1 comments

Peacock. A New Programming Language

1•hashhooshy•23m ago•1 comments

A postcard arrived: 'If you're reading this I'm dead, and I really liked you'

https://www.washingtonpost.com/lifestyle/2026/02/07/postcard-death-teacher-glickman/
2•bookofjoe•24m ago•1 comments

What to know about the software selloff

https://www.morningstar.com/markets/what-know-about-software-stock-selloff
2•RickJWagner•28m ago•0 comments

Show HN: Syntux – generative UI for websites, not agents

https://www.getsyntux.com/
3•Goose78•29m ago•0 comments

Microsoft appointed a quality czar. He has no direct reports and no budget

https://jpcaparas.medium.com/ab75cef97954
2•birdculture•29m ago•0 comments

AI overlay that reads anything on your screen (invisible to screen capture)

https://lowlighter.app/
1•andylytic•30m ago•1 comments

Show HN: Seafloor, be up and running with OpenClaw in 20 seconds

https://seafloor.bot/
1•k0mplex•30m ago•0 comments

Tesla turbine-inspired structure generates electricity using compressed air

https://techxplore.com/news/2026-01-tesla-turbine-generates-electricity-compressed.html
2•PaulHoule•32m ago•0 comments

State Department deleting 17 years of tweets (2009-2025); preservation needed

https://www.npr.org/2026/02/07/nx-s1-5704785/state-department-trump-posts-x
3•sleazylice•32m ago•1 comments

Learning to code, or building side projects with AI help, this one's for you

https://codeslick.dev/learn
1•vitorlourenco•33m ago•0 comments

Effulgence RPG Engine [video]

https://www.youtube.com/watch?v=xFQOUe9S7dU
1•msuniverse2026•34m ago•0 comments

Five disciplines discovered the same math independently – none of them knew

https://freethemath.org
4•energyscholar•35m ago•1 comments

We Scanned an AI Assistant for Security Issues: 12,465 Vulnerabilities

https://codeslick.dev/blog/openclaw-security-audit
1•vitorlourenco•35m ago•0 comments
Open in hackernews

Show HN: DNS Benchmark Tool – Compare and monitor resolvers

https://github.com/frankovo/dns-benchmark-tool
59•ovo101•2mo ago
I built a CLI to benchmark DNS resolvers after discovering DNS was adding 300ms to my API requests.

v0.3.0 just released with new features: compare: Test single domain across all resolvers top: Rank resolvers by latency/reliability/balanced monitor: Continuous tracking with threshold alerts

1,400+ downloads in first week.

Quick start: pip install dns-benchmark-tool dns-benchmark compare --domain google.com

CLI stays free forever. Hosted version (multi-region, historical tracking, alerts) coming Q1 2026.

GitHub: https://github.com/frankovo/dns-benchmark-tool Feedback: https://forms.gle/BJBiyBFvRJHskyR57

Built with Python + dnspython. Open to questions and feedback!

Comments

johng•2mo ago
Very neat tool!
ovo101•2mo ago
Thanks! Glad you find it neat. The goal was to make DNS benchmarking simple to run from the CLI, with quick checks, deeper benchmarks, and monitoring all in one place. Feedback is always welcome.
jeffbee•2mo ago
You are, presumably, already familiar with the ISC Looking Glass?

https://isc.sans.edu/api/dnslookup/google.com

ovo101•2mo ago
Yes, the ISC Looking Glass is a great resource — it’s handy for quick DNS lookups and seeing how queries resolve from their vantage point. This project is aimed more at benchmarking and monitoring resolvers over time, so they complement each other: Looking Glass for snapshots, dns‑benchmark‑tool for comparative speed and ongoing health checks.
jeffbee•2mo ago
This GPTSlop isn't endearing me to your future service offering.
nijave•2mo ago
Strong vibe coding feel coming from the project but code seemed decent based on cursory look
ovo101•2mo ago
Appreciate you taking a look — glad the code came across well. Always open to suggestions if you spot areas to improve.
ovo101•2mo ago
Fair enough — the project’s about the CLI open‑source tool, reproducible and ready to run locally.
WarOnPrivacy•2mo ago
The Spinrite guy was the first to do this (I think). https://www.grc.com/dns/benchmark.htm

That said, more options are good. I'll give this one a go.

whalesalad•2mo ago
Works on Linux with Wine too =)
ovo101•2mo ago
Nice! Good to know it runs under Wine on Linux as well. That makes it easier for folks who want to try it outside native Python environments.
ovo101•2mo ago
Thanks for pointing to Gibson’s DNS Benchmark — it’s definitely a classic and set the stage for this kind of testing. This project takes a different angle: it’s CLI‑first, scriptable, and designed for both quick “top” checks and deeper “benchmark” runs, plus a monitoring mode for ongoing resolver health. Glad you’re giving it a try, feedback is welcome.
1970-01-01•2mo ago
Here's my take. Ads will happily eat 300ms per webpage if you allow them to load. A fast DNS is great, but an adblocking DNS will save you much more time if you're just browsing.
jeffbee•2mo ago
I doubt that your conclusion is correct (because local DNS resolvers that consult blocklists are often surprisingly slow) but I think your theory of the matter is accurate. The raw speed of the DNS server is almost irrelevant because there are other much larger systemic performance issues at stake. For example Cloudflare does not forward EDNS to the origin, so the records it returns are suboptimal for services that use DNS-based service affinity. It doesn't make a difference to me if Cloudflare is a few microseconds faster — and by the way I sincerely doubt that this python program is observing meaningful microsecond-scale differences — because overall it makes applications slower.
ovo101•2mo ago
Fair points — blocklist‑based local resolvers can indeed be slower, and raw speed alone doesn’t capture the bigger systemic issues. The tool isn’t trying to measure microsecond‑scale differences, but rather provide a clear comparison of resolver behavior under load and over time. Things like EDNS handling and service affinity are exactly the kind of deeper characteristics that benchmarking can help surface, so users can decide which trade‑offs matter most for their environment.
m3047•2mo ago
DNS is utilized for many things besides looking up web sites (and consequently ads on web sites). DNS was used for many things etcd was invented to solve, and still is by many. Adblocking is kidstuff; the bearded, motorcycle riding, gun-shooting, jumping out of airplanes and hanging off of rocks jackals use a "DNS firewall" (just posted this the other day): https://www.dnsrpz.info/ and Dnstap for application-level DNS logging.
ovo101•2mo ago
Absolutely — DNS goes way beyond just resolving websites. It’s been used for service discovery and coordination long before tools like etcd came along, and still is in many systems today. Adblocking is one use case, but DNS firewalls (like RPZ) and logging frameworks such as Dnstap show how powerful DNS can be at the infrastructure level. Thanks for sharing the link — it’s a great reminder that benchmarking speed is only one piece of the bigger DNS picture.
zamadatix•2mo ago
Fast DNS and adblocking DNS (or other methods, for that matter) are not mutually exclusive topics, even assuming your primary use case for DNS resolution on a given machine is web browsing.
ovo101•2mo ago
Absolutely — fast DNS and adblocking DNS aren’t mutually exclusive. The tool here is focused on resolver speed and monitoring, but it can benchmark adblocking resolvers just as well. That way you can pick the one that balances performance with blocking, depending on your browsing needs.
ovo101•2mo ago
That’s a good point — adblocking DNS can definitely save time by cutting requests before they even reach the browser. The focus here was on resolver speed and monitoring, but pairing it with an adblocking DNS is a smart way to get both performance and less clutter while browsing.
mrngm•2mo ago
https://github.com/farrokhi/dnsdiag is another great toolbox for looking into DNS problems.
ovo101•2mo ago
Yes, dnsdiag is a solid toolbox — it’s great for digging into DNS issues at the packet level. This project is aimed more at benchmarking and monitoring resolvers over time, so they complement each other well: dnsdiag for diagnostics and troubleshooting, dns‑benchmark‑tool for comparative speed and health checks.
m3047•2mo ago
Things built with asyncio and dnspython are close to my heart. ;-)

So, my impression from the doc (and a quick browse of the code) is that this is a tool for monitoring DNS caching / recursing resolver (RD) performance, not authoritative. If performance really matters to you, you should be running your own resolver(s). [0] Granted, you will quickly realize that some outfits running auth servers seem to understand that they're dependent on caching / recursing resolvers, and some are oblivious. Large public servers (recursing and auth) tend to "spread the pain" and so most people don't feel the bumps; but when they fall over they fall over large, and they bring some principles (and thereby create "vulnerabilities") at odds with what the DNS was architected for and throw the mitigation on the other operators, including operators who never accepted these self-anointed principles to begin with.

I have a hard time understanding how DNS is adding 300ms to every one of your API requests... unless DNS is both the API and transport, or you're using negative TTLs /s.

Good doc, by the way.

[0] Actual resolvers. Not forwarders.

ovo101•2mo ago
Thanks for the thoughtful read — and yes, the tool is focused on caching / recursing resolver performance, not authoritative. The asyncio + dnspython stack makes it easy to script and monitor those behaviors over time. Running your own resolver is definitely the gold standard if performance and control really matter, but benchmarking public ones helps surface the trade‑offs users face in practice. The 300ms example was more about illustrating how ads and systemic factors can dwarf raw resolver speed, not a claim about per‑request DNS overhead. Appreciate the detailed perspective and glad the doc came across clearly.
PcChip•2mo ago
is this similar to the GRC tool?
ovo101•2mo ago
Yes, it’s in the same space as Gibson’s GRC DNS Benchmark — that tool has been around for years and set the standard for GUI‑based testing. This project takes a different angle: it’s CLI‑first, scriptable, and adds modes for quick checks, deeper benchmarks, and ongoing monitoring. So it’s more aimed at automation and sysadmin workflows than interactive GUI use.
iruoy•2mo ago
If you want to run python tools without installing them:

    uvx --from dns-benchmark-tool dns-benchmark top
ovo101•2mo ago
If you want to run Python tools without installing them, you can use uvx: uvx --from dns-benchmark-tool dns-benchmark top

This pulls the package from PyPI and runs the top command right away.

BOOSTERHIDROGEN•2mo ago
Need a docker image if you would, thanks.
ovo101•2mo ago
I’ll also publish a Docker image soon to make setup even easier.