I typically will only alert when I think cell coverage may be an issue on the summit I’m hiking to. However, now that I see how others may use alerts to adjust their schedules, I’ll try to start alerting more often.
1 Like
I don’t think anyone views an Alert as a contract either for time or a summit.
Having an alert up does unlock things like RBNHole, as well as providing some idea that you’re going to be out. If you can spot when you get there, add an alert too. You can also add wildcard alerts like GM/ES-XXX or GM/SS-???.
1 Like
I still assume that most phantom QSOs are not made intentionally. It is often due to bad conditions, for example, that people think they have been called because a call is made that is very similar.
Maybe QSOs have not been finally confirmed and are considered incomplete by the activator and therefore are not entered into the database, but the chaser thinks everything is OK.
This can of course happen on both sides (chaser and activator).
If there is deliberate misconduct, it is a completely different matter!
Perhaps the MT should think about whether there is another way…
For example, if there is a proven violation (e.g. activation in a restricted area or a wildlife protection zone during the restricted period - and these are often well documented here), the last 5 activations are cancelled. That would also affect the chasers…
But it is up to each individual how we behave as chasers. I don’t chase anyone whose activation I am sure does not comply with the rules. As an activator, I also refrained from QSOs with D1 or D0 stations in the 10m challenge.
73 Armin