For Spothole (https://spothole.m0trt.radio/), I think basic parsing should happen here and then stuff can get passed along via UDP unless that's bad form or too much data.
For Spothole (https://spothole.m0trt.radio/), I think basic parsing should happen here *and* then stuff can get passed along via UDP unless that's bad form or too much data.
/// Prints a single session line with a timestamp, source, destination, and summary.
fn print_session_line(timestamp: &str, source: &str, destination: &str, summary: &str) {
let line = format!("{} {}>{} <{}>", timestamp, source, destination, summary);
println!("{}", line);
}
See https://gitea.farpn.net/w1cdn/mwtchahrd/src/branch/udp/src/main.rs#L295.
```
/// Prints a single session line with a timestamp, source, destination, and summary.
fn print_session_line(timestamp: &str, source: &str, destination: &str, summary: &str) {
let line = format!("{} {}>{} <{}>", timestamp, source, destination, summary);
println!("{}", line);
}
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For Spothole (https://spothole.m0trt.radio/), I think basic parsing should happen here and then stuff can get passed along via UDP unless that's bad form or too much data.
APRS-specific parsing in Rust:
See https://gitea.farpn.net/w1cdn/mwtchahrd/src/branch/udp/src/main.rs#L295.
Handled some of this in #1.
Splitting location parsing off to #10.
Parse packets here or in FARPN UDP Server?to Parse basic dataAs you can tell, N6CTA did most of the work and I just packaged it up.