- cross-posted to:
- technology@beehaw.org
- cross-posted to:
- technology@beehaw.org
cross-posted from: https://lemm.ee/post/3376057
I held off on Windows 10 for as long as I could until my job required it. Now this nonsense. I hope this isn’t the start of them joining on the web DRM bandwagon.
Does a user agent change this
wait so it straight up just refuses to work if it detects that you have Firefox via the user agent??? I knew Adobe was scummy, but THAT MUCH?
That’s the go to way to do it, you only allow the browsers that you know work, Firefox probably works fine for most things but maybe one feature breaks and instead of fixing it they decided to remove it from the whitelist
That dude ain’t joking. You can bypass similar bs by changing user agent
The server just sends files as responses to http requests. If the server is playing nice and just checks the user agent reported by the client, then that’s what you would expect.
And, it might make sense to do so in order to provide a product that meets certain requirements. It is certainly worrying that they need to do that, and not a good thing to make products exclusive to proprietary clients.
yes, you can find an addon for it in the marketplace
On Firefox perhaps a UA value can still be set in “general.useragent.override”.
Used to do it a couple of years ago, now I just prefer letting websites know that they are still receiving traffic from users running Firefox instead of Chrome.