Installed 🫡

Thanks Juraj, yours is cool as well 😄

It's much simpler. But it would be very cool if the property of Nostr events (that they are compressible into one MeshCore packet) would stay (not necessarily my NIP). It's mainly about the size (check the NIP). Then we could share the reports in local mesh network. I don't even care if it is compatible with my protocol, I can change the protocol to yours (and even rename the web app to remove the confusion and retire the Android app, even though I believe mine was first, but I don't care:). Shall we fix this for everyone? The idea is - road reports are local, if internet is down, we can locally report over MeshCore radio, it can appear on local relay (mapping the meshcore packet to full signed Nostr event, including the signature). And then it would not only be decentralized "Waze", but "There's a revolution, beware, there are thugs with guns next street".

That's an interesting idea 0-)

Hey man! I really like the idea 😄 I think the best approach would be to make my Roadstr compatible with yours compact, while keeping the existing reporting system intact. That way, reports could travel both through regular relays and over meshcore, opening the door to proper interoperability the two projects without either of us having to redesign everything.. meshcore is definitely interesting and i like the idea of not being dependent by my isp to communicate with other people, but i'd want to make sure the same reports can still be published and received through standard relays. it's a nostr app after all. ideally, both would just be different ways of transporting the same signed events. I'll look into adding support for your format on my side, keeping it optional and compatible with the existing architecture. this should also make it easier for other projects to integrate in the future.. And about the name I know yours came first, I actually came up with it when I read about the new kind 1315-1316 (maybe from Gigi, utxo or Derek, can't remember who) that I came up with it 😄 but honestly, combining "road" with the "-str" suffix while also getting something that sounds like roadster, is such a natural combination that we simply arrived at it independently, just at different times. Thanks for being so openly nice about it :) anyway, I'd much rather focus on making the two projects interoperable than worrying about the naming coincidence. I think that would be a win for everyone! ⚡

Yeah. I'll gladly rename it so there's less confusion. The way I handled the NIP is that it is still primarily Nostr, but I specified a deterministic way to encode the Nostr event into MeshCore packet and back - in a way that the Nostr event is fully reconstructed, including the valid signature. Basically keep only the most precise geohash (although we include less precise for easy queriability), etc. The goal is to be able to pack everything into as small packet as possible, but also be able to unwrap it back into original Nostr event. Do you have a specification of events that you use? We might do it the other way around - if it is possible, we can use your event type and I can devise a way to compress it into meshcore packets. And I'll change my apps to use your event type. My app has no users, it's a demo at this point, so I'm totally OK with continuing with yours, if we can keep this property and extend it to MeshCore. My app is also primary Nostr, MeshCore is not yet implemented (I need a bit of work on MeshCore side as well, so it is user friendly - currently you can connect only one MeshCore app to a node, so we need a MeshCore app that can take and send events from other apps, so users don't have to choose "now I'm driving, I am opening app X, now I want to chat, I am opening app Y"). But I'll solve that part easily.