Youtube.js – full-featured wrapper around YouTube's private API
1–10 of 113 posts
Re: Youtube.js – full-featured wrapper around YouTube's private API
#2I'm always nervous about 3rd party API wrappers. It's basically saying "Here's the keys to my (users) Google account, please don't do anything bad". Even if it's open source, there's no guarantee there's no malicious change in version x.x.N+1
Re: Youtube.js – full-featured wrapper around YouTube's private API
#3Love this Q&A:
Do I need an API key to use this?
No, YouTube.js does not use any official API so no API keys are required.Re: Youtube.js – full-featured wrapper around YouTube's private API
#4I'm always nervous about 3rd party API wrappers. It's basically saying "Here's the keys to my (users) Google account, please don't do anything bad". Even if it's open source, there's no guarantee there's no malicious change in version x.x.N+1
You could just pin to a version like a good dev and rid yourself of the problem.
Just do a quick diff check when you upgrade. If you're too lazy to do that then you never really cared about security all that much in the first place.
Re: Youtube.js – full-featured wrapper around YouTube's private API
#5The reason I stopped integrating any API based system (FB, Twitter, etc...) into my code bases for services I don't pay for (or my customers) is because they all changed willy-nilly and broke on a regular basis.
This is more likely to break (be broken by google) than an official API, and those are bad enough. (hard pass on even trying this out, especially if it's good/nice I'll want to use it and kick myself later for being an idiot.)
Re: Youtube.js – full-featured wrapper around YouTube's private API
#6Awesome!! A custom client for YouTube that bypasses all their front end code. I wish there was something like this for every single web site!
Re: Youtube.js – full-featured wrapper around YouTube's private API
#7The reason I stopped integrating any API based system (FB, Twitter, etc...) into my code bases for services I don't pay for (or my customers) is because they all changed willy-nilly and broke on a regular basis. This is more likely to break (be broken by google) than an official API, and those are bad enough. (hard pass on even trying this out, especially if it's good/nice I'll want to use it and kick myself later fo…
Unfortunately it’s rarely that these kind of decisions are based on technical merit, but instead because they’re part of the business proposition, or requested by other parts of the business (sales/marketing).
Other than that, I fully agree that you should try to minimize your dependence on them, it’s not good a good position to be in; what’s in the best interest for YouTube today may not be the case in one year.
Re: Youtube.js – full-featured wrapper around YouTube's private API
#8I'm always nervous about 3rd party API wrappers. It's basically saying "Here's the keys to my (users) Google account, please don't do anything bad". Even if it's open source, there's no guarantee there's no malicious change in version x.x.N+1
Any software you use might steal your YouTube credentials.
It might be this API wrapper or it might be any other dependency. It might even be the scientific calculator you installed that had nothing to do with that project.
What makes this especially scary?
Re: Youtube.js – full-featured wrapper around YouTube's private API
#9I'm always nervous about 3rd party API wrappers. It's basically saying "Here's the keys to my (users) Google account, please don't do anything bad". Even if it's open source, there's no guarantee there's no malicious change in version x.x.N+1
You could just pin to a version like a good dev and rid yourself of the problem. Just do a quick diff check when you upgrade. If you're too lazy to do that then you never really cared about security all that much in the first place.
WHAT? How am I supposed to make a social media calculator flashlight app without pulling in 200 random libraries and their 5000 dependencies?
Re: Youtube.js – full-featured wrapper around YouTube's private API
#10If you’re YouTube or any site, and want to stop these sort of wrappers - what’s the easiest way to do so without breaking your own site?
I find this task to be an interesting engineering problem.
A related question is if there’s an unspoofable way to detect a client.