There’s been like 14 similar cases of this.
I imagine the Flock techs, installing a fleet of cameras for the local fuzz, do training seminars where they encourage exactly this kind of thing (surveilling romantic partners). Still, the fact remains that the fuzz have good reason to know that that in particular is not allowed under any circumstances.
This is a hijacking: True — the reader is damaged by restricted access, but it is also true that the author is damaged.
You post something that you intend to be read by the general public. You don’t control access; the place where you post it does. After age gating mandates, that place will assume the worst — that your content is adult content.
There are three age tiers: adult, young adult, and infants. After age gating mandates, many of your readers in the general public won’t comply by stipulating their ages. The worst-case assumption is that they’re all infants.
When age gating breaks down, there’s a mismatch between default age rating of authors’ content with default age rating of readers. Content that is adult by default won’t reach readers who are infants by default. Much of your content will go unread by much of the general public. One assumes this is age gating’s intentional design — to restrict access to your content.
Same. Nobody listens to his radio 24x7. Hardly anyone ever responds to “Hello, World!” messages in real time. We do see nodes located far, far beyond the horizon. On a good day, there are way over 150 nodes operating, which is enough to keep channel utilization above 10% without any traffic beyond NodeInfo, Telemetry, or Position.
I don’t know what it’s all for. A couple of friends keep nodes charged and on the air locally. We expected to be able to exchange off-grid text messages, but, on a bad day, only about 2/3 of our messages ever go through. We need more LOCAL nodes! It’s difficult to imagine how to advertise though.
I suspect the agenda of Ham-Radio Operators with regard to Meshtastic who had nodes up before we did was just to dabble with the technology. Their agenda with regard to emergency preparedness is much more robust. For example the list of certifications required of Salvation Army Team Emergency Radio Network volunteers is (long):
"All SATERN Members • Must be a FCC licensed amateur radio operator • Must have an up to date completed volunteer profile • Must be credentialed and have an ID badge • Must follow the amateur radio operators code of conduct • Complete Safe from Harm training • Complete Introduction to Emergency Disaster Services training • Complete FEMA ICS-100 and ICS-700 • Complete Salvation Army SA-200 Incident Command System Training • Be proficient with net operations • Be proficient with the ICS-214 form • Be proficient with the ICS-309 form • Understand the ICS-217 and ICS-205 forms • Be proficient with the ICS-213 message and ARRL radiogram • Must have an understanding of how to report and/or halt any unsafe operations.
"TYPE FIVE Shadow Communicator, TYPE FOUR Canteen Communicator, & TYPE THREE VHF / UHF Communicator
“In addition to the general training and proficiencies above: • Must have a Technician Class License or higher • Recommended Completion of FEMA AUXCOMM training • Be able to program their radio equipment in the field without the aid of a computer • Know their radios’ capabilities and limitations • Arrive equipped to meet the needs of the team typing • Be able to function in high stress environments and in adverse conditions • Be able to serve as a net control operator • Be physically fit and able to walk for 10 minutes or more to serve as a shadow • Be able to lift 50 lbs as part of a canteen crew. • Type Three must be qualified to drive a Salvation Army vehicle (must have a valid driver’s license and be a Salvation Army approved driver)”
… so, if Meshtastic node owners aspire to having any role to play in emergency preparedness, then just operating a $50 LoRa radio probably isn’t going to cut it. Understanding how to keep out of the way of the folks doing the heavy lifting is important, too. Meshtastic Users’ getting the cold shoulder from anyone else having the least familiarity with emergency services is surely plausible.
Yeah, I don’t know what’s going down, so, one of these days I suppose, I’ll get pinched.
I live in a medium-sized town with a dozen Flock cameras, which the police shrouded in garbage bags a couple of weeks ago (to defuse public outrage and ward off vandalism I suppose). Two days ago, the Common Council voted to break the Flock contract. The issue has been unsatisfactorily explained in the news. I mean — what did city government think would happen to the data? Surely they knew it would be kept for awhile and be searched. News makes it sound like they flipped when Flock tried to sell them a five-year traffic-pattern analysis.
The story (above) shines a (feeble) light on what may have gone wrong. It appears that police have been taking license numbers of cars that have been parked in shady locations and running those numbers against cameras all over creation to see whether they get hits in other parts of the country. The last thing local authorities want is an out-of-town authority charging in and following a lead on a suspicious vehicle up to no good in around here. That’s not what they bought the Flock cameras and put them up for. They were misled that the data would remain local for local use. I still don’t get the angst, though.
All I know is that I can’t get a hamburger to go, drive to a city park, eat it, and take a half-hour nap without some plain-clothes cop or vigilante waking me to ask what I’m waiting for.