Deny-all / White-list Cookies experience

Shouldn’t this be the default for a more private and sustainable browsing experience? It’s a rhetorical question as technically, obviously it should be; but we all know it implies more work and technical understanding to use this properly. Regardless, I think this usage should be more documented, tested and recommended for those who have the know how to leverage this.

Being such user, I have seen a couple of glitch that I have reported using different non-optimal methods (reddit, twitter, etc), but I will try to improve and report more on Github. With that being said, if at least part of the team could use the browser that way too, those issue would very quickly seem obvious to them, such as:

  • Airbnb isn’t working, difficult to figure out why.

  • Websites using quick redirects between multiple internal domains often don’t work either as one can only whitelist domains that are loaded in front of them (excluding those temporary redirects that sometimes require cookies to redirect properly. Being able to white-list wildcard subdomains (* would probably help.

  • Extensions too, require cookies (apparently, I didn’t know). For instance, if you start Brave for the first time, enable the deny all cookies (but those whitelisted) and load Metamask, it won’t work. You’re going to have to first allow all first-party cookies, load and configure Metamask, then lock to deny all cookies: it’s too complicated. Actually looking for reports of similar issues, I found a related post that hasn’t been answered:
    White list for 3rd party cookies in Brave Sheild

That being said, Brave is totally awesome, I LOVE IT.

1 Like

I wonder if this is the problem with the Google Keep extension too. I’m going to give it a try. But yeah, there needs to be a granular way to do this.

@jeshii @GustavMarwin,
We have several projects in the works for exactly this: