[mhsdef]

I know we like to get the pitchforks out, but, it appears to be accidental:

https://github.com/brave/brave-browser/issues/33726

[dewey]

Where does it say that it was an accident?

[amoshi]

It was unintended.

>The ideal situation would be to move these services to be installed when VPN is first USED (post purchase) and not at install time.

[contact9879]

it's an issue opened by brave's vp noting that the current behaviour should be corrected

[dewey]

That doesn't mean it was an accident, it could just mean that they realized it's a problem. Especially as this issue was opened after this HN submission got posted.

[belthesar]

Issue opened 3 hours ago, thread posted 2 hours ago. I look at Brave with skepticism as one should with a company that flirts with crypto, but in giving them a fair shake, it's important to keep the facts straight. That said, in keeping the facts straight, an issue opened a week ago citing this as a problem was closed in favor of the one opened by the Brave VP.

[MichaelZuo]

> That said, in keeping the facts straight, an issue opened a week ago citing this as a problem was closed in favor of the one opened by the Brave VP.

That seems somewhat shady, unless there was a credible explanation?

[jukiewalsh]

It’s a publicly viewable GitHub issue that people can still navigate to or comment on, it’s not like it was scrubbed. It’s surely a PR move to show they’re on top of it but not anything to read into in my opinion.

[gtvwill]

They realized they were gonna get bad looks for it so they covered that shiz up as if it were a mistake. Marketing damage control.

[pseudotrash]

Nothing is an accident with Brave. You don't go "all in" on crypto unless you're a grifter.

[seaman1921]

sure Brave is a saint, pitchforks only allowed for Google

[Pat_Murph]

Nice try Brave.