There are awards not just for activating and hunting unique parks, but they have their own WAS, there are awards for activating/hunting parks and operators multiple times, park-to-park awards, "late shift" awards for 0000Z to 1200Z contacts (good for the after-work crowd), and more. Activators help the hunters, and hunters help the activators.
KF8KI QRZ Staff EngineerQRZ HQ Staff QRZ Page Since you didn't provide the other callsign, I can't help beyond telling you that this is a problem that occurs when the user does not properly have their DX entity set in their operating location, found under settings > logbook properties. It's relatively common for things like DXpeditions and secondary callsigns where the logbook wasn't set up ...
Even though the performance difference is negligible, and optimized out in many cases - please take note that it's still good practice to use ++i instead of i++. There's absolutely no reason not to, and if your software ever passes through a toolchain that doesn't optimize it out your software will be more efficient. Considering it is just as easy to type ++i as it is to type i++, there is ...
One note: as I recall, /i/ and /iː/ are pronounced identically in most AmE and BrE dialects; dictionaries consider them separate phonemes because some dialects, like those that lack the usual "happy"-tensing, do have a difference in pronunciation there.
Do not put baluns in single element dipoles that would be used for anything other than the frequency they're cut for or the appropriate odd harmonic. Multiple-element "fan" dipoles are great with a good balun. Always use current baluns. The ONLY exception to this are the Radio Works "Remote Balun" and another 4:1 balun called the "Centaur".