Is it possible that when you are trying to submit and scroll down, you accidentally scrolled the location pin into incorrect position? I never heard such bug before. But this is the most logical explanation that i have
Whether the bug actually exists is impossible for me to verify.
That aside, I have never seen a stance of “I am right, and therefore anyone who disagrees is wrong” ever lead to a desired outcome.
I commented on that Reddit thread, and I don’t believe any consensus was reached as to what exactly happened with that submission. All we know is that the submission coordinates in the email (which are the exact coordinates of the location pin on the map) were 25 metres away from the object. 25 metres is still significant, but it’s a small enough discrepancy that it could easily have been caused by user error rather than a bug. So I don’t feel like that can be used as concrete evidence of a bug here. It is possible, of course, but the margins are small enough in that case that it cannot really be guaranteed to have been caused by a bug. There’s a pretty huge difference between their 25 metres and your 675 metres.
Additionally, let’s assume that you’re right and this is actually a bug with the submission process (and again, I’m going to say we can’t use the Reddit post as evidence, given the much smaller discrepancy). If that truly is the case, why are you the only one reporting it? There are many wayfarer users across the globe, and yet this seems to be the only report of something that would be a pretty major bug if it exists. It seems almost impossible that other users wouldn’t also be experiencing it and reporting it.
I want to be clear that I’m in no means insinuating that you did this to intentionally commit wayfarer abuse. I’m just pointing out that it seems very bizarre that you’d be the only one experiencing this when the system is seemingly working fine for everyone else.
I will also point out that when you submit a nomination, you usually have a 24 hour grace period where you can put your nomination on hold and double check that everything is how you want it to be before it enters voting. I nearly always make use of this to make sure my text, photos and location pin are all accurate, and it’s something that everyone should realistically be doing. Had you done this yourself, you would’ve realised the pin was in the wrong location, and you could’ve withdrawn and resubmitted the nomination with the correct placement. The onus is always on the submitter to make sure their nominations are accurate before they enter voting. And on the off chance something inaccurate does get through into voting, you can always message support to get them to manually reject it.
I want to emphasize that what @TjoeMi suggested is much more possible now with web submit. When we could only submit through Pokemon GO (or Ingress), we used buttons at the bottom of the screen to advance the process. But now we are using a long form that we must scroll down to see all the fields. I have noticed its very easy to accidentally scroll the map when im trying to scroll the whole form. You have to be very careful about where you touch the form to scroll past the map. Some days, i have no trouble. Other days, i have to reset the location several times. This is still user error and not a system error. The system is not arbitrarily jumping to a new location. It is changing based on the input we give it, whether we meant to or not.
Web申請における長いフォームのスクロール時に、意図せずマップエリアに指が触れてピンが滑ってしまう（誤操作を誘発する）という具体的なUIの挙動に関するご指摘、非常に説得力があり、深く納得いたしました。
確かに、これまでのアプリ内申請とは異なり、Webブラウザでの申請では画面スクロールの際に指の位置一つで意図しない「位置入力」がバックグラウンドで行われてしまう可能性は否定できません。もし私の「675mのジャンプ」が、そのようなWeb UIの構造的な罠による「意図しない誤操作（事故）」であったとするならば、それは1つの可能性として十分に受け入れることができます。非常に有意義なディスカッションをありがとうございます。
しかし、私が本当に失望し、このフォーラムのあり方として重大な問題であると感じているのは、**「この可能性や技術的な検証結果を、Niantic公式（Wayfarerチーム）が一切表明せず、一般のボランティアである皆様の推測に頼って物事を収めようとしている」**という点です。
もし多くのユーザーがWebのスクロール操作によって意図しない位置ズレ（事故）を起こし、結果として「位置偽装の不正者」としてBANされているのであれば、公式の技術チームがログを精査し、「UIの設計上、誤操作が起きやすい状態になっていた」とアナウンスし、誤操作を防ぐためのロック機能を実装するなどの改善を行うのが本来の筋です。
公式は何の技術的調査も表明もせず、裏で機械的にペナルティだけを科し、表のフォーラムでは一般ユーザーの皆様にデバッグ（原因究備）をさせて「ユーザーの過失である」という空気を作って幕引きを図ろうとしている。このプラットフォームの運営姿勢は、あまりにも不誠実です。
素晴らしいユーザーの皆様がこうして論理的で価値のある可能性を提示してくださっているからこそ、公式が一切の対話を拒否し、レンガの壁のように沈黙を貫いている現状が非常に残念でなりません。
このUIの挙動による事故の可能性を教えていただけたことで、私の中のモヤモヤは完全に解消されました。これまで真剣に考えてくださった皆様、本当にありがとうございました。
[English Summary]
Your point regarding the web-based submission UI—where scrolling down a long form can accidentally trigger map pin dragging if your finger touches the map area—is highly persuasive and logically sound.
If my 675m warp was indeed an involuntary “accident” caused by the clumsy structural layout of the web interface registered as a user input behind the scenes, I can fully accept that as a realistic possibility. Thank you for providing such a valuable and insightful perspective to this thread.
However, the core issue and my biggest disappointment with this forum’s governance is that Niantic’s official team remains completely silent, relying entirely on general volunteers to debug the system and smooth things over.
If many users are experiencing unintended location shifts due to faulty web UI design—resulting in them being wrongfully banned as “malicious abusers”—the official engineering team should analyze the logs, acknowledge that the interface tends to induce user error, and implement a scroll-lock safeguard.
Instead, the official team issues shadow penalties via direct messages, refuses any technical dialogue, and lets the community do the heavy lifting to conclude it as “just a user mistake.” This operational stance is incredibly evasive.
Thanks to your logical insight, my frustration regarding how it happened has been resolved. Thank you to everyone who contributed sincerely.
You keep saying the team should analyze the logs. What logs? What information do you think is going to appear in some kind of log to prove that an input was accidental or malicious?
If the email receipt you received has the “bad” GPS coordinates, then that is what was registered with their system.
「何のログか」についてですが、ITシステムにおける一般的なバックエンドのログ検証とは、「ユーザーの脳内の意図」を覗き込むようなオカルトの話ではありません。
一般的なまともなITシステムであれば、サーバーの受信ログやフロントエンドのイベント履歴を精査することで、以下のような**「システム側のデータ破損」と「ユーザーの操作ミス（スクロール事故）」を明確に区別する客観的データを100%確認できます。
操作イベントのタイムスタンプ： 送信ボタンが押される直前に、画面スクロールに伴う「座標のドラッグ＆ドロップ入力」が本当にブラウザ（クライアント）側で発生していたのかどうか。
APIの伝送データとサーバー受信データの乖離： 送信時にフロントエンド側が生成したリクエストの生データ（Payload）と、サーバー側が最終的にデータベースに書き込んだデータとの間に、通信エラーやパケット破損、あるいは最寄り住所への強制置換ロジックの介入がなかったかどうか。
自動配信メールの末尾に間違った座標が載っているのはあくまで「結果」であって、そのデータが「送信ボタンを押した『後』のバグで壊れたもの」なのか、「送信ボタンを押す『前』のユーザーのミス」なのかを切り分けるためにログを検証すべきだと言っているのです。
もちろん、世界規模の通信ログを細かく保存するには膨大なサーバーコストがかかります。もし、「一般的なIT基準では判別可能だが、NianticのWayfarerシステムはコスト削減や技術的制限のため、送信ボタンを押した瞬間の『結果の座標』しかログに残らない仕様（そこまで判別できないシステム）である」**というのであれば、公式からそのように説明していただければ私も「検証不可能な事故だった」として100%納得します。
しかし、データベースに登録された結果の数字だけを見て「これがすべてだ」と決めつけるのは、システムの不具合の可能性を最初から排除した、技術的に極めて乱暴な議論です。
[English Summary]
When I say “analyze the logs,” I am referring to standard IT system engineering, not mind-reading. In any properly built IT platform, checking server reception logs, session logs, and front-end event history can easily distinguish between a “backend data corruption” and a “user input error”:
Event Timestamps: The logs would register whether a coordinate-change/drag event actually occurred on the client-side right before submission.
Payload Discrepancies: Developers can compare the raw payload generated by the browser at the exact millisecond of submission against the final corrupted data written into the database to detect transmission glitches or forced snap-to-address bugs.
The corrupted coordinates in the email footer are merely the result. The purpose of a log review is to determine whether that corruption happened BEFORE or AFTER hitting submit.
Of course, maintaining detailed tracking logs for a global user base requires immense server capacity and cost. If the reality is that “while it is technologically possible in general IT, Niantic’s Wayfarer system is structurally limited and only stores the final submitted coordinates without deeper event logs,” then if the official team simply stated that, I would 100% accept it as an unverifiable accident.
However, looking strictly at the final database value and claiming “this is the absolute truth” is a technologically clueless argument that completely ignores the possibility of infrastructure failure.
I don’t recall any time Wayfarer staff has ever confirmed (or denied) those kind of technical details just because one person demanded to know them.
I think it’s best that you accept that your belief about how the system works does not align with the reality of how it works.
I see no proof that “many users” are experiencing this problem. So far, almost all the examples I’ve seen of a submission being located incorrectly have come down to:
- the user making a simple mistake (I’ve done it)
- the user not knowing that they needed to move the submission pin
- the user accidentally moving the map (I’ve done it)
- the user intentionally locating the pin away from the real world location in order to gain an in-game advantage (sometimes admitting to that afterwards, but often denying it even after they have been caught)
- the user refusing to agree that their degree of mislocation is wrong
ちょっと確認ですが、あなたは私の文章をまともに読んでいますか？
私は先ほどの投稿で、あなた方が提示した「Webスクロール時の意図しない誤操作（ユーザーの過失・事故）」という可能性について、「1つの可能性として十分に受け入れる（納得した）」と、自分の非（過失の可能性）をすでに認めています。
それにもかかわらず、なぜ私が未だに「システムエラーだと頑なに言い張っている頑固者」であるかのような的外れな箇条書きを並べているのでしょうか。人の意見を読まずに自身の主張を繰り返すだけでは、ディスカッションになりません。
私が問題にしているのは原因の有無ではなく、そうした誤操作を誘発するUIの罠や不具合の可能性に対して、公式が一切の技術的アナウンスも対話もせず、一般ボランティアの推測だけに幕引きを委ねている運用の不誠実さです。
今後、技術的・客観的で建設的なお話をしてくださる方には喜んでお返事いたしますが、文脈を読まない感情的な反論や、価値のない水掛け論には一切お答えしませんので悪しからずご了承ください。
[English Summary]
Just to be clear: Did you actually read my previous post?
In my last reply, I explicitly stated that I fully accepted and agreed with your theory about the involuntary web-scrolling input error as a highly realistic possibility for my case. I already acknowledged that potential oversight on my end.
Despite this, you are still listing out completely irrelevant bullet points as if I am still stubbornly denying any personal error. It is impossible to have a meaningful discussion if you refuse to read my comments and merely repeat your own agenda.
My point is not about denying user error; it is about the complete lack of corporate responsibility from Niantic, who stays silent on these deceptive UI traps while letting volunteers sweep the issue under the rug as “just a user mistake.”
From this point forward, I will only respond to constructive, logical discussions. I will completely ignore any further thoughtless retorts or valueless arguments that fail to read the context.
The post you are replying to was constructive and logical.
あの「Web UIのスクロールによる誤操作の可能性」という指摘そのものは、この複雑な問題の原因を紐解く上で、非常に建設的でロジカルなアプローチだったと私も思っています。だからこそ、私自身もその可能性を素直に受け入れ、納得することができました。
このように、レッテル貼りの感情論ではなく、事実の挙動に基づいた冷静で公平なディスカッションができることこそが、このコミュニティ本来の価値だと感じます。
Salixsorbusさんのように、フラットな視点で物事を見つめ、本質的なアプローチを模索しようとする方と言葉を交わすことができたことは、とても有意義でした。貴重なご意見をありがとうございました。
最後に一つ、今回の件を通じて強く疑問に思ったことがあります。「アンバサダー」というバッジはいったい何のために存在するのでしょうか？
もしこれが、単にこのフォーラムに長く張り付いているだけの人に与えられるバッジなのだとしたら、何の意味もありません。問題を解決するどころか、一般カスタマーの不満と不信感を募らせるだけの結果になっています。Niantic社に対し、この形骸化したバッジ制度そのものの見直しを強く提案いたします。
[English Summary]
The insight regarding the possibility of an involuntary web-scrolling input error was indeed highly constructive and logical in unraveling the root cause of this complex issue. That is precisely why I readily acknowledged and accepted it as a realistic scenario on my end.
I truly believe that engaging in this kind of calm, unbiased discussion based on actual interface behavior—rather than resorting to emotional labeling—is where the real value of this community lies.
It was genuinely meaningful to exchange thoughts with someone like Salixsorbus, who maintains a flat perspective and seeks a factual approach to the problem. Thank you very much for your valuable and balanced input.
Lastly, this experience has left me with one major question: What is the actual purpose of the “Ambassador” badge?
If this badge is merely awarded to individuals who simply spend the most time glued to this forum, then it holds absolutely no real value. It does nothing to solve actual issues; instead, it only fuels frustration and distrust among everyday customers. I strongly suggest that Niantic completely re-evaluates the efficacy and standard of this badge system.
まず個人への厳しい糾弾はやめましょう。
そしてこれは運営チームやアンバサダーだけの責任ではありません。ウェブ提出システムの試用段階において、私たちコミュニティ全体もこの「人間工学上の操作コンフリクト（競合）」を指摘しきれなかった背景があります。
モバイルデバイスでウェブ提出を行う際、「画面のスクロール」と「ピンの位置指定」のどちらもスワイプで行うという極めて誤操作を招きやすい設計に対し、当時明確な問題提起や解決策の提案ができなかった点については、コミュニティ側も振り返るべきかもしれません。
An ambassador serves as the liaison between the Wayfarer team and the community and vice versa. We communicate to Niantic when there are problems with the system that need to be addressed and how those are negatively impacting the community. But sometimes our role is to help members of the community understand that an issue they are dealing with is not as wide-spread as they think it is.
In this case, you wrote in more than one comment that you think this problem is being experienced by many users. I listed out my extensive experience dealing with people who have made claims that they were unfairly punished for mislocating a wayspot and what is usually the reality of the situation. There are a lot of people in the world of Pokemon GO who are trying to discredit the Wayfarer system by claiming that the punishment system is unfair or wrong. We have seen cases where punishments were overturned by Wayfarer staff. But those are vastly outnumbered by cases like the ones i listed in my previous comment.
In my role as a Wayfarer Ambassador, I will absolutely give the team constructive criticism when they deserve it. But I’m going to support them when they deserve that, too.
ご説明ありがとうございます。
つまり、運営の代わりに「それはユーザー側の勘違いやミスである」とコミュニティを説得し、問題を小さく見せること（ダメージコントロール）が、あなた方の言う「アンバサダーの役割」なのですね。よく分かりました。
貴重な「お仕事内容」の解説をありがとうございました。どうぞこれからも、その素晴らしいお仕事を頑張ってください。
[English Summary]
Thank you for the explanation.
So, in short, your definition of the “Ambassador’s role” is to act on behalf of management to convince the community that “it’s just a user error or misunderstanding,” effectively minimizing the issue for them. I understand perfectly now.
Thank you for sharing the detailed description of your “job.” Please, keep up the great work.
皆様、この投稿にご協力いただきありがとうございます。本件は本筋から外れてしまいましたので、これ以上の関与は締め切らせていただきます。