-
Notifications
You must be signed in to change notification settings - Fork 285
Consider completely disregarding irrelevant encounters #1380
Comments
Please see this Issue in the Wishlist Repo: Please note that the RKI already denied to show more Informations about Low Risk Encounters. But there are some open Issues in the Wishlist Repo requesting to show more Information about (Low) Risk Encounters, e.g. corona-warn-app/cwa-wishlist#178, corona-warn-app/cwa-wishlist#205, etc. So I think it would be good if we would close this Issue here and continue the Discussion in the Wishlist Repo, what do you think? |
You now changed the title, but also for this Request we have an open Issue in the Wishlist: 🙂 |
Hello @danielvonmitschke As @Ein-Tim pointed out, we already have several wishlist entries dealing with your request:
I would like to ask you to continue the discussion in these threads, so that the discussion about these features is not spread out and thus easier to follow. I will close your issue here and link it to the other threads as a duplicate Regards, Corona-Warn-App Open Source Team |
Duplicate of corona-warn-app/cwa-wishlist#181 |
Avoid duplicates
Current Implementation
Only low and high risk encounters are displayed. No additional information about the encounters is provided.
So a low risk encounter could either be a person quickly passing by in 20m distance or a person you are talking with in only 1m distance for quite some time but not matching the criteria to make this a high risk encounter.
Suggested Enhancement
Display statistical information about recorded risk encounters.
Or eliminate most low risk encounters where only the signal was received for a second or from a very far (calculated) distance.
Expected Benefits
Less confusion about low risk encounters.
Give users the possibility to evaluate low risk encounters themselves.
e.g. (assuming that I need to be talking 15min to someone for an encounter to be considered high risk):
If I have 4 low risk encounters where I talked 14min to someone is very different from having 4 low risk encounters where only a signal was received from another phone.
The text was updated successfully, but these errors were encountered: