51–60 of 206 posts
Yes, yes, yes. Even if this doesn't work out in the long-run. This is what I want Mozilla to be focusing on: privacy-first browsing experiences.
Code at https://github.com/mozilla-mobile/focus - feel free to file issues/bugs/questions on Github. We primarily use Bugzilla for this project, but happy to move bugs around.
Why having a separate application with these features instead of adding them to Firefox for iOS ? Is it planned to have content blockers support in Firefox for iOS ?
I can also use this without worrying about mix ups that I sometimes end up with in other browsers where I use both private and non-private tabs.
Edit: Seems a bit slow. Need to use it more to get better measurements.
Code at https://github.com/mozilla-mobile/focus - feel free to file issues/bugs/questions on Github. We primarily use Bugzilla for this project, but happy to move bugs around.
Why having a separate application with these features instead of adding them to Firefox for iOS ? Is it planned to have content blockers support in Firefox for iOS ?
Firefox is based on the WKWebView. Modern and Fast, but has a very poor (thin) API. It has zero options for interacting with the network stack, which is a requirement for content blocking. Bugs have been open since iOS 8, Apple does not seem to be interested or does not have the resources to surface more API. All the APIs are in WKWebView, just private.
Focus uses the older UIWebView. Slow, but better ability to interact with the network layer. Not ideal, but at least it is possible.
So to answer your question: We would have to replace WKWebView in Firefox for UIWebView. We've been very close to doing this in some form. But it is is big compromise in terms of functionality and stability. So I am not sure when and in what form that will happen.
Stuck between a rock and a private API.
The opposite of privacy: every address you type in Firefox Focus gets sent, live, to Yahoo/Verizon, complete with a User-Agent identifying the request as coming from Focus, indicating an unusual desire for privacy.
Since this user's response to their own comment was killed (not sure why) I'll repeat: this is incorrect. Domains are chosen from a hard-coded list: https://github.com/mozilla-mobile/focus/blob/master/Blockzil...
Further info:
1) Appears the Brave browser uses the same hardcoded suggestions list. Why have such a list?!
2) If you are really concerned about privacy this is still a bad option because accidental hit of Go/Search/Enter sends an incomplete address to Verizon/Yahoo -- with no choices to disable this or chose another destination.
Code at https://github.com/mozilla-mobile/focus - feel free to file issues/bugs/questions on Github. We primarily use Bugzilla for this project, but happy to move bugs around.
This looks really good! Not sure if this is worth opening an issue over, but are you planning on supporting search engines other than google?
I was really looking forward to trying this browser and wonder what the hardware limitation is.
Code at https://github.com/mozilla-mobile/focus - feel free to file issues/bugs/questions on Github. We primarily use Bugzilla for this project, but happy to move bugs around.
The submission describes an app, yet the readme here describes a content blocker. Is this the correct repo?
Earlier quoted context omitted.
Content blockers require a 64 bit CPU. This is an Apple requirement
I expected that, but that's an unfortunate side effect of coupling the new browser app with the previous content blocker app. (Just found out that it's not compatible with my iPad 4)