Brian Reddyb is a confirmed long-term sock puppeteer, hoax perpetrator, and community-banned user; a list of all socks used until
2008-02-15 is available
here. I eventually blanked the list in the spirit of
WP:DENY; however, this has not deterred the vandal. The accounts listed above are the socks Reddyb has used since then; all, except for
QuintessentialReddy, have already been blocked indefinitely. In two recent posts to my talk page (
[9],
[10]), Reddyb has declared that he has again perpetrated several "Brian Reddyb Coups" – his terminology for planting derivations of his name into various articles (see
here for a listing from last year, from which most of the diffs above are taken). Today I uncovered
this "coup", which had already gone unnoticed for around ten days.
My opinion is that a checkuser should be run in order to identify and list all socks (other than the above) which have been used by this vandal. Firstly, it would allow them to be blocked en masse, and secondly, it would facilitate the reversion of the subtle vandalism without having to undertake tedious investigation.
Ayla (
talk) 23:03, 1 March 2008 (UTC)
reply
- Clarification: A checkuser is not being requested to confirm any of the accounts listed above (they are already obvious), but only to unearth new ones. Thanks.
Ayla (
talk) 23:08, 1 March 2008 (UTC)
reply
- Ugh! Brian Reddy was a pest when I started on WP four years back. Can't believe he's still at it! -
Alison
❤ 03:34, 2 March 2008 (UTC)
reply
Confirmed - the following:
-
QuintessentialReddy (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddtastic (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddybop (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddyb (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Le Coup de Reddyb (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
ReddyFoSho (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddybee (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddtastic (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Maltese Reddy (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
ReddybPartDeux (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Illbreddy (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddyfowhat (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
Reddybrek (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
ReddyRNot (
talk ·
contribs ·
deleted contribs ·
logs ·
filter log ·
block user ·
block log)
-
IP blocked - hardblocked, for quite a long time. He'd been using a corporate gateway for a lot of his vandalism -
Alison
❤ 03:41, 2 March 2008 (UTC)
reply
- Thanks! Surprisingly, no vandalism appears to have been performed by the newly-exposed socks.
Ayla (
talk) 14:30, 2 March 2008 (UTC)
reply
-
Clerk note: All socks have been blocked and tagged.
Icestorm815 •
Talk 21:45, 2 March 2008 (UTC)
reply
Reopening case
The above sock, which apparently was missed during the last checkuser which was created some 20 hours after the last checkuser, has contacted me again:
[11],
[12]. Could you please run a scan on this account too? Regarding the hardblock – keep in mind that this vandal most likely has a dynamic IP; see
the old list.
Ayla (
talk) 22:53, 2 March 2008 (UTC)
reply
-
IP blocked - no other socks ... yet. This editor is also using a /16 range from a popular Irish ISP. As it happens, another banned editor is being abusive on that range, so if this persists, a short /16 rangeblock AO/ACB might be the thing to do -
Alison
❤ 01:50, 3 March 2008 (UTC)
reply
- OK, thanks. I'm starting to doubt whether there really are any other "coups". Since a /16 range is rather wide, I'll refrain from relisting for now unless the situation gets out of hand.
Ayla (
talk) 09:53, 3 March 2008 (UTC)
reply
Weekscrazy has been
removing content from the
discussion which led to the
sock puppeteer's
ban.
Reddysteddybrekky, apart from having a similar username to the
sock puppeteer, has
vandalised
FM104 (an article also edited by
Weekscrazy) and sought to
introduce a paragraph of
questionable notability. The newly-registered
Onetwothreefourfivesixseveneightnineteneleventwelve would soon afterwards
re-format the paragraph.
CounterFX 17:30, 12 July 2007 (UTC)
reply
Confirmed --
jpgordon
∇∆∇∆ 22:11, 12 July 2007 (UTC)
reply
- Thanks.
CounterFX 23:05, 12 July 2007 (UTC)
reply
- For reference:
Fm104 is also part of the latest wave of accounts targeting the
FM104 article, performing an identical act of vandalism as
Reddysteddybrekky (compare
[13] and
[14]). The connection is obvious, so no further checkuser is necessary.
CounterFX 15:12, 13 July 2007 (UTC)
reply
Brian Reddyb and
Chiefofmsiss have recently been banned on basis of compelling evidence of sock puppetry and elaborate hoaxes (refer to discussions on
Talk:Rednex; for a concise demonstrative sample of the disruptive edits, see
[15] and
[16]).
Sanchezsteamer was also banned on grounds of high probability of involvement (see
[17]).
Request for checkuser is intended to conclusively confirm
Sanchezsteamer's involvement in the hoax, and implicate
Chiefofmsiss1. Also request admin to ban
Chiefofmsiss1 and block the creation IP if the checkuser result is affirmative.
CounterFX 22:57, 3 July 2007 (UTC)
reply
Confirmed for Brian R and Chiefofmsiss. Chiefofmsiss1 is kinda obvious. Sanchezsteamer feels like a neighbor or something. --
jpgordon
∇∆∇∆ 04:43, 4 July 2007 (UTC)
reply
Copy that.Affirmative. Over
Chiefofmsiss1 08:50, 4 July 2007 (UTC)
reply
- Thanks
Chiefofmsiss1. Can someone kindly effect the ban now?
CounterFX 13:12, 4 July 2007 (UTC)
reply
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.