Maybe I’m missing something but you can tell a compromised account from a secure account by the user behavior, no? If an account is compromised the activity will be spam/harassment, etc at which point a ban on that account would happen. And compromised accounts could be accessed from a non-vpn Ip also.
Think of it from the reverse direction. If you have a twitch account in good standing that’s verified with a valid email and has no violations, why all of the sudden would it make sense to apply a ban to this account? Perhaps preventing new accounts from being created on a sketchy IP could be a sensible solution, but shadowbanning an existing account makes no sense and is a lazy approach to security. In addition, fingerprinting makes it so a service can easily differentiate between users using the same IP.
I’ve only experienced a shadowban while using ubuntu. I switch between all the major operating systems on the same twitch account and with the same vpn service/servers. The bans have only been initiated while on linux, although they did follow over to the other OSes until some type of timer was passed.
This follows what some online shopping services do, which is to assign weights to certain user metrics and if a set threshold is crossed it rejects your payment or otherwise blocks you from a transaction. So VPN+MacOS might work but VPN+Linux matches some type of metric fraud systems associate with criminals.
It’s trivial for twitch to differentiate between users who are logged in and have verified accounts. Slapping bans by IP is archaic and lazy when you have more precise metrics to go by. And at the very least, they should make you aware that you are banned before accepting your money for their services.
Your question is a good one. I’m not the one who downvoted you fyi. To answer your question, it is absolutely a personal anecdote based on my own experimentation. I’m sure others will add their own experiences. Based on my experiences there’s no doubt about twitch shadowbanning based on VPN use. I’ll admit I don’t have a basis for Linux and adblockers being a part of the equation, but I made it clear in my original post that those were assumptions.
To further speculate, I have an idea that the shadowban may actually be triggered by somebody using the same VPN server doing something that triggers it, affecting anybody else on that server. I can’t possibly provide evidence for that theory, but it would explain the seemingly random nature of the shadowbans.
Unless you automate this to run a search at random intervals, wouldn’t google see a blast of searches and just ignore it as noise? I imagine they employ AI already to filter out nonsensical activity or bot activity.
Really, just stop using google. I migrated from google many years ago. It’s been great. The frustrating part is when they buy up good products and run them into the ground (Nest, Fitbit). Seriously fuck google.
QEMU. Using NAT but it’s attached to the host’s NIC. I know this is probably what’s causing the issue. I’m not sure how to connect it to the VPN.