How do we communicate Tor tabs to the user? Do we separate "Tor" tabs from "Private" tabs?
Much of the user research suggests that people expect private/incognito tabs to protect against ISP-level snooping, rather than just forgetting what's stored locally. https://spreadprivacy.com/is-private-browsing-really-private/ https://www.elie.net/blog/privacy/understanding-how-people-use-private-browsing.
One implementation option:
A broader UX question is how to organize these essentially independent concepts.
Users, _e.g._ doing research on controversial topics, might want to maintain ordinary browser history, site logins, _etc._, while disguising from their ISPs what they're browsing, and disguising from sites they don't log into who they are -- for all this they need Tor, but not everything else in off-the-record mode.
Other users, on, say, shared family or library computers, might just want to avoid leaving a scare for the local machine -- for this they want off-the-record mode. Maybe this should _imply_ Tor as well -- but there's a cost to that, in performance and Cloudflare captchas.
(...though if that would cause users to put pressure on Cloudflare to make their captcha work better, maybe that's a good thing...)
assigning @bradleyrichter for the MVP task, which is deciding what the text for the Tor switch is on about:newtab. for reference this is what i wrote:

@flamsmark @diracdeltas
new mockup with some layout changes and latest text revision from gdoc:
changes from current shipping layout:

I hope you don't mind me making a small criticism @bradleyrichter starting from the bottom up.
1) After 'experience' wouldn't it be better to remove the full stop and include a 'comma so', and removing 'Browser instead', for 'feature or switch.'
2) Remove the second paragraph under 'More about private tabs' because it's almost congruent to the paragraph below 'Make private tabs much more private with Tor'.
3) What was wrong with initial mock-up below 'This is a Private Tab' (not DDG but Tor)? You should retain the original mock-up with the exception of the title.
4) Removing the bit before it, 'Tor can slow ... prove you're human,' should be the second paragraph under 'More about private tabs' after the other is removed.
5) This may be just a technicality but in regards to your first paragraph you may want to cc @flamsmark because I'm sure an aspect of Tor will be loaded in History in case a specific page is accidentally loaded via a non-anon route.
Thanks
@NumDeP Thanks for looking into the details and providing feedback.
To summarize, you prefer the original layout with the Brave shades icon and intro paragraph?
We needed to add more fine print which ended up pushing the Tor switch below the fold. This drove the layout change putting the fine print at the bottom.
Also, the longer Tor switch label "Make private tabs much more private with Tor" (also considering translations) pushed the Tor icon to the far right and would drop to a second line if the text wraps.
Other than these 2 issues, I think the original mockup worked fine as well.
@flamsmark did the final text editing. Tom - perhaps you can review the suggestions above. TY.
quick mocks using a french Tor title in the original layout:
not wrapping:

wrapping:

I wasn't part of the original Tor switch label discussion but it certainly was shorter!
Here is the newly proposed layout that will work better for line breaks from translations.

Actually @bradleyrichter forget it. I like what you did with the frame and the fact you switched the icons and switches over. That size of that duck on the right was freakish before :)
The switches are off by default AFAIK, so we should probably show that in any mockups intended to make us comfortable with usability / ease of scanning for the toggles.
Most helpful comment
@flamsmark @diracdeltas
new mockup with some layout changes and latest text revision from gdoc:
changes from current shipping layout: