How would this work? One would connect it's repository to a cloud platform that would then act based on the existing daemons of the repo?

That's exactly right. Our cloud-based agent Charlie (https://charlielabs.ai/) supports this, and our hope is that other platform providers will offer support in the future as well.

Skills live in the repository, so it felt like a natural complement. It also lets other developers see what the active daemons are and collaborate on them. With proper context, agents are quite good at writing and editing these daemon files too.

DAEMONS.md is meant to be an open spec, like skills.

there's details on how other platforms can support it here: https://ai-daemons.com/spec/#provider-guide

Just shipped numa v0.13.0: added request hedging (fires a parallel query after 10ms if the primary stalls, inspired by Google's Tail at Scale paper) wire-level cache with serve-stale (RFC 8767) and a DoT client for encrypted upstream.

Wrote about the tail latency investigation: https://numa.rs/blog/posts/fixing-doh-tail-latency.html

should be fixed by #54 in 0.10.3 thanks again!

Thanks for pointing this out! I’ve created https://github.com/razvandimescu/numa/issues/36

let me know how it goes

This was started as a learning project, went from the start to the lowest level then I've just added features I wanted one by one, it just made the most sense

let me know if you do it!

Numa can do recursive resolution from root nameservers + DNSSEC, .numa local domains with auto HTTPS for dev, and LAN service discovery. What features would you be interested in?

What about split horizon dns so I can locally resolve home servers instead of going to tailscale

Split DNS already works — Numa auto-detects Tailscale forwarding rules from the system config. Queries matching .<ts.net> go to Tailscale’s DNS, everything else goes through Numa

If you want to skip Tailscale entirely for home servers, Numa’s LAN discovery auto-finds machines running Numa on the same network. Or add static records in numa.toml for machines that don’t run it.

Just normal ad filtering.

It definitely is and you can see it in the git commits. The DNS wire protocol parser was the original learning project I wrote to understand the spec. Later features (recursive resolver, DNSSEC validation, the dashboard) were built with the help of AI

That's fair, thanks for letting me know!

also in romanian nume = name(dns) and I also get the easter egg of that well known Romanian song numa numa :) https://www.youtube.com/watch?v=YnopHCL1Jk8

On OpenWRT — it's musl-based Linux so the binary should run the arm one would need a crosscompile Free BSD can be done (pr's welcome?)

When you've capitalized the N in "Numa", it's a lot more obvious to my brain you don't mean the acronym. But this is nitpicky bikeshedding and maybe I'm weird :)