It would be fine to just have the feature so .oninon sites are accessible. To get more than that requires education, much like an aircraft pilot. One small mist

It would be fine to just have the feature so .oninon sites are accessible. To get more than that requires education, much like an aircraft pilot. One small mistake and you may literally get yourself and others killed. Even Tor Browser can't be trusted, due to bugs. A bare beginning solution is a firewall to block non-Tor connections: http://www.reddit.com/r/onions/comments/1l15hx/10_steps_to_make_tor_safer_with_pfsense/ http://www.reddit.com/r/onions/comments/1l15hx/10_steps_to_m... Without that, you're just the Titanic happily floating across the ocean without making sure you've got enough lifeboats if something goes wrong. Should failure always mean death? Is it too much to ask to insist on a firewall safety net to block non-Tor connections when the next bug is found in the Tor Browser Bundle (or whatever)? I'm all for making .onion sites reachable, as long as that's the only thing this new feature promises to do. It would make *.onion sites mainstream, which is good for everybody. Strength in numbers, heard immunity, get lost in the crowd - that's precisely what Tor relies on to achieve its most basic goals. Taking Tor mainstream with support in Firefox would mean there would be more Tor users for the seriously privacy-paranoid to hide behind.