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.

Replies (8)

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.
Because MeshCore is what has coverage where I am at. Everywhere. I'm not religious about it, I just want to use something that people actually use. Other parts of the world might be different, but where I am, it's MeshCore.
I have before, but I'll check it out now. The problem with this is that it's brutally difficult to start the network effect. That's mainly what Uber and Bolt waste shittons of money. You either have not enough drivers or not enough riders. Equilibrium is super hard to achieve. And if you are out of equilibrium, the app becomes unusable. You don't want to wait half an hour for your ride, because the only car is on the other side of the town. And you don't want to use an app that has no riders. Andrew Chen described it nicely in Cold Start Problem. I have experienced this with my other project and it's hardcore.