Well, this is an interesting DW/LJ HTML discovery!

[thewayne]

Maybe this is documented and I didn't know it, but it's a revelation to me!

I just posted my latest Ukraine war info dump. I write it up, insert the cut tags, do a select all/copy, post it, open an LJ window, paste, post. Except I screwed up the cut tags on LJ and had to do some fussing to get it to post right.

Came back to check the DW side, and it was correctly cut. Just to make sure, I opened it in Edit.

The cut tags in my Dreamwidth post said LJ-CUT!

*POOF*

Mind blown!

Definitely going to have to remember this and experiment with it further! This is either an undocumented feature, meaning it could go away at any time in the future, or some legacy code deeply buried in the system that someone didn't notice.

Comments

[motodraconis]

I use lj cut on DW!

[elayna]

We've always been able to use the LJ instructions in DW, I kept using them for years before I got around to looking up the DW equivalents.

[disneydream06]

I didn't realize there were DW equivalents. :o

[bibliofile]

What Dreamwidth-specific markup/HTML tags can I use? (FAQ 82)

[thewayne]

I know the CUT code, I was surprised that the LJ-CUT code worked.  But as others have pointed out, supporting it makes sense to make imported pages work properly.

[disneydream06]

Thank you for that link.

[frith]

Legacy LJ-clone HTML. If it was removed, there would be a lot of imported LJ posts from way back when that would have HTML errors. Like when YouTube gave me blank areas where I used to have embedded videos. (Now I use an Img Scr code to use the YT's preview image as a link target. Works without Javascript.)

[silveradept]

Entirely intentional on the DW developers' part. When the crossposter was working, it worked both ways, so that people could post primarily to LJ and mirror to DW. Plus, imported entries, as was mentioned above, want to be seamless and working instead of clunky and requiring years of corrections. And, y'know, lowering the cognitive burden on someone new to the site by not requiring them to learn an entire new syntax until they want to take advantage of summer of the extended features that DW has on those things.

So that'll probably always be there as a legacy thing. The parser understands it, and it's no great burden to maintain that compatibility, as far as I know.

[thewayne]

I was unaware of a reverse cross-post.  I moved from LJ to DW and never knew of or was interested in such a thing.  But it does make sense.

[silveradept]

I'm probably wrong about it, but I'm pretty sure there was a way to set it up so that DW was the mirror instead of LJ.

[thewayne]

Not important to me.  When I moved to DW, DW became my primary.