~singpolyma/biboumi

ref: 760076a33aa50c700bc0d825e5cb9d0fa9d5bd17 biboumi/src/xmpp/biboumi_component.cpp -rw-r--r-- 42.8 KiB
760076a3 — louiz’ 4 years ago
Make the global ad-hoc configure command available in fixed mode

fix #3360
b0168fd4 — louiz’ 4 years ago
mam: Send “fin complete” only when appropriate

Also simplify how we did the whole “limit + 1”
And fix one bad interpretation of the XEP for the case where the query has
no after or before restriction.

fix #3349
61de6b1d — louiz’ 4 years ago
Revert "Use a different Date data type"

This reverts commit 857c7d3972a03cbeebf730d99b924d3710dee6a0.
a90f196a — louiz’ 4 years ago
Revert "Use the Date to find a next page in RSM, not the id"

This reverts commit 5ef7ba08028065b03d51d1dc70bb35aeb41ae19d.
0d487f40 — Emmanuel Gil Peyrot 4 years ago
Use Config::is_in_list() to allow for multiple admins
5ef7ba08 — louiz’ 4 years ago
Use the Date to find a next page in RSM, not the id

This way, it works, whatever the order of insertion in the database was.

fix #3343
d375a9ed — louiz’ 4 years ago
one log_debug -> log_error, also some trivial indent
857c7d39 — louiz’ 4 years ago
Use a different Date data type

PLEASE backup your database before testing this commit, and report any
migration issue.

In postgresql, we use timestamp with timezone.
In sqlite3 we use REAL (the date is expressed as julianday)

This requires a migration of the muclogline_ table:
In postgresql it’s pretty simple, we convert all the integer into timestamps

With sqlite3, we actually rename the table, create the new one with the
correct type, then copy everything to the new table, with a conversion
function for the Date_ column, and then we delete the old table.

fix #3343
49bb3830 — Georg Lukas 4 years ago
Channel disco-info: use shorter string
d81a9456 — louiz’ 4 years ago
Change the nick of the joining user AFTER sending all the join stuff

fix #3305
e2fc3cf6 — louiz’ 4 years ago
Properly handle force-join presences by sending everything in return

fix #3305
0de282a1 — louiz’ 4 years ago
Advertise the muc#stable_id feature on disco#info results

From XEP 0045:
“Note: the requirement to reflect the 'id' attribute was added in version
1.31 of this XEP. Servers following the new specification SHOULD advertise
that with a disco info feature of 'http://jabber.org/protocol/muc#stable_id'
on both the service domain and on individual MUCs, so that clients can check
for support.”
9500bfd4 — louiz’ 4 years ago
Reflect message IDs in channel MUCs

fix #3283
158d743b — louiz’ 4 years ago
Remove the virtual channel feature altogether
4a2a280d — louiz’ 4 years ago
Support the <before/> element in MAM requests
50d3c4a0 — louiz’ 4 years ago
Do not forget an early return, to return the correct item-not-found error
d7055414 — louiz’ 4 years ago
Send a item-not-found error when the “after” value is not in the archive
0280343c — louiz’ 4 years ago
Handle the “after” RSM value to page through results
99389eef — louiz’ 4 years ago
Always return the oldest matching messages from MAM, even if no date is set
369da19d — louiz’ 5 years ago
Remove the debug logs from previous commit
Next