[danShumway]

Two potential reasons spring to mind:

A) In order to drive Tor adoption and increase the feasibility of normal people hosting sites on Tor, it is necessary that normal people be able to connect to hidden services, even if they themselves are not necessarily reaping the privacy benefits.

If Firefox and Chrome both supported the Tor protocol out of the box then I would be more likely to host content on Tor, because I wouldn't need to tell my family and friends to install a new browser just to access that content.

B) Even though Brave's Tor features are inferior to the Tor browser, they still probably offer some privacy benefit over normal browsing (assuming users are not assuming that the mode is perfectly private).

That being said:

A) It would still be better for Brave to fix issues like this over time, and the leak is worth taking seriously instead of brushing off as a known issue.

B) A warning on a FAQ is not sufficient to handle point B. Brave should be looking into UX methods to make it clear to users that visiting a Tor site does not make them anonymous. Most of the people installing Brave are never going to see that warning.

[permo-w]

I’d say more likely than either of those things, it’s just convenient, and it gives them a(nother) selling point over other browsers.

Besides, assuming you live in the West, as long as you aren’t you’re planning a terrorist attack, watching child porn, selling drugs, weapons, assassinations, bomb making materials, etc, then brave will probably do

I would still use TOR for pretty much any dark web activities, but in practicality, as long as you aren’t doing anything that you can imagine a policeman actively hating you for, it’s probably pretty safe