-
-
Notifications
You must be signed in to change notification settings - Fork 109
Opt-in weekly sending of statistics #6851
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hocuri
added a commit
to deltachat/deltachat-android
that referenced
this pull request
May 12, 2025
Counterpart of chatmail/core#6851
a4d64cb
to
5619601
Compare
3 tasks
Hocuri
added a commit
to deltachat/deltachat-android
that referenced
this pull request
Jun 25, 2025
Counterpart of chatmail/core#6851
285d80a
to
416131b
Compare
932b191
to
8895fd8
Compare
511aaa9
to
966124a
Compare
966124a
to
b1c57ee
Compare
Hocuri
added a commit
to deltachat/deltachat-android
that referenced
this pull request
Aug 15, 2025
Counterpart of chatmail/core#6851
6b9f05f
to
4314864
Compare
iequidoo
reviewed
Aug 17, 2025
iequidoo
reviewed
Aug 19, 2025
This way, the statistics / self-reporting bot will be made into an opt-in regular sending of statistics, where you enable the setting once and then they will be sent automatically. The statistics will be sent to a bot, so that the user can see exactly which data is being sent, and how often. The chat will be archived and muted by default, so that it doesn't disturb the user.
Co-authored-by: Simon Laux <[email protected]>
iequidoo
reviewed
Oct 16, 2025
iequidoo
reviewed
Oct 16, 2025
iequidoo
reviewed
Oct 18, 2025
Simon-Laux
reviewed
Oct 20, 2025
link2xt
reviewed
Oct 20, 2025
iequidoo
approved these changes
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This way, the statistics / self-reporting bot will be made into an opt-in regular sending of statistics, where you enable the setting once and then they will be sent automatically. The statistics will be sent to a bot, so that the user can see exactly which data is being sent, and how often. The chat will be archived and muted by default, so that it doesn't disturb the user.
The collected statistics will focus on the public-key-verification that is performed while scanning a QR code. Later on, we can add more statistics to collect.
Context:
This is just to give a rough idea; I would need to write a lot more than a few paragraphs in order to fully explain all the context here.
End-to-end encrypted messengers are generally susceptible to MitM attacks. In order to mitigate against this, messengers offer some way of verifying the chat partner's public key. However, numerous studies found that most popular messengers implement this public-key-verification in a way that is not understood by users, and therefore ineffective - a 2021 "State of Knowledge" paper concludes:
This is why Delta Chat tries to go a different route: When the user scans a QR code (regardless of whether the QR code creates a 1:1 chat, invites to a group, or subscribes to a broadcast channel), a public-key-verification is performed in the background, without the user even having to know about this.
The statistics collected here are supposed to tell us whether Delta Chat succeeds to nudge the users into using QR codes in a way that is secure against MitM attacks.
Plan for statistics-sending:
TODO[blog post]
in the code)