I think the implicit assumptions about the “Police carry insurance” thing are:
- Non-criminal Qualified immunity protections are replaced by insurance carriage
- LEOs have to pay their own insurance (presumably with a pay hike that’s the “average” insurance payment
Without QI, LEOs would be liable. Insurance companies can certainly force LEOs to fight court cases, but the costs of doing so will fall on the insurance companies. An LEO that’s constantly a problem will find themselves in court a lot, and will end up costing the insurance company a lot, regardless of whether it’s just legal fees, or massive damages to their victims in addition to legal fees. So the insurer will force them to pay ever increasing premiums, and eventually they won’t be able to afford to be in law enforcement.
Most of what you’re saying would undermine the existing professional insurance requirements for doctors etc. Hell, it’d undermine insurance requirements for driving!
Also remember insurance companies rarely insure just one thing. You may get a carrier that specializes in LEOs, but in practice like most insurers it’ll cover a wide variety of different types of liability insurances, directly or indirectly. So it’s not necessarily in its best interests to defend LEOs regardless of what they’ve done. That just encourages bad law enforcement, pushing up its costs elsewhere.
The big problem with blocking GA altogether is that GA is usually how people who put together websites find out what browsers people are using to browse those websites.
And if you’re about to say “But they can just look at the user agent in access.log!”, sure they can, but those are in logs that are accessed by sysadmins, not people trying to find out how their websites are used. The first thing someone who’s trying to find out how to optimize their website does is go into GA. If they see no Firefox users in GA, then they don’t care about Firefox compatibility. They may even filter it out to prevent bots.
In order to fix the tracking cookies thing we need to do more than block a popular tool for getting website metrics, we need to understand why it’s used and provide alternatives that respect privacy.