There is a new nodelet, Notifications.

What this essentially does is split out the system-generated notification messages into a separate nodelet from the Chatterbox nodelet. So if you enable this nodelet, then all of the messages which come to you from the system (i.e. from root or NodeReaper) are shown in this nodelet and not in the Chatterbox nodelet.

This is structured very similarly to the Chatterbox nodelet, but with a few simplifications:

As with all nodelets*, this one can be viewed "standalone" on its own page, simply by going to the node of the same title: Notifications.

* With just a couple exceptions.

Replies are listed 'Best First'.
Re: New Feature: Notifications Nodelet
by choroba (Cardinal) on Apr 09, 2024 at 19:12 UTC
    What do you (all) think about adding a link to the Notifications to Message Inbox? It's kind of related and it's where I'd go looking for the messages if I didn't know about Notifications.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
[reply]
[d/l]

      If you don't have this new Notifications nodelet enabled, you see the messages in the Chatterbox nodelet. That's the only thing affected. You see all messages in your Message Inbox, always.

[reply]
Re: New Feature: Notifications Nodelet
by hippo (Archbishop) on Apr 09, 2024 at 21:21 UTC
    There is a new nodelet, Notifications. (Yes, you can click on that. Every nodelet* can be viewed on its own page, simply by going to the node of the same title.)

    Well I took the bait and clicked on Notifications. It took me to a page of search results. Same for the Chatterbox links, FWIW. :-/

    🦛

[reply]

      Thanks for the report. Fixed. (Note that users not logged in will still get the behavior you described.)

      Please let me know if you see any further issues.

[reply]
        The "delete" doesn't seem to be working in the Notifications page nor its nodelet.
[reply]
Re: New Feature: Notifications Nodelet
by LanX (Saint) on Apr 10, 2024 at 14:09 UTC
    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:

    • direct reply? YES -> send and skip
    • thread watch? YES -> send and skip
    • followed person YES -> send
    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

[reply]
[d/l]
      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]

Back to Perl Monks Discussion