Chronologically Sort Used Invite Codes

[ninetydegrees]

Title:
Chronologically Sort Used Invite Codes

Area:
site interface

Summary:
On http://www.dreamwidth.org/manage/invitecodes?full=1, you can see when your invite codes were used. They're more or less sorted chronologically (by year definitely for me; by month, day and time only approximately). I'd like them to be fully sorted chronologically.

Description:
I'm sure some people would like to be able to sort them by other criteria such as 'recipient' and 'sent on' so it might be best to do all the cats at once.

Poll #7124 Chronologically Sort Used Invite Codes

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

View Respondents

This suggestion:

View Answers

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

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
22 (40.7%)

(Other: please comment)
0 (0.0%)

Include entry subject line in Take a look at this Dreamwidth entry

[katherine]

Title:
Include entry subject line in Take a look at this Dreamwidth entry

Area:
site: email

Summary:
Include the Dreamwidth entry's own subject line in the Take a look at this Dreamwidth entry e-mail's subject.

Description:
I'd like to see (even part of) the Dreamwidth entry's own subject line in the Take a look at this Dreamwidth entry e-mail's subject. "Take a look at this Dreamwidth entry" is rather generic especially when one gets more than one.

Poll #7127 Include entry subject line in Take a look at this Dreamwidth entry

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

View Respondents

This suggestion:

View Answers

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

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
16 (30.2%)

(Other: please comment)
0 (0.0%)

Switching the userhead in the posting interface to the DW userhead

[beatrice_otter]

Title:
Switching the userhead in the posting interface to the DW userhead

Area:
posting

Summary:
Right now, the icon in the Posting interface to insert a username uses the LJ userhead instead of the DW userhead. This should probably be changed so that the DW userhead is the one used.

Description:
Right now, the icon in the Posting interface to insert a username uses the LJ userhead instead of the DW userhead. This should probably be changed so that the DW userhead is the one used. This would standardize the look of the site. I can't see any drawbacks, all you need to do is swap out the old icon for one of the new userhead.

Poll #7125 Switching the userhead in the posting interface to the DW userhead

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
55 (85.9%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
9 (14.1%)

(Other: please comment)
0 (0.0%)

Memo field on Manage Invite Codes

[susanreads]

Title:
Memo field on Manage Invite Codes

Area:
invite codes

Summary:
Add a memo column to the list of invite codes, to note when you've done something with a code other than use it or send it by email

Description:
The Invite Someone page tells me I have a certain number of unused invite codes, and shows me the first (oldest, I think) 5. But some of them (probably including those 5) have been offered (by means other than email) to someone, who hasn't used them yet, but they might. I can click through to a longer list, which shows me when and where I've sent those codes that I sent by email but which haven't been used yet. I would like to be able to add a note to those that weren't emailed, e.g. "Sent in a PM to $USER" or "posted on dw-codesharing", with a date if there's room. Then the Invite Someone page could display codes that don't have notes in preference to those that do, or display the note.

This would reduce the work involved in making sure that I don't offer someone codes that have been offered to someone else already. There's a workaround, which is to email each code to $MY-E-ADDRESS+$NOTE, but that's a bit fiddly and not everyone knows how to do it or has an email that can handle it.

The only problem I can think of is fitting the extra column onto the page. The list on the Invite Someone page has space to the right; on the longer list, perhaps it could go in the email address column because there wouldn't be both.

Poll #7126 Memo field on Manage Invite Codes

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

View Respondents

This suggestion:

View Answers

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

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

Shouldn't be implemented.
1 (1.7%)

(I have no opinion)
21 (35.0%)

(Other: please comment)
0 (0.0%)

Direct Message re: This Entry

[zvi]

Title:
Direct Message re: This Entry

Area:
Messages, Entries, Comments

Summary:
Allow people to send a direct message re: an entry instead of commenting on it

Description:
"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." -rho

The reason that a number of commenters favor allowing commenters to screen entries and/or to split up the comment function into entry discussion and sending a private message is that sending a direct message requires a commenter to (a) go to a separate page and (b) invoke the entry to which they are responding.

I propose that, instead, we permit someone to respond to an entry in the form of a comment, but then, with a tickybox, "send comment as direct message instead", send the OP a direct message whose subject line is the entry being commented upon, in the format

-----------------------------------------------------------------------------------
RE: example.dreamwidth.org/12345.html where you wrote:

[first 250 characters of entry]

example commenter responded:

[a message they want to send the OP but not anyone else]
-----------------------------------------------------------------------------------

This will allow people to have the direct communication they want in a format where the OP can't inadvertently reveal their direct communication to the other people reading the entry, and it won't require them to go to any other pages or summarize the entry, as this will be done automatically.

The drawback, from the journal owner's point of view, is that discussion will be disaggregated. I am not particularly concerned about this, as people always had the option of sending the OP a direct message or an e-mail or making an entry in their own journal in response.

The big drawback from the direct message sender's point of view is that the OP may allow people to make comments who are not allowed to send direct message's.

In this case, I suggest we degrade gracefully and say, "You do not have permission to post the message below"

[text box with the commenter's message, so that they can copy it or send an e-mail or whatever they need]
[button: comment on the entry] [button: cancel sending message] [link: return to entry]

Poll #7129 Direct Message re: This Entry

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

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
29 (43.3%)

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

Shouldn't be implemented.
6 (9.0%)

(I have no opinion)
21 (31.3%)

(Other: please comment)
3 (4.5%)