I've worked a dx station multiple times but he refuses to confirm our QSO. When I email him he say's I'm ok in his log, I noticed he doesn't seem to have the gold star next to any of the callsigns that are displayed. Is there a way to search his log for our QSO's? Tnx Dan WG5G
I can answer that for you Dan. No there is no way you can do that. Only the last 15 contacts are visible in the user's log on their Bio page. If you want to know something about a QSO you had, you can email or PM the person. But there's no way to search someone else's log Dave W7UUU
why is that? what is the threat? we wondered about exactly this yesterday. recently we ran an event under a shared call. the participants wanted to look through the shared call log. only the call's log manager could see the full log. what is being saved here?
It's the way QRZ set it up from day one - just like LoTW, ClubLog, HRDlog, etc. It's called "double blind" - I can't see your info, you can't see mine. Nothing remotely new in the idea of "my log is private". If you want totally open logging, where you can just make up confirmations all day long, try eQSL. It's not a double-blind system - and that's why neither LoTW nor QRZ will accept "confirmations" from eQSL. Either your data matches mine or it doesn't and there's no confirmation. You can't cheat by searching my log for "when we worked, on which band, and which mode" just to get a confirmation because you either didn't log it, or you logged it wrong. That's why Dave W7UUU
Huh? Why are you sharing your passwords? I have never done that - I'm not sure even what you're suggesting. Dave W7UUU
Logs are private Most people will put comments in those logs. Those don't need to be shared with everyone, sometimes/particularly, the person that's wanting to look it up.... .. HI Confirmation is automatic on QRZ. If they log you and you log them, why do you need to look them up anyway? If you logged them also, it'll show an automatic confirmation on QRZ, that's the great thing about using the QRZ logger. 73 from, The K0UO " Rhombic Antenna Farm" miles of wire in the Air & On the AIR daily
It's V85T QSL direct only no clublog or LOTW, but he does use the QRZ.COM log, I think what he does is confirm you on QRZ.COM log after you send him a card, I've seen other user's doing this. Tnx Dan WG5G
Actually, the way it works on ClubLog is this: you can look up the call sign you know you worked, and sure enough it will show that you did - but it won't provide the details! It's still "double blind" but at least says you're barking up the right tree... See below - I have that exact situation right now: ClubLog says I worked 7Q7EMH on four bands, but somehow I messed something up for the 20m contact and I do not have the details so I can't create the confirmation! It even tells me it was in 2023 and was on FT8 ... but for whatever reason my system glitched and didn't record the details properly. I'm going to email them and plead my case - and see if they can help me out.... It's a clever system ClubLog uses - but frustrating in cases like mine, where you can see there is the contact, but you cannot confirm it LOL! Dave W7UUU
Is it not possible for the call's log manager to save a copy of the log and email it to the participants or post it on the event or club website?
Yeah, that would work, too, sort of. I would have just emailed the adif but that's not very readable for the OMs. Now I understand the issue of faking QSOs so I see why the no poking around rule. I just don't think about cheats. Not clever that way.
That's the approach I'm taking. Alas, I always forget about renaming old "ALL.txt" and starting new ones - and the ALL.txt file that contains the QSO is 1.6 GIGAbytes of text data!! It's too much even on a very high power machine. It chokes Word, Excel, Google Docs and Sheets as well as Open Office. So I broke it down into 14 files each 100mb long using a freeware program. But even at 100mb file size, it's still slow as molasses to search. So I'm going break it down into 25mb files and try searching those. It's AMAZING how much data WSJT-X produces and stores in that file!! Moral of the story folks: if you run FT8 very often at all, think about renaming the ALL.txt file every few months. You don't ever have to worry about creating a new one - WSJT-X will just generate a new ALL.txt the first time it tries to write to the file and finds it missing. That way, should you ever need to do as I need, and find a QSO you worked but it failed to log, you can search the file much more easily. Dave W7UUU
