[Moon] call3.txt why?

[Mark (G4PCS)]

Hi Lars,
 
that seems to me like a very reasonable suggestion. Of course it's possible to do it (manually) already, but I would vote for it being implemented like that within the software, if ever such a vote was conducted...
 
Every JT65 contact I've had has been done this way - I have no call3.txt file on my PC. Every JT65 contact I've had has been random, and I've never put a callsign in the "call field" until after it's been decoded - even then only for convenience, to generate the messages easily.
 
It used to be that "integrity" was an assumed given, and 99.9% of the time rightly so. I, probably like many others (the "silent majority"?), am sick and tired of the loose cannons accusing all and sundry of "cheating". To have our efforts (considerable in many cases) belittled by people who know sod all about what we're doing is annoying in the first instance, and after a while becomes downright insulting.
 
During a qso we never know for sure what our qso partner is doing, whatever mode we're using - we can only look after our own integrity and take pride in what we do. Do we spend our time constantly questioning whether people *really* heard every single character of both callsigns during a qso, whether every single person is running power that's *within* their licence limits, etc, etc? The principles are the same, but of course we very rightly assume that most operators are honest, just like us.
 
I've been active on EME, on and off, for more than 20 years. I've operated everything from single yagis up to a 224 colinear array on 2m. I reached a stage where I felt I'd "been there and done that". For me, JT65 was a breath of fresh air that inspired me to build a new, portable, EME system for 2M and get qrv again - as has been the case for many people. Of course, I knew from prior experience that I'd be also be able to work many people on CW with the system I built, and I have. My genuine hope is that a lot of newcomers, drawn to EME by WSJT, will realise that they're actually hearing, with their own ears, most of the JT65 signals they're working - and that there's no reason they can't work those same stations on CW!
 
I just hope that the very small number of people who constantly inject huge amounts of negativity into the EME community will realise how much damage they're doing...
 
Regards, Mark G4PCS



----- Original Message ----
From: Lars Pettersson <sm4ive at telia.com>
To: Joe Taylor <joe at Princeton.EDU>; moon at moonbounce.info
Sent: Tuesday, 22 April, 2008 5:10:32 AM
Subject: Re: [Moon] call3.txt why?

Hi all
A suggestion.
Remove the CAll3.txt, remove the DS function
and let the software use the RF path only.

Would that not solve a lot of all this on going, never ending story.

Lars SM4IVE




----- Original Message ----- 
From: "Joe Taylor" <joe at Princeton.EDU>
To: <moon at moonbounce.info>
Sent: Tuesday, April 22, 2008 2:10 AM
Subject: Re: [Moon] call3.txt why?


> Hi Wolfgang and all,
>
> DL5MAE wrote:
>> Excuse me, but I really dont understand why we must enter a "new 
>> callsign"
>> in a data-base to work them? Whats the reason?
>
> 1. There is no need to do so, and for 95% of the stations who work JW5E
> using JT65 it will make absolutely no difference whether you do, or do 
> not.
>
> 2. If you will be aiming to work JW5E with an ear-and-brain mode, you
> have already made the equivalent "entry" in your database.  (Of course,
> I know that you would never, ever, make any use of that information
> during your QSO attempt.)
>
> -- 73, Joe, K1JT
>
> _______________________________________________
> Moon mailing list
> Moon at moonbounce.info
> http://www.moonbounce.info/mailman/listinfo/moon
>
> Please enter/update your standings:
> http://www.vhf-dx.net/top.html
>
> When you decide to remain anonymous I may consider this unpolite and 
> remove you from the list
> 



_______________________________________________
Moon mailing list
Moon at moonbounce.info
http://www.moonbounce.info/mailman/listinfo/moon

Please enter/update your standings: 
http://www.vhf-dx.net/top.html

When you decide to remain anonymous I may consider this unpolite and remove you from the list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.moonbounce.info/pipermail/moon/attachments/20080422/4ead563b/attachment.htm