It's a great idea (well, a great extension of Growl's concept), but the infrastructure isn't there — not entirely. For real-time notifications to happen (and b

It's a great idea (well, a great extension of Growl's concept), but the infrastructure isn't there — not entirely. For real-time notifications to happen (and be reasonably lightweight), you need to have hooks into your monitored services. Growl works because its clients send messages to the Growl server on your machine when something interesting happens. Web services will need to have a similar mechanism for (securely) telling your notification service that "something happened." Weblogs are already most of the way there: modern blogging engines can send HTTP "pings" when new entries are posted. Apache sends its errors to a file, so it would need to be extended to post errors to your notification service. I'm rambling now, but if anyone wants to start a working group or somethin', props. It's going to need some intelligent design to take the weight of the whole internet flowing through it and to ensure that private notifications (your web server, Facebook) don't get into the wrong hands.