[Top] [All Lists]

Re: [CQ-Contest] Self Spotting

To: Stephen Bloom <sbloom@acsalaska.net>, "cq-contest@contesting.com" <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] Self Spotting
From: Dale Putnam <daleputnam@hotmail.com>
Date: Wed, 8 Nov 2017 17:21:20 +0000
List-post: <mailto:cq-contest@contesting.com>
We could.... make it a practice to always check 10 ... on the 10s... 15 on the 
15s.. 20 on the 20s..

THAT makes sense to me...  without rules.

Have a great day,
--... ...-- Dale - WC7S in Wy

"Actions speak louder than words"
1856 - Abraham Lincoln

From: CQ-Contest <cq-contest-bounces@contesting.com> on behalf of Stephen Bloom 
Sent: Wednesday, November 8, 2017 10:05 AM
To: cq-contest@contesting.com
Subject: [CQ-Contest] Self Spotting

Hey all:

I mostly stay out of the rules change discussions here except for the
occasional snark, but I have been thinking about this one a bit.  I know it
has been discussed before but, I am wondering if there is some level of self
spotting for SSB contests that most would find acceptable, and would be
feasible for the various rule committees.  For CW and Digital, most of us
are now used to skimmer/cluster spotting.  I think most like it, some don't,
but it's part of the landscape now even for those who themselves operate
unassisted.  For SSB as an example, it is extremely frustrating to *know*
that say, 10M is open to somewhere, yet it is impossible to get anything
going there, since the odds of several of us checking it out at the exact
same time at this point in the sunspot cycle is low.  I don't know exactly
what rules would work (self spot only so often?), but it seems that allowing
it would raise the overall fun level, without changing the basic
architecture and strategy.  Thoughts?


Steve KL7SB

CQ-Contest mailing list
CQ-Contest Info Page - Contesting.com Ham Radio Mailing 
CQ-Contest@CONTESTING.COM is an electronic mail reflector dedicated to hams 
interested in all types of amateur radio contesting. This is a good place for 
contest ...

CQ-Contest mailing list

<Prev in Thread] Current Thread [Next in Thread>