Recently, I downloaded the 0.3 beta version of Community Server. My personal blog is powered by .Text, the predecessor of CommunityServer. As both .Text and CommunityServer are supposed to support the MetaBlogApi interface, I first decided to just support this common standard in Finch. To my discontent, I found that the support in .Text for MetaBlogApi is, although not bad, not complete. Especially the support for categories seems a bit buggy. No harm done: I implemented the categories for .Text in a special .Text-specific work-around, which seems to work fine.
Then CommunityServer was announced. It is to be the 1.0 version of .Text, although it contains much more functionality, like forums and image galleries. My first take on the 0.3 version: it looks nice, works easily and the integration between the three parts seems to be done well, without requiring all parts to be used. Good work.
The MetaBlogApi support by the CS blogs application on the other hand seems to have been ignored a bit. No matter what method I try to call, I invariably get a 500 server error. As the sources are not shipped with the beta, it is hard to say what the problem is, but something is terribly wrong in there. And even when an exception occurs, this should be reported in an XML-RPC error structure.
I do hope this will be fixed. I will try to file a bug report, although I'm not sure where to do this. The CommunityServer forums I guess.
I'm still aiming at supporting CommunityServer in Finch, but without API support, it all ends
UPDATE: The errors I was encountering where caused because I was accessing CS with the hostname in the URL instead of 'localhost'. When setting CS up, I had entered localhost to be the domain name. CS doesn't work when accessed through a different host name. Still a lot of errors from the API though