Auster@thebrainbin.org 16 hours ago
Can't test now, but an idea: as afaik EGS, GOG and Steam all have public APIs, maybe pull games to your internal database based on what is in the accounts of people joining in? As people likely have kilometric backlogs, it should already be useful for them, and it should help lessening the initial load as you wouldn't need to pull what probably is past 100k+ unique titles all at once.
When you add such login options, I mean.
Although, in this idea of leveraging public APIs, maybe database sites have them too? In all such cases, you could probably also already import useful stuff like tags, ignoring what's redundant and thus lessening the load on both your server and the API's server.
YUART@feddit.org 2 hours ago
Hi, thanks for the idea.
From my point of view, it’s not that complex to grab data from game stores and put it into my database. For services without insane rate limiting, I can pull 100k games in a few hours. Storing all the needed data is also not a problem.
The biggest problem with game data for now is to distill it and calculate differences, and this is what takes the most time and computing resources. Currently, Gamescovery DB has 70k+ games from itch.io and I spend a lot of time filtering it than on grabbing data from itch.io (originally, I grabbed around 100k games from itch.io).
So, when the right time comes, Gamescovery will have games from Steam without any complex hacks. I’m not sure about GOG and EGS, didn’t check that.