Main
Latest
- ISDSL Stats
- Twitter Pwned Again
- Jabber ID Change
- charlvn.za.net downtime
- Neotel NeoConnect Price Comparison
- Eskom? No, the stove!
- Back in George!
- @media 2008
- Finally charlvn.za.net gets updated
- Clickpass
Archives
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
Google Social Graph API
I just read a fairly old post titled URLs are People, Too on the Google Code Blog. The following paragraph sounded very similar to our initial discussions regarding SDSN:
So you've just built a totally sweet new social app and you can't wait for people to start using it, but there's a problem: when people join they don't have any friends on your site. They're lonely, and the experience isn't good because they can't use the app with people they know. You could ask them to search for and add all their friends, but you know that every other app is asking them to do the same thing and they're getting sick of it. Or they tried address book import, but that didn't totally work, because they don't even have all their friends' email addresses (especially if they only know them from another social networking site!). What's a developer to do?
I experimented with the Google Social Graph API for a couple of weeks now but I'm not entirely sure I want to make use of it. With my experience, the data gets cached on Google like all of its search results. In other words, if you make changes on the web, it won't necessarily be immediately reflected on the API. If you do your own parsing, obviously this places you in control, but if you want to rely on Google that might be a frustrating thing for people who just set up their XFN blogrolls (for example) and then want to have your site make use of it.
This is at least as far as outgoing links are concerned. As far as incoming links are concerned, it's an entirely different story. To find all of those you would have to go and crawl the entire web, much like Google! Certainly not something I have the resources for at this point in time. So although the results might not always be 100% complete and updated, at least you can get a rough idea of who is linking to you.
Copyright © 2004-2009 Charl van Niekerk. All articles are released under the Creative Commons Attribution 2.5 South Africa licence, unless where otherwise stated.
0 Comments
Post a Comment