It really isn't though. I also started using Firefox recently and I miss tab groups on mobile as well as on my PC. Yes, there is the simple tab groups add-on, but it just doesn't compare.
Brave is also easier to set up ad-blocking, because it comes with ad-block enabled and script-blocking two clicks away.
Don't get me wrong, I will continue to use FF, but Brave has some features, FF does not have (yet).
Tab groups is the biggest thing I'm missing after I made the switch the other week. I'm used to having loads of tabs open, so not being able to easily minimize the ones I'm currently using is annoying to say the least.
One plus is containers. Only opening Meta sites in their own container, same with Google/Youtube is pretty neat.
Oh I hate bookmarks for that purpose, I already have too many as is. Found a way to make the tabs even smaller though, so not having a scroll bar for them will be very nice!
Remembered one more thing; in Firefox I can only have 31 tabs open before the scroll bar appears. In Chrome it's closer to 90-100! That's kinda huge imo.
If you go to the about:config page you can edit browser.tabs.tabMinWidth down to 50 (default is 76) which lets you fit a bit more
If you want more than that it's possible by editing the userchrome: https://old.reddit.com/r/firefox/comments/zda0ov/can_i_get_below_50_tab_width/
Modifying userchrome is admittedly difficult if you're not a developer.. but not out of reach if you're able to follow a guide.
I did set the tabMinWidth first, but the result was... lackluster... to say the least (I like having ~50-100 tabs per window....). However, I JUST found out about userChrome.css before you wrote, and also found code that worked for it!
Some sites don't adhere to standards, it's like old IE all over again. You go to load the site on FF and some check form doesn't work. This happens on 3 sites that I have to use.
I left chrome for FF. Used it almost exclusively for a few years, it's good enough. Recently it got some needed boosts via Microsoft not screwing them.
About 6 months ago I started working with IPFS a lot. Brave baked in support and it's pretty good, so I use brave as my primary and FF as my secondary. I was using some tools to sync bookmarks, but now I just pop into FF and import from brave every now and then.
Brave is better and anti-fingerprinting, if someone is going to sell my data, I think I'd rather give it to brave than google.
No need to wait, Firefox is already a strong competitor (in terms of features, not market share). Adblock on Firefox mobile makes mobile sites so much easier to use.
I guess you could argue that having ublock is a pretty big deal for security though. Regardless I won't consider an alternative unless it offers ublock, even if ux or security is better - happy to sacrifice convenience for privacy and usability.
It might be interwoven, but at the end there are three interfaces:
the headers or tags that trigger it to be enabled for a website
the API towards the attester
the headers that are added to subsequent call to include the verdict of the attester
It should be enough to disable/sabotage nr. 1. If not, you can sabotage nr. 2 so it simply doesn't attest shit. And finally you can suppress adding the verdict to the responses.
If the actual "fingerprinting" or whatever else is in there is still intact doesn't matter if you just don't trigger it.
Of course webservers would simply deny serving brave then. But it's still a good move. The more browsers get "denied", the easier it will be to make a case against websites for some kind of discrimination.
God I hope so, Google's definitely in that "Live long enough to become the villain" camp of the infamous dichotomy (is that the right word) offered from that line from Dark Knight.
It's a massive undertaking to maintain a fork of something that large and continue pulling in patches of later developments.
Not to say that Brave doesn't have the resources to do so - I really don't know their scale - but this notion of "just fork" gets thrown around a lot with these kinds of scenarios. It's an idealistic view and the noble goal of open source software, but in practical and pragmatic terms it doesn't always win, because it takes time and effort and resources that may not just be available.
Did you read the tweet from Brendan Eich linked in the OP? According to him, Brave already is a fork, and he provides a link to a (surprisingly) extensive list of things that are removed / disabled from chromium on their browser.
This is correct - any “Chromium-based” browser is literally a fork unless it’s completely unchanged from upstream (even rebranding and changing the logo and name would require maintaining a fork).
Sure. And the further a fork diverges from upstream the more difficult maintenance becomes. My point is that relying on the open source model to fork projects making hostile changes only works so long as the community is actually able to maintain the fork(s), and so long as those forks actually have a reasonable chance of being adopted. It's equally important, if not even more important, to try to ensure these large projects steer in consumer friendly directions than to react and fork to try to remove anti-consumer features.
Google has enough market and mind share that they can push this and it's a real risk of becoming an anti-consumer standard regardless of any attempts to maintain a fork.
So what do I think we, as a body of users of the Internet, should do? Simple. Stop using Google Chrome and any other Chromium based browsers. Google has the ability to push these changes and make them defacto standards (and later, codified standards) because we collectively give them the power to by using Chromium downstreams.
That may be true, but it's a fork where I doubt any company has the capability to do the engine development needed to be totally independent from Google. There is a reason Apple and Mozilla are the only two alternative engines left. It costs a lot to develop a browser