aboutsummaryrefslogtreecommitdiffstats
path: root/plugins/mod_mam
Commit message (Collapse)AuthorAgeFilesLines
* mod_mam: Implement extended MAM metadata queryKim Alvefur2020-11-301-1/+35
|
* mod_mam: Add support for page flippingKim Alvefur2020-11-301-3/+8
| | | | | This was easy. Needs tests tho, 100% chance of the logic being backwards.
* mod_mam: Advertise extended MAM 0.7.x behind a feature flagKim Alvefur2020-11-301-1/+12
| | | | | | | In order to ease testing until the extended feautres are all implemented. Also TODOs for all the sub-features.
* mod_csi_simple,mod_carbons,mod_mam: Update comment about XEP-0353Kim Alvefur2021-01-081-1/+1
| | | | It went back to Deferred
* mod_mam: Archive XEP-0353: Jingle Message InitiationKim Alvefur2020-05-091-0/+4
|
* MAM: Remove 1% of contents when reaching limits, fix #1545Kim Alvefur2020-05-051-1/+3
| | | | | | With mod\_storage\_internal this counts out to 100 messages out of 10 000, meaning should not hit the quota limit immediately until that many messages have been added again.
* mod_mam: Store only incoming errorsKim Alvefur2020-04-261-3/+4
| | | | | Unclear if clients normally ever send error messages, but there may be locally generated bounces sent on behalf of local sessions.
* mod_mam: Remove unused variables [luacheck]Kim Alvefur2020-04-231-4/+0
| | | | Logic using full vs bare JID addressing may return in the future.
* mod_mam: Don't store any groupchat messagesKim Alvefur2020-04-231-1/+3
| | | | | | | | The intent was to not store MUC groupchat messages, which are sent from the MUC to local full JIDs, while allowing for potential future account based group chat. However, since this function handles messages in both directions and outgoing MUC messages are sent to the bare room JID, those were stored.
* mod_mam: Make note of Experimental (or Deferred) XEPsKim Alvefur2020-04-221-0/+3
| | | | | Since these XEPs are subject to change we may need come back and double check these in the future.
* mod_mam: Save delivery failures (thanks Ge0rG)Kim Alvefur2020-04-221-0/+3
| | | | | Makes it possible to learn of delivery failure even if it came bouncing back while you were offline.
* mod_mam: Keep chat markers (thanks Ge0rG)Kim Alvefur2020-04-221-0/+3
|
* mod_mam: Respect no-store hint (thanks Ge0rG)Kim Alvefur2020-04-221-1/+2
| | | | | no-store is used in an example in XEP-0313, so obviously this is the preferred hint
* mod_mam: Fix typo in commentKim Alvefur2020-04-211-1/+1
| | | | If it is with a body then it execution does not get this far
* mod_mam: Prefer not archiving if no interesting payloads are foundKim Alvefur2020-04-211-1/+3
|
* mod_mam: Check sender of error instead of receiverKim Alvefur2020-04-211-0/+3
| | | | | | The intent is to capture errors to stanzas sent by the local user, so that they can see why a message failed to be delivered even if the error came after they went offline.
* mod_mam: Store XEP-0184 receipts and requestsKim Alvefur2020-04-211-0/+5
| | | | Happy now Ge0rG?
* mod_mam: Add more positive hints for storageKim Alvefur2020-04-211-0/+12
| | | | Mostly just lifted from mod_csi_simple
* mod_mam: Rework hints handlingKim Alvefur2020-04-211-7/+6
| | | | Improved readability and early returns definite yes/no answer.
* mod_mam: Invert check for typeKim Alvefur2020-04-211-5/+13
| | | | | This is based on code in mod_csi_simple and aiming towards being more flexible and maintainable than a couple of tests for when not to store.
* mod_mam: Log 'why' a stanza is archivedKim Alvefur2020-04-211-1/+1
| | | | | Logging of 'why not' is already done. Why not both? Will make more sense when the rules evolve a bit.
* mod_mam: Factor out "should we store this" into a functionKim Alvefur2020-04-211-13/+21
| | | | | Meant to improve readability and ease further improvements to this algorithm.
* Merge 0.11->trunkKim Alvefur2020-03-111-1/+5
|\
| * mod_mam,mod_muc_mam: Allow other work to be performed during archive cleanup ↵Kim Alvefur2020-03-111-1/+5
| | | | | | | | | | | | | | | | | | | | | | (fixes #1504) This lets Prosody handle socket related work between each step in the cleanup in order to prevent the server from being completely blocked during this. An async storage backend would not need this but those are currently rare.
| * mod_mam: Fix rebase mistake [luacheck]Kim Alvefur2019-12-241-1/+1
| | | | | | | | The 'err' was there in trunk
* | Merge 0.11->trunkKim Alvefur2019-12-241-14/+57
|\ \ | |/ |/|
| * mod_mam: More careful validation of MAM query formKim Alvefur2019-12-231-1/+9
| | | | | | | | Adapted from mod_muc_mam
| * Merge 0.11->trunkMatthew Wild2019-10-031-0/+2
| |\
| * | plugins: Remove tostring call from loggingKim Alvefur2019-07-301-2/+2
| | | | | | | | | | | | | | | | | | Taken care of by loggingmanager now Mass-rewrite using lua pattern like `tostring%b()`
| * | mod_mam: Report correct count of results for forward queriesKim Alvefur2019-07-131-1/+1
| | | | | | | | | | | | | | | #results is only correct for backwards queries, the table is unused for forward queries.
| * | mod_mam: Move final log message to end of query procedureKim Alvefur2019-07-111-3/+3
| | |
| * | mod_mam: Log RSM parametersKim Alvefur2019-07-111-0/+3
| | | | | | | | | | | | | | | Helps when trying to figure out why some queries fail, ie when paging using an archive id that doesn't exist.
| * | mod_mam: Log query failure reasonKim Alvefur2019-07-111-0/+1
| | | | | | | | | | | | | | | The storage engine will usually make a lot of noise for serious errors, but not always.
| * | mod_mam: Log more details in final log messageKim Alvefur2019-07-111-1/+1
| | | | | | | | | | | | Saves you from counting messages sent
| * | mod_mam: Include query id in final log messageKim Alvefur2019-07-111-1/+1
| | | | | | | | | | | | Should make it easier to find related log messages
| * | mod_mam: Use stanza id in log message as fallback if no query idKim Alvefur2019-07-111-1/+1
| | |
| * | mod_mam: Include username that performed queryKim Alvefur2019-07-111-1/+2
| | | | | | | | | | | | Not always easy to find from surrounding logs
| * | mod_mam: Make log message more compactKim Alvefur2019-07-111-4/+5
| | |
| * | Merge 0.11->trunkKim Alvefur2019-05-271-2/+7
| |\ \
| * | | mod_mam: Propagate item-not-found to client (fixes #1325)Kim Alvefur2019-05-051-1/+5
| | | |
| * | | mod_mam: On quota hit, separately delete by time and by item countKim Alvefur2019-03-221-3/+11
| | | | | | | | | | | | | | | | | | | | This is to work around a possible SQL issue where offsets and time stamps don't interact correctly.
| * | | mod_mam: Trim archive when quota has been exceededKim Alvefur2017-11-071-3/+18
| | | |
| * | | Merge 0.11->trunkKim Alvefur2019-03-221-1/+1
| |\ \ \
| * | | | mod_mam: Fix operator precedence (thanks mimi89999)Kim Alvefur2019-01-201-1/+1
| | | | |
| * | | | mod_mam: Handle expiry of messages that expire in the middle of the cut-off dayKim Alvefur2019-01-061-2/+6
| | | | |
| * | | | mod_mam: Measure how long it takes to run the message expiry job jobKim Alvefur2019-01-061-0/+3
| | | | |
| * | | | mod_mam: Fix word order in log messageKim Alvefur2019-01-041-1/+1
| | | | |
| * | | | mod_mam: Perform message expiry based on building an index by dateKim Alvefur2019-01-031-31/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For each day, store a set of users that have new messages. To expire messages, we collect the union of sets of users from dates that fall outside the cleanup range. The previous algoritm did not work well with many users, especially with the default settings.
* | | | | mod_mam: Schedule cleanup again if unable to delete messagesKim Alvefur2019-12-241-0/+1
| | | | |
* | | | | mod_mam: Log error when unable to delete old messages (fix #1479) [luacheck]Kim Alvefur2019-12-241-0/+2
| | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 02:19:18 +0000