Fast Reviews of URL/Link/HTML Violations in Titles and Descriptions Triggering 4-Hour Restrictions

Review Support
1

Dear Niantic Wayfarer Team,

I would like to bring a potential contradiction in the design of the Wayfarer reviewing system to the attention of the technical/product team.

I have now received a four-hour reviewing restriction twice after reviewing nominations very quickly.

In both cases, I was reviewing nominations where the title or description contained a URL, a link, or HTML.

These issues can often be identified immediately simply by looking at the title or description. The Wayfarer reviewing interface provides the corresponding checkbox for precisely this type of violation, allowing the reviewer to identify and process it very quickly.

As a result, I can legitimately select the appropriate checkbox and complete the review within a very short period of time.

This creates a contradiction in the current system:

Wayfarer provides specific review options that allow URLs, links, or HTML in titles and descriptions to be identified and processed quickly, while the automated system can apparently interpret the resulting fast review as suspicious behavior and impose a four-hour restriction.

I understand why Niantic monitors unusually fast reviewing activity. I also understand that such monitoring is necessary to detect reviewers who simply click through nominations without properly reviewing them.

However, a nomination containing a URL, link, or HTML in its title or description is a special case. The relevant issue can be visible immediately, and there is no legitimate reason why a reviewer should have to spend a long time examining the nomination when the applicable rejection criterion is already clearly established.

I therefore believe that review speed should not be evaluated independently of the specific rejection criterion selected.

For example, the system could recognize that a very fast review involving the relevant URL/link/HTML-in-title-or-description rejection criterion may be entirely legitimate, particularly when the violation is objectively visible in the nomination.

My concern is not simply about my individual four-hour restrictions. It is about a potential system-design problem that could affect other legitimate reviewers as well.

If Niantic provides specific checkboxes that allow URLs, links, or HTML in titles and descriptions to be identified quickly, reviewers should not be penalized merely because they use those tools efficiently.

I respectfully ask the technical/product team to investigate this interaction between the review interface and the automated review-speed detection system and consider whether the algorithm should be adjusted accordingly.

I fully support measures against fraudulent or abusive reviewing. My intention is simply to review correctly and efficiently using the tools provided by Wayfarer.

Wayfarer username: Prinz242

Kind regards,

Roland Berg

2

Hey @rbah345899ge ,

Welcome to the Wayfarer Community Forum.

The system enforces a cooldown when it detects anomalies in your review pattern. One or two reviews do not lead to a cooldown.

I have looked into your reviews and can confirm that the system is working as designed and there is no issue with it.

Thanks,

3

Thank you for the clarification.

I understand that the current behavior is working as intended.

However, I would like to point out a possible problem with this design.

The review interface provides checkboxes for quickly identifying URLs, links, or HTML in titles and descriptions.

Using these checkboxes can make a review very quick when the violation is immediately obvious.

At the same time, very fast reviews can result in a four-hour restriction.

This creates a contradiction: the interface allows and encourages quick identification of these violations, while the system can penalize the reviewer for doing so quickly.

I therefore ask Niantic to consider whether this aspect of the system could be improved.

For example, the selected rejection reason could be taken into account when the system evaluates review speed.

This could help prevent legitimate reviewers from being restricted simply because they efficiently used the review tools provided by Wayfarer.

Thank you for considering this feedback.

4

In my experience, at least 90% of the nominations I review contain these issues in the title or description. This naturally leads to a high reviewing speed. These issues are often immediately visible and can be reported using the corresponding checkboxes.

5

Whoa! I almost never see url’s in the title or description. They are allowed and encouraged in the supporting section. Could you please post a screenshot the next time you get one of these to review?

6

As mentioned earlier, I reviewed your reviews, and this number is incorrect. The system is designed to detect anomalies in the review pattern, and it did so as planned.

I recommend that you re-review the Wayspot guidelines to avoid this in future.

7

An example

(attachments)

Screenshot_20260821-131229.jpg
Screenshot_20260821-131229.jpg1080Ă—2424 303 KB

8

https://wayfarer.nianticlabs.com/new/review

9

You can not link to the instances of your reviews or contributions

10

Hier ist keine URL oder sonst was drin?

11

I don’t see any url.

If you are talking about the Title being linked to a google search this is standard to help with identifying what it is.

This is part of the system not a link added by the submitter.

12

There is no link in this image… I do not understand what you are doing…

This appears to be a nomination for a pool, which sounds to me to be a good place to exercise and socialise. I’d be checking it was not at a single family home or a school, and otherwise looking to accept assuming the rest of the review is good.

13

If this is what you have been rejecting for url, you are rejecting incorrectly. I am glad you asked about this.

14

I think that @SlimboyFat71 has the answer.

When looking at this you can see why it would be an easy error to make. It looks like it would be part of the title as it is in that space.

I don’t think there is an explanation about that link?

Personally I just mentally blank it out as it was usually not helpful.

If this is the case I hope the team can take this feedback on board.

15

I would like to respectfully point out one important fact.

Niantic’s own Wayfarer guidelines explicitly state that titles and descriptions containing URLs or HTML should receive a negative rating.

This means that identifying such a violation can be an immediate and legitimate reason for a very fast review.

More importantly, Niantic has officially acknowledged that its Machine Learning system has made mistakes.

In the official “ML Auto-Decision Issue” post, Niantic stated that eMiLy was causing “some incorrect auto-accept and auto-reject decisions”.

Niantic therefore has officially confirmed that its automated technology can make incorrect decisions.

For this reason, I do not think it is reasonable to assume that an automated detection of review speed cannot produce false positives.

My point is not that the system should be disabled.

My point is that the system should consider the reason for a fast review.

If a reviewer quickly selects the specific rejection criterion for a URL or HTML violation in a title or description, this should be recognized as a potentially legitimate fast review.

I therefore ask Niantic to consider whether the current system can be improved to take the selected rejection criterion into account when evaluating review speed.

This would reduce the risk of legitimate reviewers being restricted simply because they efficiently used the review tools provided by Wayfarer.

Thank you for considering this.

16

I think you missed the point that you’re rejecting things for a link where there is no link present…

This is not an ML issue or a cooldown issue, it’s a bad reviewing issue, so the cooldown was entirely appropriate. You saying you’re rejecting 90% of the things you review for this!! That means you’ve likely incorrectly rejected a large number of people’s nominations, which is really sad.

Hopefully you learn from this and can review better when the cooldown expires. Please feel free to share reviews here if you’re unsure and ask for a 2nd opinion while you’re learning.

17

IMG_4919
IMG_4919444Ă—1000 102 KB

Trying to understand an issue.

Putting aside your other points can you confirm if you regard all inside the green box as being the title including the bit in the yellow circle please.

18

The title did not contain a URL in the example you gave.

You did not get the cooldown simply for going too fast. Aaron has explained that the system does not only look at the speed of your decision, it looks for “anomalies” in the review “pattern” in your history. Rejecting 90% of the reviews you do for URL in the title is definitely an anomaly.

What do you mean by review tools?

19

I would like to correct my previous statement and sincerely apologize for my mistake.

I had assumed that the blue, clickable links displayed in Wayspot titles had been added by the submitters themselves. I have now realized that Niantic Wayfarer apparently generates these links automatically from the title and simply opens a Google search for the title.

This was a general issue, not an isolated case: the automatically generated links led to Google searches for the respective titles. However, these searches did not contain any specific reference to the particular Wayspot nomination and therefore provided no evidence regarding the specific submission. This gave me the false impression that the submitters themselves had added links intended to serve as evidence for their nominations.

When such a link, automatically generated by Niantic, merely opens a general Google search and provides no evidence relating to the specific nomination, I believe it is understandable how this misunderstanding occurred. Nevertheless, my conclusion based on that assumption was incorrect, and I sincerely apologize for it.

I would like to apologize to the Wayfarer staff, to the submitters whose nominations may have been unfairly reported or incorrectly evaluated as a result, and to everyone who pointed out my mistake to me. I am very grateful for these comments and for helping me clarify the situation.

Please consider my previous reports or assessments based on this assumption to be unfounded. I sincerely regret the misunderstandings and thank you for your work and for the helpful feedback.

20

I am very happy that you came here and asked why you were getting cooldowns! I could see myself making a similar mistake if I did not have a community to ask :hugs: