τεχνοσοφια

I finally pushed out some embarrassingly outdated WordPress plugin updates a few moments ago.

• Updated unAPI plugin with a patch contributed by Jay Luker that removes the hard-coded "wp_" table prefix. The updated version of the plugin has been tagged as 1.4.1.
• Updated LinkPURL plugin with a patch contributed by Mark Matienzo that enables partial redirects. I made some additional tweaks to the plugin to make this feature configurable via the WordPress management UI. This has been tagged as 1.1.
• Created a new unAPI plugin branch for Mark Matienzo's Scriblio-oriented tweaks. The branch is called 1.4.1-anarchivist-scriblio and it contains the scriblio.diff file. I have yet to integrate the diffs, as the file that was patched has changed since the patch was issued. If anyone is interested in working on unAPI/Scriblio integration, please get in touch with me.

And here is my to-do list which I hope will keep me honest.

• Update OAI-ORE plugin to support version 1.0 of the ORE specification.
• Add per-post (and per-page?) resource maps that wrap all embedded images and links.
• Enable "cool URIs" for all resource maps.

It is my hope that I'll get to those sometime before the summer begins. :)

On Monday I woke up with a very mild and very annoying bronchial infection. Doctor Me prescribed two days of rest, relaxation, and chicken soup. Where "chicken soup" is "finally dropping the unreasonably expensive and embarrassingly outdated web hosting package at Speakeasy and transferring all of my domains and content to Dreamhost," that is. I am now paying less than a third of what I had been for a hell of a lot more features. And, I must say, administering DNS records, transferring files, and upgrading long-neglected software is rather amusing when you're loopy and feverish.

My experiences thus far with Dreamhost are very promising. I'm impressed but perhaps that's because I've been in the web hosting ghetto for so long. I understand there will very likely be downtime and sluggishness — that I can deal with. Being shackled to 1999 technologies for $30/mth, while my e-mails go unanswered, not so much.

I upgraded both Technosophia and my wife's blog to the latest WordPress release (2.3) from something ridiculous like 2.0.3. In doing so, I also switched to the svn upgrade configuration Ryan Eby detailed a while back.

I crossed my fingers and it turns out the unAPI server plug-in still works in WP2.3. Huzzah! Not sure if it works in the 2.1 or 2.2 branches, but I suspect it does.

This is a slightly modified (read: rough) transcription of the talk I gave at this year's NJLA conference, called "Library Revolution." Continue reading…

I've finally gotten around to updating the unAPI plugin for WordPress so that it fits into the WordPress plugin architecture, making it simple to install and maintain. I'm calling it version 1.0 since it's the first substantial release of the plugin since I got involved. Just unzip that sucker (or check the code out) to wp-content/plugins/unapi and do the rest via the administration pages, including activation and identifier configuration.

I updated the plugin page and imported it into the svn repo hosted at wp-plugins.org.

This was my first WP plugin, so I would appreciate any feedback. All you folks that are using it should try stripping out the old version (which requires hacking some theme files) and plugging this in.

What is unAPI? Why should you care about it?

Read Introducing unAPI, in Ariadne issue 48, for answers to those questions… and more! Here's the obligatory snippet:

Common Web tools and techniques cannot easily manipulate library resources. While photo sharing, link logging, and Web logging sites make it easy to use and reuse content, barriers still exist that limit the reuse of library resources within new Web services. To support the reuse of library information in Web 2.0-style services, we need to allow many types of applications to connect with our information resources more easily. One such connection is a universal method to copy any resource of interest. Because the copy-and-paste paradigm resonates with both users and Web developers, it makes sense that users should be able to copy items they see online and paste them into desktop applications or other Web applications. Recent developments proposed in weblogs and discussed at technical conferences suggest exactly this: extending the 'clipboard' copy-and-paste paradigm onto the Web. To fit this new, extended paradigm, we need to provide a uniform, simple method for copying rich digital objects out of any Web application.

(Full disclosure: I helped a bit with this article. Thanks to Dan et al. for giving me the chance to sully their otherwise well-thought out article.)