My understanding was that these programs don’t rely on YouTube’s API, but rather they are loading the page and scraping it for the relevant video files, comments, and other data. So it’s a little harder to kill them than just shutting down API access. That said, with all the new web DRM crap getting pushed by Google and others, I can’t imagine it will be long before they can detect that you aren’t viewing the page the way they want you to view the page, and then block access in some other form.

I stayed in a motel recently that had a kitchenette with a mini fridge in the same room as the bed. You can tell management spent extra for this fridge too, since it had a temperature readout and a see-through door. But by god, that bright blue LED temperature display lit up the entire room and kept me up all night. I tried to cover it with some paper, but that only made it spread further. A couple socks draped over the top eventually did the trick.

I don’t know much about him myself, but he was recently on Adam Conover’s podcast and he was super well spoken.

Yeah, I agree that sounds pretty scummy, especially since it isn’t spelled out anywhere. In the short term, I imagine you could disable the history through Chrome, or whatever you’re using as your default browser. I have been using the web version for now, since Jerboa still needs a ton of work. I just set up a direct link to my instance on my Android phone screen.

Woah, that might explain why it has been throwing so many errors for me - I’m using Brave as my default web browser.