Just curious

[vettecat]

When I have something long to say, I tend to put a cut-tag after a very brief intro, so as not to clutter everyone's friends page. But I'm beginning to wonder whether I'm cutting them too short, and people aren't seeing those posts when they scan down the page. So, I was wondering...

[Poll #923012]

Comments

[joecoustic.livejournal.com]

I was going to mention that the second choice left out the option I was looking for but I just realized that I misread it. What I read was "when can you use a cut tag" not "when must you use a cut tag". Now it makes sense that "after one line" wasn't there :).

Either way, I ascribe to the - it's your journal and your rules - idea, but I do understand the issue.

[vettecat.livejournal.com]

Glad it made sense in the end!

[gnomi.livejournal.com]

Length isn't always my criterion for whether or not to cut. Some long posts I leave uncut, if I think they're sufficiently important or time-sensitive (as I know a number of folks who save cut-tagged posts for later reading).

The last question I also had a problem choosing an answer for. The main reason I see to cut-tag meme results (especially the generated-quiz ones) is that they frequently go wider than the average friends page and break formatting across the whole friends page.

[vettecat.livejournal.com]

I haven't had that problem but I'll try to keep it in mind.

[530nm330hz.livejournal.com]

What Nomi said.

I've cut things after two words if I think they'll only appeal to a small subset of my readership, and I've left long important posts uncut.

And meme posts that include images cause lots of breakage. I often read lj on my wireless pda, and the screen is only 480 pixels wide. If a post includes a wide image, one that will require downloading a lot of pixels, or yet another fetch off to some overloaded server (have you seen the "How well do you know me" quiz thing that's been going around? Nice concept, painfully slow) then it seriously degrades my ability to read lj at all.

[vettecat.livejournal.com]

I hadn't thought about the "reading it on a 1" screen" issue, I'll try to keep it in mind.