I said already that I love #Reticulum.. yet i just thought of it this way:
As Reticulum is transport agnostic (a node connects through many "interfaces": local wifi, BLE, lora radio, UHF, FM radio, etc. _and_ TCPClient interfaces), the fact one can actually use _internet_ is the 🐘 in the room (most ppl probably do connect to reticulum via internet today?) and also an amazing feature:
1/ it enables super-easy onboarding. basically install an app, some will add TCPClient interface for you, and voila.
2/ it enables to test features, routing, new protocols and ideas at large-scale, while learning how everything works, and becoming ready for the next thing.
@jz @jz @lvl3k i am really on the fence on this: on the one hand, yes, it's awesome that #reticulum can Just Work over TCP out of the box but i'll be damned if i'll allow onboarding to be "super easy"... meshchat? *nomadnet*? much of it is just hostile UX, and sometimes it feels deliberate (come on, control-d to send a message??)... and also, that means we rely on the internet to route messages, and it's unclear what will keep working after we're censored or everything collapses.. on the other hand, meshcore networks are have a strong "lora-only" approach that really forces to work out the radio problems directly (and those are *hard), i'm not sure reticulum would actually scale *there*, at the size of a city