Viewing Tiktok profiles breaks with privacy.resistFingerprinting=true
When viewing any tiktok account profile page, for example this one , the videos do not show up, and says "Something went wrong, Sorry about that! Please try again later."
Here's what i did:
- Created new Firefox profile with default settings and no extensions
- Visited a TikTok profile, and saw it opens as expected
- Changed privacy.resistFingerprinting to true
- Refreshed the TikTok profile page, and the error message shows up
I opened the console and compared and there were new warnings:
- Blocked https://www.tiktok.com/@tiktok from extracting canvas data because no user input was detected.
- Get user detail failed for getting wrong response
And 3 errors, when there were 0 before, all three read
- Uncaught TypeError: _0x5e9eb8[_0x2bd187] is null
所有回覆 (5)
Yes, enabling that preference causes errors.
Disable privacy.resistFingerprinting (RFP) and use the new fingerprinting protection (FPP) instead which allows disabling it per-site and fine-grained control of protections. The following useragent exception allows TikTok profile pages to load:
privacy.fingerprintingProtection = true privacy.fingerprintingProtection.overrides = +AllTargets,-NavigatorUserAgent
zeroknight said
Disable privacy.resistFingerprinting (RFP) and use the new fingerprinting protection (FPP) instead which allows disabling it per-site and fine-grained control of protections. The following useragent exception allows TikTok profile pages to load: privacy.fingerprintingProtection = true privacy.fingerprintingProtection.overrides = +AllTargets,-NavigatorUserAgent
At the moment i really cant find much documentation at all as to what FPP does. It appears to have been added in v120 but there's nothing at all I can find as to what it actually does. I trust it's good, but I want to know what i'm losing by disabling what I have on right now
FPP is provided under the "Suspected fingerprinters" setting. It only has a few protections by default but with the +AllTargets override it should match RFP. You can test it on sites like browserleaks, if you notice any difference it would be considered a bug.