Currently, the program only supports a single account. I reviewed the device ID generation logic, which is bound to the proxy_str and implemented using uuid.uuid3. This is a good approach. I think we can also bind the UID with the proxy to create a uid_proxy_map. Each time the program starts, we can read the uid_proxy_map data, ensuring that the UID only uses the proxy it is bound to. This establishes a unique relationship between the UID, proxy, and device code, which can better obscure bot behavior.
Currently, the program only supports a single account. I reviewed the device ID generation logic, which is bound to the proxy_str and implemented using uuid.uuid3. This is a good approach. I think we can also bind the UID with the proxy to create a uid_proxy_map. Each time the program starts, we can read the uid_proxy_map data, ensuring that the UID only uses the proxy it is bound to. This establishes a unique relationship between the UID, proxy, and device code, which can better obscure bot behavior.