Site Maintenance

[theljstaff]

Our apologies for the delay in reporting these details and any inconvenience this has caused. We wanted to make sure we fully analyzed the extent of the situation before publishing details

Comments

[ron_newman]

Will you please fix whatever you did that broke ljdump, ljmigrate, ljarchive, etc. ?

[scarlet_discord]

Seconded!

[alobar]

Me too! ljArchive can d/l posts, but not comments. I want full functionality back!!

[budgie_uk]

Can't download anything (posts/comments) in LJArchive.

Nor can my client (Semagic) load history any longer.

[schnee]

Yes, yes, four times yes!

[siderea]

As I understand it (and I am not a web deve-- Oh, wait, yes I am!) it is not likely to be possible that they can fix this. The changes they made which broke third party applications are, at first blush, changes that needed to happen to close security holes. Those third party applications' developers will need to update those applications to use the new, improved, more secure login process.

[robinhood]

I wish I could upvote this.

[slarti]

While yes, that's a great idea, there's the small problem that none of this "better communication" has happened yet, and thus no one really knows how we're supposed to update our code.

(I'm continuing to really hope that the final answer isn't to scrape login.bml, because that's an ugly ugly hack where before we had... well, not an elegant client interface protocol, but at least one that worked and was relatively lightweight. What does LJ's own iOS client use? They don't really scrape the human-visible pages, do they? Can the rest of us use whatever protocol it uses?)

[av8rmike]

The XMLRPC problem has already been patched; it just didn't make it out in this recent release.

[pne]

Are you sure that fixed "the" XMLRPC problem?

That seems to me to fix *an* XMLRPC problem ("Can't obtain anum") but not the problem of not being able to stay logged in in order to download entries.

[av8rmike]

I don't know which problem the original commenter was referring to. You'd probably know better than I would the nature of what's going on.

Yes, this.

[smarriveurr]

Also, as much as I dislike a lot of things that go on at LJ, including the actual topic of this original post, it's not actually their job to maintain support for third-party tools that happen to operate on their output. That would be on the designers of those tools.

Re: Yes, this.

[ron_newman]

It is their job not to break established published APIs that the third-party tools are using. Which is what just happened.

[draconin]

Definitely seconded! It's really irritating that LJArchive no longer works, particularly as it's not being updated by the author(s). Alternatively, how about providing a tool yourselves that's quick and easy to use along the lines of LJArchive?

[anjak_j]

Co-signed.

[rivendellrose]

Agreed.