-
Notifications
You must be signed in to change notification settings - Fork 755
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 plugin setting Code unclear how to use #92
Comments
@sorin-pop this plugin is made by volunteers in their free time Why don't you grow up? |
Yes, that was exactly my point as well (Why don't YOU grow up?). But it seems you did not understand my point. Too bad. |
@sorin-pop if you can't understand that this plugin is made by people (not part of Volumio Team) during their free time, and that plugins can be improved by anyone (you included) since they are open source, then there is no point getting your whinings. |
Sir, now that's the kind of ideas I love hearing! |
OK, after a Volumio restart the Youtube plugin seems to work much better. The issues reported above are no longer present. So it's not as bad as I thought, I just needed a Volumio restart after installing the plugin. Perhaps this will be useful info for somebody else who will run into this problem. I apologize for being so frustrated initially, and for my tone. Well, Cris, I guess I won't have to write to you directly for the moment. (although I don't really understand you mentioning some plugin of mine! That's kind of weird...This ticket was about your plugin. But I'm glad you like the idea of possibly making it payable and elevating it from just a simple hobby buggy project to a more professional one) |
Not clear what to do.
Enter the following code on {0}. What does {0} mean?
I get a code of 10, but when I try to enter it at https://www.google.com/device I cannot type it in.
This really seems like very very buggy and unprofessionial. Why don't you guys make this plugin payable, but then at least make it properly. So frustrating...
The text was updated successfully, but these errors were encountered: