Chrome phasing out support for User-Agent

Post by naasking » Thu, Mar 26, 2020, 5:13 PM UTC

NotSammyHagar wrote: post #160

jedberg wrote: post #143

Earlier quoted context omitted.

> I'm pretty sure that the webmasters responsible for this are using user agent string blocking as a naive attempt to block bots from scraping their site, but that assumes that the bots that they want to block actually send an accurate user agent string the first place. That is exactly what they are doing, and it works really well. We blocked user agents with lib in them at reddit for a long time. Any legit person bu…

Yes perhaps. But it caused problems for regular users like this fellow. I also have tried various 'download via script' for web pages for offline use. I thought I had a problem on my end, I never realized I could have been getting blocked.

Post by AnssiH » Thu, Mar 26, 2020, 5:33 PM UTC

rubin55 wrote: post #284

heavyset_go wrote: post #214

Earlier quoted context omitted.

Streaming above 720p also doesn't work via Firefox on any operating system.

Source?

Post by freehunter » Thu, Mar 26, 2020, 6:17 PM UTC

collinmanderson wrote: post #291

jsjddbbwj wrote: post #278

Earlier quoted context omitted.

Chrome 0.2 on Windows XP?

As a web developer, I have very little trouble reading the User-Agent header. User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.1.2222.33 Safari/537.36 Sec-CH-UA: "Chrome"; v="74" Sec-CH-UA-Full-Version: "74.0.3424.124" Sec-CH-UA-Platform: "macOS" Sec-CH-UA-Arch: "ARM64" Sec-CH-Mobile: ?0 Isn't moving this information to a separate Sec-CH-UA headers going to make t…

Post by maverick74 » Thu, Mar 26, 2020, 8:38 PM UTC

jakeogh wrote: post #273

Fantastic. Thank you Chrome team! Especially for those who dont execute arb JS, this is a huge +. Personally, I would like to drop the line completely and not send the key at all, but it's a start.

Post by elevenoh » Fri, Mar 27, 2020, 1:59 AM UTC

specialist wrote: post #303

jacobolus wrote: post #205

Earlier quoted context omitted.

Here in Safari, Gmail is not only 10x buggier than it used to be before the redesign, it also uses at least 10x more client-side resources (CPU, network, ...). A handful of open Gmail tabs single-handedly use more CPU over here than hundreds of other web pages open simultaneously, including plenty of heavyweight app-style pages. It’s hard to escape the conclusion that Google’s front-end development process is complet…

I recently learned about Superhuman. Via the Acquired podcast. Not a recommendation; I haven't used Superhuman. But I remain astonished there's an apparently very successful startup who's entire effort is a "pro" webmail client for gmail. It would have never occurred to me to create a better webmail. As I reach my greybeard years, I'm increasingly aware that I've been doing everything wrong.