nostr:nprofile1qqsxyllxr558rfkrn7df69cshgd3qy0rwev0a4l5sfuq754vpu5spjsppemhxue69uhkummn9ekx7mp0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshsz9nhwden5te0daexzmn8v4ehjmnr9e6x2cmg9uepv3ej might have something to say about that. 👀
Discussion
nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshspg7dju if your looking for an overlay network that abstracts away the hardware stack to enable named data networking, I recommend just using nostr.
Nostr relays could easily accept events via LoRa, but LoRa isn't strictly required when running a nostr relay. I also see a lot of value in the nostr relays, because they enable asynchronous communication.
Reticulum addresses a lot of problems at once and it isn't as modular as nostr: path finding, TCP/IP, LoRa etc.
I found this podcast very insightful in this context:
https://pod.link/1678531266/episode/bf4d8dc9698131921236d1524136f675
I don't think it's either or, reticulum is built by hams, lots of thought were into resolving comms outside the internet. Even transports voice.
Makes sense. I would love to see the two technologies integrate. Perhaps the relays could serve as glue for this...
