Age | Commit message (Collapse) | Author |
|
|
|
Sorry Link Mauve
|
|
|
|
|
|
|
|
|
|
|
|
add a log because it should not happen
|
|
Makes letsencrypt renewals more pleasant.
Thanks jonasw and aioxmpp for the ASN.1 wizardry
|
|
Keep all presence before status code=110 in a buffer, then batch-process
them when receiving our initial join.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Less eye travel for short statuses.
(patch from Ge0rG)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Implements XEP-0084 and XEP-0153.
|
|
This adds an optional dependency on PIL.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
When a user isn't in a room, but due to a component bug we receive a
unavailable presence, we were showing a join.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
exit the rooms properly, call functions instead of full-blown commands,
do not randomly focus stabs, etc
|
|
Fixes #3186.
|
|
The problem is that core.legitimate_disconnect is set to True in the
on_connecting callback which is called before the session_end for some
reasons. on_connecting sets core.legitimate_disconnect back to False so
session_end thinks we've been disconnected and connects automagically
adding a resource and thus duplicating everything.
Moving the reset of legitimate_disconnect to the on_connected callback
fixes the problem.
|
|
… it's about time I fixed this
|