Is HydraVeil going to be packaged as a flatpak?
This quote below from Daniel Micay of GrapheneOS is fire,
"You talk about privacy in general but then talk specifically about fingerprinting which is not something any mainstream browser has meaningful defenses against, including Firefox. Even for the Tor browser it hardly accomplishes much with JavaScript enabled. I have fingerprinting code that works great with it and bypasses their weak attempts at mitigating it. You're proving the case for why doing something is not always better than nothing. If what is done isn't meaningful, which it really isn't, then people are given a false sense of security / privacy which ends up causing them more harm than if they acted as if that non-working defense didn't exist. Define an actual threat model and explain what the defenses are supposed to mitigate. In reality, it's ineffective, and there's a reason it's not exposed in the UI. Firefox has an almost entirely bogus tracking protection feature exposed in the UI which is fundamentally broken from the design and entire concept behind it, so there's a pretty low bar, and yet these features don't meet it."
And that's why HydraVeil exists. Sources/info here:
https://simplifiedprivacy.com/web-browsers-become-the-new-os/and-the-program-is-tyranny.html
Discussion
It's unlikely, as flatpaks are more isolating from the rest of the system, and HydraVeil uses systemwide resources. Also they are generally served up by the flathub repo, which is outsourcing our security to Fastly CDN for little benefit
Understandable although I think it's still possible and you can have your own repo. What about #appimage packaging?
Also, does HydraVeil defeat fingerprint.com?
It's possible yes, but people typically use their flatpak repo to standarize it.
And yes it gives different fingerprint ids to fingerprint-com