Brave browser should not be included in core (pattern of sketchy behavior)

[ianks]

Output of brew config

n/a

Output of brew doctor

n/a

Description of issue

I've come to discover that Brave browser has a record of abusing user's trust for their own benefit. IMO, it's not a good idea to enable this type of behavior by extending Homebrew's trust by default. It should be moved to an external tap.

Since this issue was posted, Brave has injected their affiliate code into links and leaked DNS when supposedly using Tor. I was unaware that they had previously whitelisted Facebook and Twitter trackers while claiming to block trackers. It still removes site ads to place their own with a cryptocurrency kickback scheme on top of it.

• Why Brave is blocked? lobsters/lobsters-ansible#45 (comment)

[gromgit]

It should be moved to a cask.

It is a cask.

[ianks]

Sorry, I meant "tap" (external to the Homebrew org)

[p-linnane]

As @gromgit said, it's already a cask. Additionally, this it outside our threat model. Users are expected to know what they are installing. We simply provide a way to install it.