w3schools.com reports numbers based on its log files (i'd say the visitors of this site represent a specialized subsegment of total Internet community, from which it's hard to make a generalization about an average Internet user). I tend to think that numbers reported by netmarketshare.com (which show that in 2018 Windows 7 has still been the most widely used OS) are more reliable: https://netmarketshare.com/operating-system-market-share.aspx?options=%7B%22filter%22%3A%7B%22%24and%22%3A%5B%7B%22deviceType%22%3A%7B%22%24in%22%3A%5B%22Desktop%2Flaptop%22%5D%7D%7D%5D%7D%2C%22dateLabel%22%3A%22Trend%22%2C%22attributes%22%3A%22share%22%2C%22group%22%3A%22platformVersion%22%2C%22sort%22%3A%7B%22share%22%3A-1%7D%2C%22id%22%3A%22platformsDesktopVersions%22%2C%22dateInterval%22%3A%22Monthly%22%2C%22dateStart%22%3A%222018-01%22%2C%22dateEnd%22%3A%222018-12%22%2C%22segments%22%3A%22-1000%22%7D
Thank you for this add-on: it's very useful and important also because it takes care of JS properties, and this is essential. But there is a problem: when there is a request for a favicon.ico image the browser gives out the actual user agent! instead of the one you would expect. Any idea why this happens? Thanks.
I haven't been able to reproduce the issue you mentioned about favicon.ico. For example, i just visited a site and checked request headers sent, & everything seems functioning OK: Host: static.bfmtv.com User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3 Accept-Encoding: gzip, deflate, br DNT: 1 Connection: keep-alive Cookie: TCPID=119131139489067326342; xtvrn=$548539$; xtan=-; xtant=1; etuix=9cc_5.jv5oCi69wkDT9jtGVIJNVLip69oIcOR5ViDZO_4giNojVnug--; ownpage_fp2=7ebfab6931223c16 Pragma: no-cache Cache-Control: no-cache TE: Trailers
11/15/2017: I've been able to implement it as a WebExtension, but some minor nice-to-have traditional features couldn't be implemented so far. If the bug i mentioned below is fixed, it might be easier to re-implement the traditional features.
11/03/2017: I will try to convert it to a WebExtension, but as of now, WebExtensions cannot set preferences, which means there's no standard way to set navigator.* properties. You can vote for the following bug to request this feature for WebExtensions: https://bugzilla.mozilla.org/show_bug.cgi?id=1414078 Your options will probably be: 1. If i convert to a WebExtension, you could use it with HTTP User-Agent header spoofed, but navigator properties not spoofed. 1.1.Until the bug above is fixed, I will try to provide a user.js file (probably somewhere under https://github.com/haqer1 ) so that users could spoof navigator properties as well by saving that file under their profile folder (with manual updates required until the bug above is fixed). Once the bug above is fixed, i would try to release an update also spoofing navigator.* properties. 2. Switch to an ESR release, & continue to use pre-WebExtensions Blend In (but values will get more and more obsolete over time). 3. Not to spoof anything (i.e., not to try to blend in (perhaps until the bug above is fixed)).
I believe there's either a bug or incompatibility that doesn't work with my TB 10 (esr). The "thunderfoxing" cannot be undone when toggling the "extensions.tildebirlik.privacy.blend-in.messenger.thunderfoxing" string. Also, I see NO OTHER values in about:config except "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0". So, I assume, it's simply not possible to use an updated (most used) TB user agent (and not FF 40). As ulf3000 below said, this would make TB actually more fingerprintable. But works fine for me in FF.
ADD: In answer to your reply, "As of now restart is required upon change of thunderfoxing setting" -That's not the issue, I did restart. With the latest "Blend In" versions there simply seems to be no entry in TB's "about:config" for a most used version of TB (only a FF entry). The last "Blend In" version that still had such a TB entry seems to be Blend In 38.0t31.6.0 which I'm sticking to, right now.
This is also mentioned in About this Add-on section.
But i'll try to automate this for v41 (or v42).
Follow-up on ADD:
I just tried this using v40.0.3t38.2.0 on Linux, and it works as expected: 1. With thunderfoxing: "Firefox/40.0"; build-id is "20150826023504"; oscpu is "Windows NT 6.1; WOW64", etc. 2. Toggled thunderfoxing to false, quit, &amp; started again: "Thunderbird/38.2.0"; build-id is "20150813074416"; oscpu is "Windows NT 6.1; WOW64", etc. This stuff is shown under .applied, but better checked by setting Start Page to a URL that shows this stuff. So i'm unable to reproduce this issue. Perhaps worth trying with a new profile (-ProfileManager)... Also, will try to set up a place for bug reports (like there is for my IA addon) some time in the near future...
FYI, the just released v43.0t38.4.0 has the following 2 new features which you might find useful: * Thunderfoxing setting's changes now take effect immediately (re-start is not required). * Settings can now be viewed on a newly added local page (as opposed to having to view them by accessing a 3rd-party page): resource://blend-in/blended-in.html.
The URL from the 2nd feature, can be set in Tools->Options (Edit->Preferences): Location & accessed conveniently by using Alt+Home shortcut.
Could you include an array of buildIDs keyed to specific FF versions, auto-detect the FF version and use the associated buildID? This would help to reduce potential website compatibility issues that can result if the addon is updated before Firefox itself is updated (or if using Firefox ESR (Extended Support Release)).
Since buildIDs are version-specific, & latest agile release is the most common, the current implementation seems adequate for blending in as far as buildIDs go.
Users who'd like to stay at an older release or ESR release AND not blend in their versions with the crowd can disable auto-updates for Blend-in in Shift+Ctrl+A or globally by setting extensions.update.autoUpdateDefault;false in about:config.
Users who need to temporarily unblend in for compatibility or software download reasons, etc. can toggle notApplicableIfRealPlatformIsWindows or applicableIfRealPlatformIsNotWindows in about:config.
P.S. I've tried to keep this project low-key, but could consider registering it on mozdev.org, for instance, for enhancement requests, etc.
I haven't had any issues with Google Maps and Blend In. When you are having an issue, try toggling notApplicableIfRealPlatformIsWindows in about:config page; if you are still having an issue after that, then it's not related to Blend In.
P.S. If you can come up with the actual steps to reproduce, feel free to post them; but i'm quite certain it's not a Blendin' issue. :)
Does exactly what the description says. On another note, I also do know that extensions like this one can cause some updating problems (depending on the system you're using) for some downloadable programs (like iTunes, Flash, Java). However, this can be fixed simply by disabling this extension temporarily if a 32-bit program doesn't like your 64-bit system. Overall, this is a good extension as this extension does what it is supposed to do.
If you would like more ideas/etc for your extension. Please locate my e-mail on my profile and I will get back to you as soon as I can.
Update: Very nice developer who keeps this extension up-to-date with browser updates that come along. For example, Firefox 27.01 was updated to Firefox 28 (The developer keeps this extension up-to-date with change). Very well done as this is difficult to do!
This add-on does exactly as the description says. Developer has done a good job keeping up with the fast development cycle. Unfortunate more are not using this add-on as it would become more powerful against fingerprinting with ubiquity. Received my lowest score to date with Panopticlick using this add-on and NoScript.
Works as advertised, simply and cleanly changing the operating system reported by your browser. However, if you're looking for anonymity (not sure why else you would use it), this has pretty minimal effect. This is not the fault of the plugin, it's just that the OS doesn't actually convey all that much identifying info since there aren't all that many to choose from. Things like plugins and font lists are far more informative. Also, changing the OS reported by your browser makes a lot of download pages (including Firefox's) more difficult to use because they'll automatically present you with links to the OS they think you're using.