<![CDATA[The Blog Hustle]]> https://thebloghustle.npub.pro/tag/runstr/ https://thebloghustle.npub.pro/tag/runstr/rss/ episodic Sun, 30 Mar 2025 00:37:54 GMT Sun, 30 Mar 2025 00:37:54 GMT <![CDATA[The Blog Hustle]]> https://thebloghustle.npub.pro/tag/runstr/ https://i.nostr.build/BksqZ8QSHxr9FGj2.webp <![CDATA[RUNSTR - Direction and Goals ]]> Sun, 30 Mar 2025 00:37:54 GMT https://thebloghustle.npub.pro/post/1743294738823/ https://thebloghustle.npub.pro/post/1743294738823/ naddr1qqxnzde5xverjdphxvursv3nqgsrpn4kfee3j7s9jkxghkf2kpuus9dmgnalhvlttktkd3fq0uytmagrqsqqqa28k9he55 RUNSTR naddr1qqxnzde5xverjdphxvursv3nqgsrpn4kfee3j7s9jkxghkf2kpuus9dmgnalhvlttktkd3fq0uytmagrqsqqqa28k9he55 npub1xr8tvnnnr9aqt9vv30vj4vreeq2mk38mlwe7khvhvmzjqlcghh6sr85uum Hey Freaks,

RUNSTR is a motion tracking app built on top of nostr. The project is built by TheWildHustle and TheNostrDev Team. The project has been tinkered with for about 3 months, but development has picked up and its goals and direction have become much clearer.

In a previous post I mentioned that RUNSTR was looking to become a Nike Run Club or Strava competitor, offering users an open source community and privacy focused alternative to the centralized silos that we've become used to.

I normally ramble incoherently.....even in writing, but this is my attempt to communicate the project's goals and direction as we move forward.

This is where the project is now:

Core Features

  • Run Tracker: Uses an algorithm which adjusts to your phone's location permissions and stores the data on your phone locally
  • Stats: Stored locally on your phone with a basic profile screen so users can monitor calories burned during runs
  • Nostr Feed: Made up of kind1 notes that contain #RUNSTR and other running related hashtags
  • Music: Brought to you via a wavlake API, enabling your wavlake playlists and liked songs to be seen and played in the app

Current Roadmap

  • Bugs and small improvements: Fixing known issues within the client
  • zap.store release: Launching a bug bounty program after release
  • Clubs: Enabling running organizations to create territories for events, challenges, rewards and competition
  • Testflight: Opening up the app to iOS users (currently Android only)
  • Modes: Adding functionality to switch between Running, Walking, or Cycling modes

Future Roadmap

  • Requested Features: Implementing features requested by club managers to support virtual events and challenges
  • Blossom: Giving power users the ability to upload their data to personal blossom servers
  • NIP28: Making clubs interoperable with other group chat clients like 0xchat, Keychat, and Chachi Chat
  • DVM's: Creating multiple feeds based on movement mode (e.g., Walking mode shows walkstr feed)
  • NIP101e: Allowing users to create run records and store them on nostr relays
  • Calories over relays: Using NIP89-like functionality for users to save calorie data on relays for use in other applications
  • NIP60: Implementing automatic wallet creation for users to zap and get zapped within the app

In Conclusion

I've just barely begun this thing and it'll be an up and down journey trying to push it into existence. I think RUNSTR has the potential to highlight the other things that nostr has going for it, demonstrating the protocol's interoperability, flexing its permissionless identity piece, and offering an experience that gives users a glimpse into what is possible when shipping into a new paradigm. Although we build into an environment that often offers no solutions, you'd have to be a crazy person not to try.

https://github.com/HealthNoteLabs/Runstr/releases/tag/feed-0.1.0-20250329-210157

]]> Hey Freaks,

RUNSTR is a motion tracking app built on top of nostr. The project is built by TheWildHustle and TheNostrDev Team. The project has been tinkered with for about 3 months, but development has picked up and its goals and direction have become much clearer.

In a previous post I mentioned that RUNSTR was looking to become a Nike Run Club or Strava competitor, offering users an open source community and privacy focused alternative to the centralized silos that we've become used to.

I normally ramble incoherently.....even in writing, but this is my attempt to communicate the project's goals and direction as we move forward.

This is where the project is now:

Core Features

  • Run Tracker: Uses an algorithm which adjusts to your phone's location permissions and stores the data on your phone locally
  • Stats: Stored locally on your phone with a basic profile screen so users can monitor calories burned during runs
  • Nostr Feed: Made up of kind1 notes that contain #RUNSTR and other running related hashtags
  • Music: Brought to you via a wavlake API, enabling your wavlake playlists and liked songs to be seen and played in the app

Current Roadmap

  • Bugs and small improvements: Fixing known issues within the client
  • zap.store release: Launching a bug bounty program after release
  • Clubs: Enabling running organizations to create territories for events, challenges, rewards and competition
  • Testflight: Opening up the app to iOS users (currently Android only)
  • Modes: Adding functionality to switch between Running, Walking, or Cycling modes

Future Roadmap

  • Requested Features: Implementing features requested by club managers to support virtual events and challenges
  • Blossom: Giving power users the ability to upload their data to personal blossom servers
  • NIP28: Making clubs interoperable with other group chat clients like 0xchat, Keychat, and Chachi Chat
  • DVM's: Creating multiple feeds based on movement mode (e.g., Walking mode shows walkstr feed)
  • NIP101e: Allowing users to create run records and store them on nostr relays
  • Calories over relays: Using NIP89-like functionality for users to save calorie data on relays for use in other applications
  • NIP60: Implementing automatic wallet creation for users to zap and get zapped within the app

In Conclusion

I've just barely begun this thing and it'll be an up and down journey trying to push it into existence. I think RUNSTR has the potential to highlight the other things that nostr has going for it, demonstrating the protocol's interoperability, flexing its permissionless identity piece, and offering an experience that gives users a glimpse into what is possible when shipping into a new paradigm. Although we build into an environment that often offers no solutions, you'd have to be a crazy person not to try.

https://github.com/HealthNoteLabs/Runstr/releases/tag/feed-0.1.0-20250329-210157

]]> <![CDATA[NIP-101e: Workout Data and Running Extensions]]> Wed, 19 Mar 2025 21:28:27 GMT https://thebloghustle.npub.pro/post/1742418925012/ https://thebloghustle.npub.pro/post/1742418925012/ naddr1qqxnzde5xg6rzwpexg6nqvfjqgsrpn4kfee3j7s9jkxghkf2kpuus9dmgnalhvlttktkd3fq0uytmagrqsqqqa28vtrkel #runstr naddr1qqxnzde5xg6rzwpexg6nqvfjqgsrpn4kfee3j7s9jkxghkf2kpuus9dmgnalhvlttktkd3fq0uytmagrqsqqqa28vtrkel npub1xr8tvnnnr9aqt9vv30vj4vreeq2mk38mlwe7khvhvmzjqlcghh6sr85uum NIP-101e: Workout Data and Running Extensions

NIP-101e represents a crucial step forward for fitness tracking on Nostr, giving us a common language that would allow workout data to flow freely between apps. This proposal outlines a thoughtful framework with Exercise Templates, Workout Templates, and Workout Records that would finally free our fitness data from proprietary silos and put it back in our hands. I'm eager to see this proposal implemented because it would create the foundation for a genuinely open fitness ecosystem on Nostr.

As a runner building a Nostr running app RUNSTR, I've proposed some running-specific extensions to NIP-101e that address the unique needs of runners without disrupting the elegant structure of the original proposal. My extensions would standardize how we record GPS routes, pace metrics, elevation data, splits, and even weather conditions - all things that matter tremendously to runners but aren't covered in the base proposal that focuses more on strength training.

By implementing NIP-101e along with these running extensions, we could create something truly revolutionary: a fitness ecosystem where runners aren't locked into a single platform because of their data. You could track your morning run in my app, analyze your training in another app that specializes in statistics, and share achievements with friends using whatever Nostr clients they prefer. I believe strongly in getting NIP-101e implemented with these extensions included because it would foster innovation while giving runners unprecedented freedom to own their data and use it however they want. Let's make this happen and show what's possible when fitness data becomes truly interoperable!

]]> NIP-101e: Workout Data and Running Extensions

NIP-101e represents a crucial step forward for fitness tracking on Nostr, giving us a common language that would allow workout data to flow freely between apps. This proposal outlines a thoughtful framework with Exercise Templates, Workout Templates, and Workout Records that would finally free our fitness data from proprietary silos and put it back in our hands. I'm eager to see this proposal implemented because it would create the foundation for a genuinely open fitness ecosystem on Nostr.

As a runner building a Nostr running app RUNSTR, I've proposed some running-specific extensions to NIP-101e that address the unique needs of runners without disrupting the elegant structure of the original proposal. My extensions would standardize how we record GPS routes, pace metrics, elevation data, splits, and even weather conditions - all things that matter tremendously to runners but aren't covered in the base proposal that focuses more on strength training.

By implementing NIP-101e along with these running extensions, we could create something truly revolutionary: a fitness ecosystem where runners aren't locked into a single platform because of their data. You could track your morning run in my app, analyze your training in another app that specializes in statistics, and share achievements with friends using whatever Nostr clients they prefer. I believe strongly in getting NIP-101e implemented with these extensions included because it would foster innovation while giving runners unprecedented freedom to own their data and use it however they want. Let's make this happen and show what's possible when fitness data becomes truly interoperable!

]]>