iequidoo

I thought of smth like `CommandApi::require_version(usize)`, but such an approach isn't generic, it doesn't help with signature changes, so maybe just rename `FullChat` to `FullChat2` so that all users are...

I'm not sure about not sorting up, but agree with wrt group unarchiving and creation. If i added someone to a group then it may be interesting to me that...

For some reason i couldn't reproduce this, i tried Gmail and a chatmail (nine) for Alice. Bob was using a chatmail in both cases. It looks like your Alice on...

Let's close this as a duplicate of #5354 for now

The reason is apparently message reordering. First you received some message where K is already in the Chat-Group-Past-Members list instead of "To", then you received the actual message removing K...

Maybe. Anyway, we shalln't move the message that was already added to the chat (because if you sent some messages in between, it would be unclear if the removed member...

> whether to allow adding a contact by email address Note that even now chatmail users can have email-address-contacts, e.g. if an encrypted multi-recipient message arrives -- it will be...

Supporting multi-transport for unencrypted messages isn't necessary, instead we could: - Allow unencrypted messaging if the primary address is non-chatmail. - Use multi-transport only for encrypted messages. This way a...

So "unencrypted messaging" is controlled by the user. But this doesn't make it impossible to only use multi-transport for encrypted messages and the primary transport for unencrypted (if the user...

> The problem with `MsgsNoticed` event is that it does not tell which messages are noticed [...] Exactly. The current approach is to emit `MsgsNoticed` and effectively remove all notifications...