That reminds me that I still need to clean up and publish my little PoI provider tool. Weird edits on Foursquare can really mess up local data that relies on their database.
Yeah thankfully each of my checkins stores a snapshot of the venue at the time so at least changes like this don't affect the old checkins. Also I apparently have enough Foursquare superuser privileges that I was able to rename the venue back immediately! :)
Thanks for the response. I am trying to understand the specifics of the risk involved here. The site itself is HTTPS however the load balancer/proxy infra sometimes redirect to HTTP for the callback URL
Everything that the user's browser touches has to be HTTPS.