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.
Guidance to developers affected by effort to block less secure browsers, apps
111–120 of 165 posts
Re: Guidance to developers affected by effort to block less secure browsers, apps
#112Earlier 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."
Re: Guidance to developers affected by effort to block less secure browsers, apps
#113Earlier 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/
Re: Guidance to developers affected by effort to block less secure browsers, apps
#114How does this mesh with their plans to deprecate User-Agent? https://9to5google.com/2020/01/14/google-deprecate-chrome-us...
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
#115And if so, can that be solved by the proposed approach of gradually narrowing the requirements for supported clients?
Re: Guidance to developers affected by effort to block less secure browsers, apps
#116Disabling less secure apps has been postponed though because of covid.
Re: Guidance to developers affected by effort to block less secure browsers, apps
#117This 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! :)
Re: Guidance to developers affected by effort to block less secure browsers, apps
#118Earlier 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.
Re: Guidance to developers affected by effort to block less secure browsers, apps
#119This 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.…
Re: Guidance to developers affected by effort to block less secure browsers, apps
#120I 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.