in reply to Re: New Feature: Notifications Nodelet
in thread New Feature: Notifications Nodelet

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.
  • Comment on Re^2: New Feature: Notifications Nodelet

Replies are listed 'Best First'.
Re^3: New Feature: Notifications Nodelet
by LanX (Saint) on Apr 10, 2024 at 14:54 UTC
    > 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