There is no real use case, IMO.
I setup a few nodes a couple of months ago. It's mostly no activity, punctuated by some random "can you read me" type messages, and for some unknown reason people who think there is something impressive about them having a node on a commercial flight.
The entire thing would fall over in any kind of scenario where you needed to rely on this janky mesh network as a primary means of communications.
It can be fun/useful for very out of the way things where you have a handful of people out camping, or other off-grid situations. But frankly even in those cases there are far better/established ways to keep in sync if you need to (eg: FRS).
This stuff is mostly a solution looking for a problem.
Many upper level managers seem to be blind to the fact that the kind of person who can actually excel as a "do it all" is most likely not the kind of person that wants to work in that kind of environment. Those people will do a year or two pulling down a salary while they are also spinning up a side project, and then they'll bolt as soon as they can. It sounds like a recipe for constant employee churn, leaving behind a wake of fragile code.
Most sensors can be implemented in a way that enables self-calibration.
I'm oversimplifying it here, but the macro process is taking some known attributes and mapping them to what you are observing. For example, if you can detect people, and you know the average height of a person, you can compute where your horizon is, and where you should (or shouldn't) expect to see people in the FOV. You can do this with cameras, lidar, etc. When you have multiple sensors you can do a lot more to have them all sample an object in their own ways and converge on agreement of where they are relative to each other and the object.
That has been a global problem, lots of it in the US as well. I tend to only buy honey from known local producers, either at specialty stores or street markets.
Interesting Cuecat story: LibraryThing bought a massive stock of Cuecats and, 20 years later, they still sell them, repurposed to scan ISBNs from books for cataloging purposes: https://wiki.librarything.com/index.php/CueCat_Guide
Slashdot is still online and updating. Some of us still use optical drives from time to time (especially those of us with an existing stock of M-Disc media for long-term archiving).
Gateway was purchased by Acer, so it’s not like they just disappeared. Not any more than DEC, SBC, or Studebaker anyway. They were just absorbed.
I usually solve the across words with the clues and then try to do the down words without the clues.
It would be nice if the board were a little bigger to give you more room to try and organize the wordlets (not sure what to call the letter groups?) and try different arrangements.
Oh that's an interesting play style! It's fun to learn about the challenges players layer on to the base game.
Good feedback about the board size... that's tricky. The problem is that many people play on their phones with small screens. If I increase the grid size then each individual tile shrinks. In my testing that can make it harder for people with poor vision to read the tiles and also make it harder to use the touch controls.
But, I agree on desktop it would be really nice to have more space. I may explore letting people configure the grid size when they submit custom puzzles and use that as a test of larger grids!
I've played with MeshCore and Meshtastic a bit, and while they are fun, the general hype seems overblown. The "SHTF" types that get involved with this tend to just taint the whole concept for me. I was/am interested in the use cases for building sensor networks, but most of the chatter seems to be around people who just want to send Hello World type texts back and forth, without realizing how poorly a network like this would perform in a real SHTF scenario.
I got to participate in a game that used Meshtastic and GPS where you walk around a large camp and "capture" different regions. It worked great for that and was a lot of fun.
If there ever where a more serious situation where my life depended on one of these meshes, I would be feeling pretty uneasy. They are absolutely not reliable enough to even consider such a thing. I suppose they might be better than nothing.
To say nothing of what is required to set up the devices. I wanted to put a full dev system on a raspberry pi 3 just so it would all be in one place and I could work on it when in a location with no internet - it ran out of memory trying to compile the massive web app that is the default client interface.
It was just something a friend of mine came up with - we called it "Area Capture" or something (and was ironically, mostly vibe-coded).
There were 4 or 5 "color" teams. Each one carries a meshtastic node, and they all report to a central server back at base. The play field was roughly a square mile divided up into a grid of smaller squares. If you walk into one and it's past the cooldown time, it claims it for your team. Most squares at the end of two hours wins. The server would send out updates over meshtastic also: "Blue captures H12" "Red has 18", etc. If you were at the base station, you got to see it all play out live on a big map.
There was another one played at night which was a hide and seek game / capture the flag sort of game. It would tell the seekers some limited information about the seekers, and each side had special functions they could use. Hiders could "go invisible" or fake their location for a certain time. Seekers could call a limited number of "drone strikes" on different squares. The game ends when either the hiders are caught, or they make it to a specific target location.
Lots of possibility for that sort of thing with Meshtastic. I guess either could have run on a phone since now even rural camping areas have decent cell coverage these days, but that's not quite as impressive.
I feel the same way, and both mobile apps are pretty janky, with Meshtastic being extra obnoxious because the UI teams between Android and Apple apparently don't talk to each other- very hard to onboard/answer questions from someone new if you're on a different platform than them.
It was fun and cheap to set up, but I look forward to something with better messaging persistence so you can at least reliably not miss stuff.
I largely agree and want to add more,I also think the lack of standards also will effect it's usability in a real shtf scenario. why should I use meshstastic over meshcore for example. I also don't think lora will be in my mind in that kind of scenario.
We have a pretty big meshtastic/meshcore / reticulum scene in Taiwan organized through g0v's civic defense group. It's a nontrivial issue for us when the PRC keeps cutting our cables - which is why Audrey Tang was hitting up Starlink back when they were the digital minister.
Basically we very much may need these secondary networks someday.
I really want to get plausible "Walkaway" intranet set up here with e.g. mirrored Wikipedia and whatnot, I don't know enough yet to do that though.
I'm not aware of janky laws in Florida, when I had panels installed on my last house in 2017 there wasn't much friction from the perspective of laws. Standard permitting process (basically just expensive paperwork).
The issue was with the insurance companies. We had an 11.6Kw array, and it was getting difficult to find insurers that would allow more than 6Kw of rooftop solar.
reply