V4NSH4J Discord Mass DM GO Versions Save

1. Added option to add multiple fingerprints - More the fingerprints, the more threads you can use safely

2. Fixed Quarantined Detection and stopping of token

3. 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.

4. Adapted to CaptchaAI's new API

5. Adapted to Invisifox.com 's new Downloadable solver API and it is working very well at the moment of writing this commit

6. Added logs for captcha being solved

7. Removed a xsuper.go which was pushed on accident and was no use to the program anymore.

8. 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.

1. Fixed the stability issues (Invalid response codes, failing to get cookies)
2. Add your useragent, x-super-properties and JA3 for best compatibility.

There now seems to be a hard limit on the number of tokens you can join to a server in a given time. Any tokens joining after the limit always get captcha'd. Only current workaround I found to this was joining tokens slower.

1. Major re-write of sections of the code
2. Possibly fixed fingerprinting issue causing DMDGO to get flagged again and again, fully customizable in config. [Docs available soon, but default config should work]
3. Even better emulation of an actual Discord client
4. Removed SOCKS4/ SOCKS5 proxy compatibility
5. Added a new captcha API (captchaai.io)
6. Fixed token changer writing file with censored tokens if option enabled in config for censoring tokens on console.

This was a very big re-write on my end to fix the fingerprinting issues causing DMDGO to be flagged repeatedly, please report any and all bugs on the associated discussion. Testing everything in DMDGO's giant code base alone is a very big task for me, it's better tested by the community. I've tested joins and DMs and it seems to be working perfectly fine just like a token on browser.

Unpatched

Unpatched it, no idea how long it'll last but I'm here to fix it.

Added cloudflare bot management cookie , but I think it somehow flags so It's disabled by default.

The config has changed so make sure you update.

https://youtu.be/94u_rv50iuE

1. Randomized Locales in X-super-properties unpatching it yet once again but still not a permanent solution

1. Unpatched and more closely resembling Latest chrome browser information
2. Added option to add your own Useragent and X-super-properties in config
3. Fixed Token Login
4. Fixed problem with Semantic versioning

Edit since release: Fixed a mistake I made which made it still get captcha. Re-download to get the update

1. Added Mass DM for friends
2. Added Scrapers to scrape Username#Discrim in logs folder (if enabled in config)
3. Unpatched Requests by getting latest chrome headers and building our own X-Super-Properties using latest versioning information
4. Introduced a new Captcha API invisifox.com [https://t.me/invisifox] They are offering free trials as of the time of writing this.

Someone mass reported the pastebin (We were using pastebin so we could update the values without having to make a whole new release) where DMDGO was fetching Useragents and X-super-properties for in v1.10.10 so it was taken down which is why it defaulted to using an offline already flagged one which is why it's "patched". In this version we are building x-super-properties according to point 3. If it doesn't work out, we'll revert back to the way we were doing it in v1.10.10 but this time putting them up on github so they don't get taken down. Pastebin logic: "We don't know what this means so this text is very malicious!!"

Unpatched and added a lot of combinations of the thing discord is patching 🤞