Put Linux on an Atom or a Pi with Firefox or Chrome/Chromium installed.
Ship it to a friend in the US.
Open port on router pointing to SSH port on Atom/Pi.
Use SSH X11 Forwarding to display Firefox or Chrome on your local device.
This sounds really idiotic to something that can be solved so simple.
What you are looking at here would easily cost you more than $500 in total not to mention maintenance etc.
An "SSH forwarding" means it's a socks proxy (socket tunneling). You can buy a residential from the marketplace, probably for a lot cheaper too than this will ever cost. And you can probably find a static residential IP or even a dedicated mobile IP for much less than that.
Javascript, Canvas, WebRTC and unmatched DNS-to-ASIN can give away your real IP in-browser.
Ok look, javascript alone cannot give you away it's just a client sided language meaning, compared to PHP that only executes on the server, javascript only executes in your own browser which makes it a little more vulnerable to disclosures.
Latest version of Firefox protects you from canvas fingerprinting with the safest settings as well as there are tons of add-ons you can add to protect your computer-generated canvas. Either way Canvas is not a reliable way to identify anyone as they need a baseline of who else generated the same canvas resemblance.
WebRTC is very easy to disable as well (most modern versions of VPN clients protects against this, exception is OpenVPN which is generic.).
In firefox you can do it from about:settings and search for media peer connection and disable it. Google it if u need additional facts.
And DNS linking is as well not reliable as its really simple to change to anything you like but it might give a clue from where u are. This can be solved by ticking the box in firefox at the bottom saying something about tunneling DNS too.
And while you are at it, disable WebGL2 as well which is also done in 10 seconds.
To stay hidden is one thing and is really not rocket-science. In most casual ways it's just to enter the right settings.
I know many new people for example only places their proxy info on firefox first field for HTTP but not for HTTPS and this will make HTTPS sites NOT go through the proxy as that's what you told Firefox to do. You need to tick the box of "Use this for every protocol".
Due to the nature of a SOCKS5 proxy this is automatically tunneled as well so for that you dont need to enter any additional info..
So to conclude is to you:
Use Firefox (portable is fine or use "profile manager")
Configure it CORRECTLY
Use a residential IP (4g/mobile proxy is included) that does not rotate or can at least rotate within the same city.
That's it. You are now safe.
Double check the settings on browserleaks or whoer etc to make sure you are safe before you start.
Some sites matches IP with timezone or computer language too, this can also be spoofed wtih an extension. But most of the times its just the IPs.
