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
- remove useless comment that just says the obvious thing
- use same annotation as super class
- remove Scrubber class; that replaces some number in upstream,
this is not needed for Delta Chat
* hide AddReactionView when user clicks on the attachments buttons
* use new hideAddReactionView() also at existing places to simplifies code understanding and maintainance (having one single point that does the hiding)
---------
Co-authored-by: B. Petersen <r10s@b44t.com>
on new installations or accounts,
the "What's new?" messages only clutter the device messages
with unimportant information
(either the user is new to the app, so everyrhing is new and nothing is changed,
or an existing user has created a new account,
they have seen the changelog anyways)
in other words,
the changelog will be added only for updates.
when reading https://c.delta.chat/classdc__context__t.html#a1a2aad98bd23c1d21ee42374e241f389 ,
this was always the gist,
however, somehow forgotten or removed on the way :)
targets #2914
'pinned' chats are always shown together below each other;
moving the 'pinned' indicator to the same position in each chat
makes the UI a little less cluttered and nicer
(all pinned indicators will form a column if you will)
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