Put your users on the live map in three lines.

01Send one datagram on frequency change

One UTF-8 JSON object per update, ≤ 1 KB. Fire-and-forget — no reply to parse, no connection to keep open.

import socket, json
socket.socket(socket.AF_INET, socket.SOCK_DGRAM).sendto(
  json.dumps({"freq_hz":14074000,"mode":"FT8",
              "source":"MyLogger"}).encode(),
  ("127.0.0.1", 7373))

QUdpSocket s;
s.writeDatagram(
  R"({"freq_hz":14074000,"mode":"FT8","source":"MyLogger"})",
  QHostAddress::LocalHost, 7373);

require('dgram').createSocket('udp4').send(
  JSON.stringify({freq_hz:14074000, mode:'FT8',
    source:'MyLogger'}),
  7373, '127.0.0.1');

# fire-and-forget, no wait
echo '{"freq_hz":14074000,"mode":"FT8"}' \
  | nc -u -w0 127.0.0.1 7373

02Payload

Send whichever frequency unit you already have — no conversion on your side.

03Why there is no authentication

The trust boundary is the operator browser, not the packet.

The operator is already signed in to ham-radio.live in their browser, and that session carries their identity. The connector only reads 127.0.0.1:7373 and forwards frequency to that logged-in session. The port is bound to loopback, so nothing off the machine can reach it — a local sender can only ever affect its own operator session. No API key to issue, store, or leak.

04Already broadcasting? You may be done.

The connector also listens on the standard ports loggers already use. Emit on one of these and integration works today — nothing to build.