News for hackers. Stuff that matters.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by aidenn0 on Tuesday May 05, 2020 @10:17PM (#23087330)
An actual firefox for iOS is disallowed from by the app-store rules.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by kccqzy on Tuesday May 05, 2020 @10:44PM (#23087465)
There is a Firefox Focus though: https://apps.apple.com/us/app/firefox-focus-privacy-browser/... I use Firefox Focus almost every day, mainly for "focused" browsing, i.e. one page at a time, no tabs; without tabs and the urge to open links you really get to focus on the current page more. It has some content blockers capable of blocking ads and trackers too, although in my regular browsing I use 1Blockers for configurability (say, disable cookies on news sites).
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by toyg on Wednesday May 06, 2020 @08:05AM (#23090018)
> There is a Firefox Focus though

It's still built on WebView.

Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by kccqzy on Wednesday May 06, 2020 @10:09PM (#23098904)
Yes. But this article is about the browser called Firefox, not the rendering engine called Gecko. It is somehow common for HN commenters to conflate these two, or think that the rendering engine is the "soul" of the browser, a view I do not agree with.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by ohbleek on Tuesday May 05, 2020 @11:17PM (#23087602)
+1 for firefox focus, it is the browsing app I use for iOS unless I want to come back to something later then I'll open it in safari, from focus
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by jedberg on Tuesday May 05, 2020 @10:20PM (#23087348)
I know. That’s why I was excited. I thought they found a workaround.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by enitihas on Tuesday May 05, 2020 @10:55PM (#23087509)
Even if they find a technical workaround, Apple will just reject the app though. Not sure there is a workaround for that.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by yjftsjthsd-h on Tuesday May 05, 2020 @11:10PM (#23087575)
I'm given to understand that it's not even a technical issue; you can build an iOS app that uses a real browser engine of your choice, it's always just been that Apple by policy won't let you publish it. (This is all second-hand, though, so take with a grain of salt.)
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by pedrocx486 on Wednesday May 06, 2020 @12:00AM (#23087788)
You're correct, no need for grains of salt. Hence why some apps that are in jailbreak "stores" can do things apps from the store can't.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by yjftsjthsd-h on Wednesday May 06, 2020 @01:44AM (#23088202)
Yeah, I was pretty sure but I don't actually operate in that sphere at all so I'm working completely from random stuff I remember reading:) Thanks for confirming.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by aerique on Wednesday May 06, 2020 @08:57AM (#23090371)
My jailbroken iPhone 3GS was the best mobile experience I've had. Used that thing for 5 years.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by enitihas on Tuesday May 05, 2020 @11:32PM (#23087660)
Does iOS allow creating new executable pages?
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by swiley on Wednesday May 06, 2020 @12:16AM (#23087849)
Nope. (Well, maybe iOS would allow it with the correct entitlements but apple won’t let you publish an app that can.)

You can run a browser in an interpreter but anything modern would be very unpleasant to use that way.

Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by yjftsjthsd-h on Wednesday May 06, 2020 @01:43AM (#23088198)
I expect there are 2 options: Either you can make a good (fast) browser without it (unlikely or everyone would do it), or it is possible to do because Safari has to work somehow.

> apple won’t let you publish an app that can

Agreed, but we're talking about whether you can technically make such an app, say to run in dev mode on your own personal device.

Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by fragmede on Wednesday May 06, 2020 @03:46AM (#23088761)
Dev mode is still limited and doesn't grant root access to the device. In dev mode there's still an app certificate, and Apple still signs it, and still prohibits escaping the app sandbox. There are also JIT specific entitlements to allow an app to dynamically load or generate code. Without those, it's unclear how feasible a developer-signed version of Firefox on iOS is.

https://siguza.github.io/psychicpaper/ is a recent writeup that includes more details on (escaping) the limitations.

Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by jlokier on Wednesday May 06, 2020 @10:26AM (#23091299)
> it is possible to do because Safari has to work somehow.

Safari is a special case. It is allowed to use JIT and writable executable pages, but this is not allowed for third party apps.

It is definitely technically possible on iOS, but a significant challenge for third party developers unless using a jailbroken device.

Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by enitihas on Wednesday May 06, 2020 @02:27AM (#23088372)
Safari might be special cased though.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by userbinator on Tuesday May 05, 2020 @11:10PM (#23087574)
I believe jailbreak or those other "developer" methods (certificates/enterprise?) are still available.
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by enitihas on Tuesday May 05, 2020 @11:33PM (#23087664)
Yeah, both of them will see mozilla kicked out of App Store
Re:Firefox for Mobile now supports NoScript, PrivacyBadger, ... by gnicholas on Wednesday May 06, 2020 @12:51AM (#23088006)
Same here. I was hoping that since these are "recommended" addons, perhaps they had negotiated with the developers to make them freely available and just included them in the build as features the user can enable if desired.