Working in that environment, seeing as Google rolled out the idea of "cloud computing" meaning "you have no involvement or agency in your computing because we do it for you" radicalized me for much of the work of my career.

It was one thing to run a datacenter to index the world's public web information. I understood that, it made sense.

But watching as Google and Apple co-developed the idea that computers, which I cared about, got abstracted into toys and jewelry that had all your key computing done in a way you had no agency over... where I saw firsthand the kinds of churn of resources necessary to keep these things going, it made me want to fight for a different computing future.

@eff #Reticulum would fit well into this especially resiliency and scalability-wise compared to Meshtastic, which is also great for isolated relatively smaller groups that use LoRa only.

eg. during an internet shutdown, people who use a reticulum-based messaging client to talk to eachother via TCP/IP would still be able to reach at least part of their network via LoRa using the same tools, the same way they did before.
And even better, if any of the nodes on the LoRa mesh reach outside the internet blackout zone (due to physical location or other means), then all the others on the mesh inside the blackout zone would also have access to all reticulum-based services, but with LoRa speeds of course.