pul

It would replace the Cloudflare to server network hop with a cloudflare PoP to R2 hop. That covers approximately the same geographical distance and results in similar latency.

(I'm the author btw)

Cloudflare R2 doesn't distribute files globally. They only cache requested files in PoPs. So then it would function the same as an API behind the Cloudflare CDN.

You're not the first to mention this, so clearly users expect something different from what I've designed it for. I think I'll drop the TLD postfix suggestions.

Interesting, I didn't think of that yet.

I think most people search for domains they own, which doesn't correlate with Tranco popularity ranking. Treating 'popularity' not as a function of visitors, but as a function of number of known domain names with that prefix could work, though.

Author here.

Yes, it will autocomplete the most popular domains first, then known registered domains, and then fall back to appending popular TLDs.

The reason is that it's impossible to enumerate all domains. gTLDs (like .com, .info) mostly publish their zone files, but ccTLDs (like .cn, .de) usually don't.

But maybe you're right. After reading these comments, it's clearly confusing to people.

Hi HN!

Ruurtjan here, founder of Wirewiki.com. I recently tried to get autocomplete as fast as I could. I'll be checking in here the rest of the day to answer any questions.

Also happy to hear any suggestions for Wirewiki.

I don't think I'll make a CLI for this any time soon.

The main thing I bring to the table with Wirewiki is UX, and I don't feel like I could do that well in a CLI.

It’s a wiki (loosely defined as an authoritative browsable graph / index) of everything that goes over the wire.

You're right that it doesn't do the name Wirewiki justice yet. I've got so many things planned to add at some point, much more than just DNS. Check again in 2 years' time ;)

> The list of servers you're going to get with a naive scanning approach is not what you want.

Absolutely right. I'm doing uptime monitoring and a handful of checks (udp/tcp, nxdomain, dnssec, dns filtering) before listing them, but I feel like it could definitely be improved. Would love to talk! I'll send you an email.

You're the second person in these comments who points out faux name server redundancy. Interesting. I hadn't considered it as a major theme, but I'll move it up the list a little.

> Authoritative drift.

This is why I query all authoritative name servers (as well as delegating name servers when querying NS records) in the DNS propagation tool. I haven't seen any other site do this. This feels like such an obvious thing to me, but somehow I'm the only one.