I know there are other projects in the fitness app domain, but can't recall who was involved or what they were called. Perhaps nostr:nprofile1qydhwumn8ghj76twdejhytnnv43xzum5d9uzuum0vd5kzmqpp4mhxue69uhkummn9ekx7mqqyqrx8x3cdjwpq9ppwc3ve085pyyvfudqcvlz87xk668540m9t78hzh692k6 remembers.

Having a brief look at your kinds, is POWR also an app of yours? Because it appears to generate the 1301-events a bit differently.

See: https://nostr.com/nevent1qqsgznyfs9rw7gcsgv6xf8v7llhktde3rht0mnkqw47678qeh7vxj4spzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhg0rgv6u

It just dumps a bunch of values under ''exercise'', whilst what i gather from that spec thats not supposed to be how it works no?

https://github.com/RUNSTR-LLC/RUNSTR/blob/main/docs/KIND_1301_SPEC.md

Reply to this note

Please Login to reply.

Discussion

The exercise tag lists a kind 33401 event, which is a published exercise (eg pushups) that have associated parameters (eg, title, type, equipment, etc). Personal life got a little out of control so I’ve had to take a step back from Powr for a few months, but hoping to get back to it soon. You can mess with it at powr.build although still very buggy.

Here’s a draft of the workout nip I had been working on. https://github.com/DocNR/POWR/blob/main/docs/technical/nostr/exercise_nip.md

Has been a while I digged into this. But at that time, I it was https://github.com/nostr-protocol/nips/pull/1423 I was following.