You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Here you're looking at 30+ second requests that take GBs of memory on average. Even the big cloud providers don't have a good out of the box solution that doesn't cost an arm and leg.
That's exactly what we found- it's soooo expensive. At the very least it pays to do a lot of research into optimization before you put something up.
I think the ideal solution would be a serverless one so you're not having a GPU humming all the time and in case you get a traffic spike you can spin up multiple nodes to handle it. I'm in the process of trying out Google AI Cloud Platform. Let's see if that works.
One other learning I'll share is that the compute time increases close to exponentially for image size in my experience...so you can get away with higher traffic for something like DeOldify if you limit images to say 256px.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
