- # Note, there is no intelligence here, but there are clearly basic heuristics that could
- # be applied at this point that reject (more likely rewrite) the call of a busted spot that would
- # useful for a zonal hotspot requirement from the cluster node.
-
- # In reality, this mechanism would be incorporated within the cluster code, utilising the dxqsl database,
- # and other resources in DXSpider, thus creating a zone map for an emitted spot. This is then passed through the
- # normal "to-user" spot system (where normal spots are sent to be displayed per user) and then be
- # processed through the normal, per user, spot filtering system - like a regular spot.
+ # The main de-duping key is [call, $frequency], but we probe a bit around that frequency to find a
+ # range of concurrent frequencies that might be in play.