@hzrd149 I made a small PR on `blossom-server-sdk`

GitHub

add optional options to S3 storage options by ebrakke · Pull Request #1 · hzrd149/blossom-server-sdk

I was trying to setup a blossom server using blossom server and an R2 bucket, but kept getting errors. This PR allows setting a couple more paramet...

Huge shoutout to the creators of

GitHub

GitHub - sports-alliance/sports-lib: A Library for processing GPX, TCX, FIT and JSON files from services such as Strava, Movescount, Garmin, Polar etc

A Library for processing GPX, TCX, FIT and JSON files from services such as Strava, Movescount, Garmin, Polar etc - sports-alliance/sports-lib

It has everything I need to do activity file analysis right the browser. I can even convert from .fit to .gpx files! #running #nostr-ava

Protocol

Note: This protocol documentation is preliminary.

Pokycentric seems interesting. It's like if NOSTR was built on protobufs and REST

Wikifreedia

activity-nip | Wikifreedia

By Erik. NIP-XXX Activities This is a WIP. Feedback is welcome. Provide a NOSTR native alternative to social activity apps (like strava, garmin, et...

WIP nip for activities on NOSTR. This is a nip designed to share different activities (running, biking, hiking, etc...) and generate summaries of these activities. Clients can handle managing just a users activities in a totally offline / private way. But you can also share the bits about your activity that are worth sharing. For example, you don't have to upload your whole activity file to your activity just to get a summary. You could generate all your stats locally, and then publish a trimmed GPX file for others to see without getting doxxed. If summary files are readily shared, then DVMs could generate summaries from those summaries. So without having to leak all your precise GPX files, you could still figure out activity streaks, or similar routes near you. DVMs could generate routes from partial GPX files. I feel like the possibilities are really endless here. Those who are data oriented can run their own models in Python and publish the results. Result sets could be standardized. There's a lot to be done, but I think it could be exciting.

For nostr-ava I think I'm going to lean into a DVM model to analyze gpx files. Here's the flow I'm thinking 1) user uploads a gpx file in a client and adds relevant metadata around it (name, description, etc...) 2) GPX files is uploaded to a blossom server and the location is stored in the original note 3) user can then request analysis of the gpx file by creating a DVM job request. This will allow multiple ways to analyze (there's a lot of cool python libraries to transform GPX files), and also allows DVMs to use output from previous DVMs to do meta analysis. Clients can pull in the original notes + any DVM results per activity and display them as they see fit. I'm envisioning DVMs for run matching, analyzing your progress throughout the year, comparing with other similar routes (e.g. segments and KOM stuff) #nostrava #running

That's a fun view to see from your house.

AI seems to be going the way or crypto with the "but think of the energy and emissions!" Rhetoric.

Motivated to revisit a Strava alternative for nostr. I think it can be achieved with DVMs and file storage. Haven't thought too deeply about this, but let's say everything starts with a GPX file. You upload this note and it has your metadata for the activity (like a Strava post) and a location where the gpx file can be retrieved. Then you have a number of DVMs that can perform analysis on this file. Anything from really basic things (like elevation and HR analysis) to complex features that stava has (matched runs, segments, etc) I think using something like a geohash would enable segments and matched runs quite easily. You can start to see similar activities in your area. Pair it with something like npub.pro and you have your own Strava like blog. #running #strava

Instead of using the raw json as content, you could use the v4 encoded token. This is how most wallets expect tokens to be sent and received

GitHub

nuts/00.md at main · cashubtc/nuts

Cashu protocol specifications https://cashubtc.github.io/nuts/ - cashubtc/nuts

@brugeman great job with npub.pro Also, the "login with DM" flow was one of the easiest login experiences I've had so far with nostr.

Longest run since highschool, felt great. #running #proofofwork Finished off with a nice paddle board

Steaks were amazing. #steakstr #meatstr

Epic day climbing in the flatirons #climbing

https://officialrealbook.com/history/ Information wants to be free

Nostr song lyrics, guitar tabs, and sheet music. Because the existing sites that host that stuff always try to push their apps. Can basically just be a wiki style note.

Upgraded an old 5th Gen iPod video. New case, bigger battery, and 256GB SSD

Had 0 intentions of running this morning. Out late at a show last night. Woke up and saw it'd be 95 degrees today. Managed to get out and do my run! #proofofwork #running

@PABLOF7z short PR to fix the text wrapping issue on wikifreedia

GitHub

fix: text wrapping in EventContent by ebrakke · Pull Request #31 · pablof7z/wiki

Currently wiki entries are unreadable on mobile (and a lot of web clients as well) as the container forces a scroll. This PR removes the flex class...

First (rough) pass at a #climbing NIP

Wikifreedia

Crimpstr NIP | Wikifreedia

By Erik. -XX === Climbing related events for information and tracking climb -----------------------------------------------------------------------...

I opted for a new kind for these events as to not clutter existing wiki applications, though we could easily use the 30818 kind and just utilize a type and c tag to get climbing related things. I think the biggest unlock here is incorporating the geohash of an area / route into the name. This will ensure that we can disambiguate between climbs of the same name. It also has the added benefit of hierarchical ordering built in, so you can easily group climbs together without having to enforce a strict hierarchy like MP does. Using curation sets for tick lists, and for area oganizations (e.g. ordered climbs from left to right) might also be sufficient. My goal here is not enforce any ordering on the notes themselves, but let people group things together however they see fit. @PABLOF7z @Rylan

A little demo / POC of #crimpstr Using @PABLOF7z's wiki nip, and some data that I just happened to find somewhere, this could be a great decentralized repository of climbing knowledge. Indexing events using meilisearch for great discoverability (something mountain project sucks at) @Rylan #climbing