4 ms·

Which would still be fine. The only thing that'd be blocked is obtaining those OAuth tokens by passing your Google username/password to a browser automation too

Which would still be fine. The only thing that'd be blocked is obtaining those OAuth tokens by passing your Google username/password to a browser automation tool.

dleslie 6y ago
Which would break some common authentication options in ytdl: https://github.com/ytdl-org/youtube-dl#authentication-options https://github.com/ytdl-org/youtube-dl#authentication-option...
- tester756 6y ago
  Let's dont act as if the whole world was trying to fight against ytdl.
  - dleslie 6y ago
    It's not just about ytdl; this policy will ban all headless browsers, text-based browsers, and browsers with automation tools.
    - trickstra 6y ago
      And it's also ineffective, because any full GUI browser can be automated with extensions or userscripts, so banning useragents or non-javascript browsers won't actually prevent automates sign-ins.
- worik 6y ago
  It is not the whole world attacking ytdl - but Google, definitely. Evil by default?
  - seniorivn 6y ago
    when you delete "don't be evil" tagline, you become evil by default
salawat 6y ago
So they're breaking mountains of automated test and scripting tools? Nice to know. >Headless browsers locked out (thanks for nreaking test automation) >Node.js (riiight) >Text-based browsers (Going aft Lynx? Of all things?) >JavaScript MUST be enabled Totally not a power grab here folks. Totally not a company known to value reaping user data in any form possible up to any kind of user hostile behavior, or exercising undue influence over the character of the Net. Nope, no siree, Bob. Moving riiiight along.