Hocuri 5711f2fe3a feat: More context for the "Cannot establish guaranteed..." info message (#6022) ...

The "Cannot establish guaranteed end-to-end encryption with ..." info
message can have lots of causes, and it happened twice to us now that it
took us some time to figure out which one it is.

So, include some more detail in the info message by simply adding the
non-translated error message in parantheses.

If we want to put in some more effort for nicer error messages, we
could:
- Introduce one new translated string "Cannot establish guaranteed
end-to-end encryption with …. Cause: %2$s" or similar (and remove the
old stock string)
- And/Or: Introduce new translated strings for all the possible errors
- And/Or: Maybe reword it in order to account better for the case that
the chat already is marked as g-e2ee, or use a different wording
(because if the chat is marked as g-e2ee then it might be nice to notify
the user that something may have gone wrong, but it's still working,
just that maybe the other side doesn't have us verified now)


![Screenshot_20241003-222245](https://github.com/user-attachments/assets/c064c82e-01ac-4bac-ab11-3c9ac9db5298)

2024-10-04 13:51:06 +02:00

..

bob.rs

feat: More context for the "Cannot establish guaranteed..." info message (#6022)

2024-10-04 13:51:06 +02:00

bobstate.rs

feat: Scale up contact origins to OutgoingTo when sending a message

2024-05-21 17:40:07 +00:00

qrinvite.rs

chore: fix 2024-03-05 nightly clippy warnings

2024-03-08 02:53:47 +00:00