[Hydraulix989]

Okay, then you release your recorded call AFTER they defect (I'm not saying he shouldn't have covered his ass by recording the call, that's the smart thing I would've also done). Imagine how bad that would look for Apple.

If I had to guess, Phil & co. wouldn't want to risk that nuclear scenario (and they are definitely smart enough to know better).

[spacehunt]

> Okay, then you release your recorded call AFTER they defect

Isn't this essentially what happened (at least according to Kapeli)? He wrote the blog post, sent Apple a draft, then Apple went to the press.

[eridius]

Not at all. Apple released a PR statement about what led up to the termination. And nothing they said in there was incorrect, and nothing they said in there would have contradicted his blog post. The PR statement explained that the fraud was detected across 2 linked accounts and from the way it was written it was obvious that Apple was treating both accounts as being a single developer. The blog post would have explained that his account was linked to another one with fraud, and that he's working with Apple to unlink it. Everybody who reads both posts would understand that his account didn't have any fraud on it directly, but was linked to an account with fraud.

[RotsiserMho]

That's essentially what the blog post he drafted said: https://kapeli.com/apple_draft

[eridius]

Right, because those 3 points are what Apple said his blog post had to include (if you listen to the call).

[spacehunt]

I mostly agree with you, but clearly this is not how Kapeli felt for some reason (eg. perhaps because English is not his first language):

> Tonight Apple decided to accuse me of manipulating the App Store in public via a spokesperson.