Crossposting doesn't work for anyone currently. It's a problem that seems to be on since around 24th/25th of January. (I could still make a post that crossposted on January 24th, but others seemed to already report failures on that date, so that's why I add 25th as a date when it began to work no more again.) Worse than last time, this time simultaneously importing content from Livejournal doesn't work either! Been pondering for days how to compensate this state of things... Which of the two things is the one to get fixed quicker. So I can continue to post as I like to.
Failures in importing content from Livejournal had popped up months ago already before and finding a technical solution to that took weeks, more than it usually took to find a new knack to make the crossposter get through LJ's spam protection mechanisms.
I've been wondering about that too (seemingly it's the same for others too, if you take a look into the support forum).
As far as I've taken a look into LJ's past login sessions, it seems like the crossposter doesn't even make it to enter LJ as it's not listed there since said dates. Before, you see it listed as "Dreamwidth Studios XPoster". The import feature, in contrast, seems to make the login as it appears as "Dreamwidth Studios Content Importer" in the list. Only it seemingly isn't able to do anything or perform the action it has the command to do.
It's odd we've not seen anything from DW Support about this if only a "we're looking into it". I wonder if the slowness of notifications means they're not getting the messages about this - though I'd expect them to be better hooked into the community than that.
It might also be they're already looking into it, but the way to get a workaround is not that easy this time. On the starting page of the support area, they've been listing the issue with crossposting possibly failing at times for long now, so it's not like a completely new problem and not like it can be brought to a halt. It's going to happen again from time to time (e. g. if Livejournal changed something in its code again).
It's been an on-and-off problem for years - particularly when interacting with spam blockers, but the DW team are usually very good at comms, even if its only to say "we know this is a problem for a lot of people at the moment, we're working on it."
Edit: Tried it myself now and although the queue gives out errors during the course of the process, somehow the importer makes it all the way to the end, completing every step. So that makes entries and comments basically can be imported from LJ to DW.
I tried vice versa - crossposting directly from here to LJ -, this still seems to be dead, not working. Tested it with a short private entry, and - no, you don't get a crosspost link underneath your entry here. So that lane is still closed.
But somehow something seems to move behind the scenes, you can say...
It's weird that the import worked, judging by the post in dw_maintenance. I mean, I get that sometimes stuff apparently randomly gets through, but even so. I wonder if they've got some kind of strange partial block, since I only imported comments, not journal entries.
TL;DR version: The importer works a bit different than the crossposter and due to people (maybe) using it a bit lesser (as a part of the people who import their journal contents here does that only once and then stays here), it's got a slightly better probability to make it through LJ's protection mechanisms (via just fetching a gap of a non-blocked IP address).
You've probably seen it, but DW support has now made a long post on it. TLDR: LJ are blacklisting all DW IP addresses because of some users who are trying to cross-post with incorrect LJ passwords, triggering their "attempted hacking" detection. Previously they had whitelisted DW's IP addresses to avoid this problem (since there are so many DW/LJ cross-posters) but LJ are nowdenying they ever did this, saying they can't do it again and are ignoring DW support contacts.
The technical explanation, to me, doesn't feel like a thought I didn't have before myself, if I think deeper about it... Well, as I see it, there's nothing else that one can do than just keeping one's own passwords always correct for crossposting and then trying it from time to time again (maybe use a private test post to check if it works again).
But the official word on that issue at least is something that one can orientate by. Even if the result is crappy.
Same old, same old then. Though perhaps with less chance of it actually getting resolved this time around.
There are a couple of people reading on LJ who I wouldn't want to lose touch with but... well, most people are here now. There's also an active community I participate in, but that's a different kettle of fish anyway.
Oh well. I assume it will be back eventually. If not, I suspect that may be the final divorce between this account and LJ. There's only a couple of people who still actively follow me over there.
(no subject)
Date: 2022-01-29 03:50 pm (UTC)It's a problem that seems to be on since around 24th/25th of January. (I could still make a post that crossposted on January 24th, but others seemed to already report failures on that date, so that's why I add 25th as a date when it began to work no more again.)
Worse than last time, this time simultaneously importing content from Livejournal doesn't work either! Been pondering for days how to compensate this state of things... Which of the two things is the one to get fixed quicker. So I can continue to post as I like to.
Failures in importing content from Livejournal had popped up months ago already before and finding a technical solution to that took weeks, more than it usually took to find a new knack to make the crossposter get through LJ's spam protection mechanisms.
(no subject)
Date: 2022-01-29 04:06 pm (UTC)What surprises me is that I've not been having crosspost failure notifications.
(no subject)
Date: 2022-01-29 04:34 pm (UTC)As far as I've taken a look into LJ's past login sessions, it seems like the crossposter doesn't even make it to enter LJ as it's not listed there since said dates. Before, you see it listed as "Dreamwidth Studios XPoster".
The import feature, in contrast, seems to make the login as it appears as "Dreamwidth Studios Content Importer" in the list. Only it seemingly isn't able to do anything or perform the action it has the command to do.
(no subject)
Date: 2022-01-30 11:36 am (UTC)(no subject)
Date: 2022-01-30 12:59 pm (UTC)On the starting page of the support area, they've been listing the issue with crossposting possibly failing at times for long now, so it's not like a completely new problem and not like it can be brought to a halt. It's going to happen again from time to time (e. g. if Livejournal changed something in its code again).
(no subject)
Date: 2022-01-30 01:55 pm (UTC)(no subject)
Date: 2022-01-30 01:53 pm (UTC)(no subject)
Date: 2022-01-30 04:58 pm (UTC)Edit: Tried it myself now and although the queue gives out errors during the course of the process, somehow the importer makes it all the way to the end, completing every step.
So that makes entries and comments basically can be imported from LJ to DW.
I tried vice versa - crossposting directly from here to LJ -, this still seems to be dead, not working. Tested it with a short private entry, and - no, you don't get a crosspost link underneath your entry here.
So that lane is still closed.
But somehow something seems to move behind the scenes, you can say...
(no subject)
Date: 2022-01-31 04:56 pm (UTC)(no subject)
Date: 2022-01-31 05:38 pm (UTC)TL;DR version: The importer works a bit different than the crossposter and due to people (maybe) using it a bit lesser (as a part of the people who import their journal contents here does that only once and then stays here), it's got a slightly better probability to make it through LJ's protection mechanisms (via just fetching a gap of a non-blocked IP address).
(no subject)
Date: 2022-01-31 01:33 am (UTC)TLDR: LJ are blacklisting all DW IP addresses because of some users who are trying to cross-post with incorrect LJ passwords, triggering their "attempted hacking" detection. Previously they had whitelisted DW's IP addresses to avoid this problem (since there are so many DW/LJ cross-posters) but LJ are nowdenying they ever did this, saying they can't do it again and are ignoring DW support contacts.
(no subject)
Date: 2022-01-31 01:52 am (UTC)The technical explanation, to me, doesn't feel like a thought I didn't have before myself, if I think deeper about it...
Well, as I see it, there's nothing else that one can do than just keeping one's own passwords always correct for crossposting and then trying it from time to time again (maybe use a private test post to check if it works again).
But the official word on that issue at least is something that one can orientate by. Even if the result is crappy.
(no subject)
Date: 2022-01-31 04:59 pm (UTC)There are a couple of people reading on LJ who I wouldn't want to lose touch with but... well, most people are here now. There's also an active community I participate in, but that's a different kettle of fish anyway.
(no subject)
Date: 2022-01-29 03:51 pm (UTC)(no subject)
Date: 2022-01-29 04:07 pm (UTC)(no subject)
Date: 2022-01-29 04:53 pm (UTC)(no subject)
Date: 2022-01-30 11:37 am (UTC)(no subject)
Date: 2022-01-30 07:23 am (UTC)(no subject)
Date: 2022-01-30 11:37 am (UTC)