Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Joey Samson" edits #47

Open
TagaSanPedroAko opened this issue May 16, 2018 · 7 comments
Open

"Joey Samson" edits #47

TagaSanPedroAko opened this issue May 16, 2018 · 7 comments

Comments

@TagaSanPedroAko
Copy link
Collaborator

TagaSanPedroAko commented May 16, 2018

@govvin, @seav

I just discovered that the previously blocked user "Joey Samson" are again vandalizing the map with non-existent or speculative edits related to planned LRT lines. I just undid his latest edit that added a fake LRT-1 station (https://www.openstreetmap.org/changeset/58882760#map=16/14.5893/120.9824) and warned him. I think he should be blocked longer than the previous one.

Modus operandi of user (and sock puppets):

  • Additional of unconfirmed/speculative or completely fictional urban developments, usually related to real estate and transportation, like new malls, mall expansions, and unbuilt or fictional LRT/MRT stations. Some of the user's edit resulted into major deletion of features that still exist (e.g. the former TEC Theater near SM Center Muntinlupa)
  • Randomly adding users as friends.
  • Pestering other users to add administrative boundaries.
@ianlopez1115
Copy link

The user has resurfaced from inactivity a few days ago, editing administrative boundaries in the Caloocan area (changeset 85562522). This has been fixed in changeset 85723971.

@TagaSanPedroAko
Copy link
Collaborator Author

TagaSanPedroAko commented May 5, 2021

Late reply, but have just found another possible sock puppet of this account: News General. No edits, but is pestering me. Have requested block as precaution, but no development since January.

@DP24PH
Copy link

DP24PH commented Jul 28, 2021

UPDATE: Upon receipt of Ticket#2016122510000052, the said account got blocked by OSM DWG for 10 years, preventing further suspicious edits. I have specifically reported the said account for vexatious request that even our local mappers (including @ianlopez1115) got fed up already. Reversions have initiated by the DWG team, thus restoring the affected changesets back to original one. However, we have to watch out for further sock puppet of the associated account.

@ianlopez1115
Copy link

To be clear, I'm fed up with the requests to add boundaries for this place or that place (to quote a recent changeset comment replying to that). Hopefully the block placed on the user would either deter further requests or make the user reassess one's self and hopefully engage with the community in good faith.

@DP24PH
Copy link

DP24PH commented Jan 5, 2023

UPDATE [EXTRA INFORMATION 2] as of 2023-01-05

Upon recent email notification receipt, another account (Lian Spurgeon Suarez Las Piñas II) has been registered. However, due to the possibility of being a sock puppet of this account, targeting most of our fellow OSM mappers for possible harassment, immediate action is now required. @SomeoneElseOSM from OSM-DWG could help us with this issue.

CC: @Timmy-Tesseract @govvin @seav

@SomeoneElseOSM
Copy link

Thanks. Re "Lian Spurgeon Suarez Las Piñas II" email [email protected] with a subject of "Re: [Ticket#2023010510000061] Lian Spurgeon Suarez Las Piñas II" if you have any more info.

@ianlopez1115
Copy link

ianlopez1115 commented Jan 7, 2023

@DP24PH

I suggest that the user be reported if either one of the following are met:

  • User sends a request via the OSM user messaging service and/or by commenting on changesets that certain map features such as but not limited to boundaries of legislative districts and local government units be added and/or modified
  • User makes disruptive edits, especially those focused on commercial buildings (including shopping malls) and railway-related infrastructure

Best to keep an eye on the said account for now. If there are disruptive edits made under that account, revert and report. If the account sends similar requests, do not reply/interact and instead report to the Data Working Group using the same subject. If the account continues to persist, keep sending relevant proof until it is dealt with.

Also, for the record I previously filed a complaint as [Ticket#2020050310000054] with the heading/title "Blocked user with history of spurious edits keeps messaging me" in May 2020 hoping that I no longer have to receive messages, which worked to a certain extent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants