Is this the start of resistFingerprinting finally getting actual UI implementation? I know that canvas protection is just one part of it, but could this be signalling a full implementation of fingerprinting protection in the GUI by Mozilla?
this entire github issue pretty much solves my question so I’ll mark this as the solution. thanks @sha123 for linking to an older discussion where Thorin first explained the difference between FPP and RFP.
Yes based on what what was said in the github discussions, it does seem like FPP will entirely replace the need for CanvasBlocker. Right now it’s only getting canvas randomization but, based on the first github page linked, there should also be audio protections coming as well.
Phase 1 includes fonts at vis level 2 (i.e only allow os system fonts), subtle canvas randomizing (excluding IsPoinInPath and isPointInStroke), and I think window positions = 0. Last but not least, removing math entropy in audio for all FF users - note this does not remove all entropy, and RFP has additional protections which should then make all RFP users the same per platform (because Hrtz etc affect results but RFP sets those).
Having those built into the browser would make CanvasBlocker redundant and would likely make you stand out a lot more (since the pool of FF users with Strict mode on is going to be significantly larger than the pool of CanvasBlocker users).
Massive organizations are monitoring your online activities. Privacy Guides is your central privacy and security resource to protect yourself online.