Oddbean new post about login | logout I want Meshtastic to do e2ee DMs from my phone to the recipient's phone, not from my node to the recipient's node. There is a big difference. #meshtastic #radio #secure #comms #communications #LoRa #e2ee #encryptio. #security #infosec
Kludgey but GnuPG encrypted messages might work. Not as neat as something like Signal though
nostr:nevent1qqsfvf6ksykzl2aqr7l6e859596flj00xgleycmq3tlaqkmlg5scwsspz3mhxw309akx7cmpd35x7um58g6rsd3e9upzptssprfrjv9hwmqcpyhka26pujcflnelq0ekgxcmfehw82skd4mqqvzqqqqqqyjycurj
Well, Reticulum is built on top of Meshtastic, which is built on top of LoRa. So Reticulum won't solve any range issues. I know it can use 801.11 and Ethernet, but thise are way shorter range than LoRa. Reticulm is cool, and it does have its place, but it's not very interesting without Meshtastic. It is Meshtastic that is the critical component for getting long range comms without the internet.
Can you share a link/code/etc which shows that reticulum is requiring explicitly the meshtastic stack/ protocol?
I saw video demo of Reticulum showing the different transports it cpuld use. Meshtastic was the only one they showed that was not IP based. All the others were Ethernet, 802.11, I2P, and other internet protocols. Meshtastic was the only layer that was an off-grid technology. If you can point me to any long range protocol that reticulum can use, I'd love to be wrong about this.
The way I understand it #reticulum isn't built on and doesn't use #meshtastic but can use #LoRa in addition to other methods while meshtastic only uses LoRa. Disclaimer: this is a gross oversimplification.
Yeah, it looks like I was mistaken. The video must have said LoRa and my brain thought of Meshtastic because I've used raw LoRa packets, LoRaWAN, and Meshtastic and Meshtastic absolutely blows the other two out of the water in terms of range and reliability. That makes me wonder, if Reticulum really wants to use all these different transports, why **don't** they support Meshtastic in addition to LoRa?
You could write your own transport. It is in Python and then get that to work if you wanted to.
Yeah I don't recall it using Meshtastic? Like I never investigated how the RNode's communicate but I never thought they would be using the Meshtastic protocol buffers?
Well, Reticulum is built on top of Meshtastic, which is built on top of LoRa. So Reticulum won't solve any range issues. I know it can use 801.11 and Ethernet, but thise are way shorter range than LoRa. Reticulm is cool, and it does have its place, but it's not very interesting without Meshtastic. It is Meshtastic that is the critical component for getting long range comms without the internet.
Can you share a link/code/etc which shows that reticulum is requiring explicitly the meshtastic stack/ protocol?
I saw video demo of Reticulum showing the different transports it cpuld use. Meshtastic was the only one they showed that was not IP based. All the others were Ethernet, 802.11, I2P, and other internet protocols. Meshtastic was the only layer that was an off-grid technology. If you can point me to any long range protocol that reticulum can use, I'd love to be wrong about this.
The way I understand it #reticulum isn't built on and doesn't use #meshtastic but can use #LoRa in addition to other methods while meshtastic only uses LoRa. Disclaimer: this is a gross oversimplification.
Yeah, it looks like I was mistaken. The video must have said LoRa and my brain thought of Meshtastic because I've used raw LoRa packets, LoRaWAN, and Meshtastic and Meshtastic absolutely blows the other two out of the water in terms of range and reliability. That makes me wonder, if Reticulum really wants to use all these different transports, why **don't** they support Meshtastic in addition to LoRa?
You could write your own transport. It is in Python and then get that to work if you wanted to.
Yeah I don't recall it using Meshtastic? Like I never investigated how the RNode's communicate but I never thought they would be using the Meshtastic protocol buffers?
The way I understand it #reticulum isn't built on and doesn't use #meshtastic but can use #LoRa in addition to other methods while meshtastic only uses LoRa. Disclaimer: this is a gross oversimplification.
Yeah, it looks like I was mistaken. The video must have said LoRa and my brain thought of Meshtastic because I've used raw LoRa packets, LoRaWAN, and Meshtastic and Meshtastic absolutely blows the other two out of the water in terms of range and reliability. That makes me wonder, if Reticulum really wants to use all these different transports, why **don't** they support Meshtastic in addition to LoRa?
You could write your own transport. It is in Python and then get that to work if you wanted to.