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

Discuss: Kicking out Fitbit, using OpenHumans #392

gedankenstuecke opened this Issue Jun 6, 2017 · 4 comments


None yet
3 participants

gedankenstuecke commented Jun 6, 2017

Today @tsujigiri, @madprime and I discussed a bit about the possibility to remove our (broken, see #252) Fitbit integration and replacing it with a far simpler integration of OpenHumans. (context: @tsujigiri and I had discussed the feature creep in openSNP some months back and I think it would be a good opportunity to do so).

The OpenHumans API allows to easily list all the public data sources that people have. On our end we could use their OAuth2 integration to just link OpenHumans accounts to openSNP accounts. On our end we could just store

  1. the OpenHumans username
  2. the Public Data sources that this user has on OpenHumans.

That way we could easily add this two bits of information into our phenotypes.csv and people who are really interested in this could easily download the data via the OpenHumans-API, we don't have to fix the Fitbit integration and there's no data duplication going on. What's your take on it? 😄


This comment has been minimized.


philippbayer commented Jun 7, 2017


The Fitbit integration likes to break and this gives us the opportunity to add more data while having to implement only one API integration.

What do we do with the 'old' Fitbit data then? Just delete it all? Keep legacy around?


This comment has been minimized.


gedankenstuecke commented Jun 7, 2017

I'd say we point people who're having a Fitbit connection set up to OpenHumans and delete the data after some grace period, so that people can backup the data that's on openSNP so far?


This comment has been minimized.

BenjaminHCCarr commented Aug 24, 2017

I would support this.
line 144 of: view-source:
<h4><a class="btn btn-info" href="/fitbit/start_auth">Connect your Fitbit account with openSNP</a></h4>
leads to the errror on of


500: Something broke.
If it keeps on doing this, please send us an e-mail: {info at opensnp dot org}.

hat tip, I may also be slightly biased in favor of @OpenHumans anyway


This comment has been minimized.


gedankenstuecke commented Aug 25, 2017

Yeah, that's still of our todo, if someone wants to take on this job prior to me being done with thesis writing: Please go ahead, and be aware that there's a $5,000 grant opportunity from Open Humans which could support exactly this work. 💰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment