Skip to content
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

Renew YouTube API Key #190

Closed
adrienjoly opened this issue Mar 3, 2019 · 4 comments
Closed

Renew YouTube API Key #190

adrienjoly opened this issue Mar 3, 2019 · 4 comments
Assignees

Comments

@adrienjoly
Copy link
Member

adrienjoly commented Mar 3, 2019

Our YouTube API Key has been used and remained untouched for many years.

As it's publically available through our front-end and source code, it's possible that other developers started using it.

In order to prevent restrictions that may occur in that case, let's create a new API Key and purge our CDN caches to make sure that openwhyd.org users start using the new one.

@adrienjoly adrienjoly created this issue from a note in Development (⚙ In progress) Mar 3, 2019
@adrienjoly adrienjoly self-assigned this Mar 3, 2019
@adrienjoly
Copy link
Member Author

Steps:

Development automation moved this from ⚙ In progress to ✔️ Done / pending QA Mar 3, 2019
@adrienjoly adrienjoly moved this from ✔️ Done / pending QA to 🌲 In production in Development Mar 3, 2019
@adrienjoly
Copy link
Member Author

adrienjoly commented May 26, 2019

The change of API key was reverted on March 5th, because it quickly went over-quota: d503f11

@adrienjoly adrienjoly reopened this May 26, 2019
Development automation moved this from 🌲 In production to ⚙ In progress May 26, 2019
@adrienjoly
Copy link
Member Author

Since then, my request for increasing the quota of that API key was accepted by YouTube => let's try to use that one again.

adrienjoly pushed a commit that referenced this issue May 26, 2019
## [1.6.1](v1.6.0...v1.6.1) (2019-05-26)

### Bug Fixes

* **youtube:** switch to new YouTube account, for [#190](#190) ([8c8802b](8c8802b))
@adrienjoly
Copy link
Member Author

The change of API key was pushed to production and the CDN caches were purged.

=> the usage of the new key can be seen on https://console.developers.google.com/apis/api/youtube.googleapis.com/quotas?project=openwhyd

Development automation moved this from ⚙ In progress to ✔️ Done / pending QA May 26, 2019
adrienjoly added a commit that referenced this issue May 30, 2019
adrienjoly pushed a commit that referenced this issue May 30, 2019
## [1.6.2](v1.6.1...v1.6.2) (2019-05-30)

### Bug Fixes

* **youtube:** revert to previous YouTube account, for [#190](#190) ([32446c9](32446c9))
@adrienjoly adrienjoly removed this from ✔️ Done / pending QA in Development Sep 24, 2019
adrienjoly added a commit that referenced this issue Nov 28, 2020
## What does this PR do / solve?

PlayemJS has been maintained for Openwhyd, to play and detect tracks, by communicating with the APIs of the streaming sources we support.

While PlayemJS has supported more sources than most alternative players we have found online, its codebase has become hard to maintain, so it suffers from a lack of updates, which lead to numerous problems taking a lot of time and effort to fix: e.g. #272, #262, #192, #190, #143, #132, #128, #16...

In order to simplify Openwhyd's codebase and make it easier for us to replace PlayemJS with an alternative, let's start by trying to remove it from the bookmarklet and see if anybody misses it from there.
adrienjoly pushed a commit that referenced this issue Nov 28, 2020
## [1.43.1](v1.43.0...v1.43.1) (2020-11-28)

### Bug Fixes

* **bookmaklet:** Transpile changes form [#408](#408) to JS ([59f6f98](59f6f98))
* **bookmarklet:** Re-add PlayemJS in bookmarklet ([#408](#408)), for track detection ([8fd1a3e](8fd1a3e))
* **bookmarklet:** Remove PlayemJS from bookmarklet ([#408](#408)) ([7296b21](7296b21)), closes [#272](#272) [#262](#262) [#192](#192) [#190](#190) [#143](#143) [#132](#132) [#128](#128) [#16](#16)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant