Earlier quoted context omitted.
This is the Little Snitch[0] problem. If you have ever used Little Snitch, you will soon realize that 1) there is so much crap phoning home and 2) most people do not want to deal with giving permission to each and every one of these services. I have tried giving permission and at the end of the day, it's just not worth the time. For me, Little Snitch is great as a reporting tool but it's just too much work as a firew…
> most people do not want to deal with giving permission to each and every one of these services. It’s far worse than just annoying: if people have to give permission to a bunch of things they don’t understand, they will absolutely give permission to something they shouldn’t. You want the user to make a few decisions as possible, and every single one should be an actual decision: where the user knows what the options…
I understand the point, though. Going to just about any major website you will be pummeled with prompts to allow for a dozen different domains just to view one page, and it doesn't really give any indication of what those are used for. They have a what seems to be infinitesimally small list of connections that they do recognize and explain their use, but ultimately it's pretty useless for the vast majority of prompts.
I'd like there to be a better way to deal with this, but I'm not really sure what the solution to it would look like. You can download blocklists and just silently allow other connections, but I don't think that's significantly better than just using a hosts file.
The most useful thing Little Snitch does is alert me when individual applications try to phone home. For browsing the web it feels more like a chore.