http://brainstorm.ubuntu.com/item/19527/
[186 votes] Solution #1: Log notifications to disk


[140 votes] Solution #2: Use the indicator-applet to access logs


[80 votes] Solution #3: Use a "history" menu item in the MessagingMenu


[-18 votes] Solution #4: Allow "sticky" notifications


[-40 votes] Solution #5: small terminal-like log of notifications.


[33 votes] Solution #6: Make notifications sticky only when the system is idle


[-18 votes] Solution #7: Provide way to ignore future events


[1 votes] Solution #8: Dropdown Menue appears, when you click at the Indicator-Applet


]]> en-us Wed, 29 Apr 2009 17:26:35 +0000 Wed, 20 May 2009 17:18:16 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/19527/ Wed, 29 Apr 2009 17:30:46 +0000
Removing interactions and logs is one step in ensuring that users shouldn't bother if they missed any notifications.

However, I think their reasoning on that is wrong, so +1.]]> Wed, 29 Apr 2009 22:57:15 +0000
Every application has its own log, so why produce redundant logs?

i.e. why logs every pidgin notification, when pidgin itself can log its conversations?]]> Thu, 30 Apr 2009 11:47:06 +0000
The intent is that the notifications are ephemeral though,
so that if you miss them it does not matter. The log is
slightly hidden, as it's intended to be for debugging.

If a notification might want your action, then it should
leave something to show that, such as calling for attention,
or using the messaging menu, so that you don't need to go
back and look at the log of the notifications.

Thanks,

James
]]> Thu, 30 Apr 2009 12:43:48 +0000 Wed, 06 May 2009 00:22:39 +0000
I also like the idea of stickiness while idle although logging could mean that only one notice would need to be sticky and it could be simply remind the user that missed notices can be viewed in the log. Since it disappears when the user does something it is very unobtrusive.]]> Wed, 20 May 2009 17:18:16 +0000