Skip to content
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

obscure private device provenance #7249

Merged
merged 6 commits into from
Dec 15, 2021
Merged

obscure private device provenance #7249

merged 6 commits into from
Dec 15, 2021

Conversation

bewest
Copy link
Member

@bewest bewest commented Dec 14, 2021

Allow users to choose whether or not to reveal the provenance of the data to
consumers. This is intended to help protect data rights to portability and
access. If consumers start abusing or discriminating against Nightscout users
due to the source of the data, this allows users to conceal this information.

Allow users to choose whether or not to reveal the provenance of the data to
consumers.  This is intended to help protect data rights to portability and
access.  If consumers start abusing or discriminating against Nightscout users
due to the source of the data, this allows users to conceal this information.
Disregard brand of device when considering glucose values.  By de facto usage,
the meaning of LOW and HIGH within Nightscout means that glucose is beyond limits.
LOW means 40 or lower.  HIGH means 400 or higher.  Both tend to invite
questioning therapy options, including inspecting if the device is working
correctly, as well as potential treatment options.
The results to render may come from an in-memory cache, or from the database.
If they came from the in-memory cache, it's possible that obscurring the device
field could actually change the values in memory.  When obscurring, the device
field, this patch copies all of the values in order to ensure that the
in-memory copies are unaffected.  With this patch, cached objects should not be
affected.
With this change, any code referencing the sandbox or /api/v2/properties for
plugin will also benefit from having the device information obscured.
…/cgm-remote-monitor into wip/bewest/obscure-provenance
@bewest bewest merged commit 5ceb82d into dev Dec 15, 2021
@sulkaharo sulkaharo deleted the wip/bewest/obscure-provenance branch December 30, 2022 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants