In the case that you're providing an explicit id as an argument, yes. If it were a query, no. It's dangerous to use an empty value for all failed lookups, as you can't differentiate between "not found because it doesn't exist" versus "not found because the database went offline for a minute".
deactivating and/or closing your account just gives them more datapoints imo, and the number of people who do it is so small that it makes a great metric for fingerprinting.
It's not the size of the change that's a problem, it's that the change doesn't address the problem at all, and that the only metric for success for these changes is how angry they make people (which, in the circles of the people proposing these changes, means the change is "working").
It's entirely possible to hire more engineers of color and pay them fairly, but it turns out that pitting workers against each other by introducing a handful of inconsequential process and standards changes is much cheaper and hinders the solidarity that enables coordinated advocacy for better working conditions.
It looks like yet another cosplay of 20th century labor politics, but with the typical 21st century twist of diverting the fight from those who wield power to... the paying customers, for whatever reason.
To give an example, I'd rather not have votes count from people who are upset about this one particular method of ranking. I might start using this view more!
PiHole has a web admin UI that's pretty slick. It has options to disable the entire thing indefinitely/for a set period of time if you need to, and it can log all DNS queries, so you can override/manually block anything you need. There's also nifty charts and metrics to show you how much traffic has been blocked.
I found that, after tinkering with blocklists for a bit, I turned off logging altogether and just let it run. The one thing that gives us grief occasionally is (unsurprisingly) tracking links from promo emails and social media. These are usually easy enough to bypass, but it can be a pain for non-tech-savvy people.
This is a feature that has been requested, but isn't implemented yet. Suggest you give it a thumbs up on github as they implement things in order of highest number of thumbs.
It wouldn't be DNS blocking. The feature request on the project is about adding an HTTPS MITM Proxy that would then do the cosmetic filters among other things.
AGH already supports adding AdGuard filters, but for obvious reasons it only applies domain based filters. Adding the MITM proxy would allow for processing of the cosmetic filters too.
No. It inherently cannot. Pi-Hole isn't a proxy where all traffic is flowing through it and has a chance to be modified. Pi-Hole is strictly answering the question, "What is the IP address for this hostname?" If a given hostname is known to host trackers or something undesirable Pi-Hole will claim it's an unknown host so the device is unable to reach it.
