This my first post, feels like a good time to pipe in. I've got a few things on 
my plate, some of you may be interested in.

* TypePad Atom API - Updating and overhauling the Atom API for TypePad. I've 
been working with Byrne Reese internally to get a really solid spec hammered 
out. So far things are looking really good.

* TypePad Atom feed support - TypePad Currently has Atom (v1.0) feeds for blogs 
but I've been extending that quite a bit. The general idea is that TypePad will 
provide the following atom feeds: recent blog entries, recent blog comments, 
individual entry + comments, blog category feeds, photo gallery, individual 
image + comments + meta info, TypeList feeds, etc etc. I'm also adding support 
for the threading extension provide by James Snell. The entire process has been 
very fun and educational.

* Fence - Fence is a small application that was originally a proof-of-concept 
learning project to interact with the TypePad Atom API but has become a full 
project. It is written in cocoa/objective-c (my first cocoa app) and uses a 
home grown Atom framework resembling the perl module XML::Atom. I've put a 
project blog out that has more information and screenshots ( 
http://blog.socklabs.com/typepad-uploader ). The Atom cocoa framework can 
interact with any Atom API friendly website so its not just TypePad specific.

* iPhoto export tools - I've also created a few different iPhoto plugins that 
export to TypePad using the Atom cocoa framework as mentioned above.

Thats it for me, as you can see most of my development is in Perl but I do some 
mac os x and cocoa stuff as well. Questions? Comments?

# Nick Gerakines

On Fri, May 05, 2006 at 09:11:25AM -0400, Robert Sayre ([EMAIL PROTECTED]) 
wrote:
> 
> I've been working to add Atom support to Firefox 2. Some other Firefox
> devs are toying with exposing internal data like history and bookmarks
> as Atom feeds.
> 
> What software are you writing?
> 
> --
> 
> Robert Sayre
> 
> "I would have written a shorter letter, but I did not have the time."
> 
> 

Reply via email to