Wow, #4 is frustrating. (Disclosure: am a ham, but not one of the uptight ones. I'm not personally offended when someone breaks the rules, and I'm not gonna run off and call the FCC or something. But I am concerned when they don't seem to know or care why.)

First, I don't know if their interpretation of the rules is correct. For the sake of argument, I'll assume it is. More importantly, most other people in that thread seem to be going along with the idea that it is correct. This is how it reads to me:

Submitter: We're violating the rules and should make this change.

Replier 1: That change would be inconvenient in Seattle so we're not doing it.

Replier 2: It wouldn't work well in Boston, either, so it's a no-go.

Part of me wants to shake them. This isn't 'Nam. There are rules. Whatever you think about the FCC regulations, they're not voluntary, and they certainly don't have an opt-out for "it wouldn't work as well that way". To a first approximation, everyone else using the public airwaves is more or less following the law. If following the law makes your project not work as well, that's your problem. It's on you to fix your project so that it's legal to use.

I'm not one of those old hams who gets hyper cranky about this stuff, but I do understand how they come to be that way. The only reason we can use the spectrum at all is that people are mostly using it legally so that their work isn't interfering with everyone else trying to use the same public resource.

>Would you trust AI generated mesh firmware?

This is also a loaded question. The only specifics they've offered are that he simply used Claude Code. Um... OK? Do the tests pass? Did his changes add any security flaws? Regressions that were untested?

What's an example of a GPS coordinate "outside earth's bounds"?

what's even the need to transmit/receive GPS as part of the protocol?

> It's ridiculous to me that they're concerned about the trustworthiness of AI-generated code when their code quality is so low.

Agreed, but at least it's somewhat sensibly structured. AI? Good lord you'll end up with a slopaghetti mess.

> They don't even have automated tests and ignore attempts to add them.[0, 1, 2, 3]

Two people, 540 issues and 270 PRs open at the moment. Not wanting to be that guy... but do the math. The reviewer team is small as hell and after this drama (which probably kept both of them busy with BS) they'll likely be even less willing to trust others.

If you want to stand a better chance at getting your code into other people's hands, go and contact the person behind the Evo fork. IIRC he's part of Hansemesh, Germany's biggest regional MC.

I have heard indirectly multiple times now that the only two ways to get a PR of interest merged is to either gather enough people to Like the issue on Github or to join the Discord and ask.

[1] https://github.com/mattzzw/MeshCore-Evo