[Short Summary for Global Admins] My account (mobuzz) was suspended for 30 days due to a “false location” (675m away). This was entirely caused by a known browser/map sync glitch during the “Save Draft” and “Submit” processes.
Proof of Innocence: On the exact same day, the identical nomination submitted by my wife’s account was successfully APPROVED at the 100% correct GPS location using the same photo/text. There is zero logical incentive to fake a location 675m away on one account while getting it approved correctly on another.
Instead of fixing this worldwide platform bug, Niantic blindly penalizes good-faith contributors and support bots (Zachary) abruptly shut down my ticket. I request an engineering review of the logs and the removal of this unfair strike.
I understand that this is distressing for you.
Your appeal will have been looked into by the humans in the team.
What frequently happens is that a member of the wayfarer team contacts you using the forum DM option - if this happens you will see a message icon on your forum avatar top right.
As it is the weekend it may take a little time so please do be patient.
ご質問ありがとうございます。
もちろん、送信前の確認画面ではピンが正しい位置にあることを毎回執筆時に必ず確認しています。
私の地域は住宅等の目標物が多数あるため、私はいつも地図の縮尺を最大まで変え、さらに衛星画像に切り替えて、1メートル以下の単位でピンポイントに座標を指定するという徹底したこだわりを持って申請を行っています。それほど厳格に位置を管理しているため、確認画面で675mもズレていればその場で必ず修正するか、申請を取り下げています。
個人的には、この「衛星画像での超ピンポイント指定」という極限の操作が、Wayfarerの不安定なマップ同期システムに負荷をかけ、バグを引き起こす原因になったのではないかと考えています。
問題は、**「確認画面でいくらチェックしていても防げない、システム内部の致命的な座標ジャンプ」**が存在することです。
時間の都合で「下書き保存」を利用した際、UI上は正しく設定したはずの座標が、次に編集する時に狂っているという現象に何度も遭遇してきました。送信前（あるいは下書き確認時）にズレに気づけた場合は、一度申請を完了させた後に「再編集ができない仕様」であるため、非常にもどかしさを感じつつも、わざわざ申請を取り下げて一からやり直していました。しかし今回は、送信ボタンを押したまさにその瞬間に、画面に映らないシステム内部で座標がジャンプしてしまったため、目視で防ぐことができませんでした。
実は、私が受けた1回目のBANも全く同じ理由（バグによる座標ズレ）でした。
現在のWayfarerは、申請数を確保したい思惑からか、手軽に申請・審査ができるよう基準を下げて門戸を開いています。しかし、その裏にある技術的な課題（座標ズレバグ）を完全に放置したまま、善意の第三者であるユーザーを、システムのエラーによって一方的に「不正者（犯罪者）」扱いし、アカウントをBANする。こんな冷徹で杜撰なシステムだと誰が想像できたでしょうか。自分が大切に育てたアカウントが閉鎖されるリスクを背負ってまで、怖くて誰も申請などできなくなります。順序が完全に間違っています。
今回は英語でのご質問でしたので、念のためこれまでの経緯と詳細を英文でも記載しておきます。
Since you asked in English, I will also include the details of my situation in English below for your reference.
[English Summary]
Yes, I absolutely rechecked the pinned location on the confirmation screen before hitting submit. In my area, there are many residential landmarks, so I always maximize the map scale and switch to satellite imagery to pinpoint coordinates within a 1-meter accuracy.
The core issue is a system-side glitch that bypasses user confirmation. When utilizing the “Save Draft” feature, coordinates frequently warp upon reopening the draft. While I usually catch these errors and painstakingly withdraw and resubmit from scratch (since we cannot re-edit after submission), this specific 675m leap happened internally at the exact millisecond of final transmission via Google Chrome.
In fact, my very first ban was triggered by the exact same technical bug. Niantic has lowered the bar to invite more nominations, yet they completely ignore their own platform’s fatal flaws, treating good-faith contributors like criminals and executing bans based on groundless algorithmic numbers. No one will dare to contribute under such authoritarian risk.
I suggest you to check the flow of submission. Before you submit, you can pin the nomination into the correct position. Its still submitter duty to ensure its positioned correctly instead of relying on whatever position it give
なるほど、あなたが言う「確認」とは、送信後の受領メールの末尾に記載されている座標データのことですね。
確かに、申請後に届く自動配信メールを隅々までチェックし、その時点でズレに気づいて自主的に取り下げを行わなかった点については、私にも確認不足の余地があったかもしれません。
しかし、その論理こそが、Nianticがシステムの致命的な欠陥を解決できないために作った「ユーザーへの責任転嫁の逃げ道」そのものです。
もし本当にユーザーに確認の義務を課すのであれば、受領メールの段階で「この位置で間違いなければ、リンクを押して正式に申請を確定させてください」というような、**後から確認・修正ができるフロー（承認システム）**を構築すべきです。現在の仕様では、メールでズレに気づいたところで、ユーザーに許された選択肢は「わざわざ申請を取り下げて、また最初から全ての作業を1からやり直す」という理不尽な重労働だけです。一度申請ボタンを押したら再編集すらできない仕様にしておきながら、「メールの末尾に座標を載せておいたから、気づかなかったお前が悪い」というのはあまりにも不条理です。
結局のところ、運営側も「送信時や下書き保存時に座標が勝手にジャンプしてしまう致命的なトラブル」を把握していながら技術的に解決できないため、メールに一言座標を載せることで「私たちは免責されている」と言い張るための逃げの論理を作っているとしか思えません。
手軽さを謳って基準を下げ、ボランティアの門戸を広げながら、バックエンドの通信バグのしわ寄せを全てユーザーの責任にし、挙げ句の果てにアカウントをBANする。このような杜撰で冷徹なシステムを、善意のコミュニティに対する「誠実なプラットフォーム」と呼べるでしょうか？
[English Summary]
Ah, so by “verification,” you mean checking the raw coordinates buried at the bottom of the automatic confirmation email after submission.
Perhaps I should have checked that automated email and withdrawn the submission immediately. However, that exact logic is nothing but a cheap excuse for Niantic to shift the blame for their own systemic flaws onto the users.
If they genuinely expect users to verify the final data, they should implement a Proper Confirmation Flow—such as a link in the email saying, “Click here to confirm your submission if the location is correct.” Instead, once you hit submit, you cannot re-edit anything. If you notice a glitch in the email, your only choice is to withdraw it and waste your time re-doing the entire process from scratch.
Forcing users to play Russian roulette with a bugged transmission system, providing no way to re-edit, and then using a hidden line of text in a confirmation email as an excuse to ban good-faith contributors is highly authoritarian and lazy engineering. Niantic is simply dodging their technical responsibilities.
Apart from what you have said in this thread, is there anything to confirm that there is an error that means the location you choose for your submission gets corrupted at some point between creating a draft and submit and the completed submission getting received by Niantic? This is what you have described as the “critical coordinate jump bug on the system side during sending and saving drafts”.
(This would be separate from any issues caused by relying on the GPS location without checking it.)
There could be a discussion somewhere that I have missed.
[English Summary]
salixsorbus, I have found the definitive, undeniable global evidence proving this system-side glitch.
About 24 days ago on Reddit (r/NianticWayfarer), a 10-year+ veteran player (acadiel) reported the exact same coordinate-warping bug that triggered an unfair abuse warning:
Thread Title:“Ten year+ player gets Wayfarer abuse warning for submitting a neighborhood community dock at its actual GPS location”
His case is a 100% identical mirror of mine:
He verified everything via satellite/geotags, but upon submission, the system internally warped his pin directly onto the nearest residential house.
He suspected that Wayfarer’s backend system forcibly snaps or syncs coordinates to the nearest street address/landmark during transmission, causing an involuntary data corruption.
The Niantic support was a total “brick wall,” repeating automated responses.
This proves that the “invisible coordinate jump bug at the millisecond of transmission” is a documented global defect affecting innocent users.
The timeline of absolute facts:
My original photo Exif: 100% correct location.
My visual confirmation on UI: 100% correct location.
My wife’s submission (same photo):100% correctly received and approved.
Global Reddit Reports:Proven backend bug that forces pins to warp to adjacent locations upon transmission.
My final received data:Warped 675m away exclusively due to this system corruption.
Niantic cannot continue to use post-submission email footers as a legal shield to blame voluntary contributors for its own broken infrastructure. I strongly demand that the engineering team perform a rigorous review of the backend transmission logs.
