The Successes of my first AJAX Application: Part 4

This is the fourth part to my successes and failures when creating an AJAX Experimental application.

Part 4: It got me thinking about how to take advantage of the Technorati API.

Because the general idea of the application that I was starting to develop was to help automate the creation of Technorati Tags and other Interesting searches, it was a logical step to start to use the Technorati Developer API (

Technorati offers about 8 different API's which allow you to create applications based around the data that they collect from their spider. The API's are easy to use, and like the Yahoo! ( API's use the REST method of interacting with web services. This has the advantage of easily being able to construct simple requests through the use of a GET command.

Their basic API consist of:

  1. CosmosQuery: Queries information about who in the "Blogosphere"
  2. SearchQuery: Obtains a list of blogs that contain the query that the REST query provides
  3. GetInfoQuery: Information about a user of Technorati.
  4. OutboundQuery: Who the blog you are searching for links too.
  5. BlogInfoQuery: Information about one particular blog.
  6. TagQuery: Information about the number of blogs, and post that contain a specific tag. As well as a list of the blogs.
  7. TopTags: The tags in the popularity range n,m
  8. KeyInfo: Some usage statistics, such as the number of queries that day.

I used the Tag Query, to help determine how popular certain keywords are. (Pulled back from the Yahoo API). This helped me to determine which of the tags were important, and also the tags that would help me get the most exposure for a particular entry.

One thing that this Tag doesn't do, but I think it should, is to return the ranking of the Tag. There isn't a way to find the relative posistion of this tag. All you could do is to incrementally search through the TopTags to see where the tag is positioned.

I didn't take full advantage of the API, because there are some holes in what can be done with it. One of the features that I would like to see is the "related tags". The technorati site contains this information and I think would be a real benefit to developers if we could also access this information.

Unfortuantly the TagQuery is a little slow, it is quite heavy weight, so I had to remove it from the App, however because of this I have a couple of options when I come to redevelop the AJAX application:

  1. Only as the TagQuery to return 1 blog result. This will reduce the bandwidth and I hope the response time.
  2. Develop a Asynchronus Call manager (I have talked about in Part1: It got me thinking Asynchronosly! The call manager will be a queue based priority system, it will work out the most important calls to make first. (It won't be complex).
  3. Ask Technorati to develop a light-weight MetaData interface.

My next application will have to use both of the above points.

Any Thoughts or guidance you can give me. Email me:

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, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.