![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Allow adding (or replying) initial/default recipient when replying to a PM
Title:
Allow adding (or replying) initial/default recipient when replying to a PM
Area:
inbox, private messages
Summary:
When replying to a Dreamwidth PM sent to you, allow adding recipients to the initial recipient (sender of the message you're replying to), or even replacing that recipient with an arbitrary list, for a quick and dirty forward,
Description:
This wouldn't breach privacy that I can see (who the original message went to), because the only initial recipient of the reply would be the sender, as it already is, and no other recipient of the original message would be offered as a suggestion or listed. (Indeed, that would be impossible, as the list of original recipients isn't kept anywhere. One message sent to several users looks the same as several identical messages sent very close.)
This suggestion:
Should be implemented as-is.
13 (26.5%)
Should be implemented with changes. (please comment)
0 (0.0%)
Shouldn't be implemented.
15 (30.6%)
(I have no opinion)
19 (38.8%)
(Other: please comment)
2 (4.1%)
no subject
If you, Matt, send the same PM to five people, then it is not a private message. It is just a message. There's nothing private about it at all.
Likewise...
If I receive a message from Sophie and copy my answer, along with her original message, to her and five others, then it is not a private reply. It's just a reply. And her private message is no longer private, either.
If what I've described above is not how private messaging works - nor how it should work, in most people's opinions- then I want the name of it changed to "on-board email", "the mailing lists", "on-site email" or whatever phrase best connotes no expectation of privacy at all.
I absolutely hate misnomers, especially ones that are as misleading as "private message" is turning out to be - at least judging by this thread.
no subject
For the record, the scenario that the parent commenters are describing (which is already possible) is to copy the message into the clipboard, paste it into a new message, and use the 'multiple recipients' feature of specifying multiple names separated with comments to send that message to others. Since the message system doesn't distinguish between 'replies' and 'new messages', it's basically the same thing. From a purely technical standpoint, adding this feature wouldn't make any difference.
In other words, for a message to 'not be forwardable', the Dreamwidth code would need to check the contents of the message to make sure that the message you're sending doesn't contain content from any message you've received previously. Obviously, that's not going to happen, because it would be an artificially silly restriction.
Now, from a social standpoint (disregarding the fact that anybody who really wants to can just send a new message anyway), I can see where you're coming from about not having a forward option. Not having that option would mean that the other person would have needed to specifically use a new message, which will at least mean that they would have had to think more about whether that's a good action.
In the end, I'm against this suggestion, but not for that reason; I'm against it because I think that PMing isn't really supposed to be a replacement for email. There are better tools available for the job.
no subject
But I've never thought of them as private messages, merely on site messages. So I'll talk it through with Denise when I get a chance, and consider rewording the relevent FAQs to remove the term private.
The feature itself doesn't use the term private messages anywhere I can see, it's just documentation that does. I've found two, How do I send people messages on Dreamwidth? and How do I protect my privacy on Dreamwidth? (Part 2), that's from a cursory search, I'll do a more thorough scan when I've time, if you see any more let me know.
Not perhhaps a long term fixx, but there's going to need to be a discussion about what people want the site to offer in terms of features like messages, so we either call them PMs and keep them private, or we call them something else and don't give people false expectations, and move them towards a different functionality.
Definitely can't call them email though, they're not email, they don't follow email protocols.