Just completed a run with Runstr! πββοΈπ¨
β±οΈ Duration: 00:59:32
π Distance: 5.11 mi
β‘ Pace: 11:38 min/mi
ποΈ Elevation Gain: 249 ft
π Elevation Loss: 220 ft
π Splits:
Mile 1: 11516:43
Mile 2: 11499:60
Mile 3: 10007:11
Mile 4: 2000:00
Mile 5: --:--
Mile 6: 215893:37
#Runstr #Running
Login to reply
Replies (8)
nostr:nprofile1qqsrpn4kfee3j7s9jkxghkf2kpuus9dmgnalhvlttktkd3fq0uytmagpz3mhxue69uhkzmr8duh82arcduhx7mn99uq32amnwvaz7tmyd968gmewwp6kytmjv4kxz7g689stz so the splits started off correct but then they went all over the place. Not sure if its because i paused it at the halfway mark to let my dog rest a minute.
Are you using V0.2.9.5-alpha
https://github.com/HealthNoteLabs/Runstr/releases/tag/feed-0.1.0-20250330-161335
If not you'll need to uninstall the app and download it again from GitHub.
I guess I wasn't. I deleted the app and all apk files, reinstalled and it looks waaay different. I'm new to using github and apks. My bad. Will test again tomorrow.. For real this time.
Much appreciated!
Testing zaps on this noteβ¦ we made six attempts toβ‘zap this note, at lhasasensei@minibits.cash, over a period of about 1 hour. All six attempts were successful. Please check on your end to be sure you received. Average zap time was 5946ms (5.9 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.
Thanks. I got the zaps. I think it's because I needed to like accept the zaps from minibits or something.
For some reason its not connecting with Amber. Any idea how to fix? I deleted the runstr sections in Amber and tried reconnecting, but it didn't help.
Try restarting the app, are you using a pixel 8a?