-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Youtube not working as provider anymore #20
Comments
Thank you Aitor! I'm working on fixing it now |
Hi again, To fix my own problem (old, legacy servers with ruby < 1.9.3, minimal dependencies, no need for access to authenticated videos/info) I hacked away Videodrome two days ago and replaced my local UnvlogIt's youtube implementation to use it instead of the youtube_it gem. This said, yt is probably a much better replacement for UnvlogIt since it aims to be a full-fledged ruby client for Youtube Data API and allows you o eventually add methods to access private Youtube's video information. Enjoy the weekend! |
I'm actually doing something similar for unvlog.com (this poor guy is really old!). I'll check your implementation because we probably don't need the powerful features from yt for basic operations |
It has been made in a rush and there is definitely space for improvement but it works (I'm running it in a few production sites). But feel to pull request or create issues if you find something or have any suggestions. |
I'll do! (Both, pull request you something if I find something and enjoy the weekend 💃 ) |
Just a small heads up: the youtube_it gem is not working anymore.
Youtube finally switched off the V2 of their Data API on May 6th 2015 (source). The gem's author seems to be unresponsive to the new situation (kylejginavan/youtube_it#251) so, right now, this gem seems to be a dead end.
As mentioned in the previous link, some people is migrating to http://github.com/Fullscreen/yt. They support v3 and have a migration document: https://github.com/Fullscreen/yt/blob/master/YOUTUBE_IT.md. Unfortunately this gem requires ruby '>= 1.9.3' so if you switch to it, this new interpreter requirement should be stated in the acts_as_unvlogable gemspec.
The text was updated successfully, but these errors were encountered: