Simple solution, which I've advocated before. Logs (at least
"competitive" logs) should be sent in by 0100Z, one hour after the end
of the contest. Exceptions for DXpeditions and others on an individual
basis. If you're using unreliable or outdated software requiring
merging/massaging of logs, etc., too bad. That's part of contest
preparation. It's no different than if something else breaks and you
have to fix it during the contest.
Barry W2UP
Julius Fazekas wrote:
> Tree,
>
> Somehow I can just picture your eyes alight in ecstasy
> over the possibilities of skimmer log checking...
>
> It will solve some problems and maybe create new ones.
>
> What would prevent someone from going back and
> changing their log based on the recording of the
> contest?
>
> Could you listen to the recording during breaks and
> change your log?
>
> Could these audio files be doctored to include uniques
> that aren't real?
>
> "Could" is most likely not the right word ;o)
>
> Anyway, think you get my drift. Just something else to
> ponder and maybe a design consideration for this type
> software. Maybe some sort of time lock could be
> incorporated to limit access until after the submittal
> period? Then how would computer crashes or "gaps in
> the tape" situations be adjudicated?
>
> Ahhhh, the sweet smell of technology!
>
> 73,
> Julius
>
>
> Julius Fazekas
> N2WN
>
> Tennessee Contest Group
> TnQP http://www.tnqp.org/
>
> Elecraft K2/100 #3311
> Elecraft K2/100 #4455
> Elecraft K3/100 #366
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
>
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|