| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
resource we asked for)
Some servers give out random resources. Then, we didn't deduplicate own messages afterwards because we saved the wrong resource.
|
|
|
|
| |
iterating over it)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
request_info/items async, add caching has_entity_feature
|
| |
|
|
|
|
| |
fixes #756
|
|
|
|
|
| |
fixes #179
fixes #812
|
| |
|
|
|
|
|
| |
Fixes #791 where a signal to update the UI is sent to
late when sending files, resulting in an out of sync
conversations list.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes #591
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It is especially important for OMEMO database, as it stores *ephemeral* keys
|
|
|
|
| |
fixes #748
|
|
|
|
| |
fixes #739
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also show "Me" when no local alias is set instead of JID
|
| |
|
|
|
|
| |
fixes #470
|
| |
|
|
|
|
| |
fixes #669
|
|
|
|
| |
Fixes #248, #643
|
| |
|
| |
|
| |
|
|
|
|
| |
Mss are striped when storing in db. Comparing messages with and without ms might lead to wrong orderings. Related: Message duplication in UI when scrolling up.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
fixes #675
|