It seems like a good idea at first glance but it's actually useless amd may potentially be harmful. The "developer" proudly advertises browser finger fingerprint spoofing as one of the features and also recommends using it alongside a vpn, which means that if there is no lower level surveilance the traffic won't poison your advertiser profile, it will just be a literal random noise, on the other hand if there is os-level surveilance (as is the case for stock android) it will ignore this random noise. Either way it's useless and the only outcome it acheives is making you solve captchas every time you want to actually use google, because you get flagged as a bot. But that's just technicals, the actual issue is that it's actually just an ai slop, which becomes obvious looking at the readme file, also the "dev" admitted to using ai (which is still underplaying it's role) on github. So if you are serious about privacy and safety the first step to take would be to not install random slop on your device and give it your credentials (as is necessary for some of it's "functionalities")
washington_irving
This issue was raised on github, the dev admitted to using AI (but probably still underplayed it's role in the project) but closed the issue and didn't bother to disclose it in the readme.
ahh, sorry what I meant is that the app shouldn't randomize identifiers, such as browser fingerprints or even cookies, because the goal is to make the noise associated with the user's profile, otherwise it's just random requests and it becomes pointless.
Still, browser fingerprints are most commonly used and spoofing them seems counterproductive. If the goal is to maximize confusion about users interests and search history it should mimic actual users' behavior as closely as possible.
yes, but when you spoof fingerprints the only thing connecting the noise generated by the app to the user is then the IP address and ironically the README recommends using it alongside a VPN to hide your IP, which means that the queries made by Fauxx are, like you said, "just noise", not noise associated with your profile, the noise could as well be generated by any other device
also, I think that the extensive use of LLMs should be stated in the description, not burried in a closed issue, as it is an important matter especially when creating a privacy oriented project
The concept is very interesting, I used the app for a while but I don't get one thing. Why would you want to randomize fingerprints? If the goal is to pollute your profile with random data then it does the exact opposite thing and makes it harder to assosiate the noise with actual user activity.
well, if the point is to "poison google's data collection" by obfuscating your real traffic with random noise then I'd assume you still want to use google