Yah, I'm assuming that the DDOS on LJ is extending response times too far for my QotD script to tolerate, but I haven't had enough spare spoons to troubleshoot it yet, or manually back-post. I'll try to get LJ caught up.
I can access LJ from a browser where I've been logged in since before the recent DDoS attacks. Surprisingly (given the next bit) I can even log in and post an entry using a different browser. The command-line client I use (Clive), and my QotD-posting script that depends on it, time out when trying to log in. Could LJ have changed their API in response to the DDoS, in a way that screws up Clive? Annoyingly, it takes almost seven minutes to fail, and it fails wiith a segfault instead of a non-success return code from a normal exit, so the automatic-retry aspect of my script is defeated.
I don't really want to hand-post each of the missing entries by copying from a Terminal window and pasting into a web browser, but I guess I'll do that eventually if I have to. (Except for this morning's test post, the last time I posted an entry, rather than a comment, to LJ/DW/IJ/etc. from a browser was ... uh ... probably at least two years ago, if anywhere near that recently? I'd much rather just do
foreach foo (3 4 5 6 7) ljfixtemp 2011120$foo end
but i guess that even if I have to hand-post 'em, at least it'll be copy+paste (after I modify the temporary script to save entry contents for copying) ... but if this is an API change that Clive needs to be hacked to catch up with, I may just give up on LJ entirely until I've got enough free time to delve into Clive's internals and whatever API docs I can make sense of (unless Clive suddenly starts being maintained again -- I haven't checked lately). I want to make it easy for my only-reading-LJ friends to know when I've posted something to DW, but I've got way too much else on my plate right now.
Don't sweat it on my account; I can just add Dreamwidth to my daily list. (I see some of them on FB, but between intermittent reading and high volume there, I'm more likely to miss stuff.) You may want to post to LJ about what's up and see how many people are still keeping up with it there, though.
LJ
FYI, QOTD posts haven't been showing up on LJ for the past few days.
Re: LJ
Re: LJ
I don't really want to hand-post each of the missing entries by copying from a Terminal window and pasting into a web browser, but I guess I'll do that eventually if I have to. (Except for this morning's test post, the last time I posted an entry, rather than a comment, to LJ/DW/IJ/etc. from a browser was ... uh ... probably at least two years ago, if anywhere near that recently? I'd much rather just do
but i guess that even if I have to hand-post 'em, at least it'll be copy+paste (after I modify the temporary script to save entry contents for copying) ... but if this is an API change that Clive needs to be hacked to catch up with, I may just give up on LJ entirely until I've got enough free time to delve into Clive's internals and whatever API docs I can make sense of (unless Clive suddenly starts being maintained again -- I haven't checked lately). I want to make it easy for my only-reading-LJ friends to know when I've posted something to DW, but I've got way too much else on my plate right now.
Re: LJ