4 ms·
To be fair what that guy originally said and what happened were two different things. Apple contacted him before they shut down his account. At least that's wha
by lucaspiller 10y ago
To be fair what that guy originally said and what happened were two different things. Apple contacted him before they shut down his account. At least that's what Apple said...
http://www.loopinsight.com/2016/10/10/apple-responds-to-dash-controversy-with-proof/ http://www.loopinsight.com/2016/10/10/apple-responds-to-dash...
- pedro2 10y agoThe author says that's not true. He has phone call recording proving he is right: https://blog.kapeli.com/dash-and-apple-my-side-of-the-story https://blog.kapeli.com/dash-and-apple-my-side-of-the-story
- matt4077 10y agoHe has a phone recording of how he screws himself, by recording a phone call and trying to escalate a situation that Apple was trying to fix. He's not in the App Store today, because just posting that call without consent shows he can't be trusted. They may have tried to contact him at the address of the second account, which was spamming the store and may or may not have been him.
- wishinghand 10y agoIs the developer from Dash based in the USA? Does two party consent cross international lines? He may not have the concept of not posting a phone conversation because it's a legally allowed thing and he didn't think to check what was the legal norm in Palo Alto.
- matt4077 10y agoHe's not in the US and it may have been legal. It's still astonishingly stupid. Apple was trying to defuse the situation and asked him to call of the pitchfork-wielding mob by communicating their point of view (an account he paid for was spamming reviews). They were willing to accept his somewhat dubious assertion ("I paid for someone's account, and gave them hardware, and sometimes borrowed that hardware again, but it's not me and I'm in no way responsible"). But instead of accepting this resolution allowing everyone to safe face he seemed to be drunk with the power of the solidarity he had gotten initially, or he just wanted to really win the argument. I don't know the motivation, but anyone could have told him that trying to blackmail Apple was not going to end well,
- kuschku 10y ago> or he just wanted to really win the argument. I don't know the motivation, but anyone could have told him that trying to blackmail Apple was not going to end well, So you’d also say someone should never sue Apple for doing something bad, because they might abuse their monopoly power against you if you try to win?
- lostlogin 10y agoThat's an interesting use of the word 'abuse'. I think that with a power balance as unequal as it is Apple needs to show a ton of compassion and restraint in its dealings but I don't think you could say that they were abusing their power.
- lmm 10y agoSue them in a court of law, if it's bad enough, though be prepared for a long and hard fight. But never try to fight them in the court of public opinion.
- deleted 10y ago[deleted]
- u02sgb 10y agoTreat people based on their actions. Paying user of dash here and I've been very impressed by how the developer has allowed the Windows and Linux app zeal to use his document sets and format for free. Only condition was that they don't release a competing version for OS X. I think he deserves the benefit of the doubt.
- n1000 10y agoWhatever the case may be. I think there are plenty examples where situations escalated simply because the company ignored an urgent and justified request. I remember calling AppleCare and the poor guy on the phone admitted that there was a bug in OSX but had no means to escalate my problem further. Another example is the recent Spotify bug, which did not receive any attention until the story made it to the top of HN. I think companies actually cause damages to themselves by not reacting sooner.
- londons_explore 10y agoAs an engineer for a related company, I sometimes go and look at the support forums or tickets for my software. I find hundreds or thousands of complaints. Many are legitimate bugs, and some are user stupidity ("I need to check my mums email but she won't give me her password, can you let me in anyway"). For those which are legitimate bugs, I know, through user metrics, that they only affect a tiny fraction <0.1% of the users. I, and the rest of the engineering team have to prioritize our team between fixing these bugs for the 0.1%, and making the product better for the 99.9%. It can be a tough choice, but when you've decided that it's time to move on and develop new features, hearing about individual instances of rare bugs is no longer useful. We just aggregate how many users are impacted by each significant bug, and from time to time quash the top ones. Manually editing a database entry for a single user is no longer privacy-justifiable, so basically the only fix we can do is to fix the bug for all users at once. And if the bug is only affecting 15 out of 300,000,000 users on a product that makes 1 cent per user per year, I can't afford to spend more than 30 seconds on it really, yet most bugfixes are at least a days work.
- n1000 10y agoThanks for the insight. Makes me understand what is going on "on the other side". Although the message is a bit sad. If you don't scream loud enough it doesn't get fixed. Steve Jobs seemed to have an ear or the 0.1% :) I am pretty certain one (rare) OSX bug got fixed because I emailed him.
- z3t4 10y ago1 cent per user per year sounds very small when most online business gets valued at 1 usd / month per user times 3 years.