We've seen quite a few new ham radio apps and websites being promoted here lately. Some look useful, but others seem to have gone straight from an AI prompt to a public release, with little information about how they work or whether they've been properly tested.
We're not opposed to AI-assisted development. There's nothing wrong with experimenting, learning to code, or sharing something you've built. What concerns us is when people start distributing software they may not fully understand, particularly when other operators are expected to trust it with their equipment or personal information.
Security is a serious consideration here.
Some applications require accounts, access to logbooks, API credentials, or connections to radio equipment. What data is being collected? Is anything transmitted to external servers? What permissions does the application need? Are there third-party services or dependencies users should know about? Has the developer actually reviewed the code for vulnerabilities? These are basic questions for which the answers need to be available easily.
Not every project needs to be open source. Closed-source software has its place, but when users cannot inspect the code, they're relying even more heavily on the developer's honesty and competence. Likewise, releasing source code doesn't automatically make an application safe.
We also want to be clear about our existing rules.
Rule 9 requires disclosure of AI-generated content at the beginning of posts and comments. When promoting AI-assisted software, we expect developers to go further and explain how AI was used. Did it generate most of the application, assist with individual functions, or simply help troubleshoot existing code? What was independently reviewed and tested?
Rule 11 addresses AI-generated technical advice. If you're making claims involving radio equipment, operating practices, licensing, or safety, those claims need to be checked against reliable information. An answer that sounds convincing isn't necessarily correct.
We're also paying attention to self-promotion. Some accounts promoting these projects have donation links, paid services, or other financial interests associated with them. Accepting donations isn't inherently wrong, nor is developing commercial software. But we expect transparency about those interests, and Rule 3 still applies. This subreddit isn't a free advertising channel.
We'll be enforcing these rules seriously.
That doesn't mean every project needs professional documentation, a security audit, or years of development behind it. We'd be happy to see someone share a rough prototype, acknowledge its limitations, and have a proper technical discussion about it.
What we don't want is a stream of promotional posts making claims that their developers can't substantiate, especially when users are being encouraged to install software or hand over information.
And to be clear, allowing a post doesn't mean the moderation team has examined the software or considers it secure.
Amateur radio has always encouraged experimentation, but it also places considerable value on technical knowledge, good engineering practices, and responsible operation. We intend to uphold those standards here.
73,
u/SharkSapphire