iequidoo

fix: Create new Peerstate for unencrypted message with already known Autocrypt key, but a new address

7

See commit messages. This is aimed to solve the @adbenitez's problem with sharing the same key by several accounts.

See commit messages. Also need to think how to add at least some tests for this.

feat: Sync chats deletion across devices

6

**feat: Sync chats deletion across devices** Motivation: Now broadcast lists creation is synced across devices. Groups creation, in some means, too -- on a group promotion by a first message....

feat: Use random filenames for blobstorage (#4309)

6

### Based on #5495 See commit messages. See also the discussion here: https://github.com/deltachat/deltachat-core-rust/pull/4555. Close #4309 Fix #5338

api!: Remove msg_id (last message ID) from Chatlist::get_summary2() (#3071)

10

See commit messages.

Accordingly, there's no need in `Peerstate` for self addresses (and in the db too).

Follow-up to 5fa7cff46. Let's still not send a sync message if the contact wasn't modified. This is not very important, but just for consistency with the `chat::rename_ex()` behaviour.

This way it's clearer which key is which and also adding the key fingerprint to the file name avoids overwriting another previously exported key. I think this is better than...

feat(ffi): Add DC_STR_CANT_DECRYPT_OUTGOING_MSGS define

5

As @gerryfrancis said, > FYI, I have gotten this system message after I created new DC profiles (for testing), but the device has been the same since. Although I know...

This needs a test, the test in the first commit is unrelated. @adbenitez, i can't reproduce #5514, the test in the first commit just works. Maybe you can clarify the...