ptz

Congrats on finding a 3rd Rock GIF lol. I had to make that one from DVD screencaps.

Something like this...but the opposite:

Ah, maybe that's the 100 node limit I was thinking of. I'm still relatively new to this myself.

I do have my private channels named (with the exception of a single secondary channel called LongFast to be able to interact with the "default"/public mesh), but you can only have 7 (or is it 8?) channels per device; that's a hard limit of the firmware/protocol.

From what I've read, I think there's also an upper limit of around a hundred nodes per mesh.

Would I personally? No. If you're posting the pre-shared key publicly, then might as well just use the default one.

I definitely wouldn't force people to join a Discord channel, that's for sure.

Forget exactly which community mesh page I was looking at, but basically you create an account on their website, the admin verifies you're not spam, and then a section becomes available to you that has the mesh channel config info. The community mesh page would also get listed on the Meshtastic Local Groups list.

So I would setup a website for it, create a registration/membership system, and put the channel info in the "Members Only" section of the site.

Edit: Ah, yeah: Dayton Mesh

Configuring your Meshtastic Device for the Dayton Mesh

In order to access the Dayton Mesh channel information, you may become a member by Creating an Account. Once you are signed in, a new link will appear called Channel Settings. There is no cost, and we do not collect personal information aside from your email . The reason we have decided to go this route for membership is twofold. Primarily, this allows us to protect channel information from scraping while still having all information in one location. Secondarily, we may add user-centric features in the future such as self-reported node locations, member-only event information, user-submitted blog posts about builds, etc. As such, having a membership system from the beginning allows us to more easily implement such features in the future. We use Amazon Cognito for user management.

I'm still setting up my mesh, so just me and a friend at the moment lol.

Once I get everything planned, the goal is to start a community mesh project for this area.

Each channel also has a pre-shared key (even the default LongFast one). Most community groups only share their channel info once you've joined or otherwise been vetted; they typically don't post those details for everyone to see.

If you keep the default longFast as your primary channel, be aware that your location is shared over the primary channel, so you're sharing it with everyone.

On my mesh, my primary channel uses a custom name and PSK so that only members can use it / see my location.

Because I also wanted to be able to relay for and interact with the "public" / default channel, I created a secondary channel named LongFast. For that to work, I had to also modify my LoRa settings to use the default frequency slot for my region (20, in my case, which is 906.875 MHz).

I had almost forgotten that Altoids tins were the go-to project case before we had 3D printers.

Fun fact: They're dancing to jawa21's remix of Ode to Spot.

• New Yak City
• Chicag-Oh, shut up already
• Utter Pradesh
• Talky-o (Talk-yo?)

How about "Whut up, Wesley?"