fub: A photo of an ADM3A terminal (ADM3A)

I saw a post on dw_maintenance, partly in Russian, that imports could be slow because of the massive influx of new accounts that want to import their LJ-based blog to DW. So of course something is going on — turns out that in order to post, users have to identify themselves. This is because a law in Russia, another way for the authorities to crack down on dissent. And because LJ is owned by a Russian company, it has to comply.

Elsewhere, someone linked to this thread on Bluesky by one of the owners of DW on what that might mean for the non-Russian users of LJ. And maybe it’s alarmist, but I agree it doesn’t look good. It can’t be bad to be prepared.


I have migrated my blog to a WordPress instance on my own domain, but I still had entries that included images hosted on LJ — because I have a permanent account there, I had some image hosting space and I used to it upload photos and pictures to use in my posts. When I migrated the posts, the images were left where they were, and the WordPress entries simply linked to the images on LJ.

So I located all of those, downloaded them from LJ and uploaded them to the WordPress instance and replaced every image. So even if LJ goes down outside of Russia, I still have those photos in my entries.


Crossposted from my blog. Comment here or at the original post.
fub: A photo of an ADM3A terminal (ADM3A)

andrewducker reminded me that LJ (and, hence, also DW) have a post-by-email interface. The WordPress plugin I used to cross-post to LJ uses the XMLRPC API, but that did not seem to work on DW (and, to be frank, I also had to modify the code to get it to work on LJ too). The API situation at DW is a bit of a mess: the classic “the old API is unsupported, the new API is not finished yet”, which is always a lot of fun…

So messing around with that would be complex and time-consuming, but formatting a mail in a certain way and sending that is, actually, very easy to do in PHP — so I went for that.

The only drawback is that the previous interface would update the entry on LJ when I updated the entry on my blog. The XMLRPC API has an ‘edit’ mode that allows you to do so, and the ID of the entry was recorded in the WordPress instance, so the code could refer back to that entry. Of course, since post-by-mail is essentially ‘fire and forget’, there is no feedback. But I did not use that feature a lot. If it happens, I just need to update the DW entry manually. That should not pose too much of a burden.


This is the first non-test post that will go through the new crossposting code — it should work, fingers crossed. If you see this on DW, then it worked!

(Or not, and I fixed it, and then deleted the entry on my blog and re-posted it. I’ll never tell.)


Crossposted from my blog. Comment here or at the original post.

Profile

fub: (Default)
fub

January 2026

S M T W T F S
    123
45678910
11121314151617
18192021222324
25262728293031

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jan. 8th, 2026 02:12 am
Powered by Dreamwidth Studios