Commons:Requests for checkuser/Case/Andrija12345678
Jump to navigation
Jump to search
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.
Andrija12345678
[edit]- Andrija12345678 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
Suspected related users
[edit]- Andrija1234567 (talk • contribs • Luxo's • SUL • deleted contribs • logs • block user • block log )
- Related IP address, if any (talk • contribs • IP address, if any/lookup WHOIS • IP address, if any.html RBL • tools • luxo's • IP address, if any crossblock • block user • block log
Rationale, discussion and results
[edit]Reason: Replace this text with an explanation of why this check needs to be carried out including your explanation of your request for checkuser and examples of policy violations. Note that we do not fish, and you need to explain why we need to check (how is Commons disrupted, or the admins' work made harder) or we may decline the request. Please give some corroboration of why you think the users are related, not just a statement that they are. AnToni (talk) 16:17, 12 January 2021 (UTC)
- @AnToni: Is there any reason a check is needed here? Is there any abuse committed by any of the users listed here? pandakekok9 13:02, 13 January 2021 (UTC)
- Declined - 1) Per COM:RFCU, "Checkuser is a last resort for difficult cases; pursue other options first." Not withstanding the quacking name (note {{Duck}} is in the "request declined" section), the relationship is apparently so obvious that the requestor has already blocked Andrija12345678 on bs.wiki and 2) the request appears copy-and-pasted instruction boilerplate with, thereby quite ironically, no evidence of either the relationship or the disruption to the Commons. Эlcobbola talk 15:39, 13 January 2021 (UTC)
The above discussion is preserved as an archive of the Request for checkuser. Please do not modify it.
Subsequent requests related to this user should be made above, in a new section.
Subsequent requests related to this user should be made above, in a new section.