Hi, Le mercredi 5 juin 2024, 14:15:21 UTC+2 Marvin W a écrit : Indeed, and not only for mobile, one may want different kind of notifications depending on hours etc. I think this can be done with future XEP (e.g. to have notification rules filtered by the kind of device). Maybe this could be anticipated in this specification by allowing explicitly several <notify/> elements? Also, it would be nice to have this working with pubsub, notably for blogging/ comments: it would be great to specify how we want to be notified when somebody mention you in a comment. But this is not about this protoXEP, it's about PEP native bookmarks which only accept <conference> so far. Anyway it's a good start, and it's simple which is good. Best, Goffi

Thanks for the feedback! ♥ accordingly :) Cool! I did not mention it but (with lovetox's approbation) I will probably implement it in gajim, and certainly in slidge too (although it will require privileged entity support for it to work, and allowing slidge to subscribe to your relevant PEP node(s)). From the business rules: being spelled out in an incoming message in a group-chat, but MAY rely on other mechanism to "ping" the user, such as a Message Replies (XEP-0461) <https://xmpp.org/extensions/xep-0461.html> or Message Reactions (XEP-0444) <https://xmpp.org/extensions/xep-0444.html> element referring a user's previous message. I can see use cases for "on-reply" vs "on-mention" but only because we don't have "explicit mention/pings" used yet, ie, no way of writing the nickname of someone with no intent on pinging them (or it's just not implemented in clients I use). Also, thinking about it more, maybe a reaction to a message should not be considered a mention, in large group chats especially, we probably don't want that. Maybe I should change this to: spelled out in an incoming message in a group-chat, but SHOULD rely on an explicit mechanism to "ping" the user, such as a Message Replies (XEP-0461) <https://xmpp.org/extensions/xep-0461.html> [2 <https://nicoco.fr/xep-notification-filter.html#nt-idm52>] referring a user's previous message or <future XEP for mentions with explicit ping intent>. explicitly several <notify/> elements? So maybe we could have: <notify xmlns='urn:xmpp:notification-settings:0'>   <never context='mobile' />   <on-mention context='desktop' /> </notify> The context attribute would be optional if there is only child but required if there are several ones. And (notif-setting, context) pairs MUST be unique (can we express that in them schema?). What do you say if we allow context = 'mobile', 'desktop' or 'advanced', with 'advanced' meaning that rules are defined as children of the element, eg <always context='advanced'>   <when day="monday" xmlns='custom:namespace-0:0'>     <start>9:00</start>     <end>17:00</end>   </when>   <something-very-advanced xmlns='custom:namespace-1:0' type='super-subtle' /> </always> We could make that similar to bookmarks extensions in the sense that clients MUST preserve what's in there, especially if they don't understand the content? -- nicoco

Hi all, I updated https://nicoco.fr/xep-notification-filter.html and the github PR accordingly to the list feedback. Unless I forgot something, I think the only thing I did not incorporate (yet?) is the "on-mention"/"on-reply" distinction singpolyma suggested. I'm not 100% against adding it, but I think it falls under the "advanced" use case that this specification allows as children of the dedicated element. Let me know if your concerns have been addressed in this latest revision and if you have any other comments, suggestions, or anything else to add! Cheers, -- nicoco