?

Log in

No account? Create an account
August 26th, 2004 - LiveJournal Client Discussions — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Client Discussions

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

August 26th, 2004

Auth Challenge troubles... [Aug. 26th, 2004|12:42 am]
LiveJournal Client Discussions
lj_clients
[dagon]
I'm having a problem with getting the challenge method to work; in fact, I can't get it to work at all.

I've studied the protocol documentation and tried looking at the perl example, but I'm not all that familiar with perl.

For right now, in the first stages of my client development, I'm starting off with the flat protocol. I have the client logging in with the clear text, but I don't know how to do the challenge method.

What exactly am I supposed to send to the server to issue the challenge? And how is it sent?

"Essentially, you generate a challenge by issuing a blank request to the getchallenge method. If your method call is successful you're given:"

How is that blank request to the getchallenge method issued?

Thanks.
link10 comments|post comment

Best Practices Question [Aug. 26th, 2004|11:05 am]
LiveJournal Client Discussions

lj_clients

[royhuggins]
My project isn't actually a client but my question is probably well answered by people who work on clients. So...

I have a collaborative storytelling project that interacts with LJ. It does so at a relatively superficial level (using RSS feeds and screen-scraping) and I'm curious if it would be best to use the LJ client API for the functions it performs.

Function 1) The storytelling system supports linking to stories that are posted in the author's LJ. To avoid dead links, it will check the author's journal (via the RSS feed) to make sure that the story is properly posted in his/her journal.

Function 2) When there are signs that a reader has had trouble finding an author's story in his/her LJ, the system will perform a follow-up check to make sure that the story is still posted in the author's journal. For this function, it screen-scrapes the page that exists at the LJ entry's permalink URL (e.g. http://www.livejournal.com/~royhuggins/123456789.html.) The screen-scrape is necessary because the post may be so old that it is no longer in the RSS feed. The guy's on lj_dev pretty clearly stated that this use of screen-scraping is okay. But I'm wondering if there is a better way.

Question: I haven't studied the client API beyond what mentions people have made in this community and in lj_dev. Before diving into the docs, I would like to see if people who work with it think that it would be worth my time. Would my bot be able to use it to perform the above functions? Would it be better to use the API than the methods I described above?

Thanks very much!
link2 comments|post comment

navigation
[ viewing | August 26th, 2004 ]
[ go | Previous Day|Next Day ]