poitrus

This is a weak argument as pi-hole needs to go to a resolver or perform recursion itself which will give you the same latency or worse. The 1ms latency will only apply to already cached entries that are also cached by you OS anyways, whichever solution you are using.

If you configure NextDNS on a router, your router will perform the exact same caching pi-hole is doing, so it will make no difference performance-wise.

NextDNS will soon have a solution to auto-follow tracking links and allow some blocked domains temporarily from the blockpage. Just make sure you install the root CA on all devices.

Where do you think pi-hole sends your DNS queries?

There is absolutely no affiliation between Netflix and NextDNS.

Your cache would work the same with NextDNS. I'm not sure to see your point.

It's convenient to have stdout only returning the body so you can work with it without having to remove the header. With curl, if you pass the -v, you get headers on stderr too.

When headers are specifically requests with -i for instance, I agree curlie should print them on stdout. PR accepted ;)

I get that sometimes too. It should be fixable without having to send headers to stdout.

Author here: the main driver for writing curlie was not about the slowness of httpie but about all the features I was missing from curl. As curlie is just a wrapper on top of curl, you get all the great options of curl like http/2, http/3 support, advanced TLS options etc.

Source?

A records are blockable the same way, it wouldn’t buy them anything here.