False sock-puppetry allegations (checkuser tool abuse) on 29 June 2019

The full correspondence with the Arbitration Committee: outline.

Precursor

A content-dispute escalated into a debated block. The Arbitration Committee was notified of the unwholesome circumstances (admin involved in a conflict). Shortly after the block was escalated into sock-puppetry allegations by a high-profile (checkuser) admin, who then quickly backed out, and “washed hands”.

“You know what, I don’t even care any more. It’s no longer a CU block, and I don’t want to have anything to do with you any more. Please, no one contact me about this editor; I’ve washed my hands of it. NinjaRobotPirate (talk) 16:21, 29 June 2019 (UTC)” (diff)

This was the first encounter with this admin. Mind-bogglingly, the false allegations are still publicly visible.

Proof of legitimate use of alternative accounts

Preparation

  • 18:51, 27 June 2019 - “Do you have any alternate accounts that you’d like to declare? NinjaRobotPirate (talk) 18:51, 27 June 2019 (UTC)”
  • 23:45, 27 June 2019 - “I declared it to the ArbCom. —Aron M 23:45, 27 June 2019 (UTC)”
  • 19:52, 28 June 2019 - “Might I ask you: did this question help you review my unblock request? —Aron M 19:52, 28 June 2019 (UTC) ”
  • 20:09, 28 June 2019 - “I’m not going to even consider unblocking you unless you’re up front about what other accounts you’ve used. NinjaRobotPirate (talk) 20:09, 28 June 2019 (UTC)”
  • 15:05, 29 June 2019 - “If you aren’t “going to even consider unblocking”, […] then what was the purpose of Your question? […] I can only think this is just an effort to find another reason to block me, which is very disheartening. —Aron M 15:05, 29 June 2019 (UTC)”
  • 15:32, 29 June 2019 - “Since you’re so enamored of Arbcom, you can appeal to them. This is now a CU block. NinjaRobotPirate (talk) 15:32, 29 June 2019 (UTC)”

Shorter than one hour CheckUser block (log)

  • 15:32, 29 June 2019 - CheckUser block
  • 15:51, 29 June 2019 - “Some of your accounts are obviously interacting with each other, and since you won’t even say what accounts you’ve used previously, you can deal with the only people you’re williing to be open with. NinjaRobotPirate (talk) 15:51, 29 June 2019” - Proof: a proper signature
  • 16:20, 29 June 2019 log - Reverted CheckUser block.
  • 16:21, 29 June 2019 - - “You know what, I don’t even care any more. It’s no longer a CU block, and I don’t want to have anything to do with you any more. Please, no one contact me about this editor; I’ve washed my hands of it. NinjaRobotPirate (talk) 16:21, 29 June 2019 (UTC)”
  • The alt accounts remain blocked, user pages state “operator has abusively used multiple accounts”.

Follow up

  • 18:42, 29 June 2019 “Thank you for reverting the CU block. Might I ask you to also revert closing the unblock request with the reason: “Confirmed sock puppetry. NinjaRobotPirate (talk) 15:31, 29 June 2019 (UTC)” , or am I allowed to do it?”
  • 18:42, 29 June 2019 “I’m disheartened by NinjaRobotPirate assuming bad faith to such a great extent, that escalating the block was necessary.”
  • 18:54, 29 June 2019 - Bbb23 revoked talk page access
  • 19:10, 29 June 2019 - AndrewGProut still at it, after a month of silence (minor editwar on a talk page , on the article , another article ) - “Wikipedia is not therapy = Aaron needs to vent his problems with the world elsewhere. Andrewgprout (talk) 19:10, 29 June 2019 (UTC)”

Reports

The full correspondence of this ongoing harassment: outline.

Editor blocked within 22 hours of another user's conflict-of-interest accusations

On 28 May admin Bbb23 made a threat of blocking: “I don’t see you lasting very long.” … “I’m monitoring your edits”. On 17 June he saw an opportunity, and without a warning, made an indefinite block within 22 hours. This is the timeline of related events.

Accusations and block

Report to ArbCom

Unblock request

  • 2 July, 2019 - Open letter to the enwiki ArbCom and Functionaries
  • 13 hours later - Response failing to address the inquiry, and admin accountability question
  • 2 July, 2019 - Repeated inquiry for justification of previous block
  • Not answered
  • 4 July, 2019 - “Please acknowledge receiving this and the previous email 2 days ago, inquiring the reason for the block”
  • 5 July, 2019 - Second response failing to address the inquiry, and admin accountability question
  • 6 July, 2019 - “In lack of evidence, the DE block remains unjustified. I assume it is understood, this is a breach of WP:ADMINACCT