Wikipedia:Arbitration Committee/CheckUser and Oversight/2022 CUOS appointments/CU: Difference between revisions

Revision as of 14:46, 27 September 2022

Revision as of 14:49, 27 September 2022

Line 21:

:#Since you block a large number of proxies, colos, etc, I'm interested to know how you handle associated collateral. As a checkuser I'm certain you'll see a whole lot more. Can you provide some examples of potential collateral and how you've dealt with it? -- [[user:zzuuzz|zzuuzz]] ^{[[user_talk:zzuuzz|(talk)]]} 15:21, 26 September 2022 (UTC)

:#*Generally speaking, I do my best to limit potential collateral of webhostblocks by querying for underlying ranges that may not be assigned to the same provider ({{code|whois -aM $RANGE}}) and looking for specific indicators of hosting activity with Shodan range queries whenever I'm uncertain. I also frequently soften bot-proxyblocks when I see evidence of CGNAT use. A specific example of collateral mitigation that comes to mind is when a steward reached out because he had verified that [[special:contribs/213.202.232.64/28|213.202.232.64/28]], a subrange of the then-hardblocked hosting range 213.202.232.0/21, was being used by a school. I didn't want to lift the block entirely because the underlying range [https://www.shodan.io/search?query=net%3A213.202.232.0%2F21 does have lots of hosting on it], so we worked out how to reblock the entire range in [https://meta.toolforge.org/stalktoy/213.202.232.0%2F21 small increments] and dropped the /28 down to a softblock. --[[User:Blablubbs|Blablubbs]] ([[User talk:Blablubbs|talk]]) 17:04, 26 September 2022 (UTC)

:#You seem to be most active in blocking open proxies. I've looked through your block log. On 1 January 2022 you blocked two ranges 133.125.0.0/16 and 133.167.0.0/16 as colocation webhost SAKURA. Walk me through how you reached that conclusion. Then on 31 October 2021 (I've not looked further back) you blocked 85.255.237.99 with "Block evasion:VXFC." Amanda blocked this editor in 2017 as a sockpuppet of Flow234. This editor appears to edit botanical and medical articles. You blocked following a question about the subject matter of untitled paintings. The previous edit from the IP was a helpful correction in the spelling of Kordofan, Sudan, and the following edit provided information about U S politicians. Walk me through your reasoning. (Sorry this keyboard isn't equipped with a tilde). <!-- Template:Unsigned IP --><small class="autosigned">—&nbsp;Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/92.31.254.24|92.31.254.24]] ([[User talk:92.31.254.24#top|talk]]) 20:49, 26 September 2022 (UTC)</small><!-- Template:Xsign --> How did Dreamy Jazz manage to timestamp my question six minutes before his edit? Having just been notified of a message from Kevin when I switched on this afternoon I have to say that I think he is quoting the wrong policy. The relevant policy is surely [[WP:LOUTSOCK]] which proscribes IP editing from registered editors. It does ''not'' proscribe IP editing from unregistered editors. If you still think I am affected by this clause please run a CheckUser on me. My IP address is unchanged from when I asked the question yesterday. I have not edited "under both a named account and as an IP", nor have I been "using alternative accounts."

:#You mention that you are active in UPE work, what is the line between investigating UPE and investigating socks with CheckUser in your mind? -- [[User talk:AmandaNP|<span style="color:white;background-color:#8A2DB8"><b>Amanda</b> (she/her)</span>]] 05:47, 27 September 2022 (UTC)

:#Your last edit was at 19:45 last night, thus four minutes before the question was asked. Yet the two previous days you edited after that time. Also, you answered the first question within two hours and the second within one hour but my question remained unanswered for eleven hours. Did you communicate with anyone about it before it was removed?

=====Comments (Blablubbs)=====