Permit (but don't force) lj-cuts on talkread.bml.
Short, concise description of the idea
This suggestion is like avva's, but such that &ljcut=1 would show the entry "cut" (i.e., as it appears on lastn/friends/day pages).
Full description of the idea
If you've read all the comments to avva's suggestion, then there is little new in this suggestion; I'm just posting it because things brought up in comments don't qualify for the polls.
I suggest that we keep everything exactly the way it is now, except that if a talkread.bml (Read Comments) page is passed the parameter &ljcut=1 (which would only happen if someone explicitly linked to it), then the entry would appear "cut" (i.e., as it it appears on lastn/friends/day pages). A few additional possibilities to go along with this are discussed in the section on implementation ideas.
An ordered list of benefits
Most of the benefits are discussed in avva's suggestion.
The benefit of this way over the other way is that this is more optional and backward-compatible; no existing behavior is modified. (Rather, a new behavior is created.)
An ordered list of problems/issues involved
People might get annoyed by links to "cut" entries. It's worth noting, though, that LJ would never produce these links itself (except possibly as an option; see below); the issue is that fellow users might link to "cut" entries, and this could be annoying.
An organized list, or a few short paragraphs detailing suggestions for implementation
avva said implementation would be easy; who am I to argue?
If I use the green arrows to navigate from entry to entry, &ljcut=1 could be preserved (even if I go through entries without lj-cuts anyway).
There could be a &nc=#-like option to include it automatically (purposeless, I know, from lastn/friends/day views - where I just saw the cut entry - but maybe useful from the month view).