WYGIWYG
I’m mostly worried that at some point they’ll fire up a client, note the nodes it’s connecting to, send police to their locations, nested wash rince repeat.
I was actually kinda stoked at AI because we could have it locally write semi-plausible fiction with digital payloads embedded. And all of a sudden our social media is based on a database hidden in bad vampire fan-fiction.
There is 0 meshcore anywhere near me. I drove heltek v3’s around my beltway, nada.
I would think a mile should be doable to your kid’s school.
Nope, tried it, no radio line of site. it’s a little hilly here and there’s a shit ton of old-growth forrest in between.
I’ve been trying to find a tree tall enough to repeat with clear solar from the south, that’s not on someone’s property, The only good options are in the middle of a swampy run.
I have. Threw an external antenna on my roof just peaking above the crest (HOA hasn’t noticed yet). I Keep nodes set as router-late in my car so when I go driving I can see other people exist.
TBF, even when I’m out, I’ve never made contact on the mesh. There are a dozen meshtastic nodes here and there, best I can tell it’s just a couple other hams, no real comms going on. Even the VHF Ham scene here is mostly dead.
My actual goal was to get a half-decent signal for my kids’ bus route and school. The school is only a mile away, but it’s not like i’m going to throw a $300 aprs radio in his bag, a $30 LoRa capsul though, sure!
The protocol is reasonably private. Trying to find exact sources of a piece of traffic is about as hard as it can be. Reading the contents of the traffic is also at a very high bar.
The downside is, it still needs visible nodes to connect to, and the VAST majority of us only actually have access to TCP routed networks for that purpose. The only way you’re talking to that reticulum node in Norway from California is because BGP is delivering your crypto stream for you.
If you have a small neighborhood and you’re all like-minded, you could use reticulum over HaLow or LoRa network adapters to create a private, IP-less mesh and it could go as far as you can find more people willing to run the hardware. HaLow has enough bandwidth to stream video, LoRa is mostly only good for text. Of course, If someone is doing something like video, it won’t take much to saturate everyone’s connection. It’s not like someone could run a Plex server and everyone could be watching it in the neighborhood at the same time; that 30MBPS can only handle a couple of decent-quality streams.
Compared to the open internet and the slightly dark parts of the internet, there is nothing of great interest, except the fact that no one can easily hunt down what you did while you were there.
The real problem is, by the time you actually want to be there because there is no anonymous access to the real net, they’ll ferret out people running i2p at all and block them from doing so.
I’ve totally wanted to do something neat with Reticulum; we just lack a way to communicate video speeds over long distances without last-mile service providers. I’m sitting on a pile of HaLow / meshtastic gear, but I’m too broke (and close to an airport) to put up a good mast and I live far enough in a hole that I can’t get to the main artery of RLOS.
I send up mesh nodes on a drone once in a while and I can see a hell of a lot of net.
I2p and Reticulum scratch the general area of the privacy itch, But I worry that the government will decide that pricacy is treason, start a client and start going node to node dropping the hammer on people.
Hey troll, that’s from the fucking link. go read it yourself. and welcome to my blocklist
They told him that paying him was out of the question and he said ohhh
They can fucking pay him.
The updated post contains the full story, and it goes as follows: Back in February, when AMD asked Paul to bring down the blog post temporarily, the company said it would issue a standard CVE, fix the software, and attribute the findings to him, though a bounty payment was out of the question. Paul agreed (a decision he now regrets), though he asked what kind of timeline AMD would follow, suggesting the industry-standard 90-day window until he posted the public disclosure again.
AMD replied saying that it would “likely need a longer embargo, as additional tools beyond Ryzen Master appear[ed] to be impacted and [would] need releases.” That was an interesting statement in several ways: first, it raises the question exactly why AMD would need so long to publish what was seemingly a one-character fix, replacing “http” with “https” in the code. Second, if the issue was bad enough to require so long to solve, then arguably Paul’s work would merit some recompense. Third, as Paul pointed out, if this issue looked this pressing, why didn’t it have a higher priority?
Nevertheless, he ended up agreeing on a 100-day window, and asked AMD the equivalent of “wassup?” before the clock ticked its last tock, only to be asked for extra time again, being told that “multiple tools are affected by [the bug]”, and that “[AMD’s] customers request additional time once [the fixes] are made available.” Eventually, AMD reached out stating that a fix would be ready on June 9, totaling 124 days after the initial finding.
“the company said it would issue a standard CVE, fix the software, and attribute the findings to him, though a bounty payment was out of the question.”
Nah, they should pay him…
They could have sat on 30 second ads every 15 minutes till the cows came home and most of us would have been fine with it.
They could have sat on premium family for $9 a month for years and we’d have been ok with it.
They had to be greedy as fuck until none of us want to use their services.
If I weren’t so close to an airport, I’d do a tethered balloon. I do have a drone so i could lay paracord over a high branch and hoist it up if I had the gear to not get bit by something nasty. If I wasn’t so worried about the cost. I could just strand a solar node up there with a long break-away line and just write it off when it needed batteries.