search

theCrag / website

theCrag.com: Add your voice and help guide the development of the world's largest collaborative rock climbing & bouldering platform
https://www.thecrag.com/
109 stars 8 forks source link

Single email per message instead of daily digest #879

Open brendanheywood opened 11 years ago

brendanheywood commented 11 years ago

Something I've found really annoying in the last 2 weeks is attempting to use the messaging system for near real time comms. I've missed out on a couple messages that we're fairly time sensitive because I wasn't on the site. Getting an email almost 24 hours later, then responding, and then the other person getting that email 24 hours later isn't ideal.

So basically I'd like to see the messaging system send emails for discussion you are 'involved' in, in near real time. The 'interested' messages from fav crags etc can and should still be a digest. Even if there was a small delay up to 5 minutes I think this would be a massive leap up.

Yes this will be fixed for those who have the android app, but plenty of people won't and email is universal. And even with the app I'd personally prefer to manage all of my messages in one place (eg gmail)

Yes there will be load impactions but it seems the messages are still being sent in real time by the event system anyway, they just optionally also need to be queued up and sent via email too.

scd commented 11 years ago

Agreed. Maybe not this release but the one after. This next release has a huge amount of stuff on it. Btw, Adam's app works really well with this use case.

brendanheywood commented 11 years ago

Some more notes / thoughts on email headers:

from: if a friend and permission are right, use their email, otherwise use a generic 'notifications@thecrag.com' reply-to: initially a noreply email, later will be the discussion id hash email address to: the users email address (github uses cc, not sure why) mailinglist: unsubscribe: url to unwatch that discussion precedence: bulk - handle out of office auto replies Message-ID: message id - avoid duplicates if resent References: the message id of what this is responding to, ie the root message List-Archive: url of whole discussion

http://www.jamesshuggins.com/h/web1/list-email-headers.htm

brendanheywood commented 11 years ago

Just randomly playing the other day and wondering about email titles. I was thinking if we had a boilerplate [theCrag] in the title as well as the title of the crag eg 'Arapiles' as well as the name of the discussion that it could get a bit cluttered. Some services like github don't even have github in the email title at all. That might be a bit extreme so I was toying with the idea of a little almost ascii art boiler plate which looks like our logo:

image

Another idea based as a crumb trail:

image

I think it's important to keep something static so people can filter the emails.

cgome commented 11 years ago

I prefer the second option (crumb trail). On Dec 24, 2012 2:38 PM, "Brendan Heywood" notifications@github.com wrote:

Just randomly playing the other day and wondering about email titles. I was thinking if we had a boilerplate [theCrag] in the title as well as the title of the crag eg 'Arapiles' as well as the name of the discussion that it could get a bit cluttered. Some services like github don't even have github in the email title at all. That might be a bit extreme so I was toying with the idea of a little almost ascii art boiler plate which looks like our logo:

[image: image]https://f.cloud.github.com/assets/187449/29422/84a6cfea-4d7a-11e2-93a3-d4e4baf38435.png

Another idea based as a crumb trail:

[image: image]https://f.cloud.github.com/assets/187449/29427/cd08fbf0-4d7a-11e2-8ba8-80dfd19ee82d.png

I think it's important to keep something static so people can filter the emails.

— Reply to this email directly or view it on GitHubhttps://github.com/theCrag/website/issues/879#issuecomment-11653906.

Mdemaillard commented 4 years ago

see related #720