News for hackers. Stuff that matters.
Re:Reverse-engineering the Starbucks ordering API by IshKebab on Thursday July 13, 2017 @04:49AM (#14759748)
What abuse would it be ripe for exactly? I assume the only thing they were trying to prevent is third party apps.
Re:Reverse-engineering the Starbucks ordering API by bpicolo on Thursday July 13, 2017 @12:37PM (#14762731)
Say a third party app orders the wrong coffee, or orders too much stuff, etc. There's a real business risk because they have to shell out physical capital to make coffee.

I might be slightly off because thinking about it the app probably requires up-front payment. But either way, fully open APIs can cause problems if they're more meant for internal processes

Re:Reverse-engineering the Starbucks ordering API by prawks on Thursday July 13, 2017 @02:48PM (#14764009)
One funny (ab)use case that may not be immediately obvious: any public API that accepts payment for goods via credit card will sooner or later attempt to be used by carders to test purchased/stolen card lists for validity.
Re:Reverse-engineering the Starbucks ordering API by lsaferite on Thursday July 13, 2017 @06:58PM (#14766018)
So? You mitigate this on the server since you can never trust the client.