-
Notifications
You must be signed in to change notification settings - Fork 131
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
IGDB API v4 migration #541
Comments
From a user perspective 1. is the best. The 4. option requires some serious willpower to get through the hassle. Are there other services which provide similar information and are viable?
|
Looks interesting and I'll think about integrating it. But it doesn't really solve the problem: client bundles API keys it ideally shouldn't. A server to manage keys, proxy and cache requests is the proper solution, but it raises a few questions:
Currently there is no other functionality that may require a server. If there is a server:
|
IGDB was acquired by Twitch and new IGDB API is now part of Twitch API, so it now uses Twitch API authentication.
Basically this means that GameHub can't include an API key and should either have a server to proxy requests or require end user to create a new app on Twitch and use an app token to call IGDB API.
Both of these options seem inconvenient.
Here is the message I sent to the IGDB Discord at the time they were deprecating v3 API:
Answer:
I'm not sure what to do, option 4 seems to be the best, but it will be inconvenient for the users.
The text was updated successfully, but these errors were encountered: