-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR : s = '0.' + ':'.join(x[0]) IndexError: list index out of range #2
Comments
URIs were changed: CHALLENGE: str = "https://discord.com/cdn-cgi/challenge-platform/h/b/scripts/jsd/main.js"
CLEARANCE: str = "https://discord.com/cdn-cgi/challenge-platform/h/b/jsd/r/"
The other stuff for json={
"s": s,
"wp": None
} It also seems like even |
@alluding what is the best approach to create |
The only thing dynamically changing is the obfuscation/format of the code. The functions |
got it, thank you.. ive been able to solve ! btw, ive been wondering in translate the js function to python since its a bit annoying to call node to make only this calcs |
You can translate |
Do we need other cookies to get cf_clearance? (__dcfduid, __sdcfduid, __cfruid, _cfuvid) ? |
Those cookies you specified are more of Discord's thing than Cloudflare's. I'm not worried about them, and it worked without cookies. However, if you're sending requests to Discord itself for any sort of task, I'd recommend keeping your request as realistic as possible. This means including the cookies (dynamically generate them), x-fingerprint (some requests include this), x-super-properties, etc. |
@alluding I can't understand how discord reg-in works now. Sometimes i need only email verify, sometimes phone + email and no verify needed. |
I see what you mean. Yes, the register API is a bit sensitive. The reason browsers are more detected than mobile is because, usually, people assume using the browser API is much better and easier. Because of this, browser user agents, headers, cookies, etc., and devices are overall more detected since the chances of people using browsers for tools/bots are higher. This is why you get more verifications, etc., compared to when on a phone. Yes, it's still possible with an emulator of some sort, but that is much harder and way more time-consuming, and some people decide not to do it because not all can either. They know that this is the reason why browser-based registrations are much more prone to phone/email locks and captchas compared to if you signed up on mobile. This is why people try their best to emulate mobile devices instead of browsers. |
@alluding How do you think who has most impact on "bot score"? cloudflare challenge or hcaptcha? Discord can only check request headers. |
Neither. The bot score is checked by hCaptcha, and Discord uses it to flag activity. However, the actual bot score is determined by your device and other factors. Discord doesn't only check the request headers; there is fingerprinting, device analysis, and more. If you didn't know, they can see quite a lot of information, including flagging your IP for suspicious activity if you're excessively interacting with the API. Therefore, the bot score isn't influenced by hCaptcha or Cloudflare. The hCaptcha challenge can flag activity, but Discord is the one checking the bot score and verifying it to decide if it should be flagged. It could just ignore it, say you got a valid captcha, and let you pass. |
@alluding So discord does tls fingerprinting and deep packet analysis? I created some accounts from different real devices, some of them was with added phone number. After 8 hours more than half was "ACCOUNT_PERMANENTLY_DISABLED", even with phone. I understood that the analysis of some data takes place with a delay, not immediately after reg-in. |
That is most likely a "silent flagged" account. A silent flagged account will let you do some things, and the account will be fine for a bit, but it will most likely be deleted or terminated after some time. |
https://discord.com/cdn-cgi/challenge-platform/scripts/invisible.js 404 is the reason for this error
The text was updated successfully, but these errors were encountered: