@Roy-Mustang I agree with you very much. I have tested my proxy and there is no problem because it runs normally on my computer. The rest are browser settings. Is it possible that the data in FingerprintSwitcher has been used by many people and is no longer trusted on many platforms? And I didn't find a way to set the browser history in Bablosoft Wiki. Maybe it doesn't support it at all.
Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint
Moved
Support
-
I can't reproduce the issue.
Yes, I can't always register an account; the success rate is around 70%. But I still manage to register them. Apparently, registration success is influenced by a combination of parameters, such as the fingerprint and proxy.
Also, try using PerfectCanvas. -
My problem is that I constantly get an error like the one in the picture. When I use a fingerprint, I get this error, but if I don’t use it, there’s no issue — however, after I enter the email verification code, it sends me back to the previous step.
-
have the same issue. Any news for how to fix it?
-
After three months of in-depth analysis, we’ve completely resolved the castle_token issue. castle_token is a real headache. @m4zuper
You need to make a major update to BAS. castle.io can bypass BAS directly and detect the computer’s original fingerprint.
The problem is that the BAS fingerprint system only works for page load.
However, castle.io opening a new worker and retrieving the fingerprint from there bypasses all of BAS’s fingerprint manipulation systems. -
If I had to explain this briefly, think of it this way—my English isn’t very good.
BAS > x.com > page load fingerprint is active (meaning BAS has injected the fingerprint) > x.com loads a JavaScript chunk (3 different modules) > the module (castle_sdk) starts a new worker (this works on the principle of launching a new browser) > it can directly access the computer’s original canvas and readpixel data. -
https://github.com/gelistiricitr/castle-reverse
Here are all my works.
-
@makuma said in Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint:
My problem is that I constantly get an error like the one in the picture. When I use a fingerprint, I get this error, but if I don’t use it, there’s no issue — however, after I enter the email verification code, it sends me back to the previous step.
You received this error because x.com detected you as a bot and immediately prevented you from registering via email, requiring you to register using your phone instead.
-
@vntricky said in Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint:
@makuma said in Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint:
My problem is that I constantly get an error like the one in the picture. When I use a fingerprint, I get this error, but if I don’t use it, there’s no issue — however, after I enter the email verification code, it sends me back to the previous step.
You received this error because x.com detected you as a bot and immediately prevented you from registering via email, requiring you to register using your phone instead.
Please don’t spread misinformation. I’ve already explained everything in my message above; by spreading misinformation, you’re misleading people.
-
This post is deleted!
-
@tersinemuhendis said in Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint:
@vntricky said in Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint:
@makuma said in Twitter shows “Something went wrong” only when using FingerprintSwitcher — works fine without fingerprint:
My problem is that I constantly get an error like the one in the picture. When I use a fingerprint, I get this error, but if I don’t use it, there’s no issue — however, after I enter the email verification code, it sends me back to the previous step.
You received this error because x.com detected you as a bot and immediately prevented you from registering via email, requiring you to register using your phone instead.
Please don’t spread misinformation. I’ve already explained everything in my message above; by spreading misinformation, you’re misleading people.
I only explained how the error occurred. The root problem—the fingerprint detection—is beyond my expertise.
