I will see the shirt offer and raise him one shirt. Any Google employee who forwards me confidential and highly important legal documents, and thus risking immediate firing if not a lawsuit of their own, will get not one, but two t-shirts! All the way from Italy!
It's not legitimate news. It's confidential correspondence. Arrington is seeking to bribe a Google employee to betray his employer by breaching his NDA. If the document were evidence of wrongdoing on Google's part, it would be a different matter -- the employee would be a whistleblower and his betrayal would be laudable. But that's not what we're talking about. Google is the victim of the alleged wrongdoing. If the information gets leaked, they're victimized even further by being deprived of a bargaining chip with Apple.
Apple lied in an official FCC inquiry. That's news.
Arrington is seeking to bribe a Google employee to betray his employer by breaching his NDA.
The vast majority of news leaks throughout history have been based on ulterior motives; whether they are politically or financially-based, seems inconsequential. TechCrunch isn't a party to that NDA, so they should only consider the public interest of the story.
If the information gets leaked, they're victimized even further by being deprived of a bargaining chip with Apple.
What bargaining chip? The ability to collude to scuttle a government investigation? If the FCC asks for the letter, Google has to give it up anyways.
Your kind of assuming that Google would want the FCC investigation to conclude and effectively force Apple into accepting Voice.
But perhaps they would prefer for Apple to just get so uncomfortable over the poking around they accept Voice off bat in an attempt to take the heat off.
Which means Google have that rejection letter as big guns at any later stage.
Yes Google have to give it to the FCC if they ask for it - but if they don't ask (I am not 100% sure of the rules here) they don't have to mention it or do more than vaguely hint at it's existence.
More than that, I was wondering: Who would do that for a T-Shirt? Its just disgusting to me (and indicative of why I don't read Tech Crunch) that they are so full of themselves that they feel even a T-Shirt from them holds significant value.
Agreed, perhaps the work week has sapped people of their sense of humour. Or perhaps there's a rare genetic anomaly that turns people into hackers and leaves them without a single funny-bone in their body.
Its not that its a lost sense of humour, I would guess (because I know why I thought it wasn't a joke) its because of the relatively low opinion many people here have of TechCrunch. Its almost (at least to me) like Nixon, right after Watergate, joking "I wouldn't want you to get a parking ticket..." Sure, it isn't a big deal, but it is rather slimy, and since you already have a low opinion of the party, the whole "joke" is skipped over.
And the fact that sarcasm doesn't translate over the internet well doesn't help any. Or, as I have refered to it: damn you internet and your lack of signifying sarcasm, or, in the semi-pronouncable internet acronym form: DYIAYLOSS.
I don't believe this would have gone over much better if spoken aloud. Sarcasm isn't typically a humour well used in NA, either people can't say it right or people don't understand it. Coming from the UK where sarcasm can be used in every sentence, it's like being the only person with sight in a world of blind people.
I believe (!) should become a standard for sarcasm on the web, it would at least hint people that the line is different from the norm.
I once passed on a story to TC that had one upvote on HN at the time. It went on to become a huge sensation online and in print worldwide. I won't disclose it but basically the company threatened to sue all involved in spreading it. Afraid, I wrote to Arrington and he assured me he'd rather goto jail than out a source.
Of course I never seriously thought the company had a case(especially against me). I just took a public link and fwded it to someone who made it big. Very different from leaking.
What strikes me as worrisome is that, at least by the tone of the article, there is no possible doubt in Arrington's mind that the screenshot exists, and that it is EXACTLY what was claimed to him, and he hasn't even seen it.
I'm sure it's a somewhat thin argument, but I personally would think they'd start reserving their over-committal in the wake of the Facebook-picture-fax thing. I mean, they bought that hook, line and sinker, and that was a hoax they at least SAW.
What strikes me as worrisome is that, at least by the tone of the article, there is no possible doubt in Arrington's mind that the screenshot exists, and that it is EXACTLY what was claimed to him, and he hasn't even seen it.
This is a far better critique of TechCrunch than the "quid pro quo" angle.
I find that a little funny. By wearing the free t-shirt, wouldn't everybody know what it's you that leaked said screenshot? Unless everybody at google regularly wears techcrunch clothing, which probably isn't likely. He should probably offer something which doesn't implicitly identify his source.
This is disproved by the fact that at least 10 perfectly photoshopped screenshots had to have been submitted in the first hour, and have not been posted.
So, I'm a little confused about the root issue here. Can anyone explain what's so special about Google Voice compared to Skype? It seems that Apple has approved an app with a similar functionality in Skype for the iPhone. Is there something extra special about Google Voice that I'm not seeing? If the two apps are functionally identical maybe Apple is hung up on some aspect of the implementation. The whole "Apple believed the application duplicated the core dialer functionality of the iPhone” sounds like it could be more of a technical issue vs a functionality / religion issue. (Religion being Thou shall not make phone calls without glorious At&T)
There's no relevant difference between GV and the plethora VOIP & dialer apps out there. At least none that would be explained away with a straight face by the "core functionality" argument.
Anyone have a copy of any bona-fide Apple App Store rejection notice?
It's possible both sides are playing semantic games. A "we can't include this app at this time without tweaks" could be seen as a 'rejection' or merely a 'request for info/changes' depending on your perspective. I wouldn't put it past Apple to have carefully worded all 'rejections' and 'approvals' so that there is always wiggle room in both directions.
False. The iTunes Connect interface displays a red stoplight and a "Rejected" indication when an app has been rejected. Can't be clearer than that. Now whether or not they showed this image to Google I haven't the foggiest idea, but that's the way it's always happened to me. Behold:
http://dl.getdropbox.com/u/59605/imgboards/Screen%20shot%202...
As for e-mail rejection notices, they can be a little weasley. Here's the operative sentence in a rejection I got from Apple:
> We've reviewed [app name] and determined that we cannot post this version of your iPhone application to the App Store because [reason].
Though, I can see Apple's wiggle-room still. The image talks about rejecting a 'binary'. The boilerplate text, rejecting a 'version'.
So picturing myself seated on Apple's (self-interested, self-serving) mental furniture, they may interpret things as: "We've rejected a version, and rejected a binary, but the app itself is still (and perpetually!) eligible for further consideration."
Now we're playing semantics. The problem with redefining "rejecting an app" is that the phrase already has a perfectly good meaning: "dismiss as inadequate, inappropriate, or not to one's taste." Rejecting doesn't (have to) imply permanence; I rejected non-Newtonian physics for much of my life, but I do so no longer. If showing a red stoplight, the word "Rejected", and Phil Schiller calling you to say the app's not in the store doesn't mean the app was rejected than the phrase has no meaning. (Again, don't have any insider knowledge here; just inferring what happened based on my experience with app rejections).
Further, even playing by Apple's own semantics (which I take strong issue with), there's clearly an "Application status" called "Rejected". So even if they were to suddenly become nihilists and apps are never rejected, that's not consistent with what the iTunes Connect interface actually says, which (IANAL) I presume is legally actionable with respect to what constitutes an official Apple communication.
Obviously, there's some kind of communication/PR/spin gap between Apple and Google. The distinction is so tiny and cosmetic that it's not worth getting all worked up over: Apple is weaseling around its decision, and it's pretty slimy, but it's going a little far to shout "you lie." (A "nuke"? Seriously?)
Personally, I wish the hotheaded folks at the 'Crunch would move on to the larger questions: what's the real reason the app was "not accepted"? Is the decision anticompetitive? What can Google (and its customers) do about it?
The documents released yesterday indicate that Google was informed of the rejection of the current Google Voice application during a phone call with Phil Schiller on July 7th. Plenty of room for ambiguity in that.
How many programs nowadays of the complexity of Google voice don't use some kind of internal state machine interpreter or domain-specific-language to simplify the programming model?
So they could use that loophole in a negative way to hinder competition whenever they choose to do so, not saying they "would" but they certainly "could".
Except they "didn't". They've already listed their reasons (http://www.apple.com/hotnews/apple-answers-fcc-questions/) and to my knowledge have never used the interpreter rule in anything remotely resembling the way you describe.
Anyone left on HN who still wants to stand up for Arrington's reputation as a journalist?