At flare-up #237 you'd think one would have figured out a professional way to handle questions like this. Buried in the pointless flamewar is the maintainer's

At flare-up #237 you'd think one would have figured out a professional way to handle questions like this. Buried in the pointless flamewar is the maintainer's own reply which is the way forward: > Anyway, if there's a well respected network of community DNS servers that can roughly match Cloudflare/Google we can add, sure. That is the correct and initial response the maintainer should have given. It puts the onus on OP to show how their preferred DNS stacks up against Cloudfare/Google. Instead, the maintainer plays dumb wrt the importance of defaults, essentially guaranteeing that OP will escalate the rhetoric. Worse, the maintainer responds in kind. If the maintainer had gone the correct (and easy!) route, we'd all benefited by having learned how this non-profit DNS stacks up against the others from a technical standpoint. (How does it, anyway?) And to cover my bases-- when spam gets through to the inbox, no serious person asks, "Why doesn't anyone ever talk about the spammer's responsibility to prevent spam? What about the spammer?" Similar logic applies for why I'm talking about maintainer and not OP.