l

> Also, what does TUI mean here? Text-based User Interface, e.g. https://github.com/adbenitez/deltachat-cursed

Failed attempt to do it with `surf` library: #2782 We need to redo the fix for the new `reqwest` library that we use now, maybe this time it will work.

Duplicate issue #2700 reported here: https://nitter.net/Alex_Helali/status/1440060286086443013

Probably makes sense to add CI test for `cargo vendor`?

My proposal is to deprecate `dc_add_contact_to_chat` and `dc_remove_contact_from_chat`, and replace them with `dc_add_contact_to_msg(context, dc_msg_t *msg, contact_id)` and `dc_remove_contact_from_msg`. This way member list changes can be attached to messages just like...

Maybe also introduce `dc_msg_set_chat_id`, so chat ID can be set before sending the message and the core can check if membership changes are valid for this chat. The second argument...

It requires changes, but will be compatible so no problem if it's implemented only on one platform at first. Without changing UI the best thing that can be done is...

It is sort of expected according to this comment: https://github.com/deltachat/deltachat-core-rust/blob/a4486d8c300338769a1e487bca7b1c42b0eb99be/src/job.rs#L380 `message::exists` checks if the message exists and is not in the trash chat. As for starting the timer when message...

> I have just found out that group rename system messages are ephemeral and therefore affected as well, so another Delta Chat client using the same account is never informed...

I'm even ok with hardcoded rewrite of anything that ends with `.hermes.radio` with `hermes.radio` during provider lookup. We can generalize later if more providers require it.