-
The rules for submitting a Dispute have been clarified. Please make certain you read the rules clarification(s) OR read the full DR rules.
Have anyone used Fingerprint Switcher by BabloSoft
- Thread starter jeff1985
- Start date
jeff1985
Regular Member
- May 10, 2013
- 495
- 94
what do you mean....their software...does it come with the purchase....i will be using real residential ips...
Aty
Elite Member
- Jan 27, 2011
- 7,631
- 5,301
Keep hoping, lol.
DanDD
Senior Member
- Mar 10, 2014
- 955
- 326
their fingerprint switcher can only be used with browser automation studio which is free
Pistacho
BANNED
- Apr 24, 2019
- 79
- 66
It is useless because every one is jumping on the band wagon of providing browser fingerprinting without knowing a clue about the industry.
Browser fingerprinting for the sole purpose to identify unique visitors based on the Jaccard index derived from unique identifier browser features is much less popular now.
There was a huge backlash against this practice. Now the industry is focusing strictly more in the realm of Fraud and Spam.
This means that they do not care what md5/sha1 hash your Canvas fingerprint produces, but they only care about the web_gl shader name you are using.So you can easily spoof that.
What they are really checking is the use of Selenium and/or browser based bots that are spamming/botting their sites.
In essence because the majority of these nuances are created by people with low tech skills that only know how to operate a browser with scripts, they have employed a lot of feature checks around their browser fingerprints to catch the bad actors.
This basically means that some of the most advanced browser fingerprints can catch you lying about using a Chrome User-Agent while using a Firefox browser. Finding these discrepancies is enough to categorize you as a non welcoming visitor.
To seriously have an anti browser fingerprint solution that can blend in and pass every browser feature check will require a lot of work.
You will need to recompile all the browsers to include native code functions inside the browser. That’s because now a days browser fingerprints solutions check if the defined functions are native and not reimplemented with your JavaScript script you used to redefine some variables/functions.
On top of that you will need to know the thousands upon thousands of differences each browser has that the other ones do not.
So if browser A had feature #765 but browser B and C do not, well if the browser fingerprint you are on is checking for that feature and you are caught using Browser B or C but wearing Browser A User-Agent then you got caught lying.
In conclusion the anti browser fingerprint solutions everybody is buying either by being aware or unaware of what they provide is totally useless at evading the Fraud and Spam fingerprints.
All these solutions provide you the means to anonymize your unique hardware and locale features that every browser displays, and maybe turn some features on and off like webrtc.
However with the most advanced sites don’t lie that you are using Opera but running a Chrome browser because it will yield 0 results.
It is really hard to do that cause nobody has documented all the different quirks of each browser family, nonetheless implemented them.
Browser fingerprinting for the sole purpose to identify unique visitors based on the Jaccard index derived from unique identifier browser features is much less popular now.
There was a huge backlash against this practice. Now the industry is focusing strictly more in the realm of Fraud and Spam.
This means that they do not care what md5/sha1 hash your Canvas fingerprint produces, but they only care about the web_gl shader name you are using.So you can easily spoof that.
What they are really checking is the use of Selenium and/or browser based bots that are spamming/botting their sites.
In essence because the majority of these nuances are created by people with low tech skills that only know how to operate a browser with scripts, they have employed a lot of feature checks around their browser fingerprints to catch the bad actors.
This basically means that some of the most advanced browser fingerprints can catch you lying about using a Chrome User-Agent while using a Firefox browser. Finding these discrepancies is enough to categorize you as a non welcoming visitor.
To seriously have an anti browser fingerprint solution that can blend in and pass every browser feature check will require a lot of work.
You will need to recompile all the browsers to include native code functions inside the browser. That’s because now a days browser fingerprints solutions check if the defined functions are native and not reimplemented with your JavaScript script you used to redefine some variables/functions.
On top of that you will need to know the thousands upon thousands of differences each browser has that the other ones do not.
So if browser A had feature #765 but browser B and C do not, well if the browser fingerprint you are on is checking for that feature and you are caught using Browser B or C but wearing Browser A User-Agent then you got caught lying.
In conclusion the anti browser fingerprint solutions everybody is buying either by being aware or unaware of what they provide is totally useless at evading the Fraud and Spam fingerprints.
All these solutions provide you the means to anonymize your unique hardware and locale features that every browser displays, and maybe turn some features on and off like webrtc.
However with the most advanced sites don’t lie that you are using Opera but running a Chrome browser because it will yield 0 results.
It is really hard to do that cause nobody has documented all the different quirks of each browser family, nonetheless implemented them.
D
Deleted member 657006
Guest
post a solution you seem to no everything ...
Pistacho
BANNED
- Apr 24, 2019
- 79
- 66
I do not know everything as I’m just a simple observer with a quench for knowledge. I will make of note of that to later put more of this stuff on a separate thread.