![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
denise) wrote in ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
dw_suggestions2010-09-22 06:23 am
"Promote" comment to top-level entry
Title:
"Promote" comment to top-level entry
Area:
commenting, posting, centralizing all your stuff
Summary:
Since DW has extended comment length, I often find myself writing a mini-novella in comments (whether fiction or just me running off at the keyboard again). When the comments are in someone else's journal, I will frequently c&p that comment into a top-level entry in my own journal, so as to have all of my stuff together in one place. It would be nice to be able to do that automatically.
Description:
(I feel the need to say HEAR ME OUT BEFORE YOU MAKE A DECISION, based on goings-on Elsewhere. Heh.)
What I am envisioning for this feature is a checkbox on a comment, probably right after the "Check spelling and preview" checkbox: "Repost my comment to my journal as a new entry". Checking it would bring you to an update page, with the text of the comment pre-filled in the update box. You'd then be able to review the entry-to-be, in order to remove anything that doesn't make sense out of context, add a <cut> tag if necessary, choose your security level option, add metadata on the entry like current mood/music/tags/etc, and finally post the entry.
The commenter would be able to review the text of the entry-to-be before posting it, and there would be no 'official' indicator (ie, no "This comment reposted from the entry "Entry Title" made by username" or whatever). Because of that, there'd be fundamentally no difference than copying and pasting from the comment box, so I wouldn't see the need to remove the checkbox on locked entries or allow people to block others from using it in their journal. It would just be a shortcut for people who write extensive comments that wind up being worthy of a top-level entry of their own.
This suggestion:
Should be implemented as-is.
56 (59.6%)
Should be implemented with changes. (please comment)
7 (7.4%)
Shouldn't be implemented.
10 (10.6%)
(I have no opinion)
20 (21.3%)
(Other: please comment)
1 (1.1%)
no subject