com
Sample Operations 
http://friendfeed.com/api/feed/public
http://friendfeed.com/api/feed/user/sopmac21379
http://friendfeed.com/api/feed/user/sopmac21379/comments
http://friendfeed.com/api/feed/user/sopmac21379/likes
http://friendfeed.com/api/feed/user/sopmac21379/discussion
http://friendfeed.com/api/feed/user?nickname=bret,sopmac21379
http://friendfeed.com/api/feed/home
http://friendfeed.com/api/feed/search?q=friendfeed
The public web is made up of linked pages that represent both documents and people. Google Search helps make this information more accessible and useful. If you take away the documents, you’re left with the connections between people. Information about the public connections between people is really useful — as a user, you might want to see who else you’re connected to, and as a developer of social applications, you can provide better features for your users if you know who their public friends are. There hasn’t been a good way to access this information. The Social Graph API now makes information about the public connections between people on the Web, expressed by XFN and FOAF markup and other publicly declared connections, easily available and useful for developers.
Update: MySpace, SixApart, and Bebo have officially joined the OpenSocial!
TechCrunch >_ “OpenSocial is a set of three common APIs, defined by Google with input from partners, that allow developers to access core functions and information at social networks:
Hosts agree to accept the API calls and return appropriate data. Google won’t try to provide universal API coverage for special use cases, instead focusing on the most common uses. Specialized functions/data can be accessed from the hosts directly via their own APIs. (more…)
{via TechCrunch} :: MySpace is gearing up to launch MySpace Platform, according to a number of third party developers who’ve been contacted for input on the product. While this has been rumored since
June, this is the first indication that the service is preparing to actually launch. And we also have information that suggests that it will be announced next week at the Web 2.0 Conference in San Francisco.The new developer platform, like Facebook Platform which was announced in May, will essentially be a set of APIs and a new markup language that will allow third party developers to create applications that run within MySpace. Developers will be able to include Flash applets, iFrame elements and Javascript snippets in their applications, and access most of the core MySpace resources (profile information, friend list, activity history, etc.). Applications will need to be hosted on MySpace servers.
And in a big change in strategy for MySpace, developers will be able to serve their own advertising within their applications, and keep 100% of the revenue (Facebook also allows this).
Suddenly Facebook, with nearly 5,500 third party applications, has significant competition around their platform - Within a month both MySpace and Google (see our post here) will probably have launched their own services. Platform competition is great for developers, but it also means they need to create and maintain separate code for each platform they choose to play on. Someone is hopefully working on a startup that will streamline that process for people. Whoever does it first, and best, can have a winner on their hands.
Virtually everyone on the Amazon Web Services team has occasion to interact with our developer customers from time to time. This rich source of product feedback gives us a lot of insight into ways that we can do an even better job of meeting their needs as we grow and enhance each of our web services.Some of the developers building applications with Amazon S3 have been asking us about an SLA, or Service Level Agreement. An SLA defines the minimum acceptable level of performance from a service along with some sort of penalty for not meeting expectations. A typical SLA actually defines a performance or reliability boundary which is somewhat lower than what the system is actually designed, built, and expected to deliver.
We know that many of our customers, including a multitude of teams within Amazon, are using S3 in mission-critical ways and need a formal commitment from us in order to make commitments to their own users and customers.
After talking to many developers to make sure that we fully and precisely understood what the term “SLA” meant to them, we were able to start defining one that was appropriate for S3.
I am very happy to announce that, effective October 1, 2007, The Amazon S3 Service Level Agreement is in effect. (more…)
