New in Labs: Stop sending mail you later regret
gmailblog.blogspot.com
gmailblog.blogspot.com
I could then go back to it and edit it at will or delete it before the send time has passed.
Our industry has really benefited from a "throw it against the wall and see what sticks" mentality. Is this a good feature? I don't know, but I do like the idea of Google inventing 100 or 1,000 such features and seeing if one of them is a winner.
I am not so sure that a product management team with a gating and evaluation process will do a better job of picking features than--no offense googlers--a million monkeys randomly inventing features they think are neat-o.
But rather than setting delays I'd like to just define a range (say 8am–6pm) during which mail is sent. Anything outside that range would be queued until the next period.
1) How to build it? (server-based or client-based) and 2) Who's going to pay for it?
It sounds like one of those things that a small number of people talk passionately about but there's not actually any money in making their pain go away. Or maybe -- beats the heck out of me where the payback is.
Client-side this is less than a week on the Microsoft platform -- a month if you want to handle all email clients. Server-side? I think you'd have to pick just one mail host and stick to customizing it.
One of the issues would be turning it off -- you'd have to have some kind of neato keypad test thingy to prevent drunken farts from just clicking the button and sending anyway. That leads me to believe a better design might be client-side.
Store-and-forward has another big set of issues though. File sizes and bandwidth requirements are easily non-trivial. In addition, there could be legal issues with keeping the data around for awhile and then forwarding that wouldn't exist if you just piggy-backed on some other app. In a way, it kind of puts you in the league with GMail and the other guys, right?
Since Gmail has a bunch of google lab apps in the gmail settings, it might well happen....
As of many people replying they need a feature no one has - here's opportunity of creating a completely new web e-mail system :-).
I've never tried it, though.
$ at 8:00am sh -c 'mail person@normal-sleep-schedule.com < my_message.txt'If you wake up in the middle of the night to heed nature’s call, take a moment to leave a voicemail message for your boss. Your message will automatically leave a recorded time-stamp, thus reinforcing the illusion that you work around the clock. This is a big improvement over reality -- that you chugged a beer before going to bed.
Maybe it could be a greasemonkey-added "Send later..." button that you have to manually click on every time (to avoid thinking you sent an email, but it was actually put into a queue) along with an input box for delay-time.
When you click it, it could (1) add a unique identifier to the subject, (2) save the email in drafts, and (3) send a message to a server-side app (which knows your Gmail authentication info) with the ID of the message and the time it should be sent. Then at the appropriate time this app logs in, finds message by unique ID, gets rid of said ID, and sends the message.
Let me put it this way: During the normal weekday, a 15 minute delay is probably sufficient. But coming home late on a Friday night, is 15 hours enough? Or, in some cases, 15 days?
So that's the question: how to define X ahead of time without knowing all conditions for which X applies? I suppose you could have date/time conditionals, but there would be instances where you probably violate your own rules.
Also, if they are listening I would like to be able to Twitter within Gmail. Have an inbox tab and a Twitter tab; spend all my time in Gmail & refresh Twitter a few times a day, why not consolidate?
What they did instead is so gimmicky it makes me cringe.
In other words, if you know your mail won't be sent right away, will that delay the background, subconscious mental process of analysing your actions to see if you screwed up?
If you want a moral in this story, don't drink two 1-liter mugs of micro-brewery beer within a couple hours and then continue drinking Guinness and shots ($30+ worth!) after relocating to a popular Irish bar.
From experience one has followed the other. but YMMV ;)
I think both an email client and SCM client should be integrated with a breath tester.
Google enables our vices without actually identifying them. :)
(Regular YCer here, just don't need this linked to my actual name)
Yeah, you wouldn't want anyone to know you enjoy sex.
If you try to actually turn this on in your Gmail settings, you will scroll past their random signature option.
I kind of like it when they implement stuff like that, just because it's fun.
There was some scripting built in, and one of the things you could do was add a one hour sending delay to anything with a certain number of chilis.
The combination of visual display and scripted "let me sleep on it" features worked really well.
Similarly, email clients should catch references to attachments that aren't there, and ask "do you really want to send this without an attachment?"
Even more generally, they could recognize (and allow to be configured) certain addresses as requiring additional confirmation before sending -- so a mistaken overbroad or misdirected CC becomes less common.
(I'm thinking: first time you send to an address, you get a confirmation popup, and a chance to classify this address: require dialog confirm; require captcha/retype-of-name confirm; require waiting period; require confirm if combined with other address; etc.)
This was a Better GMail (Firefox extension) feature that is now available in GMail Labs under Settings.
Of course, the next step is to have an hardened mail goggles feature which requires you to write a greasemonkey script in order to send an email.