News for hackers. Stuff that matters.
Re:Brave Browser and the Wayback Machine: Working Together by csteubs on Tuesday February 25, 2020 @10:42PM (#22420088)
I tend to agree. I run a QA team for an e-commerce startup and started using Brave for manual testing about a year ago. Chromium means the same dev tools I know and love, the extensions I use for debugging in Chrome work out of the box, Brave ads/BAT is all opt-in, and the the default "Shield" settings are great for sussing out analytics implementation issues. It seems like most of the arguments against Brave hinge on the token economy and the business model, which I really could not care any less about. Make your money, Brave.

The Wayback machine feature is an interesting move, especially in the world of A/B tests and feature flags. I hope this bolsters support for IA initiatives and ends up powering some cool products, because I can think of a few ideas already (leaning heavily on competitive intelligence, inferring feature performance based on longevity/time-in-test, etc.)

Re:Brave Browser and the Wayback Machine: Working Together by wilkystyle on Tuesday February 25, 2020 @11:12PM (#22420205)
In theory I really like the economic model. By ensuring a revenue stream outside of ads, it should mean that we get the polish and longevity of a commercial product, but without having to pay for it (either with money or by giving up our privacy).

In practice, though, I wish it were more stable, with basic working features. Instead it seems like basic functionality is buggy[0], and major breaking changes could crop up at any time[1].

[0]: https://community.brave.com/t/brave-sync-temporarily-disable...

[1]: https://github.com/brave/brave-browser/issues/7639