Live data from Hacker News

Chrome phasing out support for User-Agent

infoq.com

271–280 of 329 posts

Re: Chrome phasing out support for User-Agent

#271
post #169

Earlier quoted context omitted.

If your site doesn't use JS, you don't need features. Just use responsive HTML.

How do you handle browsers that render HTML differently?

Use different HTML that renders the same everywhere relevant

Re: Chrome phasing out support for User-Agent

#275

Earlier quoted context omitted.

Wait til you see how amazing the experience can be with Usenets...

How do I get into using Usenet?

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

#276

Earlier quoted context omitted.

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.

You can use webtorrent - https://webtorrent.io/

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

#277

Earlier quoted context omitted.

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.

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.…

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

#278

Good. User-agent strings are a mess. Here is an example of a user-agent string. Can you tell what browser this is? Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.27 Safari/525.13 How did they get so confusing? See: History of the browser user-agent string https://webaim.org/blog/user-agent-string-history/ Also, last year, Vivaldi switched to using a user-agent st…

Chrome 0.2 on Windows XP?

Re: Chrome phasing out support for User-Agent

#280
post #63

Earlier quoted context omitted.

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...

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.

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.
Post reply on HN