Most os have a minimal browser functionality for viewing help files and such, not all applications spawn the os system browser for this. It's quite common for even the most rudimentary applications to use html and an embedded browser to view them. The failure here is that it can go outside of the application context to the web (or at least non-whitelisted website/pages)
in this case, it is actually a separate browder within the Android operating system itself, not the Chrome browser. using brave doesn't mitigate the issue
Pretty much this. We are well past the point of hiding by choosing a different browser. Even unplugging might just make you light up on their grid. They probably have satellite surveillance that flags anything human or vehicle shaped that is moving around without radio emissions as suspicious.
Most os have a minimal browser functionality for viewing help files and such, not all applications spawn the os system browser for this. It's quite common for even the most rudimentary applications to use html and an embedded browser to view them. The failure here is that it can go outside of the application context to the web (or at least non-whitelisted website/pages)
in this case, it is actually a separate browder within the Android operating system itself, not the Chrome browser. using brave doesn't mitigate the issue
Explain how Brave copied a different browser into Android's settings engine?
Or, better yet, show me using Brave's source code.
https://github.com/brave/brave-browser
Pretty much this. We are well past the point of hiding by choosing a different browser. Even unplugging might just make you light up on their grid. They probably have satellite surveillance that flags anything human or vehicle shaped that is moving around without radio emissions as suspicious.