Interesting morning on the #Boston #MeshCore network.
Due to what we think is the ongoing tropospheric ducting situation, we are seeing messages and repeaters appear sporadically from #CT, #NJ, and #NC despite not having bridged those meshes yet.
We already have NH and RI bridged. CT is only a small gap away from a reliable connection to the rest of the mesh.
We are seeing messages take 16 hop+ paths into Boston and #nh
@occult That is pretty neat. Real question: How are you thinking about “managing” public channels with such a large mesh?
Like, would “public” be just kind of wildly active, but in addition to #test maybe you have more regional specific channels, like #boston? (Maybe you have this already.)
Here in the Bay Area, I’ve seen a LOT more traffic/chattiness in the past few weeks. It’s exciting! But also feels like the transition from when receiving a single email was a thrill to email starting to feel burdensome. 😅
@scott we've been coordinating with our direct neighbors on exactly this. Everyone is using something like #region (and folks have subregions of course, self-organized). Nothing we can do about folks using Public or common channels like #test other than gently nudge them to user other channels.
It would be difficult for 50 people in NH to have a conversation in Public while 200 people in Boston are having a different convo over them, now add in CT and the problem compounds.
occult
Scott Murray 