http://oi45tmbel5syg4uet4t2fg6ipfu22ewfb4dfgpeckarn3qtv3pwq.b32.i2p/tips.html
But you should be aware of what the risks are, because making privacy choices based on an underestimation of the risks is very dangerous. HTTP fingerprinting As I said elsewhere, HTTP is a nightmare for user privacy. There's a Catch-22 in it, because the steps needed to mitigate common security and privacy risks (e.g. rejecting cookies and javascript, altering your user agent string) make your browser's behavior uncommon in subtle ways and therefore easier to fingerprint...