u/techtornado

Of course Flock would bid on it...

How about not having an Orwellian "safety" network

Innocent until proven guilty
4th Amendment

Time to bring the rain

I am exploring MeshChat and Reticulum and all that surrounds it

First, is there a way to have unencrypted channels?
Due to unfortunate rules from the FCC's, encrypted radio work is very restricted without a line of sight.

Let's say you have a Gmrs or Hams radio and want to send a message to family and friends more reliably than on MeshtasticCore.

The Aprs repeater is reachable instead due to the hill you're working and so you send a quick update that looks like this:

Aprs in > wifi or Meshtastic out to the local network

Friends respond on-mesh/Wifi in > decrypt > Aprs/Gmrs out.

Is that sort of thing within the realm of capability in Reticulum yet?

AvenzaMaps just ruined their best casual hiker feature by abruptly paywalling OSM downloads.

Very frustrating that is and I don't mind manually uploading map tiles or similar into an app, but it needs to have the speed/simplicity of Avenza, Organic, etc.

I need the name of the trail or the dashed path line + GPS dot, path tracking isn't required but would be a nice to have feature.

iPhone is preferred, can do Android as needed

It feels like the whole of ATL/North Georgia MediumFast group has set all of their nodes to 7 hops because my node list is very very full now.

The couple of routers we do have in Chattanooga have a rather high bit of airtime due to all of the NodeIDs being cast in our general direction.

I suspect that Meshaging for us 'Nooga nerds is rubbish because of that...

With that observation, why is NodeID given such high priority across the mesh and is always reliably delivered 7 hops away?

This tech has so much potential once we can reliably send and receive messages at only 2 hops away as most nodes are within that range to the router or client-base on a hill.

We could even leverage CB to do the hard work of queuing messages going in and out to save on airtime with the pocketnodes.

Would setting NodeID to have it's own hop count be limited to 2, maybe 3?

Making telemetry/ID broadcast intervals to be 1 hour or more?

Enabling routers send out a set of hush messages to suppress NodeID's when it's too noisy?

TDMA slots of dedicated listen and transmit times +/- elements of Token Ring to ensure nobody gets stepped on?