Matthew's Journal

I have been automatically cross-posting my DW entries to LJ for some time now (since April 2017), and AFAICT this has mostly Just Worked.

The DW folks recently said that LJ have stopped co-operating with them about the cross-posting feature; they used to pass-list DW's IP so that even if one person put in the wrong password, most people would still be able to cross-post and now refuse to do so (or even acknowledge that they used to).

I have also been pointed at section 9.2.6 of the current LJ ToS, which prohibits "use [of] automatic scripts (bots, crawlers etc.) to [...] interact with the Service".

So it looks like it will no longer be possible to have my DW entries cross-posted to LJ (and indeed the most recent couple of entries haven't made it across); I'll copy this entry over by hand, but I don't think continuing to do so regularly is going to happen.

If that's going to be a problem for you, do comment, but do please consider joining me over at DW (or using your OpenID account to read me on DW)...

If you use OpenID to log into Dreamwidth (e.g. by using your LJ account), you may well have noticed it isn't working properly at the moment. This is because the most recent code push broke the main OpenID login form; a fix has been merged into the code, but presumably won't be deployed until the next code push.

In there mean time, there is a workaround: even though the main OpenID login form is broken, you can still use the comment form to log in.

If you click reply on any public entry, choose OpenID as your user type and tick the login box, and then click preview, that should log you in (without posting a comment), and then you can use DW as normal.

Thanks to angoel for reporting the bug to me (and confirming the workaround works) and to roadrunnertwice for the workaround.

ETA: I think the bugfix was applied during yesterday's code push.

Anyone know what's up with LJ? The status page is hardly enlightening, and after it being down for nearly all of yesterday, I can read entries now, but can't post entries or comments (I just get blank returns from the update pages, no matter how often I hit refresh).

It's getting very annoying :(

I know I don't currently post here very much; I currently post at LJ, and don't have any immediate plans to change this. I guess if there were DW-only people who wanted to read my writings, I could start cross-posting, but there doesn't seem to be demand for that.

Anyway, I thought on the current DDoS on LJ. Given that DDoSes are bad, and things I don't want to encourage, I'd like to suggest people don't migrate to DW right now - that, to me, would be to be seen to be supporting the DDoSers.

I have a longer post I want to make to LJ, but that will probably have to wait for the DDoS to abate.

Given that DDoSes are bad, and things I don't want to encourage, I'd like to suggest people don't migrate to DW right now - that, to me, would be to be seen to be supporting the DDoSers.

I've had the same userpic ever since I started my LJ. stephdairy has very kindly cleaned up the picture somewhat, but I find myself strangely unwilling to change from the "original". So, I thought I'd see what you all thought :)

[Poll #532193]

Tags. Great idea, enable my readers and I to search for entries relating to a particular topic, with much more flexibility than the "memories" system.

Except, that they won't work with S1 journals. When I joined LJ, S1 was the only thing going, and I chose one of the available styles, and settled into it. S2 came along, and I played a bit, but I couldn't get it to look like my nice, comfortable S2 style. So I shrugged, and stayed with S1. After all, whilst they would only introduce whizzy new themes and suchlike into S2, that didn't matter, as I was happy with the way my journal looked.

I grumbled about the lack of tags support in S1 journals (if you try and click on a tag in an entry of mine, you just get "sorry, tags only work with S2"). The line I'm getting in the support request I opened is "well, you can just move to S2, so do that if you want tags". The thinking is that the vanilla S1 styles are available as S2 styles. This attitude annoys me because it's not true.

( text of my most recent comment in the support thread )