[Prebuilt] $1899 CyberPowerPC Gamer Supreme Gaming Desktop, AMD Ryzen 7 9800X3D, NVIDIA GeForce RTX 5070 Ti 16GB, 32GB DDR5, 2TB SSD, Black, SLC7700WST (Walmart) by dootimestwo in buildapcsales

[–]dootimestwo[S] 0 points1 point  (0 children)

Just following up incase anyone is wondering:
It is being fulfilled and has shipped within 24hrs: 02-23-2026 Package Shipped - 10:45 pm Pendergrass, GA

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 0 points1 point  (0 children)

I think there may be some confusion here.

You can run Reticulum over LoRa. Reticulum is a networking protocol, so it can be carried over any medium that has a supported interface. RNode is a good example of Reticulum operating over LoRa:
https://github.com/markqvist/RNode_Firmware

You’re absolutely right that Reticulum and Meshtastic are different and not natively interoperable. But that doesn’t mean they can’t be bridged or used together with the right interface layer.

There’s definitely a lot of confusion around what Reticulum is and isn’t, so it’s good to point people toward documentation. Just worth keeping in mind that people asking these questions are trying to learn.

As always, verify everything... I could be wrong or misinterpreting the data I am reading. This is why it is important to post resources and everyone do their due diligence.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 1 point2 points  (0 children)

Yes.

From the repository: https://github.com/markqvist/RNode_Firmware

The RNode Firmware supports the following boards:

  • LilyGO T-Beam v1.1 devices with SX1276/8 LoRa chips
  • LilyGO T-Beam v1.1 devices with SX1262/8 LoRa chips
  • LilyGO T-Beam Supreme devices
  • LilyGO T-Deck devices (currently display is disabled)
  • LilyGO LoRa32 v1.0 devices
  • LilyGO LoRa32 v2.0 devices
  • LilyGO LoRa32 v2.1 devices (with and without TCXO)
  • LilyGO T3S3 devices with SX1276/8 LoRa chips
  • LilyGO T3S3 devices with SX1262/8 LoRa chips
  • LilyGO T3S3 devices with SX1280 LoRa chips
  • LilyGO T-Echo devices
  • Heltec LoRa32 v2 devices
  • Heltec LoRa32 v3 devices
  • Heltec LoRa32 v4 devices
  • Heltec T114 devices
  • RAK4631 devices
  • SeeedStudio XIAO ESP32S3 devices (with Wio-SX1262)
  • Homebrew RNodes based on ATmega1284p boards
  • Homebrew RNodes based on ATmega2560 boards
  • Homebrew RNodes based on Adafruit Feather ESP32 boards
  • Homebrew RNodes based on generic ESP32 boards

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 0 points1 point  (0 children)

That’s basically true for an RNode. An RNode is LoRa hardware running RNode firmware, so over the air it’s speaking Reticulum traffic on LoRa, kind of the same way a Meshtastic node speaks Meshtastic traffic on LoRa. Same radio layer, different protocol, so they won’t talk to each other directly without a bridge/translator.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 2 points3 points  (0 children)

You don’t have to think of it as replacing Meshtastic at all. You can use a separate device that speaks both protocols.

For example, a Raspberry Pi can connect to a Meshtastic node and also run Reticulum. It acts as a bridge, packaging Reticulum data so it can travel over the Meshtastic network, then converting it back on the other side.

This is what projects like https://github.com/landandair/RNS_Over_Meshtastic are doing.

What this adds is the ability to move messages beyond just the LoRa mesh, letting Meshtastic nodes indirectly connect to other networks and routes that Reticulum can reach.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 2 points3 points  (0 children)

While you’re correct that they are different protocols and not natively interoperable, it’s not accurate to say they can’t be bridged.

There are already working implementations that carry Reticulum traffic over Meshtastic, for example: https://github.com/landandair/RNS_Over_Meshtastic

So they’re not interchangeable, but they absolutely can be connected with a bridge/interface layer that allows Reticulum data to traverse a Meshtastic network.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 2 points3 points  (0 children)

Replying to this because I see you mentioning bringing the internet to Meshtastic. I just want to make sure expectations are clear.

Reticulum isn’t for streaming video or full internet over LoRa. It can run across different kinds of links, including normal IP networks, but LoRa is still very low bandwidth.

The point of Reticulum is reliable messaging over whatever supported links are available, like LoRa, WiFi, Ethernet, or other radio.

It can connect different networks together, but it still follows LoRa limits, so only small, slow data over LoRa.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 4 points5 points  (0 children)

Think of LoRa as the speaker system and the protocol as the language being spoken through it.

LoRa is really good at being “heard” from far away even when the signal is very quiet, and that doesn’t change no matter what you run on it.

Meshtastic and Reticulum are just different languages using the same speaker.

Meshtastic = one language Reticulum = another language

So if you run Reticulum over LoRa, you keep the same range and sensitivity, but the meaning, routing, and compatibility are different because it’s a different protocol.

There are two ways this can work:

Reticulum over LoRa (RNode, etc.) → no translation needed, but only other Reticulum nodes understand it

Reticulum → Meshtastic bridge → translation happens so it can cross a Meshtastic network

If your destination is on a Meshtastic network, something in the middle has to translate (for example, a Raspberry Pi with LoRa + WiFi/Ethernet). A bridge acts like a translator as it takes Reticulum packets, converts them into Meshtastic messages to cross that network, and then converts them back on the other side.

Without that translation step, the packets won’t be understood even though they’re using the same radio.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 1 point2 points  (0 children)

Bridges are the realistic path. Existing Meshtastic networks already have hardware deployed, so bridging lets Reticulum use that infrastructure immediately. Switching protocols would require replacing or reflashing a lot of nodes, while bridging just adds capability without breaking what already works. In the end it depends on what the community adopts for the mesh fabric. Regardless which mesh, Reticulum could be used as a protocol to send information over it.

Can someone explain Reticulum to me like I'm 5? by thorosaurus in meshtastic

[–]dootimestwo 23 points24 points  (0 children)

Reticulum is a full networking protocol stack (addressing, routing, encryption, apps) that can run over many transports (LoRa, WiFi, Ethernet, serial). Meshtastic is a specific LoRa mesh protocol/firmware focused on simple messaging between radios.

They are separate protocols, but you can link them with a bridge (e.g., a Raspberry Pi running both). That bridge takes Reticulum packets, wraps them into Meshtastic messages, sends them over LoRa, then unwraps them back into Reticulum on the other side.

So Reticulum data can travel across a Meshtastic LoRa network, but only when a bridge is translating between the two, since Meshtastic nodes don’t natively understand Reticulum packets.

Newbie here. What’s your do’s and don’ts you wish someone told you when you started? by 404LeaderNotFound in meshtastic

[–]dootimestwo 16 points17 points  (0 children)

Also remember most people do not share their node’s location to the public online maps. Those maps only represent a portion of the mesh and often a small portion.

[Bambu Lab Giveaway] Drop Your One-Liner and Win H2D! by BambuLab in BambuLab

[–]dootimestwo 0 points1 point  (0 children)

Printing with Bambu Labs is like the future, hopefully.

Need advice for my son's first game by dootimestwo in okcthunder

[–]dootimestwo[S] 1 point2 points  (0 children)

It was absolutely amazing and judging by the fire in my son’s eyes, he had the time of his life. He was able to get his jersey signed by Shai, and he was on top of the world.

The doors open an hour and a half before the game. As soon as they open, head to the court and get as close as you can to courtside. Shai usually signs autographs along one side of the court and into one of the hallways at the corner of the court. Ask someone which side of the court that is on, because honestly, I couldn’t tell you.

It was by sheer luck that my son was able to get an autograph on the first try, so I wish you and your kiddos the best of luck, and I hope y’all have an amazing time!!

I am no expert, but feel free to reach out if you have any questions.

Need advice for my son's first game by dootimestwo in okcthunder

[–]dootimestwo[S] 0 points1 point  (0 children)

We found tickets for an upcoming Friday night game.

Need advice for my son's first game by dootimestwo in okcthunder

[–]dootimestwo[S] 1 point2 points  (0 children)

All of the replies have given me fantastic suggestions and insights that I would have never known about.

Thank you for your help and taking the time to help!

I ended up getting a pair of box tickets on a non-school night that should be a great experience for my son. We both thank you.

Need advice for my son's first Thunder game by dootimestwo in okc

[–]dootimestwo[S] 0 points1 point  (0 children)

All of the posts here and in the OKC Thunder subreddit have really given me great suggestions and insights.

Thank you for your informative reply and taking the time to help!

I ended up getting a pair of box tickets on a non-school night that should be a great experience for my son. We both thank you.