> It is undeniable that notifications became an inescapable part of our overly techy lives in the past decade.
Eh, I dunno. They make sense on a phone, which fundamentally is for contacting a person. The device is all about tasks which are not kicked off by a user. On a computer, though? What, is there some expectation that my computer will start doing things of its own volition? No notification handler is a perfectly good answer.
I mostly agree, but there are a few notifications I really want, most particularly battery and device status notifications. If you have a mechanism for that, you might as well have a mechanism for whatever other notifications might be offered, but also an easy way to eliminate the ones you don't want.
A very useful feature of a modern messaging system is desktop integration, which iMessage (on macOS), whatsapp, Signal, Slack, among others support, so at the very least I'd want a desktop notification system to properly handle those notifications. Oh and also received emails. But that aside, this is Linux - do you not have any cronjobs? Like seriously any? Not even on other servers? Even if not from I'd like notifications from those, as well as other background tasks (eg when a large data set has finished downloading). To be fair, these use cases are largely covered by Chrome notifications, but these are use cases a notification system cam do a better job of covering.
For cronjobs, I haven’t needed to add any. I guess some must come built in in Ubuntu. Generally these are more like completely background maintenance tasks, to the point where I don’t care to know when they complete.
I could see the point of a task that is sort of “kick it off and it’ll let me know when it is done.” I actually have some tasks that I stick in LSF that could probably benefit from something like that, but in my case they are short-running enough that I just check back in a couple minutes.
I'm also using dunst (with qtile). I'm using it since many many years and love it and hate it. I cannot make it work to keep critical notifications on until I acknowledge them with a click. The rest works well. Always keep it simple.
I also remember there have been breaking changes, but I did not recall. I changed my config and got it to it
12 comments
[ 3.6 ms ] story [ 38.7 ms ] threadThe author mentioned some uncool breaking changes but didn’t elaborate.
Eh, I dunno. They make sense on a phone, which fundamentally is for contacting a person. The device is all about tasks which are not kicked off by a user. On a computer, though? What, is there some expectation that my computer will start doing things of its own volition? No notification handler is a perfectly good answer.
For cronjobs, I haven’t needed to add any. I guess some must come built in in Ubuntu. Generally these are more like completely background maintenance tasks, to the point where I don’t care to know when they complete.
I could see the point of a task that is sort of “kick it off and it’ll let me know when it is done.” I actually have some tasks that I stick in LSF that could probably benefit from something like that, but in my case they are short-running enough that I just check back in a couple minutes.
I'm also using dunst (with qtile). I'm using it since many many years and love it and hate it. I cannot make it work to keep critical notifications on until I acknowledge them with a click. The rest works well. Always keep it simple.
I also remember there have been breaking changes, but I did not recall. I changed my config and got it to it