[danneu]

I think notifications must stack to be usable.

My experience with websites that queue up notifications (the old thesixtyone.com) is that you sort of pause, sit there, and wait for them to finish up so you see what they say. A better experience is for them to stack up in the corner so you can read them, then click them away once you're done.

[wavded]

I had one more thought on this @danneu, I believe Growl stacks? I'm not a Mac user so I'm not sure if that is true. On Linux, Ubuntu libnotify does not, nor does Gnome Shell's notifications, two leading desktop environments for Linux and I've used both without having that desire for them to stack. Not saying stacking is not better, but I think its usable, and has its pros. E.g. how many should stack reasonably without being an issue, having a bunch stacked can crowd a portion of the screen. This lib may be able handle that in the future, but one of its strengths is that its easy for users to create vastly different themes partly because it doesn't stack. A relevant point of discussion however.

[wavded]

The idea of humane messages is that they require no user input to close. I do like stacking idea, maybe a future release. For now, setting the timeout to be shorter, or forcing new messages provides a workaround.

[gojomo]

I find messages that close themselves very inhumane; I can easily miss them if I look away or switch tabs, or they can disappear while I'm trying to understand them, with no way to bring them back.

My top feature request would be a 'stays up until dismissed or navigated away from' option.