News for hackers. Stuff that matters.
Re:Rogue Amoeba responds to Phil Schiller by taligent on Friday June 08, 2012 @11:44PM (#4087101)
I don't understand where Rogue Amoeba is coming from here.

They don't have a "right" to be on the App Store. It's Apple's store ergo their rules. And everybody knows that the rules are more guidelines and Apple can and will change their mind about them at any time. Especially if you try and undermine them e.g. by using their private encryption key.

Does it suck. Absolutely. Is it unfair. Probably. But this has been the game for the last 3 years and Rogue Amoeba should not act surprised.

Re:Rogue Amoeba responds to Phil Schiller by kevingadd on Friday June 08, 2012 @11:45PM (#4087105)
Removing an app from the store is one thing. Bending the truth or outright lying to your own customers in order to deflect blame for a decision that you made arbitrarily is entirely another. The fact that this nonsense is coming from a high-level Apple employee and not some customer service rep who can claim not to have known the truth makes it worse.
Re:Rogue Amoeba responds to Phil Schiller by lloeki on Saturday June 09, 2012 @05:06AM (#4087666)
> Bending the truth or outright lying to your own customers in order to deflect blame for a decision that you made arbitrarily is entirely another.

This entire sentence applies to Rogue Amoeba. The Airplay protocol has been reverse engineered years ago: it's basically RTSP with an encrypted stream. Creating an AirPlay audio receiver is currently subject to a license, and requires a private key. This key has been extracted from a dumped AirPort Express ROM. Rogue Amoeba can say what they want about reimplementing the whole AirPlay protocol on their own, the clef-de-voûte is this private key, only available through licensing. When Schiller mentions private APIs, I believe he is not talking about an iPhone private API (which I'm positively sure Rogue Amoeba took great care of not using) but the remote AirPlay API, which they have no right to use without licensing.

The key point here is that there's a key virtually locking the API. I think it's perfectly apt to say now that — thanks to the Google/Oracle case — implementing an API is licit, but you would subsequently have to use your own public/private keys. Yet existing AirPlay sources encrypt the stream with Apple's public key, hence the content is at the sole destination of Apple's private key.

Compare this to the following situation: you publish you PGP public key and someone writes you an email and encrypts it with your public key. If someone steals your private key, that does not entitle him to decrypt and read the message whose sole intended recipient is you. This is, I believe, the crux of Apple's AirPlay licensing.

I generally don't like Apple's silent hammer, and I really like Rogue Amoeba and their software (which I bought multiple times), but — since I knew what was in play technically — when reading the last status report of Rogue Amoeba, it was obvious to me that they were concealing information with the goal of bending the truth to support their side of the argument.

Re:Rogue Amoeba responds to Phil Schiller by imjoel on Saturday June 09, 2012 @08:22AM (#4087926)
Exactly. Despite Apple's schizophrenic application of their guidelines, Rogue Amoeba simply needs to take responsibility for everything you pointed out here. To continue to do otherwise is unprofessional and only hurts them in the end. Apple will continue to make billions.

P.S. Who else had to Google clef-de-voûte? FYI: It basically means "most important component" or "key element." (via bab.la)

Re:Rogue Amoeba responds to Phil Schiller by jguimont on Saturday June 09, 2012 @09:25AM (#4088032)
Clef de voûte is the polygonal piece at the center top of a voute (big wall opening in cathedrals for example).

Without it everything falls appart.

Re:Rogue Amoeba responds to Phil Schiller by gonzo on Saturday June 09, 2012 @02:51PM (#4088918)
Keystone in English
Re:Rogue Amoeba responds to Phil Schiller by NyxWulf on Saturday June 09, 2012 @08:52AM (#4087978)
heh, I was about to, but then I saw your response. Thanks.
Re:Rogue Amoeba responds to Phil Schiller by cafard on Saturday June 09, 2012 @09:29AM (#4088042)
Keystone, then?
Re:Rogue Amoeba responds to Phil Schiller by stcredzero on Saturday June 09, 2012 @10:06AM (#4088118)
If you pull it out, does everything fall down?
Re:Rogue Amoeba responds to Phil Schiller by jonah on Sunday June 10, 2012 @02:37AM (#4090373)
Yes.
Re:Rogue Amoeba responds to Phil Schiller by mikeash on Saturday June 09, 2012 @12:37PM (#4088454)
Why is it that in every thread discussing Apple's potential misbehavior, people bring up their extreme profitability as if that were somehow relevant to the question of right and wrong? Drives me nuts.
Re:Rogue Amoeba responds to Phil Schiller by recoiledsnake on Saturday June 09, 2012 @01:33PM (#4088581)
I guess the argument(I don't really agree) is that ~99% of their customers don't know about all this and don't care, thus Apple need not care about some random developers because it doesn't hurt sales in the least and that Apple exists to make money for their shareholders and not to foster openness and innovation or necessarily doing what's right for their users.

Also see http://daringfireball.net/2011/03/dirty_percent

Re:Rogue Amoeba responds to Phil Schiller by mikeash on Saturday June 09, 2012 @01:49PM (#4088636)
That would make sense if the argument were, "Apple must do this or else face failure in business," but that's almost never it.
Re:Rogue Amoeba responds to Phil Schiller by drewcrawford on Sunday June 10, 2012 @01:28AM (#4090262)
> When Schiller mentions private APIs, I believe he is not talking about an iPhone private API (which I'm positively sure Rogue Amoeba took great care of not using) but the remote AirPlay API, which they have no right to use without licensing.

A key is not an API. AirPlay is not an API. Full-stop.

Whether Rogue Amoeba was wrong to do this or whether Apple was right to ban them or whether reasonable observers could have predicted the banhammer is not at issue in this thread.

The issue is--Phil Schiller mislead a customer by describing Rogue Amoeba's behavior in a factually inaccurate way. Rogue Amoeba's blog post picks apart these inaccuracies like shooting fish in a barrel. I studied Phil's e-mail and I found exactly one sentence that I thought was accurate.

Sure, Apple can remove this app from the store. They should either just say that, or not respond to the customer at all. Somebody who has made a decision that he/she feels confident about has no need to slant the facts and make misleading statements. Whether or not Apple was right to do this independent of the fact that they were wrong to discredit Rogue Amoeba in an inaccurate way.

Re:Rogue Amoeba responds to Phil Schiller by lloeki on Sunday June 10, 2012 @05:39AM (#4090628)
> A key is not an API.

I never said that.

> AirPlay is not an API.

AirPlay is a remote interface allowing a local application to control software on a remote device and stream data to it. I could implement it over HTTP as a RESTful API or whatever way I see fit and however simple and thin it would be†, it is still a way for applications to programmatically interact through an interface, hence, an API.

But again, this is not a problem since we can now safely implement interfaces without fear.

> Rogue Amoeba's blog post picks apart these inaccuracies like shooting fish in a barrel

... and (assuming that one thinks they scored) misses the elephant in the room. encrypted AirPlay audio streams. Rogue Amoeba knows about this. Apple knows about this. The only party concealing that fact is Rogue Amoeba, and they're entirely disingenuous about it. Since the very first developments (and really, since their announcement of the feature upon release) people have been wondering about the inclusion of the Apple private key; yet Rogue Amoeba stayed quiet on the subject. What I expected of them was at some point to directly answer the question "did we use the Apple private key?" with "yes" or "no".

Again, whether I put a license or not to use my PGP private key, no one has the right to pick up content encrypted for me. They basically created an eavesdropping piece of code.

And this is true for any licensing scheme. If there's no license satisfying my will, I have no right to take it anyway. Rogue Amoeba even goes to admit:

> While Apple licenses the ability for hardware manufacturers to play AirPlay audio, there is no such licensing program for software. When we inquired as to the possibility of this type of licensing being available for software manufacturers in the future, we were informed that it was unlikely.

Then they decided that since there's no license covering that case, they have the rights to build something respecting the AirPlay API (they do) and decrypt data with a stolen private key (they don't). And went on to build it and sell it, get kicked out, complain (rightfully so regarding opacity, laconic answers, and delays), and ignore the most critical part in all subsequent communications. How cool is that?

Now the fact that Apple has no explicit licensing scheme for software manufacturers is a blind spot of their part, but who honestly believes that hardware manufacturers implement their AirPlay receiving devices as pure hardware? I bet the licensing terms could apply just as well to pure software endpoints.

> Whether or not Apple was right to do this independent of the fact that they were wrong to discredit Rogue Amoeba in an inaccurate way.

And the same applies to Rogue Amoeba.

† AirTunes has a HTTP control channel used to negotiate details, AES key exchange via RSA encryption, a remote volume knob, metadata transmission, progress information, and a data channel for audio streaming that can be suspended without closing the stream. http://git.zx2c4.com/Airtunes2/about/

Re:Rogue Amoeba responds to Phil Schiller by drewcrawford on Sunday June 10, 2012 @07:32PM (#4092585)
> AirPlay is a remote interface allowing a local application to control software on a remote device and stream data to it.

The first issue with calling this "using a private API" is that the part of the application under dispute doesn't open a connection to any remote service--but accepts connections from incoming Apple hardware. It is much more correct to say that Apple is "using a private API" in this case.

The second part of the problem is that even if Rogue Amoeba was initiating connections to AirPlay clients (which they are not, at least not the part of the program under dispute), this would not be an "API" as it is usually defined.

For example, OED calls an API:

> a system of tools and resources in an operating system, enabling developers to create software applications.

Wikipedia says:

> In general the difference between an API and a protocol is that the protocol defines a standard way to exchange requests and responses based on a common transport and agreeing on a data/message exchange format, while an API (not implementing a protocol) is usually implemented as a library to be used directly: hence there can be no transport involved (no information physically transferred from/to some remote machine), but rather only simple information exchange via function calls (local to the machine where the elaboration takes place) and data is exchanged in formats expressed in a specific language.

The rest of your post deals with whether Apple is right to do what they did or whether Rogue Amoeba is right to do what they did. Did you even read my reply? In this thread, neither of those two positions are relevant. If Rogue Amoeba had broken into Apple Headquarters and personally tortured Steve Jobs to extract the private key, that would not be relevant. What is relevant is whether Phil Schiller lied and misrepresented Apple's position in a dishonest way.

Let me break down, specifically, the misrepresentations, in numerical form for easy reference:

1. "not accurately recounted on Rogue Amoeba’s website." In what sense exactly is Rogue Amoeba's website inaccurate?

2. "accessed encrypted AirPlay audio streams without using approved APIs" this implies that there exists some approved APIs that RA could have used. Again, whether Apple should or should not provide these APIs is not relevant, what is relevant is that Phil implies that usable APIs exist when they do not

3. "or a proper license" This implies that a proper license exists, see 2. Again, not relevant whether or not Apple should or should not provide a license to RA, only relevant that they imply RA had the option to use it and did not

4. "in violation of Apple’s agreements" This may be in violation of agreements that Apple has with various hardware manufacturers, but this statement implies that RA is bound by these agreements or even knows or can find out what is in them. They cannot. Essentially, Phil is holding RA to a secret standard.

5. "Apple asked Rogue Amoeba to update their app to remain in compliance with our terms and conditions" According to RA, Apple ignored RA's questions for clarification for several weeks.

6. "We have an Airplay licensing program explicitly to assist companies in creating AirPlay capable products." - This implies that RA could have taken advantage of the licensing program and did not. In fact RA could not have taken advantage of the licensing program. Whether this is good or bad is not at issue; the issue is Phil is misleading the customer.

7. "Apple never said that we would pull the rug out from anyone" - iOS guideline 2.20, 3.10, 6.3, 22.7, and others explicitly say that Apple will pull the rug out from under developers. Whether or not these are reasonable or unreasonable guidelines is not at issue in this thread; the issue is that Apple does in fact say they will do it and Phil claims they will not.

8. "we in fact worked with this developer to ensure they update their app and remain on the App Store" For some definition of time elapsed and public outcry; see #5.

I hope this clarifies the issue. Whether RA was right or wrong to extract the private key in the way that they did (or use a private key they got from another source) is not an issue. The issue is: did Phil Schiller lie to a customer? I think I've made a pretty convincing case.

Re:Rogue Amoeba responds to Phil Schiller by lloeki on Monday June 11, 2012 @07:13AM (#4094035)
> this would not be an "API" as it is usually defined.

I beg to differ, and consider both definitions you subsequently give as incredibly restrictive as it would exclude some of the most used APIs in the wild. Everyone in the field will call the Twitter API an API, and everyone will agree that StatusNet implements the Twitter API.

That said, the consumer of the API is indeed AirPlay clients while the API is being served by Apple TV, Airport Express and AirFoil Speakers (Touch). But again this does not matter (and even if we called it a protocol, and really here we have multiple protocols at hand) and RA would have every right to implement it (just as Google implements the Java API, or Wine the Windows API, or StatusNet the Twitter API).

1. It is inaccurate in that it misses one of the most critical points of the discussion.

2. I agree that RA (probably) did not use any non-approved iOS API and that they have every right to implement the AirPlay API/Protocol. I maintain though that they can not make their implementation interoperate with existing AirPlay clients that encrypt the stream. Whether that falls under the "approv[able] API" wording is a stretch, but nonetheless possible. Even RA considered that case in their May 29th post. But this does not matter, since the rest of the phrase is linked to this one with "or".

3. No this does not. This says: "you do not have a license to do that". The fact that no such licensing scheme exists is relevant only in implying that they simply can't do that at all.

4. Apple's iOS developer agreement being quite vague, I'm pretty sure they could fit almost anything they want under this agreement, and this is bad.

5. According to RA, Apple rejected the app because they deemed it non compliant, and as such they "asked Rogue Amoeba to update their app to remain in compliance with our terms and conditions". Not detailing what was not compliant, however rough, does not make the previous statement false. The first Apple answer seems like the usual preset, generic and despicable answer. If anyone takes time to analyze and invalidate an application to such levels of detail, they should disclose their full process and reasons to reject the app together with the app rejection.

6. They do have a program, and it appears to exclude software makers. I find it very sad that it comes to such an escalating situation to at least extend the current licensing scheme to software manufacturers.

7. Agreed.

8. Both the part you cite and the point you make are entirely true, and the second part is simply outrageous. Apple definitely has to improve on that front.

So, did Schiller wrote an inaccurately worded letter? Sure it did. And while they handled the case in a heavy handed and awkward manner, can we call those purposeful lies? It might be, but I'm really not convinced. In the meantime Rogue Amoeba recognizes they "inquired as to the possibility of this type of licensing being available for software manufacturers in the future, [and being] informed that it was unlikely" yet still trying to push the update through approval.

What's more they go on to say, regarding accessing the encrypted content:

> "Quite simply, it is not. While there are multiple layers of encryption involved in the AirPlay audio streaming protocol, their primary purpose appears to be preventing third parties from building applications which interoperate with AirPlay."

In a word, they assumed they had the right to circumvent a mechanism protecting Apple's licensing scheme (however vile we think it is WRT interoperability), made a run for it, were caught red handed, and called out the web regarding the injustice. Maybe they genuinely believe they're right, but that does not make them the good guys.

To sum this up, I believe both sides are at fault, but I'm much more inclined to say that they are all acting in good faith, and that such matters would resolve with much less friction if there was not so much tension (mainly due to delay and opacity, which only increase the uneasy feeling that things are arbitrary) around the review process.

Re:Rogue Amoeba responds to Phil Schiller by drewcrawford on Wednesday June 13, 2012 @06:25AM (#4105198)
> I beg to differ, and consider both definitions you subsequently give as incredibly restrictive as it would exclude some of the most used APIs in the wild.

You'll have to take that up with OED and Wikipedia. I think it's fair to say that at the point that they agree with each other and disagree with us that we're the ones using the words wrong rather than them, and it's us who need to invent new words rather than they. That's what it means to be a language authority.

#1 seems like an overall summary statement so my response is implied by the below

#2 I can't detect any disagreement

#3 - "you do not have a license to do that" - They also don't have a license to rent a bouncy castle. Phil isn't listing things that they don't have a license to do, he's (attempting to) explain why Apple rejected the application. He's implying that a license exists.

4. The word "violation" has a specific legal meaning. In this case, I can tell you for sure that he's specifically referring to agreements that Apple has with hardware manufacturers (which actually say you cannot do this explicitly), which RA has never read

5. I will concede that Phil's statement is technically correct, but when you consider how the average customer would interpret this statement, it leads them to an incorrect conclusion.

6 & 7 - No point of disagreement that I can detect.

8. No point of disagreement that I can detect.

> can we call those purposeful lies?

Phil is on the board of directors of a publicly traded company and society holds such people to an extremely high standard of honesty. I'm not sure why the word purposeful is of any relevance, but they're certainly misleading statements and Phil Schiller is not employed by Apple to blab whatever he thinks of to say to random customers.

> In a word, they assumed they had the right to circumvent a mechanism protecting Apple's licensing scheme (however vile we think it is WRT interoperability), made a run for it, were caught red handed, and called out the web regarding the injustice. Maybe they genuinely believe they're right, but that does not make them the good guys.

The following set of words: {right, vile, made a run for it, red handed, called out, injustice, good guys} ascribe a certain moral narrative to this situation that I do not subscribe to at all. There are a lot of very worldviewish questions in here (e.g. what it means for a software company to be moral, whether morality can be meaningfully ascribed to a company, etc.)

I don't mean to dissuade you of these views, because I imagine that if we take the time to wade through it, we will discover that each other's positions are pretty reasonable. But that would require us to wade through a lot of psychology, philosophy, religion and ethics to arrive at that point, and so in the interests of time I would recommend steering clear of ascribing particular ethical conclusions to the actions of actors except in the narrow cases where it is actually important, in which case we must be willing to defend it at some length.

One such area (of valuable exploration) is whether, assuming Phil made misstatements in his e-mail, it was morally correct to send. I think we agree on enough of the points to conclude that these misstatements did exist, and so the problem reduces to whether a corporate director sending misstatements to a customer is immoral. From your reply, the operative test seems to be whether they constituted a purposeful lie which is, at the very least, an interesting test.

Re:Rogue Amoeba responds to Phil Schiller by dhugiaskmak on Saturday June 09, 2012 @12:06AM (#4087151)
I don't know how you can come to the conclusion that this is an arbitrary decision by Apple, or that Apple is lying about something in the matter. It seems clear to me that even though Apple keeps using the term "approved API" what they mean is "the AirPlay encryption key that you don't have a license for". It's an odd use (or misuse) of terminology but it doesn't change the facts.
Re:Rogue Amoeba responds to Phil Schiller by noibl on Saturday June 09, 2012 @12:55AM (#4087233)
It's more than terminology.

"We have an Airplay licensing program explicitly to assist companies in creating AirPlay capable products. Apple never said that we would pull the rug out from anyone, we in fact worked with this developer to ensure they update their app and remain on the App Store"

The clear implication there is that Apple had procedures available for getting this to work and RA just ignored them. RA's response directly contradicts this.

P.S. thanks for the unexplained downvotes.

Re:Rogue Amoeba responds to Phil Schiller by rbritton on Saturday June 09, 2012 @01:19AM (#4087290)
RA did state that they inquired as to licensing it for a software product and were told that there were no plans to make that available. So, they didn't ignore the procedures as much as they ignored the response.

In the end it's Apple's store with Apple's rules. The rules have changed without warning in the past and will likely do so countless times in the future. The tradeoff for this is what is likely one of the most lucrative app stores to date for developers.

Re:Rogue Amoeba responds to Phil Schiller by cheatercheater on Saturday June 09, 2012 @04:41AM (#4087625)
Except if you build a system to which millions (yes, millions) of people contribute in one way or another, pretend everyone's invited, and then decide to do something very self-righteous against the good of nearly anyone else involved just in order to feed your fat butt, then you are labelled an oppressive, opportunistic sociopath, and very rightly so.
Re:Rogue Amoeba responds to Phil Schiller by batista on Saturday June 09, 2012 @02:24PM (#4088807)
The never pretended "everyone's invited".

In fact, the first iOS didn't have third-party apps, and when the API finally appeared, it had very clear restrictions and a $99/year fee attached.

Re:Rogue Amoeba responds to Phil Schiller by cheatercheater on Sunday June 10, 2012 @02:42AM (#4090384)
Sadly, that's not the way it's being marketed to the masses of developers. You're talking about what seems to be a technical detail to someone who's been corporate-brainwashed by the apple reality distortion field (maybe they're keeping Jobs in stasis in order not to lose it?). Then, SURPRISE!!! it's not such a technical detail after all, apple has tricked you so! It's like a surprise birthday party, except your gift is a burning bag of dog poo.

Typical corporate trickery. The reason a lot of people fall for it is because they have an open mind (definitely advocated by Apple) and therefore are gullible (definitely wanted by AAPL).

Having written something somewhere doesn't make you less of an asshole for handling in a dirty, asocial way.

Re:Rogue Amoeba responds to Phil Schiller by omfg on Friday June 08, 2012 @11:55PM (#4087130)
What? Schiller lays out the reasons the app was rejected quite clearly. Rogue's response is to suggest that these issues are ambiguous because it hasn't been clearly defined by Apple. Well, guess what, now it has. Rogue should've just let it go.
Re:Rogue Amoeba responds to Phil Schiller by taligent on Friday June 08, 2012 @11:53PM (#4087123)
I agree that it is ridiculous the way Apple basically changes the rules as it goes along. I just don't understand the outrage or surprise. There has been 3 years of developers trying to bend the rules and posting complaints like this.

FACT: They reverse engineered Apple's proprietary technology and want Apple to help sell their app.

MY POINT: You must be nuts if you think that will happen.

Re:Rogue Amoeba responds to Phil Schiller by dfxm12 on Saturday June 09, 2012 @12:05AM (#4087147)
I just don't understand the outrage or surprise. The moment we get complacent is the moment we lose. What's the worst that can happen from trying or speaking up? At worst Apple says "no", and maybe the public becomes more aware of the situation and thus might feel compelled to apply pressure to Apple. This is the reason for the outrage.
Re:Rogue Amoeba responds to Phil Schiller by fpgeek on Saturday June 09, 2012 @12:12AM (#4087160)
One interesting question is whether or not this sort of thing will be grounds for revoking a Gatekeeper certificate. Apple certainly could argue that accessing AirPlay streams without proper authorization is a form of malware / something they have to police because of agreements with content providers / etc
Re:Rogue Amoeba responds to Phil Schiller by parley on Saturday June 09, 2012 @05:14AM (#4087681)
I know commenting just for the sake of agreeing is advised against, but this time I had to. If there's an outrage over app store rejection for these reasons, then imagine the reaction to gatekeeper cert revocation for the same reasons.
Re:Rogue Amoeba responds to Phil Schiller by fpgeek on Saturday June 09, 2012 @06:33AM (#4087796)
That's the thing. To me the level of outrage seems startlingly low, plus Apple seems generally impervious to outrage in general. In my opinion, this does not bode well for the future.
Re:Rogue Amoeba responds to Phil Schiller by dmbaggett on Saturday June 09, 2012 @11:41AM (#4088323)
It's Apple's store ergo their rules.

Subject to the rule of law, of course.

Re:Rogue Amoeba responds to Phil Schiller by wmf on Saturday June 09, 2012 @12:02AM (#4087140)
Goading Apple into breaking their own rules is a bit trollish, but when all else has failed maybe trolling is what we need.