News for hackers. Stuff that matters.
Re:Reverse-engineering the Starbucks ordering API by StavrosK on Wednesday July 12, 2017 @08:59PM (#14758020)
It seems to me that you can make an API that is trivially reverse-engineerable and both have your pie and eat it.
Re:Reverse-engineering the Starbucks ordering API by tuna-piano on Wednesday July 12, 2017 @09:39PM (#14758171)
But then your users start using the Starbucks ordering Slack channel, cool! But their credit card is hacked. Or the slack channel breaks. Or a stalking ex-boyfriend intercepts the order and delivers the latte himself. Starbucks would likely be blamed for these problems.

Remember the Snapchat leak from a few years ago?[1] I'd bet almost everyone who heard about the leak thought that Snapchat got hacked, and many then thought that their personal photos are not safe on Snapchat. But the reality is different. Users logged into a site called "Snapsave", many probably thinking it was part of Snapchat. It was Snapsave that used the private Snapchat API and got hacked... not Snapchat.

[1] http://www.huffingtonpost.com/2014/10/10/snapchat-leak_n_596...

Re:Reverse-engineering the Starbucks ordering API by dave5104 on Wednesday July 12, 2017 @09:08PM (#14758058)
In this case, don't you mean have your frappuccino and drink it?
Re:Reverse-engineering the Starbucks ordering API by karljtaylor on Wednesday July 12, 2017 @09:44PM (#14758186)
thanks a latte.