| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
attribute is set
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
shut down presence
|
| |
|
| |
|
| |
|
|
|
|
| |
with message
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and waiting for sm catchup
|
| |
|
|
|
|
|
|
|
| |
Apparently nimbuzz.com doesn't include status code 110 in muc self
presence
It does however include the full real jid in the presence’s item.
We can use that as a work around to detect a self presence.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
52a2efe0a87d6422060e78e0ca7df38c2affd2f2
|
|
|
|
|
|
|
| |
wait for a first SM ACK before calculating if we need to trigger any
notifications
might have to be changed to an XEP-0199 ping later on. for now sending
<r/> after resume seems to work outfine
|
|
|
|
| |
…in Conversations only enviroments
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|