Notification Timeout - Most notifications are not indefinitely relevant

[Luehrsen]

I propose an additional field for the notification model: timeout - A datetime after which the notification is not shown.

Most WordPress systems are not maintained daily, not even on a weekly basis. But I foresee that there will be a lot of notification that are relevant to only a certain timeframe, for example seasonal marketing pushes.

To decluter the notifications for the users and to keep the message queue as relevant as possible I suggest giving the sender the ability to define a timeout for that notification, after which it will not be shown anymore and deleted from the queue.

[folletto]

This is a very interesting idea that I think it would be worth exploring.

1. What's the benefit of a timeout compared to an app able to use a second API to remove a specific message once it's not relevant anymore (pro: more flexibility for the plugin, con: more management on the plugin side)
2. What's the potential for abuse of this one? What if a plugin sends something problematic so the user sees it, to then disappear thus becoming untraceable? Other?
3. How would this work with different delivery methods? Given WP Notify has to be compatible and work with other delivery protocols, how would this work on either iOS/Android or if the notification triggers an email?

[raaaahman]

On a technical point of view, some notices might only be relevant during a session (noticing the user that his/her last action worked/failed), so tagging such notifications to not persist would be a must.