Thank you for sharing this valuable insight.

Nostr over Reticulum network would be an interesting development. Certainly some technical hurdles to work through, but the payoff could be substantial. Reticulum currently has the NomadNet which can serve as a static site or BBS, but in general, group chat or collaboration is pretty weak for Reticulum (based on what I presently know about it). Nostr could be that group chat, persistent messaging, community building, micro-economy tool that could also bridge Reticulum node relays to clear-net and/or I2P relays if so desired. This is something I would like to ponder for a while...

I was also tempted to try Meshcore. I settled on skipping it for two main reasons. While it seems to solve some of the potential weaknesses found in Meshtastic, it isn't popular or even known in my area. It also doesn't differentiate itself enough from Meshtastic. Reticulum, with caching, routing, and the ability to use basically any type of wired or wireless network and make them interoperable doesn't have the same limitations. It has different ones currently, but Reticulum looks like a solid base to build something from.

It can, there is a github project that enables that. I've not tested it yet. The additional features that I have using RNodes over Meshtastic devices has kept me from trying this out. I will test it eventually.

I've been spending time researching, building, and testing different resilient and mesh type networks and hardware. I started playing with #Meshtastic but keep getting pulled towards #Reticulum network and #RNodes. Meshtastic has the marketing, ease of entry, and hardware support. In actual execution it suffers the same downsides as FMRS radios. Reticulum is something much more. A complete encryption first network stack capable of leveraging the best path whether that's across the internet, across ISM band or other radio links or both. The ability to cache messages in the network until a node becomes available again, and no arbitrary three hop limit is a plus. Being able to text with someone out of eyesight through the radio and also with someone on the other side of the globe at the same time is very interesting. What it lacks is the fit, polish, marketing, and momentum of Meshtastic. In every other way, I find it to be superior. Oh, you can also send images, voice messages and files over Reticulum as well. Here is my first Reticulum node running Meshchat on a Raspberry Pi connected to a RAK flashed with RNode all powered with PoE. I'm building a few of these to start building out a local/regional network over time.

I have to say that my first touch with ClaraVerse AI tool stack leaves me impressed. Certainly some bugs to work through and some features to finish, but dang, it feels like another step. For someone just jumping into self-hosted AI features, this is pretty amazing. For someone that already has a pretty well defined self-hosted, but centralized AI stack, the configuration is a little fiddly. I have a dedicated machine with GPU power for Ollama, N8N, ComfyUI, Open WebUI, Perplexica, a bunch of MCPs and a voice stack for TTS/STT etc. I prefer to just point everything there. It is, however, quite beautiful and I can see this as my daily driver in the future. It combines so much in a single package that it's quite amazing. Between VSCode and ClaraVerse, my AI software stack may have just become less messy. I know nothing about the developers, their ethics, etc. They seem focused on local AI, so they can't be all bad. It is multi-platform. Would recommend checking it out. https://claraverse.space/ #ai #llm #localai #claraverse #ollama #openwebui

This is a project that I've looked at that enables a Meshtastic interface in Reticulum. https://github.com/landandair/RNS_Over_Meshtastic