Discord Mass DM GO v1.11.2 #806
V4NSH4J
announced in
Announcements
Replies: 2 comments
-
Hello everyone! can anyone guide me how to use latest version of DMDGO |
Beta Was this translation helpful? Give feedback.
0 replies
-
What should i do with this message? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Added option to add multiple fingerprints - More the fingerprints, the more threads you can use safely
Fixed Quarantined Detection and stopping of token
Added a new threaded Mass DM option (For public testing right now, so I know if it works well, I'll turn it into a full fledged feature) This mode joins tokens according to delay and starts sending messages with them. And switches token at rate limit or locks.
Adapted to CaptchaAI's new API
Adapted to Invisifox.com 's new Downloadable solver API and it is working very well at the moment of writing this commit
Added logs for captcha being solved
Removed a xsuper.go which was pushed on accident and was no use to the program anymore.
Added spacing to logs so they align in console
About Discord's new detection ->
Discord now has an inbuilt anti-raid system (For joins & DMs) If they think a raid is happening, they will push mandatory captchas. Usually these captchas will lock your tokens even if unsolved.
All this information is according to tests done on and before 21st August.
Basically there appears to be a threshold on the number of tokens that you can join [Around 50 in a short period of time] or the amount of tokens you can send DMs with [Around 10]. This threshold is reached when these actions happen on the same fingerprint. In this version, you can add multiple fingerprints to fingerprints.json file (There's 3 added by default for your reference) So let's say you're using 1 fingerprint, then you can safely use around 8-10 threads. If you're using 5 fingerprints, you can safely use 40-50 threads. And so on.
Once this threshold is reached, any fingerprint will be captcha'd for a while. So your goal should be never reaching it.
Every fingerprint I ever add hard-coded to DMDGO gets flagged, which is why you are able to put your own, and as many as you want.
There also seems to be a "report raid" button on servers, but as of now, it appears to be kind of useless. But if it's there, I'm sure they plan on working on it's functionality.
If you need more information on getting your fingerprint, refer to these announcements - https://t.me/discordfansonly/106 https://t.me/discordfansonly/98
And yes, all this does mean that if someone else using their own fingerprints achieves this threshold on a server, you despite all your fingerprints won't be able to do any actions effectively (More testing required)
The new DM mode no. 24 is a threaded DM mode, this will join tokens and start DMs as well. You can add random delays to not go too fast. I tested with 20 threads on 3 fingerprints from browsers on my computer. I highly recommend switching it out, you can still add a fingerprint in config like before, but it'll be only 1 fingerprint which is not ideal for more number of threads. If it works well for everyone, I'll add most features of the original mass DM script to it.
This discussion was created from the release Discord Mass DM GO v1.11.2.
Beta Was this translation helpful? Give feedback.
All reactions