Change User Agent String Automatically

[van p]

https://www.ghacks.net/2019/04/21/new-microsoft-edge-may-change-user-agent-automatically/

Since there's so much discussion about this topic on this forum, is there any chance this could be done with Pale Moon and/or Basilisk?

[vannilla]

But it's done already. Not like Microsoft, but a similar mechanism has been there since at least 27 (probably earlier, but I didn't keep track.)
And there are extensions too if you want.

[Nigaikaze]

is there any chance this could be done with Pale Moon and/or Basilisk?

It has been under consideration. See UXP issue #380 for further details.

[New Tobin Paradigm]

If that is used or a different implementation.. It would be a scheduled update of a list not a phone home ping for every site you visit. Cause that is beyond fucking ridiculous.

[gepus]

Misleading:

The new Microsoft Edge web browser is based on Chromium, the same core that Google Chrome uses. It may identify as Chromium because of that and that should give it the same level of compatibility with websites and applications as Google Chrome.

There is no way the UserAgent can improve compatibility with websites and applications.

Only thing it can do is to overcome discriminatory Apartheid tactics (aka Browser Sniffing) used by some content providers like Google and Microsoft.

[Moonchild]

There is no way the UserAgent can improve compatibility with websites and applications.

We have 10 years of experience with the opposite, because webmaster don't listen and don't make changes. Neither will framework authors. They will continue using UA sniffing which means to be compatible you have to present them with what they expect.

[gepus]

As a former Opera Presto user I have 20 years of experience with UA sniffing.
For me compatibility means code served by the remote server which the browser can or can't deal with.
If a faked UA (because of discriminatory behavior) means browser compatibility for you - be it.

[vannilla]

As a former Opera Presto user I have 20 years of experience with UA sniffing.
For me compatibility means code served by the remote server which the browser can or can't deal with.
If a faked UA (because of discriminatory behavior) means browser compatibility for you - be it.

The thing is, Pale Moon can actually deal with 90% (or more) of the code out there, and for that 10% (or less) that it can't, usually frameworks have polyfills available despite the UA sniffing.
The features that require a change in the core are a very small percentage, and it's unclear how much they are used in the wild, if at all.
Maybe 20 years ago it wasn't the case, but it is now.
So faking the UA can improve compatibility in 2019.

[gepus]

Maybe 20 years ago it wasn't the case, but it is now.
So faking the UA can improve compatibility in 2019.

It was the same story as it is in 2019.
We had SSUAO as we have today. An SSUAO wasn't considered to be a compatibility fix since the browser was compatible with the site and was only blocked on purpose.
A compatibility issue was only if the browser couldn't deal with the code of the remote server, regardless of the UA. It happened rarely but it happened as it can happen in 2019 as well. Wonder then how such a situation is called nowadays, 20 years later?

[New Tobin Paradigm]

I see what you are doing here. Stop it. Just.. stop.