Wikipedia:Long-term abuse/Tim Zukas
Original name(s) | Tim Zukas |
---|---|
Wikilifespan | Since August 2010 |
Known IPs | See list |
Physical location | Oakland and other socks should be tagged and reported to sockpuppet investigations for confirmation. When reporting, please link to this long-term abuse report. When the active abuse has been taken care of, please update this report with the latest information. |
Status | Active |
Please report all ongoing incidents of abuse to ANI.
Basic information
WP:MULTIPLE
to gain the upper hand in content disputes. Under his attention, multiple articles have been edit-protected.
Many other editors have reverted Tim Zukas's work, but his persistence creates edit wars at articles such as:
- Braniff International Airways[1][2][3][4][5][6][7][8]
- Columbia Gorge Regional Airport[9][10][11][12][13][14][15][16]
- Boeing 314 Clipper.[17][18][19][20][21][22][23][24][25][26][27][28]
- Editing logged out
It's clear from certain sequences of edits that Tim Zukas has edited logged out as these IPs. Tim Zukas has even answered two questions on his own talk page using IP addresses.[29][30]
- Frontier Airlines (1950–1986)[31][32]
- Union Pacific GTELs[33][34]
- Pacific Air Lines: Edit by Tim Zukas, (BracketBot signals the Tim Zukas talk page a few minutes later), then a few minutes after that, an edit by IP to fix BracketBot problem, with an edit summary of "Fixing typo raised by BracketBot".
- Gerald R. Ford International Airport[37][38]
- Twin Peaks (San Francisco)[39][40]
- Horseshoe Curve (Pennsylvania)[41][42]
- National Airlines (1934–1980)[43][44]
- Regarding horseshoe curve[47][48][49]
- Talk:Baldwin Street[52][53][54]
- Long Island Rail Road[55][56]
- Great-circle distance[57][58]
- Custer CCW-5[59][60]
- Great-circle navigation[61][62]
Blocks
- 8 April 2014, 75.16.27.73 blocked for three months.
- 21 April 2014, 128.32.104.164 was blocked for one week because of block evasion.
- The previous three-month block was evaded again in June 2014.[66]
- 14 April 2015, Tim Zukas was blocked for six months for persistent disruptive editing.
- 25 January 2016, Tim Zukas was blocked indefinitely after this warning followed by this AIV report.
Involved IP addresses
- 205.154.246.130 (talk · contribs · WHOIS) November 2016 – April 2017
- 205.154.244.241 (talk · contribs · WHOIS) June, December 2016, January–April 2017
- 205.154.244.243 (talk · contribs · WHOIS) January–February 2017
- 169.229.6.163 (talk · contribs · WHOIS) September 2014, January–February 2017
- 205.154.244.240 (talk · contribs · WHOIS) December 2016 – March 2017
- 169.229.6.164 (talk · contribs · WHOIS) January 2015, February 2017
- 130.65.109.102 (talk · contribs · WHOIS) October 2016, February 2017
- 204.102.74.238 (talk · contribs · WHOIS) December 2014, January–February 2015, January, October–December 2016
- 169.229.202.223 (talk · contribs · WHOIS) November 2014, January–March 2015, February 2017
- 169.229.202.225 (talk · contribs · WHOIS) February–March 2015, February 2017
- 75.16.27.79 (talk · contribs · WHOIS) November 2014 – February 2015
- 50.161.85.102 (talk · contribs · WHOIS) August–September 2014
- 128.32.104.169 (talk · contribs · WHOIS) July–October 2014, January–February 2017
- 75.16.27.70 (talk · contribs · WHOIS) March 2013 – August 2014
- 70.90.163.138 (talk · contribs · WHOIS) October 2013 – February 2015, December 2016 – March 2017
- 128.32.146.105 (talk · contribs · WHOIS) April 2013
- 128.32.146.101 (talk · contribs · WHOIS) January 2013 – April 2014
- 75.16.27.73 (talk · contribs · WHOIS) January 2013 – February 2015
- 128.32.104.160 (talk · contribs · WHOIS) August 2012 – August 2014
- 128.32.11.112 (talk · contribs · WHOIS) February 2012 – November 2013
- 128.32.104.161 (talk · contribs · WHOIS) November 2011 – March 2014
- 173.164.133.26 (talk · contribs · WHOIS) April 2011 – February 2015
- 75.16.27.74 (talk · contribs · WHOIS) April 2011 – February 2015
- 128.32.104.164 (talk · contribs · WHOIS) September 2010 – April 2014
- Tim Zukas (talk · contribs · deleted contribs · page moves · block user · block log)
Comment
SPI
case, linking in this abuse report. I reproduce below. I suspect that not a lot will happen in the case of the historical socks.
“ | Suspected socks should be tagged and reported to sockpuppet investigations for confirmation. When reporting, please link to this long-term abuse report. When the active abuse has been taken care of, please update this report with the latest information. | ” |
DieSwartzPunkt (talk) 17:50, 12 April 2015 (UTC)