![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
truncated crossposts
Title:
truncated crossposts
Area:
crossposting
Summary:
Add option to truncate posts when crossposted, so that entire post is not reproduced elsewhere.
Description:
Like many folks, I crosspost so non-DW people can see the entry on their flist, but I don't care for having the entirety of every post kept in multiple places. I'd much rather provide some kind of summary/entry section as teaser, and require that reading the rest means coming back to DW (which is also the only place I have comments turned on, as well).
Perhaps default be the first X number of characters, or stop at the cut (with cut being link to the DW post?). Which gets used would be dependent on which is programmatically easier. ETA: to clarify, this would be optional per post. You could crosspost as normal, with the entire thing going elsewhere, and then on the next post you could opt to truncate. [See comments from some other suggestions on how truncating might work.]
I'd be happy either way, so long as the objective of "only a little posted elsewhere, and must come to main (DW) journal to read the rest" is achieved.
This suggestion:
Should be implemented as-is.
36 (48.0%)
Should be implemented with changes. (please comment)
16 (21.3%)
Shouldn't be implemented.
11 (14.7%)
(I have no opinion)
12 (16.0%)
(Other: please comment)
0 (0.0%)
no subject
no subject
no subject
no subject
no subject
You can't do that with a feed -- the summary option would apply to every single post, without variation, and that's not what I'm asking for, here.
no subject
no subject
Instead of using a specific character limit or the first <cut>, I'd like to have the entry truncated at a specific tag, like <trunc>, which would create an anchor in the dw entry, like <a name="trunc"></a>, and a link to the anchor from the crossposted entry.
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
no subject
Another +1 to add to this. :)
no subject
no subject
no subject
no subject
If you don't want to store posts on other websites, you can choose not to crosspost on an individual basis, and you can post at the other website to alert them that there's an entry at DW, but I really don't think that we should encourage this behavior by automating it.
no subject
I also think new features need a lot of justification. Where exactly would it appear in the UI? How long would it take for somebody new to grasp it? What use does it have for someone who's not cross-posting to anyplace?
Maybe if you have comments turned off on the remote service, you could flip a switch somewhere in the crossposting section that says that "cut" tags link people back to the DW entry. If I were to implement this, that's how I'd do it. I'm not sure it's a good idea though.
no subject
I think that's the best way of implementing it.
no subject
no subject
no subject
One) It's actually a pretty common behavior with RSS feeds, for the feed to show the whole article, but with comments available at the originating website.
Two) I think having a single conversation is a larger benefit for more users than partial posting would be, since there are other methods to achieve partial posting, and it appears that partial posting is an occasional desire, while comment consolidation is something people like to turn on and leave on.
Three) I think that, with LJ-based platforms specifically, there'd be a harm to users and the service, if their friends were following them via RSS feed account at LJ: specifically, on can comment on the RSS entry at the remote LJ platform, but it doesn't trigger any of the usual comment monitoring for the OP, and people really, really, really don't get that.
no subject
no subject
no subject
no subject
I suppose if the post were really really long, then truncate automatically in any crosspost, but otherwise, I just think it would be handy if on any single post, I could choose whether or not the entire post gets sent elsewhere.