Here’s my skeleton for my magical REST interface. It’s still missing a lot of method calls for Flickr and Vimeo, but the guts are there and the remaining methods will be done in priority when I need them.  Right now it supports automatic caching and logging via simple options.

At some point I’ll probably put it on a public SVN repository, but for now you can have the tarball.  There’s a README in the file with a simple sample. And the source is pretty self explanatory so you should be able to figure it out if you want to.

The remainder of the work will be done in the order I see fit.  Likely read-only methods (most of the getters) Authentication and write methods will be much much later.

I’ll also add more RESTful interfaces as I need them.  Probably Facebook soon, Twitter later.  Who knows.

Drop your comments here if you’ve got any questions.

I was reading a post over on Mashable about the most popular twitter clients and I found it somewhat fascinating.  As of the somewhat recent Zend Framework 1.7 release, there was a new service added. Zend_Service_Twitter  – which gave me a few ideas on what to do with my own twitter account and actually feed it some information.

One thing I’m going to do, is with the new rewrite of pileofcrap.org is to have users be able to auto-update their twitter when they post a new article or photo to their highly improved PoC Blog thing.  Thanks to Zend it’s pretty simple:

$twitter = new Zend_Service_Twitter($user, $pass);
$twitter->status->update('This is my new update');

And it’s done.  Used in conjunction with tinyurl or is.gd’s APIs I can automatically do micro-updates to twitter and have all the followers of all my users automatically be notified of the new content.  It’s pretty slick, huh?

Maybe someday pileofcrap.org can be on the top client list.