Rootjazz

Thank you for the update! It's great to hear that proxyless solving will be coming back in a few hours. We appreciate your continued support.

Thank you very much for your prompt response to the specification change to blob data. We truly appreciate it. Additionally, I would like to share some information provided by the capsolver support team regarding the success rates of captcha resolution with different versions of Chrome. It has been ...

I had direct interactions with the capsolver support team and received valuable information about the captcha solving program. Following the integration of this information into our program, we have definitely seen improvements in performance after captcha resolution. Building on this success, I pro...

Thank you for sharing detailed information. I understand that the new version contains many improvements, especially the enhanced logging features. The fact that issues not detected in older versions are reported in the new version suggests that these issues might have existed before, which is very ...

Here is the information on the issue discussed: Summary ・Problem Overview: [Request for modification regarding the issue of accounts being frozen after being unlocked] Detailed Issue ・Conditions of Occurrence: [Using capsolver to unlock on Twitter dub results in the account being frozen immediately ...

During the review of DM transmission logs, we identified several issues with the login process and cookie management when comparing dub version 3.617 and dub version 3.567. The specific issues are outlined below. Cookie Usage: ver3.567: A cookie named "global trust cookies" is used in each...

Thank you for resolving the issue. I always appreciate your prompt response.

I am also experiencing the same issue. I am using version 3.606, and after logging in, I receive a "BadRequestError" from the API when trying to retrieve the home timeline. The error message states, "The following features cannot be null: articles_preview_enabled."

It's ideal to perform the like action at the same time as the follow action with the same account. Yesterday, I updated to version 3.604. Before that, I was using version 3.601, and I did not encounter this problem. The only things I did were update to version 3.604 and check the [Attempt to login w...

Thank you in advance.

ID: logs_86384