4 ms·
It appears that setting it to the same as Chromes does indeed work! for context this is what I had set (and, for quite some time it was working): "Mozilla/5.0
by dijit 7y ago
It appears that setting it to the same as Chromes does indeed work!
for context this is what I had set (and, for quite some time it was working): "Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecho/20100101 Firefox/57.0"
Ironically I set this so that I could continue logging in to google. Since I had been unable to log in to google-apps without setting this user agent string.
What did it fail on? the mis-spelling of "Gecho"?
- migueldemoura 7y agoThat User-Agent won't trigger the block page you were experiencing. No clue about the issues with Google, perhaps some feature detection going on?
- The-Compiler 7y agoNope, it's Google trying to ban "embedded browser frameworks" - see https://github.com/qutebrowser/qutebrowser/issues/5182 https://github.com/qutebrowser/qutebrowser/issues/5182 for details.
- GoblinSlayer 7y agoI used straight firefox and was still banned just fine. It didn't start in 2019 either. Chrome is their cash cow, if you don't use it, you're a liability.
- The-Compiler 7y agoI always recommend setting custom user-agents for a problematic page instead of setting them globally. For the Google issue, qutebrowser v1.9.0 does that already, see https://github.com/qutebrowser/qutebrowser/issues/5182 https://github.com/qutebrowser/qutebrowser/issues/5182
- anthk 7y agoSo can do Falkon :) Having a Chrome UA is a MUST on webkit based browsers if you want Google's taxing services such as Earth/Maps/Gmail and so on being faster and smoother than ever. Seriously. Once you open Street View on luakit/vimb with a Chrome UA, the diff is night and day.
- The-Compiler 7y agoI tried with Street View im vimb. I don't see any difference - it's slow to the point of being almost unusable, while it works fine in qutebrowser.
- anthk 7y agoon ~/.config/vimb/config set hardware-aceleration-policy=always set webgl=true
- The-Compiler 7y agoThat seems to help, but I still don't see a difference with/without a Chrome UA.
- anthk 7y agoTry a mobile Chrome UA, such as the one for a recent Galaxy Tab.
- jimrandomh 7y agoIt's the severely-outdated Firefox version number. Spambots and crawlers sometimes have user-agent strings corresponding to very old browsers, because they were set once when the bot was created and then never updated. On an unrelated site that I run, we get a lot of traffic with user agent strings corresponding to implausibly-old browsers, and it's ~100% bots.
- SilasX 7y agoNovember 2017 is “severely outdated”? https://www.mozilla.org/en-US/firefox/57.0/releasenotes/ https://www.mozilla.org/en-US/firefox/57.0/releasenotes/
- nrb 7y agoTwo full years for an evergreen web browser, which contains probably the largest surface area for software exploits of anything on the machine? I’d argue absolutely yes. As others have echoed, this is probably a huge marker for malicious bots to Cloudflare.
- giancarlostoro 7y agoEven a month of no updates to browser is a bad idea.
- deleted 7y ago[deleted]
- jlokier 7y agoThe evergreen browser is a thing, but the idea that everyone can trivially upgrade those browsers is promulgated as true when it's a bit of a myth. It is sometimes expensive for people to upgrade browsers, called evergreen by developers so they can avoid annoying support expenses for a few percent of people. I had a phone running a Mozilla browser, which received updates until it didn't any more. Then the only way to upgrade browser was to purchase a new smartphone. Unfortunately it was a superb device with no newer replacement, so to upgrade browser I had to downgrade my smartphone for other uses, and pay the cost of an expensive new smartphone despite not really wanting one. But sites saw it as "you are running an old Firefox, you obviously can trivially upgrade". I still have a perfectly great old Android tablet running an old version of Chrome which cannot be updated. Other than website compatibility, everything on it that it is used for is still working flawlessly. Perfect screen, sound, wifi, memory, battery. For now, enough sites work on it that I still use it. That can be replaced easily with another tablet, but it is disappointing to have to spend cash and throw away a working product to e-waste, just to replace it with a functionally identical device because of the way the software treadmill works. (It doesn't have to work like that, it's a choice made by developers collectively.)