User agent sniffing is poor practice anyways. Try to use the feature and react according to the browser's abilities. Analytics and similar can sniff all day though.

To push browsers to get rid of UA string, we should all use a UA string extension that uses the same string like "DOG-SHIT". That way it'll start showing up in analytics.

And if you're trying to date the "data science" girl, spam the app/website with UA string like "hi-amy-will-you-go-out-with-me--sincerely-jack-who-sits-behind-you."

Client Hints are the recommended replacement for UA strings. I believe the default behavior for Chromium browsers is already changing (looking for schedule link).

[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hin...

In retrospect, wasn't putting "Mozilla" in your user-agent string when you aren't the Mozilla Foundation or project a trademark violation, that they could have enforced?

I know it would be a temporary disaster but I think at this point I wish Safari, FF, Chrome and Edge would just decide on a flag day to get rid of user agents.

From March 17th, 2023 (or whatever) all user agent strings are now “WebBrowser/1.0” until the end of time.

Just force the switch to better methods.

The title is clickbait. If anyone forced here anything, then it was not IE but - once again - webmasters who don't deserve that "title" ;)

I get this warning for TSB in the UK. I was wondering why, despite having the latest version.

> overpriced MacBook Pro that has a sticky letter s today

This joke flew right over me. Can someone elaborate?

The more this happens the more Chrome deciding to freeze the UA string forever makes sense.

Are they talking about only MacBook Pros with Intel chips since they reference Butterfly keyboards or is that sarcasm that sort of feels out of place ?

So rv0110.0 would not work?

Stop sending User-Agent. Replace it with nothing. Not client hints. Nothing.

If sites start rejecting Firefox clients because of that, then instead change it to send exactly the same User-Agent (and other software identification) that Chrome sends, and commit to exactly faking Chrome's signals in the future.

The UA header never had any business existing to begin with. Servers guessing client capabilities from the software they're running, or trying to work around client bugs, is architecturally insane, concentrates power excessively, and guarantees that morons will write bugs like the one this story is about. And the other uses of the information are simply evil.

If you need to signal specific capabilities, which you generally should not be doing because you shouldn't have punted all real attempts at standardization years ago, then signal specific capabilities. Or let the server try stuff and give only success or failure feedback.

>Teams are broken under Firefox

>change useragent to egde/chrome

>it works now

Thank you Microsoft.