04-webfinger | 02. Pre-developed technology | social

04-webfinger Utilization

Zheng Zhe 201005 is affiliated with section 02. Technical pre-Research

Kuber's socialbadge also uses webfinger to obtain its associated information based on the e-mail address entered by the user. Of course, kuber still uses social graph to obtain association information, because the data of webfinger can be called by social graph.

What is webfinger?

Finger is a UNIX command. You can enter the finger email@domainname.com in UNIX to know the information related to this email account. It can be understood that the finger command is an attempt to use an email account as the online id card of each netizen in the early stages of network development.

What is the purpose of webfinger? That is, by enabling the user to append the metadata information to make the existing Email address more valuable. Metadata includes the following:
* Personal data to be disclosed
* Link to the ID provider (for example, openid server)
* Public Keys
* Other services with the ID of this email address (for example, the usernames of all services of Flickr, Picasa, smugmug, Twitter, and Facebook)
* Indicates the URL address of a network identity.
* Personal Data (nickname, name, etc)
* Or even a link that does not contain public metadata but only points to a terminal containing metadata.

 

Google launched webfinger to make your email more useful and become an email-centric openid.

Webfinger is now integrated into Google's various social APIs

You can find the webfinger trace in the buzz API Doc. The buzz api faq says: We plan to introduce "distributed profile and contact information with webfinger 』. Google also said :『

We 've now enabled webfinger for all Gmail/Google profiles with public profiles.

』

The query address of Google webfinger is:

Http://www.google.com/s2/webfinger? Q = Acct % 3 azhengyun % 40gmail.com

That is, the input keyword is "Acct: foo@example.com ". Acct indicates the account.

The above query returns:

<? XML version = '1. 0'?>
<XRD xmlns = 'HTTP: // docs.oasis-open.org/ns/xri/xrd-1.0'>
<Subject> Acct: zhengyun@gmail.com </subject>
<Alias> Http://www.google.com/profiles/zhengyun </Alias>
<LINK rel = 'HTTP: // portablecontacts.net/spec/1.0' href = 'HTTP: // www-opensocial.googleusercontent.com/api/lele/'/>
<LINK rel = 'HTTP: // portablecontacts.net/spec/1.0?me' href = 'HTTP: // www-opensocial.googleusercontent.com/api/lele/110589389080388532670/'/>
<LINK rel = 'HTTP: // webfinger.net/rel/profile-page' href = 'HTTP: // www.google.com/profiles/zhengyun' type = 'text/html '/>
<LINK rel = 'HTTP: // microformats.org/profile/hcard' href = 'HTTP: // www.google.com/profiles/zhengyun' type = 'text/html '/>
<LINK rel = 'HTTP: // gmpg.org/xfn/11' href = 'HTTP: // www.google.com/profiles/zhengyun' type = 'text/html'/>
<LINK rel = 'HTTP: // specs.openid.net/auth/2.0/provider' href = 'HTTP: // www.google.com/profiles/zhengyun'/>
<LINK rel = 'describedby 'href = 'HTTP: // www.google.com/profiles/zhengyun' type = 'text/html '/>
<LINK rel = 'describedby 'href = 'HTTP: // s2.googleusercontent.com/webfinger /? Q = Acct % 3 azhengyun % 40gmail.com & amp; FMt = foaf 'Type = 'application/RDF + xml'/>
<LINK rel =' Http://schemas.google.com/g/2010#updates-from' Href =' Https://www.googleapis.com/buzz/v1/activities/110589389080388532670/@public' Type = 'application/atom + xml'/>
</XRD>

Where, it returns

Https://www.googleapis.com/buzz/v1/activities/110589389080388532670/@public is my Google buzz public update.

The alias node is: "The <alias> element indicates an alternative Uri the account might be known. this wowould typically be an HTTP profile page, email address (prefixed with A mailto: URI scheme), or another account Uri. the first link provides the location of the user's portable contacts service. therefore, it generally corresponds to the user's profile address.

 

Google's query portal provides us with the possibility of obtaining the profile address based on the input email address (especially the Gmail address.