Difficult solution for a simple location problem?

Stuff stuff stuff:

#!/usr/bin/perl - the location of perl in all LJ code files

#!/usr/local/bin/perl - sometimes required for people, for various reasons. Requires changing the top line in a ton of code files.

Are there any clean ways for handling these differences? It's really hackish to just write a script to run and change every one of the magic lines after each cvs update.

"Invalid password" when calling login method over XML-RPC

A week or two ago my LJBackup client started being unable to login - I didn't change anything (I think!), but now I always get an "Invalid password"…
cl-journal livejournal client

Hey everyone, I'd like to present a livejournal client that I wrote to fulfill my needs but maybe there are other people that can find it…
SessionGenerate and ljloggedin

Are there any information after release 86 and changes in cookies scheme to use sessiongenerate? It returns ljsession key, but this key is not enough…

Post a new comment
13 comments

"Invalid password" when calling login method over XML-RPC

A week or two ago my LJBackup client started being unable to login - I didn't change anything (I think!), but now I always get an "Invalid password"…
cl-journal livejournal client

Hey everyone, I'd like to present a livejournal client that I wrote to fulfill my needs but maybe there are other people that can find it…
SessionGenerate and ljloggedin

Are there any information after release 86 and changes in cookies scheme to use sessiongenerate? It returns ljsession key, but this key is not enough…

Log in

Difficult solution for a simple location problem?

"Invalid password" when calling login method over XML-RPC

cl-journal livejournal client

SessionGenerate and ljloggedin

Error

"Invalid password" when calling login method over XML-RPC

cl-journal livejournal client

SessionGenerate and ljloggedin