CONTACT THE STATION
How to reach the operator.
Shortwave is a personal project — one person, no company, no support desk. There is more on that on the about page. Mail reaches that one person directly: info@shortwaveradio.online.
What to write about
Faults on the console. The key not registering, audio that will not start, the decoder disagreeing with what you sent, a frequency that shows operators who are not there, anything that looks broken on a phone.
Corrections to the reference pages. The chart, the prosigns, the Q codes, the phonetics and the history pages are meant to be accurate. If something on them is wrong, or right but misleading, that is worth an email. A source helps but is not required — a clear statement of what is wrong is enough to go and check.
Dispatch board suggestions. Subjects you would like covered, or gaps in what is already there.
Advertising and partnership enquiries. These are read. Most are declined, and a generic template is deleted unread, so say plainly what you are proposing.
Reporting a fault
The useful details, in one message: which browser and which device, what you were doing when it went wrong, what you expected instead, and whether the station showed CONNECTED or was trying to reconnect at the time. A screenshot settles most arguments. If the problem involves audio, say whether you had tapped or pressed a key before it happened, since browsers hold sound back until you do.
For anything that is clearly a bug, the GitHub issues page is the better channel. It is public, it will not get buried, and the fix ends up attached to the report.
Before you write
The FAQ already answers most of what arrives by email — how to transmit, what a frequency is here, why you might be in listen-only, and whether anything you key is stored. Questions about data are answered on the privacy page.
Response time
This is run around a job. Expect a few days, sometimes a couple of weeks, and occasionally nothing at all if a message gets lost in a busy inbox. Every message is read. Not every message can be answered, and a bug being reported is not a promise that it will be fixed quickly.