Ubuntu
minitube package

Custom API Key

Asked by bbhtt

The latest changelog shows Minitube has been compiled with an API key which unfortunately doesn't work for me, probably Google rate limiting it. Last time I used the application there was a way to set the API key in it or in a config file, I cannot find it? Where is it being set? Also the latest commit on upstream removed the whole API part from Readme.md, can we not set it now?

Thanks.

https://imgur.com/n0nnIMJ (It was probably in left bottom, I forgot)
https://imgur.com/BFFD0Ve

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu minitube Edit question
Assignee:
No assignee Edit question
Solved by:
bbhtt
Solved:
Last query:
Last reply:
Revision history for this message
bbhtt (bbhtt) said : 		#1

I'm on Groovy proposed minitube 3.4-1. Forgot to add it.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#2

Then report a bug. Groovy is not ready and not even remotely stable

If you are happy to put up with errors, bugs and feature holes but want to get the OS ready for release in October by reporting bugs then by all means, use Groovy but don't expect a smooth ride.

If you want an OS that works then I suggest you wipe the install off and do a clean install of Focal (Ubuntu 20.04). Focal is also LTS and is supported til April 2025, Groovy only has 9 months of support.

Groovy isn't even in the first alpha stages....what did you expect?

You can start the bug logging process with:
ubuntu-bug minitube

Groovy is not for the lay user. It's for people who are very familiar with the OS and want to help get the system ready. Please log bugs with Groovy, not questions (Until release day). Focal will give you a smoother OS experience.

Revision history for this message
bbhtt (bbhtt) said : 		#3

> If you are happy to put up with errors, bugs and feature holes but want to get the OS ready for release in October by reporting bugs then by all means, use Groovy but don't expect a smooth ride.

Yes I'm fine with it and have reported 4 bugs since moving to Groovy yesterday.

I wasn't sure if this was a "bug" or some settings were changed in the release process that we cannot set an API key any more. I came back to this software after a long time.

> Groovy is not for the lay user. It's for people who are very familiar with the OS and want to help get the system ready. Please log bugs with Groovy, not questions (Until release day). Focal will give you a smoother OS experience.

I migrated from Focal to Groovy to proposed. :)

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#4

If you see issues in Groovy, please report bugs

Revision history for this message
bbhtt (bbhtt) said : 		#5

> If you see issues in Groovy, please report bugs

https://github.com/flaviotordini/minitube/commit/7b4ef7f8aa76f316e1396a0b7b7dcde4874e0ede

?

Thank you...

Revision history for this message
michael (yellupcm-gmail) said : 		#6

Please refer to question 692234. The way I understand it, you must have Google cloud, to be able to request a key. I don't need or want Google cloud, so no more Minitube. If you find out another way, please put it here. Thanks

Revision history for this message
michael (yellupcm-gmail) said : 		#7

You made #5 comment while I was writing #6. Reading site above, it did not, make clear, how to get key.

Revision history for this message
bbhtt (bbhtt) said : 		#8

> Please refer to question 692234. The way I understand it, you must have Google cloud, to be able to request a key. I don't need or want Google cloud, so no more Minitube. If you find out another way, please put it here. Thanks

Sorry to say this but I think people here doesn't know anything about the software they are answering question's for!

You just need a regular Google account to generate an API_KEY AND client_id,client_secret

Sign in here with GMail: https://console.developers.google.com/apis/library/youtube.googleapis.com

Enable Youtube V3 > Create a project,create an API_KEY,Client id etc>Copy them to your application.

My problem is that I don't have a way to enter that API_KEY on minitube since there's no dialogue box or config file. This may be a bug,dev's decision(the latest commit above) or the Debian maintainer pre-compiled with a now dysfunctional key.

Revision history for this message
michael (yellupcm-gmail) said : 		#9

Not trying to answer, just adding comment. Thanks for clarifying about Google account, not Good cloud. That makes more sense.

Revision history for this message
Kai Kasurinen (kai-kasurinen) said : 		#10

https://flavio.tordini.org/minitube-3-5-and-musictube-1-13

"I had to rush this release because Google restricted the Youtube API only to manually approved projects. And their terms forbid any other viewer apart from their own."

Revision history for this message
Manfred Hampl (m-hampl) said : 		#11

According to the previous readme file you can provide the API key at start time with an environmental variable.

Have you tried

GOOGLE_API_KEY=enter_your_API_key_here minitube

Revision history for this message
bbhtt (bbhtt) said : 		#12

> "I had to rush this release because Google restricted the Youtube API only to manually approved projects. And their terms forbid
> any other viewer apart from their own."

Sorry but Debian and thus Ubuntu is built against upstream 3.4 and not 3.5. So no invidious api? But thanks for finding it, that explains the change in readme,last time I saw, Flavio said porting to invidious will require a major rewrite and not a priority : https://github.com/flaviotordini/minitube/issues/143

> GOOGLE_API_KEY=enter_your_API_key_here minitube

Doesn't seem to work, if a key is pre-compiled in it, as you can see after the "?key=" here, https://imgur.com/BFFD0Ve, I think it uses that only and not the one I pass.