FreeBSD user agent in Firefox and Chromium is Linux 64 bit

I don't know when www/chromium changed, but www/firefox changed long ago.

… how many metrics are measuring web traffic and counting FreeBSD as Linux?

You can probably include Statcounter.

 
I regret this change. For badly-written websites there are user-agent changing extensions, at the very least it allows for reporting this to the webmaster(s). It would be great if there was an OPTION in the port to disable this behaviour. I don't like the idea of using local patches on my poudriere build, but restoring the User-Agent feels like quite innocent.
Important to know: apparently many Firefox extensions whitelist Linux and won't work anymore. Why does it always feel like the world is regressing?

Even then, recently I found that I was blocked from viewing a website of a large electronics-parts supplier due to "changes to prevent bots from navigating the website". A User-Agent that contains Linux was apparently already enough to trigger this. (Which is just an example what bad website design leads to, not related to the commits below).

More information can be found here:
PR 226919 and the two relevant commits: ab146876a894c84256e94c43b6955b2a2ad49313 and 5f83a8cdba544023d975dd1da704ac833836a062.
Quick note to forum admins: a [ commit ] tag could be useful, mirroring the [ pr ] tag for commits.
 
Last edited:
the 2018 changes for compatibility with AMO).

… blocked from viewing a website of a large electronics-parts supplier …

PR 226919 and the two relevant commits: …

You might find that at least one of those commits was irrelevant to the website.

2018 report 226919 (from me) was specific to AMO, that is, addons.mozilla.org for add-ons (Firefox extensions, and so on) – not an electronics-parts supplier.

1729549563498.png


1729549890182.pngAt a glance, the scope of other commit was also limited to searches for add-ons:



the change upstream, RESOLVED FIXED on the 123 branch.

Ten months ago

That was, January 2024.

HTH
 
Back
Top