Sat, 31 Aug 2019 16:08:45 +0200 MUC: Fix delay@from to be room JID (fixes #1416) 0.11 0.11.3
Kim Alvefur <zash@zash.se> [Sat, 31 Aug 2019 16:08:45 +0200] rev 10234
MUC: Fix delay@from to be room JID (fixes #1416)
Sat, 31 Aug 2019 16:04:50 +0200 MUC: Add a test covering basic room creation, messages and destruction
Kim Alvefur <zash@zash.se> [Sat, 31 Aug 2019 16:04:50 +0200] rev 10233
MUC: Add a test covering basic room creation, messages and destruction
Wed, 28 Aug 2019 01:41:00 +0200 net.server_epoll: Add support for opportunistic writes
Kim Alvefur <zash@zash.se> [Wed, 28 Aug 2019 01:41:00 +0200] rev 10232
net.server_epoll: Add support for opportunistic writes This tries to flush data to the underlying sockets when receiving writes. This should lead to fewer timer objects being around. On the other hand, this leads to more and smaller writes which may translate to more TCP/IP packets being sent, depending on how the kernel handles this. This trades throughput for lower latency.
Sun, 25 Aug 2019 23:25:42 +0200 core.certmanager: Remove unused import [luacheck]
Kim Alvefur <zash@zash.se> [Sun, 25 Aug 2019 23:25:42 +0200] rev 10231
core.certmanager: Remove unused import [luacheck]
Sun, 25 Aug 2019 23:12:55 +0200 Remove COMPAT with temporary luasec fork
Kim Alvefur <zash@zash.se> [Sun, 25 Aug 2019 23:12:55 +0200] rev 10230
Remove COMPAT with temporary luasec fork The changes in the temporary fork were merged into mainline luasec ca 2013 and included in the 0.5 release in 2014.
Sun, 25 Aug 2019 21:31:04 +0200 MUC: Simplify nickname refresh loop
Kim Alvefur <zash@zash.se> [Sun, 25 Aug 2019 21:31:04 +0200] rev 10229
MUC: Simplify nickname refresh loop Affiliation data is passed as a loop variable so no need to retrieve it
Sun, 25 Aug 2019 20:22:35 +0200 core.certmanager: Move EECDH ciphers before EDH in default cipherstring
Kim Alvefur <zash@zash.se> [Sun, 25 Aug 2019 20:22:35 +0200] rev 10228
core.certmanager: Move EECDH ciphers before EDH in default cipherstring The original intent of having kEDH before kEECDH was that if a `dhparam` file was specified, this would be interpreted as a preference by the admin for old and well-tested Diffie-Hellman key agreement over newer elliptic curve ones. Otherwise the faster elliptic curve ciphersuites would be preferred. This didn't really work as intended since this affects the ClientHello on outgoing s2s connections, leading to some servers using poorly configured kEDH. With Debian shipping OpenSSL settings that enforce a higher security level, this caused interoperability problems with servers that use DH params smaller than 2048 bits. E.g. jabber.org at the time of this writing has 1024 bit DH params. MattJ says > Curves have won, and OpenSSL is less weird about them now
Fri, 23 Aug 2019 01:28:53 +0200 mod_storage_internal: Include last text message
Kim Alvefur <zash@zash.se> [Fri, 23 Aug 2019 01:28:53 +0200] rev 10227
mod_storage_internal: Include last text message 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.
Fri, 23 Aug 2019 01:15:44 +0200 mod_storage_*: Also include timestmap of first message in :summary API
Kim Alvefur <zash@zash.se> [Fri, 23 Aug 2019 01:15:44 +0200] rev 10226
mod_storage_*: Also include timestmap of first message in :summary API For completeness along with most recent timestamp. Might be nice to be able to order by oldest unread message.
Fri, 23 Aug 2019 01:10:27 +0200 mod_storage_*: Include timestamp of latest message in :summary API
Kim Alvefur <zash@zash.se> [Fri, 23 Aug 2019 01:10:27 +0200] rev 10225
mod_storage_*: Include timestamp of latest message in :summary API 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.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip