I find that a whitelist is easier to manage than a blacklist. I am not surfing the entire web every day. Why should every URL in existence be accessible by default. Instead, I prefer every URL is blocked by default. No different from any other firewall configuration. With logging of blocked HTTP requests and DNS lookups, it is easy to discover telemetry.

> No different any other firewall configuration.

Depends on whose firewall config, but I don’t suppose most firewalls are setup as whitelists for outgoing connections…

I appreciate your dedication but this seems like a huge pain. Like a restrictive Little Snitch config but with worse UI most likely.

I think that GUIs are a huge pain. I prefer config files. Also, Little Snitch is not portable across platforms. Mac-only.

Most firewalls are set up as whitelists for incoming connections. Similarly, I set up DNS and HTTP "firewalls" as whitelists for outgoing connections. Zonefiles define the RRs that applications are able to query and lists/maps/tables define the hostnames/URLs that are accepted by the proxy.

I’d be divorced in short order if my family had to constantly ask me to add sites to the whitelist.

I can’t see this being workable for the vast majority of people.

You could probably put each person on their own vlan and let them manage their own lists.

It might postpone the divorce by about 5 minutes while you try to explain it.

I don't understand why you would use MacOs if you care about privacy. Why do you use it? (Just to be clear, this isn't "boo macos sucks", I'm genuinely curious why so many people use it (especially in it inclined communities))

This has to be a mistake lol. I had kind of assumed that the lists that come with my pi-hole block most telemetry stuff already.

This was started 11 days ago. I would also start out with all domains in beta. If you add the list to pi-hole you will eventually get the domains once they are "stable" either way.

Even the beta list is only 24 lines long...

Yeah... about that. Seems less useful.