Forum Replies Created
-
Posts
-
This is by design.
It is to comply with requests from major Dxpeditions and to prevent the logs being used to scrape QSOs (for SWL purposes and/or fake QSLs)
A P2P will confirm if the QSO is +/- 5 minutes…
There is a problem where the two times are either side of midnight UTC… as the date then doesn’t match. I’ll try and fix that…
Adrian: the file you sent me had 148 entries with a claimed P2P, of which 12 were not confirmed. A quick scan shows garbage-in/garbage-out to be the cause.
Logsearch makes an educated guess if one log specifies HH::MM:SS and the other 00:HH:MM (or even 00:00:00) but logs with 00:00:HH take a bit of guessing… as an observation EVERY ONE of your logs has incorrect time information.
But of course, this is still MY FAULT that your P2Ps are not confirming?!
As an occasional (solo) operator of club-call MX0WFF I have mixed views… many of my ‘club’ activations are valid for me as the op, but not the club.
I guess it boils down to what we consider ‘club’ activations to be… is just using a club callsign a club activation?
This question has been asked a number of times…
Logsearch (currently) only supports English (sorry) so if you have the page translated, then some of the buttons (eg Search, Apply) do not work 🙁
On the ToDo list is to add support for other languages…
Ummm… DL/F5HTR/P/P is an invalid callsign
When you say “is not accepted” is this in a log, or as a username?
With apologies – my work and family matters have been getting in the way of my hobby.
Could you give me some examples that have not confirmed, where both parties logs are uploaded?
With close to nine million QSOs in the database, I need a clue 😉
