this fits better to chatmail:
- one can have chatmail=OFF and normal-mail=ON
- new accounts are most often chatmail,
even if there is a normal-mail account,
and get the setting OFF,
which is better in most cases
with chatmail, providers exist that allow to send encrypted mails only.
pulling in the system address book unconditionally for chatmail will harm UX
as for most of these addresses,
no public key will be known until eg. a QR code is scanned.
we may think this over in the future.
note, that one usually also can create a Delta Chat chat from the address book,
so, this works also without having Delta Chat pulled in all addresses
(which has some issues, https://github.com/deltachat/deltachat-android/issues/2923 )
* copy invite links to clipboard
* rename INVITE_PAGE to INVITE_DOMAIN
* share link together with QR image, improve QR image
* share invite-URL instead of QR image
* 'Load QR code from image' is no longer a recommended workflow
the primary UI works with invite-links now.
'Load QR code from image' is still supported,
but is tuned down as no longer recommended workflow.
---------
Co-authored-by: B. Petersen <r10s@b44t.com>
* add strings for 'Invalid Unencrypted'
* add a 'learn more' dialog for 'invalid unencrypted'; the dialog shows the known 'scan qr code' and the known help for it
* clarify wording, add 'for this chat'
* do not linkify domains
* draft a new welcome-message with focus about how to get in contact; the 'Invite Link' implies also contacts with delta chat not installed yet (we could also add a QR code to the invite page as well as adding a 'Manual contact' that fits for classic mail)
* add some dc background info
* rename 'Device Talk' to 'Info'
* Revert "rename 'Device Talk' to 'Info'"
This reverts commit 027e205718c2923bc774a2d069f3283fc9e0e7bd.
* improve english grammar, thanks @adzialocha
adbenitez