(2003-05-13) Technorati Api
Dave Sifry's provided an API to the Technorati data. Dave Winer wishes for XmlRpc, which re-raises the ReST debate, which Tim Bray gives a good intro for. But Dave says it was beside the point, which is that he had to hand-write more code to handle the interface, which would have been automatic with XmlRpc. It would be interesting to see a more detailed side-by-side comparison of the steps to handle the API, esp when the API changed the second day. Was Dave ignoring tools that are available? Or is that the tools aren't available in Frontier Script? I'd like some meat...
- May17: Mark Bernstein follows some of this conversation, also pointing to the quick evolution of Aaron Swartz's solution XmlTramp http://www.aaronsw.com/2002/xmltramp/ |toolkit Dave Winer hates the use of an App Key. Tim Bray [agrees](http://www.tbray.org/ongoing/When/200x/2003/05/12/Soap Again) it's annoying. Why not use BasicAuth for authentication, and make the App Key the ID? Then the App Key doesn't have to be part of the URI.
It's not a bad idea. I can even make it more human-readable, and rther than ask for the appkey, I can ask for the user's Technorati username/pasword, so it is easier to remember. The appkey is a nice way to associate a single resource with a user using a one-way hash, that's all. Interesting points. --Dave Sifry
Edited: | Tweet this! | Search Twitter for discussion
No backlinks!
No twinpages!