[Dx4win] New TQSL not ready for prime time

[Rick Murphy]

Joseph,
You're entitled to your opinion. However, to say it's "Not ready for prime
time" is incorrect, particularly for DX4WIN users.

The only serious problem found in 1.14 was for Mac users that are trying to
upload duplicate QSOs to LoTW. None of the testers reported this problem
prior to the final release.

Please note that the major performance problems with LoTW several months
ago were caused almost entirely by people uploading massive logs
repeatedly, so this defect really shouldn't matter unless someone is
deliberately trying to deny service to other users. There's an easy
workaround for people running in to this problem on MacOS.

Of the other problems you mention, the invalid zone problem is already
fixed with no TQSL update needed. The command line problem isn't anything
normal users would run in to, and has no impact whatsoever on DX4WIN users.
Actually, the Mac problem also has no impact for DX4WIN users, either.

So, sure, stay with what you have - you get no usable error messages when
certificate imports fail, you're allowed to upload QSOs with incorrect
zones without being warned, you can upload QSOs to Logbook as often as you
like, you can upload logs that'll get rejected by Logbook because your
certificate has expired, you can't upload directly to Logbook, and you'll
be allowed to upload using locations where there's no valid certificate
(which Logbook will reject). You won't be notified when the fixes for the
minor problems are available, and can't automatically update to fix any
defects.

If any of those problems are issues for you, there's an updated version of
TQSL available on the sourceforge site -
http://sourceforge.net/projects/trustedqsl/files/TrustedQSL/ - so please
give the update a try. We're doing what we can to improve the user
experience and appreciate constructive comments.

I'm having a hard time undestanding the point of your message. Please
explain.

(Apologies, but the team has spent a lot of personal time trying to make
TrustedQSL better. Taking cheap shots ticks me off, and this is a cheap
shot.)
     -Rick



On Wed, May 22, 2013 at 8:33 PM, Joseph Orsak <jorsak at nc.rr.com> wrote:

> I think I'll be waiting a good long while before trying the new Trusted
> QSL:
>
> "May 21, 2013: From the Trusted QSL software development team - We
> announced last week that TQSL 1.14 would be available today (20 May 2013).
> However, three defects were reported last week:
>
>   a.. Incorrect behavior when the user specifies the wrong ITU zone
>   b.. Incorrect behavior when TQSL is invoked via command line without the
> -l switch present
>   c.. Incorrect behavior when processing an ADIF file containing duplicate
> QSOs when TQSL is running on MacOS
> These defects have been corrected, but we must test the corrected version
> before publicly releasing it. Expect the public release within the next  10
> days."
>
> http://www.arrl.org/logbook-of-the-world
>
> 73,
>
> Joe W4WN
> ______________________________________________________________
> DX4WIN mailing list
> Home: http://mailman.qth.net/mailman/listinfo/dx4win
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:DX4WIN at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
> --
> Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA
>