[PYTHON] GITHUB RARE USERNAME CLAIMER

[259]

Made by me. I was able to claim about 20 3Ls in 10 hours of running.
It works using selenium chromedriver (Included ratelimit auto cooldown)

Hidden Content

You must register or login to view this content.

[443]

WTF is this. Do you really think this code can be released ? Its slow and unoptimized. Also why selenium when you could use head requests which would be way faster . I don't know man, you should really update this or just recode the whole thing. GL

edit : was a bit harsh mb

 

 

[259]

WTF is this. Do you really think this code can be released ? Its slow and unoptimized. Also why selenium when you could use head requests which would be way faster . I don't know man, you should really update this or just recode the whole thing. GL

its not slow, actually the right amount to not get perm ratelimited by github for 1 hour. Requests are not faster, unless you send requests asynchronous with proxies which seems a bit overkill for a checker. The delay is perfect how it is.

[210]

WTF is this. Do you really think this code can be released ? Its slow and unoptimized. Also why selenium when you could use head requests which would be way faster . I don't know man, you should really update this or just recode the whole thing. GL

why not stop crying and make one urself if u that good at coding and leave others release their things

---

Made by me. I was able to claim about 20 3Ls in 10 hours of running.
It works using selenium chromedriver (Included ratelimit auto cooldown)

good release mate

[443]

WTF is this. Do you really think this code can be released ? Its slow and unoptimized. Also why selenium when you could use head requests which would be way faster . I don't know man, you should really update this or just recode the whole thing. GL

its not slow, actually the right amount to not get perm ratelimited by github for 1 hour. Requests are not faster, unless you send requests asynchronous with proxies which seems a bit overkill for a checker. The delay is perfect how it is.

If the objective is speed, how is it overkill to use requests and proxies.....

 

 

[202]

Made by me. I was able to claim about 20 3Ls in 10 hours of running.
It works using selenium chromedriver (Included ratelimit auto cooldown)

w?????

[132]

WTF is this. Do you really think this code can be released ? Its slow and unoptimized. Also why selenium when you could use head requests which would be way faster . I don't know man, you should really update this or just recode the whole thing. GL

Hello, please be nice. Thanks.

Why don't you make a pull requests if you are being so critical?

Follow me on GitHub

Contact me on discord for legitimate purposes or you will be blocked:
snippytogruta (995042999035756654)
Make sure to verify my id

[259]

WTF is this. Do you really think this code can be released ? Its slow and unoptimized. Also why selenium when you could use head requests which would be way faster . I don't know man, you should really update this or just recode the whole thing. GL

its not slow, actually the right amount to not get perm ratelimited by github for 1 hour. Requests are not faster, unless you send requests asynchronous with proxies which seems a bit overkill for a checker. The delay is perfect how it is.

If the objective is speed, how is it overkill to use requests and proxies.....

The objective is not speed. You can check every and I mean every 3L possible in 14h. Wont matter if it takes you 14h or 1h. People have been doing this for years they just dont have enough patience