You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm using the last version of the CVAmp on Windows Server 2022 (and 2019).
I have 3 list of ISP proxies (Ultra Private). It's not from Webshare.
One of those list, most of all tokens are getting marked as "Bot Detected: True" and I can't follow anyone (sometime it works). Most of the time, if I want to follow my account with any of my Tokens, I have to Login manually (New Chrome Profile + Proxy Switcher + F12 and add manually this auth-token), then I can follow my channel, change some badges, etc...
I also have alot of accounts that is not marked as flagged, but If I use it on CVAmp, it gets marked as "Bot". I don't know what is the proccess used to check it, but, I guess it's broken.
The text was updated successfully, but these errors were encountered:
Hey you, thanks for getting in touch. The detected flag is set if there are any graphql communication errors between the instance and Twitch. No further implications can be derived from this — it's simply an indicator that not everything is running smoothly. Perhaps my naming scheme was too drastic. I am working on the next version to decrease the detection rate, but it is a cat and mouse game.
Hi, I'm using the last version of the CVAmp on Windows Server 2022 (and 2019).
I have 3 list of ISP proxies (Ultra Private). It's not from Webshare.
One of those list, most of all tokens are getting marked as "Bot Detected: True" and I can't follow anyone (sometime it works). Most of the time, if I want to follow my account with any of my Tokens, I have to Login manually (New Chrome Profile + Proxy Switcher + F12 and add manually this auth-token), then I can follow my channel, change some badges, etc...
I also have alot of accounts that is not marked as flagged, but If I use it on CVAmp, it gets marked as "Bot". I don't know what is the proccess used to check it, but, I guess it's broken.
The text was updated successfully, but these errors were encountered: