(because the last one was private)
Check out my extension RandomUA, which randomizes your User-Agent header for each request in a way that preserves compatibility but really mucks up tracking.
Learn more at https://leotindall.com/randomua/
Please boost and send me comments on what features you'd like to see!
@tindall often with these randomizers, the biggest fear I have is the sites where i purchase stuff from or pay my bills in are not able to track if am the same entity being sent to the payment gateway. am not sure if ua is part of their consideration but it's been a really bad experience.
@tindall usually buying stuff can be retried. But stuff like booking a seat going somewhere and there are limited seats and absolute rush to get preferred seat, there are no second chances if the browser can't send through the data to the pg reliably. So it's not a very happy thing nor is it ever taken lightly.
@tindall Hey, good work! The thing I would recommend is writing a good non-technical description of what the extension does so more people understand what it is and why it is useful. Also, upload some nice screenshots, that gives people confidence that they are not installing something harmful. Finally, there is a console.log in the .js file. Should that be there? I installed the extension on Chrome and it seems like it does not log anything.
@damaru Re: the console.log statement, it logs to the browser console, not the general dev console; it's useful if people want to see what they're masquerading as.
Re: screenshots, that's a good idea; those are in the works for 0.2 which should be coming out in about twenty minutes. Thanks for the suggestions!
@tindall Is UA really all that big a part of the fingerprint? I thought it didn't account for much entropy.
@tindall I guess if they rely on it as a stable part of the fingerprint, that could help.
ｃｙｂｒｅｓｐａｃｅ: the social hub of the information superhighway
jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal