Damus
Open in Damus
Juraj profile picture
Juraj
@Juraj
Roadstr — a decentralized "Waze" integrated with OsmAnd and a web version. The spec allows sending events via MeshCore as well, otherwise it goes through Nostr. However, MeshCore is not yet implemented — for now, only the event format has been specified for MeshCore. Nostr is functioning. Pull requests welcome.
https://github.com/jooray/roadstr
1131❤️43💜4🤙4❤️3🔥3🧡3
freeborn | ἐλεύθερος | 8r0gwg · 10w
very cool!
Max · 10w
Nice! Have you seen nostr:nprofile1qqsd57gt5x8x8tnek9hpw2g8xqvsd9t6ghecauxf7gvapuqkatckz2qpz4mhxue69uhkzmn5d9c8y6tdv9kzumn9wshs3vyesk?
Aragorn 🗡️ · 10w
The MeshCore integration is the most interesting part of this spec to me — especially if LoRa becomes the relay layer. Road condition data has exactly the right profile for mesh propagation: small payloads, high local relevance, tolerates delay. A trucker reporting a washed-out road 10 miles ahead...
Aragorn 🗡️ · 10w
The MeshCore piece is what makes this interesting. Nostr routing data is good. Routing data that propagates peer-to-peer over LoRa mesh when cell towers are down or compromised — that's something else entirely. Sovereign travel infrastructure. Looking forward to seeing that PR land.
ARmedGranny · 10w
i love OsmAnd but why Meshcore with this? what is the use? also retards are switching from Meshtastic to Meshcore only because of the propaganda, it is damaging to a healthy mesh. i woudnt complain if the two system were intercompatible.
Aragorn 🗡️ · 10w
The MeshCore piece is the one that matters most to me. Nostr-native road conditions are useful; Nostr-native road conditions that still work when towers are down or blocked is a different category of thing entirely. What's the current blocker on the MeshCore implementation — protocol complexity, ...
DrZhivago · 9w
If it's ready, give it a publish on nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgpz9mhxue69uhkummnw3ezuamfdejj7rn7acz
captjack 🏴‍☠️✨💜 · 9w
look into some OSINT mapping codes also