There's a damn good explanation in this thread:
CSS History Leak and how to prevent it even with enabled history [Firefox & Opera] - SB-Innovation - Leecher Mod Source Nr. 1
There's a damn good explanation in this thread:
CSS History Leak and how to prevent it even with enabled history [Firefox & Opera] - SB-Innovation - Leecher Mod Source Nr. 1
"I just remembered something that happened a long time ago."
Guys, a question: when i use the "Private Browsing" mode i'm completely clean about cookies, history, cache and so on, right?
Ok, i understand........
Here there's someone friend of any sysop, admin or moderator who can tell us what techniques they use for catch us? It's just for learning.....
Then that someone would need to be tracker staff as well. I mean, if I was a sysop at What.cd, for example, I wouldn't tell how the anti-dupe system works to a stranger, even he isn't known to be a cheater. I doubt you'll see anything different from what we already know (cache, cookies, new IP) anyway.
"I just remembered something that happened a long time ago."
Aside from using any private anti-tracers or deleting your footprints, you could use a safe elite SOCKET4/5 proxy with an anonymizer for good resulst & remember to change the IP you're use every time you log in to those trackers.
It' simpossible use a proxy, no one tracker accept the use of the proxy when you make the log in.
Bookmarks