Oh God, please not make it persistent. This notification comes up every single time I start plasmashell and now I have to explicitly manually get rid of it.
Also I disagree security updates available notification should be "low urgency". Instead of making everything that shouldn't be in the history low priority (which is not what low priority means, it is just a side-effect) I would suggest you add a flag for KNotification to not keep in history.

In D22429#495652, @broulik wrote:

Oh God, please not make it persistent. This notification comes up every single time I start plasmashell and now I have to explicitly manually get rid of it.

That's kind of the point though. The user should be seeing these notifications and having to explicitly acknowledge them in some way; updates are important. If it's annoying for you, maybe you should turn Discover's notifications off entirely?

Or maybe persistent/close on timeout behavior should be user-configurable. It actually is on macOS where each individual notification can be made persistent, close-on-timeout, or disabled.

Also I disagree security updates available notification should be "low urgency". Instead of making everything that shouldn't be in the history low priority (which is not what low priority means, it is just a side-effect) I would suggest you add a flag for KNotification to not keep in history.

Fair point. I'll give it a go.

That's kind of the point though. The user should be seeing these notifications and having to explicitly acknowledge them in some way;

It wasn't nearly as annoying if a kded module was responsible for it and not the applet, so it wouldn't show up every single time I restart plasmashell which I tend to do a lot.

In D22429#496180, @broulik wrote:

That's kind of the point though. The user should be seeing these notifications and having to explicitly acknowledge them in some way;

It wasn't nearly as annoying if a kded module was responsible for it and not the applet, so it wouldn't show up every single time I restart plasmashell which I tend to do a lot.

Me too. However, this is a developer workflow, not a typical user workflow. Defaults should be optimized for users, not developers. Weirdos like us who are killing and restarting plasmashell 30 times a day can just turn off Discover's updates notification.

I agree that it would be nice if we could somehow make the notification only appear when plasmashell is started due to a login, not every time.

Will fix the code issues you bring up in another patch.

How about only making security update notifications persistent? There is no real harm in missing non-security updates in my opinion.