Nostr Web Client

My vote is for runstr to keep an eye on the pebble open-source stack. I have been a carmin user for a couple years but will likely migrate back to pebble after since the path is moving toward an open os that can be put on any hardware.

In the meantime, Garmin integration would be nice, but having the ability to upload a .fit would be a more flexible and generic solution

RUNSTR 7mo ago

How do you feel about using a personal blossom server or private relay to hold health and fitness data?

And what do you think about selling open source watches with a forked OS for more compatability with nostr apps.

I've been thinking of going the opposite direction and creating our own standards and health notes from scratch over here. I'm not sure how concerned I should be with the traditional health and fitness ecosystem. I was never a fan of the twitter and mastadon bridge stuff, I'm leaning towards blossom integrations, NIP60 wallets and more nostr native features.

Reply to this note

Please Login to reply.

Discussion

armstrys 7mo ago

Honestly, I have been disconnected from the development side of nostr for a long enough time that I don't have a good feel or opinion about data handling to know how I feel about health data on a private relay. I have minimal exposure to how blossom works.

As for data standards and hardware... All I will say is that people are SUPER picky about what they will wear. I spent years trying to find a pebble replacement that I liked and settled on Garmin despite a lack of an open ecosystem. I think you would be hard pressed to get significant adoption if the platform can't take in data from other health ecosystems and hardware