Some feedback on the Notification API:

* The Growl API requires a "notificationName" which is what it displays in the configuration UI. The "title" can't be used for this as the title usually changes for each notification (e.g. subject of email). A potential complication is that every application that registers with Growl has to provide it's full set of notificationNames when it initializes the Growl client. Also, not sure how Growl handles the situation where different "applications" (i.e. websites) sends notification from the same application (that is Firefox). * Bubbles on the task bar on Windows has quite a different user experience compared to Growl. It can only be used to show one notification at a time and therefor obviously doesn't scale to handle a steady stream of incoming notifications. I think Gears would have to implement it's own notification system on Windows, something that behaves more like Growl. * I think some form of permission system should be used for turning on notifications on a particular website. A dialog asking: "This website wants to send you notifications. Do you want to allow this? Yes/No". This is already supported for other functionality in Gears right?

I've been looking at how to implement this, and I have a couple of ideas and questions. Not sure this is the right list for this as it's very technical in nature. Dion said someone had already started looking at this, maybe we can join forces? I'm primarily looking at implementing it on Mac with Growl right now.

Cheers, Jon