No, notarization is about preventing malware. That's all. This has been promised to us by Apple many many times. Malware prevention only. Fortnite is not malware.
Notarization is not a stick-less carrot. Anyone can sign up and agree to the rules and pay the fee begin notarizing apps. If you break the rules you agree to when you sign up, you lose access to notarization.
It seems like we disagree about this basic understanding, so I'll take a couple guesses at it.
Are you, perhaps, arguing that Apple should not be allowed to terminate developer access to notarization under any circumstance — regardless of their behavior? Or are you arguing that Epic's behavior is "acceptable" rule breaking, but other kinds of behavior are "unacceptable" rule breaking?
I'm happy to consider that I could be wrong here, but I'll need a few more sentences from you to do so.
Since most people are essentially prevented from running non–notarized macOS software, Apple should treat notarization as a rubber stamp. As long as your app is not literally malware, Apple should notarize it.
Apple's use of notarization as a stick for Epic here certainly goes against if not the letter, then the spirit of their developer documentation: [1]
> Notarization gives users more confidence that the Developer ID-signed software you distribute has been checked by Apple for malicious components. Notarization is not App Review. The Apple notary service is an automated system that scans your software for malicious content, checks for code-signing issues, and returns the results to you quickly. If there are no issues, the notary service generates a ticket for you to staple to your software; the notary service also publishes that ticket online where Gatekeeper can find it.
[1] https://developer.apple.com/documentation/xcode/notarizing_m...
1. You can submit software anonymously, or with a free account, or with a paid account.
2. Apple can refuse notarization for the usual reasons they do now.
3. Apple can, in the future, revoke notarization and notify you.
3a. If you choose to submit anonymously, notification is impossible.
3b. If you choose to submit with a free developer account, they'll notify you of revocation and why.
3c. If you choose to submit with a paid developer account, they'll allow you to contest the revocation.
At the very least such decisions should be subject to appeal to an independent board, and failing that the legal system.
Should they have not exercised that right, and left us all at risk — even though the daemon itself wasn't malware, nor had it been abused for such purposes by anyone?
Checks and balances are not a new concept.
If Apple wants to suspend someone's App Store developer account, fine. But you should be able to distribute outside the App Store regardless.
The whole point of distributing outside the App Store is to avoid all that nonsense with Apple's rules.
Does the sale require me to submit payment details to a not-already-trusted platform?
The change remotely triggered by Epic redirects users to a third-party (Epic) payment system, but what if it were, say, a malicious Epic insider? How much user payment info/cash could they grab before they were detected and disabled?
"2.3.1 Don’t include any hidden or undocumented features in your app; your app’s functionality should be clear to end-users and App Review."
In old sci-fi books, there's a couple that describe a future where connecting an old device to the Internet without having first installed updates will result in the device being exploited and/or ruined within a few seconds.
I notice that the Xcode worm was reposted again this morning, which seems like the perfect mechanism for covertly preparing for a worldwide hack of all iOS devices through a backdoor that has been compiled into all software. (You could get a similar effect by introducing malware into CocoaPods, and with similar reach.) All of these protections Apple has with Gatekeeper and Notarization would, to many extents, protect end users against that attack.
As you said, it's definitely a broad brush. The risk is absolutely real, though I imagine we all disagree on how important it is. It's the same problem as the risk of Python/Ruby/Node dependency compromises. Any solution that would work for protecting us against an NPM compromise would also work for protecting us against a macOS software compromise. Apple's solutions have a higher total value of protection, in exchange for a higher total value of bothersome.
Is the NPM model (you can ship any code worldwide, have fun!) safe enough for non-technical users, such that Apple could just drop Gatekeeper and let us all go back to the wild west macOS days? If not, what model is acceptable, given that Apple's model isn't?
Well, it kinda is, isn't it?
> Programs are also considered malware if they secretly act against the interests of the computer user.
Is convincing children that they need to spend money to not be a "default" really in the interest of a computer user? Is taking advantage of gambling addictions with lootboxes really in the interest of a computer user (or society at large)?
I get what you really mean, and I'm probably stretching the definition a bit much; Yet it's worth considering if Fortnight is really a good thing in the first place.
That's a fine argument to make, but it's nothing to do with what we're discussing here :)
If you wrote a blog post about how Apple and Google should ban gambling reward techniques from their app stores, I'd read it if you posted it to HN!
Well, except we're talking about how these measures are generally reserved for malware. Thence my (pseudo) logic chain.
IMO that's a fine conversation to have, but it is not Apple's place to make that decision for me.
Apple and Google are hardly faultless, but Epic is is the one who started this dick-measuring contest.
I don't think "snuck" is accurate. They did intentionally do it, but it was likely pretty obvious to the app reviewer. This was necessary, because you can't sue a company because they'll harm you for something you'd like to do, but haven't done yet. You have to do the thing, get harmed, and then sue.
> Apple could have revoked their developer certificate in response, which would have essentially killed all installations of Fortnite iOS/Mac worldwide within 24 hours. That they are merely revoking their ability to sign new code and giving them 2 weeks to perform an orderly shutdown is far less draconian than they're capable of being here.
Don't pretend they're doing this to be nice to Epic; they know that if they cut off all existing Fortnite users, they'd get a huge amount of customer complaints and bad press. At least here they can appear like they're being reasonable and only hurting the company that violated their policies.
Well, presumably only in-app purchases made with apples payment system.
Apple says "you can't do this", but Epic does the thing and says "I should be allowed to do this. As you can all see, this is what happens when I try to put my foot down on it and here's this target audience of people who are benefited by the thing I'm trying to do". This works for them because they are advocating for a freedom of software choice and to rebel against the massive profit line that has made Apple the target of Spotify's legal hate as well.
The rules they broke prevent Epic from doing a thing that consumers would prefer (lower prices) and has been argued against by other parties (30% cut). It doesn't really matter that they broke the rule if the court of public and legal opinion is that the rule was not good to begin with.
Forcing me to give them to Apple is, if I prefer to give them to Epic and hide them from Apple
Guess which one is the only Apple approved option
Yeah isn't that what people see as a problem?
> Notarization is about protecting users who are not capable of making an informed decision about code safety from developers who refuse to comply with Apple's terms of service.
My family owns a Mac on which we have played Fortnite in the past. We have no desire to be "protected" from Epic Games. I thought to point of notarization was to prevent malware, not to punish companies which Apple doesn't like.
If Apple was about user protection then one would expect there to be a way for users to opt out of their safety sandbox if it didn't fit users needs.
Their OS and store restrictions are about monetising the ecosystem as much as anything else, calling developers who try to circumvent the apple tax greedy while pretending Apple is doing this purely for user experience is some cognitive dissonance.
It takes a real sucker to fall for the “its for your own safety” propaganda while they arbitrarily tax you 30% on the fields you tilled like some medieval feudal lord.
You're conflating two things here: code safety, and what Epic did. At no point did Epic do anything unsafe, nor did they put their users in any danger. They simple violated a business rule Apple enforces.
You are arguing that Apple is incorrect to assert that rulebreakers should not have privileges to deploy code to end-user devices worldwide, when the rule is not one that protects users.
Apple's counter-argument would presumably be that this business rule exists specifically to protect users from being harmed by developers, given the prevalence of "free trial" subscription scams over the past X decades of Internet marketing (and before that, TV commercials).
So, I don't buy the argument that Epic did nothing unsafe. It takes seconds to construct multiple scenarios where users have been abused by third-party payment systems, such that Apple would consider them "malicious behaviors that impact the user".
ps. There's a technicality branch here on "malware" != "malicious behaviors", but, like, malicious payment processing is implemented using software, "malware" is "malicious software", so "malware" still applies to the scenario I constructed above — and that flexibility demonstrates why "malware" is a terrible abbreviation for whatever everyone individually thinks it means.
I shudder at the thought.
I very much categorize Epic's actions in the "unsafe" basket.
This is exactly what apple tried to prevent (snd is earning a shit ton money with it): manual credit card entry because except the big ones almost no one would be safe
Imagine that
Imagine a world where people buy things on a website let's name it Amazon
Or pay for online auctions using something very sketchy, something like a PayPal
Imagine paying online for cabs, food delivery, books or to rent a movie or a BnB on the other side of the World, to buy a flight, theater, museum ticket
What a wild wild west it would be, we will be fighting each other like crazy if it wasn't for Apple that saved us all from ourselves...
That's not even the case here.
Epic built an app using webviews and the web part of the view is loaded from a remote server controlled by Epic.
Which is the most common way to build multiplatform apps nowadays.
Epic simply updated the web part on the remote server.
Which also proves Apple can't even provide the basic safety they are promoting to push notarization.
Unless they ban webviews completely, we will never know how many apps are already doing it exploiting the less tech savy users, but still bringing profit to Apple.
I used to do consulting work as part of which I submitted Mac compatibility patches into the Unreal Engine source code repository. As is, it is not clear to me if I'll be hit by the Apple ban-hammer, too, or if they will limit it to "only" the 4000+ people directly employed by Epic.
This is why I want Epic to lose.
This type of people need protection.
Notarization is about protecting users who are not capable of making an informed decision about code safety from developers who refuse to comply with Apple's terms of service. Epic willfully violated their terms with Apple to make a point, and Apple is responding in the same way that they did to Facebook: taking away their access to the users, because they cannot be trusted to comply with the restrictions placed on their behavior.
Most (if not all) of the restrictions on the App Store exist to protect users from app developers who prioritize their own greed over the rights of privacy and safety that Apple promises the users of the App Store. Developers are the threat model, and there's nothing inherently wrong with Apple's response to Epic declaring themselves a rulebreaker — and, thus, a threat.
(If Epic was not trying so hard to be able to sue for damages, they might have been able to negotiate, same as Facebook did. But they wanted to be a martyr for the cause, so here we are.)
Consider this thought experiment: At your employer, an IT employee goes rogue and installs malicious code on your computer to read your email. How would you feel if IT leadership said "they promised not to do it again" and allowed them to continue unsupervised work on your computer while you're away? Most people would feel awful, because you can't trust the IT employee's word — they literally just broke their agreement not to snoop! — and because your leadership clearly doesn't care about your privacy.
Should Apple "fire" Epic, now that Epic's word can no longer be trusted? This answer should, in theory, match the answer above. I bet for most software developers, it does not. I encourage thinking through that dissonance rather than rejecting the thought experiment.