Re: Suggested rules of conduct
Decisive Comment wrote:
Ultimately this is something DPR ought to remedy with some (probably) simple updates to the challenges platform -- not a time consuming overhaul, just little things to aid hosts. In a thread that I think was deleted, tasad wrote something critical of hosts, to the effect that "If a host isn't weeding out the cheaters, s/he isn't doing their job" (meaning, amusingly, that he criticized hosts who post here and thank him for doing their job).
DPR make it very clear that weeding out cheaters is not a role of challenge hosts, so tasad would be posting his opinion at best of what he believes a host's role should be.
At https://www.dpreview.com/challenges/BecomeHost.aspx#what_does_a_challenge_host_do
DPR list the roles for hosts:
"The contents of a challenge host's to-do list varies throughout their challenge's life-cycle. During the preperation phase the host will:
1. Decide title & theme
2. Write the challenge rules.
3. Pick the start date.
4. Specifiy entry limits (overall and per-entrant).
The challenge is then announced and the challenge host can take it easy in the days before submissions open. However, once entries start flooding in (and until the end of the voting phase) the host needs to review any complaints made against submitted images.
1. Review complaints
2. Disqualify entries (pro-actively and/or in response to complaints)"
Challenge hosts are volunteers and so forcing them to spend time and resources weeding out cheats is not appropriate. If hosts were paid for their time then maybe then adding weeding out cheats could be added to their role.
I just uploaded a test photo to a challenge and changed the capture date manually. Why this is an always-editable field I don't know. Why keep it editable if the capture date is already extracted from the entry's exif?
If for whatever reason the image has no exif data, then sure, allow the entrant to enter a date... in this case, flag the image with some kind of 'alert' icon or note so that the host can immediately see that the image had a manually entered capture date (unless the challenge has no date restrictions in which case who cares). The host can then proceed to handle things however they wish.
Not allowing manual dates screws only the dumb cheaters obviously but it's at least something.
Exif data on its own is useless for verifying when a photo was taken because it can very easily be replaced deliberately or even inadvertently.
One quick and simple example, when replacing a sky in an image using Photoshop Elements, depending on how you do it, the final edited image could very easily end up with exif data from the image containing the sky.
Another thing could be to let hosts see partial IP addresses of entrants and voters. Did Joey Clicker and Jimmy Snapper enter images from the same IP?
IP addresses don't really prove anything if a member uses a VPN because they can hide behind an IP address from just about anywhere on the planet and change their IP address every time they log on if they like.
Did Joey and Jimmy give 5 stars to each other's entries? For extra benefit, something like a "possible duplicate accounts" button could be displayed for hosts to alert DPR admins.
Little things to alleviate unnecessary big things.
Maybe, maybe not.