Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2844a09e98126ee

Jump to content

Wikipedia:Requests for checkuser/Case/Red4tribe

From Wikipedia, the free encyclopedia
If you are creating a new request about this user, please add it to the top of the page, above this notice. Don't forget to add
{{Wikipedia:Requests for checkuser/Case/Red4tribe}}
to the checkuser page here. Previous requests (shown below), and this box, will be automatically hidden on Requests for checkuser (but will still appear here).
The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.

Red4tribe: yet more funny business

[edit]

The Red Hat of Pat Ferrick t 23:51, 20 May 2008 (UTC)reply

Clearly, more than one IP address is involved here, but it is blatantly obvious that it is the same editor, either using different networks, or enlisting the help of acquaintances to make the edits.

The Red Hat of Pat Ferrick t 01:22, 21 May 2008 (UTC)reply

76.15.56.93 (talk+ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · block log · cross-wiki contribs · CheckUser (log))

  • Code letter: E
  • Supporting evidence: Having only just come off a ban and warning for 3RR violations and sockpuppetry regarding self-made maps that he was adding to Dutch Empire, and me having had to again report him for 3RR violations this time at Italian Empire , he appears to again be resorting to hiding his identity to get his maps added after warnings about reverts, this time to Overseas expansion of the United States.

Why is this one edit so important and in need of a checkip? I realise that checkip's involve privacy issues, unlike checkusers, but Red4tribe has a history of adding dubious maps (or, at least, maps that other users find fault with) and this is the second time that he is resorting to hiding his identity to get them onto WP.

The Red Hat of Pat Ferrick t 00:38, 14 May 2008 (UTC)reply

"Sighs", I forgot to log on, this is indeed my IP, I had logged of then I logged back on. I don't see how this is nesseccary, it has happened before and it will happen again. (Red4tribe (talk) 00:40, 14 May 2008 (UTC))reply

So you have been online for several hours, you were editing right up until 20:20 as Red4tribe, then you logged off, at 20:22 you decided to edit again but "forgot" to log in, made one single reversion as the IP address to add back your map, then logged back in to continue your editing run as Red4tribe from 20:23? And you expect me, and others, to believe that after this conversation in which you admit to sockpuppetry because it was an "easier way to get information in wihtout me breathing down your neck"? The Red Hat of Pat Ferrick t 00:49, 14 May 2008 (UTC)reply
No, I don't expect you to believe it because it's you. And at this point, really don't care about the accuracy of articles anymore, you are just undoing every edit I make(nearly) just to bother me. It is really quite pathetic. I was planning to call it a night, when I had seen my map(which is accurate) removed so, I hastily added it back, forgetting to log in. Now I am going to have to wait and defend my case. (Red4tribe (talk) 00:54, 14 May 2008 (UTC))reply

Red4tribe: New Request

[edit]
Now claims, after first replying, when challenged, "let's see what happens" that it is his "brother" sitting next to him. The Red Hat of Pat Ferrick t 10:43, 5 May 2008 (UTC)reply
Trip Johnson/Red4tribe/SaudiArabia44 Trip Johnson is another account with exactly the same signature, seems to be generating a consensus with his sock puppet accounts on the Talk:Battle of Harlem Heights page [] with all three contributing with exactly the same signature

Clerk note:Interesting how Red was dormant for 2 years. Blocked and tagged sock indef. Red 1 week.RlevseTalk 01:13, 6 May 2008 (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.