I am seeing an alarming rise in the number of duplicate nominations I am seeing using the same photo as the existing Wayspot. Can we get clarification of what Niantic would like us to do here? I just rejected this latest example under 3rd party photo since it is the same photo as on the existing Wayspot.
I don’t know if this is being done to add more photos to the Wayspot, or in an effort to get the ML model to pick up and accept this. Per dynamic link, it only currently has one photo, but has exactly the same description. So this is a spammed nomination, whatever the reason.
I also got this to review, and it seemed odd having the same photo as the existing Wayspot on the map, but a completely different name and a slightly tweaked description. The location pin was pretty much in the exact same spot as the existing Wayspot, too.
However, this community runs north along Gladys Ave and south along Cassandra Way.
It could be the submitter is not as experienced, and make lack some patience, and couldn’t wait for their first nomination to be decided upon, so they thought they had to submit again, but with some tweaks to the title/description. Or, they may have thought they had better chances of getting the pool approved if they submitted 2 nominations instead of 1. They also just copy/pasted the link to the criteria clarification page in the help pages, not the forums, which could be another indication of a less experienced submitter, again could.
Also, this was for sure an upgraded nomination, and they could have auto-upgrade on, and may not even know much about it or Contribution Management.
Being the main photos were the exact same and I couldn’t fully tell if this was abuse or inexperience, I marked as a duplicate.
But this is hard to tell if it’s a dupe, by mistake or inexperience, or 3rd party. We really don’t know what the submitter was thinking. They could have submitted both of these.
I am not getting the point you are trying to make. Why would the submitter’s intent matter for how we mark this? I am not suggesting we mark it as abuse (unless Niantic staff chime in and say that we should) if we see the same photo submitted as a new nomination for a live Wayspot. “Third party photo” is as close as I can come to “duplicate photo” and that is not in the Abuse section.
I’m not saying there is or isn’t abuse here. My judgment was to mark as a duplicate, and that’s my choice after reviewing it. You do sometimes have to consider what may have been the intent of the submitter, as there are abusers out there, I felt it might not be an accuracy issue.
I think we should mark it duplicate AND Niantic should not add the exact same photo to the Wayspot.
Everything else is just costing us time to do something Niantic could and should do systematically. I choose to use my volunteer hours for nominating and reviewing - not for doing manual onesies where they should do automatic thousands-ies.
Also I think that for each nomination, Niantic should make sure that Explorers don’t reuse a photo from their own prior request that is pending or approved. (IOW if the prior use of that photo was declined, carry on with this one.) This photo comparison could be part of the process when the Explorer hits Submit or (if saved for later) Upload.
I think that ML didn’t reject this nomination, and since it hasn’t been accepting since the end of November (which the submitter may/may not be aware of), it went into community voting. Maybe this submitter is used to their nominations being accepted by ML, but after 24-48 hours when it wasn’t accepted, they may have thought they didn’t fully submit, so they resubmitted, just using a different title and tweaked descriptions.
They may not check their emails on a regular basis (I know people that do not so I never contact them via email), they may not check Contribution Management on a regular basis, and/or they may be used to ML accepting their nominations quite regularly.
There are so many different ways to look at this nomination, to consider as to why it was submitted again with the same main photo, but different title and tweaked description. And we are all going to judge a nomination like this differently, and this shows how some can reject for different reasons (such as a memorial bench being rejected as indistinct and a generic business).
We know staff keep their eyes on the forums, so if they do look further into this, they can and most likely will let us know. Right now, it’s just up to us as reviewers to make sure this doesn’t get accepted.
I apologize if I missed something - there was a lot of incorrect information going around so I didn’t read everything.
Is this not answered? It is a little buried but it’s always been clear to me that we reject outright (not duplicate) a nomination using the exact same photo.
The following should not be submitted and, when reviewing, should be considered as rejection criteria:
[…]
Exact duplicates of existing photos
Selecting the photo as a duplicate would add the photo. I wish Niantic used more algorithms to handle exact duplicates (and watermarks, 3rd party, etc) but that’s not how they currently handle things. It’s easier to reject than duplicate and expect somebody to clean it up, later.
So, no, not really solved, as it could have been the same submitter for both nominations, and they took the photos, so it may not be a 3rd party photo issue.
This! but what reason should I use? I don’t want to get another “reviewing incorrectly email” - and since it seems many people are unaware that we are supposed to reject, I am super glad I asked this question.
