 |
|
eQSL.cc Home
Search
Login
Authors
Recent Posts| Viewing User Profile for: K1OKS Orval K Swaney, Jr | |||||||||||||||||
| About | Contact | ||||||||||||||||
|
Send Private Message |
||||||||||||||||
| Post Statistics | |||||||||||||||||
|
K1OKS Orval K Swaney, Jr has contributed to 2 posts out of 11650 total posts
(0.02%) in 639 days (0.00 posts per day).
20 Most recent posts:
General web site suggestions »
Bureau (aka buro) card sending for other sites Apr 4, 2023 04:50 PM
(Total replies: 0)
I upload logbooks to multiple sites, in part to help others who are trying to achieve QSL awards, and need others' QSL confirmations. While it may seem these sites are competition to eQSL, I see eQSL as an improved QSL card solution, saving both on postage/purchase, and reducing pollution caused by postal delivery. One site, ClubLog, has a link (for most QSO's) to verify one's listing in another logbook without logging in. On the surface that sounds ... concerning, but it's not an open book, only showing contact time, band, etc. with callsign. Another thing they offer is a choice of how members offer to send QSL cards, Direct, or Bureau (BURO). This is where I'd like to see eQSL added. It would require some form of link / coding, but in principle, if a contact were to request a QSL card (or in this case, eQSL card), he would select eQSL as the method, and ClubLog would send the requester's call (other needed info from their logbook?) to eQSL, and eQSL would confirm/deny the QSO. eQSL could send the eQSL card, and dynamically, if the receiver isn't a member, eQSL could include a short "join us" message in the "here's the eQSL sent by ABC12DEF ham callsign". Including the contact's callsign in details would make it more likely the receiver would open it (again, they're possibly not a member, and they might think it's spam otherwise). How to get started? Identify if there is already an API/PHP in the eQSL website to support such an incoming request for eQSL card. Setup a dialog with ClubLog to iron out what info might be needed to make the transaction happen. Again, remind them (and potentially other websites) that eQSL offers a way to send QSL's with less environmental impact, less carbon footprint. Mention that the receiver can print the eQSL locally if they choose to, for adding to their collection (similar results to shipping a printed card in an envelope, but without the mailman). How does this benefit eQSL? directed email (promise NOT to spam!!) providing wanted eQSL cards, going to prospective DX ham operators, with an (pre-negotiated!!) authorized paragraph/message to any non-eQSL members (sort by call sign) welcoming them to also join eQSL. K1OKS Orval K Swaney, Jr
General web site suggestions »
ADIF QSO entry issues Dec 12, 2022 10:37 PM
(Total replies: 0)
I appreciate the ffort made to improve the website, and I was able to download a copy of my entries to ADIF or TXT file for local viewing. What I discovered was bothersome, though. In ALL cases, the "RST_RCVD" field has an entry of "0". For example: <RST_SENT:3>+03<RST_RCVD:0> <RST_SENT:3>-02<RST_RCVD:0> <RST_SENT:3>-11<RST_RCVD:0> So basically, regardless of WSJT-X's entry including both fields, when sent to/received by eQSL, the second field data is being stripped off, and being replaced by "0". And secondly, as my log entries are sent in parallel to eQSL, as well as QRZ and LotW, I find a surprising number of confirmed (received 73) entries in a row are listed under QRZ, but not included in eQSL. This is NOT a complaint, and may just be my own mis-understanding(?). Perhaps to receive contacts' credit on eQSL, the QSO must have an account on eQSL, so they can confirm/reject the QSO, so naturally the entry is null, prior to them signing up? I find a very high percentage of completed entries in LotW and QRZ are missing in eQSL. Hopefully this is the reason? K1OKS Orval K Swaney, Jr |
|||||||||||||||||