NewPipeExtractor

NewPipe has it's own library NewPipeExtractor and does the work on your device, so IP bans aren't really a problem compared to a hosted instances where multiple clients access youtube through the IP of the instance. https://github.com/TeamNewPipe/NewPipeExtractor Piped is an alternative to Invidious which uses the NewPipeExtractor library: https://github.com/TeamPiped/Piped But instances with high traffic or 'suspicious IP Adresses' can still be banned very quickly.

NewPipe Extractor [1] can be used independently, e.g. the piped web front-end [2] also uses it. [1] https://github.com/TeamNewPipe/NewPipeExtractor [2] https://github.com/TeamPiped/Piped

You could start by taking a look at the base library that powers NewPipe and Piped called NewPipe Extractor [0][1]. It can extract the information you need from YouTube without using the API, I believe that includes access to the video streams themselves. Otherwise you could try and use Invidious through the developer API [2] although I must admit I have zero idea how good it is. [0]: https://github.com/TeamNewPipe/NewPipeExtractor [1]: https://teamnewpipe.github.io/documentation/ [2]: https://docs.invidious.io/api/

I wasn't sure myself either, so I looked it up. - Piped [1] uses NewPipeExtractor [2] (which is also used by NewPipe) to parse YouTube responses. I assume this is somewhat similar to what yt-dlp [3] does ? - Invidious states in their FAQ [4]: "By default, the video stream is fetched directly from Google's servers (googlevideo.com)". [1]: https://github.com/TeamPiped/Piped [2]: https://github.com/TeamNewPipe/NewPipeExtractor [3]: https://github.com/yt-dlp/yt-dlp [4]: https://docs.invidious.io/faq/#q-what-data-is-shared-with-yo...

There is also Piped [0] which is a direct alternative to Invidious. It uses the NewPipeExtractor [1] from the NewPipe Android app [2] to contact YouTube. [0] https://github.com/TeamPiped/Piped [1] https://github.com/TeamNewPipe/NewPipeExtractor [2] https://github.com/TeamNewPipe/NewPipe

The reasoning behind the rejection [0] seems quite thought out, and took some time and discussion in coming. > Violation of foundational rights cannot be justified by some crude imagination of freedom, that argument doesn't hold. Quoting the German constitution, Art. 2 (1): "Every person shall have the right to free development of his personality insofar as he does not violate the rights of others [...].". The contents violate other people's rights quite obviously and repeatedly. Such a platform shall never receive any attention through our app. Not every country has the broad definition of freedom of speech that the US has. It shouldn't be an _expectation_ that the developers would attempt to subvert their own laws to satisfy a loud minority. (Refer back to emphasis before taking issue with this particular sentence.) [0] https://github.c

NewPipe doesn't use youtube-dl, they have their own implementation of the stream extraction code[1]. Unless that codebase also has test cases which specifically try to download RIAA content, they would need to find a different justification for a DMCA takedown. [1]: https://github.com/TeamNewPipe/NewPipeExtractor