Comment Re:Automated digesting (Score 1) 173
For example, "Recovery: server.domain.com is online" could be enhanced to something like, say, "Recovery: server.domain.com is online. Further on/off messages are suspended for 8 hours unless you click
I think I mentioned elsewhere, a part of the problem with the sort of notifications I'm talking about is that I'm receiving them from many different vendors/services/devices who each choose their own standards, forms, and methodologies. It's the nature of things that I don't necessarily have any control over what I receive, how I receive it, when I receive it, or what form it comes in as. If I could even control what came in the subject line, then I wouldn't consider it such a problem.
For example, it's not just notifications saying, "Recovery: server.domain.com is online", but also any number of different notifications from different domain registrars that a domain is about to expire. I can't make GoDaddy, Namecheap, and NetworkSolutions follow the same procedures for how far in advance I get notified that a domain will expire, or what that notification will look like. I can't even stop one of those companies from deciding to change their own policies, changing the subject, content, and sender of those kinds of notifications. In fact, just to give an example, Dropbox uses Mailchimp for a bunch of their notifications, which means that each email is sent from a different sender address.
You can say, "Well these companies should have a better method of notification than email," or "These companies should be following certain standards," but good luck with making that happen. Until you can come up with a better solution, I'd really appreciate if someone could come up with some good tools for managing this kind of flood of notifications.