edit: Forgot to add, the website uses no JavaScript and doesn't track you at all. It also tries to implement most of YouTube's functionality, so you don't loose anything by using the website instead of YouTube.
edit: Forgot to add, the website uses no JavaScript and doesn't track you at all. It also tries to implement most of YouTube's functionality, so you don't loose anything by using the website instead of YouTube.
As soon as you store any of their content on your server, even if in just RAM, you're fucked, because that's copyright infringement.
Tell this to the hundreds of online youtube downloaders which are downloading youtube videos to their servers and then making it available for the user to download it from them: https://www.google.hu/search?q=online+youtube+downloader
> (5A) you agree not to distribute any part of or parts of the Website or the Service, including but not limited to any Content
By downloading and sending the videos from your servers, you are distributing their content.
> (5C) you agree not to access Content through any technology or means other than the video playback pages of the Website itself, the YouTube Player, or such other means as YouTube may explicitly designate for this purpose
Downloading a video via CLI is not using the YouTube player.
> (5D) you agree not to (or attempt to) circumvent, disable or otherwise interfere with any security related features of the Service or features that (i) prevent or restrict use or copying of Content or (ii) enforce limitations on use of the Service or the content accessible via the Service
By removing ads you are interfering with the restriction that users must watch ads.
> (5L) [...] not intended to be downloaded (either permanently or temporarily), copied, stored, or redistributed by the user.
Should be obvious.
> (5M) You shall not copy, reproduce, distribute, transmit, broadcast, display, sell, license, or otherwise exploit any Content
You are copying and distributing the content.
Exactly what's the goal of your ill-fated plan? You're going to get blocked/banned and when you continue to circumvent it, you're going to get a C&D. This is an absolutely terrible idea.
(The LimeWire website only ran PHP (soft requirement), the credit card processing box only ran Perl (hard requirement), no shared network drive between website and credit card box (hard requirement), so none of the existing Open Source CAPTCHA implementations worked. So, I made the CAPTCHA answer a cryptographic function of a shared secret, the user's /24 network, and a user-supplied timestamp rounded to a 32 or 64-second boundary. Timestamps older than 15 minutes were rejected, and messing with the timestamp would mean that the captcha answer wouldn't match the image you were given. I watched an attacker solve a CAPTCHA for an IP in Virginia and a couple seconds later try replaying it thousands of times from an IP in England. A few IP addresses for US navy satellite ground stations in Virginia (NAT for tons of deployed sailors) had to be white-listed from the replay checker.)