[UPDATE] Why requests-V1 is NF

[sandrocods]

[UPDATE] Why requests-V1 is NF

[Nyumat]

Hello, @sandrocods

Let's hope other people who used the tool at some point see this thread and read it entirely to understand the current state of development.

I'm very new to python so I've been learning how to implement the DearPyGUI module for the client to be hosted through so the proxy list is readable and threads can be limited. However, the reason why requests-V1 returns an error is that the proxy implementation isn't 100% complete only due to there currently being no method in the Bot class to return the list from free-proxy-list.net, yet.

However, the bad news is ByteDance/TikTok has recently been catching on to many of the recent bot/services that have been "exploiting" their product. With this now being an actual factor, the main blocker in these new updates to the application is that on each requests as the userAgent, the tokens are secretly passed in GET...so sooner or later if not already, working on this project in will be useless.

And while yes, there low-key is a simple way to bypass this by just decrypting the SHA1 hash and generating X-Gorgon / X-Khronos headers along with the current proxy approach I started...as someone who has other things to work on, it's better left alone unless someone wants to take on the task of doing, which would require you to port a whole separate server to read the calls return the 2 string(s)

I also started school/leetcode grind so in general it probably won't be done soon if it were to be done, unfortunately. ://

-Nyumat 😄