Log in

No account? Create an account
April 14th, 2002 - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

April 14th, 2002

ver=1 [Apr. 14th, 2002|11:23 am]
LiveJournal Client Discussions
From the news: it looks like LJ has switched to UTF-8.

To indicate to LJ that your client supports UTF-8, you need to set the "ver" key on your requests. People who don't send the key are assumed to be at protocol version 0; version 1 is identical to zero with the addition of UTF-8 support.

Here's my login input from LogJam:
cut for jerronimoCollapse )
link9 comments|post comment

other q&a [Apr. 14th, 2002|11:44 am]
LiveJournal Client Discussions
I was mailed these questions:

The protocol docs used to say to POST to /cgi-bin/log.cgi, so that's what I use. But I just noticed that they now say to post to /interface/flat. Does it make a difference?
Those URLs are effectively identical (one maps to the other), but /interface/flat is the newer, more official one. Because Brad tries to never break backwards compatibility, /cgi-bin/log.cgi should stay around, but you should use /interface/flat to be more "correct".

Just saw that there's an XML-RPC interface to LJ. Does it support anything that the regular protocol doesn't, or does the server just translate it into the regular protocol first?
The latter. Both protocols have equivalent functionality (internally, they're both just wrappers around the same code). I'm not sure if anyone has written anything that uses the XML-RPC interface (the flat protocol is so simple that it's about as hard to use it as it is an XML-RPC library) so I can't vouch for its bug-free-ness, but there it is.
(Update: Currently you can find XML-RPC documentation at http://www.livejournal.com/doc/hack/ .)
link3 comments|post comment

Unicode support in Journalert 0.94 [Apr. 14th, 2002|04:29 pm]
LiveJournal Client Discussions


The Journalert client for Mac OS X has been updated with support for the new UTF-8 LJ protocol extensions. This was this missing link ... now Unicode is fully supported all the way from the (Cocoa-based) GUI down to the server.
link4 comments|post comment

[ viewing | April 14th, 2002 ]
[ go | Previous Day|Next Day ]