News for hackers. Stuff that matters.
Re:Why we’re betting against real-time team messaging by hedora on Monday June 19, 2017 @11:26AM (#14587643)
For a while gmail had this ui "feature" where <tab><enter> or <tab>string-of-characters<space> would send an email without prompting.

I still fear the web UI. I guess emailing out bullet lists was against the implicit use case the gmail UI team had in mind.

Stuff like this definitely changes how tools are used.

Re:Why we’re betting against real-time team messaging by burntwater on Monday June 19, 2017 @03:37PM (#14589769)
This exact problem led to my current behavior that I now use in all email apps: I delete/never fill in the "to" fields leaving that for last. Can't accidentally send an email to nowhere...
Re:Why we’re betting against real-time team messaging by majewsky on Tuesday June 20, 2017 @05:16AM (#14593115)
Entirely unrelated to the Slack discussion, but I wonder if that could be a positive pattern for a mail client: only allowing you to define the recipients when you have written out the full message.

Also, when replying to a long mail thread, showing you the previous list of recipients and requiring you to select those that you want to include in your next mail. Could limit CC sprawl quite a bit.

Re:Why we’re betting against real-time team messaging by pythonaut_16 on Monday June 19, 2017 @12:11PM (#14588013)
In the case of Gmail (and most email systems really) I always start out by putting my own address in the To: field. That way if I accidentally send it will just come back to me. It can also be useful because I can first send the email to myself to double check the way it will look on the receiving end before sending it to the actual recipient.