in reply to New Feature: Notifications Nodelet

Not to sure about that feature, but

> It only shows a maximum of 16 notifications;

the number should be configurable in the Message Settings to be usable

same like

Max to display in Chatterbox (hard limit 50)

And as I said, if possible notifications shouldn't replicate

I'd prioritize per notified node:

I have the impression you want to create a fourth category for multiple triggers. I think that's overkill...

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery

Replies are listed 'Best First'.
Re^2: New Feature: Notifications Nodelet
by jdporter (Paladin) on Apr 10, 2024 at 14:37 UTC
    the number should be configurable

    I hesitate to create yet another configuration variable. I'm inclined to use the same one as for chat messages, at least for starters.

    notifications shouldn't replicate

    Notifications from the new watcher mechanism do not replicate. The only duplication you'll see now is when you get a reply to one of your own nodes (old mechanism) and you also have a watch which triggers (new mechanism). Unfortunately, these two mechanisms are unrelated and in separate parts of the code, so de-duplicating here will be ... non-trivial.

    I'd prioritize per notified node:

    I like this idea.

    I have the impression you want to create a fourth category for multiple triggers

    Not at all.

    Today's latest and greatest software contains tomorrow's zero day exploits.
[reply]
      > I'm inclined to use the same one as for chat messages, at least for starters.

      sounds good! :)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery

[reply]

In Section Perl Monks Discussion