Mike thinks we're not that far from being able to try a Tor Browser Bundle build on Android.
The main blocker he sees currently is Torbutton, since "FF mobile's crazy multi process model breaks various listeners in strange ways" and "Torbutton listens to a ton of request observers that are complicated by a multi-process model". See #5279 (closed) and #3100 (closed) for subtasks Mike expects will be needed along the way to making Torbutton work for FF mobile.
But in the mean time, we could make a Tor Browser Bundle with Proxy Mobile as the proxy forcer addon. (Nathan, how much does that plan differ from how Orweb works today?)
Then it would be an incremental set of steps for Mike to add Torbutton-like features into Proxy Mobile. Specifically, Mike says "I think the way to go is to copy+paste torbutton features into that thing, starting with easiest-first. And if that goes well, we'll start using it on the desktop, too (since we want to gut so much shit out of desktop torbutton anyway)"
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
To be clear, I'm not volunteering to port the Torbutton pieces to ProxyMobile myself, but I am happy to instruct+assist someone else who is hired to do so as part of deploying TBB on Android.
I am working to find someone to pay/bribe/entice to do this. I think the approach outlined is valid.
The other idea that Jake had was instead of going the add-on right, to instead just compile Fennec source code with all the proper defaults needed, and ship that as Tor Browser for Android.
The other idea that Jake had was instead of going the add-on right, to instead just compile Fennec source code with all the proper defaults needed, and ship that as Tor Browser for Android.
Yeah, that's compatible with what I'm suggesting. Our Tor Browser builds for the desktop include a prefs.js with all of the prefs for Torbutton already set. This makes settings prefs from the addon itself one of the things you don't need to carry over in the cut and paste job. However, there still will be other things to do beyond pref setting.
The extension porting is what makes this a large task, but it's probably right on the border.. If it can be combined with another extension developer task after the initial port for maintenance, it might be about right for one person.