From Meta a Wikimedia project coordination wiki Redirected from Requests and proposals Requests for CheckUser informatio

This page allows you to request information on Meta.

Procedure

Please read the before asking for a check.
When adding new requests, please use the {{}} template to list the user names in question and {{}} for IP addresses, which simplifies investigation.
List your request at the bottom of the "Requests for Meta-Wiki only" heading.
When asking for a check we need to know:
- why do you believe that the accounts are related (please present evidence for that with the help of , etc.),
- why, if the accounts are related, they are being used abusively, in violation of policy; and
- why a block or other measures can't be justified without the need of technical evidence.

Important

Note: To request checkuser access, see (Steward requests/Permissions).
Note: To request information for other wikis, see (Steward requests/Checkuser).

Checkuser icons
These are used by and for easier skimming of their notes, actions and comments.
{{}}: Confirmed	{{}}: Additional information needed
{{}}: Likely	{{}}: Deferred to
{{}}: Possible	{{}}: Completed
{{}}: Unlikely	{{}}: Note:
{{}}: Unrelated	{{}}: Doing...
{{}}: Inconclusive	{{}}: Stale
{{}}: Declined	{{}}: CheckUser is not for fishing
{{}}: CheckUser is not magic pixie dust	{{}}: The CheckUser Magic 8-Ball says
{{}}: It looks like a duck to me	{{}}: CheckUser is not a crystal ball

archives all sections tagged with {{|1=~~~~}} after 1 day.

Requests for Meta-Wiki only]

Seawolf35]

( • • • logs • • block log • CentralAuth • AllContribs • checkuser • investigate)
( • • WHOIS • • block log • guc • checkip)

Seawolf35 is a new account created about a year ago. They have started an RfC (Requests for comment/Global ban for Slowking4 (2))

IP 119.59.127.124 is globally locked. Nonetheless the IP has a single edit to (Requests for comment/Global ban for Slowking4 (2)), making a number of changes to the original post made by Seawolf35. [1]

"This user is currently globally blocked. The global block log entry is provided below for reference: 06:48, 6 April 2024: EPIC (meta.wikimedia.org) globally blocked 119.59.126.0/23 (expires on 6 April 2025 at 06:48) (Open proxy/Webhost: See the help page if you are affected)"

As a result, anyone reading or closing the RfC, it will look like the edits were there from the beginning, and that everyone had a chance to see them before commenting. In fact, it was made several weeks after the RfC was opened, after all the votes had been made. There is nothing in the RfC to indicate that any changes were made to the original post, or who might have made them.

The IP edit was made 16:50, 12 April 2024. A few hours later, at 23:47, 12 April 2024, Seawolf35 showed an interest in other global locks made by the same user:EPIC. [2] () 18:19, 13 April 2024 (UTC)[reply]

@ You need to drop the stick, I assure you I am not that IP. I do a lot of SRG reporting and I have reported some of the accounts that got locked, that is why I had an interest. Such a check that you have requested, would be a violation of global Checkuser policy, which you evidently didn’t bother reading. () 18:38, 13 April 2024 (UTC)[reply]

Don't you want to know who is trying to disrupt the RfC?

Don't you want to know who is making stealth edits to deceive the people who close the RfC?

Don't you think that it would be more fair to add changes to the original RfC at the beginning, instead of at the end when everyone has commented already?

Did you stop being concerned about sockpuppets? () 19:00, 13 April 2024 (UTC)[reply]

How the fuck does adding links to a by-default minuscule section deceive people?

Did you stop being concerned about sockpuppets?

And I thought you said that (a potential sockmaster saying that an editor is not them is definitive proof?) () 20:24, 13 April 2024 (UTC)[reply]

IPs should not be connected to an account no matter if the IP is a VPN or alike. () 14:12, 14 April 2024 (UTC)[reply]

Not done we are never going to report that a username=an IP address. — 14:23, 14 April 2024 (UTC)[reply]

Slowking4]

( • • • logs • • block log • CentralAuth • AllContribs • checkuser • investigate)
( • • • logs • • block log • CentralAuth • AllContribs • checkuser • investigate)

Culturefan4 is a new account created on March 16 and their only edits have been on (Requests for comment/Global ban for Slowking4 (2)). Besides the similarities in username, they to be one of their fans (and deny they are Slowking4), but I generally find it very hard to believe that they are not the same user (or are meatpuppets). -- ( | ) 07:15, 18 March 2024 (UTC)[reply]

If there is going to be an attempt to dox users with low edit counts, why not do ALL the low edit accounts that have been questioned, and not just badger the oppose votes. ==> also / () 16:36, 18 March 2024 (UTC)[reply]

And here I was beginning to think the drama was at a low level. Go ahead, run the check. () 16:41, 18 March 2024 (UTC)[reply]

@ Exciting, your words of Betacommand reminded me of something happened previously. This request is not anything could be considered as doxxing, instead an attempt to stop consensus hijacked by sockpuppets. () 10:21, 19 March 2024 (UTC)[reply]

I agree with Lemonaka. -- ( | ) 20:22, 20 March 2024 (UTC)[reply]

@ () 02:57, 23 March 2024 (UTC)[reply]

Not done: though Culturefan4's account was created to support Slowking4 in this RfC, and they're certainly a sockpuppet of someone, I don't think there is sufficient evidence to warrant a comparison with Slowking4. This isn't consistent with Slowking4's usual communication style. Thanks for the report, it is good to have more eyes on this regardless of whether a check happens. Regards, (—) 16:12, 23 March 2024 (UTC)[reply]

From Meta a Wikimedia project coordination wiki Redirected from Requests and proposals Requests for CheckUser informatio

Meta:Requests for CheckUser information

Requests for Meta-Wiki only]

Seawolf35]

Slowking4]

See also]