I am not super deep into how these browsers and forks function, but if there's an expectation of this fork being more private or secure than other browsers or forks, then I'm curious to know if there's supposed to be some type of countermeasure to prevent tracking "attacks" like these.
In reference to the nothing-private project: https://github.com/gautamkrishnar/nothing-private https://nothingprivate.gkr.pw/
I am not super deep into how these browsers and forks function, but if there's an expectation of this fork being more private or secure than other browsers or forks, then I'm curious to know if there's supposed to be some type of countermeasure to prevent tracking "attacks" like these.
The Cover Your Tracks test (https://coveryourtracks.eff.org/) appears to be as good as Brave which is promising. Has this particular issue just not been addressed or is this an oversight perhaps? Maybe something I'm missing with my settings? Not sure, just curious, seems like some browsers are addressing this directly so it's probably of interest for Mercury too https://github.com/gautamkrishnar/nothing-private/tree/master/browsers-with-countermeasures
Thanks!