|Joined:||Sat, May 14th 2011, 20:53||Roles:||N/A||Moderates:||N/A|
|W1AW/1-CT Logs Incomplete||Sep 25th, 16:33||1||203||on 25/9/14|
|QRZ.com can now sign LoTW logs||May 20th, 18:56||2||383||on 23/5/14|
|ASSP version inconsistency at edgeni.net||Jun 21st 2013, 18:12||1||733||on 21/6/13|
|RTTY Procedure Guide||Dec 11th 2012, 23:26||4||2,056||on 16/1/13|
|Looking for an old QSL Card - K4IBJ||Oct 31st 2012, 17:50||2||1,074||on 10/2/14|
|Electronic QST problems on Linux||May 23rd 2012, 18:29||10||1,891||on 17/11/12|
|WAS Forum||Mar 30th 2012, 01:35||4||1,338||on 19/6/12|
|W1AW/1-CT Logs Incomplete||K0STK||on 25/9/14|
|The leaderboard shows that W1AW/1-CT has uploaded their logs. But there are only 2 QSOs ...
As of Fri Sep 26 14:09:32 UTC 2014 the leaderboard now shows 25,529 QSOs. But 2 of my QSOs are missing.
|5B DXCC plaque with LOTW||F8CRS||on 23/9/14|
Have you looked at http://www.arrl.org/dxcc-and-lotw-faq and https://lotw.arrl.org/lotw-help/dxcc-award-credit/ ?
|QRZ.com can now sign LoTW logs||K0STK||on 20/5/14|
"Our next big announcement concerns our online logbook. Many, many folks have asked us for LoTW integration and we're pleased to announce that this is now available to all Logbook subscribers. This means that if you're an LoTW user, you can push your QRZ logs directly to LoTW with just a couple of clicks of the mouse. The logbook offers options to send individual QSO's, lists of QSO's, or even your entire logbook directly to LoTW. We have created a configuration page which allows you to import your LoTW certificate into QRZ so that we can sign and send the logs on your behalf."
According to page 4 at http://files.qrz.com/static/qrz/lotw_cert_guide.pdf they have you export a certificate which is not protected by a password. Then you upload that unlocked certificate to their server,
This seems to me to be a dilution of the identity assurance provided by LoTW.
edit: a word
|FLdigi to N1MM logger||kb1yvr||on 27/4/14|
| According to https://groups.yahoo.com/neo/groups/paNBEMS/conversations/topics/4533:
'use [the] Fldigi "engine" within N1MM as opposed to plain Fldigi. Just use N1MM, set-up Fldigi as your preferred digital engine, and then select Field Day in N1MM Logger and off you go. Setting up of N1MM will involve telling it the path to Fldigi.'
Also see http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+Fldigi+for+Sound+Card+Modes
|Vanity Call - When to apply vs expiration date||WV0L||on 6/4/14|
Vanity call sign applications submitted less than 2 years and one day after a call sign expiration date will be denied.
It is also my understanding that applications are processed in a random order rather than in the order received.
Here some facts about the timeline for application processing retrieved from an archive.org copy of vanityhq.com:
1. Vanity applications are usually processed on Tuesdays, Fridays, and Saturdays
2. Applications received on Monday are processed on Friday, 18 days later
3. Applications received on Tuesday are processed on Saturday, 18 days later
4. Applications received on Wednesday, Thursday, or Friday are processed on Tuesday, 18 days after the Friday date
5. Holidays occuring between the received date and the processed date don't seem to change the schedule. However, Monday holidays cause the Tuesday processing to be a day late
6. Applications filed on Saturday, Sunday, or a holiday are marked "received" and date stamped the next business day
7. Applications are processed as a batch job in the early morning hours while the ULS system is off-line. If the batch job fails it may cause grants to be delayed