[Slackbuilds-users] youtube-viewer API key

[B Watson]

Hunter Sezen pointed this out to me yesterday:

https://github.com/trizen/youtube-viewer/issues/308

The TL;DR version: Google has revoked the API key that youtube-viewer
uses. So we have 3 paths to choose from. I'm the youtube-viewer SBo
maintainer, I could just pick one, but I'd like to get some input from
the community.

1. Require every user to register with google and get an API key, and
   pass it to the SlackBuild (e.g. as environment variables).

2. Include an API key of our own. This key could also be used for
   other things that need one, e.g. Pafy.

3. The youtube-viewer author is working on a thing called straw-viewer
   that uses an alternate API (invidio.us) that doesn't require any
   sort of API key. It otherwise looks & acts like youtube-viewer. So
   I could just ditch youtube-viewer entirely.

Option 1 would be fine, but it would mean I'd step down as maintainer
of youtube-viewer. I won't be creating an API key, and so won't have a
way to test new versions of it.

For option 2, it's not really a bad idea for there to be an 'official'
SlackBuilds.org Google API key. But I'm not going to be the one to
register for it (prefer to minimize "relationships" with corporate
entities when I can). So, anyone want to step up and do this?
You wouldn't have to become maintainer of anything: I'd include your
key in the youtube-viewer build.

Option 3, I'm already working on. There will be a straw-viewer SlackBuild
very soon. Initial testing shows it works well. It doesn't necessarily
have to replace youtube-viewer in our repo, either, so option 1 or 2
could still apply.