4 ms·

Not necessarily, there are a lot of variables. If someone is a fugitive of a government and is using ham radio while also being stationary, sure. I think most H

Not necessarily, there are a lot of variables. If someone is a fugitive of a government and is using ham radio while also being stationary, sure. I think most HAMs are aware they can track signals that are stationary quiet well. After all, the cats who get caught breaking the rules are usually doing it daily for months. Think of the occasional crazy old bat who decides to do a pirate radio station. But so long as the individual is on the move it becomes more difficult. That is also supposing a government from a federal down to local level are monitoring all ham frequencies 24/7. Now if we are talking like a rebellious faction within a country, well they are technically breaking all other rules of the nation anyways, so no-encryption HAM rules suddenly becomes the line in the sand they draw as to not cross?

generalizations 5y ago
That's a pretty far-out use case, if you even specified one. The utility of a long range, decentralized, encrypted mesh net is pretty broad in comparison.
- sliken 5y ago
  I'm all for the idea of a long range, decentralized, encrypted mesh net. I've read a fair number of papers proposing and analyzing different approaches to make this happen. Unfortunately, unlike the internet, or a local mesh network the total collective bandwidth isn't there. If it worked people would try to do full duplex audio with loved ones, file sharing, monitoring GPS coordinates of fleets of vehicles, internet gateways, and a zillion other bandwidth intensive things. Bandwidth is so low, that even sending bytes is rare, encoding that average a few bits per character are common. Such encodings try to minimize the bits by using less bits for more common english characters, so they often are measured in words per minute instead of bits or bytes. There was exist various hybrid solutions like APRS (which can use ham + internet), winmail (ham + internet email), various digital radio protocols (ham to tower, which has an internet connection). But a pure radio mesh net just doesn't seem practical.
  - generalizations 5y ago
    Done enough research into this that I'm familiar with the stuff you're describing. I remember looking into those packet radio protocols, and honestly, they seemed kinda rudimentary, especially (IIRC) the error correction algos. Seems like there's a lot of low-hanging fruit in that area. > I'm all for the idea of a long range, decentralized, encrypted mesh net. I've read a fair number of papers proposing and analyzing different approaches to make this happen. What do you think the fundamental value of a meshnet would be? For my part, seems like an (encrypted) text-only system with high latency (15 minutes per paragraph, even) and a range of hundreds of miles between hops, would be preferable to something capable of streaming HD video that was restricted to hops of only a few hundred feet. I think that's a fair comparison of what the physics can handle, and I think that if the former existed, there'd be a lot of people using it. Edit: looks like I edited out from under you. Sorry, didn't think you'd see it so quick.
    - sliken 5y ago
      The bandwidth is so low it's a bit mind boggling. On a particular frequency you might well be broadcasting/interfering with a fair chunk of the united states and only managing 4.6 bits/sec. If it's 3 hops then divide that by 3. I just don't see any kind of metadata tracking of peers, requests, mesh status, etc being reasonable at that low bandwidth. Sure, could a few people handle email like setups, sure. But even a small bump in popularity and it would be saturated and everything would break and nobody could use that frequency. Once you adapt fully to that bandwidth I think you'd end up with things much like what we already have like winmail and js8call.
      - generalizations 5y ago
        I'm not convinced there aren't ways to make it feasible. It would certainly select for high-value messages, and there'd have to be systems for avoiding DDOS-style attacks. I remember doing a back of the napkin protocol for such a network, and assuming that most messages were tweet-sized and took 5 minutes to send. I get it, though I think you're describing a worst-case scenario. Bunps in popularity would just extend the latency. I think there's ways to overcome the problems and exploit the unique advantages. The thing with things like JS8call is that it's still like using a postcard instead of a letter. I don't use postcards because I wouldn't put anything more than a superficiality on them.

generalizations 5y ago

That's a pretty far-out use case, if you even specified one. The utility of a long range, decentralized, encrypted mesh net is pretty broad in comparison.

sliken 5y ago
I'm all for the idea of a long range, decentralized, encrypted mesh net. I've read a fair number of papers proposing and analyzing different approaches to make this happen. Unfortunately, unlike the internet, or a local mesh network the total collective bandwidth isn't there. If it worked people would try to do full duplex audio with loved ones, file sharing, monitoring GPS coordinates of fleets of vehicles, internet gateways, and a zillion other bandwidth intensive things. Bandwidth is so low, that even sending bytes is rare, encoding that average a few bits per character are common. Such encodings try to minimize the bits by using less bits for more common english characters, so they often are measured in words per minute instead of bits or bytes. There was exist various hybrid solutions like APRS (which can use ham + internet), winmail (ham + internet email), various digital radio protocols (ham to tower, which has an internet connection). But a pure radio mesh net just doesn't seem practical.
- generalizations 5y ago
  Done enough research into this that I'm familiar with the stuff you're describing. I remember looking into those packet radio protocols, and honestly, they seemed kinda rudimentary, especially (IIRC) the error correction algos. Seems like there's a lot of low-hanging fruit in that area. > I'm all for the idea of a long range, decentralized, encrypted mesh net. I've read a fair number of papers proposing and analyzing different approaches to make this happen. What do you think the fundamental value of a meshnet would be? For my part, seems like an (encrypted) text-only system with high latency (15 minutes per paragraph, even) and a range of hundreds of miles between hops, would be preferable to something capable of streaming HD video that was restricted to hops of only a few hundred feet. I think that's a fair comparison of what the physics can handle, and I think that if the former existed, there'd be a lot of people using it. Edit: looks like I edited out from under you. Sorry, didn't think you'd see it so quick.
  - sliken 5y ago
    The bandwidth is so low it's a bit mind boggling. On a particular frequency you might well be broadcasting/interfering with a fair chunk of the united states and only managing 4.6 bits/sec. If it's 3 hops then divide that by 3. I just don't see any kind of metadata tracking of peers, requests, mesh status, etc being reasonable at that low bandwidth. Sure, could a few people handle email like setups, sure. But even a small bump in popularity and it would be saturated and everything would break and nobody could use that frequency. Once you adapt fully to that bandwidth I think you'd end up with things much like what we already have like winmail and js8call.
    - generalizations 5y ago
      I'm not convinced there aren't ways to make it feasible. It would certainly select for high-value messages, and there'd have to be systems for avoiding DDOS-style attacks. I remember doing a back of the napkin protocol for such a network, and assuming that most messages were tweet-sized and took 5 minutes to send. I get it, though I think you're describing a worst-case scenario. Bunps in popularity would just extend the latency. I think there's ways to overcome the problems and exploit the unique advantages. The thing with things like JS8call is that it's still like using a postcard instead of a letter. I don't use postcards because I wouldn't put anything more than a superficiality on them.