Skip to content

disable bcc_self on new installations #733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
r10s opened this issue Oct 21, 2019 · 1 comment · Fixed by #825
Closed

disable bcc_self on new installations #733

r10s opened this issue Oct 21, 2019 · 1 comment · Fixed by #825
Assignees
Labels
enhancement New feature or request

Comments

@r10s
Copy link
Contributor

r10s commented Oct 21, 2019

  • bcc_self should be disabled on new installations to mitigate annoyances on first time installation, eg. this would avoid double-notfications.

  • when an autocrypt-setup-message is really sent or received successfully, it is enabled implicit.
    EDIT: no, see comment below

  • for existing installations, bcc_self should not be changed

@r10s r10s added the enhancement New feature or request label Oct 21, 2019
@r10s r10s self-assigned this Oct 29, 2019
@r10s
Copy link
Contributor Author

r10s commented Nov 7, 2019

when an autocrypt-setup-message is really sent or received successfully, it is enabled implicit.

no. we should not try to be too smart here. enabling/disabling settings after first-time-installation might be even more annoying to the user.

instead of implicitly changing things, a message should be added to the new device-chat when multi-device is detected in some way. to keep things simple for now, the message should just explain what to do, having some click-here-to-edit-x seems to be a bit out of scope - and maybe not needed at all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant