If I create a GraphQL API, I can see me accidentally falling foul of this. I'd require users to use their own API keys rather than using mine, so it would look like users would be potentially going through the same AWS IP. Hopefully using GraphQL through an AWS would mitigate this, but I can't be sure, I don't want to do the work only to get banned.
Should I lock down the GraphQL instance for my own purposes, and make others clone the code run their own versions? Or would I be okay?
TLDR: If anyone wants JSON formatted docs for the GB API, you can find them at https://gb-json-docs.netlify.com/index.json. If there is already a version of the docs in a json format, please let me know before I waste more time, I couldn't find it.
I've been wanting to play with GraphQL on something a bit more meaty, and I thought why not build a GraphQL endpoint on top of the Giant Bomb API. I haven't done that juuuust yet, because I wanted to use the documentation as config. Unfortunately, I couldn't find a json formatted version of the docs, so I went ahead and made it.
The JSON file is updated once every 24 hours to track updates to the API. This is done by using a zapier webhook that kicks off a build on netlify. Pretty nice.
Ah I only just realised we needed to put the gb coins on the first screen. Oh well.
Here is a new level, inspired by @risifrutti and their Tippy Air 2.0. Gradual difficulty ramp, using spikes and ramps, spread out the challenges a bit, and added the the occasional enemy. I enjoyed making and playing this one.
Here is "Hug your Thwomp from side to side", a level based around the way Thwomps push you around in Super Mario 3d World. I'm glad I added a checkpoint, the end can be a fucker.
Log in to comment