code.google.com — With so many websites to join, users must decide where to invest significant time in adding their same connections over and over. For developers, this means it is difficult to build successful web applications that hinge upon a critical mass of users for content and interaction. Developers can now utilize public connections their users have already
Feb 1, 2008 View in Crawl 4
ssj2119Feb 3, 2008
good deveopment
smackheroFeb 3, 2008
well, typically when you block someone on a site, your block list is not publicly available. so while that might be a cool feature, it would be hard to implement without breaking this privacy practice. perhaps you don't care if the person you block finds out that you've blocked them (spammers/trolls for instance), but right now most social networks keep that information hidden from other users.a quick hack that can be used in the mean time would be to search users with connections to "<a class="user" href="http://www.rnc.org/">http://www.rnc.org/</a>"
bingopowerFeb 3, 2008
That sounds like a bit of an oversight...ages ago, when I was toyed with writing IRC clients (they were fun to test, I guess), I added an "aquaintance" functionality, the attributes of which would would determine if someone was friend or foe.
ascalyukFeb 26, 2008
interesting to see list of sources (social networks etc.) which Google Social Graph API use. This will be useful in future for internal sites integration.
a12alexFeb 28, 2008
I totally agree with you.
jgeekFeb 29, 2008
yet another test - faces for URL's: <a class="user" href="http://www.servletsuite.com/socialwidget.htm">http://www.servletsuite.com/socialwidget.htm</a>
findhostcouponsMar 22, 2009
Very interesting story and really good news from Google!