fav.or.it API - The future of comment distribution

January 7th, 2008 • Related • Filed Under

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

I have just announced the new API for fav.or.it over on the fav.or.it blog. As most of my readers are very technical I thought I would give you all the heads up on it as some of you may be interested in making use of it.

Here is the quick summary.

The fav.or.it API is designed to allow access to many of it’s core services. The first round of exposed requests allow comments to be distributed from external clients through fav.or.it back to the host of the specified blog. It is our desire that by opening up our core platform that we start a new flow of comments around the blogosphere and that by doing so everyone will benefit from a ‘better conversation’. The API will become available for testing sometime this week, we will make a further announcement when it is ready. We hope that this documentation will allow you to get started on developing exciting applications.

For full documentation on the API we have a Google Group which has detailed description of each request and more detailed information on all our services.

There Are 3 Responses So Far. »

  1. Comment by nick halstead on 8 January 2008:

    this is a test comment its really great

    sent from: fav.or.it [FID1353]

  2. Comment by Adam on 9 January 2008:

    Fav.or.it looks quite interesting. Wouldn’t mind giving it a try!

  3. Comment by AMS on 17 January 2008:

    Hi Nick,

    I’ve checked out the API docs, it seems promising, but hmm, I’d like to make a suggestion (before it goes public and gains much much more attentions) about “read” requests (e.g., commentstatus), It’s great that you gonna provide the response in multiple formats, but the URI for different formats is not … let’s call it “well-structured”.
    It actually means multiple endpoints for only one request which is not the best possible way to design a RESTful Web-Service.
    I think it’d be better if you chose one of the return formats as the default one and then provide users the ability to chose the format using a GET parameter.
    You know a “.” (dot) in a URI ruins all the fun! :)

Post a Response