Wikipedia:Requests for checkuser/Case/Matilda
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.
request links: main • edit • links • history • watch Filed: 06:01, 20 May 2008 (UTC) |
- Matilda (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki) - Master Account
- Bidgee (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · block log · CA · CheckUser(log) · investigate · cuwiki)
- G:
- Supporting evidence: I have a sneaking suspicion that the user Bidgee might be a sockpuppet or meatpuppet(used in non-derogatory intent) for the administrator Matilda based on her behaviour. After I left these messages on Matilda's talkpage [1], [2] Bidgee came rushing to her defence with whom I have never came in contact with my whole life, who was not been involved in any of the matters we were referring to and who has never made an edit at the same time on the same day based on the contributions made by the two. Really what harm is there in checking for clarification? I do not wish to know her IP and if Matilda is in fact using a sockpuppet then my suspicions will be confirmed. If not no harm done. (Note: I told Matilda if she warned me again I would report her, so she did not and instead Bidgee did) TeePee-20.7 (talk) 06:01, 20 May 2008 (UTC)
Declined -
CheckUser is not for fishing - really sorry, but this example is the classic definition - Alison ❤ 07:02, 20 May 2008 (UTC)
- For the record, see
- TeePee-20.7 was subsequently blocked. A strong consensus emerged that TeePee-20.7's behaviour was uncivil; one aspect of this was TeePee-20.7's bad faith accusations of fellow editors such as Matilda and Bidgee.
- --A. B. (talk • contribs) 03:24, 25 May 2008 (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.