>>2407434You are already in a compromised machine I suppose.
>Compile a bunch of offline desktop app installation .exe files that you've tested to be working and good>Get a VPN with offline installation option>Get a new computer or hard drives (wiping them completely isn't easy)>Install it offline>Only go on the internet through the VPN>Only allow desktop apps to go through the VPN>Obviously never use Google services or sites with Google+ plugins>Never use any sites that have any kind of plugins of shit you have to be logged in for (Like Facebook). You can run scripts for this. It'll increase loading time every time though.>Never allow cookies>Never allow Javascripts and stuff like that automatically>create new email addresses and passwords for everything>never have passwords or CC info in digitalised formats, only on paper (making up too crazy passwords is counter productive)>Have an extra computer running for viewing shit like YouTube. Only view shit on that that you'd have no problem admitting to in court or in front of a BLM lynch mob. If you have a decent phone or a gaming console, do it through that and connect it to a TV.>Experiment with and do research on less known search engines and browsers. Whichever one is currently the best for what you'll need can change all the time>Look into Linux OSs>Try to keep up to date, shit can change pretty fastBut honestly, it's not worth it unless you are doing illegal shit. I just allow Google to rape me because at worst they'll have info on how regular and boring my sexual taste is. Who gives a shit?
>>2407439Also this. All mainstream hardwares are compromised. You might be able to keep Google's automated botnet out of your life, but groups like the NSA or high level hackers can always fuck your shit up. You'll need unique OSs to bypass that, but if you even need to ask, you shouldn't be fucking around with those.
>>2407444>implying