βοΈ onsighted Anna-Maria, 6c
Vacation = going climbing and starting to keep my scorecard as nostr events
#crimpstr
βοΈ onsighted Anna-Maria, 6c
Vacation = going climbing and starting to keep my scorecard as nostr events
#crimpstr
for broken clients that will not rendered the tagged event properly:
it's a kind 5132 event (I just came up with it, but it has a NIP-31 tag so there's no excuse to not render it with proper context)
it tags the area (Kalymnos), the crag (Arginonta), the route (Anna-Maria) and it includes some info about the βοΈ I did this morning.
Hundreds of thousands of users keep their data (including me, until today) in a platform that doesn't even allow you to backup your data, it was sold a few years ago to a fairly sketchy company that is trying it's hardest to monetize the data capture as much as possible.
Nostr will eat ALL OF IT.

cool! I did something similar for Strava but used kind 1 with a bunch of tags. in my case the activity type is just another tag so it doesnβt have to be sport specific
what do you think?
@note1h2zxcjq02qf8c7ypgplanlqn3z68asj6weq0xktemh8lghf7kntq93ksf6
actual event:
@note1j4ucr9vsl3y6k6h22gwawkl95ck07ylndz2wj40kp5yw4xrthn2qpkc42a
Check out https://github.com/nostr-protocol/nips/pull/1423
Still a WIP
I thought about a different kind but I want them to show up in all clients and the summary is inherently text based.
glad to see more experimentation on this though. have you implemented your proposal?
Between that and MP trying to get everyone to sign up for onx and blocking a full quarter of the page with a sign up box, gotta get all that climbing data out of the walled gardens.
Nontechy here, how can use nostr to log my climbs?
I just stopped logging completely because I hate the MP UI.
So very cool! An unexpected feature of zapping from a #nostr #safebox is the ability to include a custom message with the zap. I included one foe nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt below. In case you are wondering about the identity of the zapper, it's the identity of the #safebox that lives on the #nostr network, completely separate from your own.