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
Right now, even with the few creators I follow, notifications are really piling up in my inbox, and its becoming a pain already:
It may be sensible to introduce batching of notifications of certain kinds to avoid this. For example, if I already have received 1 notification today, then all subsequent messages are batched and sent as one email in a few hours, but then you could have excpetions, like if the notification are urgent, like actions relating to auction or other time sensitive stuff. So policy is something like: always send first notification to a given recipient right away if it has been more than X hours (e.g. X = 12 hours), otherwise put in recipient specific pool which is only sent out once it gets to a certain size Y or some number of hours Z have gone by since last notification was added.
It probably is wise to just start by looking up what some standard e-mail notification methodologies are, so we don't need to re-invent something 80% as good as something totally standard we could follow.
The text was updated successfully, but these errors were encountered:
Right now, even with the few creators I follow, notifications are really piling up in my inbox, and its becoming a pain already:
It may be sensible to introduce batching of notifications of certain kinds to avoid this. For example, if I already have received 1 notification today, then all subsequent messages are batched and sent as one email in a few hours, but then you could have excpetions, like if the notification are urgent, like actions relating to auction or other time sensitive stuff. So policy is something like: always send first notification to a given recipient right away if it has been more than X hours (e.g. X = 12 hours), otherwise put in recipient specific pool which is only sent out once it gets to a certain size Y or some number of hours Z have gone by since last notification was added.
It probably is wise to just start by looking up what some standard e-mail notification methodologies are, so we don't need to re-invent something 80% as good as something totally standard we could follow.
The text was updated successfully, but these errors were encountered: