To make it worse, I've added an XML-RPC interface to the project. Maybe one day, some open source developer will embed a "what has this artist covered" or a "who has covered this artist" feature into their CD/ MP3 player application. I'd buy that for a dollar.
This was my first XML-RPC server, and I've found that the xmlrpc-epi extensions for PHP are not yet ready for primetime when it comes to creating a server. Not to mention the fact that the libraries that are supposed to emulate the old XML-RPC for PHP APIs are not quite up to snuff in that respect either. Once they get a little more stable (and maybe even documented) I might re-install them.
If anyone has had any good experiences with creating XML-RPC servers using xmlrpc-epi , I'd be interested in hearing about them.
A new and improved version of Pecos should be out in a few days, and I'm debating whether or not I should include the beta-level XML-RPC interface for it (which dynamically registers the methods of the above object when called via aquisition). The load of the old XML-RPC for PHP libraries seems to be pretty substantial.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!