[prosody-dev] [PATCH] mod_muc_mam

[JC Brand]

Hi folks

I'm working on a fork of mod_cloud_notify, called mod_muc_cloud_notify, which
is a push notifications module for MUCs.

The idea is that the MUC advertises `urn:xmpp:push:0` and that clients can then
register push services for it.

The main usecase is not mobile with intermittent connection drops, but email
notifications for users who aren't currently in the MUC.

We're using the members list to figure out who to notify, and we're going to
look up the JID by room-reserved nickname.

This patch emits an event in mod_muc_mam, which we listen to in
mod_muc_cloud_notify, so that we know when to send out a push notification.

Regards
JC

[Kim Alvefur]

Hi,

Post by JC Brand
This patch emits an event in mod_muc_mam, which we listen to in
mod_muc_cloud_notify, so that we know when to send out a push notification.

What is your reasoning for adding these things in these specific places?

Functionally, it seems equivalent to hooking "muc-add-history" or
"muc-broadcast-message" with a priority that puts it after mod_muc_mam.
--
Regards,
Kim "Zash" Alvefur

[JC Brand]

Post by Kim Alvefur
Hi,

Post by JC Brand
This patch emits an event in mod_muc_mam, which we listen to in
mod_muc_cloud_notify, so that we know when to send out a push notification.

What is your reasoning for adding these things in these specific places?
Functionally, it seems equivalent to hooking "muc-add-history" or
"muc-broadcast-message" with a priority that puts it after mod_muc_mam.

Uh yes, actually muc-add-history is totally sufficient.

I'll use that then.

Thanks