Add precision about the low-level of the YouTube operational API

Benjamin Loison 2023-01-25 22:23:50 +01:00
parent 7209c1115b
commit f58dfdf16f

@ -18,7 +18,9 @@ so I coded a complementary API that is the YouTube operational API that relies o
The YouTube operational API has two parts:
- the actual YouTube operational API based on web-scraping YouTube UI
- [the no-key service](https://github.com/Benjamin-Loison/YouTube-operational-API/blob/7ff59b2d477c8d2caf6813a114f4201791627cc1/noKey/index.php) which consists in a proxy to fetch YouTube Data API v3 without any developer key by using a batch of more than 200 keys that I gathered thanks to people having unintentionally leaked their developer keys on StackOverflow, GitHub...
- [the no-key service](https://github.com/Benjamin-Loison/YouTube-operational-API/blob/7ff59b2d477c8d2caf6813a114f4201791627cc1/noKey/index.php) which consists in a proxy to fetch YouTube Data API v3 without any developer key by using a batch of more than 200 keys that I gathered thanks to people having unintentionally leaked their developer keys on Stack Overflow, GitHub...
Note that the web-scraping of the YouTube UI is not done with tools similar to Selenium which runs JavaScript but is a low-level web-scraping by just proceeding to HTTP requests and parsing the JavaScript variable containing data that the webpage is generated with.
Note that I host a YouTube operational API instance with both parts at https://yt.lemnoslife.com<br/>
Some of its metrics are available at https://yt.lemnoslife.com/metrics/, note that my official instance has proceeded successfully (without any downtime) on January 24 2023 (without me using it):