longterm useragent solution #790
Comments
|
Nope to the less compatible default. |
|
The default is simply the real one. The bundled useragent changer is to lie easily. |
|
vivaldi opera they both identify them selves at the end and pretend other stuff before that. Stuff at the beginning more important then stuff at the end. So i guess waterfox should be something like this:
i think alex had done something similar? The same? the Firefox version can be regularly changed to what is currently most compatible. For the remaining sites, the user uses the bundled useragent changer..... |
8e978a6#diff-a633a6dfcf161bf7cb9d3d9cdcdc2faeR439 lines 439 and 442, I guess. Related:
-1 56.2.5 is, loosely, more like 56 (with some 57) than like 60. Respectfully, -1 |
|
Are they sites that treat the UA of firefox and the same UA with "Waterfox/56.2.5" at the END differently? Github seams ok. other sites seam ok also. I think Alex's error, was to put "Waterfox" first. Stuff more to the beginning are more important. Sites will simply ignore the end they don't understand, and interpret the beginning as firefox. And he also gave firefox the version number of waterfox, a version number that doesn't exist. Do you have a problem with something like this as a default? Bundling an extension is easier then making UI changes.... It's a more realistic proposal. |
Probably not an error. Please refer to the previously linked issue, #178 (comment) in particular. |
|
you forgot the "rv:57.0" part? rv:XX and Firefox/XX at the same version number that really exist. The beginning is just a copy paste from firefox. Then at the end Waterfox/YY with YY the real version of Waterfox. XX and YY shouldn't be the same. github doesn't complain with this |
|
GitHub takes an exceptional approach to at least one Linux-specific string. #789
Nope, not forgotten. Please refer to the previously linked issue, #178 (comment) in particular.
|
|
you used "56.2" for that experiment A-0X about it's treated differently from It's the Waterfox part or the 57 part? Firefox 57 is quite old now. |
|
57 was suggested at #790 (comment) above. |
|
I think a year ago, a number of default user agents overrides were shipped with Waterfox just for compatibility. But this meant that a lot of rules where being made and updated every so often. And I'm sure that these were all cut until some we found out a better solution to manage them. I've had a few problems with the default user agent string too. Just having 'Waterfox' in there breaks slack's god awful whitelist. Even though they support the version of the browser. Usually when I do my manual overrides, I target 60, or just mask it completely |
Waterfox is a lesser used browser, so it will always have to struggle with user agent strings.
The simplest thing to do. Is set the default user agent as "waterfox $version", while let the end user easily pick a user agent with a bundled addon( that already exist) with an obvious new button. He will have a predefined list of user agents to chose from,plus the ability to use his own with a few links where he can find more.
It's a simple solution, doesn't drain resources and less users will complain about their favorite site breaking.
The text was updated successfully, but these errors were encountered: