melannen: Commander Valentine of Alpha Squad Seven, a red-haired female Nick Fury in space, smoking contemplatively (Default)
[personal profile] melannen2009-07-24 01:56 am

Warning for Bad Markup

Title:
Warning for Bad Markup

Area:
entries

Summary:
When you have bad markup in an entry, DW fails with an error message in the displayed post. Instead, it should warn you about the bad markup before posting, and give you a chance to go back and edit.

Description:
DW clearly has a way to check the markup in a post for basic problems, since it displays some really ugly error text when it happens, and I remember a time on LJ before the error text was there.

The current behavior is to interrup the post at the point where the error occurs, with the message [Error: Irreparable invalid markup ('<foo [...] bar>') in entry. Owner must fix manually. Raw contents below.] followed by the complete raw text of the entry.

I see this message, um, pretty much every time I attempt to make a post with more than a couple bits of mark-up in it. It's ugly, it breaks cut-tags, and with a long and complicated post, it's easy to miss it on preview. We hates it, precious.

It would be really nice if, instead of posting the entry complete with error text and raw code, DW instead gave you some kind of really noticeable warning that there was bad markup (a pop-up, or a big screaming message, or something difficult to miss) and offer to send you back to the entry to fix before posting. (Give the user the option to post anyway, but let them know there will be errors.)

I have no idea how this would work with clients, but even if it only worked from the web form, it would be an amazingly helpful improvement for me.

(And aside from that, some sort of polish to the current behavior would be great. I suggest post the entire entry in raw HTML but behind a cut, with the error message as the cut text. That way at least it wouldn't take over everyone's flists.)

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


This suggestion:

View Answers

Should be implemented as-is.
39 (81.2%)

Should be implemented with changes.
7 (14.6%)

Shouldn't be implemented.
1 (2.1%)

(Other: please comment)
1 (2.1%)

ratcreature: RatCreature's toon avatar (Default)

allow to track only comments made by specific users in a thread

Title:
allow to track only comments made by specific users in a thread

Area:
comment tracking

Summary:
Currently when you track a comment thread you get notified about all new comments made below the one you tracked. In addition to that general tracking I would love an option to be only notified about further comments from specific users who had commented in said thread before.

Description:
Sometimes I'm only interested in comments by certain people in a thread rather than in all comments. A typical example would be comment fic posted as a WIP in many installments, mixed in with feedback comments from other people.

Currently in order to get updates when a new part of such a story is posted in the comment thread, I also get notifications about all feedback. If there was an option to add a username to the comment tracking, that would allow me to get only the author's comments, reducing the notifications I'm not interested in.

For the feature I imagine something like an extra ticky box on the "Manage Message Settings" page you get when you click the tracking symbol. Under the general option "Someone comments under the thread by User X in entry Y" that tracks all comments there would be the option to subscribe to "User X comments under the thread by User X in entry Y" so that you could subscribe only to further comments by that commenter.

Besides for stories posted in comments that option would also be useful for discussions where you sometimes find contributions by certain people more interesting (or controversial) than other comments and want to track you their comments.

A problem or drawback might be that this option allows to keep closer track of specific people in their comments rather than just through their entry updates, so that might cause trouble if users are harrassed or trolled. However I think because this would be tracking only inside a specific entry or comment thread, it isn't really more invasive than the current tracking options.

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


This suggestion:

View Answers

Should be implemented as-is.
21 (77.8%)

Should be implemented with changes.
0 (0.0%)

Shouldn't be implemented.
6 (22.2%)

(Other: please comment)
0 (0.0%)

view=flat

Title:
view=flat

Area:
comment pages

Summary:
Can we get a link to open the comment page into flat view so all the comments are opened? Very useful on the comment heavy posts.

Description:
Right now, we can open comment pages in my style or light style. If we could add flat view, it would make it easier to keep up with epic long comment pages. Right now to do this, we have to open in light style then put the ?view=flat in the address and refresh. A link might save some time. It would be up to the reader to follow where the new comments fit in the overall page but for those who are willing to go there, it would be an easy step.

Regardless if you implement this request, you guys rock. Thanks!

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


This suggestion:

View Answers

Should be implemented as-is.
14 (36.8%)

Should be implemented with changes.
21 (55.3%)

Shouldn't be implemented.
2 (5.3%)

(Other: please comment)
1 (2.6%)

zvi: self-portrait: short, fat, black dyke in bunny slippers (Default)
[personal profile] zvi2009-07-14 01:29 am

Modify disable comments function

Title:
Modify disable comments function

Area:
entries

Summary:
1) Let journal owner see comments on entry where comments are disabled.
2) Provide option for disallowing future comments, while allowing current posts to remain visible.

Description:
People sometimes disable comments on an entry after comments have already been posted to the entry. People sometimes disable comments to their entire journal after people have made comments in it. While this is sometimes an effort to erase the record, more often, it is a signal from the journal owner to their audience that they do not wish any future comments.

1) I propose that the disable comments function, instead of making comments already made 'disappear', allow the journal owner to continue to see those comments. However, these comments should be presented without replyto links, and the replyto for each comment should redirect to the thread link. This will prevent the journal owner from repeatedly commenting to those who are no longer able to respond.

For a journal entry which is originally posted with comments disabled, the current behavior is preserved. For those journal owners who prefer the current behavior to the suggested behavior (i.e., they want disabling comments to prevent <em>them</em> from seeing comments already made) they can add this line to their customized css.

div.comments {visibility: hidden; speak: none; }

2) As I said, often disabling comments is not an attempt to hide prior discussion, but to stop future discussion. In certain circles in LJ, disabling comments on a contentious post is viewed as a cowardly coverup. Allowing past comments to remain visible to everyone able to the view entry, while disabling the replyto function, would let the historical record remain clear. Of course, the account which posted a comment should still have the ability to delete the comment, but they should not have the ability to *edit* any comments, even if they are paid users and the comment was never replied to.

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


This suggestion:

View Answers

Should be implemented as-is.
15 (30.0%)

Should be implemented with changes.
30 (60.0%)

Shouldn't be implemented.
2 (4.0%)

(Other: please comment)
3 (6.0%)

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise2009-07-13 05:23 pm

Ancestor links on comment pages

Title:
Ancestor links on comment pages

Area:
Comments

Summary:
To have a link that says Ancestor next to the Parent link, which goes to the top of the thread this comment is in.

Description:
When I follow a link to a specific comment (it could be on a post I'm tracking, or a reply to my comment, or a link in a post), I get the thread below that comment, but not the thread above, which is often more relevant. If I click "View comments", there might be dozens or hundreds; if I click Parent, I don't know how many levels I'll need to go up to get the context.

I think it would save bandwidth and possibly database load if there was a link that took you to the top of the current thread, or perhaps (in a long thread) to the point where the original comment collapses.

If it can only be done by looping round the Parent code, it could be database-heavy, but I guess most people who would use it, keep clicking Parent instead so you have the same load spread out over more time and you're drawing the intermediate pages which they don't want.


(Suggested by <user name=susanreads>, who was bitten by the free-user poll bug.)

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


This suggestion:

View Answers

Should be implemented as-is.
32 (55.2%)

Should be implemented with changes.
25 (43.1%)

Shouldn't be implemented.
1 (1.7%)

(Other: please comment)
0 (0.0%)

ivorygates: (Default)
[personal profile] ivorygates2009-07-13 07:02 am

Allow a comment to an entry to be sent as a PM

Title:
Allow a comment to an entry to be sent as a PM

Area:
entries

Summary:
If we had the option to reply to comments in our own journals in the form of a PM to the person who commented as well as in the form of a comment, it would be cool.

Description:
This is not a problem-solving suggestion. But there are times that you want to respond to a comment privately, either to provide sensitive information or just to tell the person to STFU without embarassing them. Or even to provide sekrit information that the other people reading your journal can't see. And it's a PITA to have to hunt your way over to their journal and construct a PM when you could just have one-touch shopping.

And if doing that didn't unscreen their comment -- if you happen to have all comments screened -- that would be even more awesome! It would be a way to reply to unscreened comments without opening the thread of discourse for general view.

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


This suggestion:

View Answers

Should be implemented as-is.
15 (38.5%)

Should be implemented with changes.
3 (7.7%)

Shouldn't be implemented.
17 (43.6%)

(Other: please comment)
4 (10.3%)