Message from discussion How to access Gmail Address Book
Date: Mon, 25 Feb 2008 10:49:27 -0800 (PST)
Received: by 10.100.167.3 with SMTP id p3mr600173ane.6.1203965367137; Mon, 25
Feb 2008 10:49:27 -0800 (PST)
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:18.104.22.168;
Google-TR-3) Gecko/20071126 Fedora/22.214.171.124-7.fc6 Firefox/126.96.36.199,gzip(gfe),gzip(gfe)
Subject: Re: How to access Gmail Address Book
From: oscarcito <jam...@gmail.com>
To: Google Data API <email@example.com>
Content-Type: text/plain; charset=ISO-8859-1
Ok, Jeff says:
" It's a valid question, but I can only say that there is no supported
way to access GMail contacts at this time. "
Then, what about for gmail mobile to have an option to sync contacts
between mobile and gmail? ANd about to put these contacts in the
correct place in my gmail contacts?
Thanks and sorry for my English from Spain!
On 14 feb, 22:12, "glenn.kitch...@gmail.com"
> in response to johntynan's question:
> "Could it be that a contact list in email implies some degree of
> privacy, but a list of friends on a social networking site implies an
> implicit understanding of openness?"
> It seems like OpenSocial indeed says that "friends" on all social
> websites are fair game but Google's own "contacts" are not. To be
> honest I really don't think that there should be a distinction. If
> one is open, the other should be by logical extension, since the
> information risks are the same.
> The flipside to this argument however, is that you are generally open
> about whom you call a "friend" and you'll share that information with
> everyone. Contacts aren't necessarily the same. For example, someone
> might not want all their contacts to know that they regularly e-mail a
> therapist, or let their boss know that they have an addiction to
> buying anime.
> I think a happy medium would be to make an API that only gives
> "contact" info for the person that's logged in. That way, we
> developers can make programs that see their contacts -- but NOT see
> their contacts' contacts. To do that there would need to be the
> caveat that developers MUST NOT save contact-info for future use (a
> site/gadget/whatever that saves this info could eventually assemble a
> complete social-map, which is what we're trying to avoid).
> Things get difficult, which must be why Google makes those deals.