2 ms·
James is wrong, this is Netflix's fault. The same "scam" would work under a variety of circumstances because Netflix relies on something it has no reason to bel
by tialaramex 6y ago
James is wrong, this is Netflix's fault. The same "scam" would work under a variety of circumstances because Netflix relies on something it has no reason to believe is true. Maybe you signed up to Netflix but your house mate thinks she did, she gets an email because of Eve, now you're both paying for Netflix, but actually she's paying for Eve's account.
Netflix could make this mistake with postal addresses even, if for some reason they used postal addresses. You get a letter from Netflix, you don't notice it's addressed to Eve, who had stupidly written your address instead of hers, you pay for her Netflix.
This is a data protection violation, data processors have a duty to take reasonable care that the personal information they have about data subjects is correct. If you need it, make sure it's accurate. If you don't need it, don't collect it.
- Spivak 6y agoThis is actually Google's fault. Because Google is large enough Netflix could be nice and have special handling for Gmail addresses but this would be going against the email RFC that says $inbox1+$subaddr@domain == $inbox2+$subaddr@domain iff $inbox1 and $inbox2 are identical. Netflix has zero idea how any particular email operator mangles or maps inboxes to actual users. Apple's private email service maps all sorts of inboxes to the same actual person. Mailinator maps every address to everyone.
- robjan 6y agoThis is Netflix's fault for not verifying email addresses before taking payment details for a recurring subscription.
- Spivak 6y agoTrue, Netflix should have verified that the person signing up could actually receive an email at the address they gave. But in addition Netflix is right to allow the creation of two accounts where the difference is only dots.
- kevin_thibedeau 6y agoThere is no RFC specifying the interpretation of address formats. Every domain can use whatever scheme they wish. The RFC only declares that senders can't impose additional formatting rules on receivers.