

That is… incorrect for a whole host of reasons, not the least of which is the following copyright notice given by the EFF themselves: 


That is… incorrect for a whole host of reasons, not the least of which is the following copyright notice given by the EFF themselves: 


Not just flock. My city recently backed away from flock under voter pressure… only to start seeking a contract with Motorola Vigilant. Which does all the same nasty shit.


I came up on Slackware, used it exclusively from like ‘96 - 08’. Have not touched it since. I have fond memories of debugging XFree86.conf and compiling half of what I installed from source. 🤣 This is a wild slack themed day- I just ran into a Bob Dobbs picture in the wild. 😂


A major remaining issue with Meshtastic is the NodeID being tied to the device MAC. This means that even if you can’t decrypt comms, it is trivial to track a device and thereby a user across geographical areas even with factory resets. This is solvable at a software level and iirc there’s a PR to address this vulnerability, but it has not been merged.
There are ways to make that irrelevant. I use a cheap vps and just have it funnel raw traffic for the ports I need to my home server via wireguard. All my SSL certs live on my machine and the VPS can’t see any of the traffic contents. I suppose they could redirect traffic elsewhere or start serving whatever on that domain, but I would know immediately and there are some limits to my paranoia.