cross-posted from: https://fedia.io/m/Brussels/t/344992
Until recently, it was possible to download #Youtube videos on a library PC & store on USB drive by using an #Invidious front-end. Recently the library has blocked all invidious instances. You can still view videos but when you try to download one it gives a 403 forbidden error.
Why are they doing this?
I can only think of two possibilities: 1. bandwidth limitations 2. copyright issues. Anyone know anything solid about this?
Suggestions on other options would be appreciated. I assume users cannot install their own apps, which means front-ends that need installation are problably a non-starter. It looks like there is a web-based front end called #Piped but many of those instances are hosted with the same domain as Invidious thus may be blocked as well.
Maybe their IPs are getting bans because of Invidious use. Last I checked, YT doesn’t share APIs for 3p clients, so this may count as “piracy” and the libraries are just trying to cover their ass.
Someone on the Invidious project says the copyright issue is “complicated”… that it’s a murky grey area. I’m not sure a library would research it diligently and might rather block it out of risk aversion.
So this is why I’m looking for concrete information.