| 907 | Wed Mar 27 16:59:56 2002 | 66.185.84.204 | http://www.wyellowstone.com/kellyinn/ |
|---|---|---|---|
| 908 | Wed Mar 27 17:00:23 2002 | 66.185.84.202 | http://www.wyellowstone.com/kellyinn/ |
| 2780 | Mon Apr 15 15:16:59 2002 | 66.185.84.209 | http://www.wyellowstone.com/kellyinn/ |
| 2781 | Mon Apr 15 15:17:28 2002 | 66.185.84.209 | http://www.wyellowstone.com/kellyinn/ |
| 2783 | Mon Apr 15 15:18:20 2002 | 66.185.84.202 | http://www.wyellowstone.com/kellyinn/ |
| 3353 | Sat Apr 20 14:49:58 2002 | 66.185.84.209 | http://www.wyellowstone.com/kellyinn/ |
| 3354 | Sat Apr 20 14:56:01 2002 | 66.185.84.202 | http://www.wyellowstone.com/kellyinn/ |
| 3355 | Sat Apr 20 15:03:12 2002 | 66.185.84.209 | http://www.wyellowstone.com/kellyinn/ |
| 3359 | Sat Apr 20 15:13:15 2002 | 66.185.84.209 | http://www.wyellowstone.com/kellyinn/ |
| 3360 | Sat Apr 20 15:31:20 2002 | 66.185.84.202 | http://www.wyellowstone.com/kellyinn/ |
| 3361 | Sat Apr 20 15:31:23 2002 | 66.185.84.202 | http://www.wyellowstone.com/kellyinn/ |
| 12891 | Thu Jun 20 22:06:18 2002 | 66.185.84.81 | http://www.wyellowstone.com/kellyinn/ |
| 12892 | Thu Jun 20 22:06:42 2002 | 66.185.84.74 | http://www.wyellowstone.com/kellyinn/ |
| 13360 | Mon Jun 24 9:33:59 2002 | 66.185.84.209 | http://www.wyellowstone.com/kellyinn/ |
| 13361 | Mon Jun 24 9:35:34 2002 | 66.185.84.202 | http://www.wyellowstone.com/kellyinn/ |
| 40173 | Thu May 15 16:00:20 2003 | 66.185.84.201 | |
| 40187 | Thu May 15 18:37:25 2003 | 66.185.84.201 | |
| 46977 | Wed Jun 25 20:40:20 2003 | 66.185.84.201 | http://www.wyellowstone.com/kellyinn/ |
| 47768 | Mon Jun 30 22:22:23 2003 | 66.185.84.73 | http://www.wyellowstone.com/kellyinn/ |
| 47769 | Mon Jun 30 22:23:10 2003 | 66.185.84.74 | http://www.wyellowstone.com/kellyinn/ |
| 54685 | Tue Aug 5 19:49:34 2003 | 66.185.84.73 | http://www.wyellowstone.com/kellyinn/ |
| 54686 | Tue Aug 5 19:49:54 2003 | 66.185.84.74 | http://www.wyellowstone.com/kellyinn/ |
| 54865 | Wed Aug 6 20:00:26 2003 | 66.185.84.201 | |
| 54866 | Wed Aug 6 20:01:19 2003 | 66.185.84.202 | |
| 62646 | Sat Dec 20 9:18:34 2003 | 66.185.84.201 | http://www.wyellowstone.com/kellyinn/ |
| 64440 | Mon Feb 2 20:13:36 2004 | 66.185.84.73 | http://www.wyellowstone.com/kellyinn/ |
| 64441 | Mon Feb 2 20:15:25 2004 | 66.185.84.74 | http://www.wyellowstone.com/kellyinn/ |
Sunday, March 30, 2008
Kelly Inn Yellowstone (204 = 202; 209 = 202; 81 = 74; 73 = 74; 201=202)
Extracted here are the entries for the Rogers IPs in the 66.185.84.xxx-range from the Kelly Inn, in Wyoming. These are probably all the same user, but especially to be noted are the coloured pairs, where we see IPs quickly shifting in the midst of a visit. (I'll limit myself here to shifts of two minutes or less.)
Again we see the fluidity of these IPs: one could not be sure that one's IP would be the same from the beginning of a session to the end.
Saturday, March 29, 2008
Visiting Huizhou (197 = 198 = 206 = 196)
Below is bit of a log from a site run by the Chinese government for the administrative district of Huizhou is highly suggestive of how Rogers worked. The links are all dead now, which is probably just as well since I don't read Chinese. Still, they give an idea of one surfer's progress.
There seem to be three people visiting the site at the same, one of them is from Beijing (211.155.36.46, nos. 2, 6, 12-15), another from Chengdu (218.6.192.132: no. 9), and the third a Rogers customer from Ontario, whose IP is shifting (nos. 1, 3-5, 7-8, 10-11).
Beginning at the bottom (no. 1), our Rogers' customer has posted something to forum 5 with x.x.x.198; a minute later, he looks at forum 5 (nos. 3-4), but now has x.x.x.197; he goes to read post (?) 25 of forum 5 (no. 5), but with x.x.x.198 again; then, still x.x.x.198, he looks at forum 15 (no. 7), but within seconds his IP becomes x.x.x.206 (no. 8), then x.x.x.197 (no. 10), then x.x.x.196 (no. 11).
| 时 间 | IP | 操作系统 | 浏览器 | 来 源 网 页 | |
|---|---|---|---|---|---|
| 15 | 3/14/02 4:47:44 | 211.155.36.46 | Win XP | MSIE 6.x | http://xiaogang.net/lb5000/forums.cgi?forum=6 |
| 14 | 3/14/02 4:46:39 | 211.155.36.46 | Win XP | MSIE 6.x | http://xiaogang.net/lb5000/forums.cgi?forum=6 |
| 13 | 3/14/02 4:45:55 | 211.155.36.46 | Win XP | MSIE 6.x | http://xiaogang.net/lb5000/forums.cgi?forum=5 |
| 12 | 3/14/02 4:45:55 | 211.155.36.46 | Win XP | MSIE 6.x | http://xiaogang.net/lb5000/forums.cgi?forum=5 |
| 11 | 3/14/02 4:45:12 | 66.185.84.196 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=15 |
| 10 | 3/14/02 4:44:55 | 66.185.84.197 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=15 |
| 9 | 3/14/02 4:44:02 | 218.6.192.132 | Win XP | MSIE 6.x | |
| 8 | 3/14/02 4:43:34 | 66.185.84.206 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=15 |
| 7 | 3/14/02 4:43:22 | 66.185.84.198 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=15 |
| 6 | 3/14/02 4:42:14 | 211.155.36.46 | Win XP | MSIE 6.x | http://xiaogang.net/lb5000/forums.cgi?forum=3&action=resetposts |
| 5 | 3/14/02 4:42:08 | 66.185.84.198 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=5&show=25 |
| 4 | 3/14/02 4:40:42 | 66.185.84.197 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=5 |
| 3 | 3/14/02 4:40:13 | 66.185.84.197 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/forums.cgi?forum=5 |
| 2 | 3/14/02 4:39:23 | 211.155.36.46 | Win XP | MSIE 6.x | http://xiaogang.net/lb5000/forums.cgi?forum=3 |
| 1 | 3/14/02 4:38:39 | 66.185.84.198 | Win XP | MSIE 6.x | http://www.xiaogang.net/lb5000/post.cgi?action=reply&forum=5&topic=81 |
There seem to be three people visiting the site at the same, one of them is from Beijing (211.155.36.46, nos. 2, 6, 12-15), another from Chengdu (218.6.192.132: no. 9), and the third a Rogers customer from Ontario, whose IP is shifting (nos. 1, 3-5, 7-8, 10-11).
Beginning at the bottom (no. 1), our Rogers' customer has posted something to forum 5 with x.x.x.198; a minute later, he looks at forum 5 (nos. 3-4), but now has x.x.x.197; he goes to read post (?) 25 of forum 5 (no. 5), but with x.x.x.198 again; then, still x.x.x.198, he looks at forum 15 (no. 7), but within seconds his IP becomes x.x.x.206 (no. 8), then x.x.x.197 (no. 10), then x.x.x.196 (no. 11).
Addendum. From the same site, the log from Feb. 27, 2002, shows that x.x.x.204 = x.x.x.198.
Addendum 2. From the same site, the log from March 11, 2002, shows that x.x.x.197 = x.x.x.198 = x.x.x.205.
Addendum 3. From the same site, the logs from March 14, 2002, and March 21, 2002, show that x.x.x.198 = x.x.x.203
This post has 22 minutes (197 = 206)
Over the last five years, the wikipedia articles on subjects to do with Canadian television have been heavily reworked by the Rogers IPs that we have been following. If you look at the contribution histories of 66.185.84.208 (here) and 66.185.84.206 (here) you'll see many, many edits to articles such as Rick Mercer, the CBC, the List of English programs on the CBC, etc.
And so, December 5-6, 2003, the edit history shows a dozen or so edits by 66.185.84.206 (here), all reworking the same section. Then we see this: The quick shift from x.x.x.203 to x.x.x.197 and back again all took place within a couple minutes, and again shows how fluid these IPs could be.
A very popular show with these IPs is This Hour has 22 Minutes, which a handful of the Rogers IPs that we have been tracking have made hundreds of edits to.
Labels:
66.185.84.197,
66.185.84.206,
quick change,
Rogers
Lichen (78 = 80)
This pair of edits to the wikipedia article on Lichen probably shows another example of shifting Rogers IPs:The two edits were made within the same minute. The earlier edit (the second one listed here) was simple vandalism -- "Mark likes lichen" -- and the second edit deleted it, apparently after changing his mind.
Nisha on Tamil music (78 = 73 = 79 = 72 = 75)
We have been tracking a group of Rogers' IPs to see how they could shift in the years 2003-5. One of the most useful sources of data have been message boards that post both a handle and an IP for each post. Combining name, IP, and time has shown several interesting shifts.
Another case in point are the posts of a certain "Nisha" on a board concerning Tamil music (here). Googling "Nisha" on this site gives 80 or 90 posts on a variety of subjects from July 2002 until December 2004. Almost all of these posts report her IP as 66.185.84.78 -- a Rogers IP that is part of the pool that we've been tracking. At several points, however, Rogers seems to have shunted her off to another IP. The first is in the summer of 2003:
- Jul 18 2003 18:46:51 66.185.84.78
Jul 31 2003 21:29:40 66.185.84.73
Aug 5 2003 00:32:37 66.185.84.78
- Feb 5 2004 21:25:49 66.185.84.78
Feb 6 2004 20:26:01 66.185.84.78
Feb 6 2004 20:32:23 66.185.84.79
Feb 11 2004 19:15:47 66.185.84.78
- Nov 11 2004 17:01:35 66.185.84.68
Nov 12 2004 18:33:37 66.185.84.68
Dec 1 2004 15:23:25 66.185.84.72
Dec 22 2004 12:31:48 66.185.84.75
Labels:
66.185.84.72,
66.185.84.73,
66.185.84.75,
66.185.84.78,
66.185.84.79,
Rogers
Magic Adventures of Mumfie (208 = 206 = 79 =81)
Below is a screen-capture of the first dozen edits to the Magic Adventures of Mumfie (a children's show created by creator of Thomas the Tank Engine). In it we see the same pattern that we have seen elsewhere with Roger's IPs -- especially well illustrated with the Thomas the Tank Engine articles (see here, here, here, and here) -- that they can shift around.

Labels:
66.185.84.206,
66.185.84.208,
66.185.84.79,
66.185.84.81,
Rogers
plagiarizing the First Canadian Army (80 = 78)
One of wikipedia's on-going problems is copy-right violation -- well-meaning editors often copy and paste whole articles from elsewhere, thereby undermining the quality of the encyclopedia and, at least theoretically, exposing it to legal action. Wikipedia's policy on this can be seen here, and as you can see there (and here), copy-right violations are immediately deleted.
A Roger's editor breeched that policy in January 2004, copy-and-pasting eight paragraphs from Legion Magazine, as was pointed out when the page was deleted in November of that year.
A Roger's editor breeched that policy in January 2004, copy-and-pasting eight paragraphs from Legion Magazine, as was pointed out when the page was deleted in November of that year.
In the meantime, there had been these 17 edits to the page (which wikipedia administrators can see here):
- 20:02, 29 November 2004 . . Indefatigable (Talk | contribs | block) (Copyright violation)
- 18:08, 19 November 2004 . . GJeffery (Talk | contribs | block) (fixed link)
- 15:49, 4 September 2004 . . Bryan Derksen (Talk | contribs | block) (Category:World War II military units)
- 03:53, 22 August 2004 . . 69.196.224.243 (Talk | block)
- 01:53, 21 August 2004 . . 69.196.224.243 (Talk | block)
- 20:55, 19 August 2004 . . Indefatigable (Talk | contribs | block) (Category:Canadian military formations)
- 13:00, 2 June 2004 . . Topbanana (Talk | contribs | block) (Fix some broken links)
- 00:58, 27 May 2004 . . Adam Bishop (Talk | contribs | block) (fixing links)
- 05:15, 5 March 2004 . . Anthony (Talk | contribs | block)
- 23:04, 11 February 2004 . . David Newton (Talk | contribs | block)
- 02:59, 28 January 2004 . . Gsl (Talk | contribs | block) (copyedit, links)
- 01:36, 15 January 2004 . . 66.185.84.78 (Talk | block)
- 01:08, 15 January 2004 . . 66.185.84.78 (Talk | block)
- 00:59, 15 January 2004 . . 66.185.84.78 (Talk | block)
- 23:23, 14 January 2004 . . 66.185.84.78 (Talk | block)
- 23:19, 14 January 2004 . . 66.185.84.78 (Talk | block)
- 21:55, 14 January 2004 . . 66.185.84.80 (Talk | block)
The bottom half-dozen edits are interesting. The article was created at 21:55 with a rule-breaking copy-and-paste (as I mentioned) by x.x.x.80. Then, over the next few hours, the editor returns as x.x.x.78 and fixes some formatting issues that first cut-and-paste had created.
Clearly x.x.x.80 and x.x.x.78 are the same editor, whose IP was changed by Rogers in mid-stream: the article is less than two hours old when x.x.x.78 returns, and he clearly is picking up where he had left off as x.x.x.80.
Again, the fluidity of Rogers IPs is seen.
Addendum. The same relation between IPs is probably demontrated by this edit in Nov. '03, where x.x.x.78 clears the messages off the talk-page of x.x.x.80. When one goes to edit a wikipedia page, you receive a notice of new messages on your talk page. Here it seems the wikimedia software detected this user's IP as x.x.x.80, but by the time he edited his talk-page, his IP had shifted to x.x.x.78.
Friday, March 28, 2008
fourmilab (202 = 74?)
This one I don't understand at all. Fourmilab, founded by John Walker of AutoCAD fame, is an eclectic download site for a wide variety of computer utilities, articles on mathematics, nanotechnology, etc.

This log suggests that two of the IPs that we've been tracking had hit this site 100,000 times over three months. Also present is 66.185.85.74 (not one of the IPs that we've been tracking).
Also puzzling is the fact that these three Rogers IPs, which began their visits to the site within a day or so of one another, and all begin with wc07. I think that we have to assume that they are somehow related, and that this reflects the kind of shifting back and forth that we've noticed elsewhere, but over a longer timescale for a massive amount of traffic.
You can see its access logs for January 2004, here, which is presented in descending order of the amount of traffic that was coming from an IP. Here is a screen-cap of the top four 'heavy hitters':
This log suggests that two of the IPs that we've been tracking had hit this site 100,000 times over three months. Also present is 66.185.85.74 (not one of the IPs that we've been tracking).
Also puzzling is the fact that these three Rogers IPs, which began their visits to the site within a day or so of one another, and all begin with wc07. I think that we have to assume that they are somehow related, and that this reflects the kind of shifting back and forth that we've noticed elsewhere, but over a longer timescale for a massive amount of traffic.
Gato at Guanacos (77 = 205)
Another message board that publishes the IPs of its contributers is GuanacosEnLinea.com from El Salvador. In the fall of 2004, a certain "gato" posted several messages, logging these IPs:
- 9/28/2004 3:26:57 PM -- 66.185.84.77
- 10/8/2004 6:39:10 PM -- 66.185.84.77
- 10/10/2004 7:24:11 AM -- 66.185.84.205
The shift from x.x.x.77 to x.x.x.205 is typical of what we've seen of Rogers IPs in this period.
Pete C at e-filler.ca (77 = 209)
Another message board that shows both a poster's chosen handle and the underlying IP is E-Filler.ca, where users post comments on recent events.
The comments of a certain "Pete C" in late 2004 and early 2005 perhaps connect 77 and 209.
At this thread on Nov. 18, 2004 he posted from 66.185.84.209.
In a comment of Jan. 5, 2005, however, his IP was 66.185.84.77, which it was on Jan. 14 and Jan. 16, too.
The comments of a certain "Pete C" in late 2004 and early 2005 perhaps connect 77 and 209.
At this thread on Nov. 18, 2004 he posted from 66.185.84.209.
In a comment of Jan. 5, 2005, however, his IP was 66.185.84.77, which it was on Jan. 14 and Jan. 16, too.
Robbie McBride at RPM Factor (76 = 77)
Message boards that post both names and handles of visitors have provided interesting examples of the fluidity of Rogers' IPs in the 66.185.84.xxx-range.
Another example of this is the postings of a certain "Robbie McBride" on a message board called RPM Factor Babbler. Most of his postings from mid-2004 come from 66.185.84.76 and 66.185.84.77. Especially noteworthy are these:
Another example of this is the postings of a certain "Robbie McBride" on a message board called RPM Factor Babbler. Most of his postings from mid-2004 come from 66.185.84.76 and 66.185.84.77. Especially noteworthy are these:
- 66.185.84.77 June 23 2004 at 5:48 PM
- 66.185.84.76 June 23 2004 at 5:58 PM
Jiya on Kkusum (70 = 77)
At a message board on the Indian telvision show Kkusum we have entries from a certain Jiya:
- Sunday, September 19, 02:14:06am -- 66.185.84.70
- Sunday, September 19, 02:14:43am -- 66.185.84.77
Thursday, March 27, 2008
66.185.84.204 arranges for March break, 2004
On Nov. 12, 2003, an inquiry was sent to www.florida-discount-travel.com about the Sheraton Lucaya. The request was for March 11 - 13th of the following year:
The log records the inquirer's name ("Marg *****"), email ("marg*****@rogers.com"), and phone number "905 ***-****". (I redact these out of respect for the privacy of the individual; if you go to the site, you can see it for yourself.)
The email address and phone number (which is a land line in Aurora, Ontario, according to www.411.ca) can be confirmed.
Googling the email shows that this woman is the president of an association of time-share owners in Maine; the email and phone number are the same as in the florida-discount-travel log. See the graphic on the right (again, out of respect for this person's privacy I obliterate the names and phone numbers -- but a quick google can confirm the details for any doubting Thomas.
The date, Nov. 12, 2003, is highly significant, for according to the testimony of Bernard Klatt, the same IP was used by Richard Warman to access the White Supremacist site, freedomsite.org, on November 11th (the day before Marg did), but before the 15th and 23rd.
- We have two parties. One party has 2 adults and 2 children under 12. the other party has 1 adults 1 child
The log records the inquirer's name ("Marg *****"), email ("marg*****@rogers.com"), and phone number "905 ***-****". (I redact these out of respect for the privacy of the individual; if you go to the site, you can see it for yourself.)
The email address and phone number (which is a land line in Aurora, Ontario, according to www.411.ca) can be confirmed.
Googling the email shows that this woman is the president of an association of time-share owners in Maine; the email and phone number are the same as in the florida-discount-travel log. See the graphic on the right (again, out of respect for this person's privacy I obliterate the names and phone numbers -- but a quick google can confirm the details for any doubting Thomas.The date, Nov. 12, 2003, is highly significant, for according to the testimony of Bernard Klatt, the same IP was used by Richard Warman to access the White Supremacist site, freedomsite.org, on November 11th (the day before Marg did), but before the 15th and 23rd.
Wednesday, March 26, 2008
waterloo student on treasurer traders (203 = 208 = 79)
Another interesting example of the impermanence of Rogers IPs is found in the posts of "fairplayer" at factnet.org, a discussion board dedicated to exposing various kinds of chicanery. Fairplayer was involved in some threads concerning Treasure Traders International, which is apparently a mail-order gemstone company.
Here are a list of his posts to that board in the last two months of 2004:
| November 04, 2004- 12:41 am: | 66.185.84.203 |
| November 05, 2004 - 12:48 am: | 66.185.84.203 |
| November 29, 2004 - 10:08 am: | 129.97.83.155* |
| November 29, 2004 - 12:04 pm: | 66.185.84.208 |
| December 03, 2004 - 11:59 am: | 129.97.22.32* |
| December 07, 2004 - 11:38 pm: | 66.185.84.79 |
| December 10, 2004- 8:29 pm: | 129.97.83.240* |
Labels:
66.185.84.203,
66.185.84.208,
66.185.84.79,
Rogers
At Zodiackiller.com (208 = 203)
A handful of edits by a certain "Mike J. Doe" to a discussion board dedicated to the Zodiac Killer at www.zodiackiller.com again illustrate the fluidity of Rogers' IPs:
- Wednesday, June 18, 2003 - 11:26 am: 66.185.84.208
- Sunday, June 22, 2003 - 01:09 pm: 66.185.84.208
- Wednesday, June 25, 2003 - 11:25 pm: 66.185.84.208
- Friday, July 04, 2003 - 11:47 am: 66.185.84.203
- Friday, July 04, 2003 - 11:37 pm: 66.185.84.208
University of California dreaming (or 68=71=72=74=76=77=78=81=197=198=199=200=204)?
It will surprise no one that a site like that of Earth Sciences at the University of California at Irvine attracts a lot of traffic -- almost 70,000 different IPs visited there in the fall of 2003, and these are recorded in the logs linked to below. Among them are some of the Rogers IPs that we have been tracking in other posts: that is, those with the numbers 66.185.84.xxx (see the summary thread, here).
Extracting these IPs from the log of September 2003 yields the following list:
| hits | files | kbytes | visits | IP |
|---|---|---|---|---|
| 3 | 3 | 155 | 1 | 66.185.84.68 |
| 73 | 70 | 1972 | 7 | 66.185.84.71 |
| 44 | 44 | 584 | 4 | 66.185.84.72 |
| 4 | 4 | 206 | 2 | 66.185.84.76 |
| 1 | 1 | 24 | 0 | 66.185.84.196 |
| 2 | 2 | 59 | 0 | 66.185.84.198 |
| 86 | 80 | 1558 | 5 | 66.185.84.199 |
| 43 | 43 | 841 | 5 | 66.185.84.200 |
| 1 | 1 | 1 | 0 | 66.185.84.201 |
| 1 | 1 | 54 | 1 | 66.185.84.204 |
| 26 | 26 | 635 | 2 | 66.185.84.209 |
The logs for October 2003 provide a similar group of IPs:
| hits | files | kbytes | visits | IP |
|---|---|---|---|---|
| 1 | 1 | 54 | 1 | 66.185.84.68 |
| 194 | 165 | 4526 | 17 | 66.185.84.71 |
| 73 | 72 | 1773 | 6 | 66.185.84.72 |
| 1 | 1 | 24 | 0 | 66.185.84.74 |
| 19 | 19 | 3432 | 2 | 66.185.84.76 |
| 1 | 1 | 12 | 1 | 66.185.84.77 |
| 1 | 1 | 24 | 0 | 66.185.84.78 |
| 22 | 13 | 156 | 3 | 66.185.84.81 |
| 12 | 12 | 120 | 2 | 66.185.84.197 |
| 2 | 2 | 107 | 1 | 66.185.84.198 |
| 168 | 152 | 2265 | 12 | 66.185.84.199 |
| 48 | 48 | 709 | 7 | 66.185.84.200 |
| 6 | 6 | 80 | 1 | 66.185.84.204 |
| hits | files | kbytes | visits | IP |
|---|---|---|---|---|
| 9 | 9 | 328 | 1 | 66.185.84.68 |
| 2 | 2 | 180 | 1 | 66.185.84.69 |
| 7 | 4 | 29 | 1 | 66.185.84.70 |
| 193 | 167 | 3344 | 16 | 66.185.84.71 |
| 69 | 68 | 1657 | 8 | 66.185.84.72 |
| 14 | 6 | 130 | 5 | 66.185.84.76 |
| 1 | 0 | 0 | 0 | 66.185.84.77 |
| 1 | 0 | 0 | 0 | 66.185.84.78 |
| 1 | 1 | 44 | 0 | 66.185.84.79 |
| 11 | 11 | 290 | 0 | 66.185.84.80 |
| 25 | 23 | 642 | 2 | 66.185.84.81 |
| 247 | 230 | 4095 | 11 | 66.185.84.199 |
| 22 | 22 | 441 | 3 | 66.185.84.200 |
| 1 | 1 | 80 | 0 | 66.185.84.201 |
| 1 | 1 | 80 | 0 | 66.185.84.202 |
| 24 | 23 | 147 | 4 | 66.185.84.204 |
| 1 | 1 | 24 | 0 | 66.185.84.208 |
| 5 | 5 | 558 | 1 | 66.185.84.209 |
And December, 2003:
In all, there are twenty-two IPs listed in these months. How many users is this? Less than 22, presumably -- especially given the number of singletons in the "hits" and zeros in "visits".| hits | files | kbytes | visits | IP |
|---|---|---|---|---|
| 73 | 69 | 645 | 5 | 66.185.84.71 |
| 12 | 12 | 228 | 0 | 66.185.84.72 |
| 4 | 4 | 198 | 2 | 66.185.84.76 |
| 1 | 1 | 24 | 0 | 66.185.84.78 |
| 1 | 1 | 24 | 0 | 66.185.84.79 |
| 1 | 0 | 0 | 1 | 66.185.84.81 |
| 48 | 47 | 1774 | 7 | 66.185.84.199 |
| 32 | 32 | 783 | 2 | 66.185.84.200 |
| 14 | 14 | 509 | 1 | 66.185.84.204 |
| 22 | 22 | 495 | 1 | 66.185.84.208 |
Monday, March 24, 2008
studying at Waterloo (202 = 204 = 206 = 208 = 209)
An interesting sample of how oddly Rogers IP address can sometimes operate comes from a log of an instruction site from the University of Waterloo, here. As you can see, the log covers 24 hours, beginning a few minutes after midnight on 29 April, 2004. There are 1420 entries from 138 IPs; 268 of the log entries come from some of the Rogers IPs that we have been following: 263 hits from 66.185.84.202; two from 66.185.84.204; and one each from 66.185.84.206, 66.185.84.208, and 66.185.84.209.
As I said, almost all the posts are from x.x.x.202. But the five instances where there is a handoff to other Rogers IPs are interesting. Here they are, extracted with their immediate context, and excluding all non-Rogers IPs:
Hat-tip, Nbob in BCL's comments.
As I said, almost all the posts are from x.x.x.202. But the five instances where there is a handoff to other Rogers IPs are interesting. Here they are, extracted with their immediate context, and excluding all non-Rogers IPs:
| 1 | 66.185.84.202 | 04/29/04 11:12 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 8882 |
|---|---|---|---|
| 66.185.84.209 | 04/29/04 11:13 | "GET /cgi-bin/geniq/biology/272b/final04.iq HTTP/1.1" 200 11083 | |
| 66.185.84.202 | 04/29/04 11:16 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 9458 | |
| --------------------- | |||
| 2 | 66.185.84.202 | 04/29/04 16:01 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 9471 |
| 66.185.84.206 | 04/29/04 16:01 | "GET /cgi-bin/geniq/biology/272b/final04.iq HTTP/1.1" 200 11069 | |
| 66.185.84.202 | 04/29/04 16:01 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 9470 | |
| --------------------- | |||
| 3 | 66.185.84.202 | 04/29/04 17:18 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 9468 |
| 66.185.84.208 | 04/29/04 18:00 | "GET /cgi-bin/geniq/biology/272b/final04.iq HTTP/1.1" 200 11083 | |
| 66.185.84.202 | 04/29/04 18:02 | "GET /cgi-bin/geniq/biology/272b/final04.iq HTTP/1.1" 200 11076 | |
| --------------------- | |||
| 4 | 66.185.84.202 | 04/29/04 22:24 | "POST /cgi-bin/iq/biology/272b/quiz1.iq HTTP/1.1" 200 7349 |
| 66.185.84.204 | 04/29/04 22:25 | "GET /cgi-bin/geniq/biology/272b/final04.iq HTTP/1.1" 200 11069 | |
| 66.185.84.202 | 04/29/04 22:25 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 12661 | |
| --------------------- | |||
| 5 | 66.185.84.202 | 04/29/04 22:49 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 9463 |
| 66.185.84.204 | 04/29/04 22:51 | "GET /cgi-bin/geniq/biology/272b/final04.iq HTTP/1.1" 200 11076 | |
| 66.185.84.202 | 04/29/04 22:51 | "POST /cgi-bin/iq/biology/272b/final04.iq HTTP/1.1" 200 4035 | |
The series again illustrates the fluid nature of Rogers IPs. Potentially more interesting, however, is to compare this log with the description here, where we again see shifting IPs between "getting" and "posting".
Hat-tip, Nbob in BCL's comments.
Sunday, March 23, 2008
Thomas the Tank Engine IV: or how 206 = 208
We have already noted the edits made by a Rogers customer to the wikipedia articles related to Thomas the Tank Engine (see here, here, here). At about the same time, the same editor (one assumes) was responsible for a number of edits of the series' founder, Britt Allcroft. The first eight edits of the article's history can be seen here:| 19:10, 31 December 2003 | 66.185.84.208 (Talk) | |
| 21:42, 27 December 2003 | 66.185.84.208 (Talk) | |
| 21:31, 27 December 2003 | 66.185.84.208 (Talk) | |
| (diff) | 21:31, 11 November 2003 | 66.185.84.208 (Talk) |
| (diff) | 06:38, 11 November 2003 | Jimfbleak (Talk | contribs) m (it's-->its) |
| (diff) | 00:46, 11 November 2003 | 66.185.84.208 (Talk) |
| (diff) | 00:45, 11 November 2003 | Angela (Talk | contribs) m (fmt) |
| (diff) | 00:44, 11 November 2003 | 66.185.84.206 (Talk) |
manual of style. Within another minute, the original editor returns, but now as x.x.x.208, which he or she still had (or perhaps had again) when they returned to edit the article six weeks later.
Labels:
66.185.84.206,
66.185.84.208,
quick change,
Rogers
Ringo, Ringo, Ringo! (Or, 208 = 207 = 199)
We have been seeing that Rogers IPs could change unpredictably even while its customers were surfing. Consider the article of Ringo Starr. You can see part of its history from November 2003, here:
| (diff) | 14:22, 16 November 2003 | 66.185.84.199 |
| (diff) | 14:15, 16 November 2003 | 66.185.84.208 |
| (diff) | 14:14, 16 November 2003 | 66.185.84.207 |
| (diff) | 21:23, 14 November 2003 | 66.185.84.208 |
| (diff) | 21:22, 14 November 2003 | 66.185.84.208 |
| (diff) | 21:22, 14 November 2003 | 66.185.84.208 |
| (diff) | 21:22, 14 November 2003 | 66.185.84.208 |
| (diff) | 21:21, 14 November 2003 | 66.185.84.208 |
| (diff) | 21:17, 14 November 2003 | 66.185.84.208 |
(In the next few months, however, this editor returns, but seems only to have been allocated x.x.x.208: see here.)
Labels:
66.185.84.199,
66.185.84.207,
66.185.84.208,
quick change,
Rogers
Wednesday, March 19, 2008
I don't, I don't, I don't: why same-sex marriage does not necessarily lead to legalized polygamy
Michael Coren has many virtues that I find admirable: he is intelligent, articulate, and--given his religious convictions--surprisingly independent in his thinking. Despite this he sometimes takes bizarre positions. Take, for example, his call to nuke Iran in 2006. One shakes one's head.
A few days ago, he again went a bit astray in a column that revisited same-sex marriage and argued that the decision will inevitably lead to the legalization of polygamy. Coren provided a convenient summary for his case:
As far as I know, however, polygamy is not, a requirement of any religion. Mormonism abandoned it long ago, and although conservative Islam allows men to take up to four wives, it does not require it and never has. (In fact, it is relatively rare even in those countries where it is legal, and Islam doesn't even encourage it: see here and here).
A few days ago, he again went a bit astray in a column that revisited same-sex marriage and argued that the decision will inevitably lead to the legalization of polygamy. Coren provided a convenient summary for his case:
And thus the inevitable. I predict that polygamy will be legal and accepted in this country within five years. Any Charter challenge in support of the custom would not only be backed by the revolutionary precedent of same-sex marriage redefinition but also by guaranteed freedom of religion clauses.Coren's position has a superficial logic to it: if the rules can change for one group, they can for another, and at first glance the polygamists have two avenues by which they might make their argument: freedom to marry and freedom of religion.
But constitutional law is not a vending machine into which a coin is inserted, thereby guaranteeing a tasty snack. Nor do judges overthrow existing law on a whim. Any future change will require a test-case and a legal argument.
Such was the case with the constitutional challenge that led to marriage equality. The principle at question was the equal protection of the law: that if the state issues marriage licenses, it is unconstitutional to disallow someone a marriage license because she is a lesbian, just as it would be to disallow it for a Chinese, an octogenarian, or a Catholic. Not everyone likes the argument or is persuaded by it -- but the court was convinced, parliament ultimately agreed, and the matter was legally settled, if not politically.
Such was the case with the constitutional challenge that led to marriage equality. The principle at question was the equal protection of the law: that if the state issues marriage licenses, it is unconstitutional to disallow someone a marriage license because she is a lesbian, just as it would be to disallow it for a Chinese, an octogenarian, or a Catholic. Not everyone likes the argument or is persuaded by it -- but the court was convinced, parliament ultimately agreed, and the matter was legally settled, if not politically.
How would this principle apply to polygamy? Essentially, the state limits the number of marriage licenses to one per customer. Do you want to marry someone else? First, your first marriage must be dissolved. At the moment the law is applied to all equally--Catholics, Muslims, Mormons, and atheists are all allowed only to have one spouse at a time. So, too, gays and lesbians. A polygamist can no more acquire a second wife under this principle than he could could have more than one SIN number. There is no avenue for a constitutional challenge here -- at least that I can see.
Coren supposes that the charter principle of freedom of religion might also be invoked. This is less than obvious, however. Freedom of religion prevents the state requiring someone to perform an action that their religion forbids, or forbidding someone from doing something that their religion requires.
Coren supposes that the charter principle of freedom of religion might also be invoked. This is less than obvious, however. Freedom of religion prevents the state requiring someone to perform an action that their religion forbids, or forbidding someone from doing something that their religion requires.
As far as I know, however, polygamy is not, a requirement of any religion. Mormonism abandoned it long ago, and although conservative Islam allows men to take up to four wives, it does not require it and never has. (In fact, it is relatively rare even in those countries where it is legal, and Islam doesn't even encourage it: see here and here).
Now, even a superficial consideration of our legal system and various religions' moral systems shows that they operate in different registers. There are many behaviours that religions forbid but the state allows (consumption of alcohol, blood transfusions, divorce); there are behaviours that the state forbids or regulates that religions are silent about (speed limits, the structure of legal trusts, the filing deadline of one's taxes).
In light of this, a successful constitutional challenge to legalize polygamy seems unlikely to me -- there is no obvious legal avenue for a challenge. So, unlike Coren, I doubt whether multiple "I do"s are in any of our futures.
Sunday, March 16, 2008
Vampire Chronicles (72 = 81?)
Wikipedia attracts The wikipedia article on Ann Rice's series, The Vampire Chronicles. Here are a few edits from its edit history:
- (diff) 20:28, 4 December 2004 66.185.84.81 (Talk) (→''Vittorio, the Vampire'')
(diff) 20:27, 4 December 2004 66.185.84.72 (Talk) (→''Blood and Gold'')
(diff) 20:26, 4 December 2004 66.185.84.81 (Talk) (→''Blood and Gold'')
If you click on the diffs, you can see that the edits are vandalism, with x.x.x.81 "STEPHEN S IS A BIG POO FACE YOU EATS POO", x.x.x.72 erasing it, and then x.x.x.81 re-inserting it.
Given the fluidity of the IPs, it seems x.x.x.72 is erasing his own handiwork.
The Inklings (or 78 = 81)
The article on theologian C.S. Lewis shows another interesting example of IP-shifting. Three edits were made to the external links section within a few minutes of one another. (For the edit history, see here)
| (diff) | 03:53, 21 November 2004 | 66.185.84.78 |
| (diff) | 03:51, 21 November 2004 | 66.185.84.81 |
| (diff) | 03:50, 21 November 2004 | 66.185.84.81 |
| (diff) | 03:50, 21 November 2004 | 66.185.84.81 |
Saturday, March 08, 2008
Fluidity of Rogers IPs in 2003/4 (Summary thread)
Note. More complete, more easily accessible version of this data can be seen in this later post.
- 66.185.84.68 (Nov. '04)
- 66.185.84.72 (Nov. '04, Dec. '04)
- 66.185.84.73 (July '03)
- 66.185.84.74 (Oct. '03)
- 66.185.84.75 (Dec. '04)
- 66.185.84.78 (July '03, Nov. '03, Jan. '04, Feb. '04, Aug. '04, Nov. '04)
- 66.185.84.79 (Feb. '04, Nov. '04)
- 66.185.84.80 (Oct. '03, Nov. '03, Jan. '04, Aug. '04, Oct. '04)
- 66.185.84.81 (Oct. '04, Nov. '04, Nov. '04)
- 66.185.84.196 (Feb. '05)
- 66.185.84.197 (Dec. '03, Oct. '04, Feb. '05, Feb. '05, Feb. '05)
- 66.185.84.198 (Feb. '05, Feb. '05)
- 66.185.84.199 (Feb. '03, Oct. '04, Feb. '05, Feb. '05, Feb. '05)
- 66.185.84.200 (Sept. '03, Nov. '03, Feb. '05, Feb. '05)
- 66.185.84.201 (Feb. '05)
- 66.185.84.202 (Nov. '03, April '04, Oct. '04)
- 66.185.84.203 (July '03, Nov. '04, Feb. '05)
- 66.185.84.205 (Oct. '04, Feb. '05, Feb. '05)
- 66.185.84.206 (Nov. '03, Dec. '03, Jan. '04, April '04, Feb. '05, Feb. '05 )
- 66.185.84.207 (Feb. '03, Feb. '05)
- 66.185.84.208 (Feb. '03, July '03, Oct. '03, Nov. '03, Nov. '03, Jan. '04, April '04, Oct. '04, Nov. '04, Feb. '05)
- 66.185.84.209 (April '04, Feb. '05)
These reflect, of course, only the tiniest fraction of what was really happening. Every time anyone visits a webpage, the visit is logged somewhere, but very few of those logs are ever published; only a tiny fraction of internet users edit wikipedia, and only a fraction of them do so without signing in, thereby allowing us to see their IPs.
Still, the evidence that we do have makes it is fairly clear that having any one of these IPs--indeed, any Roger IP--at one moment doesn't guarantee that you have it at another. The reason, of course, is that Rogers was using these IPs as proxies for all their traffic from a specific region.
That Rogers used some of these IPs as proxies is something that we already knew. What we don't know is how large a number of Rogers subscribers was served by this pool of IPs. Dozens? Hundreds? Thousands? Tens of thousands?
That Rogers used some of these IPs as proxies is something that we already knew. What we don't know is how large a number of Rogers subscribers was served by this pool of IPs. Dozens? Hundreds? Thousands? Tens of thousands?
Updated and expanded; re-edited to make dates clearer
Wednesday, March 05, 2008
Ontario (199 = 208 = 200 = 204 = 197 = 209 = 206)
We have been seeing several examples of how quickly the IPs could change for Rogers customers. Another good example comes from the wikipedia article on Ontario. Here is the article'sedit history (again, wikipedia logs read from bottom to top):
| 16:30, 19 February 2005 | 24.235.186.61 | |
| (diff) | 02:17, 18 February 2005 | 69.197.107.164 (Talk) (→Introduction (In the begginning)) |
| (diff) | 03:27, 16 February 2005 | 66.185.84.199 (Talk) (→Introduction (In the begginning)) |
| (diff) | 03:19, 16 February 2005 | 66.185.84.208 (Talk) (→The Social Contract) |
| (diff) | 03:16, 16 February 2005 | 66.185.84.200 (Talk) (→Politics) |
| (diff) | 03:15, 16 February 2005 | 66.185.84.204 (Talk) (→Politics) |
| (diff) | 03:15, 16 February 2005 | 66.185.84.197 (Talk) (→Politics) |
| (diff) | 03:14, 16 February 2005 | 66.185.84.209 (Talk) (→Politics) |
| (diff) | 03:14, 16 February 2005 | 66.185.84.206 (Talk) (→Politics) |
| 07:13, 15 February 2005 | Earl Andrew (Talk | contribs) m (→Territorial evolution 1788-1899) |
Toddlers (203 = 199 = 205 = 197 = 198 = 201)
Another example of the fluidity of Rogers' IPs is illustrated by the short-lived wikipedia article involving toddlericon a sub-genre of Lolicon (a kind of Hentai). Its edit history (which is read from the bottom up):
| 21:36, 21 February 2005 | 66.185.84.201 |
| 01:51, 18 February 2005 | 66.185.84.201 |
| 04:20, 17 February 2005 | 66.185.84.198 |
| 04:19, 17 February 2005 | 66.185.84.197 |
| 04:03, 17 February 2005 | 66.185.84.197 |
| 04:03, 17 February 2005 | 66.185.84.205 |
| 04:02, 17 February 2005 | 66.185.84.199 |
| 04:01, 17 February 2005 | 66.185.84.203 |
Friday, February 29, 2008
Scottsonline (199 = 205 = 200; 204 = 208)
There are many details to be extracted from logs for miscellaneous websites that help illustrate the impermanent nature of Roger's IPs in the years 2003 and 2004. Below are some Rogers IPs extracted from a log for scottsonline.com. Especially, to be noted are the coloured entries.
The same point can be made about the two red entries, from four days later. The two red log entries are only 15 seconds apart, and x.x.x.204 "hits" only a single page once before disappearing and giving way to x.x.x.208. This is easiest to explain if this is one user whose IP has changed suddenly, as these IPs can be seen to do elsewhere.
Beginning with the blue entries, it is theoretically possible that four Rogers customers showed up within a few minutes of one another at 13:12:10, 13:26:30, 13:27:06, and 13:28:08 of Sept. 08, 2004. But especially with the last three log entries, it is easier to believe that this is one person, and that it is yet another example of the fluidity of the Rogers IPs, and within a minute-and-a-half, the Scottsonline customer had cycled through 66.185.84.205, -200, and 197.
IP pages hits bandwidth last visit date 66.185.84.71 2 7 124154 2004 09-02 08:29:00 66.185.84.199 1 1 1686 2004 09-08 13:12:10 66.185.84.205 1 1 1686 2004 09-08 13:26:30 66.185.84.200 4 18 112762 2004 09-08 13:27:06 66.185.84.197 26 86 4103099 2004 09-08 13:28:08 66.185.84.204 1 1 25877 2004 09-12 18:20:44 66.185.84.208 6 41 568401 2004 09-12 18:20:57 66.185.84.69 14 77 959341 2004 09-22 08:09:40 66.185.84.76 6 9 25130 2004 09-24 20:20:29 66.185.84.80 34 284 7429937 2004 09-28 14:01:20
The same point can be made about the two red entries, from four days later. The two red log entries are only 15 seconds apart, and x.x.x.204 "hits" only a single page once before disappearing and giving way to x.x.x.208. This is easiest to explain if this is one user whose IP has changed suddenly, as these IPs can be seen to do elsewhere.
Whether the other IPs reflect the same users, and whether the 'blue-user' and 'red-user' is the same person, is less clear. But given that these IPs often seem elsewhere to shift into one another, it seems highly likely not only that the red IPs and blue IPs all belong to the same user, but so, too, do the other IPs that we find here: x.x.x.69, x.x.x.76, and x.x.x.80.
Tuesday, February 26, 2008
video gaming (or, 208 = 80 = etc.)
We have seen that in 2003 and 2004 (and since), Rogers IPs bounce around quite a bit. Indeed, once one begins to look, it is not hard to find other places where the instability of Rogers' IPs can be seen. Consider the postings of a certain Necros at a message board dedicated to video-game graphics in the years 2003-2004. Each post includes not only Necros' name and message, but his IP-address, too, which allows us to detect some more IP-bouncing.
Necros' first couple dozen posts on the board are from an AOL account. Beginning in September, 2003, however, he begins to post from a series of Rogers IPs:
The IPs, with the exception of those from the U. of Toronto seem to be all Rogers (with the possible exception discussed below), and again we see the propensity of the IPs to shift. Very common are 66.185.84.208 and 66.185.84.80.
no. 348 2003/10/02 66.185.84.208 (Rogers) no. 374, 380 2003/10/19-20 63.139.3.74 (Rogers)* no. 443 2003/11/30 66.185.84.208 (Rogers) no. 460, 471 2003/12/27, 2004/01/03 63.139.106.197 (Rogers)* no. 499, 500, 532 2004/01/11, 17 66.185.84.208 (Rogers) no. 553, 560, etc. 2004/01/28 - 02/24 63.139.106.197 (Rogers)* no. 724, 729 2004/03/16, 17 66.185.84.208 (Rogers) no. 749, 756, etc., etc. 2004/03/24-05/27 69.193.41.176 (Rogers) no. 1117, 1126, etc. 2004/06/02, 06, 19, 07/15 66.185.84.208 (Rogers) no. 1214, 1225, 1238 2004/08/08, 11, 13 66.185.84.80 (Rogers) no. 1256 2004/08/17 66.185.84.208 (Rogers) no. 1265, 1274, 1292 2004/08/21, 23, 25 69.193.222.114 (Rogers) no. 1355 2004/07/07 66.185.84.208 (Rogers) no. 1398 2004/09/21 142.150.5.189 (U. of Toronto) no. 1402, 1407, etc. 2004/09/22-10/26 66.185.84.80 (Rogers) no. 1497 2004/10/21 142.150.5.189 (U. of Toronto) no. 1502 2004/10/26 142.150.5.189 (U. of Toronto) no. 1508, 1512, etc. 2004/10/30 - 11/01 66.185.84.80 (Rogers) no. 1551 2004/11/06 66.185.84.208 (Rogers) no. 1556 2004/11/11 142.150.107.117 (U. of Toronto) no. 1585 2004/11/25 142.150.107.159 (U. of Toronto) no. 1600 2004/12/12 66.185.84.74 (Rogers) no. 1616, 1620, 1624 2004/12/28-29 66.185.84.80 (Rogers)
Beginning in 2005, we can add a few more IPs. A few more posts are here
| no. 99, 100 | 2005/01/19 | 66.185.84.76 (Rogers) |
*According to ARIN: 63.139.106.197 now falls within a block that belongs to PaeTec Communications. In 2004, however, the similar IPs seem to have belonged to Rogers: see this log (search for the IP), and this one under Tue Nov 25 22:58:23 2003 , and this one under 2004/03/07 .
Labels:
66.185.84.208,
66.185.84.76,
66.185.84.80,
Rogers
Sunday, February 24, 2008
What's in a name: or, 200 = 196 = 197 = 198 = 199 = 205 = 206
We have been seeing that wikipedia histories show that Rogers' subscribers' IP addresses are not completely fixed: one can begin with one IP, shift to another, and then back within a very short space. Klatt testified that when 66.185.84.204 visited the freedomsite, the logs show shifts to 66.185.84.200 and back, and it is clear that this happened a good deal.
A good example of how much shifting could happen comes from the wikipedia article List of Biblical names. As its name implies, it is merely a long alphabetical list of characters who appeal in the bible.
Consider this section of its edit-history from February 2005. (Wikipedia logs are read from the bottom up.)
(It is clear that the user is the same -- he is engaging in what in wikipedia is called blanking-vandalism.)
A good example of how much shifting could happen comes from the wikipedia article List of Biblical names. As its name implies, it is merely a long alphabetical list of characters who appeal in the bible.Consider this section of its edit-history from February 2005. (Wikipedia logs are read from the bottom up.)
- 18:01, 14 February 2005 PFHLai (Talk | contribs) (remove {{Vprotectedsmall}})
- 03:42, 14 February 2005 PFHLai (Talk | contribs) (+ {{Vprotectedsmall}})
- 03:41, 14 February 2005 PFHLai (Talk | contribs) m (Reverted edits by 66.185.84.200 to last version by PFHLai)
- 03:37, 14 February 2005 66.185.84.200 (Talk) (→K)
- 03:36, 14 February 2005 PFHLai (Talk | contribs) (restore a previous version after vandalism by an Anon. with multiple IPs)
- 03:33, 14 February 2005 66.185.84.197 (Talk) (→J)
- 03:26, 14 February 2005 66.185.84.198 (Talk) (→I)
- 03:24, 14 February 2005 66.185.84.206 (Talk) (→H)
- 03:21, 14 February 2005 66.185.84.205 (Talk) (→G)
- 03:18, 14 February 2005 66.185.84.199 (Talk) (→E)
- 03:13, 14 February 2005 66.185.84.198 (Talk) (→D)
- 03:09, 14 February 2005 66.185.84.206 (Talk) (→C)
- 03:06, 14 February 2005 66.185.84.196 (Talk) (→B)
- 03:03, 14 February 2005 Rje (Talk | contribs) m (rv to last edit by Ihcoyc, semi-blanking)
- 03:01, 14 February 2005 66.185.84.200 (Talk) (→A)
(It is clear that the user is the same -- he is engaging in what in wikipedia is called blanking-vandalism.)
Saturday, February 23, 2008
Thomas the Tank Engine III: or how 208 = 202 = 200 = 80 = 78 = 81
We have been exploring the edits made to Wikipedia by a series of Rogers IPs in 2003 and 2004. The editor shows consistent interest in a group of articles, many of which relate to the children's program Thomas the Tank Engine.
One such article was its American spin-off Shining Time Station. Here is the edit history of its first six weeks (the logs read from the bottom):
One such article was its American spin-off Shining Time Station. Here is the edit history of its first six weeks (the logs read from the bottom):
- 14:42, 31 December 2003 66.185.84.208
20:22, 30 December 2003 66.185.84.208
20:21, 30 December 2003 66.185.84.208
20:19, 30 December 2003 66.185.84.208
23:27, 12 November 2003 Dysprosia m (fmt)
23:27, 12 November 2003 Minesweeper (fmt)
23:00, 12 November 2003 66.185.84.208
20:59, 12 November 2003 66.185.84.208
20:58, 12 November 2003 66.185.84.208
20:44, 12 November 2003 66.185.84.208
20:41, 12 November 2003 66.185.84.208
00:15, 12 November 2003 66.185.84.208
20:30, 10 November 2003 66.185.84.208
20:14, 10 November 2003 66.185.84.202 (Talk)
- 22:56, 20 November 2004 66.185.84.81
00:10, 10 November 2004 66.185.84.208
21:33, 23 October 2004 66.185.84.80
Thomas the Tank Engine II: or how 208 = 80

At the following link you can see the edit history of the wikipedia article for Salty the Diesel Engine, a minor character in the Thomas the Tank Engine series.
Salty's article was created as a 'stub' on 15 Oct. 2004 by 66.185.84.208; an attempt was made to redirect it to the main Thomas the Tank Engine page, a couple hours later. Within a day, the original editor returned and undid the redirect.
It is hard to avoid the conclusion that an editor who uses 66.185.84.208 might sometimes use 66.185.84.80.
Friday, February 22, 2008
Rammstein: or, 204 = 207
We've been looking at the fluidity of Roger's IPs in the years 2003 and 2004. Another example of this comes from late 2004, when a wikipedia used 66.185.88.204 to edit the rock group Rammstein and the song of the same name. A week later, the same editor (one assumes) returned to edit the rock group's article, and then two months later, when they had 66.185.88.207
Rick Mercer's Monday Report I: or, how 204 = 206
I pointed out here that on Sept. 5, 2003, a Rogers customer using 66.x.x.204 seems to have been temporarily rerouted through 66.x.x.200 (and perhaps back-and-forth several times). And here that on Jan. 2, 2004, one was rerouted through x.x.x.208.
On Jan. 1, 2004, someone used 66.x.x.204 to edit Rick Mercer's Monday Report. A snippit of the log for these days can be seen here, where you can see that x.x.x.208 was used Jan. 1, x.x.x.204 on Jan. 3, and yet another IP, 66.185.84.206, on Jan. 5.
Thomas the Tank Engine I: or how 204 = 208
We have already seen here that on Sept. 5, 2003, a Rogers communications customer was routed through both 66.185.84.204 and 66.185.84.200 during a short visit. Below I will point out that sometimes the x.x.x.204 user is routed through x.x.x.208.
One of the largest data set for IPs is wikipedia, since it allows its editors to choose whether or not sign in when they edit. By examining an article's history, you can see the names of editors who signed-in and the IPs of those who didn't.

Take the article Gullane Entertainment Ltd. (which redirects to Gullane Entertainment, a television production company that produces children's programming, best known for the series Thomas the Tank Engine
Now, if you click on the "history" tab above the article, you can see its editing history, where you'll see that on Jan. 2, 2004, 66.185.84.204 made a small edit to the article, replacing an internal link with an external. Only a few days earlier, however, the article was created by 66.185.84.208 and had provided all of the information in it, and within a few months 66.185.84.208 edited the article again.
Now, it is fairly clear that these two IPs are the same editor, and what this illustrates is something that several commentators in other blogs have noted. No one seems to hold these IPs long.
One of the largest data set for IPs is wikipedia, since it allows its editors to choose whether or not sign in when they edit. By examining an article's history, you can see the names of editors who signed-in and the IPs of those who didn't.
Take the article Gullane Entertainment Ltd. (which redirects to Gullane Entertainment, a television production company that produces children's programming, best known for the series Thomas the Tank Engine
Now, if you click on the "history" tab above the article, you can see its editing history, where you'll see that on Jan. 2, 2004, 66.185.84.204 made a small edit to the article, replacing an internal link with an external. Only a few days earlier, however, the article was created by 66.185.84.208 and had provided all of the information in it, and within a few months 66.185.84.208 edited the article again.
Now, it is fairly clear that these two IPs are the same editor, and what this illustrates is something that several commentators in other blogs have noted. No one seems to hold these IPs long.
Klatt's testimony, or sometimes 204 = 200
Here are pages 1636-8 of Richard Warman and the Canadian Human Rights Tribunal v. Marc Lemire (T1073/5405 vol. 9) of Feb. 8, 2007. In it, Bernard Klatt is testifying about the logs of Lemire's site.
The point to note is that during his visit to the site on Sept. 5, 2003, the user "90sareover" showed up in Lemire's logs both as 66.185.84.204 and as 66.185.84.200, although only visiting the site briefly. Klatt is unable to explain this, but it is a phenomenon that is worth keeping in mind, since if 90sAREover had hit return in one of the moments when his traffic was being channeled through 66.185.84.200, we'd not be having this discussion.
The point to note is that during his visit to the site on Sept. 5, 2003, the user "90sareover" showed up in Lemire's logs both as 66.185.84.204 and as 66.185.84.200, although only visiting the site briefly. Klatt is unable to explain this, but it is a phenomenon that is worth keeping in mind, since if 90sAREover had hit return in one of the moments when his traffic was being channeled through 66.185.84.200, we'd not be having this discussion.
Saturday, February 16, 2008
Tuesday, January 15, 2008
Sunday, January 13, 2008
Subscribe to:
Posts (Atom)
