The root problem in this controversy, in my opinion, is that iOS offers no other way to install third party applications outside the appstore for the general public. If a blackmailing attacker hits your app with fraudulent reviews on purpose you have nowhere to go with your app. If you could at least host the .ipa for installation on your own web page, such tactics wouldn't necessarily turn into a death sentence, just a loss of access to an effective sales channel (the app store)
Apple Responds to Dash Controversy
21–30 of 199 posts
Re: Apple Responds to Dash Controversy
#22this is a new attack vector that will definitely start getting used against competitors.
Re: Apple Responds to Dash Controversy
#23The root problem in this controversy, in my opinion, is that iOS offers no other way to install third party applications outside the appstore for the general public. If a blackmailing attacker hits your app with fraudulent reviews on purpose you have nowhere to go with your app. If you could at least host the .ipa for installation on your own web page, such tactics wouldn't necessarily turn into a death sentence, jus…
Platforms that dont support side loading need to be held to a higher standard than those that dont.
Re: Apple Responds to Dash Controversy
#24This is a very weird definition of "proof". A much more accurate headline might be "Apple responds to Dash controversy by insisting they were right all along and refusing to provide proof." Edit: The tone of the entire article rubs me the wrong way; it reads like a press release that nobody could be bothered to re-write. > The integrity of the App Store is as important to Apple as it is to consumers. Citation needed?…
Unfortunately The Loop isn't much of a news site, more of a controlled Apple leak blog. Dalrymple has gotten to the point of being a complete Apple shill. Edit: Compare the tone of the Loop article to Daring Fireballs: http://daringfireball.net/2016/10/apple_dash_controversy Gruber takes a much more unbiased approach, supported well. The Loop article reads like a statement from the Principal read by your teacher.
I'd like to think we can keep personal attacks like this off of HN without some sort of substantiation.
Re: Apple Responds to Dash Controversy
#25There's proof, but we're not going to link it because ... reasons. Why would they not include any proof that might exist?
Because they're in an arms race with review spammers, and telling the spammers how they were detected causes them to evolve new, undetected behaviors. It might not be fair, but it's logical.
While Apple understandably may be very reluctant to disclose review validation / fraud detection methods, they could certainly show some trusted media figure -- Marco, some other popular ios developer, maybe even Gruber -- some detailed bit of proof and put this controversy to rest. If, indeed, they have any proof.
Re: Apple Responds to Dash Controversy
#26So if I want to remove a competing app from the app store, all I have to do is buy them a bunch of fake reviews and Apple will ban them?
yup.
Re: Apple Responds to Dash Controversy
#27This may sound stupid, and I am not by any means saying this is what happened here, but would it be possible for someone to maliciously buy fake reviews for a competitor app? What would happen in this scenario?
Re: Apple Responds to Dash Controversy
#28So if you want to get your competitor banned from the App store, just post lots of spammy positive reviews for their product? How would you defend your app against such an attack?
While I don't know how their rating system or detection works, I imagine it would be harder than just posting spammy positive reviews. They would have to have solid evidence that you're doing it to your own app, or paying someone to do it on your behalf.
Re: Apple Responds to Dash Controversy
#29Where does Apple respond? Or is this blog maintained by Apple?
Re: Apple Responds to Dash Controversy
#30So if you want to get your competitor banned from the App store, just post lots of spammy positive reviews for their product? How would you defend your app against such an attack?
I would recommend responding to Apple when they attempt to contact you. It appears that this developer did not do that.