PABLOF7z on Nostr: Oh this one is easy! First, all of those are just tags, no need for content json ...
Oh this one is easy!
First, all of those are just tags, no need for content json shoehorning.
No need for date, obviously, since created_at us already there (and can be back dated if need-be)
Name could be subject, per NIP-12 (iirc), though this is not important.
Coordinate should be waypoint events, not part of the first event; which gives you speed per split/recorded waypoint and other data.
No need for totals; just when you hit finish you post a new event signaling the end of the run.
The main thing is that nostr’s basic building construct are events, so you can use that framework to think of ongoing-things as separate, linked, events.
And if you don’t want that flexibility and just want to log an event after the fact, more like a journal entry, you can do as suggested at the beginning; just or those things as tags.
The main thing to think about is that, usually, hierarchy in data structures represents either different concepts (eg. product <> inventory) or things that occur non-atomically; thus the modeling thinking in “event” terms shows that this should probably not be hierarchical but rather separate structures.
Thanks for coming to my TED talk. 😂😂😂😂
First, all of those are just tags, no need for content json shoehorning.
No need for date, obviously, since created_at us already there (and can be back dated if need-be)
Name could be subject, per NIP-12 (iirc), though this is not important.
Coordinate should be waypoint events, not part of the first event; which gives you speed per split/recorded waypoint and other data.
No need for totals; just when you hit finish you post a new event signaling the end of the run.
The main thing is that nostr’s basic building construct are events, so you can use that framework to think of ongoing-things as separate, linked, events.
And if you don’t want that flexibility and just want to log an event after the fact, more like a journal entry, you can do as suggested at the beginning; just or those things as tags.
The main thing to think about is that, usually, hierarchy in data structures represents either different concepts (eg. product <> inventory) or things that occur non-atomically; thus the modeling thinking in “event” terms shows that this should probably not be hierarchical but rather separate structures.
Thanks for coming to my TED talk. 😂😂😂😂