All Proxies Are Invalid...

[UnknownAgent]

Hello there, I have a number of questions on using this program.

• Hey, should I use auto proxy scraper?
• Can you give a list of good working proxies?
• Where will the valid proxies be stored?
• Why does it scrap rate limited proxies?
• Should I enable multi check ?
• How many codes to generate to get a valid one?

[ghost]

• Hey, should I use auto proxy scraper? No. If you really want to use this program, you should buy a good list of paid proxies.
• Can you give a list of good working proxies? No. You need to buy it.
• Where will the valid proxies be stored? In working_proxies.txt
• Why does it scrap rate limited proxies? It doesn't. You use proxies because each up can only make a limited amount of requests per minute. If you use proxies, You can bypass that limit, although the proxies then self still get ratelimited. That's why you need a big list of proxies
• Should I enable multi check ? Yes. If a proxy is ratelimited, it will automatically switch to another proxy and try checking the code with that one. However, it may take longer
• How many codes to generate to get a valid one? It depends. I would say 50k - 100k

[TKperson]

@ghost I disagree with you.

Can you give a list of good working proxies? No. You need to buy it.

You can find many good ones by yourself instead of using auto generated ones. Some free proxies work just like paid proxies or even better than paid ones. Why paying for one when you can get one for free. If you still disagree with me at this point I can make a video about it to proof getting a free working proxy is not hard at all.

Or you can try do a quick google search of "free proxy list"; I'm sure you will find dozens if you have the time to check the proxies yourself. Or use a good proxy checker

How many codes to generate to get a valid one? It depends. I would say 50k - 100k

Oh really??! 62 available characters,16 available places, and characters can be repeated for the nitro token/hash. 62^16 (47672401706823533450263330816) different and available nitros, so if I divide that by 100k I'll get the number of people that bought nitro to have a chance to even get a nitro at around 100k requests: (62^16)/100000 = 4.767240170682353e+23. It seems like 4.767240170682353e+23 people forgot about that they bought a nitro within the 2 days period.

I don't really think we have that many people on Earth. see more at: https://github.com/Stanley-GF/Discord-Nitro-Generator/issues/13#issuecomment-762048011

This is not the end yet, I haven't used this generator yet, but after checking out the code, I realized there are a few things that can be easily added to give a way better performance for this program maybe a lot more faster by using some multi threading libraries. This code is going to be painfully slow if its left as it is right now, even if you made this in assembly, optimized everything single bit of the code, and assuming you can make http requests without getting rate limited or account disabled everything at a perfect condition. It will not get you a nitro, unless you are lucky af <- used the f word there bc it is lucky af.

[logicguy1]

Also keep in mind that discord allows about 50 codes to be checked before ratelimiting, the reatelimit can last up to a week