[GiphyBridge] use not rate limited public api key (error 403 fix) #2625
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since more than a week the Giphy bridge stopped working.
The bridge constantly returns 403 (e.g: https://bridge.easter.fr/?action=display&bridge=Giphy&s=%40fallguysgame&format=Json).
Calls to the Giphy API with the currently used public beta key constantly return 403 BANNED (e.g: https://api.giphy.com/v1/stickers/search?api_key=dc6zaTOxFJmzC&q=%40FallGuysGame).
This is probably due to the severe rate limiting of beta api keys.
I looked at the network traffic of Giphy.com and found that the website calls the API with this key: Gc7131jiJuvI7IdN0HZ1D7nh0ow5BU6g
It's probably Giphy's own prod api key and therefore not rate limited. From a quick google search it looks likes others already use that key and that it is around since more than a year.
This PR changes the public beta key "dc6zaTOxFJmzC" to Giphy's own prod api key "Gc7131jiJuvI7IdN0HZ1D7nh0ow5BU6g".
I tested this change on a private instance for couple of days and have not noticed any problem.