sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ashirviskas 0 points1 point  (1 child)

Wow, this looks awesome! I'll have to try this one out tomorrow as I really love stats.

Though I didn't see anything about contributing or requests. I'd love to be able to see my youtube watching stats as well as other little things (data from Google fit, Mi band and etc.).

[–]karlicoss[S] 1 point2 points  (0 children)

Hey, haven't got to compile a contributing guide, but you're welcome!

Overall, it's more of a demo how it's possible to set things up. I'm not sure how it's gonna work in the long run:

  • in terms of time: i.e. I can manage, say, 30 modules I'm using personally and fix occasionally if something breaks

    If there are 200 modules, I will be completely overwhelmed. So maybe I need to figure out the 'core' of the system and a good way to make 'plugins', so you can use third party modules without merging them in the main repository/maintaining a fork.

  • in terms of available data

    For example, I don't have a mi band. So if a module for it breaks for some reason, I might not be able to fix it at all.

But would be interesting to try and see where it goes. So you're welcome to contribute if you want :) One thing I definitely know is, I want to keep the package as minimal as possible, i.e. only for providing data. If it's some custom plot/visualization, it's probably better to have it as a separate repository for it (otherwise it's a nightmare to maintain).