Repository navigation
Multiple callsigns displaying poorly on the website #1
Description
The example below provides the expected trigger at HamAlert, but the presentation is poor, with all 3 callsigns in the trigger title:
W1AW,K3LR,DX1DX rather than:
3 callsigns
DX1DX, K3LR, W1AW
or
51 callsigns
AC4NK, AE6Z, AE8I, ...
This is particularly poorly presented as the callsign count within the trigger increases. It's particularly bad on a mobile device. Adding a space after the callsign separation comma fixes this issue (or only using a space for separation)
Activity
darryldunkin commentedon Mar 12, 2026
I think I figured this one out. If you use the '--compact' mode this sort of works, but it still sends the callsign as a single string.
Hamalert is expecting the data to come through as a JSON array instead of a string. If you edit the entry in the website, and choose 'list' it will re-create the entry correctly.
This shows the difference:
darryldunkin commentedon Oct 11, 2026
I've been sitting on a branch for a while, but wanted the recent updates. I merged in the most recent changes and 'fixed' this the best way I could.
#7