I am just sitting here reading about the Feedster API, and I am wondering what is the point.I like the idea of them providing an API, but I just don't get what it is this API is supposed to provide. Is it supposed to be a list of feeds and related data belonging to a site? I was hoping that they would provide a content search.However syaing that, you can quickly get do a search by substituting the query paramaters in their own search on their site, like the ones I used to provide.Perhaps I would like to see searches through an API, but I would also like to see more meta data about searches, so for instance if I did a search for Kinlan on feedster through an API it would return information like the number of blogs "Kinlan" is mentioned in. The number of pages etc. You could instantly see the popularity of certain searches then (I could have a search that provides my page users with a count of all the people talking about me - Zero at the moment). Also cute little API's that will enable users to see the top searches every hour. Just little things like that. I could see a lot of people integrating these features into their sites. I would.I use the technorati api and the Yahoo API to help me categorize my blog entry. I used to have links to feedster searches (which I removed because they took me too damn long to create - the query string for searching is MASSIVE). If I could rate my searches with the number of results before I check the results and other Meta data of my search I would find that quite handy .Publishing search results as an RSS Feed is cool though! :)Also to use the API, I have to provide my private key, this means that I have to hide it, that means that I have to provide a proxy script on my server to get to the results data. I would like a way that I could get to the API without having to proxy all the requests from my site. Yahoo make you use an Application ID, that ID doesn't have to be secret it is just for reporting.
About Me: Paul Kinlan
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.