You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under "My Account -> Preferences -> Offline Email Notifications" add a choice to only trigger a mail when no mobile client with enabled push notifications are available. I don't know how this is feasible, but something like a mobileClientLastSeen token to guide the choice whether to send a mail or rely on the push notification reaching the user.
I love the idea of getting an email when mentioned/DM'ed while offline, albeit one for every such message is a little much to my taste, luckily there's already an issue for that: #6079. Anyways this idea could make communication less intrusive in various use cases, when the user is not online with a desktop client.
The text was updated successfully, but these errors were encountered:
I liked your idea of having an additional option to only send an email when no mobile client with enabled push notifications are available. my only concern is if your device isn't available anymore, in this case the server doesn't know if the push notification was delivered or not, leading to lost notifications.
Rocket.Chat Version: 0.56.0
Running Instances: 1
DB Replicaset OpLog: Enabled
Node Version: 4.8.1
Under "My Account -> Preferences -> Offline Email Notifications" add a choice to only trigger a mail when no mobile client with enabled push notifications are available. I don't know how this is feasible, but something like a mobileClientLastSeen token to guide the choice whether to send a mail or rely on the push notification reaching the user.
I love the idea of getting an email when mentioned/DM'ed while offline, albeit one for every such message is a little much to my taste, luckily there's already an issue for that: #6079. Anyways this idea could make communication less intrusive in various use cases, when the user is not online with a desktop client.
The text was updated successfully, but these errors were encountered: