| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This led to a missing 'when' field on changed items, which would cause a
traceack.
|
| |
|
|
|
|
|
|
| |
A protocol built on this API now allows showing a list of unread
conversations with a counter, ordered by either oldest or newest
message, along with the text body itself.
|
|
|
|
|
| |
For completeness along with most recent timestamp. Might be nice to be
able to order by oldest unread message.
|
|
|
|
|
|
|
| |
Clients may want to show a list of conversations ordered by how
timestamp of most recent message.
The counts allow a badge with unread message counter.
|
|
|
|
| |
Eg might want to include last message, timestamp, chat state or other info.
|
| |
|
|
|
|
| |
(partial fix for #1325)
|
|
|
|
| |
May help with writing a better migrator
|
| |
|
|
|
|
| |
contact
|
| |
|
|
|
|
|
|
| |
Performance doesn't seem great but 10k should be far enough from limits
inherited by the Lua parser. 1000 messages seemed pretty close to what
an active user might produce in one week.
|
| |
|
|
|
|
| |
This was planned to be added long ago but was forgotten.
|
|
|
|
| |
(fixes #733)
|
| |
|
| |
|
| |
|
|
|
|
| |
an archive store
|
| |
|
|
|
|
| |
mod_storage_sql)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
but keyval) store types
|
|
|
|
| |
data in a store
|
|\ |
|
| |
| |
| |
| | |
list_stores() with an iterator version
|
| |
| |
| |
| | |
modules.
|
|/
|
|
| |
allow using module:provides().
|
| |
|
| |
|
|
mod_storage_internal, and greatly simplify storagemanager's error handling and fallback code
|