BCC/CC message to original sender.
Closed this issue · 7 comments
This was brought up on IRC in #cjdns
<brendanje> lukevers: I just ran into a usability issue… I spaced out and don't remember who I just sent a message to. It'd be cool if the system could let me know so I don't spam folks. Send me the same email or something.
I don't know the difference between BCC and CC, so I left both in the header of this issue. I really should take a look at that because I don't want to end up using the wrong one.
@SashaCrofter, thoughts?
It might get annoying to get a "you just sent a message to" or "here's
the message you just sent to" type email every time you send an
email. Maybe it would be better to mark them somehow (such as "Message
Sent" in the popup) JavaScript side, until page reload. That way, you
could keep track of who you've messaged (per session, at least).
There could also be, say, a checkbox in the message dialogue saying
"CC me on this message" or something. I don't think that should be
default, though.
I think a checkbox would probably be the best way to do that, and we
default it to unchecked.
On Sun, Aug 11, 2013 at 12:25 AM, Sasha Crofter notifications@github.comwrote:
It might get annoying to get a "you just sent a message to" or "here's
the message you just sent to" type email every time you send an
email. Maybe it would be better to mark them somehow (such as "Message
Sent" in the popup) JavaScript side, until page reload. That way, you
could keep track of who you've messaged (per session, at least).There could also be, say, a checkbox in the message dialogue saying
"CC me on this message" or something. I don't think that should be
default, though.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/157#issuecomment-22452296
.
Annoying? Only for a large number of messages. Is the messaging system intended for conversation or just pings?
Btw, if it's for pings a template offering some guidance on how to ask for peering would be cool.
The javascript-side log of messages sent would be really awesome! Local storage instead of volatile memory?
@brendanjerwin the messaging system is intended for people to find more peers. NodeAtlas does not, however, continue to relay messages back and forth. If someone wishes to respond, the sender's email is included at the footer of the email and I believe it's also automatically put into the reply-to field (@SashaCrofter may need to verify that, but I think that's something that we do).
Currently we don't do pings, but we have kept them in mind and haven't implemented it yet. You can see #56 for our full list of status codes that are currently being kept.
On the note of templates being shown for some guidance, I don't think that's a bad idea. I think another idea which should be eventually implemented is that we have some help bubbles that pop up when you hover over something because some things aren't explained well enough.
If that's the case, that the conversation is handed off to email entirely, then sending the original email to the sender would be even cooler. Then I could see the entire conversation in my email client.
Btw, by "ping" i meant pinging / begging for a peer. Looks like I stumbled on some lingo.
On Aug 11, 2013, at 10:12 AM, Luke Evers notifications@github.com wrote:
@brendanjerwin the messaging system is intended for people to find more peers. NodeAtlas does not, however, continue to relay messages back and forth. If someone wishes to respond, the sender's email is included at the footer of the email and I believe it's also automatically put into the reply-to field (@SashaCrofter may need to verify that, but I think that's something that we do).
Currently we don't do pings, but we have kept them in mind and haven't implemented it yet. You can see #56 for our full list of status codes that are currently being kept.
On the note of templates being shown for some guidance, I don't think that's a bad idea. I think another idea which should be eventually implemented is that we have some help bubbles that pop up when you hover over something because some things aren't explained well enough.
—
Reply to this email directly or view it on GitHub.
After thinking about this, I'm not so sure how much of an issue this is. When the person receives an email from NodeAtlas, they can directly reply to that message because replyTo is set to the from address. If the recipient does not reply directly to the email that is their loss because they also lose the original email in the thread. I don't think this is an issue of NodeAtlas more of an issue of people using it correctly.
I'm closing this issue, but if anyone thinks Bcc really should be implemented, please reopen this issue or comment saying so.