FYI about strict navigation blocking any URLs that have fbclid parameter

[kowith337]

I've noticed that Facebook start to have improved their ability to track external URLs by add the fbclid parameters, even the target URL was already resolved by custom userscript, extensions and others like...

Here's an example of URL that added fbclid parameter.

https://github.com/kowith337/PersonalFilterListCollection/blob/master/docs/Facebook0-Bypassing.md?fbclid=IwAR0EibcyYCzmDGfhk_Z1WqKaq8FpBuKjDwO8rTTWEPzMNHrGM7bLvb2-DN4

And now I have added two rules, both are block as document to prevent navigation happen.

PersonalFilterListCollection/filterlist/FacebookZuckestionKiller.txt

Line 21 in 5742ff9

||*&fbclid=$document,important

PersonalFilterListCollection/filterlist/FacebookZuckestionKiller.txt

Line 22 in 5742ff9

||*?fbclid=$document,important

An idea is to let the strict blocking function activated by two rules above, while uBlock or Nano give the warning about strict blocking to prevent navigating to the URL that have tracked parameter, the real URL can be exposed below the blocked URL by click to the 🔍 button with all parameters stripped and it won't bind in the real URL together.

However, for some domains that have multiple parameters like...

You need to make a text selection and then...

• Copy URL and then paste to address bar (or perform Paste and Go), make sure you have exclude selecting all of fbclid parameters and values.
• Right Click (or Tap+Hold) and perform Go to web address that you've selected.
  • For Firefox and other forks, it doesn't show the Go to menu, instead, you can perform Open in new tab/window or private window with text selected URL.

[uBlock-user]

why two filters ?

Just use *fbclid=$1p,document,important or *clid=$1p,document,important to block gclid too.

[kowith337]

I'm not sure using wildcard will be affected to anything that not related to both parameter of that or not, but based on my experience, the first parameter will start with ?param_name, and will be start with &param_name for second and/or afterwards, depend on the target site that have another parameter before Facebook injecting fbclid or not.

However, I think I've seen sometime it's also beginning with # but don't know is Facebook still can read their fbclid value with that situation or not?

[uBlock-user]

Forbes makes use of # so it's not just ? or &, unfortunately # is not considered as a URL param query.

[kowith337]

Currently Facebook also increase layer of external URLs tracking...

1. All of external URLs will going through l.facebook.com or lm.facebook.com if you're use mobile site, neither it's basic or touch.
2. Destination URL inside u parameter will also binding with fbclid (URL encode/decode)
3. Also boxed by h, __tn__ and c[0] parameter.

[uBlock-user]

$queryprune has been added to uBO dev build, now you can prune those queries.

[kowith337]

Thanks for your information and updates about uBO dev, however, after testing by myself, I decided to use the queryprune rules as for handling requests that shipped with unnecessary parameters, this might helpful in some case e.g. Steam trying to bind snr parameters everywhere, even while search for games and/or products, the strict blocking document in ASTLW may still keep with left some short message behind domain=~, but other requests (e.g. xhr in overdone version) will lower priority to block or getting removed once that function added in stable releases.