• hayvan@piefed.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 day ago

    I’ve been playing around with Meshtastic and Meshcore for a few weeks now. Especially I’m impressed with Meshcore community in Europe.

    Let’s see how Reticulum performs.
    I wish there was a way to interoperate though (e.g. forward a MeshTastic message even if you are not actually participating in the network)

    • Unrefined@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      0
      ·
      20 hours ago

      Tried both…prefer meshcore when urban, and meshtastic when anywhere more remote and looking for a node to node connection.

      • Taasz/Woof@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        20 hours ago

        Agreed, I wish meshcore would add features for better remote operation, right now it’s not as useful away from an established repeater network.

        • shortwavesurfer@lemmy.zip
          link
          fedilink
          arrow-up
          0
          ·
          18 hours ago

          There is the new mesh core off-grid repeat mode that turns companions into repeaters on a separate frequency from the standard mesh for if you are out in the backwoods with no repeater access.

  • Iced Raktajino@startrek.website
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 day ago

    I really want to like Reticulum, but none of the stock applications fit my needs. I was going to write my own but I just cannot grasp interacting with its network layer. Maybe the docs are lacking, maybe I’m just sane and the project is written by a madman (or vice-versa), maybe it’s a bit of both, but I just cannot wrap my head around it.

    • empireOfLove2@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      22 hours ago

      Reticulum is just on the wrong side of the utility-complexity curve imo. Its very powerful but only if you have deep networking knowledge and already have a suite of ultra low bandwidth apps that can make use of its capabilities. I already can’t convince my friends to get on meshtastic, let alone meshcore or god forbid Reticulum - it’d probably make their eyes roll back in their heads.

    • mesa@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      I agree. I think guides like the above can showcase a bit of what each project can do and how to do it. But retriculum took me about a week or so to get working. For almost no nodes.

      But I was able to chat with images for the first time over the mesh…so that was really neat!

      • Iced Raktajino@startrek.website
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        1 day ago

        Nice. I did get a few nodes talking with NomadNet but like I said, I needed more out of it before I could see myself using it.

        As a simple but functional “hello world” I was trying to make an MQTT relay to receive/push messages and just couldn’t get things going at all. The MQTT part was straightforward but getting those messages to and from the Reticulum network layer was an exercise in frustration. It was more of a side project at the time, so I may double back and put some more effort into it.

        Other than being a starter project, my goal was to work toward a higher-level abstraction that I could use TUN/TAP interface to interact with. Basically a low MTU virtual ethernet port. Kind of like the highly experimental VPN function in the Meshtastic python library. Or a virtual serial port between two Reticulum nodes would be nice. Just something so external programs not written specifically for Reticulum can communicate across it.