File

mod_reminders/mod_reminders.lua @ 6301:fa45ae704b79

mod_cloud_notify: Update Readme diff --git a/mod_cloud_notify/README.md b/mod_cloud_notify/README.md --- a/mod_cloud_notify/README.md +++ b/mod_cloud_notify/README.md @@ -1,109 +1,106 @@ ---- -labels: -- 'Stage-Beta' -summary: 'XEP-0357: Cloud push notifications' ---- +# Introduction -Introduction -============ +This module enables support for sending "push notifications" to clients +that need it, typically those running on certain mobile devices. -This module enables support for sending "push notifications" to clients that -need it, typically those running on certain mobile devices. +As well as this module, your client must support push notifications (the +apps that need it generally do, of course) and the app developer's push +gateway must be reachable from your Prosody server (this happens over a +normal XMPP server-to-server 's2s' connection). -As well as this module, your client must support push notifications (the apps -that need it generally do, of course) and the app developer's push gateway -must be reachable from your Prosody server (this happens over a normal XMPP -server-to-server 's2s' connection). - -Details -======= +# Details Some platforms, notably Apple's iOS and many versions of Android, impose -limits that prevent applications from running or accessing the network in the -background. This makes it difficult or impossible for an XMPP application to -remain reliably connected to a server to receive messages. - -In order for messaging and other apps to receive notifications, the OS vendors -run proprietary servers that their OS maintains a permanent connection to in -the background. Then they provide APIs to application developers that allow -sending notifications to specific devices via those servers. +limits that prevent applications from running or accessing the network +in the background. This makes it difficult or impossible for an XMPP +application to remain reliably connected to a server to receive +messages. -When you connect to your server with an app that requires push notifications, -it will use this module to set up a "push registration". When you receive -a message but your device is not connected to the server, this module will -generate a notification and send it to the push gateway operated by your -application's developers). Their gateway will then connect to your device's -OS vendor and ask them to forward the notification to your device. When your -device receives the notification, it will display it or wake up the app so it -can connect to XMPP and receive any pending messages. +In order for messaging and other apps to receive notifications, the OS +vendors run proprietary servers that their OS maintains a permanent +connection to in the background. Then they provide APIs to application +developers that allow sending notifications to specific devices via +those servers. -This protocol is described for developers in [XEP-0357: Push Notifications]. +When you connect to your server with an app that requires push +notifications, it will use this module to set up a "push registration". +When you receive a message but your device is not connected to the +server, this module will generate a notification and send it to the push +gateway operated by your application's developers). Their gateway will +then connect to your device's OS vendor and ask them to forward the +notification to your device. When your device receives the notification, +it will display it or wake up the app so it can connect to XMPP and +receive any pending messages. -For this module to work reliably, you must have [mod_smacks], [mod_mam] and -[mod_carbons] also enabled on your server. +This protocol is described for developers in \[XEP-0357: Push +Notifications\]. + +For this module to work reliably, you must have \[mod_smacks\], +\[mod_mam\] and \[mod_carbons\] also enabled on your server. -Some clients, notably Siskin and Snikket iOS need some additional extensions -that are not currently defined in a standard XEP. To support these clients, -see [mod_cloud_notify_extensions]. +Some clients, notably Siskin and Snikket iOS need some additional +extensions that are not currently defined in a standard XEP. To support +these clients, see \[mod_cloud_notify_extensions\]. -Configuration -============= +# Configuration - Option Default Description - ------------------------------------ ----------------- ------------------------------------------------------------------------------------------------------------------- - `push_notification_important_body` `New Message!` The body text to use when the stanza is important (see above), no message body is sent if this is empty - `push_max_errors` `16` How much persistent push errors are tolerated before notifications for the identifier in question are disabled - `push_max_devices` `5` The number of allowed devices per user (the oldest devices are automatically removed if this threshold is reached) - `push_max_hibernation_timeout` `259200` (72h) Number of seconds to extend the smacks timeout if no push was triggered yet (default: 72 hours) - `push_notification_with_body` (\*) `false` Whether or not to send the real message body to remote pubsub node. Without end-to-end encryption, enabling this may expose your message contents to your client developers and OS vendor. Not recommended. - `push_notification_with_sender` (\*) `false` Whether or not to send the real message sender to remote pubsub node. Enabling this may expose your contacts to your client developers and OS vendor. Not recommended. + Option Default Description + -------------------------------------- ---------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- + `push_notification_important_body` `New Message!` The body text to use when the stanza is important (see above), no message body is sent if this is empty + `push_max_errors` `16` How much persistent push errors are tolerated before notifications for the identifier in question are disabled + `push_max_devices` `5` The number of allowed devices per user (the oldest devices are automatically removed if this threshold is reached) + `push_max_hibernation_timeout` `259200` (72h) Number of seconds to extend the smacks timeout if no push was triggered yet (default: 72 hours) + `push_notification_with_body` (\*) `false` Whether or not to send the real message body to remote pubsub node. Without end-to-end encryption, enabling this may expose your message contents to your client developers and OS vendor. Not recommended. + `push_notification_with_sender` (\*) `false` Whether or not to send the real message sender to remote pubsub node. Enabling this may expose your contacts to your client developers and OS vendor. Not recommended. -(\*) There are privacy implications for enabling these options. +(\*) There are privacy implications for enabling these options.[^1] -Internal design notes -===================== +# Internal design notes -App servers are notified about offline messages, messages stored by [mod_mam] -or messages waiting in the smacks queue. -The business rules outlined [here](//mail.jabber.org/pipermail/standards/2016-February/030925.html) are all honored[^2]. +App servers are notified about offline messages, messages stored by +\[mod_mam\] or messages waiting in the smacks queue. The business rules +outlined +[here](//mail.jabber.org/pipermail/standards/2016-February/030925.html) +are all honored[^2]. -To cooperate with [mod_smacks] this module consumes some events: -`smacks-ack-delayed`, `smacks-hibernation-start` and `smacks-hibernation-end`. -These events allow this module to send out notifications for messages received -while the session is hibernated by [mod_smacks] or even when smacks -acknowledgements for messages are delayed by a certain amount of seconds -configurable with the [mod_smacks] setting `smacks_max_ack_delay`. +To cooperate with \[mod_smacks\] this module consumes some events: +`smacks-ack-delayed`, `smacks-hibernation-start` and +`smacks-hibernation-end`. These events allow this module to send out +notifications for messages received while the session is hibernated by +\[mod_smacks\] or even when smacks acknowledgements for messages are +delayed by a certain amount of seconds configurable with the +\[mod_smacks\] setting `smacks_max_ack_delay`. -The `smacks_max_ack_delay` setting allows to send out notifications to clients -which aren't already in smacks hibernation state (because the read timeout or -connection close didn't already happen) but also aren't responding to acknowledgement -request in a timely manner. This setting thus allows conversations to be smoother -under such circumstances. +The `smacks_max_ack_delay` setting allows to send out notifications to +clients which aren't already in smacks hibernation state (because the +read timeout or connection close didn't already happen) but also aren't +responding to acknowledgement request in a timely manner. This setting +thus allows conversations to be smoother under such circumstances. -The new event `cloud-notify-ping` can be used by any module to send out a cloud -notification to either all registered endpoints for the given user or only the endpoints -given in the event data. +The new event `cloud-notify-ping` can be used by any module to send out +a cloud notification to either all registered endpoints for the given +user or only the endpoints given in the event data. -The config setting `push_notification_important_body` can be used to specify an alternative -body text to send to the remote pubsub node if the stanza is encrypted or has a body. -This way the real contents of the message aren't revealed to the push appserver but it -can still see that the push is important. -This is used by Chatsecure on iOS to send out high priority pushes in those cases for example. +The config setting `push_notification_important_body` can be used to +specify an alternative body text to send to the remote pubsub node if +the stanza is encrypted or has a body. This way the real contents of the +message aren't revealed to the push appserver but it can still see that +the push is important. This is used by Chatsecure on iOS to send out +high priority pushes in those cases for example. -Compatibility -============= - -**Note:** This module should be used with Lua 5.2 and higher. Using it with -Lua 5.1 may cause push notifications to not be sent to some clients. +# Compatibility ------- ----------------------------------------------------------------------------- - trunk Works - 0.12 Works - 0.11 Works - 0.10 Works - 0.9 Support dropped, use last supported version [675726ab06d3](//hg.prosody.im/prosody-modules/raw-file/675726ab06d3/mod_cloud_notify/mod_cloud_notify.lua) ------- ----------------------------------------------------------------------------- +**Note:** This module should be used with Lua 5.2 and higher. Using it +with Lua 5.1 may cause push notifications to not be sent to some +clients. + ------- ----------------------------------------------------------------- + trunk Works as of 25-06-13 + 13 Works + 0.12 Works + ------- ----------------------------------------------------------------- -[^1]: The service which is expected to forward notifications to something like Google Cloud Messaging or Apple Notification Service -[^2]: [business_rules.markdown](//hg.prosody.im/prosody-modules/file/tip/mod_cloud_notify/business_rules.markdown) +[^1]: The service which is expected to forward notifications to + something like Google Cloud Messaging or Apple Notification Service + +[^2]: [business_rules.md](//hg.prosody.im/prosody-modules/file/tip/mod_cloud_notify/business_rules.md)
author Menel <menel@snikket.de>
date Fri, 13 Jun 2025 10:36:52 +0200
parent 3921:9eabd68b8e48
line wrap: on
line source

-- mod_reminders
--
-- Copyright (C) 2020 Marcos de Vera Piquero <marcos@tenak.net>
--
-- This file is MIT/X11 licensed.
--
-- A module to support ProtoXEP: Reminders
--

local id = require "util.id"
local datetime = require"util.datetime";
local errors = require"util.error";
local jid = require"util.jid";
local st = require"util.stanza";
local os_time = os.time;

local xmlns_reminders = "urn:xmpp:reminders:0";

local reminders_store = module:open_store(xmlns_reminders, "keyval");

local reminders_errors = {
	missing_fields = {
		type = "modify";
		condition = "bad-request";
		text = "Missing required value for date or text";
	};
	invalid_dateformat = {
		type = "modify";
		condition = "bad-request";
		text = "Invalid date format";
	};
	past_date = {
		type = "modify";
		condition = "gone";
		text = "Reminder date is in the past";
	};
	store_error = {
		type = "cancel";
		condition = "internal-server-error";
		text = "Unable to persist data";
	};
};

local function reminder_error (name)
	return errors.new(name, nil, reminders_errors);
end

local function store_reminder (reminder)
	-- pushes the reminder to the store, and nothing else
	return reminders_store:set(reminder.id, reminder);
end

local function delete_reminder (reminder_id)
	-- empties the store for the given reminder_id
	return reminders_store:set(reminder_id, nil);
end

local function get_reminder (reminder_id)
	return reminders_store:get(reminder_id);
end

local function send_reminder (reminder)
	-- actually delivers the <message /> with the reminder to the user
	local bare = jid.bare(reminder.jid);
	module:log("debug", "Sending reminder %s to %s", reminder.id, bare);
	local message = st.message({ from = "localhost"; to = bare; id = id.short() })
		:tag("reminder", {id = reminder.id; xmlns = xmlns_reminders})
		:add_child(reminder.text)
		:tag("date"):text(datetime.datetime(reminder.date)):up();
	module:send(message);
	return delete_reminder(reminder.id)
end

local function schedule_reminder (reminder)
	-- schedule a module:add_timer for the given reminder
	module:log("debug", "Scheduling reminder to datetime %s", reminder.date);
	local now = os_time();
	local when = reminder.date;
	local delay = when - now;
	module:log("debug", "Reminder text: %s", reminder.text);
	local function callback ()
		send_reminder(reminder)
	end
	module:add_timer(delay, callback);
end

local function process_reminders_store ()
	-- retrieve all reminders in the store and schedule them
	for reminder_id in reminders_store:users() do
		module:log("debug", "Found stored reminder %s", reminder_id);
		local reminder = get_reminder(reminder_id);
		if reminder.date and reminder.text then
			local text = st.deserialize(reminder.text)
			module:log("debug", "Read reminder %s", reminder.id);
			-- cleanup missed reminders
			if reminder.date < os_time() then
				module:log("debug", "Deleting outdated reminder %s", reminder.id)
				delete_reminder(reminder.id)
			end
			schedule_reminder({
					date = reminder.date;
					id = reminder.id;
					jid = reminder.jid;
					text = text;	
			})
		else
			delete_reminder(reminder_id);
		end
	end
end

local function create_reminder (jid, reminder)
	local date = reminder:get_child("date");
	local text = reminder:get_child("text");
	if date == nil or text == nil then
		return nil, reminder_error("missing_fields")
	end
	local now = os_time();
	local _, parsed_date = pcall(datetime.parse, date:get_text());
	if parsed_date == nil then
		return nil, reminder_error("invalid_dateformat")
	end
	if parsed_date < now then
		return nil, reminder_error("past_date"), nil
	end
	local reminder_id = id.medium();
	local rem = st.stanza("reminder", {xmlns = xmlns_reminders; id = reminder_id});
	local data = {
		id = reminder_id;
		jid = jid;
		text = text;
		date = parsed_date;
	}
	local stored = store_reminder(data);
	if not stored then
		return nil, reminder_error("store_error")
	end
	schedule_reminder(data);
	return rem
end

local function handle_set (event)
	local origin, stanza = event.origin, event.stanza
	local reminder = stanza:get_child("reminder", xmlns_reminders);
	if reminder.attr.id ~= nil and reminder:get_child("date") == nil then
		-- delete existing reminder
		local ok = delete_reminder(reminder.attr.id);
		if ok then
			module:log("debug", "reminder %s deleted", reminder.attr.id);
			origin.send(st.reply(stanza):add_child(reminder));
		else
			module:log("debug", "failed to delete reminder %s", reminder.attr.id);
			origin.send(st.error_reply(stanza, "cancel", "internal-server-error"));
		end
		return true;
	else
		-- create new reminder
		local jid = stanza.attr.from
		local created, err = create_reminder(jid, reminder);
		if err ~= nil then
			origin.send(st.error_reply(stanza, err))
			return true;
		else
			origin.send(st.reply(stanza):add_child(created))
			return true;
		end		
	end
	origin.send(st.error_reply(stanza, "modify", "bad-request"));
	return true;
end


-- load saved reminders and set timers
process_reminders_store();

module:hook("iq-set/host/"..xmlns_reminders..":reminder", handle_set)
module:add_feature(xmlns_reminders);
module:log("debug", "Module loaded");