* apply token changes on leaving the dialog; this avoids unnecessary changes, races or possibly needed blocks if the user is just playing around
* ask before disabling PUSH; this is mainly to avoid accidental taps
* add a 'learn more' button pointing to instant-delivery
* add a switch for push notifications
* move 'instant delivery' down
* reword to 'force background connection'
* remove unused string
* respect user setting wrt pref_push_enabled
* f-droid defaults to PUSH = false
* get token directly when enabling PUSH
* delete FCM token when PUSH is disabled
* reword 'QR code' to 'Invite Code'
* reword adding classic email
* remove the 'new contact' things together
* add 'new classic contact' shortcut only for non-chatmail; it is still always available in the three-dot menu of 'new contact'
* use same menu for qr show/scan
* add 'new classic contact'
* remove 'scan' button from 'new classic contact' (ppl usually came from 'scan')
* rename to 'add contact manually'
* stay with 'qr code' for now
* add submenu to 'Explore Other Options'
* move 'Manual Login' to 'Explore Other Options'
* clearer titles, even if they are repetive
* move 'Scan QR' to 'Other'; this allows us to make 'Other' more outstanding
* cleanup layout
* tweak wording to 'Use Other Server' pointing to 'List in Browser', 'Classic Login', 'Scan Invite Code'
* use a standard secondary button for 'Use Other Server'
* show default onboarding server name
* reword to 'List Chatmail Servers'
* always close other-sign-up-options on tapping an option
* clarify that 'classic login' is about e-mail
'Signature' is very much related to email, sth. below the text,
this is not the case for Delta Chat, esp. not when using chatmail
'Status' implies that others may be aware of changes,
which is not the case as well.
therefore we'll try 'Bio' - which is also used by by 'Telegram', 'Github', 'Mastodon';
(whatsapp and signal use 'About', but we were failing to get a good hint for that :)
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 )
* 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
the hint already led to confusion on 37c3 testings of chatmail.
the hint that appears when a one-to-one-chat was just created manually
(by entering an email address manually) is a bit misleading when using chatmail,
as it says it 'does not matter if the other side uses Delta Chat'.
this is still true, however, with chatmail it is needed that messages
outside the chatmail-server are encrypted,
which is arguably not so easy without delta chat and QR code scanning.
this PR therefore just removes the hint;
it would still be great if the error message 'cannot encrypt' is improved,
however, this is another thing.
bjoern