The clock is the server's, as asked: it is the machine at the radio, where
the browser may be a phone in another timezone with a clock nobody checked.
When the two disagree by more than a second the panel says so, rather than
logging a time the operator did not expect.
The rest, decided against how logging is actually done:
One station log, not one per rig. DXCC, WAS and LoTW count the callsign, not
the radio, and a station worked on the second rig is still worked. The rig
goes on the QSO as MY_RIG. Station location does follow the rig, though —
these rigs can be in different places, so MY_GRIDSQUARE comes from the one
that made the contact, which is what LoTW's station locations expect too.
The operator is a per-QSO field set once per session. ADIF separates the
callsign used on the air from the person at the key, and multi-operator
stations rotate people through one station callsign. It defaults from the
configured callsign, so a single operator never touches it. It cannot come
from the session: the auth roles are control and rx, with nobody's name on
them.
The log file is configurable, defaulting to the user's data directory.
Bookmarks sit in the config directory because they are settings and decode
logs in the cache directory because they are disposable; a QSO log is
irreplaceable, and cache directories get swept.
Import collisions match on callsign, band, mode and a two-minute window.
Loggers rarely agree to the second on the same QSO — one stamps the contact,
the other the entry — so an exact-minute key duplicates half of what it is
asked to merge. Two minutes absorbs that without swallowing a legitimate
re-work, since contest rules forbid a second contact on the same band and
mode. Times compare as instants so midnight matches, and modes are
normalised or an imported SSB would miss our USB.
That normalisation is now written down: a rig mode is not an ADIF mode. DIG
is the one the rig cannot answer — a rig in DIG is in FT8 or FT4 depending on
what is decoding — and WSPR never opens an entry at all, because hearing a
beacon is not a contact.
Refs #54
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SyX26FCpMQxiBoC7r5K1A7
Signed-off-by: Stan Grams <sjg@haxx.space>
sjgandClaude Opus 5
83b453135a