This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Tor beyond private tabs #14649
Labels
feature/tor
needs-discussion
A suggestion that lacks agreement from the team.
open-in-brave-core
wontfix
We initially implemented support for Tor in private tabs on the premise that Tor is necessary to provide the 'privacy' that it seems a majority of users expect 'private tabs' to convey. However, total anonymity against all actors involved -- the next person on the computer you're using, your ISP, the remote host -- is not the only value of Tor.
The initial idea was 'new Tor tab'. What we first implemented was a toggle switch to make private tabs 'really private' the way the majority of users seem to expect them, rather than impose the jargon 'new Tor tab' on them. Then we switched to 'new private tab' vs 'new private tab with Tor' so that users could have control over which private tabs get to use Tor. This design is still in flux.
This is an issue to track these design decisions. I offer these user profiles as examples that we might want to support. (This is aside from background tasks for which, in the future, we might want to use Tor, e.g. version updates, ledger operations, &c.)
The text was updated successfully, but these errors were encountered: