Originally Posted by
cowtool
The reasons for shutting it down would also make me not want to do that.
It's not "I don't want to run it anymore", but closer to "I don't want it to exist any more".
I'm sure they aren't interested in the source code. But they may be interested in a list of features that it had and some data on how often they were used (and how often they resulted in bookings?)
When I have some free time (likely not until next week), I'll be pulling down the entire site (rather than just disabling the button and having all backend calls throw an exception), replacing it with a simple static web page that describes its history.
I'm kind of surprised you're not keeping it up just for yourself. Though I suppose that's just what you would have to say if you *were* keeping it up for yourself....
I guess you wouldn't want people asking you to run queries for them and the best way to assure that doesn't happen is to not keep the capability to run them.
I find it curious that AC can't just block the API end points. They could issue tokens in the UI session flow and then require those tokens to run queries. Of course abusers could simulate the whole flow but it must be easier to detect abusers when you force them to simulate a whole session than just API requests. That said I kind of wish the business didn't rely on blocking API requests and actually found a way to make these third party interfaces beneficial to their business.
Oh. And yeah, thanks for it while it lasted. I was only a minor user but it still helped me find the best deals on a couple trips.