Comment on Google just broke *all* third-party web clients, including yt-dlp; a full JS implementation is now required.

• MehBlah@lemmy.world ⁨1⁩ ⁨day⁩ ago

  Any IP on the local ISP requires a google login to work. Very few work without the cookie generated from it.

  source

  • Wildly_Utilize@infosec.pub ⁨1⁩ ⁨day⁩ ago

    I downloaded this morning with yt-dlp and American rented mullvar servers (seal for android)

    Never have logged in

    source
  • ripcord@lemmy.world ⁨1⁩ ⁨day⁩ ago

    Weird. I haven’t downloaded anything for a month or so (other than running into a different issue on somesomething), but I haven’t had to do that for any video for the several years I’ve been downloading.

    source

    • ripcord@lemmy.world ⁨1⁩ ⁨day⁩ ago

      Is this maybe much more common on common VPN IPs? Not what I think you meant by “local ISP”, but would make a lot more sense to me.

      source

      • MehBlah@lemmy.world ⁨1⁩ ⁨day⁩ ago

        It wasn’t that way until earlier this year. I switched to a vpn to get around it.

        source
      • T156@lemmy.world ⁨1⁩ ⁨day⁩ ago

        It is definitely more common on VPN IPs, since Google likely identifies the outgoing address as a datacentre, and gets suspicious.

        source
• Killer@lemmy.world ⁨1⁩ ⁨day⁩ ago

  You don’t need to afaik.

  The only time i’ve had to include cookies is if i was trying to download something that was a premium feature like enhanced bitrate.

  source