More field integrations

[lefnire]

Currently have Habitica, would like to integrate others.

• Weather API
• Fitbit
• What else?

[kamaradclimber]

I think it would be very valuable to expose an api to add/update fields before adding more integrations. Integrations are very valuable (habitica one provides a lot of information) but this excludes a lot of data that could be "pushed" by an external system.

It would let any user add fields for what is (possibly) relevant to their lifestyle and update them automatically.

Here are a few examples of fields I'd like to add but would probably not update every day due to the toil it would represent:

• day of the week (I know my mood is deeply affected by the day of the week)
• on holidays or at work (I already have a system that knows this so updating it automatically would be convenient)
• time slept (my watch knows this but it's not sent to any cloud so no integration would ever be exposing it for gnothi to fetch it)
• number of meetings during the day

I'd be glad to discuss this need further (could also open a separated issue of course)

[lefnire]

That's a much better idea. Let other devs handle the integration, just make sure my API is amenable (if you build it, they'll come). After I get the Groups branch pushed live, bugs ironed, etc; I'll revisit this thread and let see if we want to collaborate.

BTW, the Groups branch moves everything to Websockets (rather than REST). There's a lot of push stuff, so I figured "if I have the connection open per client anyway (that's the ding on scalability), might as well do everything there to save bandwidth / improve consistency". Would you as an API integrator be OK connecting via Websockets, or should I expose this (and maybe some other) routes as REST?

[kamaradclimber]

Thanks for your answer. REST is probably easier to integrate with but I don't have enough experience with websockets to answer with absolute certitude.