5 ms·

Apple should change their process so that they contact all linked accounts if it's possible that they would be closed. End of. Kind of. Seems like Apple is w

Apple should change their process so that they contact all linked accounts if it's possible that they would be closed. End of. Kind of. Seems like Apple is working off the assumption that linked accounts are acutely aware of what each other are doing, and thus are all equally responsible for each others actions. Clearly this assumption is not valid. Having listened to the entire call, I think both parties conducted themselves with respect and good faith. The only question unanswered in the call is “why didn't Apple notify both accounts?”. Apple is in a position of disproportionate power here. They created the platform, they make the rules, everybody either plays by them or doesn't play at all. I really hope Apple will just be honest and admit that they did, in fact, have an inadequate process for dealing with this kind of corner case. They did make a mistake. They closed someone's account when it shouldn't have been closed. If Apple is adamant that they made no mistake, they only reinforce the feeling that Apple has become an inhuman giant, a profit-hunting corporate entity, that doesn't really care about human values — the antithesis of what Apple used to be.

Twisell 10y ago
Wether apple is inhuman or the developer is a prick is quite an open question. Both were faulty and they obviously didn't come to an agreement. Apple phone offer would have gave both of them a clean exit and it might always remain shady why this agrement wasn't actually implemented... After carefully listening to the phone call I still don't understand why the developers was arguing at all. He could have been back in buisness in a breeze with no harm at all.
- metafunctor 10y ago
  Both Apple and the developer made mistakes. That much is clear. Apple, being a big corporation, is inhuman if they do not admit their mistakes. The developer, being a human, is a prick if he doesn't admit his mistakes.
- pfg 10y ago
  > Both were faulty and they obviously didn't come to an agreement. I don't know how you arrived at that conclusion. The developer offered to publish a blog post saying that the app was removed due to fraudulent activity on a linked account he was not aware of. Apple accepted and then went ahead and published a statement accusing him of engaging in fraudulent behaviour anyway, claiming they gave plenty of warning, but not mentioning that the activity was limited to the non-Dash account, that the developer claims to have been unaware of the connection, and that they did not inform him of the connection or give any warning on this account. That's just dishonest.
  - Twisell 10y ago
    Well it's more like Apple asked him to post an explanation on his blog. As far as I know this asked blog post was never published and then Apple realease it's response. So again this might well remain unsolved because probably no one appart from the arguing parties can't tell why the agreement on the blog post in exchange for dev program re-enrollment wasn't fulfilled by either parties...
    - pfg 10y ago
      > As far as I know this asked blog post was never published and then Apple realease it's response. From the blog post: > Update: Just to make it clear, I have complied with Apple’s request and have sent a blog post draft approximately 30 minutes after this phone call ended. I have since not received any contact from Apple in any way, and they did not respond to my calls. Their recent statements come as a shock as I thought we were working together to resolve this issue. Given that Apple's statement left out several important facts (arguably, to paint a rosy picture of their behavior), I'm inclined to believe the developer here.
      - Twisell 10y ago
        So maybe we can agree it relate to faith, not facts. I choose to focus more on the actual phone recording than to the dev post because at least you can hear both positions. Indeed something had gone wrong in the process they agreed on phone. But it's words against words. So I really think it's better not to chose to believe in one over another, because that would always be tainted by our own personal predisposition (which of course may differ).
- moduspwnens14 10y ago
  What mistake did Apple make?! Is everyone here taking the developer's word at face value? Despite him giving no reason to do so?
moduspwnens14 10y ago
Where did you hear the entire call? I only heard the part on his blog that clearly didn't start at the beginning. Apple didn't notify both accounts because they're under no obligation to notify someone that they're committing fraud and ask them politely to stop. Why would you take the word of a developer dumb enough to post this audio clip and publicly shame Apple in blog posts as someone honest and working in good faith with them? Here's a much more likely story: he's not telling the truth and he's in over his head. His cousin didn't leave fraudulent reviews from his test devices on his and competitors' apps for no apparent reason.
- metafunctor 10y ago
  Ah, I should've said "entire recording". What's posted on the blog is all I've heard. Apple is under no obligation to do anything, they can do as they please. But just because an entity is “under no obligation” to do something, or something is “completely legal”, doesn't make it right. In this case, I'm siding with the developer for a few reasons. First of all, his app is good, the reviews are genuine, and even Apple thinks so. Second, I can relate to him, as I've given away test hardware to others, and I was not aware that I should vouch for whatever they do with the hardware. Finally, Apple is the big player here with all the muscle. When in doubt, I try to side with the party that didn't come up with the rules.

Twisell 10y ago

Wether apple is inhuman or the developer is a prick is quite an open question. Both were faulty and they obviously didn't come to an agreement. Apple phone offer would have gave both of them a clean exit and it might always remain shady why this agrement wasn't actually implemented... After carefully listening to the phone call I still don't understand why the developers was arguing at all. He could have been back in buisness in a breeze with no harm at all.

metafunctor 10y ago
Both Apple and the developer made mistakes. That much is clear. Apple, being a big corporation, is inhuman if they do not admit their mistakes. The developer, being a human, is a prick if he doesn't admit his mistakes.
pfg 10y ago
> Both were faulty and they obviously didn't come to an agreement. I don't know how you arrived at that conclusion. The developer offered to publish a blog post saying that the app was removed due to fraudulent activity on a linked account he was not aware of. Apple accepted and then went ahead and published a statement accusing him of engaging in fraudulent behaviour anyway, claiming they gave plenty of warning, but not mentioning that the activity was limited to the non-Dash account, that the developer claims to have been unaware of the connection, and that they did not inform him of the connection or give any warning on this account. That's just dishonest.
- Twisell 10y ago
  Well it's more like Apple asked him to post an explanation on his blog. As far as I know this asked blog post was never published and then Apple realease it's response. So again this might well remain unsolved because probably no one appart from the arguing parties can't tell why the agreement on the blog post in exchange for dev program re-enrollment wasn't fulfilled by either parties...
  - pfg 10y ago
    > As far as I know this asked blog post was never published and then Apple realease it's response. From the blog post: > Update: Just to make it clear, I have complied with Apple’s request and have sent a blog post draft approximately 30 minutes after this phone call ended. I have since not received any contact from Apple in any way, and they did not respond to my calls. Their recent statements come as a shock as I thought we were working together to resolve this issue. Given that Apple's statement left out several important facts (arguably, to paint a rosy picture of their behavior), I'm inclined to believe the developer here.
    - Twisell 10y ago
      So maybe we can agree it relate to faith, not facts. I choose to focus more on the actual phone recording than to the dev post because at least you can hear both positions. Indeed something had gone wrong in the process they agreed on phone. But it's words against words. So I really think it's better not to chose to believe in one over another, because that would always be tainted by our own personal predisposition (which of course may differ).
moduspwnens14 10y ago
What mistake did Apple make?! Is everyone here taking the developer's word at face value? Despite him giving no reason to do so?

moduspwnens14 10y ago

Where did you hear the entire call? I only heard the part on his blog that clearly didn't start at the beginning. Apple didn't notify both accounts because they're under no obligation to notify someone that they're committing fraud and ask them politely to stop. Why would you take the word of a developer dumb enough to post this audio clip and publicly shame Apple in blog posts as someone honest and working in good faith with them? Here's a much more likely story: he's not telling the truth and he's in over his head. His cousin didn't leave fraudulent reviews from his test devices on his and competitors' apps for no apparent reason.

metafunctor 10y ago
Ah, I should've said "entire recording". What's posted on the blog is all I've heard. Apple is under no obligation to do anything, they can do as they please. But just because an entity is “under no obligation” to do something, or something is “completely legal”, doesn't make it right. In this case, I'm siding with the developer for a few reasons. First of all, his app is good, the reviews are genuine, and even Apple thinks so. Second, I can relate to him, as I've given away test hardware to others, and I was not aware that I should vouch for whatever they do with the hardware. Finally, Apple is the big player here with all the muscle. When in doubt, I try to side with the party that didn't come up with the rules.