posted on Aug, 25 2019 @ 07:04 PM
a reply to: billxam
Ok there's some possibles there , changing ip via location has sometimes made it go away . At the end of the day though you're just trying to log in
to oneall via gmail , so 'this device is not recognised' is not an acceptable response . You could be on any device or a public device at the library
. Also , I've found I can log in to youtube with the same gmail , but not into ats at the same time . But log into ats , and your automatically
logged in youtube too. Theres something wrong there it seems .
Disregarding that ats question for the moment , why would asking for a verification code to be sent to your phone not provoke you to just do as asked
? Why did you never just pay the fee and get the code sent , at those 'uh-oh' moments ?
What I'm thinking other than google being super paranoid about it's users being who they say they are is that if 'standard rates apply' to get a
verification code through your phone , so you can log into oneall , this could be quite a profitable hijack of people using dos attack ransomware ,
just with multiple mini ransoms . Google / oneall are not explaining the problem they're giving you which they expect you to pay to fix . They're just
'this device isn't recognised , and for your security , verify it's you" . and if you don't do that they put the same block but saying 'your activity
is unusual , and for your security , verify it's you' . As if it's unusual not to want to give out your phone number to get into oneall , as well as
pay for the privilege at the same time .
If "Standard rates apply" . It's clear that this form of throwing a stumbling block could be very financially profitable if carried out on a large
scale at the same time as being ideal for advanced data harvesting purposes .
edit on 25-8-2019 by DoctorBluechip because: (no reason given)