June 13th, 2003

charlie, computer cat

XHTML compliance

http://www.livejournal.com/support/see_request.bml?id=116956
http://zilla.livejournal.org/show_bug.cgi?id=732

Now I know nothing of CVS and little of Perl, but I do know my way around the style system and how to write XHTML compliant markup. I'd like to volunteer to edit the system styles so that they'll validate assuming that the contents of the variables (e.g. the mood images) also validates. Assuming you're willing to let me at them, how do I go about it?

PS. I couldn't think of where else to post this, but if it's out of place, point me to where it should go.

Blogger API supported

We've implemented a small wrapper of the full Blogger API on top of the LiveJournal API.

So now you can use Blogger clients to post to LiveJournal.

Please help test this (it's now working on the test server) with different Blogger clients. The only one I've tested so far is w.bloggar, and it all seems to work.

To use moods and music, just put at the top of your post:

lj-mood: happy
lj-music: tunes

The settings you'll need for a custom server are:

Host: test.livejournal.org
Page: /interface/blogger

(We've mailed the author to have him add LiveJournal support, so future users of that client won't need to enter custom settings.)

The one screwy thing is date handling. We're always using GMT at this point. The blogger API doesn't seem to send a date. I presume Blogger lets you set your account's timezone? Or, do posts not have times? Let me know how this works.

I looked into supporting MetaWeblog, but it doesn't look worth it, considering it's basically identical to Blogger with some random stuff added and removed. Everybody who supports MetaWeblog seems to also support Blogger. Also, the MetaWeblog API is inconsistent, sometimes having an 'appkey', and sometimes not. I'm not sure what they were thinking.

I might add Moveable Type protocol support, but I can't find any good Moveable Type clients to test with. (what's the best client that supports their full API?)
tux

CVS Commit Poster

Would it be possible to change the CVS Commit Poster (log_accum) slightly?

The code is roughly around about line 180ish - what it does is changes the output slightly so that links to newly committed files work instead of taking you to a diff which causes a 404 error. The new link takes you to the information page of the new file rather than directly to the CVS markup page.

An example of the new output is:

To generate a diff of this commit: cvs rdiff -r0 -r1.1 31Y4/untitled http://localhost/cvs/viewcvs.cgi/31Y4/untitled

Collapse )