25-04-2024, 09:56 PM
I am sure every digital user has hit this wall.
After a successful session, there is always the "paper work" and it is getting ridiculous. All of the "QSL" services that folks seem to expect are a right royal PITA to keep up to date, such as; LOTW, eQSL, QRZ.com.
I use WSJT-X and that is run in conjunction with JT-Alert that generally upload to eQSL on the fly.
This leaves QRZ.com and LOTW which both require mucking around editing the adi file (to simplfy the date filtering) then uploading to each site.
I used to upload directly to QRZ.com in the same manner as eQSL but that is now a subscription feature.
It looks like all of the local logging software that JT-Alert works with are also subscription.
In all this I still end up with no local log.
Maybe just use a paper log and send out QSL cards? That seemed to work for 100 years or more
So how do folks do it?
After a successful session, there is always the "paper work" and it is getting ridiculous. All of the "QSL" services that folks seem to expect are a right royal PITA to keep up to date, such as; LOTW, eQSL, QRZ.com.
I use WSJT-X and that is run in conjunction with JT-Alert that generally upload to eQSL on the fly.
This leaves QRZ.com and LOTW which both require mucking around editing the adi file (to simplfy the date filtering) then uploading to each site.
I used to upload directly to QRZ.com in the same manner as eQSL but that is now a subscription feature.
It looks like all of the local logging software that JT-Alert works with are also subscription.
In all this I still end up with no local log.
Maybe just use a paper log and send out QSL cards? That seemed to work for 100 years or more
So how do folks do it?
Colin
Barossa Valley, SAP. PF95ln
(aka VK5CSW)
Barossa Valley, SAP. PF95ln
(aka VK5CSW)