Reporting spam in emailed comment notifications

[hatam_soferet]

Title:
Reporting spam in emailed comment notifications

Area:
Comment notifications

Summary:
Add "Delete the comment and report as spam" as an option in emailed comment notifications.

Description:
Emailed comment notifications have a list of options:

View the thread beginning with this comment
Go to the top of the thread this comment is part of
View all comments to this entry
Reply at the webpage
Delete the comment

It would be very convenient if "Delete the comment and report as spam" was also an option. I want to help DW by reporting spam, but it's annoying to have to do it by opening a whole new browser window, especially when I'm on a computer where I can get my email but not access DW.

Poll #7103 Reporting spam in emailed comment notifications

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
23 (43.4%)

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

Shouldn't be implemented.
13 (24.5%)

(I have no opinion)
16 (30.2%)

(Other: please comment)
1 (1.9%)

Include Name of Journal Base Style and Theme In Credit Module in Journal

[ivorygates]

Title:
Include Name of Journal Base Style and Theme In Credit Module in Journal

Area:
Styles

Summary:
By default, journal styles credit the designer or designers of the base style and the theme and display that information in one of the modules. What does not appear is the name of the base style or of the theme being used by the journal. It would be nice if that information also displayed.

Description:
When I read a journal displayed in the owner's style, there are many times when I would like to know what base style and what theme they have chosen. While there is a default module that appears in the journal [unless you select to remove it] that displays the names of the people who created the base style and the theme, neither the base style name nor the theme name is displayed in the module [at least in any of the journals I've looked at]. This is frustrating if you see a style/theme you think you'd really like and have to do a lot of trial and error on the "Select Journal Style" page to try to find it, and it would be nice if there were an option to display this information by default.

Since some people write their own style from scratch, or tweak the theme, or use their own resources for background images, it would probably also be nice if the module that displayed full style and color credits could automatically default to "Base style: DesignerName; Theme: JournalOwner; Resources: Journal Owner" in that case.

Poll #7105 Include Name of Journal Base Style and Theme In Credit Module in Journal

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
37 (72.5%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
13 (25.5%)

(Other: please comment)
0 (0.0%)

Ability to leave/join communities on Manage Circle page

[yvi]

Title:
Ability to leave/join communities on Manage Circle page

Area:
Manage Circle

Summary:
In addition to subscribing/unsubscribing, add the option to leave/join communities on http://www.dreamwidth.org/manage/circle/edit

Description:
On http://www.dreamwidth.org/manage/circle/edit , there is a Communities section. You can do the ticky/unticky thing there to subscribe or unsubscribe to a community. However, when it comes to membership, you can only see your current status there, not change it. Let's please add that.

How this suggestion came to be: I was going through the communities and actually used the hover menu to leave and unsubscribe from communities because half of that isn't possible on the page. And then I accidentally saved the page. So now for all the communities I had planned to leave and unsubscribed, I had now left the community, but been re-subscribed, as the checkbox was marked when submitting the page. Had I been able to do everything via the Manage Circle page, I could have spared myself that.

Poll #7104 Ability to leave/join communities on Manage Circle page

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
54 (93.1%)

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

Shouldn't be implemented.
1 (1.7%)

(I have no opinion)
3 (5.2%)

(Other: please comment)
0 (0.0%)

Split comment screening into moderation and private comments

[rho]

Title:
Split comment screening into moderation and private comments

Area:
comments

Summary:
As it currently stands, comment screening is used for two very different purposes. It's used to allow the journal owner to check over comments before they are visible, and it's used to make private comments that are never intended to be seen by anyone other than the journal owner. I propose that this functionality be split in two.

Description:
[Based on http://dw-suggestions.dreamwidth.org/548634.html?thread=3291930#cmt3291930]

The original idea behind comment screening was that it should be like moderation. The journal's owner would have a chance to read over the comments before they were visible, and delete any that were incendiary, inappropriate or just plain spam.

What with users being users, a lot of people have found other uses to put this feature to, though, namely as a method of making private comments that aren't meant to be visible to anyone other than the journal owner.

While I always think it's great when people find unexpected uses for features, the problem here is that the two main uses are very different and have very different needs. Features that will benefit one usage can be to the detriment of the other.

The obvious example here is what happens when you reply to screened comments. In the original implementation, a comment would automatically be unscreened when you reply to it. This absolutely makes sense in the moderation model, but is disastrous for the hidden comments model. As a result, Dreamwidth no longer automatically unscreens comments when you reply to them.

What I'm proposing is that the overloaded concept of comment screening should be split into two. That is, we should have two features, one of which would be for comment moderation, and the other of which would be for making private comments. The biggest advantage to this would be that the two features could then be developed separately and in their own directions, without needing to worry about how they impact each other.

I think it would also be useful in terms of clarity of what the feature is for. There are also currently instances where it's not immediately obvious why the author is screening comments. For instance, if someone makes an emotional post about a controversial subject, they might want to screen comments to moderate out trolls, or they might want to screen comments because they don't have the emotional energy for public discussion. With the split, this would become much clearer.

The biggest disadvantage I can think of for this is the added complexity. this would especially be noticeable when posting entries, since there are already a lot of available options there.

The following are NOT part of this suggestion themselves, but are intended as examples of the sort of thing that could be done if this split were implemented.

* A reversion to the old behaviour of moderating comments automatically when they're replied to for moderated comments only.

* The implementation of comment moderation whitelists of people whose comments display without moderation (possibly based upon access lists).

* Allowing people to see how many comments are awaiting moderation on a post.

* The option for private comments to be truly private and not have any way of them being made public.

* Comments on an entry being able to be enforced public, enforced private or (the new setting) commenter chooses whether to be public or private.

* Giving the poster of a comment the ability to change the privacy status of their comments (if allowed in journal/entry settings).

Poll #7106 Split comment screening into moderation and private comments

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
30 (48.4%)

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

Shouldn't be implemented.
11 (17.7%)

(I have no opinion)
17 (27.4%)

(Other: please comment)
1 (1.6%)