News for hackers. Stuff that matters.
Re:Chrome phasing out support for User-Agent by jorams on Wednesday March 25, 2020 @11:49AM (#22685693)
The weird thing about this is that the only company I've seen doing problematic user-agent handling in recent years is Google themselves. They have released several products as Chrome-only, which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent. Same with their search pages, which on mobile were very bad in every non-Chrome browser purely based on user agent sniffing.
Re:Chrome phasing out support for User-Agent by currysausage on Wednesday March 25, 2020 @12:42PM (#22686259)
If you have the new Chromium-based Edge ("Edgium") installed: the compatibility list at edge://compat/useragent is really interesting.

Edgium pretends to be Chrome towards Gmail, Google Play, YouTube, and lots of non-Google services; on the other hand, it pretends to be Classic Edge towards many streaming services (HBO Now, DAZN, etc.) because it supports PlayReady DRM, which Chrome doesn't.

[Edit] Here is the full list: https://pastebin.com/YURq1BR1

Re:Chrome phasing out support for User-Agent by ShamelessC on Wednesday March 25, 2020 @02:36PM (#22687202)
This is off topic but do you know why Edge is the only browser to support DRM for streaming? Or is that incorrect?

I see lots of people who have to use edge on order to get 4k content from Netflix; presumably because of the DRM issues.

Re:Chrome phasing out support for User-Agent by jgunsch on Wednesday March 25, 2020 @04:38PM (#22688300)
Other browsers support DRM too, but with different tradeoffs.

Chrome uses Widevine, but one of Chrome's philosophies is that you should be able to wipe a Chrome install, reinstall Chrome, and have no trace that before/after are the same person. That means no leveraging machine-specific hardware details that would persist across installs. "Software-only DRM", essentially.

Edge on Windows (and Safari on OSX) are able to leverage more hardware-specific functionality --- which from a DRM perspective are considered "more secure", but the tradeoff is a reduction of end-user anonymity (i.e. if private keys baked into a hardware TPM are involved).

Last I checked, Chrome/Firefox were capped at 720p content, Safari/Edge at 1080p, though it looks like Edge is now able to stream 4k.

Re:Chrome phasing out support for User-Agent by tryptophan on Wednesday March 25, 2020 @05:17PM (#22688608)
Its absurd that paying customers get a worse experience than just using the piratebay.
Re:Chrome phasing out support for User-Agent by recursive on Wednesday March 25, 2020 @05:40PM (#22688756)
Last time I used piratebay, I saw a lot of porn and malware/scam ads. I had to find and install a torrent client. Then I had to make sure I was downloading a movie that had enough seeders. And then I couldn't watch the movie until (and if) the download finished.

When I use netflix, I have a much better experience.

Re:Chrome phasing out support for User-Agent by olyjohn on Wednesday March 25, 2020 @05:54PM (#22688842)
I know this is all anecdotal, but last time I used a torrent site, I found the movie immediately and it pulled the whole thing down in under 3 minutes. Could be that it was a newer movie and pretty popular. I do see a lot of older stuff that's not being seeded much anymore.
Re:Chrome phasing out support for User-Agent by heavyset_go on Wednesday March 25, 2020 @07:12PM (#22689305)
> When I use netflix, I have a much better experience.

If you're on Linux, you won't be able to stream at 1080p, let alone 4k. Netflix even went out of their way to disable workarounds that users developed.

Re:Chrome phasing out support for User-Agent by recursive on Wednesday March 25, 2020 @07:16PM (#22689335)
1) I'm not on Linux. 2) I'd rather have the convenience of streaming at all than the best possible resolution.

I don't know what the resolution of my TV is, but I highly doubt it's over 1080p, if that.

Re:Chrome phasing out support for User-Agent by heavyset_go on Wednesday March 25, 2020 @07:20PM (#22689362)
Streaming above 720p also doesn't work via Firefox on any operating system.
Re:Chrome phasing out support for User-Agent by SturgeonsLaw on Thursday March 26, 2020 @07:48AM (#22692554)
According to the test pattern videos I'm getting 1080p in Firefox on Windows
Re:Chrome phasing out support for User-Agent by AnssiH on Thursday March 26, 2020 @01:33PM (#22695886)
Try "actual" content videos. You can press ctrl+alt+shift+D to open a debug overlay that shows the playback resolution.

The actual DRM limitations also vary by content (and region) - with some titles I get 720p on Linux while some other titles are limited to SD, while I get 1080p on Windows Edge on those same titles.

Re:Chrome phasing out support for User-Agent by Macha on Thursday March 26, 2020 @12:16PM (#22695081)
They may not have the same DRM restrictions as actual content? It's not that Firefox is not technically capable of rendering the videos, it's that it doesn't give the DRM the control that Netflix and rightholders want to require in exchange.
Re:Chrome phasing out support for User-Agent by rubin55 on Thursday March 26, 2020 @07:02AM (#22692334)
Source?
Re:Chrome phasing out support for User-Agent by AnssiH on Thursday March 26, 2020 @01:33PM (#22695893)
https://help.netflix.com/en/node/23931

> Mozilla Firefox up to 720p

Re:Chrome phasing out support for User-Agent by leppr on Wednesday March 25, 2020 @10:06PM (#22690249)
Some torrent clients support sequential downloading, which will be equivalent to streaming with most video formats. And obviously there's uBlock for the ads.

DRM on streaming and BluRays made it so that any usage outside basic consumption on prescribed devices is better served by illegal means.

Re:Chrome phasing out support for User-Agent by shitlord on Wednesday March 25, 2020 @08:11PM (#22689712)
You can have a similar experience with a private tracker and a seedbox. The content is curated (no malware), there's a larger selection, the quality is sometimes higher, and peers generally have better connections.

After you pick your torrent, it takes the seedbox a few seconds to download the content. Then you can stream your download using emby, vlc over http, or whatever you prefer.

Re:Chrome phasing out support for User-Agent by chii on Wednesday March 25, 2020 @05:45PM (#22688788)
You obviously haven't tried popcorntime.
Re:Chrome phasing out support for User-Agent by crucialfelix on Thursday March 26, 2020 @06:30AM (#22692179)
Used it once, cost me €840.

With torrents you can get a film in minutes. With popcorn you are exposed the entire time you watch the film.

In Germany they monitor peer connections and send a payment demanding an out of court settlement. After two years they escalate to a court appearance in a remote town. If you don't show, you lose and they turn it over to debt collection.

But I have to say Birdman was a great film.

Re:Chrome phasing out support for User-Agent by tjpnz on Thursday March 26, 2020 @07:57AM (#22692608)
This is exactly why I use a VPN. Last thing anyone needs is to be inconvenienced by BS laws bought buy special interests.
Re:Chrome phasing out support for User-Agent by mcdevilkiller on Wednesday March 25, 2020 @06:08PM (#22688943)
One of the best solutions out there.
Re:Chrome phasing out support for User-Agent by jensvdh on Wednesday March 25, 2020 @09:12PM (#22690002)
Which is illegal.
Re:Chrome phasing out support for User-Agent by oauea on Wednesday March 25, 2020 @09:58PM (#22690224)
And torrents (of copyrighted content) aren't? You're completely missing the point of this thread.
Re:Chrome phasing out support for User-Agent by nmz on Thursday March 26, 2020 @01:50PM (#22696055)
That's kind of the point, the illegal solution is better than the legal one.
Re:Chrome phasing out support for User-Agent by mixmastamyk on Thursday March 26, 2020 @03:49AM (#22691411)
Netflix doesn’t have most stuff.
Re:Chrome phasing out support for User-Agent by searchableguy on Thursday March 26, 2020 @01:19AM (#22690908)
You can use webtorrent - https://webtorrent.io/
Re:Chrome phasing out support for User-Agent by cerberusss on Thursday March 26, 2020 @05:12AM (#22691750)
I don't know this technology, but I'd really recommend using a VPN that provides a SOCKS proxy for your Bittorrent connections. Otherwise you're just announcing your IP address related to your torrent activities to the whole world.
Re:Chrome phasing out support for User-Agent by gerdesj on Wednesday March 25, 2020 @09:21PM (#22690053)
"Last time I used piratebay, I saw a lot of porn"

Why did you use piratebay unless that was your goal?

Re:Chrome phasing out support for User-Agent by besieged on Wednesday March 25, 2020 @11:58PM (#22690686)
I don't live in Europe but I canceled my Netflix the minute I learned that Reed Hastings is taking advantage of the coronavirus situation to increase Netflix's bottom line by limiting streaming quality to everyone in Europe after one phone call with a French politician.

There are plenty of torrent streaming and download clients that work just as well and are just as convenient as Netflix, without needing to rely on a central authority.

Re:Chrome phasing out support for User-Agent by neodymiumphish on Wednesday March 25, 2020 @11:19PM (#22690550)
Wait til you see how amazing the experience can be with Usenets...
Re:Chrome phasing out support for User-Agent by leadingthenet on Thursday March 26, 2020 @03:16AM (#22691299)
How do I get into using Usenet?
Re:Chrome phasing out support for User-Agent by lordfrikk on Thursday March 26, 2020 @04:59AM (#22691684)
You need: 1. Usenet provider (this allows you to download the links) and Usenet indexer (this allows you to search for content you want because files like movies usually have obfuscated filenames). Example of the former is Frugal Usenet, example of the latter is Drunken Slug (free-ish) or DogNZB (paid). One of the many things you need to watch out for with providers is retention, the length of time they keep the files so you can download them. In general, the older content you find on the indexer, the less likely it's still going to be available. The downloading itself can be done in an automated way (for example with Sonarr and the like) or kind-of manual with tools like SABnzbd.
Re:Chrome phasing out support for User-Agent by leadingthenet on Thursday March 26, 2020 @09:09AM (#22693166)
Thanks a lot!
Re:Chrome phasing out support for User-Agent by CobrastanJorji on Thursday March 26, 2020 @11:06AM (#22694232)
Not absurd so much as a major reason why the piratebay exists.
Re:Chrome phasing out support for User-Agent by matt-attack on Thursday March 26, 2020 @07:57AM (#22692603)
> one of Chrome's philosophies is that you should be able to wipe a Chrome install, reinstall Chrome, and have no trace that before/after are the same person.

Why would that be their philosophy? It sounds like some kind of privacy-motivated idea which seems contrary to Google’s typical philosophy. Or is it more about portability?

Re:Chrome phasing out support for User-Agent by Polylactic_acid on Wednesday March 25, 2020 @11:14PM (#22690521)
So any user on Edge can be hardware fingerprinted easily? I can see why other browsers stay far away.
Re:Chrome phasing out support for User-Agent by MaxBarraclough on Saturday March 28, 2020 @10:19AM (#22711269)
That's a good question. Is there anything to stop a disreputable advertiser/tracker hijacking the EME DRM scheme for tracking?

The evercookie project doesn't appear to leverage EME, for what that's worth. https://samy.pl/evercookie/

Re:Chrome phasing out support for User-Agent by jrandm on Wednesday March 25, 2020 @02:46PM (#22687289)
I am not sure about Edge specifically, but as someone who tries to use mostly open source software: Digital Rights Management (DRM) requirements often directly conflict with licensing related to open source software.
Re:Chrome phasing out support for User-Agent by colde on Wednesday March 25, 2020 @02:49PM (#22687312)
Not the only browser to support DRM. But the only browser to support PlayReady on Windows, which brings added security compared to what Widevine offers on Windows.

Another popular choice for high quality is Safari on macOS because it implements Apple's FairPlay.

Re:Chrome phasing out support for User-Agent by Wowfunhappy on Wednesday March 25, 2020 @04:39PM (#22688309)
Wait, Netflix et al use FairPlay in Safari on macOS?

I'm surprised, because Fairplay is publicly crackable.

Re:Chrome phasing out support for User-Agent by Lammy on Wednesday March 25, 2020 @05:01PM (#22688479)
So is WideVine.
Re:Chrome phasing out support for User-Agent by Wowfunhappy on Wednesday March 25, 2020 @05:14PM (#22688586)
It is?! The only public way to decrypt that which I'm aware of stopped working 15 years ago.
Re:Chrome phasing out support for User-Agent by voltagex_ on Wednesday March 25, 2020 @08:16PM (#22689749)
If you still see pirated copies of shows marked with WEB-DL (rather than Webrip), there's a way of decrypting the content directly. I really doubt the methods that are used are public, though.
Re:Chrome phasing out support for User-Agent by Polylactic_acid on Wednesday March 25, 2020 @11:16PM (#22690538)
*Added security for the remote server but massively reduced security for the end users computer.
Re:Chrome phasing out support for User-Agent by kbumsik on Wednesday March 25, 2020 @11:37PM (#22690621)
Any source?
Re:Chrome phasing out support for User-Agent by Polylactic_acid on Thursday March 26, 2020 @12:39AM (#22690807)
It allows websites to run arbitrary code blobs which interact with a hardware backdoor in your CPU with a higher permission level than the OS. With the multiple exploits that have been found in intel cpus and the Management Engine itself there is no way you should be letting any website do that.
Re:Chrome phasing out support for User-Agent by babypuncher on Wednesday March 25, 2020 @04:10PM (#22688071)
Other browsers support Widevine which is by far the more popular DRM scheme.
Re:Chrome phasing out support for User-Agent by 8K832d7tNmiQ on Wednesday March 25, 2020 @02:46PM (#22687288)
Simply because Netflix uses Playready DRM for 4k streaming, which is even harder to bypass and requires WinRT API (?) to even able to use the recent version.

Currently only Microsoft itself even try to implement it on their own Chromium-based browser.

Re:Chrome phasing out support for User-Agent by vbezhenar on Wednesday March 25, 2020 @04:07PM (#22688049)
There are different kinds of DRM. Streaming websites allow different quality for different kinds of DRM. E.g. they allow best quality only for best protected DRM (which should use encryption all the way from Netflix webserver to your display). There's software DRM (decrypting stream inside proprietary blob) which is considered weaker, so you'll receive acceptable quality in Chrome. I don't know why Chrome did not implement the most secure DRM. Hopefully Microsoft will contribute their patches back.
Re:Chrome phasing out support for User-Agent by franga2000 on Thursday March 26, 2020 @08:49AM (#22692990)
I'm guessing Edge specifically also has to do that not only because of chrome==good queries, but also because of many, many edge==bad queries.
Re:Chrome phasing out support for User-Agent by currysausage on Thursday March 26, 2020 @09:26AM (#22693332)
This is why Edgium calls itself “Edg”, not “Edge”, in the UA string.
Re:Chrome phasing out support for User-Agent by ygra on Thursday March 26, 2020 @02:34AM (#22691125)
For me that list is empty. Edge-dev 82. Maybe I'm doing something wrong?
Re:Chrome phasing out support for User-Agent by gsnedders on Thursday March 26, 2020 @11:41AM (#22694645)
IIRC, Edge-dev has an empty list. On stable and beta get the list.
Re:Chrome phasing out support for User-Agent by currysausage on Thursday March 26, 2020 @01:01PM (#22695567)
Which makes sense, given that the list could change anytime (ideally, it wouldn’t even exist) and no developer should rely on Edgium identifying as Chrome or Classic Edge.
Re:Chrome phasing out support for User-Agent by rovek on Wednesday March 25, 2020 @12:16PM (#22685994)
I had been thinking recently as I've been using Firefox more that Google maps had got clunky. With a little fiddling prompted by your comment, it turns out Maps sniffs specifically to reduce fluid animations on Firefox (and probably some other browsers).
Re:Chrome phasing out support for User-Agent by the_pwner224 on Wednesday March 25, 2020 @01:23PM (#22686610)
Thnak you, this had been bugging me for a while. Looks like I'll need to permanently install a UA-switcher extension.

Yesterday I saw a HN comment saying you can add the (?|&)disable_polymer=1 parameter to the end of YouTube URLs to make the site much faster - iirc Polymer is extremely slow on Firefox only. This extension was also linked: https://addons.mozilla.org/en-US/firefox/addon/disable-polym...

Unfortunately there doesn't seem to be any workaround for ReCaptcha on FF. I generally end up opening the website in the GNOME or KDE (Falkon) browser which use something like WebKit/Blink - there it works on the first try every time.

Re:Chrome phasing out support for User-Agent by chipperyman573 on Wednesday March 25, 2020 @01:51PM (#22686864)
Some advice about ReCaptcha, the audio test is way easier and usually only makes you do it once or twice (as opposed to the 5-10 times you usually have to do when you have disabled tracking). Sometimes it will say you aren't eligible or something, just refresh the page and it will let you try again.
Re:Chrome phasing out support for User-Agent by Larrikin on Wednesday March 25, 2020 @02:58PM (#22687398)
The audio test can also be defeated by ML extensions that do it for you automatically
Re:Chrome phasing out support for User-Agent by philwelch on Wednesday March 25, 2020 @03:04PM (#22687442)
Hey wait a minute!
Re:Chrome phasing out support for User-Agent by searchableguy on Thursday March 26, 2020 @01:25AM (#22690927)
I wonder what will be the point of these captchas if most people started avoiding them by installing extensions. If the end goal is to put significant resource constraint on the scrapper or bots, you can do it quite easily by running something to short the usage up for a few seconds if you think someone is suspicious.
Re:Chrome phasing out support for User-Agent by bluGill on Wednesday March 25, 2020 @04:10PM (#22688069)
I just use the contact site to send them a note to cut it out. There are better ways to prevent spam. Like my password that I just entered in the latest case. I'll go elsewhere in the next, they have competitors that won't be that different in price and easier to use.
Re:Chrome phasing out support for User-Agent by numpad0 on Wednesday March 25, 2020 @12:29PM (#22686126)
I had been having an issue with Google Sheets and Firefox that the app decides to change row height randomly.

On Firefox only. Obvious solution to which being...

Re:Chrome phasing out support for User-Agent by mmis1000 on Wednesday March 25, 2020 @01:00PM (#22686429)
It actually insert a line break on enter, make it invisible and can't be deleted only on firefox.

Pretend firefox as chrome makes it works perfectly.

They lock the community thread and fixed that after several days I found the finding and post it there.

Shame on you, google.

Re:Chrome phasing out support for User-Agent by llbeansandrice on Wednesday March 25, 2020 @01:47PM (#22686834)
Oh my god. I knew it was inserting a line break when I hit enter but I didn't realize it was a FF only issue. gdi Google.
Re:Chrome phasing out support for User-Agent by _jal on Wednesday March 25, 2020 @02:32PM (#22687167)
Not the first time. For some reason Google really doesn't like people talking about the games they play with browser detection.

(That's not snark - I really don't get it. They don't appear to mind people talking negatively about a lot of other stuff they get up to. Maybe lingering antitrust fears from the 90's MS suit?)

Re:Chrome phasing out support for User-Agent by ksec on Wednesday March 25, 2020 @07:08PM (#22689286)
I mean we are in 2020, none of this should be news, but then a lot of people only discovered them now. They have been doing this since early 2010s.

They have been a hypocrite from the start, but people got too consumed with its free Gmail, RSS Reader along with its Do no Evil they decided to trust them blindly.

The current browser, and Web Tech scenario is pretty much Google's way or the highway. So I am glad Apple kept Safari as the only option on Apple platform. Not allowing them to dictate everything.

Re:Chrome phasing out support for User-Agent by cpeterso on Thursday March 26, 2020 @01:14AM (#22690896)
I reported this as a Firefox bug [1] in 2015. Google fixed it on their side in 2017, but it’s back. :(

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1205573

Re:Chrome phasing out support for User-Agent by philwelch on Wednesday March 25, 2020 @03:07PM (#22687477)
Companies are afraid of legal liability much more than they’re afraid of bad PR.
Re:Chrome phasing out support for User-Agent by NotSammyHagar on Wednesday March 25, 2020 @03:07PM (#22687475)
I was hitting that too! I wondered what I was doing. I kept getting these weird fields. That fucking sucks. I'd like someone to explain google's point of view about why this is happening? I do override user agent on some systems so random websites work.
Re:Chrome phasing out support for User-Agent by cozzyd on Wednesday March 25, 2020 @03:14PM (#22687568)
Indeed, I was wondering why sheets was so broken to always randomly insert line returns.
Re:Chrome phasing out support for User-Agent by lmpostor on Wednesday March 25, 2020 @02:23PM (#22687097)
Same... I've been played.
Re:Chrome phasing out support for User-Agent by nannal on Wednesday March 25, 2020 @02:16PM (#22687051)
really working hard to shove that poison apple down your throat.
Re:Chrome phasing out support for User-Agent by true_religion on Thursday March 26, 2020 @06:08AM (#22692073)
I wouldn’t really shame them on this one. Google docs and sheets uses contenteditable under the hood. Contenteditable isn’t specified or standardized anywhere and varies wildly between browsers, and sometimes between browser versions.
Re:Chrome phasing out support for User-Agent by r00fus on Wednesday March 25, 2020 @07:51PM (#22689587)
So even that workaround is being phased out with this UA support change?
Re:Chrome phasing out support for User-Agent by yingw787 on Wednesday March 25, 2020 @12:45PM (#22686281)
Oh wait...THAT might be the problem?? I've been having that issue too! I have to cut the cell content, delete the cell, and then paste the cell content back in in order for the row height to appear the same. It never even occurred to me to switch browsers, I thought it was an issue with Google Sheets.
Re:Chrome phasing out support for User-Agent by spand on Wednesday March 25, 2020 @01:00PM (#22686421)
Same except it stopped not long ago. Maybe they fixed it ?
Re:Chrome phasing out support for User-Agent by mmis1000 on Wednesday March 25, 2020 @01:27PM (#22686647)
https://support.google.com/docs/thread/18235069?hl=en

They do, I'm not sure that should be called as a 'fix' though.

Because it even works perfectly on firefox as long as you spoof your useragent to chrome.

Re:Chrome phasing out support for User-Agent by yingw787 on Wednesday March 25, 2020 @01:06PM (#22686467)
Maybe. Still not switching away from Firefox though. I have Chrome installed because WebRTC is a lot better and teleconferencing needs have shot up recently, and because I lock my phone away in a Kitchen Safe and use 2FA with Authy the Chrome app, but Firefox is my daily driver :)
Re:Chrome phasing out support for User-Agent by yjftsjthsd-h on Wednesday March 25, 2020 @12:50PM (#22686328)
> Obvious solution to which being...

Installing an extension to spoof your user agent? Since we wouldn't want to reward Google being anti-competitive.

Re:Chrome phasing out support for User-Agent by freeopinion on Wednesday March 25, 2020 @05:23PM (#22688650)
Or... quit using buggy app?
Re:Chrome phasing out support for User-Agent by marakv2 on Wednesday March 25, 2020 @06:59PM (#22689251)
Except, that has been pointed out in the parent comments, it's not the application, it's a deliberate bug targeted towards a different browser(hence changing the user agent fixes it).
Re:Chrome phasing out support for User-Agent by isbjorn16 on Wednesday March 25, 2020 @09:59PM (#22690231)
There's a strong argument to be made here that the "buggy app" is Google Sheets.
Re:Chrome phasing out support for User-Agent by numpad0 on Wednesday March 25, 2020 @09:54PM (#22690205)
Except, there’s always the (Libre)Office!
Re:Chrome phasing out support for User-Agent by freeopinion on Monday March 30, 2020 @02:41PM (#22730862)
The browser is not the app I had in mind.
Re:Chrome phasing out support for User-Agent by lantius on Wednesday March 25, 2020 @02:34PM (#22687186)
What versions of Firefox and Chrome are you seeing different behavior in Google Maps? I get the same experience in Chrome 80 and Firefox 74 on OSX Catalina.
Re:Chrome phasing out support for User-Agent by skrebbel on Wednesday March 25, 2020 @03:22PM (#22687642)
Wow, that's proper evil.
Re:Chrome phasing out support for User-Agent by blntechie on Wednesday March 25, 2020 @01:47PM (#22686836)
Every single Google product is slower on Firefox and it’s hard to not call this malice and artificial. Many people check out Gmail and GMaps on Firefox and go back to Chrome because of their clunkiness on Firefox.
Re:Chrome phasing out support for User-Agent by mindcrime on Wednesday March 25, 2020 @02:47PM (#22687298)
"Google ain't done, till Firefox won't run"?
Re:Chrome phasing out support for User-Agent by ricktdotorg on Wednesday March 25, 2020 @02:20PM (#22687081)
> malice and artificial

are you actually asserting that Google is purposefully adding code/"tweaking" their web apps to run slowly on browsers other than Chrome?

do you have any evidence at all for this other than anecdotes about people experiencing Google web app clunkiness on Firefox?

Re:Chrome phasing out support for User-Agent by izolate on Wednesday March 25, 2020 @02:44PM (#22687267)
It could also be a passive, malicious de-prioritization of bugfixes for Firefox that would cause the same effect. It seems like this would be a more likely scenario.
Re:Chrome phasing out support for User-Agent by sudosysgen on Wednesday March 25, 2020 @03:06PM (#22687472)
I would believe that if changing the user agent or toggling some flags didn't fix it.
Re:Chrome phasing out support for User-Agent by ADefenestrator on Tuesday March 31, 2020 @09:59AM (#22737565)
Probably a lot of the other way around as well. Google employees likely use Chrome and Docs/Sheets heavily, so they get a rapid high-quality feedback loop with any bugs or performance issues affecting the Chrome devs and people around them.
Re:Chrome phasing out support for User-Agent by dijit on Wednesday March 25, 2020 @02:39PM (#22687231)
If there was direct evidence it would warrant its own post, so I think your comment has been made in bad faith since people are talking about their own experiences.

That said; if it's possible to measure firefox/chrome performance (with altered user-agents) it would make for a good blog post.

Re:Chrome phasing out support for User-Agent by adrianmonk on Wednesday March 25, 2020 @03:05PM (#22687455)
How is "hard to not call this malice and artificial" people talking about their own experiences?
Re:Chrome phasing out support for User-Agent by Talanes on Wednesday March 25, 2020 @03:38PM (#22687767)
The "hard not to call" portion takes it from the realm of objective fact and into subjective measure.
Re:Chrome phasing out support for User-Agent by adrianmonk on Wednesday March 25, 2020 @07:29PM (#22689414)
Huh, I guess "hard not to call" could be interpreted as a disclaimer or qualifier meaning "I can't prove this, and it's only my opinion".

However, I interpreted it differently, to basically mean that because of objective fact, of all the explanations you can think of, only one of them is defensible. In other words, it's similar to saying "admit it, this is the only reasonable conclusion".

Re:Chrome phasing out support for User-Agent by sjruckle on Monday March 30, 2020 @05:16PM (#22732371)
The original post had the phrase "hard to not call" rather than "hard not to call".

The meaning is inverted by swapping the "to" and "not".

Re:Chrome phasing out support for User-Agent by MikusR on Wednesday March 25, 2020 @03:16PM (#22687583)
Re:Chrome phasing out support for User-Agent by Wowfunhappy on Thursday March 26, 2020 @10:57AM (#22694137)
As a semi-counter:

Slack, Skype, and Zoom video calls don't work in Firefox, even though WebRTC is an open standard. But Google Hangouts works perfectly.

I'm loath to give Google credit for something that ought to be standard practice, but of the major (key word) free video conferencing options, they seem to be the only one that's Firefox-compatible.

Re:Chrome phasing out support for User-Agent by iso1631 on Wednesday March 25, 2020 @02:12PM (#22687018)
I try out google products on occasion and find them rubbish compared with alternatives, so go back to non-google products.
Re:Chrome phasing out support for User-Agent by michaelmrose on Wednesday March 25, 2020 @03:12PM (#22687539)
Regarding google properties what do you prefer and why?
Re:Chrome phasing out support for User-Agent by iso1631 on Wednesday March 25, 2020 @03:20PM (#22687619)
Google maps does tend to be better than OSM when it comes to route finding, I use !gm when I want routing. On my phone I use apple maps though.

Gmail is painful compared with OWA (work) and zoho (home), I stopped using my gmail account for new stuff about a year ago.

Re:Chrome phasing out support for User-Agent by michaelmrose on Wednesday March 25, 2020 @03:39PM (#22687778)
I prefer mu4e (mu for email) although ultimately I'm still using my gmail account just with another interface. I like the idea of ultimately just setting up a mail server but realistically its really really hard to switch everything at once when you have a lot of existing accounts so I'll probably be maintaining a gmail account forever.

I'm trying maps.me because unlike google it does offline walking directions but I haven't used it enough.

I really want to like duck duck go but it feels like google still provides better results.

Re:Chrome phasing out support for User-Agent by iso1631 on Thursday March 26, 2020 @08:30AM (#22692839)
> I really want to like duck duck go but it feels like google still provides better results.

I find I get better results with ddg than google. YMMV I guess.

Re:Chrome phasing out support for User-Agent by namibj on Thursday March 26, 2020 @01:07AM (#22690882)
I us brouter for my usecase of foot/bike nav in hilly terrain. Using OSM And for the UI.
Re:Chrome phasing out support for User-Agent by arendtio on Wednesday March 25, 2020 @03:11PM (#22687532)
In fact, just this week I thought about why Google doesn't make its mobile maps website fast again. It is such a pain to use it on older phones and I totally don't get, why it has to be that slow (doesn't matter if chrome or Firefox).
Re:Chrome phasing out support for User-Agent by jacobolus on Wednesday March 25, 2020 @06:11PM (#22688965)
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 completely incompetent and has no respect for customers’ battery or bandwidth.

Re:Chrome phasing out support for User-Agent by specialist on Thursday March 26, 2020 @10:18AM (#22693785)
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.

Re:Chrome phasing out support for User-Agent by elevenoh on Thursday March 26, 2020 @09:59PM (#22699898)
Superhuman looks nice.

>I'm increasingly aware that I've been doing everything wrong.

Any theme to this?

Re:Chrome phasing out support for User-Agent by basscomm on Wednesday March 25, 2020 @02:38PM (#22687220)
> The weird thing about this is that the only company I've seen doing problematic user-agent handling in recent years is Google themselves.

I frequently consume web articles with a combination of newsboat + Lynx, and it's astounding how many websites throw up HTTP 403 messages when I try to open a link. They're obviously sniffing my user agent because if I blank out the string (more accurately, just the 'libwww-FM' part, then the site will show me the correct page.

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.

Re:Chrome phasing out support for User-Agent by jedberg on Wednesday March 25, 2020 @02:47PM (#22687302)
> 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 building a legit bot would know to fake the agent string.

The script kiddies would just go away. It drastically reduced bot traffic when we did that. Obviously some of the malicious bot writers know to fake their agent string too, and we had other mitigations for that.

But sometimes the simplest solutions solve the majority of issues.

Re:Chrome phasing out support for User-Agent by adwww on Wednesday March 25, 2020 @03:28PM (#22687693)
> Any legit person building a legit bot would know to fake the agent string.

What, that's totally backwards. Anyone using a bot to do things that might get blocked by publishers fakes the string, legit purposes should really show who / what they are.

Re:Chrome phasing out support for User-Agent by xiongchiamiov on Wednesday March 25, 2020 @05:47PM (#22688800)
It actually is encouraging people to have useful user agents. By default most people end up with a user agent that's something like "libcurl version foo.bar.baz", which isn't actually a description of who or what they are; given the prevalence of curl, it really just tells you that it's a program that uses http.
Re:Chrome phasing out support for User-Agent by jedberg on Wednesday March 25, 2020 @03:32PM (#22687713)
We only blocked agent strings with "lib" in them. You could change the agent to "WebScraperSupreme.com" and it would have been fine (and in fact some people did do that).
Re:Chrome phasing out support for User-Agent by NotSammyHagar on Wednesday March 25, 2020 @03:11PM (#22687534)
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.
Re:Chrome phasing out support for User-Agent by naasking on Thursday March 26, 2020 @01:13PM (#22695703)
Hard to argue with the economics of that mitigation though. The abuse:legitimate use ratio is probably pretty high. Getting rid of user agent strings will bring back the scaling problems, as they should probably be addressed directly.
Re:Chrome phasing out support for User-Agent by thaumasiotes on Wednesday March 25, 2020 @12:21PM (#22686051)
> They have released several products as Chrome-only, which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent.

This seems like a pretty good reason in itself why they might be interested in phasing out User-Agents.

Re:Chrome phasing out support for User-Agent by heavyset_go on Wednesday March 25, 2020 @12:37PM (#22686198)
It's the exact opposite. Without User-Agents, sites need to depend on feature detection, and closing the feature discrepancy between Chrome and other browsers is more complicated than just spoofing your UA to get Google to serve you functioning versions of their products.
Re:Chrome phasing out support for User-Agent by thaumasiotes on Wednesday March 25, 2020 @12:59PM (#22686419)
I don't quite follow your comment.

I'm saying, the hypothetical flow from Google is:

1. Our Chrome detection relies on the User-Agent header.

2. But people can just lie in the User-Agent header.

3. Let's get rid of it and use something that's harder to lie about.

Closing any feature discrepancy isn't a goal here, as far as I can see. The whole point is to lie to the user that a feature discrepancy exists when it doesn't.

You can make the argument that Google is free to do their browser detection however they want (and therefore doesn't need to solve this problem by eliminating User-Agents), but this is still an obvious example of the User-Agent header causing problems for Google.

Re:Chrome phasing out support for User-Agent by developer2 on Wednesday March 25, 2020 @01:30PM (#22686678)
I interpreted your parent's comment differently; namely, if Google's developers can't do User-Agent detection, then internally even they will have to improve how they develop (eg. via feature detection), making their products more compatible with other browsers.

Many people assume Google, as an upper-level business decision, purposely makes products work better on Chrome in order to vendor-lock users to the browser. Maybe that's true; or maybe it's developers being lazy and using User-Agent detection. Removing their ability to do so might actually improve cross-browser compatibility of Google products.

Re:Chrome phasing out support for User-Agent by jlokier on Thursday March 26, 2020 @05:17AM (#22691774)
Well, the GP is saying that the sites work perfectly fine when they just change the User-Agent.

So Google developers don't need to improve feature detection - that part is working fine already.

Re:Chrome phasing out support for User-Agent by sitkack on Wednesday March 25, 2020 @01:05PM (#22686460)
This is going to end up being the IE of Google, funny that it is also a browser (Chrome).
Re:Chrome phasing out support for User-Agent by myko on Wednesday March 25, 2020 @08:13PM (#22689730)
That's the opposite of what is happening though
Re:Chrome phasing out support for User-Agent by sitkack on Thursday March 26, 2020 @08:49AM (#22692983)
We are talking about the same object in two entirely different contexts.
Re:Chrome phasing out support for User-Agent by eh78ssxv2f on Wednesday March 25, 2020 @11:55AM (#22685752)
Google is probably so big that we might as well consider Chrome and rest of the Google as separate entities.
Re:Chrome phasing out support for User-Agent by untog on Wednesday March 25, 2020 @12:25PM (#22686085)
You can see Chrome devrels on Twitter expressing disappointment with Chrome-only web sites, saying that they raise the issue internally. Of course we have no visibility into what happens after that, but it's an indicator that you're right.
Re:Chrome phasing out support for User-Agent by klodolph on Wednesday March 25, 2020 @12:44PM (#22686272)
I’m guessing all of Google’s internal apps are only tested on Chrome, with plenty of Chrome extensions, which means that all of the developers have to use Chrome to make the tools work, and at that point, switching back and forth between different browsers is a pain so none of the other browsers get the love they deserve.

The attitude of “it works on Chrome, I don’t care about anything else” is fairly widespread anyway. Just to stem the tide a little bit I’ve been developing on Firefox and Safari first, and then checking Chrome last.

I got bitten before when I made a browser game, and then noticed that it was all sorts of broken on Edge, even though Edge supposedly had all the features I needed. It turns out that Edge did have all the features I needed, but I had accidentally used a bunch of Chrome features I didn’t need. The easy way out is to turn things off when I detect Edge. The hard way is to find all the broken parts and fix them. So nowadays, I don’t do any web development in Chrome.

Re:Chrome phasing out support for User-Agent by Tyr42 on Wednesday March 25, 2020 @12:50PM (#22686335)
At least in my part of the googleverse, we have automated tests running in all the browsers (even ie11).

But I'll admit I will also poke around outside of the tests, and I'll usually only be doing that in chrome, unless I've had a bug report about firefox in particular. And I'll only really open up Safari when I'm testing VoiceOver. ChromeVox just isn't good enough.

Re:Chrome phasing out support for User-Agent by klodolph on Wednesday March 25, 2020 @01:03PM (#22686451)
Oh, I’m sure there are automated tests. But if you have 50,000 developers using Google Docs in Chrome, they’re gonna submit some high-quality bug reports internally, whenever it breaks.
Re:Chrome phasing out support for User-Agent by dhimes on Wednesday March 25, 2020 @12:57PM (#22686392)
Please, yes, develop on Firefox first. We all need to promise to do this.
Re:Chrome phasing out support for User-Agent by JohnTHaller on Wednesday March 25, 2020 @02:08PM (#22686989)
Considering that there's been an internal and external bug filed about the US states not being in alphabetical order on contacts.google.com for years, making it impossible to type 'new y' to get New York, I don't think raising it as an issue will help much.
Re:Chrome phasing out support for User-Agent by blitmap on Wednesday March 25, 2020 @11:59AM (#22685802)
I hear what you're saying, but they pay people enough to follow a potential company-wide policy: Don't f-ck with user agents!
Re:Chrome phasing out support for User-Agent by daveFNbuck on Wednesday March 25, 2020 @01:18PM (#22686565)
It's easier to change the thing you're in charge of than it is to make a new company-wide policy.
Re:Chrome phasing out support for User-Agent by liveoneggs on Wednesday March 25, 2020 @12:28PM (#22686116)
this is exactly the opposite of what we should do when they degrade experiences of competing browsers!
Re:Chrome phasing out support for User-Agent by tmpz22 on Wednesday March 25, 2020 @12:21PM (#22686046)
I’ve started seeing alphabet employees use this as an excuse: “oh that happened on team x there’s nothing I could’ve done”. On small technical issues the excuse is fine - on large moral issues it does not work.
Re:Chrome phasing out support for User-Agent by dtech on Wednesday March 25, 2020 @12:28PM (#22686115)
In large corporations politics are abound. If the Chrome division cannot get other divisions to behave through other means, this is fine.

You can see that they should have fought harder and escalated, but issues like this are probably not the ones most upper-middle management want to potentially damage their career for.

Re:Chrome phasing out support for User-Agent by saagarjha on Wednesday March 25, 2020 @01:40PM (#22686771)
It's not fine, but it's certainly to be expected.
Re:Chrome phasing out support for User-Agent by asveikau on Wednesday March 25, 2020 @02:41PM (#22687245)
A fair number of websites will still block perfectly working features based on what OS you use.

Some examples I've seen using the latest Firefox on *BSD:

Facebook won't let you publish or edit a Note (not a normal post, the builtin Notes app). I think earlier they wouldn't play videos but they might have fixed that.

Chase Bank won't let you log in. Gives you a mobile-looking UI which tells you to upgrade to the latest Chrome or Firefox.

In these cases if you lie and say you're using Linux or Windows it works flawlessly.

Re:Chrome phasing out support for User-Agent by eredengrin on Thursday March 26, 2020 @01:09AM (#22690886)
In addition to these, I've also noticed outlook365 (use it for accessing work email) gives a very minimal interface to the point of being nearly unusable with a FreeBSD user agent. Switch to a more popular one and I get full functionality.
Re:Chrome phasing out support for User-Agent by ksec on Wednesday March 25, 2020 @07:22PM (#22689373)
I am guessing Banks only test their site against popular OS and Browser for security reasons.
Re:Chrome phasing out support for User-Agent by whoisthemachine on Wednesday March 25, 2020 @11:04PM (#22690479)
It's usually just that the company doesn't want to have to deal with potential support calls that come in about their website not working on x os in x browser, so they do the bare minimum to disable it - then if a user complains about it not working, they can plausibly deny supporting the os/browser configuration.
Re:Chrome phasing out support for User-Agent by asveikau on Wednesday March 25, 2020 @11:15PM (#22690528)
This takes more effort than letting it just work. People running an OS more obscure than Linux are not the type that are going to call asking for support. We are used to supporting ourselves.

Did I mention it's the same code as a working configuration?

I think it's more likely somebody did not know how to properly parse user-agent and they blocked more than they intended to.

Re:Chrome phasing out support for User-Agent by asveikau on Wednesday March 25, 2020 @08:18PM (#22689759)
Ok then, don't tell all the other financial institutions I use FreeBSD then, they are all letting me through without issue.

It sounds a lot like you are making excuses for them and bad/lazy/poorly thought out code.

Re:Chrome phasing out support for User-Agent by Dylan16807 on Wednesday March 25, 2020 @08:15PM (#22689744)
I think you mean their broken idea of what a security reason is. Banks are generally really bad at actual web and mobile security.
Re:Chrome phasing out support for User-Agent by AndrewKemendo on Wednesday March 25, 2020 @01:08PM (#22686481)
I would guess they have built something into chrome that gets even more data that isn't user-agent based.

UA has a lot of limitations and is fairly easy to work around giving data to for power users. I would imagine Google didn't want to keep playing around with that.

Re:Chrome phasing out support for User-Agent by josefx on Thursday March 26, 2020 @07:59AM (#22692625)
> I would guess they have built something into chrome that gets even more data that isn't user-agent based.

Chrome includes a unique installation id in requests to Google owned domains. They don't need any cookies or user agents to guess who you are and best of all they don't have to share that information with their competition.

https://news.ycombinator.com/item?id=22236106

Re:Chrome phasing out support for User-Agent by rozab on Wednesday March 25, 2020 @12:50PM (#22686337)
I know Netflix used to block the Firefox on Linux user agent for no reason
Re:Chrome phasing out support for User-Agent by jeroenhd on Wednesday March 25, 2020 @01:09PM (#22686485)
Not for a technical reason, but they had a reason: they provided no support or guarantee that Netflix would ever work on Linux + FF (Ubuntu + Chrome was guaranteed) and they didn't want any support calls for something that they wouldn't help people with anyway.

A lot of stuff gets blocked for this reason. The company doesn't want you calling them because HD video doesn't work on Firefox even though you pay for HD quality, they do not test or guarantee Firefox compatibility in the slightest and yet they have to talk to an angry customer now. It makes business sense to redirect people to supported use cases when you know your product probably won't work as intended otherwise.

You don't have to agree with the decision (and you can always cancel your membership if you do) but they had their reasons.

Re:Chrome phasing out support for User-Agent by ric2b on Sunday March 29, 2020 @12:27PM (#22720246)
Why not a banner saying that it's not supported and may have issues? You might lose customers if you simply block them from using it at all.
Re:Chrome phasing out support for User-Agent by _eht on Wednesday March 25, 2020 @03:08PM (#22687500)
> and they didn't want any support calls for something that they wouldn't help people with anyway.

Even knowing what they were doing, I fielded at least two support requests asking what was going on. I can only hope I wasn’t the only one.

Now that everything plays nicely I just happen to have no interest in Netflix for other reasons...

Re:Chrome phasing out support for User-Agent by dhimes on Wednesday March 25, 2020 @05:22PM (#22688642)
Exactly. This is going to turn into a game of whack-a-mole whereby we need to load the latest firefox extension that tricks websites into thinking we're using Chrome.

Or we could build for Firefox. There's always that.

Re:Chrome phasing out support for User-Agent by fpoling on Wednesday March 25, 2020 @01:30PM (#22686674)
The things that replaces the user agent will still be enough to differentiate Chrome from Firefox and Safari.
Re:Chrome phasing out support for User-Agent by cdata on Thursday March 26, 2020 @12:45AM (#22690829)
Chrome team members are face-palming with the best of us whenever a Google product does backwards things like filtering based on user agent string.

Google isn't a singularity ️

Re:Chrome phasing out support for User-Agent by rocky1138 on Wednesday March 25, 2020 @12:43PM (#22686269)
Facebook also uses the user-agent string to determine which version of a site to send to someone. I installed a user-agent spoofer a while back and messenger.com would fail due to it every few refreshes (as evidenced by JS console).
Re:Chrome phasing out support for User-Agent by willvarfar on Thursday March 26, 2020 @09:05AM (#22693135)
To get Microsoft Teams to run in Chromium there used to be a user-agent hack to make it pretend to be Chrome. This was superseded by someone packaging up using Electron. And finally this has been superseded by Micrsoft themselves supporting Linux using something that looks and feels like Electron again.

So, basically, Microsoft using user-agent to detect Chrome....

Re:Chrome phasing out support for User-Agent by otabdeveloper2 on Thursday March 26, 2020 @11:03AM (#22694205)
> ...which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent.

Which is probably why Google wants to phase out the user agent.

For sure whatever Google invents to replace it will not be so easily circumvented.

Re:Chrome phasing out support for User-Agent by heavyset_go on Wednesday March 25, 2020 @12:32PM (#22686154)
Some Google properties are broken on Chromium, even.
Re:Chrome phasing out support for User-Agent by arendtio on Wednesday March 25, 2020 @03:08PM (#22687496)
Ikea does it too with some of their tools (just sucks).
Re:Chrome phasing out support for User-Agent by jaywalk on Wednesday March 25, 2020 @11:54AM (#22685737)
I'm sure Google won't build in some proprietary way for them to identify Chrome.

/s

Re:Chrome phasing out support for User-Agent by true_religion on Wednesday March 25, 2020 @12:31PM (#22686143)
I mean they already did. The goal is to replace user agent parsing with a simple field that says exactly what browser and version this is.
Re:Chrome phasing out support for User-Agent by ric2b on Sunday March 29, 2020 @12:30PM (#22720257)
You mean like a user-agent string?

Gee, I wonder how this is going to end: https://webaim.org/blog/user-agent-string-history/

Re:Chrome phasing out support for User-Agent by sergiotapia on Wednesday March 25, 2020 @02:09PM (#22687003)
"Oopsie" said Google to Firefox.