Adjust user agent version automatically

[Chocobo1]

The version calculation is an estimation and it will drift off after some time. Hopefully the drift offset won't be noticeable within a few years.

Also switched the user agent to Windows 10 which has the largest portion of users to avoid standing out from the crowd.

[glassez]

Also switched the user agent to Windows 10 which has the largest portion of users to avoid standing out from the crowd.

You untie it from a specific browser version, but you bind it to a specific OS version (moreover, not the most recent), which is subject to the same obsolescence problem. Is this a good idea?

[Chocobo1]

You untie it from a specific browser version, but you bind it to a specific OS version (moreover, not the most recent), which is subject to the same obsolescence problem. Is this a good idea?

Not many options available here IMO. Win11 market share is still relatively small compared to Win10.

[Chocobo1]

Also this: https://developers.whatismybrowser.com/learn/browser-detection/user-agents/detect-windows-11-user-agent

[glassez]

You untie it from a specific browser version, but you bind it to a specific OS version (moreover, not the most recent), which is subject to the same obsolescence problem. Is this a good idea?

Not many options available here IMO. Win11 market share is still relatively small compared to Win10.

I would leave it as it is. "Linux x86_64" looks less affected by time. Besides, did we have any problems with it?..

[Chocobo1]

Besides, did we have any problems with it?..

No one reports it but it is too easy to identify/fingerprint an qbt user as the "Linux x86_64" user base is too damn small.

[glassez]

No one reports it but it is too easy to identify/fingerprint an qbt user as the "Linux x86_64" user base is too damn small.

If we proceed from the same considerations, Firefox userbase is also (relatively) small.

[Chocobo1]

If we proceed from the same considerations, Firefox userbase is also (relatively) small.

I've considered using chrome user agent but its release schedule is too unpredictable and also the composition is too complex to get it right.

[glassez]

If we proceed from the same considerations, Firefox userbase is also (relatively) small.

I've considered using chrome user agent but its release schedule is too unpredictable and also the composition is too complex to get it right.

Ok.
Last question. Is there any chance that the calculation algorithm you are using will not produce an unreleased version in some corner case (under normal conditions)?
It is preferable to look plausible than to necessarily use the latest version.

[Chocobo1]

Last question. Is there any chance that the calculation algorithm you are using will not produce an unreleased version in some corner case (under normal conditions)?

The firefox release schedule looks to me that they release every 28 days (on average). The PR uses 30 days so it should slowly lag behind the latest release. Even if the calculation is slightly ahead of the release (which should be very rare) it is no big problem because it will be the same as Firefox Beta or Firefox Developer Edition (which still are valid user agents). Those FF betas uses +1 version from the released version.
Another possibility is that FF might delay a release but manually checking the history release dates I haven't noticed such thing.

[xavier2k6]

Just posting this as an FYI / post a question.

Should we defer this PR & use Firefox 128 (ESR) / 2024-07-09 for the base version/date when available??

Is this PR or the other user-agent PR going to be backported to 4.6.x branch?

[Chocobo1]

Should we defer this PR & use Firefox 128 (ESR) / 2024-07-09 for the base version/date when available??

Probably not. The drift offset shouldn't be noticeable within a year or two. The maintenance sync/update could be performed once per 5, 6 years (if it really requires).

Is this PR or the other user-agent PR going to be backported to 4.6.x branch?

The other previous PR should be backported. This PR is suited for qbt v5 IMO.