nostr:nprofile1qyv8wumn8ghj7cmgdae82uewvfhkuumpdyhxxmmd9uq3vamnwvaz7tmwdaehgun9d35hgetn9ehhyee0qqsg2ps9p9kmldgtj20r3fkzds74d3p9xfwgtczau2dhtx7quhtva0qrmh2vq I just stumbled upon #Noshtastic and it looks really interesting. Meshtastic definitely has a message delivery confirmation problem, using Nostr and negentropy to make conversations more reliable sounds awesome.
What's the status of the project? Is is usable, scalable, interoperable with existing meshes?
Apologies for the delay. The project works but needs quite a bit of attention to the user interface and connection to the relays. The packets do relay in the existing meshtastic network. At the moment I'm surveying to figure out if I can possibly put all of the code in the meshtastic radio itself. This is obviously ambitious but would result in something that was much more usable. Both the command line interface and the Android app should build if you want to give it a try
#noshtastic has a similar issue and it fragments the packets into multiple smaller
How is the cashew token encoded? meshtastic packets can be binary ...
Maybe they were lazy and just updated the numbers on an old chart so the proportions were from some other year
https://github.com/ksedgwic/privdm
I needed a command line tool to send a nip 17 private direct message

It's at the bottom of "Radio Configuration" ...
This is not wrong
testing 123
testing, pls ignore
Briar: "Censorship-resistant peer-to-peer messaging that bypasses centralized servers. Connect via Bluetooth, Wi-Fi or Tor, with privacy built-in." https://briarproject.org/
Would be cool to have bluetooth & wifi sync on native Nostr apps. Would be useful in offline situations and countries where the internet is censored.
Do you have "Include unknown" enabled on your node list?
Some observations about Negentropy in the Noshtastic environment:
https://ksedgwic.github.io/noshtastic/posts/negentropy-for-noshtastic.html
#noshtastic #meshtastic
Noshtastic has fragmentation and reliable delivery



