This is great for privacy! I love the way Brave has clearly documented which items they block, and even link to issues so people can try to understand the reasons. That's a bit harder to do with a single-line pref string, and nearly impossible to make visible if it's remote-settings unless we have an explicit documentation page. The more tracking parameters we end up blocking (Brave currently has two dozen) the more likely this could lead to mysterious failures because unrelated sites just happened to use the same abbreviation for something else.
A contrived example, but imagine someone has a fantasy soccer league site. Players could be very frustrated if they're unable to link to their profile because we keep stripping the *F*oot*B*all *CL*ub *ID* param. A bit of documentation could help sites avoid using those IDs. -Dan Veditz -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CADYDTCB8gh7GjVpx9pMLD5pqpDjc%3DgeqkyRJzvcK2KZpwNFSgg%40mail.gmail.com.
