3 ms·
And what happens when there is a false positive? I think Google has every right to claim carrier protections (or whatever the law is) and just turn a blind eye
by snprbob86 17y ago
And what happens when there is a false positive? I think Google has every right to claim carrier protections (or whatever the law is) and just turn a blind eye to this problem.
- paulsmith 17y agoI suspect that a combination of the Luhn checksum and contextual information would give you a fairly high confidence level of it being a valid credit card number, and not some other innocent string of digits. They could clearly mark the stricken text as having been done to potentially protect privacy and provide a contact mechanism to un-obscure false positives. I think the harm of a few false positives -- remember, we're talking about obscuring a 16-digit string that has a particular valid checksum, not a very common occurrence -- is greatly outweighed by the harm of having someone's financial identity stolen from a Google search.
- apgwoz 17y agoI'm hard pressed to think of a 16 digit number that I'd want to search for, but I suppose there could be one. Barcodes, ISBNs, etc. But, for the summaries of search results, I see no reason why scrubbing the numbers would be a bad thing. I can't imagine complaining about seeing XXXX XXXX XXXX XXXX in a result summary instead of 5424 0000 0000 0015