May. 14th, 2012

azurelunatic: Vivid pink Alaskan wild rose. (Default)
[personal profile] azurelunatic

Title:
(Optional!) Interaction analytics and suggestions

Area:
circle management

Summary:
Allow the option to automatically suggest circle modifications, a la Facebook except with less creepy.

Description:
The thought that the website is watching you and has all sorts of helpful suggestions about your personal life is at heart amazingly creepy. Despite the fact that you trust the website for rather a lot does not mean that you actually want the website peering over your shoulder.

However, that changes if you invite the website to peer over your shoulder, and know the things that the website will be looking at. It's the permission that changes the perspective, and while knowing the factors is counter to a "this is our proprietary algorithm" outlook *cough*facebook*cough*, it sounds positively Dreamwidthy. It should also have an easy and intuitive way to turn it off, if it winds up not being what a user wanted for whatever reason.

If turned on, the analytics could suggest possible interactions between users, such as: "You comment to Anna and read their journal more than many other users who are not on your reading list. Do you want to add Anna to your reading list?" or "You have deleted 99% of the comments left by Bit in your journal in the last 2 weeks. Do you want to ban Bit from commenting?"

This might introduce users to features they were not previously aware of.

Any suggestion should be able to be ignored or declined; ignored (no interaction with suggestion) would be left in place; declined suggestions would go away and not come back; declined suggestions would have the option for the user to leave a note; declined suggestions would be listed in a user-accessible place, along with the notes (if any). Saving the declined suggestions would let the user recover from dismissing a suggestion if they did not mean to, and the notes would be a reminder of why the user dismissed that particular suggestion, in case things changed later (for example: "Add Charlotte to reading list?" might have been dismissed with "I'm not interested in Iron Man"; upon looking in the bin later, the user might re-visit their decision on the grounds that they love the Avengers now.)

Poll #10463 (Optional!) Interaction analytics and suggestions
Open to: Registered Users, detailed results viewable to: All, participants: 50


This suggestion:

View Answers

Should be implemented as-is.
6 (12.0%)

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

Shouldn't be implemented.
25 (50.0%)

(I have no opinion)
15 (30.0%)

(Other: please comment)
4 (8.0%)

azurelunatic: Vivid pink Alaskan wild rose. (Default)
[personal profile] azurelunatic

Title:
Demi-ban: screen all future comments from specific user

Area:
comments, comment screening

Summary:
Force-screen comments from one particular user, when it's just that user whose comments warrant screening.

Description:
Occasionally there is a user who may be commenting in a particular journal or community in such a way that they do not quite warrant a ban, but fully warrant review from the admins/owner just to make sure their comments are productive.

Everybody else is commenting all right, it's just that one person.

Setting [class that includes commenter] to have their comments screened (whether that class be everyone, non-Access/Members, or anonymous) would be overkill for this situation, because they haven't brought along friends, it's just them. Turning on screened comments tends to dampen discussion and can be a lot of work to unscreen.

A demi-ban which makes all that user's future comments screened, but leaves everybody else's alone, would solve this problem on a technical level.

On a social level, this person could then use another account to evade the demi-ban and not be subject to screening. That's something that is likely to be noticed, and then the admins/owner would have to decide how to handle it. (The admins/owner may well decide that it's time to actually ban both accounts.)

Evading a demi-ban should not be a ToS-able offense. Evading an actual ban still should be.

Poll #10464 Demi-ban: screen all future comments from specific user
Open to: Registered Users, detailed results viewable to: All, participants: 84


This suggestion:

View Answers

Should be implemented as-is.
67 (79.8%)

Should be implemented with changes. (please comment)
7 (8.3%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
10 (11.9%)

(Other: please comment)
0 (0.0%)

Profile

Dreamwidth Suggestions

December 2018

S M T W T F S
      1
23 45678
9101112131415
16171819202122
23242526272829
3031     

Style Credit

Expand Cut Tags

No cut tags