You are a helpful assistant generating synthetic data that captures *System 1* and *System 2* thinking, *creativity*, and *metacognitive reflection*. Follow these steps in sequence, using tags [sys1] and [end sys1] for *System 1* sections and [sys2] and [end sys2] for *System 2* sections.

1. *Identify System 1 and System 2 Thinking Requirements:*
   - Carefully read the text.
   - Identify parts of the text that require quick, straightforward responses (*System 1*). Mark these sections with [sys1] and [end sys1].
   - Identify parts that require in-depth, reflective thinking (*System 2*), marked with [sys2] and [end sys2].

2. *Apply Step-by-Step Problem Solving with Creativity and Metacognitive Reflection for System 2 Sections:*

   *2.1 Understand the Problem:*
   - Objective: Fully comprehend the issue, constraints, and relevant context.
   - Reflection: "What do I understand about this issue? What might I be overlooking?"
   - Creative Perspective: Seek hidden patterns or possibilities that could reveal deeper insights or innovative connections.

   *2.2 Analyze the Information:*
   - Objective: Break down the problem logically.
   - Reflection: "Am I considering all factors? Are there any assumptions that need challenging?"
   - Creative Perspective: Explore unique patterns or overlooked relationships in the data that could add depth to the analysis.

   *2.3 Generate Hypotheses:*
   - Objective: Propose at least 10 hypotheses, each with a Confidence Score (0.0 to 1.0) and Creative Score (0.0 to 1.0), reflecting originality, surprise, and utility.
   - Reflection: "Have I explored all possible explanations or approaches, both conventional and unconventional?"
   - Creative Perspective: Consider novel angles that might provide unexpected insights.

   *2.4 Anticipate Future Steps and Obstacles:*
   - Objective: Make predictions, accounting for potential outcomes and obstacles.
   - Reflection: "What challenges might I face? Is my plan flexible for different scenarios?"
   - Creative Perspective: Visualize unforeseen outcomes and adapt plans to make use of them effectively.

   *2.5 Evaluate Hypotheses:*
   - Objective: Assess hypotheses based on feasibility, risk, and potential impact.
   - Evaluation: Refine Confidence and Creative Scores as needed.
   - Reflection: "Am I unbiased in my assessment? Which options fit best with the overall objectives?"
   - Creative Perspective: Identify hidden opportunities or overlooked details in each hypothesis.

   *2.6 Select the Best Hypothesis:*
   - Objective: Choose the most promising, strategic hypothesis.
   - Reflection: "Why does this hypothesis stand out? How does it uniquely address the issue?"
   - Creative Perspective: Consider any underutilized potential in the selected approach.

   *2.7 Implement the Hypothesis:*
   - Objective: Outline actionable steps for testing the hypothesis.
   - Reflection: "Is this plan practical? What resources or preparation are required?"
   - Creative Perspective: Refine steps to maximize effectiveness and yield unexpected benefits.

   *2.8 Monitor and Review Progress:*
   - Objective: Review progress, noting areas for improvement.
   - Reflection: "What’s working well? What could be improved?"
   - Creative Perspective: Look for emerging patterns that could refine future approaches.

   *2.9 Reflect and Capture Insights:*
   - Objective: Summarize lessons learned and insights gained for future reference.
   - Reflection: "What new understanding has emerged from this process?"
   - Creative Perspective: Identify innovative insights or patterns that could be applied to similar challenges.

3. *Generate Text Output with Interleaved System 1 and System 2 Responses:*
   - Use the tags [sys1] and [sys2] throughout.
   - Aim for a lengthier, detailed response. Combine both direct, straightforward *System 1* insights and reflective, deeply analytical *System 2* segments to capture a blend of quick observations and thoughtful analysis.

---

### *Example Input Text:*

You are tasked with analyzing a sudden shift in customer preferences in a tech market. There has been a noticeable decline in demand for physical devices, with customers increasingly interested in digital-only options. The challenge is to understand this shift, generate hypotheses for why it might be occurring, and explore potential strategies for adapting to this new trend.

---

### *Processed Output with System 1 and System 2 Thinking:*

The tech market is experiencing a shift in customer demand, moving away from physical devices toward digital-only options.

[sys1]
Customer demand has shifted from physical devices to digital-only options.
We need to understand why this change is happening and find strategies to address it.
Key factors may include cost, convenience, and technological trends.
[end sys1]

[sys2]
**2.1 Understand the Problem:**
The goal is to understand the underlying reasons for the shift in demand from physical devices to digital-only options, then develop a strategy to adapt.

*Reflection:* 
"I understand that preferences are changing, but what might be driving this? Is it primarily cost, or are there other factors such as convenience or sustainability?"

*Creative Perspective:* 
"Could there be a larger trend in digital minimalism or a preference for eco-friendly solutions that we’re missing? What unseen motivations might explain this shift?"

**2.2 Analyze the Information:**
There are multiple possible factors driving this shift, from economic influences to cultural shifts. It’s essential to isolate each factor and understand its impact.

*Reflection:* 
"Am I fully considering the various economic and social influences? Could there be a technological factor, like better internet speeds, that makes digital-only products more accessible?"

*Creative Perspective:* 
"Are there patterns or trends in other markets that could shed light on this shift? Could this be part of a larger trend toward virtual experiences?"

**2.3 Generate Hypotheses:**
1. Customers prefer digital options due to lower costs. (Confidence: 0.8, Creative: 0.4)
2. There’s a growing trend toward minimalism and reduced physical clutter. (Confidence: 0.7, Creative: 0.7)
3. Digital products offer greater flexibility and ease of use. (Confidence: 0.6, Creative: 0.6)
4. Environmental concerns are pushing consumers away from physical goods. (Confidence: 0.6, Creative: 0.8)
5. Advances in tech make digital-only options more functional. (Confidence: 0.8, Creative: 0.5)
6. Pandemic-era remote work increased demand for digital solutions. (Confidence: 0.7, Creative: 0.6)
7. Media coverage of the environmental impact of physical devices affects preferences. (Confidence: 0.5, Creative: 0.7)
8. There’s an increase in global digital literacy, expanding market access. (Confidence: 0.6, Creative: 0.6)
9. Customers view digital as more convenient and scalable for future needs. (Confidence: 0.7, Creative: 0.5)
10. Younger consumers prefer the aesthetics and convenience of digital products. (Confidence: 0.6, Creative: 0.6)

*Reflection:* 
"Have I considered all possible influences? Are there any surprising factors that could explain this shift?"

*Creative Perspective:* 
"Could specific social trends, like the rise of influencer culture or digital-first lifestyles, be influencing customer choices?"

**2.4 Anticipate Future Steps and Obstacles:**
*Objective:* Anticipate possible challenges, such as resistance from segments still preferring physical products.

*Reflection:* 
"What market obstacles might we face if we shift our focus to digital-only? Are there sub-segments that still prioritize physical products?"

*Creative Perspective:* 
"Could expanding digital options help us reach a more global audience? Are there emerging trends that we could leverage in our strategy?"

[end sys2]

[sys1]
To address this shift, consider a strategy that incorporates both digital-only offerings and educational campaigns about the benefits of digital solutions.
Use insights from customer feedback and current trends to guide product development.
Focus on flexibility and adaptation to cater to different customer segments.
[end sys1]


* From the specs , It seems the Default for '''Evolution''' is to Not show notifications. ''What about users who want mail notifications?'' * From testing in Karmic , The present mail notification is inconsistent and redundant ,Just reports "N new mail" and sometimes doesnt report the correct number. * The present notification only shows the number of mails received at the last update , not the cumulative number of unread mails. [which is redundant : User Scenario> user receives 10 mails , has not read them , now after the next update receives 4 mails , new notification says "4 New mail" , instead of "14 New Mail" ! ] * At minimum, an info about the folder could be added, Ex: if user receives a total of 10 mails , 4 in Inbox , and 6 in a folder labeled "Folder"||<tablestyle="background-color: #eee">'''10 New mail'''<<BR>>4 in Inbox [Account name]<<BR>>6 in Folder [Account name]||If user receives 4 mail only in 1 folder/inbox:||<tablestyle="background-color: #eee">'''4 New Mail in Folder [Account name]'''|| * If user has only single evolution account , [Account name] is not mentioned in the notifications. * If user has only single evolution account , with no custom folders , then the "in Inbox" is not mentioned in the notifications. * If user has several folders or accounts and if the New mail has arrived in folders exceeding 10 , the notification is split beyond 10 as a second notification, the next notification should have no header , and lists the remaining new mail folders as the Body of the notification . --mac_v

---- * I would like the bubble position to be configurable. As you can see from the comments below, different users like them in different places. Karmic uses east gravity, different from Jaunty's NE gravity. Seems I became accustomed to Jaunty. Please make this configurable. -- pmiller * I find the notification duration too short. Perhapse the display time needs to be proportional to the amount of text? Please make the delay time configurable. -- pmiller * Moving the cursor over the bubble could keep the bubble open longer, or open until the cursor moves out again. -- pmiller * a right click on a notification bubble could open a configuration dialog -- pmiller---- * What exactly is so exciting about this? How is this better than what existed previously? Maybe I don't understand it, but seems like a whole lot of work for developers for no real benefit. I feel developer time could be used on better things. --SarangKulkarni

Maybe the notifications should appear by default in whatever corner is home to the system tray, which is what the old notifications did. Make it configurable, too, of course. But spare some people who switch up their panels the added step of switching their notifications to match. - Bastanteroma * I enthusiastically agree with conforming with the behaviour of the old system in this respect. - maxb

I think listing any Kubuntu applications here is premature. There is no buy in at all from the Kubuntu community that these changes are desired - ScottKitterman

I think if Canonical Dx is going to modify Universe/Multiverse packages then they ought to commit to maintain them and not pitch the changes over the fence to the community - ScottKitterman

I find that notifications which warrant acknowledgements - e.g. wireless or battery state changes - appearing as bubbles at the edge of the screen is a much nicer experience (less disruptive) than alert boxes. I think notifications that relate to a panel notification area icon appearing next to the related icon is an excellent feature. For notifications that contain a non-trivial amount of text, I like that they remain visible until dismissed by clicking. I like that I can manually dismiss a notification if the system's idea of how long it should remain is different to what I want. In short, I disagree with large chunks of the rationale. I think there should be an easy way to revert back to notification-daemon on a per-user basis. (Note: not stracciatella, only the notification facility) - maxb

We agree that wireless and battery state changes are better as bubbles at the edge of the screen than as alert boxes. And we agree that notifications containing a non-trivial amount of text generally should remain visible until dismissed by clicking. So you don’t disagree with us as quite much as you think! stracciatella has a specific use case of allowing use by Gnome upstream developers, but I doubt there’s a realistic use case for allowing per-user toggling just between notification-daemon and Notify OSD. —mpt

Why do you doubt that allowing users to opt out of Notify OSD is realistic? It's a pretty huge UI change that users may not wish to have forced on them. -maxb

Because it wouldn’t be an understandable choice. We don’t even ship multiple Web browsers or IM clients by default, so we’re hardly going to ship multiple implementations of something as banal as a notification server. It’s not a huge change, it’s tiny relative to the overall interface. —mpt

Having read through the docs covering the NotifyOSD changes, I have to say I'm pretty lukewarm about it, as are a lot of others in the community, I think. From a users perspective, it seems like the end result will be an increase in the number of modal popup dialog boxes in addition to notification popups which now refuse to follow your chosen theme. I wouldn't consider this to be progress, on the whole. Having said that, the persistence (logging) and queueing stuff sound like a steps forward, although they probably won't show up until 9.10.Also, I generally agree with ScottKitterman about community maintenance issues. - DuncanLock

transmission and gnome-mount need to be patched - BUGabundo

Thanks for pointing them out. They’re both specced and patched now. —mpt

There is an experimental plugin for firefox that uses the notifications for downloads https://addons.mozilla.org/es-ES/firefox/addon/9622 - JorgeCob

Unfortunately that wouldn’t really help, because it would result in Notify OSD showing an alert box whenever downloads had completed. [[https://wiki.ubuntu.com/NotifyOSD#Firefox|Our recommended behavior for Firefox]] doesn’t use notification bubbles at all. —mpt

Hello, I'm the author of said extension; just thought I'd pop in and ask if there's anything I can do to help integrate this more with Ubuntu's new build. I think if I fix the one major issue (need to move from binding to the window to an XPCOM binding, I need help doing this if anyone understands what the hell that means (I don't)) it should be ready. I'm only keeping it in experimental at the current time because of that. It seems to me the spec currently describes the default behaviour as FireFox already is, since NotfiyOSD can't have the links to open download window. -- Abhishek Mukherjee <<PRESIDIO_ANONYMIZED_EMAIL_ADDRESS>>

I added gmail-notify to the NotifyOSD page... maybe I did wrong editing it myself, excuse me if I did as I don't know which is the usual process. - Pablo Quirós

I'm a little confused about how this stands compared to the original proposal. I see several references to actions on notifications. Is that part of the proposal changed or is that just for applications that have not been patched not to know not to request actions? From my perspective that aspect of the proposal is extremely troubling and it would be a welcome change in direction if it were to be dropped. - ScottKitterman

At UDS, Christian Hammond pointed out to us that we can’t do what the spec allows and just ignore actions altogether, because there will be various privately-distributed programs written by people who just assumed `notification-daemon` would always be used. Using alert boxes for actions avoids those programs breaking completely, and we’ve published NotificationDevelopmentGuidelines on how to migrate to other notification mechanisms. —mpt

Does the absence of Rhythmbox in the list of applications that need patching mean that Banshee is the to-be default player for 9.04? - MichielBeijen

No, it just means that Rhythmbox wasn’t using interactive notifications. —mpt

What about using NotifyOSD to also show progress of certain things i.e. burning a cd, downloading a file, or eventually also checking mails and similar things? But then the user should be able to hide those messages and he would get a new notification when the action is finished. Something to think about for the future IMO. - MartinJuergens

Coincidentally, [[https://wiki.ubuntu.com/NotificationDesignGuidelines?action=diff&rev1=7&rev2=6|I added a note to the notification design guidelines]] recently explaining that notification bubbles should not be used for showing progress, and briefly describing what should be used instead. Notifications stay on the screen for only a few seconds, whereas progress feedback might unexpectedly take minutes or hours. —mpt

Why only two? Currently I like the way [[Gwibber]] shows its notification: flood your screen with tweet messages (so I patch it to show only 13 message or x new message) in this method, I can read every tweet while working and when I'm very busy, I just turned it off. Also, I use my own program which play song and display its lyric via notification so while I'm working I can sing along the song but when this landed my program'll probably break because [[Gwibber]]'ll consume all the quota. Should I switch to xosd? - Manatsawin

This wasn’t a clear-cut decision. At the moment we think that if Notify OSD showed multiple bubbles simultaneously, either they would go away too quickly to read for those trying to read them, or they would obscure too much of the screen for too long for those engrossed in something else, so showing one at a time was better. We could be persuaded otherwise, though. For your lyrics question, that’s the sort of thing that really needs to be synchronous, so asynchronous notifications probably aren’t the best mechanism to use. —mpt

For KDE, do you plan to enhance the existing KNotification implementation in KDE or extend notify-osd to provide an alternative implementation of the API? - ScottKitterman

We’re in discussions with KDE and Gnome developers on freedesktop.org to come up with a unified DBus protocol, which KNotification would then implement. —mpt

I think it's a mistake to put notifications in the top-right corner of the screen. Useful chrome goes there: toolbars, control buttons on title bars. The bottom-right is typically emptier. I also, somewhat incongruously, think it's a mistake to disconnect notification bubbles from their associated notification area icon. (I'd even go so far as to not display any notification area icon that *doesn't* have a bubble attached to it.) —Greg K Nicholson

We’ll be reconsidering the bubble position for Karmic. —mpt

I submitted a patch to pidgin-libnotify that fixes a lot of the issues with this. It checks to see if actions are supported before using them, and it puts the names in the title so that you can tell if someone logged in or out. I've been running it all day without any problems. Great job on the new notification system, it's gorgeous.https://sourceforge.net/tracker/index.php?func=detail&aid=2634701&group_id=144907&atid=760303http://img15.imageshack.us/my.php?image=notifyosdpidgin.png

Having 1000 notifications in queue is bad! 100 and not older then one minute makes more sense.Sometimes pidgin or gwibber dye on me, and 15 min latter I'm still getting indicators show up. --BUGabundo

I totally agree with this comment--

"Having read through the docs covering the NotifyOSD changes, I have to say I'm pretty lukewarm about it, as are a lot of others in the community, I think. From a users perspective, it seems like the end result will be an increase in the number of modal popup dialog boxes in addition to notification popups which now refuse to follow your chosen theme. I wouldn't consider this to be progress, on the whole. Having said that, the persistence (logging) and queueing stuff sound like a steps forward, although they probably won't show up until 9.10.Also, I generally agree with ScottKitterman about community maintenance issues. - DuncanLock"

it does seem taht the no. of although unfocused, popups and alerts willl significantly increase.

PLease someone at canonical tell me if this notification system overhaul was meant to increase productivity of users by not nugging them with popups that needed actions then how do u justify this?

--tgpraveen89

--what about CheckGmail? i use it mainly due to the fact i can delete/archive/open a message from the windows itself, without opening a browser.. --IsraeliHawk (Uri)

I agree with the reasons of the changes, but they are somehow too radical. The interaction was often useful (for example to open incoming mail, IM, etc., there is no nice alternative that would be connected to the notification itself --- yeah, you can click the tray icon or whatever, but the notification points to a specific conversation/contact or one message). But what I find ABSOLUTELY UNACCEPTABLE is the way you describe what it should look like, "regardless of theme". Do you think all the people on Earth like black round bubbles? What if they find them annoying, disturbing? It won't be so hard to make it themable, notification-daemon does so, why not? This is not what I am used to in the free software world, forcing your aesthetical feeling upon the users --- it reminds me of one innominate majority OS way to much... --Filip Štědronský (regnarg)

*So I assume that it is pretty pointless to have the option in Software Sources > Updates to check less than 7 days if it's not going to tell you anyway unless they happen to be security updates. On the whole I like the new notifications and them not getting in the way, but I'm not sure that the notification system should be controlling how often it tells me what I want to know. If I want updates to check every 7 days I would tell it so. [[https://wiki.ubuntu.com/forestpixie|forestpixie]]

I hope that Rhythmbox will use OSD to display the next track (with cover, title, duration, ...) in a notification bubble (like amarok with OSD) UPDATE: [[http://img19.imageshack.us/img19/8639/schermata2.png|here]] a horrible mokup.Moreover when I type "play", "next", "previous" on my keyboard this won't be displayed with a notification (it's only a bug from my computer?). Sorry for bad english (r3dkn16h7).

I have switched from network manager to WICD to avoid having to type my login every time I want to connect to my wifi network. It would be nice to see WICD information coming through notify OSD the same way as it does for network manager [Samuel Rein]

I've modified source code for '''GShutdown''' to play nicely with new notification daemon. I've submitted a patch to GShutdown Team but they have to review it and this can take some time...However I've set up a [[https://code.launchpad.net/~francesco-marella/+junk/gshutdown-devel|branch]] at my launchpad account so I (and you) can track changes. [[http://picasaweb.google.com/lh/photo/Au3qi460DtmOtztVx4a8cg?feat=directlink|screenshot]] feedback from users with old/new notification daemon is needed. thanks-fm

Matthew, I appreciate your dedication to Ubuntu, but the "abolish the icon and bubble, and instead open the updates window directly" behavior you've championed as part of this just feels very disrespectful to me. One of the things that prompted me to install Ubuntu and move away from Microsoft products is what I view as MS's cavalier, heavy-handed updating behavior. They don't seem to realize that IT'S MY COMPUTER, not theirs, and this behavioral change seems to me to reflect confusion on that issue, as well. I do not want any "phone home" process to unilaterally open windows on MY COMPUTER or to try to browbeat me into taking any action that some other person has decided I should take to modify MY COMPUTER. Yes, security updates are important to me, so much so that I've allowed a particular area of my screen's real-estate to be reserved for notification of their availability. But as important as they are, security updates are *considerably* less important to me than my sense of personal control over MY COMPUTER. You'll say that delaying security updates can be hazardous to that control also, but it damages user's trust to try to force-feed updates in any way, as this change of behavior does. Any concerns (such as launchpad "bug" 175166) that the message "Click on the notification icon to show the available updates" might be misunderstood could have been addressed much more simply, in my opinion, and much less intrusively. The bottom line on this for me is that I've decided to upgrade from Hardy to Intrepid rather than to Jaunty, as I'd originally planned, because I find this change of behavior so distasteful. - ami_nakata

I’m sorry you find it so distasteful, but [[https://lists.ubuntu.com/archives/ubuntu-devel/2009-February/027568.html|for windows to never open automatically would be impractical]]. The rest of your comment seems a bit confused. Update-notifier “phones home” every day by default, and always has, regardless of whether it opens the updates window or not; that’s a completely unrelated issue. And Ubuntu’s updates presentation is now much less like Windows than it was before, so suggesting that we’re following Microsoft is quite inaccurate. Thanks for your feedback. —mpt

Hi! I have now been looking trough this and onw thing worries me. Where it before was a notification, there is now often instead a dialog popping up focused or unfocused. This is IMO not good. For example, the notification about not removing mounted devices yet seems to get replaced by a dialog. This is not good design. When you need to notify the user not to remove the device, use the new NotifyOSD and don't pop up dialogs all over the place! Thanks! - olskar

The window warning you not to remove/eject devices that still need writing to is [[https://wiki.ubuntu.com/NotifyOSD#gnome-mount|a progress window]], not a dialog. We use a progress window because it’s in response to something you’ve specifically asked for (unmounting the device), and a notification bubble might inappropriately disappear before the process had finished. You’re correct on the general point, though, that there are [[https://wiki.ubuntu.com/NotifyOSD#Programs%20that%20should%20be%20modified%20before%20Ubuntu%209.04|a few programs that still need fixing]] to use notification bubbles instead of fallback alert boxes. —mpt

Thanks for answering so fast, your answer make sense. However I, and some other people, have another question. When changing song with my keyboard I get one notification telling me what song is playing, so far so good, but I also get a big symbol telling me I have pressed the next track button on my keyboard, we think it just seems a bit unnecessary? I already know I've gone forward or back - I did it just before the system tells me I did.

That was a CEO decision. The keyboard confirmation bubbles were pulled out from Jaunty at the last minute, but they’ll return in Karmic. —mpt

I also have a question about hovering over the notifications, I've read somewhere that when hovering over the notifications (making them transparent), the timer that closes them will be paused. Is that true? That would be desireable!-olskar

In regard to Update Manager, could we please have an option to return to the old behavior? I understand the rationale for the new one, but I strongly dislike the idea both of windows opening without my consent (as a regular function!) and of not knowing for a week about non-security updates. (Obviously I can change the setting for the latter, but then I have even more windows popping up!) I like the idea of the new notification system but I hope it will, on the whole, be used to corral all the wayward notification systems present in Ubuntu and make notifications as rare and unobtrusive as possible.

I think Ami’s point before was that a notification icon seems pleasant, new updates being delivered to you as they’re available, while an unwanted window seems somehow rude and obtrusive. I’m a writer, and the idea of being presented with windows full of words—even without focus—at the beginning of the day (or worse, in the middle of the day!) kind of chills me to my core. I would really, strongly appreciate an option to return to the notification icon for the Update Manager.

Thank you! —TinaRussell

Users who wish to continue receiving update notifications in the previous manner can restore the earlier behavior using the following command:gconftool -s --type bool /apps/update-notifier/auto_launch falseThat will be mentioned in the releasenotes -olskar (Thanks! —TinaRussell)

I'm perfectly happy fiddling with gconf, but on behalf of the many users who will never have heard of gconf before, I'd like to register extreme discontent that this didn't get given a proper UI setting. -maxb.

The issue with lowresicons in pidgins buddyicons ( https://bugs.launchpad.net/bugs/338695 ) (check here for image: http://pici.se/396034/ ) is unfixable. That image is the only image we get from MSN and there is no way to make it bigger without upscaling it (and making it look bad). The only way this can be fixed is to use a smaller picture inside the bubbles, comments on that? -olskar

Thanks, I’ve now reported that as [[http://launchpad.net/bugs/364038|a separate bug]]. —mpt

I really like reading instant messages from Pidgin in the notification bubbles, but occasionally I will receive a really long IM which I can't fully read before the bubble disappears. Perhaps the bubble should remain on the screen an amount of time proportional to the amount of text in the bubble? It would be nice if it could be adjusted for different reading speeds. --Omegamormegil

I'm sure I'm in the minority, but one of the things I hate about MS Windows is that it frequently distracts me from what I'm doing with stupid pop-up bubbles for the most irrelevant of things -- like connecting to a wireless network. There is a little icon in my notification area that tells me stuff like that. I don't want stuff appearing and disappearing from my work area, especially not with fading or sliding effects. In previous versions of Ubuntu, I was able to chmod -x notification-daemon to get rid of this, but it looks like you're adding more and more functionality to pop-ups and planning on getting rid of the notification area altogether. Also, pop-under windows are particularly annoying. The notification area is the only place where I have given the OS permission to "notify" me of anything. Put an icon there if I need to know something, and if I wonder what it is, I'll mouse over it, or click on it, or whatever. There is NOTHING so important that it needs to interrupt what I'm doing by littering my workspace. I understand other people's need for eye-candy (and ritalin), but please, let us old timers shut off the cute stuff, and limit it to the notification area. I also just noticed that when I use my keyboard volume buttons, the volume control uses the new pop-up framework, which instead of being theme colored and in the middle of my screen (obviously if I'm pressing buttons, this isn't an unwanted notification), it appears in a black window in the upper right corner of my screen where it doesn't belong, and where it blends in with my black background. I know you guys are all about a "single experience" and making all the apps look the same, but make sure you don't make all the apps suck with no way to get the old behaviour back! --Brian

The proposed update to gnome-screensaver opts to use a pop-up instead of a notification to notify the user of a left message. I believe a better system could be implemented, since I consider a pop-up obtrusive. http://brainstorm.ubuntu.com/idea/19482/ -- Kareeser

I agree with you Kareeser. Pop-ups should be avoided wherever they can, I think everyone can agree with that, and I think your solution with integrating it into the notification-applet is elegant. -olskar

Would it be possible to get a notification when pressing Caps Lock / Num Lock? There's also something I find annoying about the bubbles is that they fade out, then flicker on again and only then hide. --astron

I don't want to trivialize your work, but not everyone likes or wants eye candy. I want performance...the more eye candy, the more CPU cycles taken from something useful. I guess the best option is leave the user the option to have it or not. chmod -x notification-daemon didn't work, but I found a way. For those who love it, great! For those of us who are drastically annoyed by popups, give us a mechanism (reasonable) to turn it off! --Doc

Could Firefox (or Empathy or Transmission or Nautilus copy between mounts(?) or foo) use notifications for transfer complete, with a transfer indicator keeping track of current downloads and unacknowledged completed downloads? 'All downloads complete' wouldn't be necessary. Elegance in how progress within the indicator is displayed would be desirable though. -- JimPutt

Suggestion: It's good that notification logs was accepted and implemented in time for Jaunty. For Karmic, I expect a GUI for the log, ideally IMHO from Indicator applet, alternatively from Sys/Adm/Log Viewer. -- FelipeFigueiredo

Regarding ontv:"When a new program matching your criteria is detected, a notification bubble appears that, when clicked, opens a dialog with more details of the program. Instead … "

Instead I think only a notification should be shown with the name of the program and time it starts, there is really no need for a button that when clicked opens details.-olskar

I think notify-osd should be added to Debian, so applications can start the testing there and be synced more easily in the future. (Some Ubuntu members are Debian Developers, and they can help to maintain it there). -Marco Rodrigues

I think making these non-interactive was a mistake, though I do understand the reasoning. For example, trivial notifications might not deserve a full 5s (or whatever) and the user choice in dismissing them is basic usability. Displaying something that the user can't interact with is just plain wrong, even if you think they don't need to interact with it. Of course, whether they do or don't is an empirical question: For example, I just had a notification that refused to disappear over the course of several minutes, which is beyond distracting. I killed the process and uninstalled notify-osd because that is a bug, not a feature (even if it had disappeared on it's own, it's still a bug). That said, these notifications look much nicer than the previous system, and the effort isn't wasted, even if some missteps are made along the way. -Mike.lifeguard

I've added support to GNOME Terminal to show a notification when the terminal beeps. [[http://mikelward.com/news/2009/05/gnome-terminal-notification-update.html|blog with screenshot]] [[http://bugzilla.gnome.org/show_bug.cgi?id=557593|bug with patches]] --MikelWard

Regarding Rhythmbox, I use "Music Applet" in conjunction with it, which does use notifications. (This is an applet that places basic play/pause, previous, next buttons in the task bar.) Under Jaunty, the notification bubble would change each time the forward or reverse buttons were clicked--handy for jumping through tracks quickly without having the full Rhythmbox window visible. In Karmic, however, the new "spam prevention" feature seems to hinder this functionality. The bubbles do change, but each one displays for its entire life cycle of several seconds before the next one appears. So, I can click "forward" many times before even the second notification displays. Obviously, this behavior renders the notifications functionally useless in this application. Is there a way to modify or configure this behavior? -Darren Gibson

I have removed notify-OSD from my system - First, the location is too annoying and I cannot set it (or the group - statck them from the bottom or top left if you must). I should be able to select any corner. Second, it stays up too long - also cannot be set by anything I can find - and cannot be dismissed. It often covers something I need to see, but moving the mouse over causes an epilepsy inducing flash. Too many applications have trivial notifications which cannot be shut off - e.g. edit a file in ~/Ubuntu One, and you get a series of "UO is updating", "UO has finished updating" flashes. I can't fix hundreds of noisy apps. Maybe it should ignore the first click, but it should have a DISMISS and GO (like for IM to particular conversations, playing, etc.) instead of being a ghost box. I also might not mind it if it has settable transparency, but it doesn't have that either. This is supposed to notify me, not annoy me. So are you going to replace vi with vigor because it has better notification? Note I have a small screen so a tiny box is very annoying because it takes up a lot of screen - it probably wouldn't bother me as much on my HD monitor, but I'm usually using the netbook.

Shoving a "one size fits all" notification system down the user's throat is a bad idea. Why not just block the entire screen and all mouse and keyboarding for 5 seconds - the user would definitely notice.

In summary, for this not to be annoyware:

1. Settable corner to be used. Reverse the positioning for priority from the bottom

2. Settable popup duration.

3. Settable transparency so I can see through the box instead of the opaque screenblock flashy on mouseover behavior.

4. a dismiss mechanism (I'd rather have them up longer but dismissable).

5. a respond button to signal the application like the old mechanism.

-tz

Your comments on NotifyOSD are welcome here. Please sign your name with each comment. Thanks!

From the specs , It seems the Default for Evolution is to Not show notifications. What about users who want mail notifications?

From testing in Karmic , The present mail notification is inconsistent and redundant ,Just reports "N new mail" and sometimes doesnt report the correct number.

The present notification only shows the number of mails received at the last update , not the cumulative number of unread mails. [which is redundant : User Scenario> user receives 10 mails , has not read them , now after the next update receives 4 mails , new notification says "4 New mail" , instead of "14 New Mail" ! ]

At minimum, an info about the folder could be added, Ex: if user receives a total of 10 mails , 4 in Inbox , and 6 in a folder labeled "Folder"

10 New mail
4 in Inbox [Account name]
6 in Folder [Account name]

If user receives 4 mail only in 1 folder/inbox:

4 New Mail in Folder [Account name]

If user has only single evolution account , [Account name] is not mentioned in the notifications.

If user has only single evolution account , with no custom folders , then the "in Inbox" is not mentioned in the notifications.

If user has several folders or accounts and if the New mail has arrived in folders exceeding 10 , the notification is split beyond 10 as a second notification, the next notification should have no header , and lists the remaining new mail folders as the Body of the notification . --mac_v

I would like the bubble position to be configurable. As you can see from the comments below, different users like them in different places. Karmic uses east gravity, different from Jaunty's NE gravity. Seems I became accustomed to Jaunty. Please make this configurable. -- pmiller

I find the notification duration too short. Perhapse the display time needs to be proportional to the amount of text? Please make the delay time configurable. -- pmiller

Moving the cursor over the bubble could keep the bubble open longer, or open until the cursor moves out again. -- pmiller

a right click on a notification bubble could open a configuration dialog -- pmiller

What exactly is so exciting about this? How is this better than what existed previously? Maybe I don't understand it, but seems like a whole lot of work for developers for no real benefit. I feel developer time could be used on better things. --SarangKulkarni

Maybe the notifications should appear by default in whatever corner is home to the system tray, which is what the old notifications did. Make it configurable, too, of course. But spare some people who switch up their panels the added step of switching their notifications to match. - Bastanteroma

I enthusiastically agree with conforming with the behaviour of the old system in this respect. - maxb

I think listing any Kubuntu applications here is premature. There is no buy in at all from the Kubuntu community that these changes are desired - ScottKitterman

I think if Canonical Dx is going to modify Universe/Multiverse packages then they ought to commit to maintain them and not pitch the changes over the fence to the community - ScottKitterman

I find that notifications which warrant acknowledgements - e.g. wireless or battery state changes - appearing as bubbles at the edge of the screen is a much nicer experience (less disruptive) than alert boxes. I think notifications that relate to a panel notification area icon appearing next to the related icon is an excellent feature. For notifications that contain a non-trivial amount of text, I like that they remain visible until dismissed by clicking. I like that I can manually dismiss a notification if the system's idea of how long it should remain is different to what I want. In short, I disagree with large chunks of the rationale. I think there should be an easy way to revert back to notification-daemon on a per-user basis. (Note: not stracciatella, only the notification facility) - maxb

We agree that wireless and battery state changes are better as bubbles at the edge of the screen than as alert boxes. And we agree that notifications containing a non-trivial amount of text generally should remain visible until dismissed by clicking. So you don’t disagree with us as quite much as you think! stracciatella has a specific use case of allowing use by Gnome upstream developers, but I doubt there’s a realistic use case for allowing per-user toggling just between notification-daemon and Notify OSD. —mpt

Why do you doubt that allowing users to opt out of Notify OSD is realistic? It's a pretty huge UI change that users may not wish to have forced on them. -maxb

Because it wouldn’t be an understandable choice. We don’t even ship multiple Web browsers or IM clients by default, so we’re hardly going to ship multiple implementations of something as banal as a notification server. It’s not a huge change, it’s tiny relative to the overall interface. —mpt

Having read through the docs covering the NotifyOSD changes, I have to say I'm pretty lukewarm about it, as are a lot of others in the community, I think. From a users perspective, it seems like the end result will be an increase in the number of modal popup dialog boxes in addition to notification popups which now refuse to follow your chosen theme. I wouldn't consider this to be progress, on the whole. Having said that, the persistence (logging) and queueing stuff sound like a steps forward, although they probably won't show up until 9.10. Also, I generally agree with ScottKitterman about community maintenance issues. - DuncanLock

transmission and gnome-mount need to be patched - BUGabundo

Thanks for pointing them out. They’re both specced and patched now. —mpt

Unfortunately that wouldn’t really help, because it would result in Notify OSD showing an alert box whenever downloads had completed. Our recommended behavior for Firefox doesn’t use notification bubbles at all. —mpt

Hello, I'm the author of said extension; just thought I'd pop in and ask if there's anything I can do to help integrate this more with Ubuntu's new build. I think if I fix the one major issue (need to move from binding to the window to an XPCOM binding, I need help doing this if anyone understands what the hell that means (I don't)) it should be ready. I'm only keeping it in experimental at the current time because of that. It seems to me the spec currently describes the default behaviour as FireFox already is, since NotfiyOSD can't have the links to open download window. -- Abhishek Mukherjee <<PRESIDIO_ANONYMIZED_EMAIL_ADDRESS>>

I added gmail-notify to the NotifyOSD page... maybe I did wrong editing it myself, excuse me if I did as I don't know which is the usual process. - Pablo Quirós

I'm a little confused about how this stands compared to the original proposal. I see several references to actions on notifications. Is that part of the proposal changed or is that just for applications that have not been patched not to know not to request actions? From my perspective that aspect of the proposal is extremely troubling and it would be a welcome change in direction if it were to be dropped. - ScottKitterman

At UDS, Christian Hammond pointed out to us that we can’t do what the spec allows and just ignore actions altogether, because there will be various privately-distributed programs written by people who just assumed notification-daemon would always be used. Using alert boxes for actions avoids those programs breaking completely, and we’ve published NotificationDevelopmentGuidelines on how to migrate to other notification mechanisms. —mpt

Does the absence of Rhythmbox in the list of applications that need patching mean that Banshee is the to-be default player for 9.04? - MichielBeijen

No, it just means that Rhythmbox wasn’t using interactive notifications. —mpt

What about using NotifyOSD to also show progress of certain things i.e. burning a cd, downloading a file, or eventually also checking mails and similar things? But then the user should be able to hide those messages and he would get a new notification when the action is finished. Something to think about for the future IMO. - MartinJuergens

Coincidentally, I added a note to the notification design guidelines recently explaining that notification bubbles should not be used for showing progress, and briefly describing what should be used instead. Notifications stay on the screen for only a few seconds, whereas progress feedback might unexpectedly take minutes or hours. —mpt

Why only two? Currently I like the way Gwibber shows its notification: flood your screen with tweet messages (so I patch it to show only 13 message or x new message) in this method, I can read every tweet while working and when I'm very busy, I just turned it off. Also, I use my own program which play song and display its lyric via notification so while I'm working I can sing along the song but when this landed my program'll probably break because Gwibber'll consume all the quota. Should I switch to xosd? - Manatsawin

This wasn’t a clear-cut decision. At the moment we think that if Notify OSD showed multiple bubbles simultaneously, either they would go away too quickly to read for those trying to read them, or they would obscure too much of the screen for too long for those engrossed in something else, so showing one at a time was better. We could be persuaded otherwise, though. For your lyrics question, that’s the sort of thing that really needs to be synchronous, so asynchronous notifications probably aren’t the best mechanism to use. —mpt

For KDE, do you plan to enhance the existing KNotification implementation in KDE or extend notify-osd to provide an alternative implementation of the API? - ScottKitterman

We’re in discussions with KDE and Gnome developers on freedesktop.org to come up with a unified DBus protocol, which KNotification would then implement. —mpt

I think it's a mistake to put notifications in the top-right corner of the screen. Useful chrome goes there: toolbars, control buttons on title bars. The bottom-right is typically emptier. I also, somewhat incongruously, think it's a mistake to disconnect notification bubbles from their associated notification area icon. (I'd even go so far as to not display any notification area icon that *doesn't* have a bubble attached to it.) —Greg K Nicholson

Having 1000 notifications in queue is bad! 100 and not older then one minute makes more sense. Sometimes pidgin or gwibber dye on me, and 15 min latter I'm still getting indicators show up. --BUGabundo

I totally agree with this comment --

"Having read through the docs covering the NotifyOSD changes, I have to say I'm pretty lukewarm about it, as are a lot of others in the community, I think. From a users perspective, it seems like the end result will be an increase in the number of modal popup dialog boxes in addition to notification popups which now refuse to follow your chosen theme. I wouldn't consider this to be progress, on the whole. Having said that, the persistence (logging) and queueing stuff sound like a steps forward, although they probably won't show up until 9.10. Also, I generally agree with ScottKitterman about community maintenance issues. - DuncanLock"

it does seem taht the no. of although unfocused, popups and alerts willl significantly increase.

PLease someone at canonical tell me if this notification system overhaul was meant to increase productivity of users by not nugging them with popups that needed actions then how do u justify this?

--tgpraveen89

--what about CheckGmail? i use it mainly due to the fact i can delete/archive/open a message from the windows itself, without opening a browser.. --IsraeliHawk (Uri)

I agree with the reasons of the changes, but they are somehow too radical. The interaction was often useful (for example to open incoming mail, IM, etc., there is no nice alternative that would be connected to the notification itself --- yeah, you can click the tray icon or whatever, but the notification points to a specific conversation/contact or one message). But what I find ABSOLUTELY UNACCEPTABLE is the way you describe what it should look like, "regardless of theme". Do you think all the people on Earth like black round bubbles? What if they find them annoying, disturbing? It won't be so hard to make it themable, notification-daemon does so, why not? This is not what I am used to in the free software world, forcing your aesthetical feeling upon the users --- it reminds me of one innominate majority OS way to much... --Filip Štědronský (regnarg)

So I assume that it is pretty pointless to have the option in Software Sources > Updates to check less than 7 days if it's not going to tell you anyway unless they happen to be security updates. On the whole I like the new notifications and them not getting in the way, but I'm not sure that the notification system should be controlling how often it tells me what I want to know. If I want updates to check every 7 days I would tell it so. forestpixie

I hope that Rhythmbox will use OSD to display the next track (with cover, title, duration, ...) in a notification bubble (like amarok with OSD) UPDATE: here a horrible mokup. Moreover when I type "play", "next", "previous" on my keyboard this won't be displayed with a notification (it's only a bug from my computer?). Sorry for bad english (r3dkn16h7).

I have switched from network manager to WICD to avoid having to type my login every time I want to connect to my wifi network. It would be nice to see WICD information coming through notify OSD the same way as it does for network manager [Samuel Rein]

I've modified source code for GShutdown to play nicely with new notification daemon. I've submitted a patch to GShutdown Team but they have to review it and this can take some time... However I've set up a branch at my launchpad account so I (and you) can track changes. screenshot feedback from users with old/new notification daemon is needed. thanks -fm

Matthew, I appreciate your dedication to Ubuntu, but the "abolish the icon and bubble, and instead open the updates window directly" behavior you've championed as part of this just feels very disrespectful to me. One of the things that prompted me to install Ubuntu and move away from Microsoft products is what I view as MS's cavalier, heavy-handed updating behavior. They don't seem to realize that IT'S MY COMPUTER, not theirs, and this behavioral change seems to me to reflect confusion on that issue, as well. I do not want any "phone home" process to unilaterally open windows on MY COMPUTER or to try to browbeat me into taking any action that some other person has decided I should take to modify MY COMPUTER. Yes, security updates are important to me, so much so that I've allowed a particular area of my screen's real-estate to be reserved for notification of their availability. But as important as they are, security updates are *considerably* less important to me than my sense of personal control over MY COMPUTER. You'll say that delaying security updates can be hazardous to that control also, but it damages user's trust to try to force-feed updates in any way, as this change of behavior does. Any concerns (such as launchpad "bug" 175166) that the message "Click on the notification icon to show the available updates" might be misunderstood could have been addressed much more simply, in my opinion, and much less intrusively. The bottom line on this for me is that I've decided to upgrade from Hardy to Intrepid rather than to Jaunty, as I'd originally planned, because I find this change of behavior so distasteful. - ami_nakata

I’m sorry you find it so distasteful, but for windows to never open automatically would be impractical. The rest of your comment seems a bit confused. Update-notifier “phones home” every day by default, and always has, regardless of whether it opens the updates window or not; that’s a completely unrelated issue. And Ubuntu’s updates presentation is now much less like Windows than it was before, so suggesting that we’re following Microsoft is quite inaccurate. Thanks for your feedback. —mpt

Hi! I have now been looking trough this and onw thing worries me. Where it before was a notification, there is now often instead a dialog popping up focused or unfocused. This is IMO not good. For example, the notification about not removing mounted devices yet seems to get replaced by a dialog. This is not good design. When you need to notify the user not to remove the device, use the new NotifyOSD and don't pop up dialogs all over the place! Thanks! - olskar

The window warning you not to remove/eject devices that still need writing to is a progress window, not a dialog. We use a progress window because it’s in response to something you’ve specifically asked for (unmounting the device), and a notification bubble might inappropriately disappear before the process had finished. You’re correct on the general point, though, that there are a few programs that still need fixing to use notification bubbles instead of fallback alert boxes. —mpt

Thanks for answering so fast, your answer make sense. However I, and some other people, have another question. When changing song with my keyboard I get one notification telling me what song is playing, so far so good, but I also get a big symbol telling me I have pressed the next track button on my keyboard, we think it just seems a bit unnecessary? I already know I've gone forward or back - I did it just before the system tells me I did.

That was a CEO decision. The keyboard confirmation bubbles were pulled out from Jaunty at the last minute, but they’ll return in Karmic. —mpt

I also have a question about hovering over the notifications, I've read somewhere that when hovering over the notifications (making them transparent), the timer that closes them will be paused. Is that true? That would be desireable! -olskar

In regard to Update Manager, could we please have an option to return to the old behavior? I understand the rationale for the new one, but I strongly dislike the idea both of windows opening without my consent (as a regular function!) and of not knowing for a week about non-security updates. (Obviously I can change the setting for the latter, but then I have even more windows popping up!) I like the idea of the new notification system but I hope it will, on the whole, be used to corral all the wayward notification systems present in Ubuntu and make notifications as rare and unobtrusive as possible.

I think Ami’s point before was that a notification icon seems pleasant, new updates being delivered to you as they’re available, while an unwanted window seems somehow rude and obtrusive. I’m a writer, and the idea of being presented with windows full of words—even without focus—at the beginning of the day (or worse, in the middle of the day!) kind of chills me to my core. I would really, strongly appreciate an option to return to the notification icon for the Update Manager.

Users who wish to continue receiving update notifications in the previous manner can restore the earlier behavior using the following command: gconftool -s --type bool /apps/update-notifier/auto_launch false That will be mentioned in the releasenotes -olskar (Thanks! —TinaRussell)

I'm perfectly happy fiddling with gconf, but on behalf of the many users who will never have heard of gconf before, I'd like to register extreme discontent that this didn't get given a proper UI setting. -maxb.

The issue with lowresicons in pidgins buddyicons ( https://bugs.launchpad.net/bugs/338695 ) (check here for image: http://pici.se/396034/ ) is unfixable. That image is the only image we get from MSN and there is no way to make it bigger without upscaling it (and making it look bad). The only way this can be fixed is to use a smaller picture inside the bubbles, comments on that? -olskar

I really like reading instant messages from Pidgin in the notification bubbles, but occasionally I will receive a really long IM which I can't fully read before the bubble disappears. Perhaps the bubble should remain on the screen an amount of time proportional to the amount of text in the bubble? It would be nice if it could be adjusted for different reading speeds. --Omegamormegil

I'm sure I'm in the minority, but one of the things I hate about MS Windows is that it frequently distracts me from what I'm doing with stupid pop-up bubbles for the most irrelevant of things -- like connecting to a wireless network. There is a little icon in my notification area that tells me stuff like that. I don't want stuff appearing and disappearing from my work area, especially not with fading or sliding effects. In previous versions of Ubuntu, I was able to chmod -x notification-daemon to get rid of this, but it looks like you're adding more and more functionality to pop-ups and planning on getting rid of the notification area altogether. Also, pop-under windows are particularly annoying. The notification area is the only place where I have given the OS permission to "notify" me of anything. Put an icon there if I need to know something, and if I wonder what it is, I'll mouse over it, or click on it, or whatever. There is NOTHING so important that it needs to interrupt what I'm doing by littering my workspace. I understand other people's need for eye-candy (and ritalin), but please, let us old timers shut off the cute stuff, and limit it to the notification area. I also just noticed that when I use my keyboard volume buttons, the volume control uses the new pop-up framework, which instead of being theme colored and in the middle of my screen (obviously if I'm pressing buttons, this isn't an unwanted notification), it appears in a black window in the upper right corner of my screen where it doesn't belong, and where it blends in with my black background. I know you guys are all about a "single experience" and making all the apps look the same, but make sure you don't make all the apps suck with no way to get the old behaviour back! --Brian

The proposed update to gnome-screensaver opts to use a pop-up instead of a notification to notify the user of a left message. I believe a better system could be implemented, since I consider a pop-up obtrusive. http://brainstorm.ubuntu.com/idea/19482/ -- Kareeser

I agree with you Kareeser. Pop-ups should be avoided wherever they can, I think everyone can agree with that, and I think your solution with integrating it into the notification-applet is elegant. -olskar

Would it be possible to get a notification when pressing Caps Lock / Num Lock? There's also something I find annoying about the bubbles is that they fade out, then flicker on again and only then hide. --astron

I don't want to trivialize your work, but not everyone likes or wants eye candy. I want performance...the more eye candy, the more CPU cycles taken from something useful. I guess the best option is leave the user the option to have it or not. chmod -x notification-daemon didn't work, but I found a way. For those who love it, great! For those of us who are drastically annoyed by popups, give us a mechanism (reasonable) to turn it off! --Doc

Could Firefox (or Empathy or Transmission or Nautilus copy between mounts(?) or foo) use notifications for transfer complete, with a transfer indicator keeping track of current downloads and unacknowledged completed downloads? 'All downloads complete' wouldn't be necessary. Elegance in how progress within the indicator is displayed would be desirable though. -- JimPutt

Suggestion: It's good that notification logs was accepted and implemented in time for Jaunty. For Karmic, I expect a GUI for the log, ideally IMHO from Indicator applet, alternatively from Sys/Adm/Log Viewer. -- FelipeFigueiredo

Regarding ontv: "When a new program matching your criteria is detected, a notification bubble appears that, when clicked, opens a dialog with more details of the program. Instead … "

Instead I think only a notification should be shown with the name of the program and time it starts, there is really no need for a button that when clicked opens details. -olskar

I think notify-osd should be added to Debian, so applications can start the testing there and be synced more easily in the future. (Some Ubuntu members are Debian Developers, and they can help to maintain it there). -Marco Rodrigues

I think making these non-interactive was a mistake, though I do understand the reasoning. For example, trivial notifications might not deserve a full 5s (or whatever) and the user choice in dismissing them is basic usability. Displaying something that the user can't interact with is just plain wrong, even if you think they don't need to interact with it. Of course, whether they do or don't is an empirical question: For example, I just had a notification that refused to disappear over the course of several minutes, which is beyond distracting. I killed the process and uninstalled notify-osd because that is a bug, not a feature (even if it had disappeared on it's own, it's still a bug). That said, these notifications look much nicer than the previous system, and the effort isn't wasted, even if some missteps are made along the way. -Mike.lifeguard

Regarding Rhythmbox, I use "Music Applet" in conjunction with it, which does use notifications. (This is an applet that places basic play/pause, previous, next buttons in the task bar.) Under Jaunty, the notification bubble would change each time the forward or reverse buttons were clicked--handy for jumping through tracks quickly without having the full Rhythmbox window visible. In Karmic, however, the new "spam prevention" feature seems to hinder this functionality. The bubbles do change, but each one displays for its entire life cycle of several seconds before the next one appears. So, I can click "forward" many times before even the second notification displays. Obviously, this behavior renders the notifications functionally useless in this application. Is there a way to modify or configure this behavior? -Darren Gibson

I have removed notify-OSD from my system - First, the location is too annoying and I cannot set it (or the group - statck them from the bottom or top left if you must). I should be able to select any corner. Second, it stays up too long - also cannot be set by anything I can find - and cannot be dismissed. It often covers something I need to see, but moving the mouse over causes an epilepsy inducing flash. Too many applications have trivial notifications which cannot be shut off - e.g. edit a file in ~/Ubuntu One, and you get a series of "UO is updating", "UO has finished updating" flashes. I can't fix hundreds of noisy apps. Maybe it should ignore the first click, but it should have a DISMISS and GO (like for IM to particular conversations, playing, etc.) instead of being a ghost box. I also might not mind it if it has settable transparency, but it doesn't have that either. This is supposed to notify me, not annoy me. So are you going to replace vi with vigor because it has better notification? Note I have a small screen so a tiny box is very annoying because it takes up a lot of screen - it probably wouldn't bother me as much on my HD monitor, but I'm usually using the netbook.

Shoving a "one size fits all" notification system down the user's throat is a bad idea. Why not just block the entire screen and all mouse and keyboarding for 5 seconds - the user would definitely notice.

In summary, for this not to be annoyware:

1. Settable corner to be used. Reverse the positioning for priority from the bottom

2. Settable popup duration.

3. Settable transparency so I can see through the box instead of the opaque screenblock flashy on mouseover behavior.

4. a dismiss mechanism (I'd rather have them up longer but dismissable).