![jt65 spots jt65 spots](https://qrznow.com/wp-content/uploads/2019/07/main-ui-1.4.png)
State: matches on the state (currently US only) of the callsign according to the FCC database, updated weekly – use e.g.Added callsign exclusion conditions: now you can exclude certain (spotter) callsigns, so you won't get an alert even if all other conditions match.Added a Telnet/Cluster emulation server, which allows you to receive alerts in any program that can connect to a DX cluster.
![jt65 spots jt65 spots](https://www.kevinhooke.com/wp-content/uploads/2019/09/image-3.png)
The PSK Reporter source had to be disabled for the time being due to backend overload.Further measures may be necessary as the number of PSK Reporter spots and HamAlert users continues to grow. The PSK Reporter source has been enabled again.Ĭode optimizations and heuristics have made it possible to reduce the amount of CPU resources consumed by the matching engine.The push notification format can now be customized on the Destinations page.Solve this dilemma in the future, but at the moment, my priorities unfortunately do not allow a short-term solution.
![jt65 spots jt65 spots](https://dxnews.com/upload/Image/Palau_T8CW.jpg)
There is an almost exponential increase in the number of spots. The problem with digimode spots is thatĪlmost every digimode user is also a spotter, and as the number of people who participate in digimodes grows, Negatively impacting the other spot sources (Cluster, RBN and SOTAwatch) by causing long notification delays. PSK Reporter traffic has approximately doubled, reaching 23 million spots per day, or an average of more than 250 per second (!), with even higher peaks.Ĭombined with an increase in HamAlert users and triggers, this is putting more load on the system than it can handle, Since the beginning of the Corona virus crisis,
![jt65 spots jt65 spots](https://2.bp.blogspot.com/-nBWBChyF9os/Uud_y7YlKGI/AAAAAAAAMPE/w4PIpJStE1g/s1600/JT65+SPOTS.jpg)
WAS or monitoring for a friend's callsign etc.). Still unsuitable for some other purposes (e.g. This greatly reduces the number of spots to be processed and makes HamAlert usable again for digimode DXing in the short term, although Least wanted DXCCs according to the Club Log DXCC Most Wanted List. Upon the suggestion of a user, the PSK Reporter source has been enabled again but ignores FT4/FT8 spots for the 40 FT4/FT8 spots from PSK Reporter on 6m and higher bands are now processed again for all DXCCs (including the 40 least wanted).FT4/FT8 spots from PSK Reporter on 17m and higher bands are now processed again for all DXCCs (including the 40 least wanted).Only FT4/FT8 spots on 80-20mįor the 40 least wanted DXCCs are filtered. FT4/FT8 spots from PSK Reporter on 160m are now also processed again for all DXCCs (including the 40 least wanted).Only FT4/FT8 spots on 80-20m for the 30 least wanted DXCCs are now filtered.Updated various libraries and frameworks.Added a setting to use the local time instead of UTC within the app (does not apply to push notification contents, as those are generated by the server, but you can customize the push format on the Destinations page).FT4/FT8 spots from the Reverse Beacon Network (RBN) are now also processed, and are not subject to any limits regarding bands or least wanted DXCCs.Added SNR condition (dB, for RBN and PSK reporter spots).Added speed condition (CW WPM, for RBN spots).The PSK Reporter source is currently: PARTIALLY ENABLED (excluding 30 least wanted DXCCs on 80-20m).