Topband
[Top] [All Lists]

Re: Topband: ARRL DXCC - 160 Meters

To: <w5zn@w5zn.org>, "'topband'" <topband@contesting.com>
Subject: Re: Topband: ARRL DXCC - 160 Meters
From: <n4is@n4is.com>
Date: Sat, 17 Nov 2018 08:28:42 -0500
List-post: <mailto:topband@contesting.com>
Hi Joel

I have the same impression as Bill mentioned. 160m paper QSL requires a card
checker, however LOTW confirmation does not have the same process, no QSO or
QSL check at all. We've seen 160m " QSO's"  on Club Log  and subsequent
confirmation on LOTW on plain day light.

73's
JC
N4IS

-----Original Message-----
From: Topband <topband-bounces@contesting.com> On Behalf Of w5zn@w5zn.org
Sent: Saturday, November 17, 2018 8:12 AM
To: topband <topband@contesting.com>
Subject: Re: Topband: ARRL DXCC - 160 Meters

Folks - I'm not exactly understanding the LoTW comments on this thread. 
If it is referring to the LoTW screen shot totals listed by OK1RD on his
website then that is the combined totals in his DXCC record, not the totals
confirmed solely via LoTW so a "hack" has not necessarily occurred.

Regardless, there is convincing evidence some bogus QSL cards were reviewed
and accepted by a DXCC card checker somewhere and then entered into his DXCC
record!

73 Joel W5ZN

On 2018-11-17 05:29, Bill Tippett wrote:
>>> Doesn't say much for the DXCC checking process either.  73 Clive 
>>> GM3POI
> 
> 
> Guys this was probably done by OK1RD to embarrass ARRL/DXCC, in 
> retaliation
> 
> for ARRL (correctly) removing his bogus listing over 10 years ago.  He
> 
> probably found a way to hack LOTW and no human monitored the result.  
> I'm
> 
> sure they will correct the listing but it does raise some serious 
> issues
> 
> about the security of their system.
> 
> 
> 73,  Bill  W4ZV
> _________________
> Searchable Archives: http://www.contesting.com/_topband - Topband 
> Reflector
_________________
Searchable Archives: http://www.contesting.com/_topband - Topband Reflector

_________________
Searchable Archives: http://www.contesting.com/_topband - Topband Reflector

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