Your lookup table just got a lot bigger.
Your lookup table just got a lot bigger.
Feral, Chimp, myEmail, myDeskPhone, myCellPhone
H1 = sha1(Feral-Chimp-myEmail-myDeskPhone-myCellPhone)
H2 = sha1(F-Chimp-myEmail-myDeskPhone-myCellPhone)
H3 = sha1(Feral-C-myEmail-myDeskPhone-myCellPhone)
H4 = sha1(F-C-myEmail-VALUEOMITTED-VALUEOMITTED)
...
...
So flexibility is available, it's just more computationally expensive for the server to do the extra comparisons. The hash calcs use a little extra battery per user, but I'm much happier to donate some of my processor/battery than I am my Address Book contents.
How much extra battery are you willing to spend, and more importantly, how much effort are you willing to spend running your users' batteries down for something that you'd never yourself use?
That's sort of beside the point, though. The question is: How does uploading my Address Book information provide a much more efficient or complete solution to that set of problems? I don't think that it does. In each case, you're dependent on heuristics and sometimes those heuristics are going to miss a match. If I were Twitter, I'd happily accept those misses in exchange for hitting the matches where people spell each other's first names and email addresses consistently (for example).
> how much effort are you willing to spend running your users' batteries down for something that you'd never yourself use?
You lost me there. My point was just that for Twitter, my iPhone CPU/battery are an "externality." So while they might spend more cycles doing server-side comparisons on the hashes my phone sends over, at least they're not paying to compute the hash values.
But as I said, outside of my territory.
[1] I'm not that old, really.