From bdd23a5ff2d1d1e82a83f72c7889db33376ae50f Mon Sep 17 00:00:00 2001 From: Christian Schneppe Date: Sun, 8 Apr 2018 21:05:15 +0200 Subject: offer a more convienient way to disable omemo from trust keys dialog --- src/main/res/values/strings.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'src/main/res/values/strings.xml') diff --git a/src/main/res/values/strings.xml b/src/main/res/values/strings.xml index f5a6d80be..c2cb55f91 100644 --- a/src/main/res/values/strings.xml +++ b/src/main/res/values/strings.xml @@ -349,7 +349,7 @@ Are you sure you want to remove the verification for this device?\nThis device and messages coming from that device will be marked as untrusted. There are no usable keys available for this contact.\nFetching new keys from the server has been unsuccessful. Maybe there is something wrong with your contacts server. There are no usable keys available for this contact. If you have purged any of their keys, they need to generate new ones. - Error + Something went wrong Fetching history from server No more history on server Updating… @@ -764,4 +764,11 @@ Manage availability manually Automatically delete messages from this device that are older than the configured time frame. Automatic message deletion + Disable encryption + Conversations is unable to send encrypted messages to %1$s. This may be due to your contact using an outdated server or client that can not handle OMEMO. + Unable to fetch device list + Unable to fetch device bundles + Hint: In some cases this can be fixed by adding each other your contact lists. + Are you sure you want to disable OMEMO encryption for this conversation?\nThis will allow your server administrator to read your messages, but it might be the only way to communicate with people using outdated clients. + Disable now -- cgit v1.2.3