After the incident that led to an API Rate limit, I was thinking about ways to limit the number of API requests we sent TETRIO, and I think we could utilize an SQLite3 database that remembers registrations and the last time that a player played a game. Instead of using an API request every time, the bot could first query the database to see if it knows already if the player has played within the last week or whatever parameter is set. If they have, awesome, we saved a request. Otherwise, we send the API request and update the database with the results along with posting in whatever channel the warnings are set to.
I'm willing to set this up myself, I just wanted thoughts on the matter first. This could also be entirely overkill for a very small problem.
Edit: I also see some mongodb usage that I missed earlier so feel free to call me a goof if this is already being done.
After the incident that led to an API Rate limit, I was thinking about ways to limit the number of API requests we sent TETRIO, and I think we could utilize an SQLite3 database that remembers registrations and the last time that a player played a game. Instead of using an API request every time, the bot could first query the database to see if it knows already if the player has played within the last week or whatever parameter is set. If they have, awesome, we saved a request. Otherwise, we send the API request and update the database with the results along with posting in whatever channel the warnings are set to.
I'm willing to set this up myself, I just wanted thoughts on the matter first. This could also be entirely overkill for a very small problem.
Edit: I also see some mongodb usage that I missed earlier so feel free to call me a goof if this is already being done.