Quote Originally Posted by kimse View Post
This is how I feel reading the above: https://www.youtube.com/watch?v=UEaKX9YYHiQ

Here's why:
You have the option to use any authenticator app you want, so you could split the accounts over several apps.
There's several desktop based auth apps too, which means you could spread out the acc auths over several devices too.

I know you're saying it because there's some seriously stupid people out there and they'd probably put all accs on the same auth and then get deleted on all in one go.
But you shouldn't have to recommend something that doesn't really make a difference... unless the person reading the recommendation is stupid and didn't think about using several apps/devices.

/rant


- Kim
The assumption is that anybody who understands it (e.g. you) can make their own decision. As it stands, though, CipSoft has been handing out bans to accounts that have never been botted, simply because they are associated with bot accounts.

[begin speculation]
Also, they have the option to use Google Authenticator. That means, regardless of what authenticator you choose to use, it will likely go through the OAuth protocol. If you read the OAuth 2.0 specification, you'll see that responses contain a field called userid. If I've read the spec correctly, this is a constant that will be the same when given to any application (or any different accounts for the same application) that can be used to identify a single user across multiple apps. This means the only solution is to use completely separate authenticator apps and hope that the Google OAuth server doesn't have a way of correlating them. And, since this is Google we're talking about, it probably does.