Skip to content
This repository has been archived by the owner on Oct 6, 2022. It is now read-only.

decide whether to store historical glucose values #8

Open
awaxa opened this issue Nov 5, 2015 · 3 comments
Open

decide whether to store historical glucose values #8

awaxa opened this issue Nov 5, 2015 · 3 comments

Comments

@awaxa
Copy link
Member

awaxa commented Nov 5, 2015

cases for anonymized data:

cases that anonymized data precludes:

  • reimplement the lastbgs command from reddit-diabetes/diabot-plugins

Please suggest other uses for the data!

@awaxa
Copy link
Member Author

awaxa commented Nov 5, 2015

I think the lastbgs command helped users relate about having a bad day with their readings, but the downsides or code complexity involved may outweigh the small benefit:

  • users will want to amend records they mistype
  • some will want not want to have their data stored
  • we had to manually drop some records from the old sqlite db after a user threw a tantrum to the freenode admins

@liz-baker
Copy link

@cascer1 @awaxa bumping this for comments. I think if we do this we make it ephemeral and only store it in redis. Also it seems like a lot of work for very little payoff, although since the Discord is pretty popular now maybe they would want this?

@awaxa
Copy link
Member Author

awaxa commented Jun 25, 2017

I had forgotten all about this note!

Diabot's redis store is not perfectly ephemeral, and unfortunately it won't start without it. I flushed a couple thousand username to uuid mappings out of it today.

I think I remember users asking for logs from the supybot plugin and expecting more than a sql dump.

@dosman711 I agree with you about work/payoff, and I worry that we could easily spend more time supporting the feature than we should.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants