Mozilla Project Fusion: Tor Integration into Firefox

Post by anonymfus » Sat, Jun 02, 2018, 3:24 AM UTC

dat_boi20 wrote: post #144

tomrittervg wrote: post #137

Earlier quoted context omitted.

The Fusion project is done by a subset of that team (+me, I happen to sit with Sandboxing due to other responsibilities).

By passing this on to Mozilla and discontinuing Tor Browser, you're going to inherit the innumerable issues in their code base. Wouldn't it be easier to hard-fork and create a simple browser with minimal overhead? It doesn't have to be loaded with features. Just minimalist and private. Some anti-features that come to my attention off the top of my head: * Biometric login (as of FF60) * Dumb PR Stunts like Mr. Robot *…

Post by mtgx » Sat, Jun 02, 2018, 4:39 AM UTC

jean- wrote: post #130

openfuture wrote: post #123

Okay but what about maidsafe, dat, ipfs etc. The correct solution is to have firefox expose a 'protocol api' or something along those lines so that any 'alternate internet' project can create a backend extension to make firefox compatible with that protocol.

Seems like some people are working precisely on that. See for instance: https://blog.mozilla.org/addons/2018/01/26/extensions-firefo... (CTRL-F Decentralization) https://github.com/mozilla/libdweb

Post by icelancer » Sat, Jun 02, 2018, 5:01 AM UTC

xoa wrote: post #145

tomrittervg wrote: post #100

Hi all. I am a Tor Project Developer and work at Mozilla on this project. We appreciate everyone's enthusiasm and feedback. Our ultimate goal is a long way away because of the amount of work to do and the necessity to match the safety of Tor Browser in Firefox when providing a Tor mode. There's no guarantee this will happen, but I hope it will and we will keep working towards it. If anyone is interested in assisting…

> You can also run Tor relays and help us improve the health of the network by working with Tor's new Relay Advocate Since I've seen this come up before in many previous discussions of Tor I think it's worth emphasizing/clarifying up front: Tor relays are not the same as Tor exit nodes. Relays do not talk to the public internet, they serve only the full encrypted internal Tor virtual network. So they won't ever send…

Post by ec109685 » Sat, Jun 02, 2018, 5:16 AM UTC

bunkydoo wrote: post #185

I believe Tor browser is already just a version of Firefox if I'm not mistaken. What would be the advantage of integrating with Firefox as opposed to say, a VPN integrated into the browser via a plugin. Just seems a little redundant and Tor is beginning to seem dated also with new solutions popping up and making the pitfalls of Tor more apparent.

Post by kragormonkey » Sat, Jun 02, 2018, 5:33 AM UTC

icelancer wrote: post #225

xoa wrote: post #145

Earlier quoted context omitted.

> You can also run Tor relays and help us improve the health of the network by working with Tor's new Relay Advocate Since I've seen this come up before in many previous discussions of Tor I think it's worth emphasizing/clarifying up front: Tor relays are not the same as Tor exit nodes. Relays do not talk to the public internet, they serve only the full encrypted internal Tor virtual network. So they won't ever send…

And plenty of people insist that Tor relays are totally safe to run. They are not. I NEVER ran an exit node from my home IP, only relays, and my IP was still blacklisted from various sites due to this behavior. I still contribute to Tor via VPS rentals and such, but relays are not no-risk alternatives to exit nodes. Period.