Oddbean

To me it seems like reticulum is an overlay network - like nostr, but it comes with more complexity because it tries to address problems like path finding. I think it would be a mistake to make one overlay network (nostr) depend on another overlay network (reticulum) which still depends on TCP-IP. Tor gives relays cryptographic addresses, but it's inefficient and unreliable as a transport layer. I guess there is no harm in relays supporting multiple deferent protocols / technologies. Time will tell what works best...

RN isn’t just an overlay network. It is a network. With encryption and route finding, plus multiple interface types like radio, Lora, and tcp, Nostr relies on the domain name system for relays currently. A major issue potentially in hostile environments. RN and tor perhaps are more similar, but adding access to relays over RN is intriguing.

nostr:nprofile1qqsw8tha4zrj22njem340rfnktwdjr5lu5achmtrglh4ufhhggg6mwcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7y38t66 I must confess that I commented on something I don't sufficiently understand. Reticulum has a lot of moving parts, but I appreciate the fact that it supports multiple interface types. My hope is that adding other interface types (like radio & LoRa) to nostr relays could allow nostr relays to serve as glue between the interfaces without requiring that we find consensus on "details" like route finding. Perhaps this hope is naive so I'm keen on getting further insights from people who know about reticulum 😀

I2P could really be more interesting to adopt. Especially on the client side to communicate with relays since it would keep the IP private, including for info received on the relay side. This would remove possibility to punish nostr users.