3 ms·
Well, Google Mail does this too. For the last part I agree the with the pro you mentioned, but it is also a con, with following possible cases where it breaks
by lloeki 16y ago
Well, Google Mail does this too.
For the last part I agree the with the pro you mentioned, but it is also a con, with following possible cases where it breaks down:
- they won't show all of their info to you
- you don't care about all of it, only a subset
- they did not update their info correctly
- not everyone uses Facebook to the same extent, if at all
Having a consolidated address-book you manage, regardless of what service you use to interact with each of your contacts. Besides I can normalize the data the way I want.
That said, it would be interesting to have Facebook and others as an available source (among many others) to an address-book. Of course I suppose Facebook won't ever expose it as an LDAP endpoint of sorts.
- thwarted 16y agoExposing it via a standard method, like LDAP, would be awesome, and I agree entirely unlikely considering the (passive aggressive?) stance Facebook and Google are taking on exposing that information. Exposing your address book via a method that allows you to consume it programatically and thereby make it more useful? We wouldn't want to enable competitors because we obviously can't continue to exist or be relevant using any method other than locking people in.