this post was submitted on 05 Jan 2024
173 points (100.0% liked)
Technology
37739 readers
655 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
users can modify their useragent string, and sometimes they have to because some webdevs are morons.
some browsers actually default to using chrome instead of its own.
using a browser-reported useragent string to count marketshare itself is flawed from the start, using a very narrow and limited scope of web sites to measure it--even more so.
if i counted my own clients: home, soho and small business end users... it's about even between chrome and firefox on windows (chrome users doing so on their own, as we highly recommend firefox, and vivaldi over chrome for a chromium-based solution) with edge trailing far behind; and about 3 to 1 android (chrome) over safari on mobile with (so far, but soon to change) very few mobile firefox users.
Government websites are really bad about needing to fake the user agent string because of low bidder contracted work that often starts and ends with Internet Explorer/Edge and is rarely updated due to how government budgeting works.
Using a Chrome user agent in FF can result in broken video / audio playback on various sites.
i had to fudge the useragent to chrome yesterday to get 1080p out of azn.