3 ms·
It seems to me that you can make an API that is trivially reverse-engineerable and both have your pie and eat it.
by StavrosK 9y ago
It seems to me that you can make an API that is trivially reverse-engineerable and both have your pie and eat it.
- dave5104 9y agoIn this case, don't you mean have your frappuccino and drink it?
- karljtaylor 9y agothanks a latte.
- tuna-piano 9y agoBut 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_5965590.html http://www.huffingtonpost.com/2014/10/10/snapchat-leak_n_596...