J
@0xSentinel
Yes it is exactly true, my bot operates in the following way :
first it will get a fingerprint and assigned it a score according to the results from multiple tests (Recapctha V3 is the first one).
if the score is low, browser is resetting and go to get another fingeprint and test it again
until to find a fingerprint that pass google whit a minimum score of 0.7 the bot continue to get and try fingerprints ...
I take for example my works from this last month, the bot has never exceeded 3 or 4 attempts before having a fingerprint which obtains a score of 0.7 at least, today i can let it run for hours it no longer finds any fingerprint which get socre more than 0.3, so i wase thinking of a problem with fingerprints from fingerprinswitcher, to test this hipothese i use a profile that have a fingerprint which has a score of 0.7 on Recapctah V3 befor the problem, and it does not pass the test, it now gets a 0.3, it seems that the problem does not come from fingerprintswitcher.
I can look into it again when I have time later. For now I don't think problem because not many sites uses recaptcha v3 at the moment but as soon as it becomes a problem to me i will make sure to find a solution.
It is not my case :) I am impacted by this problem and must find a solution to be able to continue to use BAS :)
TCP stack sounds overkill I dont think google use it, maybe mostly for banks and financial institutions.
Yes, as i said i strongly doubt that this is the case for google, it was just to evoke all the possibilities on this post in order to avoid future quesitons...
Have you tried set user agent to as close to stock Chromium as possible ? I think this is what CEF is based on so using Googles own product as useragent and hope to bypass their own system is hard job. Better try set the user agent header for Chromium, Brave, etc and other browsers using Chromium.
You are right It is quite obvious, i will try and give you my feedback.
thanks
