CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] QSY

To: W0MU Mike Fatchett <w0mu@w0mu.com>
Subject: Re: [CQ-Contest] QSY
From: Jorge Diez - CX6VM <cx6vm.jorge@gmail.com>
Date: Mon, 20 Mar 2017 09:09:38 -0300
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
Mike

I think the practice is good for contesting because they are doing
contesting. If we want to think about other things, are many, contesting
isvery bad for the planet because of the energy consumption?  Or they are
the worst for the families because of us that set aside the family for
several days?

I think PJ4G team and other top Teams are doing the best to win the contest
within the rules.  There are smart and innovative people who make it
possible and others who do not realize it and when someone bring it to
light they grab the head, but everything is within the rules from what I
have seen.

Many years before, the Multi Single category made a big leap with the
intelligence of the P33W Team which was then followed by others Teams like
CN2AA

73,
Jorge
CX6VM/CW5W



<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2017-03-19 18:24 GMT-03:00 W0MU Mike Fatchett <w0mu@w0mu.com>:

> When will we see a written statement from the PJ4G guys about how this
> practice is great for contesting for X reasons and that all contests might
> want to consider it because of X.
>
> There is no statement because they are upset that their little "exploit"
> "loophole" etc was exposed for all to see and they are upset.  Maybe they
> are embarrassed as the vocal majority seems to feel this was done against
> the spirit of the rules and hobby?
>
> We have had many arguments for disallowing the practice.  The only pro I
> saw was one of the technical merits of doing such and we should not thwart
> advances in technology, which I agree but not at the expense of our already
> limited bands.
>
> I read with interest that NA2AA had created special software share just
> among friends.......It sure makes me wonder what that software is doing.
> This information was obtained from whoever wrote he QRZ bio, as it was done
> in 3rd person so I have to guess that it was written by another?
>
> W0MU
>
>
>
> On 3/19/2017 1:34 PM, Ron Notarius W3WN wrote:
>
>> Yes, it does.
>>
>> I guess flouting the spirit of the rules, while rubbing our noses in it,
>> is
>> meant to be inspiration?  If that was his intent, didn't work.  Instead,
>> it
>> reminds of me Scut Farkus and Grover Dill.
>>
>> 73
>>
>> -----Original Message-----
>> From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf Of
>> W0MU Mike Fatchett
>> Sent: Friday, March 17, 2017 10:24 PM
>> To: cq-contest@contesting.com
>> Subject: Re: [CQ-Contest] QSY
>>
>> This speaks volumes........Loud and clear.
>>
>> 73
>>
>> W0MU
>>
>>
>> On 3/17/2017 1:45 PM, David Minster wrote:
>>
>>> Yep.  I'm out.  We'll go on winning contests while you figure out ways to
>>>
>> stop us, or lick your wounds when you lose.  Or blame propagation.  Or...
>>
>>> David, NA2AA (PJ4G team)
>>> _______________________________________________
>>> 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
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>



-- 
73,
Jorge
CX6VM/CW5W
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

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