Can't they provide a build through sideloading in an alternative app stores? I'm confused with what the technicals limitations of sideloading are and what Mozilla would preferably do.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations, i'd even say it is a reason for why i still don't buy an ipad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
I was under the impression you still need the entitlement from Apple for JIT, even when you publish to alternative app stores. The only way to get that entitlement is to go through Apple's process here for EU and Japan (or tethered workarounds that may be closed at any time)
Isn't that because alternative browser engines are region-locked, so you'd need to have a WebKit version and a non-WebKit version for different regions?
This includes a long list of strict requirements, some of which are hypocritical because Apple itself doesn't follow them, e.g., "Prioritize resolving reported vulnerabilities with expedience, over new feature development" and "Most vulnerabilities should be resolved in 30 days".
One requirement that Mozilla mentions in their blog post: "Not sync any state (including cookies) between the Alternative Web Browser Engine App (EU) and any other app, even another app of the same developer, unless the user has explicitly given permission for state to be synced, either by signing into both the Alternative Web Browser Engine App (EU) and the other app, or through another mechanism of providing explicit permission"
Hm, perhaps antimonopoly branches of governments should fine companies for monopolistic behavior in other countries. Because clearly that behavior harms customers in their jurisdictions.
Btw, i stand with Mozilla on the overall issue here, Firefox should be permitted as is, in the official app stores, unencumbered by any artificial limitations, i'd even say it is a reason for why i still don't buy an ipad, because i'd like to have the same browser than on my desktop os, Firefox, and not a reduced version, ie. its full proper implementation.
I'm confused about this part. Is there some sort of code signing requirement that wouldn't be available to the "original" Firefox iOS app?
This includes a long list of strict requirements, some of which are hypocritical because Apple itself doesn't follow them, e.g., "Prioritize resolving reported vulnerabilities with expedience, over new feature development" and "Most vulnerabilities should be resolved in 30 days".
One requirement that Mozilla mentions in their blog post: "Not sync any state (including cookies) between the Alternative Web Browser Engine App (EU) and any other app, even another app of the same developer, unless the user has explicitly given permission for state to be synced, either by signing into both the Alternative Web Browser Engine App (EU) and the other app, or through another mechanism of providing explicit permission"