Not sure GDPR is related to typos or deliberate misdirection by users - though I feel your frustration. By any chance does the numeric component of your e-mail alias form a shape on the 10-key pad?
Stupid Patterns
11–20 of 53 posts
Re: Stupid Patterns
#12and then ask me to prove my identity to them?
Re: Stupid Patterns
#13does this describe the various companies that phone me and then ask me to prove my identity to them?
Re: Stupid Patterns
#14I was able to track down his actual phone number and on Facebook. Messaged him and explained to him. He wouldn't act. He said he intentionally gave a random number since he didn't want to be bothered by their phone calls and asked me to "deal with it".
Finding no other option, I used Tata sky IVRS service calling from my mobile number(linked to his account) to subscribe to a bunch of expensive channels, totalling the monthly subscription fee to 10x of what his usual fee was.
He reached out to me requesting that he be allowed to take control of his account, as he is unable to change the phone number linked to the account, without an OTP (one time password) received on the existing number (which was my number).
Did take some sweet revenge by not responding to his request for a while, but eventually gave him the OTP after a week.
Re: Stupid Patterns
#15Not sure GDPR is related to typos or deliberate misdirection by users - though I feel your frustration. By any chance does the numeric component of your e-mail alias form a shape on the 10-key pad?
Re: Stupid Patterns
#16Earlier quoted context omitted.
> In most cases there is no practical way to verify email addresses What's wrong with "Click the link in the email we just sent to x@x.com to verify your email"?
A malicious recipient can click the link and exploit that their email is now associated to the account of some other person.
But it could be mitigated by "click the link and enter the one time code we gave you at sign-up time". Too much friction? How about "click the link on the same browser you used to sign up, and we'll verify that using a cookie we just set" - functionally equivalent and probably works for 90% of users while the rest can fall back to the one time code.
I've seen a handful of sites do something like this in practice. No idea why it's not more common: presumably most people don't roll their own verification process so if some major web frameworks adopt it we'll eventually see it more widely.
Re: Stupid Patterns
#17Re: Stupid Patterns
#18Re: Stupid Patterns
#19These companies aren't verifying that the email was entered correctly.
So I continue to get notices about what this person is doing even though I've reached out to the companies and this person to try to notify them of the error.
Re: Stupid Patterns
#20Not sure GDPR is related to typos or deliberate misdirection by users - though I feel your frustration. By any chance does the numeric component of your e-mail alias form a shape on the 10-key pad?
Under GDPR, people have the right to have their PII stored accurately and can demand corrections from companies. There was a case where a bank couldn't store someone's name properly, because its legacy systems couldn't handle characters with diacritics. The customer sued, and won. https://shkspr.mobi/blog/2021/10/ebcdic-is-incompatible-with... Not a lawyer but I imagine this is a similar sort of situation and the sam…