Bear with me please. I'm trying to understand how my app might be misbehaving. And I don't see how it could hammer the site.Leo_Pride wrote: ↑Thu Jul 05, 2018 10:44 pmThat's how top-down distribution works.
You mirror us, we limit you, your users mirror you, you limit your users.
You don't let your users hammer the site because you can't or won't maintain a proper mirror.
This whole idea that a centralised database is a permanent thing with infinite resources is fundamentally flawed, and the time where we let app design issues override the needs of well-behaved clients is over.
Remove the plank from your own eye before complaining about the speck in ours.
The way it is now..
1) User on a site enters a URL to a game
2) The game ID is extracted from the URL
3) The site makes an API call to TGDB for the info
4) The info is stored locally on the site and it is never called for again
What you're proposing...
1) User on a site enters a URL to a game
2) The game ID is extracted from the URL
3) The site makes a call to MY SITE for the info
4) My site makes a call to TGDB for the info
5) I store the info on my site
6) The info is stored locally on the original site and it is never called for again
Except in the unlikely event that several sites request the exact same game, TGDB still gets the same number of API calls either way. Or am I missing something obvious?