Flood protection

[kasakka]

I think this would be essential to implement in Growl. Every day when
I wake my computer from sleep I get my whole screen filled with
messages from the Linkinus IRC client as it loads the playback buffer
of my IRC bouncer. The app is working as expected as it interprets the
bouncer playback buffer as hundreds of new messages. Yes, I've asked
the developers to implement a notification flood protection but so far
nothing has been done.

However, this is primarily a Growl issue. It would allow a malicious
app for example to constantly fill the screen with messages unless the
user quits the app, quits Growl or kills the GrowlHelperApp. There is
no situation where filling the display with tens of messages, making
everything else impossible, would be useful.

So I propose the following:

1. Add a global "maximum number of notifications on screen at once"
setting. Anything more than this gets simply dropped or Growl waits x
amount of time to display them, essentially queuing the notifications
(user option which way to use).
2. Add an application specific limit so you can force applications
that might give lots of notifications to only be able to churn out x
amount.

Shouldn't be too difficult to implement.

[xairbusdriver]

On Feb 17, 2:53 am, kasakka <kasa...@gmail.com> wrote:
<CHOP>

> However, this is primarily a Growl issue. It would allow a malicious
> app for example to constantly fill the screen with messages unless the
> user quits the app, quits Growl or kills the GrowlHelperApp. There is
> no situation where filling the display with tens of messages, making
> everything else impossible, would be useful.
>
> So I propose the following:
>
> 1. Add a global "maximum number of notifications on screen at once"
> setting. Anything more than this gets simply dropped or Growl waits x
> amount of time to display them, essentially queuing the notifications
> (user option which way to use).
> 2. Add an application specific limit so you can force applications
> that might give lots of notifications to only be able to churn out x
> amount.
>
> Shouldn't be too difficult to implement.

Of course not! After all, "coding" is just typing, right?! LOL!!

[Chris Forsythe]

We implemented the Rollup feature to address this issue. Do you have that disabled?

-- 
Chris Forsythe

--

You received this message because you are subscribed to the Google Groups "Growl Discuss" group.

To post to this group, send email to growld...@googlegroups.com.

To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.

[Daniel Siemer]

A better solution would be for the developer of LInkinus to support
notification coalescing, which has been a feature of Growl for longer
than Linkinus has existed

On Feb 17, 2:53 am, kasakka <kasa...@gmail.com> wrote:

[kasakka]

I'm still on 10.6 at work so no 1.3 for me unfortunately. Does Rollup
pose any limitations for the number of messages? Because if the
current situation is my screen getting filled with around 1000
notifications every time my machine comes out of sleep with Linkinus
not selected, so if this causes those same messages to fill the Rollup
window then I don't think that's a great thing either.

Does notification coelescing support having x messages from an app at
a time or will it just have one and that gets replaced by the next
(not the behavior I'm looking for)?

[Devin]

Sorry, I may be missing something, but are you implying the the
regular notifications shouldn't be still coming up when the rollup is
displayed? Because for me, they still keep coming.

> > To post to this group, send email to growld...@googlegroups.com (mailto:growld...@googlegroups.com).
> > To unsubscribe from this group, send email to growldiscuss...@googlegroups.com (mailto:growldiscuss...@googlegroups.com).

[Chris Forsythe]

Regular notifications should show up and then go away. If you're gone for hours and come back, you should have the rollup and not all of notifications filling up your screen. There are some exceptions to that I believe, i'd have to look into it again to remember those.

-- 
Chris Forsythe

To post to this group, send email to growld...@googlegroups.com.

To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.

[Devin]

Then I guess I don't understand how the rollup addresses this issue at
all?

On Feb 24, 6:54 pm, Chris Forsythe <ch...@growl.info> wrote:
> Regular notifications should show up and then go away. If you're gone for hours and come back, you should have the rollup and not all of notifications filling up your screen. There are some exceptions to that I believe, i'd have to look into it again to remember those.
>
> --
> Chris Forsythe
>
>
>
>
>
>
>
> On Friday, February 24, 2012 at 5:25 PM, Devin wrote:
> > Sorry, I may be missing something, but are you implying the the
> > regular notifications shouldn't be still coming up when the rollup is
> > displayed? Because for me, they still keep coming.
>

[kasakka]

This is still an issue in the latest App Store version of Growl. Enabling Rollup doesn't seem to help either. What happens is that Growl is instantly flooded with hundreds of messages and that makes them fill the screen and may cause very high memory usage (seen over 300 MB) and even make Growl beachball. Enabling Rollup doesn't address the issue.

Thus Growl should be able to handle messages so that if x amount of notifications is sent in y time from the same app, enable flood protection and don't show them. x amount would be something high like 100 messages. It should also be possible to limit amount of Growl messages to take only a portion of the screen. For example on my 2560x1440 screen, limiting them to about 10 to cover the height of the screen (one column) would be preferable.