Mercurial > prosody-modules
view mod_map/README.markdown @ 5146:a86022d702b2
mod_unified_push: Fix JWT method parameter order (fixes #1791)
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Fri, 13 Jan 2023 16:40:00 +0000 |
parents | d31fa28d9482 |
children |
line wrap: on
line source
--- labels: - 'Stage-Experimental' summary: Prototype MAM summary --- This is a prototype for an experimental archive summary API recently added in [Prosody trunk](https://hg.prosody.im/trunk/rev/2c5546cc5c70). # Protocol ::: {.alert .alert-danger} This is not a finished protocol, but a prototype meant for testing. ::: A basic query: ``` {.xml} <iq id="lx7" type="get"> <summary xmlns="xmpp:prosody.im/mod_map"/> </iq> ``` Answered like: ``` {.xml} <iq type="result" id="lx7"> <summary xmlns="xmpp:prosody.im/mod_map"> <item jid="juliet@capulet.lit"> <count>3</count> <start>2019-02-25T15:48:00+0100</start> <end>2019-08-23T01:39:50+02:00</end> <body>O Romeo, Romeo! wherefore art thou Romeo?</body> </item> </summary> </iq> ``` It can also take dataform and RSM parameters similar to a [filtered MAM query](https://xmpp.org/extensions/xep-0313.html#filter). E.g if the last message you received had an id `09af3-cc343-b409f` then the following query would tell you who sent you messages since: ``` {.xml} <iq id="lx8" type="get"> <summary xmlns="xmpp:prosody.im/mod_map"> <set xmlns="http://jabber.org/protocol/rsm"> <max>10</max> <after>09af3-cc343-b409f</after> </set> </summary> </iq> ```