dw_suggestions | Entries tagged with workflow: commenting

Title:
Comment titles shouldn't stick when switching which comment you respond to

Area:
Commenting

Summary:
When I change which comment on an entry I'm replying to, it shouldn't keep "Re:[original.comment.title]" as its title.

Description:
There is an entry. There are comments on the entry. Comment A has no title. Comment B is titled "XYZ".

I click 'reply' to Comment B. My reply automatically gets the title "Re: XYZ". This is expected and appropriate behaviour.

I end up not submitting the reply to Comment B, and decide that instead I will respond instead to Comment A. I click 'reply' to Comment A. My reply, now under Comment A, keeps the title "Re: XYZ", even though the comment it's responding to has no title. This is unexpected and I think non-ideal behaviour.

When I initially submitted this as a bug report, foxfirefey pointed out that a fix should "carefully note to ONLY replace the title if it was the same as the automatic one, so as to not wipe out a user entered title."

(I am not completely sure if this is true; if the user-entered comment text "sticks" when you switch to commenting on a new entry, a user-entered title probably should too; but if switching which comment you reply to clears the text field, the title should probably be cleared too. I don't remember how this works.)

Poll #5603 Comment titles shouldn't stick when switching which comment you respond to

Open to: Registered Users, detailed results viewable to: All, participants: 52

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
34 (65.4%)

Should be implemented with changes. (please comment)
2 (3.8%)

Shouldn't be implemented.
2 (3.8%)

(I have no opinion)
14 (26.9%)

(Other: please comment)
0 (0.0%)

ratcreature

Title:
edited comment notifications in the DW inbox

Area:
comments

Summary:
When a comment is edited the original notification in the inbox changes and also shows the edited version, but you still get a new notification with the edited comment. So basically you get duplicates with no value. I think that should be changed, so that only one notification with the edited comment is there.

Description:
With the email version of the notifications it makes sense that you get two, because one shows the old comment, the second the edited one, so you can see the edit. But in the DW inbox the notification reflects the current state of the comment (or entry), so the first notification itself is edited and changed to say "edited comment by" exactly the same as the second one.

So if the first is already updated the second is superfluous clutter. I don't think there would be any drawbacks to not having two of the same.

Poll #5578 edited comment notifications in the DW inbox

Open to: Registered Users, detailed results viewable to: All, participants: 57

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
22 (38.6%)

Should be implemented with changes. (please comment)
6 (10.5%)

Shouldn't be implemented.
6 (10.5%)

(I have no opinion)
22 (38.6%)

(Other: please comment)
1 (1.8%)

foxfirefey

Title:
Inline comment editing

Area:
commenting

Summary:
We have quick comments; we should also have quick edits!

Description:
Implement inline comment editing, without a page load. If someone isn't using JS or doesn't have quick commenting enabled, then fall back to the normal behavior. I think this would improve a very popular paid feature.

Poll #5521 Inline comment editing

Open to: Registered Users, detailed results viewable to: All, participants: 65

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
57 (87.7%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
8 (12.3%)

(Other: please comment)
0 (0.0%)

thorfinn

Title:
Claiming an Anonymous Comment

Area:
Comments

Summary:
Quite often someone will make a comment, then realise they've anonymously commented, and then have to follow up with a logged comment saying "oops, the above comment was me."

It would be nice to have a mechanism of being able to actually claim that anonymous comment with a login for at least a period of a few minutes of making it.

Description:
The annoyance:

Accidentally posting an anonymous comment leaves the wrong trail, and it would be nice to fix the the anonymous comment, instead of having to make another comment after logging in.

Thus the requirement:

Provide a mechanism for anonymous comments to be claimed, within a certain limited time period of posting, as non-anonymous by the person that originally posted the anonymous comment.

Possible Implementation Design:

1. When an anonymous comment is made, send a non-forgeable (i.e. contains a high randomness component, or is cryptographically secure) "made anonymous comment XXX id" cookie which expires within some time period (5 mins? 10 mins? 1 hour? 1 day?) Personally I think one hour is reasonable. If using a random component cookie this will probably require a server side table to store that cookie in for crossmatching. Those table entries can be expired in the same timeframe.
2. If you're viewing a page where you have the right cookie for that anonymous comment, provide a "claim this comment" option that allows you to login, which should look much like the posting a comment login stuff.
3. Upon use of that option, convert the anonymous comment to a proper comment owned by that login.

Potential Drawback:

A shared rapidly and frequently changing database table plus a regular purge job for old cookie entries would be required. If that is a performance issue, the table could made to go away by using a cryptographically secure cookie rather than a random+stored cookie.

Poll #5127 Claiming an Anonymous Comment

Open to: Registered Users, detailed results viewable to: All, participants: 59

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
34 (57.6%)

Should be implemented with changes. (please comment)
8 (13.6%)

Shouldn't be implemented.
6 (10.2%)

(I have no opinion)
11 (18.6%)

(Other: please comment)
0 (0.0%)

telophase

Title:
Radio button auto-select when logging in while making a comment

Area:
Comment form From: tag

Summary:
Have the radio button next to "OpenID" or "Dreamwidth account" on the comment form auto-select if you enter text in the text boxes associated with that button.

Description:
I came across this when trying to post a reply to a comment in my journal via my iPhone - I wasn't logged in, so I typed in my account name and password, but forgot to click the radio button next to "Dreamwidth account" (which wasn't selected, even though I have anon and openID commenting turned off), sending me to the Comment Not Posted form (luckily my comment was persistent so I didn't have to re-type it: thank you!).

It occurred to me that if the radio button auto-selected when you filled out the account/pw fields, that sort of annoyance would be avoided. At the very least, have it auto-selected if the Anonymous and OpenID commenting is turned off.

I'm not sure what drawbacks there would be: certainly if someone typed in both the OpenID field and then the DW account field, the radio button for the most recent one used would be selected, and there would be no way to un-select it - you'd have to pick one of the other options to change it, but if you were posting a comment, you'd want one of the options selected anyway.

Going to the Comment Not Posted form and having to re-enter your credentials is more of a hassle on a smartphone or other small mobile device than on a full-size computer, but still an annoyance either way.

Poll #5116 Radio button auto-select when logging in while making a comment

Open to: Registered Users, detailed results viewable to: All, participants: 48

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
43 (89.6%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (10.4%)

(Other: please comment)
0 (0.0%)

tim

Title:
Improve UI for commenting when not logged in

Area:
entries

Summary:
Users who are not familiar with Dreamwidth may not realize they can post comments on public posts in journals that have anonymous commenting disabled but OpenID enabled. I suggest improving the text that's part of the comment area.

Description:
I have anonymous commenting disabled on my journal, but have OpenID commenting enabled. If someone isn't familiar with DW and follows a link to one of my public posts, and they want to comment, what they see is a grayed-out "anonymous" radio button option and a grayed-out "OpenID" radio button, with the text "OpenID commenting on this post is limited. Please sign in here." To someone who is reading quickly, I don't think that text conveys the message "You can post a comment here using credentials you already have." Indeed, I had someone think that they couldn't comment on my blog without buying a DW account.

I suggest changing the text that appears when non-logged-in users view the comment areas on public entries to say "You can comment here without creating a Dreamwidth account, using OpenID", with a link to an explanation of OpenID. I'd welcome any comments as to how to make that text even more user-friendly -- I just know it's not good enough as is.

Poll #5110 Improve UI for commenting when not logged in

Open to: Registered Users, detailed results viewable to: All, participants: 38

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
28 (73.7%)

Should be implemented with changes. (please comment)
8 (21.1%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (5.3%)

(Other: please comment)
0 (0.0%)

foxfirefey

Title:
Remove the black border from quick reply

Area:
styles, site scheme

Summary:
The more I see the black border around ALL the quick replies (aka inline commenting), the more and more I dislike it. We should get rid of it.

Description:
As mentioned above, taking away the black border that's inline styled on the quick reply box. The quick reply box has an ID that CSS can target, so individual styles should be able to do what they want, without having to override a hard-coded in color. The hard-coded in color is pointless on most light-on-dark layouts, anyway, and might look unsynchronized with other layouts' color schemes.

I'm making this a suggestion just in case anybody can come up with a reason to keep it, because I sure can't.

Poll #4952 Remove the black border from quick reply

Open to: Registered Users, detailed results viewable to: All, participants: 55

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
26 (47.3%)

Should be implemented with changes. (please comment)
4 (7.3%)

Shouldn't be implemented.
3 (5.5%)

(I have no opinion)
20 (36.4%)

(Other: please comment)
2 (3.6%)

strangesequitur

Title:
Show Selected Icon on Comment Preview Pages

Area:
comments, entries

Summary:
Users should be able to see the icon they have selected on the Comment Preview page, and be able switch to a different icon at this stage, in much the same way that they can edit the text of a comment before submitting it.

Description:
When choosing an icon to accompany a comment to an entry, you're generally flying somewhat blind. Even with robust, descriptive Icon Tags in place, choosing an incorrect icon is a common slip-up.

The Comment Preview feature -- which is delightful and much improved from the code it spawned from -- includes previews of the comment title and text, but no icon preview. It also allows for the editing of these fields, but no option to change the selected icon. (You have to back out to the previous page to change the icon, possibly losing edits made at the Preview stage, etc. It's inelegant.)

I would very much like a visual preview of the icon I've chosen, and the ability to easily change my selection, for those rare times when my sleepy brain and dull-witted hamfingers have chosen something wildly inappropriate.

Barring a visual preview, even just the text of the icon description would be better than nothing -- one final warning in case you weren't paying attention to, say, what Random Icon was chosen, for instance.

Essentially, I want the same dynamic icon preview feature we have on the Update page. I can see how the server load and processing power might be prohibitive, though, and I suspect that if it were as easy as all that it would have been done already.

Poll #4951 Show Selected Icon on Comment Preview Pages

Open to: Registered Users, detailed results viewable to: All, participants: 76

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
72 (94.7%)

Should be implemented with changes. (please comment)
1 (1.3%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
3 (3.9%)

(Other: please comment)
0 (0.0%)

ratcreature

Title:
spellcheck should recognize the language

Area:
entries, comments

Summary:
The site's spellcheck should be smarter. It should make a best guess of what language it likely is from the text entered, and apply the right kind of dictionary.

Description:
I know some browsers have a spellcheck of their own, but I always use the site's spellchecker. Only it is not as smart as a spellcheck should be. Usually I type English comments, and that's mostly fine (though the dictionary could use some upgrade too), but today I hit spellcheck as I always do automatically, but happened to have typed a German comment.

The output was a ridiculous, annoying wall of red. But computers these days are not so bad at recognizing common languages (at least if I let that google translator guess on a language bit rather than choosing, it seems to guess sensibly and the translations actually have gotten less ridiculous than a few years ago too), so why couldn't the DW spellchecker see that the comment clearly wasn't English, recognize the language, and pick the correct dictionary automatically?

I don't know how much effort it would be technically to get text based language recognition, and I wouldn't want the dictionary be chosen dumbly based on location settings or language settings in the browser, because then I might get the red wall for English comments and that would be worse. But a spellchecker would be much more convenient if it was smarter and did things it is supposed to do automatically.

I don't see any downsides, because if the language recognition should fail for some languages, you are not worse of than now, as I assume then it would just default to English as the site language.

Poll #4880 spellcheck should recognize the language

Open to: Registered Users, detailed results viewable to: All, participants: 54

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
24 (44.4%)

Should be implemented with changes. (please comment)
4 (7.4%)

Shouldn't be implemented.
4 (7.4%)

(I have no opinion)
22 (40.7%)

(Other: please comment)
0 (0.0%)

denise

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.

Poll #4520 "Promote" comment to top-level entry

Open to: Registered Users, detailed results viewable to: All, participants: 94

View Respondents

This suggestion:

View Answers

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%)

helens78

Title:
Disable top-level comments (and only top-level comments) on a post

Area:
comments

Summary:
When a journal owner or community mod wants to close down top-level comments to a post, but allow discussion to continue on already-started threads, they should have the ability to disable top-level comments only. (A possible addition: allow journal owners to disable top-level comments to a post after a certain length of time.)

Description:
Many discussions are started in journals but end up growing more broad than the journal owner might prefer; a solution that would allow a journal owner to disable top-level comments, but allow current discussion threads to continue unchanged, would give people the ability to essentially retire a topic without shutting down all communication between discussion members in ongoing threads.

Current workarounds to achieve functionality include screening all comments to a post (in which case individual threads must still be checked and unscreened one response at a time), or freezing or deleting all top-level comments (in which case the journal owner is still doing a great deal of work in a discussion they're no longer interested in, plus people may respond to those top-level comments before the journal owner has a chance to delete or freeze them).

This could also be useful for communities: writing challenge communities where a top-level comment is a prompt, and other members can reply to that comment to fulfill that prompt, are common, and many of them would appreciate an option to prevent members from posting additional prompts while still allowing members to fulfill already-standing prompts.

It would be a nice option for auction communities, such as auctions set up to benefit time-sensitive charities -- disabling top-level comments would allow community mods to prevent members from starting auctions after the official new auction close date, while still allowing members to bid on already-existing offers.

Possible drawback: people can still reply to previous replies in lieu of having the ability to reply at a top-comment level -- in other words, it isn't troll-proof or accident-proof, and some people may be confused by the fact that they can't comment at a top level but can still reply to posts. (For journals/communities where precisely this behavior is desirable, though, I think it would make perfect sense to members under normal use case conditions -- in other words, it would be beneficial to people who are <em>not</em> trying to break the system.)

Poll #4515 Disable top-level comments (and only top-level comments) on a post

Open to: Registered Users, detailed results viewable to: All, participants: 63

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
40 (63.5%)

Should be implemented with changes. (please comment)
3 (4.8%)

Shouldn't be implemented.
9 (14.3%)

(I have no opinion)
11 (17.5%)

(Other: please comment)
0 (0.0%)

stasha2g

Title:
Option to use no icon even when default icon is set

Area:
icons, entries, comments

Summary:
One should have the ability to choose "No icon" even when default icon has been set.

Description:
Sometimes no icon, including the default, is appropriate to the situation. And sometimes the situation itself (say, a long line of +1 comments) is better served by having no icons. The icon selector should have a "none" option.

Poll #4513 Option to use no icon even when default icon is set

Open to: Registered Users, detailed results viewable to: All, participants: 82

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
66 (80.5%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
4 (4.9%)

(I have no opinion)
12 (14.6%)

(Other: please comment)
0 (0.0%)

cesy

Title:
Split up recent comments page to allow more comments

Area:
comments

Summary:
Split the recent comments page into separate pages for comments received and comments posted.

Description:
http://www.dreamwidth.org/tools/recent_comments has a section for comments received and a section for comments posted. It has handy links to skip from one to the other. It defaults to 25 comments, and allows you to show up to 150 comments of either type.

However, if you pick 150 comments, you get both 150 comments received and 150 comments posted. This is a big page to load when you only wanted one or the other, so bad for dial-up, mobiles and the poor servers.

I'd suggest splitting this into two pages that you can toggle between, since most people will use the links rather than scrolling down 25 comments anyway. This will make the page faster to load, only give you the information you actually want, and open the door to the possibility of increasing the limit of 150.

Poll #4290 Split up recent comments page to allow more comments

Open to: Registered Users, detailed results viewable to: All, participants: 35

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
27 (77.1%)

Should be implemented with changes. (please comment)
1 (2.9%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
7 (20.0%)

(Other: please comment)
0 (0.0%)

feathertail

Title:
Make option to mark comment as spam more prominent

Area:
spam, comments

Summary:
In order to mark a comment as spam, you first have to select "Delete comment" and then tag the comment as spam. This can lead to people looking for a "report spam" option that doesn't exist outside of that dialog. Let's change that.

Description:
I got my first spam comment today. Yay me! Anyway, I looked for the "report comment as spam" button but there wasn't one. What the heck?

So I Googled "dreamwidth spam" and got this: http://wiki.dwscoalition.org/notes/Handling_Spam_Reports

Which was all about the antispam team. Where were the instructions for how an average user could report something to them? I typed "spam" into the wiki's search box; still no answers.

Finally I clicked on "Delete comment" and it had a checkbox, for if I wanted to report it as spam or not. There it was!

Maybe we should make "Report comment as spam" a top-level option, like in the notification email. (Although with four or five other top-level options, depending on whether or not you have to click to unscreen the comment, it _is_ starting to get cluttered a bit.)

Poll #4242 Make option to mark comment as spam more prominent

Open to: Registered Users, detailed results viewable to: All, participants: 29

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
12 (41.4%)

Should be implemented with changes. (please comment)
2 (6.9%)

Shouldn't be implemented.
7 (24.1%)

(I have no opinion)
8 (27.6%)

(Other: please comment)
0 (0.0%)

stormy

Title:
Delete All Entries/Comments Upon Journal Deletion

Area:
Accounts, Entries

Summary:
Livejournal now features a ( delete all comments and posts ) option when a user chooses to delete their journal from Account Settings. It would be nice to see this option implemented on Dreamwidth.

Description:
On Dreamwidth, when users select to delete a non-community account, they should be given the option to delete all comments and community posts site-wide. Upon selection, the entries and comments are immediately removed from view, but I assume they're not fully removed from the database until the account is purged to prevent abuse in hacking/account theft incidences.

This feature has recently been implemented on Livejournal, and it's beneficial for several reasons.

1) It clears the servers of unneeded data once the journal is purged.

2) For privacy reasons, it gives users another option to effortlessly delete their content without affecting the content of another user, and without having to track down every entry and comment across the entirety of the site.

Poll #4241 Delete All Entries/Comments Upon Journal Deletion

Open to: Registered Users, detailed results viewable to: All, participants: 71

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
20 (28.2%)

Should be implemented with changes. (please comment)
6 (8.5%)

Shouldn't be implemented.
34 (47.9%)

(I have no opinion)
10 (14.1%)

(Other: please comment)
1 (1.4%)

Updates

Expressed concerns:

It presents the option to someone who otherwise might not be looking for it.
It interferes with conversation across the site, leaving conversations disjointed.

Not implemented :

[Suggestion] The ability to search for every post you have made to a community without entering the community directly - something similar to the Recent Comments/Latest Posted Comments page.
[Suggestion][Suggested by Others] The ability to mass Orphan Comments/Entries posted outside of your own journals/communities, which detaches your identity to the content. I'm not sure how this would work, but someone else would have to suggest this.
[Suggestion][Suggested by Others] If a mass delete button were to be put in place, then textbox or checkbox capability for excluding certain journals and communities from the deletion of comments/entries.

On http://www.dreamwidth.org/editjournal :

[Suggestion] A delete button with confirmation for [Delete this Entry].
[Suggestion] Perhaps the option to mass delete would be located on this page, separate from the Delete Journal confirmation page to avoid clicking the option without fully reading over it and considering its consequences.

On http://www.dreamwidth.org/tools/recent_comments :

[Bug] A clearer visual of comments that are already deleted with grayed out text, or the [delete] changed to [deleted]. (Found on Bugzilla)
[Suggestion] The ability to go back through all comments ever posted (at present, the max is your 150 most recent comments). Or an ability to hide or separate deleted comments so that the list will keep expanding. (Found on Bugzilla)

Am I missing anything?

northern

Title:
"Like" button.

Area:
entries

Summary:
You could offer something similar to Facebook's "like" button on entries. It would be useful, and might make people feel better.

Description:
I feel kind of embarrassed, asking for this, but several times a day I find myself wanting this feature. I'm scrolling through my reading page, and I see something funny, or noteworthy, but I don't want to make the effort of writing an actual comment. If I did, it would only contain a "yay!" or a "good for you" or an "ahahahah", so I don't see the point.

Hence, a "like" button. It wouldn't have to be a rating thing, or actually labeled "like", but it would be really useful to me, and hopefully to others. People who don't get many comments might also feel like they have more support and attention from their subscribers with something like that. For a lot of people, a comment to their journal is a bright spot of their day.

A con for this function that I can see is that actual comments might drop in frequency. I don't think they would drop much, though. Hmm. I don't see any others, except that I imagine it would take a lot of work to make such a feature. Some people might also think that this makes Dreamwidth look too much like Facebook, or that a "like" implies a rating of the person who wrote the entry.

Poll #4087 "Like" button.

Open to: Registered Users, detailed results viewable to: All, participants: 99

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
44 (44.4%)

Should be implemented with changes. (please comment)
13 (13.1%)

Shouldn't be implemented.
36 (36.4%)

(I have no opinion)
6 (6.1%)

(Other: please comment)
0 (0.0%)

feathertail

Title:
Have the "Reply" button take you to the reply form

Area:
commenting

Summary:
If you click on "Reply" from the Recent Entries view, it just brings up the entry and you have to scroll down to get to the comments form. That's not how it should work.

Description:
Think about this for a second. In the Recent Entries view, each entry has three links: A permalink to the entry, a link to the comments, and a link to reply.

The permalink takes you to the entry. The comments link takes you to the comments. Where would you suppose the reply link would take you?

Well, it doesn't take you to the reply form! Instead, it takes you to that entry with ?mode=reply, and you have to scroll down past the entry you already read in order to comment. Wouldn't it be better -- and less confusing to non-Dreamwidth natives -- if it took you straight to the comments form?

Poll #3933 Have the "Reply" button take you to the reply form

Open to: Registered Users, detailed results viewable to: All, participants: 57

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
42 (73.7%)

Should be implemented with changes. (please comment)
4 (7.0%)

Shouldn't be implemented.
5 (8.8%)

(I have no opinion)
6 (10.5%)

(Other: please comment)
0 (0.0%)

lightgetsin

Title:
Option to view top level comments only

Area:
comments, entries, accessibility

Summary:
A way to view comments only at the top level, with all threads temporarily collapsed.

Description:
Why it would be useful: anywhere you want to browse threads without having to scroll and scroll past endless collapsed comments. Useful in love memes, auctions, kinkmemes, lots of places. Also, it would be a great accessibility enhancement.

How to do it: The most obvious way would just be to have a link available on every entry to view only top level comments. From that view, you have the option of expanding any thread to view it, preferably via ajax magic.

It would probably also be useful to give users more control. I see two options here:

1. Give users a setting in their viewing options "show me only top level comments by default." Though of course you could turn it off on individual entries.

2. Make it style-specific -- if you're using a style that views top level as default (and I bet someone will make an accessibility style that does) -- then it's controlled by style=mine.

Other questions:

1. When expanding a thread from the top level comment, should the whole thread expand, or should it just appear as it normally would with comment collapsing? I tend to think expand the whole thing, because double-clicking for that would be annoying.

2. Should the "show me only top level comments" link be part of the links at the end of every entry (track, reply, comments, etc.) or should it be only inside once you've clicked through to view comments? A question of clutter versus possible annoyance.

Poll #3834 Option to view top level comments only

Open to: Registered Users, detailed results viewable to: All, participants: 44

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
28 (63.6%)

Should be implemented with changes. (please comment)
2 (4.5%)

Shouldn't be implemented.
3 (6.8%)

(I have no opinion)
10 (22.7%)

(Other: please comment)
1 (2.3%)

denise

[This suggestion was made an OpenID user, and the posting process failed because OpenID accounts can't post to communities; the suggestion was good enough that I just sent it straight to Bugzilla, but I wanted to record it here for posterity and so that my numbers can match up.]

Summary:

If HTML links will be disabled, can comment previews show this?

Description:

Comments by open-ID or anonymous users do not permit HTML links or images (or maybe that's just an option on the journals I've commented on). Can the preview option be changed to detect open-ID or anonymous comments and show them as they will be rendered with the links disabled?

zvi

Title:
Timestamp collapsed comments on journal styled pages

Area:
styles, entry pages, comments

Summary:
When a comment is collapsed (the text of the comment is not shown, merely a link to expand or open the comment on a second page) in a system style, the metadata available about the comment includes the date and time it was made.

This information should also be displayed when an entry page is in a journal style.

Description:
If the timestamp of a collapsed comment is visible, it is easier to guess whether or not one has read it before. You can keep track of the time before which you have or have not read a comment, and only open the ones that are new to you.

Poll #3481 Timestamp collapsed comments on journal styled pages

Open to: Registered Users, detailed results viewable to: All, participants: 44

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
38 (86.4%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (13.6%)

(Other: please comment)
0 (0.0%)

Dreamwidth Suggestions

Comment titles shouldn't stick when switching which comment you respond to

edited comment notifications in the DW inbox

Inline comment editing

Claiming an Anonymous Comment

Radio button auto-select when logging in while making a comment

Improve UI for commenting when not logged in

Remove the black border from quick reply

Show Selected Icon on Comment Preview Pages

spellcheck should recognize the language

"Promote" comment to top-level entry

Disable top-level comments (and only top-level comments) on a post

Option to use no icon even when default icon is set

Split up recent comments page to allow more comments

Make option to mark comment as spam more prominent

Delete All Entries/Comments Upon Journal Deletion

Updates

"Like" button.

Have the "Reply" button take you to the reply form

Option to view top level comments only

Previews for non-dreamwidth commenters

Timestamp collapsed comments on journal styled pages

Profile

Most Popular Tags

December 2018

Page Summary

Active Entries

Style Credit

Expand Cut Tags

Syndicate