ree: (words won't come together)
I am sick. Boo! Common cold, sore throat, exhausted, but pretty much pain free. The offspring seems uninfected. Good thing I have plenty of hand soap.

I keep forgetting to ask this... good Dreamwidth people, what are you using to backup your Dw account(s)? I had been using ljarchive but it started choking when I tried to backup a community with comments. I think it began around the time Dw forced HTTPS but I can't be sure.

Anyway, rec me your Dw backup software, please! I have seen http://wiki.dwscoalition.org/notes/Compatible_clients and https://zvi.dreamwidth.org/477997.html , but they are oooooold and I don't have the energy to try all the relevant options in sequence.

(If you want to tailor an answer to me specifically: I'm on Win 10. I'd prefer a GUI but I can work with a command line - I used to do a little MU* Telnetting, learned to FTP on the Windows command line, that sort of thing. I don't have perl or anything installed on my computer, but if I need it to make my backup dreams come true, I'm willing to give it a go.)
ree: photo of a woman with long blonde hair and glasses (Dream - blue gradient)
The wiki says ljArchive doesn't work with Dreamwidth. That's news to me; within the last week, I imported an old LJ to Dreamwidth and promptly used ljArchive to back it up.

Checked my new backup. Yup, everything's there, and it's not the original LJ version - the comments all say ext_### instead of the LJ URL or username.

I logged into the wiki to change it, but then I realized that I don't know why it was marked "no" for not working. Did someone mark it "no" because ljArchive, known to be picky and stop working at the drop of a hatpin, failed on their first try and they never retried? Or is there some upcoming code push that will break all the API stuff; even though ljArchive works now, maybe it's preemptively labeled non-working because that will soon be true?

Anxious Ree is trepidatious. I decided not to edit the wiki.

For what it's worth: Windows XP, ljArchive 0.9.7, works fine for me. I've had ljArchive toss a wobbly before when it found an incomplete HTML tag in an entry; fixing my markup allowed ljArchive to work again. (I think if you don't have a > for every <, it breaks ljArchive's XML parser.)

If you know, off the top of your head, of an upcoming API breaker, would you reply here, please? I know there are down-the-line plans to retool all the API stuff, but I didn't think there was anything committed just yet.

Style Credit

December 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 2023

Syndicate

RSS Atom

Expand Cut Tags

No cut tags
Powered by Dreamwidth Studios
Page generated 2025-07-20 12:27 pm