I asked this question about Audio Fingerprinting in Tor/Firefox, and a thorough answer was given, that’s great. However then the topic was almost immediately closed. While the answer was thorough, I am not fully able to understand it and have follow up questions: “Does this mean it’s expected for gecko browsers including normal firefox to share a set number of audio fingerprint hashes? (a good thing)”
The more we can actually discuss and knowledge can be shared for people to find later, the better. I think whatever policy is auto-closing a topic like that so quickly is destructive
But I didn’t mark a reply as the solution. Some one else must have, preventing me from actually getting the answer clarified in a way I could understand.
You probably have a “Solution“ button on this post, too. Other people aren’t allowed to mark it as that except you and probably the mods. If you’re absolutely sure about you not marking it as a “Solution”, I think you can ask the mods about it.
I set the solution (I do this often so 1 I never have to revisit (memory) 2 time is a resource, deal with everything in one hit whilst I’m there … and 3 I score a “solution” ).
I was unaware OPs can’t respond within 24hrs to their own issues
"Does this mean it’s expected for gecko browsers including normal firefox to share a set number of audio fingerprint hashes? (a good thing)”
Yes,. it says that in my solution
In gecko, all audio (it’s not a RFP thing) now uses the same math library across all platform architectures reducing differences to what cannot be spoofed/hidden (i.e equivalency)
a finite minimal number of deterministic hashes (diffs are only caused by architecture)
tl;dr - there is no entropy in audio with RFP
RFP (tor browser) also covers Math and additional audio entropy such as Hz
Thank you so much for the follow up. Perhaps the settings could be tweaked to not lock the thread for the OP after marking? Regardless appreciate your time and expertise