Live data from Hacker News

Guidance to developers affected by effort to block less secure browsers, apps

developers.googleblog.com

111–120 of 165 posts

Re: Guidance to developers affected by effort to block less secure browsers, apps

#111
post #7

Anti-trust action can't come fast enough.

Once upon a time Google would've been applauded for forcing people to improve their security. Like when they made https a ranking factor for sites and overnight forced all the laggards to move off http. Now, people just scream "monopoly" at everything google does, good or bad and boy is it getting tedious.

Explain to me how being forced to turn on Javascript or not use a text-based browser results in me having "improved security."

Re: Guidance to developers affected by effort to block less secure browsers, apps

#112
post #7

Earlier quoted context omitted.

Once upon a time Google would've been applauded for forcing people to improve their security. Like when they made https a ranking factor for sites and overnight forced all the laggards to move off http. Now, people just scream "monopoly" at everything google does, good or bad and boy is it getting tedious.

Explain to me how being forced to turn on Javascript or not use a text-based browser results in me having "improved security."

The reason Google is requiring you to have JavaScript enabled, potentially opening you up to running malicious code, is because they want to use feature detection to prevent people from using competitors' Google-unapproved browsers.

Re: Guidance to developers affected by effort to block less secure browsers, apps

#113

Earlier quoted context omitted.

Once upon a time Google had "don't be evil" in their corporate mission and people trusted them to act in good faith. Good old times.

They still do >And remember… don’t be evil, and if you see something that you think isn’t right – speak up! >Last updated September 25, 2020 src: https://abc.xyz/investor/other/google-code-of-conduct/

Before, it stated that the company must not be evil. Now, it is for the employees not to be evil somewhere in the end. In the meantime, if you are high up the management ladder, you can fuck the subordinates and get away with millions.

Re: Guidance to developers affected by effort to block less secure browsers, apps

#114

How does this mesh with their plans to deprecate User-Agent? https://9to5google.com/2020/01/14/google-deprecate-chrome-us...

It meshes nicely for Google, because they want to use feature detection to detect whether you're using a Google-approved browser and not a competitor's unapproved browser.

This is why they state that JavaScript must be enabled, because that's how they do feature detection:

> The browser must have JavaScript enabled.

Re: Guidance to developers affected by effort to block less secure browsers, apps

#117

This is a campaign against Lynx! > The browser must have JavaScript enabled. > You must confirm that your browser does not contain any of the following: > * Text-based browsers Once upon a time the internet was TCP with things like FTP, Email, Newsgroups, IRC and yes also HTTP (aka WWW). Now, the internet seems to be Google, Apple, Facebook aaand SEO. Hey, wait! There is a small shiny place!! Hackernews! :)

This is regarding man-in-the-middle attacks. There is not attack on Lynx. Many sites do not functionin without JavaScript. Sad, but that's the way it is.

Re: Guidance to developers affected by effort to block less secure browsers, apps

#118
post #66
post #46

Earlier quoted context omitted.

So the theory is this has nothing to do with security, but is only used to break private video downloading of youtube-dl?

It blocks misrepresentation of agent, in general; automation is also blocked in general, but _especially_ for authentication.

Sure but if the goal was to block youtube-dl usage, wouldn't they target the vastly more common usecase without authentication?

Re: Guidance to developers affected by effort to block less secure browsers, apps

#119
post #10

This has nothing to do with security and everything to do with banning tools like youtube-dl, wget and others; from the post: > The browser must identify itself clearly in the User-Agent. The browser must not try to impersonate another browser like Chrome or Firefox. > The browser must not provide automation features. This includes scripts that automate keystrokes or clicks, especially to perform automatic sign-ins.…

Has anyone thought of just not using Google? By using them you give them power in your life

Re: Guidance to developers affected by effort to block less secure browsers, apps

#120
post #8

I hate the smartphone app trend of having embedded browsers. Just launch me to my preferred real browser. Stop trying to trap us in your ecosystem.

yeah and in the case of Fairemail on Android, the embedded browser is dumbed-down and lacking most features... and the option to disable this "feature" is kind of hard to find
Post reply on HN