Running Reticulum.network

Reply to this note

Please Login to reply.

Discussion

are you really? how can we connect or do something with it?

What is it?

cool, on which HW?

I read this soooooo wrong!

FINALLY!!

(Check dms, I sent you this once)

Oooooooo. To what end?

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...

Cashu over Reticulum exists, seems inevitable that nostr will come

nostr:note12r3tlkycu3hsuccg654y3rlpqz3x6jpv9y4y35qwzyrfdt0865lsezk8qe

We also need reticulum over cashu - how else will we pay the devices that route our traffic?