Live data from Hacker News

Mozilla Project Fusion: Tor Integration into Firefox

trac.torproject.org

191–200 of 242 posts

Re: Mozilla Project Fusion: Tor Integration into Firefox

#191
post #70

Earlier quoted context omitted.

Which sites in 2018 still present multiple CAPTCHAs to users with cookies and JavaScript enabled? I think the theory behind this project is that those problems are primarily caused by Tor's popular image as a 'fringe network for pedophiles and drug dealers' and that by making it more mainstream they can fix those issues. (please more replies saying "that sounds really hard" and less replies saying "tor is not a fring…

Cloudflare.

Source? Cloudflare did post a moderately hostile response to Tor a few years back, but their technical implementation is sound and does not present multiple CAPTCHAs to users who have cookies enabled (the CAPTCHA might be broken with JS off, but that's a Google problem).

Re: Mozilla Project Fusion: Tor Integration into Firefox

#192
post #169

So we lose another valuable project of the Web. I wonder why I feel so lost - that when I was young, the Internet was barely born... and now I'm watching it die.

I agree and I don't really like how the internet is evolving either but this sounds like one of the good changes, unless I'm missing something

Re: Mozilla Project Fusion: Tor Integration into Firefox

#194
post #132

Earlier quoted context omitted.

But everyone and their cousin is a WhatsApp user, so using Whatsapp isn't suspicious.

So the solution is to grow Tor usage, or use bridges with pluggable transports.

No, using Whatsapp is a more efficient solution.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#195

Earlier quoted context omitted.

Blizzard games no longer use BitTorrent but a proprietary http-based protocol called ngdp. BitTorrent was causing a lot of issues with firewalls so users were disabling it, so they had added http mirrors to them... And then CDNs became a thing, the rest is history. I'll be happy to give more details on ngdp if you are curious.

Please.

Here, I pulled my docs for ya:

https://gist.github.com/jleclanche/91f2f5c0f2042a81db1c61464...

They basically created their own git protocol + virtual filesystem, optimized for asset patches inside large compressed binary files. I wish they'd open source it.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#197
post #87

If I understand it correctly, you shouldn't be using any website accounts using Tor browser that you also use outside of it. I really wonder if/how they can make the user properly aware of that in a kind-of super private browsing mode.

"Multi-Account Containers"

I'm not quite sure what you mean by this comment, but if you mean that their approach would be similar to MAC, in the sense that "super private browsing" would have to be enabled in about:config or through an extension: that would make sense.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#198
post #87

If I understand it correctly, you shouldn't be using any website accounts using Tor browser that you also use outside of it. I really wonder if/how they can make the user properly aware of that in a kind-of super private browsing mode.

you can , and it is still a valuable contribution to the Tor network, since it adds cover traffic. the catch is just that the website you're using will know who you are. I hope that the vast majority of users will understand that if they log in, there is no privacy mode that will save them from the site they log into.

Right, I guess that's good if you want to contribute to the Tor ecosystem, but if you want to browse anonymously, that's no good. Unfortunately, even as a somewhat tech savvy (though in hindsight obviously naive) person, the repercussions of logging in somewhere in Tor Browser weren't immediately clear to me.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#199
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…

That said, plenty of providers use the list of tor relays (which is also public) to block traffic. Sites such as https://www.dan.me.uk/dnsbl then help people do this. That site in particular may "warn": > This DNS blacklist contains ALL tor nodes (entry, transit and exit nodes) - think carefully before choosing to use this list for blocking purposes. but anyone who doesn't understand tor simply won't understand the d…

One way to help that avoids this is to operate a bridge node. Bridge nodes are used as entry points into the Tor network for people in regions where Tor is blocked, so efforts are made to keep the addresses of bridges confidential. Which makes it less likely that people who don't know what they're doing will wrongfully put it on a block list.

Re: Mozilla Project Fusion: Tor Integration into Firefox

#200

Earlier quoted context omitted.

> first party isolate is generally more stable and usually only has breakage on particular login forms Are you referring to third-party login services and comment systems (such as disqus and similar)?

> Are you referring to third-party login services and comment systems (such as disqus and similar)? See the full list of bugs of breakage when privacy.firstparty.isolate is enabled: https://wiki.mozilla.org/Security/FirstPartyIsolation#First_...

Most of those involve third-party logins. And most of the others mix domains unnecessarily, through lazy design.
Post reply on HN