Wikipedia and pedophilia

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

How Wikipedia handles the pedophilia and pedophiles is a source of controversy.

Policy

In April 2010, when Wikipedia was already nine years old, the Wikipedians began codifying their "Child protection" policy.[1] Previously, custom and convention dictated Wikipedia's response to pedophilia activism. As initially written, dealing with pedophiles and their apologists was left in the hands of the Wikipedia Arbitration Committee (ArbCom),[1] but by December 2015, ArbCom was no longer involved in that role;[2] instead, the Wikimedia Foundation's legal team assumed full responsibility for dealing with pedophiles and their apologists.[3]

As currently written, Wikipedia possessed a zero tolerance policy against pedophiles.[3]

However, the policy also forces all whistler-blowers to report their findings privately through Email instead of allowing findings to be shared, scrutinized, and refined publicly. The policy threatens any whistler-blower who publishes their findings in public with a ban.[4]

Behaviors and patterns of pedophiles and apologists on Wikipedia

Pedophile-exposing website Wikisposure documented organized attempts by pedophiles and their apologists to influence Wikipedia.[5] Wikisposure noted that pedophiles and their apologists often used pedophile-related message-boards such as Boychat to issue calls for action and/or participation, along with advice.[6] They even advised pedophiles to use sockpuppets and "alter egos".[7] Wikipedia critic and Wikipediocracy blogger Delicious carbuncle noted that pedophile editor "Ospinad" likely became "For An Angel" in order to work with a clean slate.[8] Leaked Emails also show that pedophiles and their apologists organize behind the scene through private correspondence.[9]

Incidents

Before its closure, Wikisposure exposed over thirty pedophiles involved in Wikipedia.[10] The Wikipedia criticism blog and forum Wikipediocracy also exposed several pedophiles.[8][11][12][13][14]

At least three Wikipedians, "Meco"[13], "Beta_M",[15][16] and WayneRay[14][17] are known to have possessed and/or distributed child photography.

Response time

Since Wikipedians are forbidden from reporting cases of pedophilia publicly,[4] there are not any public logs from which to calculate the average response time to cases reported.

In October 2011, Wikipedia critic and Wikipediocracy blogger "Delicious carbuncle" reported pedophile "Crakkerjakk" to ArbCom, yet Crakkerjakk was not blocked. Instead, Crakkerjakk deleted evidence of pedophilia from his online profiles, suggesting that ArbCom merely sent a message to Crakkerjakk. In February 2013, Delicious carbuncle submitted a blog entry to Wikipediocracy describing Crakkerjakk's online activities and the lack of response from ArbCom.[12] Crakkerjakk would not be banned from Wikipedia until June 2013.[18]

In late 2012, Wikipedia critic and Wikipediocracy blogger "Delicious carbuncle" voiced disappointment after ArbCom failed to adopt any measures against "For An Angel", the pedophile that Delicious carbuncle had complained about four weeks prior. Delicious carbuncle notes that even placing a message on Jimbo Wales' talk page failed to produce an adequate response.[11][19]

In fact, the only person who reacted was "For An Angel", who had Wikipedia administrator Metropolitan90 delete his userpage, effectively hiding the evidence.[20] Metropolitan90 threatened to "pursue appropriate remedies" against Delicious carbuncle, the whistler-blower, if Delicious carbuncle were to expose Metropolitan90 as an admin who failed to take action against "For An Angel".[21]

"For An Angel" was only banned from Wikipedia after Delicious carbuncle criticized Wikipedia for not doing anything.[22]

Erik Möller

In May 2008, Valleywag blogger Owen Thomas criticized Erik Möller's views on pedophilia. He noted that Möller once wrote, What is my position on pedophilia, then? It's really simple. If the child doesn't want it, is neutral or ambiguous, it's inappropriate, in an essay submitted to Kuro5hin, and he noted that Möller's website "humanist.de" once possessed an obscene photo that was later removed.[23] Erik Möller was Deputy Director of the Wikimedia Foundation from 2008 to 2015.

Zanthalon

In 2004, infamous pedophile Lindsay Ashford (born David Alway)[24] joined Wikipedia as "Zanthalon".[25] Ashford operated pro-pedophilia websites[24] and was heavily involved in attempts to influence Wikipedia and its readers.[26] In March 2007, Wikipedia Arbitrator Fred Bauder banned Lindsay Ashford from Wikipedia. However, Ashford was banned for activities damaging to the reputation of Wikipedia instead of being banned as a matter of principle.[27] Bauder allowed pedophiles to remain as long as their activities could be covered up and did not risk damaging Wikipedia's reputation (see below).

Participants blocked for not tolerating pedophiles

In February 2006, Wikipedia contributors "Carbonite",[28] "El C",[29] and "Giano"[30] advocated a zero tolerance policy against pedophiles, and Wikipedia administrator "Carnildo" banned the three of them for "hate speech" against pedophiles.[31][32] Other administrators later unbanned Carbonite,[33] El C,[34] and Giano,[35] and Wikipedia co-founder Jimmy Wales revoked Carnildo's administrative privileges.[36] However, for Carbonite, the damage was done; he quit Wikipedia soon afterwards,[37] a casualty of radical egalitarianism.

In September 2006, Carnildo's administrative privileges were restored.[38]

2007 ArbCom cover-ups

In February 2006, Pankkake added text to his userpage that read:

<templatestyles src="Template:Blockquote/styles.css" />

I think being sexually attracted to prepubescent or adolescent children is not a crime. Child pornography not involving real children (drawings, stories...) should not be prohibited.

— Pankkake, Wikipedia[39]

In March 2006, this text was brought up during an argument between pankkake and members of Encyclopaedia Metallum's forum.[40]

In December 2006, "Gwaur" added an userbox onto his userbox that contained the pedophilic "Girllove logo" ("GLogo.png")[41] and the text This user is a pedophile.[42]

In March 2007, Wikipedia Arbitrator Fred Bauder removed evidence of Pankkake's pedophilia apologia and Gwaur's pedophilia from their userpages.[43][44][45]

In December 2006, David Weiss Richardson joined Wikipedia as "Dfpc".[46] Later that month, Richardson created a second account called "Davidwr".[47] Pedophile-exposing website Wikisposure noted "d_fpc" and "davidwr" as handles that Richardson commonly used.[48] The "fpc" in "d_fpc" possibly referred to the "Free Paed Cooperative".[49] Richardson used the "Dfpc" account to engage in pedophile activism,[50] while using the "Davidwr" account for activity not related to pedophilia.[51]

In May 2007, Richardson created yet another account; this time called "LoneStarDavid".[52] Later that month, Wikipedia admin Sean William deleted a discussion concerning "Child pornography search terms" and blocked Richardson's "Dfpc" as a "single purpose account".[53] A different Wikipedia admin, David Gerard, deleted the "Child pornography search terms" page and blocked Richardson's "Davidwr" and "LoneStarDavid" accounts while claiming ArbCom jurisdiction over the blocks.[54]

In June, Richardson attempted to have his "Davidwr" and "Dfpc" accounts unblocked.[55][56] Two admins, Pgk and Jeffrey O. Gustafson, rejected Richardson's public unblock requests.[57][58]

Later that same month, Richardson, posting as "Dfpc", indicated that he had been attempting to contact ArbCom.[59] By July, Richardson was negotiating his eventual unbanning with Wikipedia Arbitrators Fred Bauder and FloNight through private correspondence.[60] In July, Richardson, posting as "LoneStarDavid", indicated that he had received permission (via private correspondence) to submit draft entries to Wikipedia through his talk page.[61] Several days later, Fred Bauder unblocked Richardson's "Davidwr" account while keeping it disassociated from the activities of the "Dfpc" account.[62][60]

In December 2008, Richardson asked "Balloonman" to examine the record of his "Davidwr" in preparation of a bid to becoming a Wikipedia administrator, presumably without telling Balloonman about his "Dfpc" account.[63] Balloonman agreed to nominate Davidwr for adminship on the condition that Richardson disclose whatever it is caused the "Davidwr" account to be blocked in May 2007.[64]

However, Richardson was not prepared to expose his past. In February 2009, Richardson, posting as "Dfpc", published a message on the talk page of his "Dfpc" account stating that the Wikipedia administration had permitted him to return, but he did not disclose that "Dfpc" was now "Davidwr".[65] A couple of days later, Richardson, posting as "Davidwr", attempted to gauge how much time must past before the the Wikipedians would not ask questions about a past event.[66][67] In March, he abandoned his bid to become an administrator.[68]

In January 2010, Arbitrator "Cool Hand Luke" brought up the Davidwr-Dfpc incident on the ArbCom mailing list. He noted that since Richardson's "pedo advocacy" was conducted on "an edit-segregated account" [Dfpc], the "Davidwr" accounts connection to pedophilia activism was not "apparent".[60] In other words, Fred Bauder, FloNight, and the 2007 ArbCom had effectively covered up Davidwr's connection to pedophilia activism.

Cool Hand Luke also suggested revisiting Davidwr-Dfpc incident.[60]

From: (Cool Hand Luke)
Date: Sat, 30 Jan 2010 17:02:58 -0600
Subject: [arbcom-l] User:Haiduc

I support siteban, but we need to work out what the rule is. We
tacitly endorsed the continued editing of Davidwr last year. He came
to our awareness when he asked permission for topic sock[puppet]s, fearful
that editing on local topics could out him. We denied this
arrangement, so he continued under his previous deal. He was unblocked
a couple of years ago when Fred [Bauder] and FloNight negotiated his return
with an unspoken topic ban. Lately, we're not allowing a topic ban
solutions at all. Given the risk of grooming, I think this makes
sense.

The only distinguishing feature of Davidwr is that his pedo advocacy
was done on an edit-segregated account [Dfpc], and the Davidwr account was
swept up by Checkuser. Therefore, there's no apparent evidence of
advocacy, but does it make sense to rely on this odd fact? We should
either revisit his account, or accept it as a historical accident.

Frank

ArbCom presumably did revisit the incident and contacted Richardson, since within 24 hours of Cool Hand Luke sending his Email to the ArbCom mailing list, Richardson, posting as "Dfpc", publicly repudiated his past stance of pedophilia on the talk page of his "Dfpc". However, the message that Richardson publish did not disclose the fact that "Dfpc" was continuing to edit Wikipedia as "Davidwr".[69] This resulted in edit warring

In July 2011, MaliceAforethought leaked Cool Hand Luke's Email regarding the Davidwr-Dfpc incident[60] and Emails about Fred Bauder covering up Pankkake's pedophilia apologia and Gwaur's pedophilia.[45]

Lolicons and sexualized drawings of children

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

In June 2007, there was an effort, perhaps coordinated on an imageboard, to replace the image used on Wikipedia's Lolicon entry with a more explicit image.[70] Eventually, artist Kohikki[71] drew Wikipedia animesque personification as a lolicon and uploaded it to Wikipedia and then Wikimedia Commons.[72][73][74] This resulted in an edit war lasting several days,[75] which was accompanied by much debate,[76][77] and the the article had to be locked several times.[78] Wikipedia co-founder Jimmy Wales intervened to deleted the Wikipe-tan lolicon images.[79]

In April 2010, Wikipedia's other co-founder Larry Sanger, who had ceased working for Wikimedia at the time, reported the presence of lolicons and drawing depicting child abuse on Wikimedia Commons to the FBI.[80] The Wikipedians became hostile to Sanger due to the incident. In May, Sanger criticized Wikipedia for not documenting the incident,[81][82] and Wikipedia administrator Rodhullandemu responded by attempting to ban Sanger.[83] In March 2011, the Wikipedians finally did document the incident, but they misconstrued Sanger's claims.[84]

Beta_M and Wikimedia Commons' resistance to the banning of pedophiles

In December 1999, Russian anarchist Vladimir Mozhenkov, a.k.a. "VolodyA! V Anarhist" and "Beta_M", was arrested in Montana for using a Carroll College computer to distribute child pornography. He pleaded guilty in August 2000[16] and was imprisoned until October 2002.[15] In 2003, Mozhenkov wrote of his arrest and imprisonment on an anarchist mailing list.[85]

<templatestyles src="Template:Blockquote/styles.css" />

P.S. I've spent 2 years and nine months in prison for posession of child porn. And the fact that there was none of it on my computer when it was confiscated didn't matter; trust me when you are arrested for something like that you need a miracle not to be found guilty (unless you are a judge or a cop).

— VolodyA! V Anarhist, Spoon Collective[85]

In 2004, Mozhenkov joined Wikipedia as "Beta_m" and created an article on Carroll College,[86] the very college that he was attending at the time of his 1999 arrest.[16]

In February 2005, Mozhenkov donated to the Wikimedia Foundation, writing For not deleting at least some articles as his justification, and Wikimedia CFO Daniel Mayer listed Mozhenkov's comment as one of his favorite during the 2005 Wikimedia fundraising drive.[87]

In June 2006, Mozhenkov stated that he to the large extent support[s] childlove [pedophilia] movement.[88]

In June 2009, Mozhenkov complained about Ukraine passing stricter child pornography laws and made a vague reference to his two years and nine months (nearly three years) in prison for possessing child pornography.[89]

<templatestyles src="Template:Blockquote/styles.css" />

My response: And after this people will still be telling me that it is those who watch pornography who abuse somebody. You can have "limited freedom" for 3 years for looking at people fucking.

— VolodyA! V Anarhist, London Anarchist Forum[89]

In February 2006, Mozhenkov ceased using his "Beta_m" account;[90] however, in January 2010, Mozhenkov returned to Wikimedia as "Beta_M".[91] Mozhenkov became active in Wikimedia Commons deletion discussions and voted to keep depictions of child pornography and lolicons.[92] Mozhenkov voted to keep "Hotel_Karada.png" and "Simulated_Forced_Fellatio_in_Bondage_Scenario.png".[93][94] Both photos were found to have originated from a child porn website and deleted.[95][96]

In March 2012, Wikipedia critic "tarantino" uncovered Mozhenkov's past and shared on it on Wikipedia criticism forum The Wikipedia Review.[15] Wikipedia and Commons administrator "Geni" then banned Mozhenkov from both Wikipedia and Commons.[97][98]

However, Commons admin "Dcoetzee" unbanned Mozhenkov's account on Commons,[98] dismissed the evidence connecting Mozhenkov to pedophilia, and promised to "admonish" Geni for "rash actions".[99] After Geni defended his actions, Mozhenkov accused Geni of "harassment" and demanded action against Geni and the closure and censoring of discussions related to the matter.[100] Mozhenkov also began gathering individuals he knew would be sympathetic to his cause.[101][102]

This resulted in a discussion that pitted predominant members of the Commons community against members of The Wikipedia Review and its spiritual successor Wikipediocracy. The Commons community became extremely defensive and retaliatory in order to protect Mozhenkov and combat the critics from The Wikipedia Review and Wikipediocracy:

  • Commons admins "Mattbuck" and "PierreSelim" blocked critic "Peter Damian" for "harassing" (confronting, actually) Mozhenkov.[103][104]
  • Commons admins "Tiptoety", "Mattbuck", and "A.Savin" blocked critic "Fred the Oyster" for "attacking" Mozhenkov.[105][106]
  • Commons admin "PierreSelim" dismissed the facts and concerns brought up against Mozhenkov as a "witch hunt" and demanded action against critics "Michaeldsuarez", "Delicious carbuncle", and "Tarc".[107][108]
  • Commons admin "Saibo" demand the blocking of critics "Mistress Selina Kyle" and "SilkTork" for "slandering" Mozhenkov.[109][110]

Ultimately, the Commons community ignored the facts and was unwilling to take action against Mozhenkov; instead, the Wikimedia Foundation (WMF) had to step in and ban Mozhenkov from Wikimedia themselves.[111] However, the Commons community, and Germans Saibo and Niabot in particular, protested the WMF's decision to ban Mozhenkov[112] and were reluctant to unblock the whistler-blowers who brought Mozhenkov's past to the community's attention.[113]

Unable to accept the outcome, Saibo began disrupting Commons.[114][115] In April, Saibo and Niabot sought to have critic "Tarc" banned.[116][117] Saibo had to be restrained, and in January 2013, Saibo banned himself from Commons in protest.[118]

In April 2012, Commons admins "A.Savin",[119] "Russavia",[120] and "Leyo"[121] blacklisted Wikipedia criticism websites The Wikipedia Review and Wikipediocracy after a less than a day old discussion among German speakers without any input from native English speakers,[122] and the Commons community was reluctant to remove the criticism websites from the spam list.[123][124] The Commons community also sought to limit what its participants can say or do outside of Commons.[124] Ultimately, the criticism websites were removed from the blacklist[125] and the proposed restrictions on speech outside of Commons were not passed.[124]

Meco and slow-moving bureaucracy

In February 2006, Norwegian pedophile Halvor Raknes Johansen, a.k.a "Meco", who was 42 years old at the time, joined Wikipedia.[126] In June 2006, Norwegian pedophile Halvor Raknes Johansen, a.k.a "Meco", uploaded several nude photos of himself onto Wikimedia Commons,[127] and in November 2006, he uploaded photos of several young boys onto Commons.[128]

In March 2008, Meco wrote of his role in distributing child pornography and his interactions with teenage boys on a forum.[129]

<templatestyles src="Template:Blockquote/styles.css" />

[…] I purchased a 28k8 leased line around 1995-96 to enable me to remain online 24/7. So I started to collect erotic and pornographic photos of boys, still no prepubescent. As I gradually became aware that there was a pedophiliac presence on the net, I looked this up out of curiosity and genuine interest for what this was all about. It was subsequent to this that I began accepting a few images that went below. agewise, what I had previously received. Due to the illicit nature of this trade and the high level of paranoia in the men who had a particular interest in this, I closed off a part of my then FTP site for such trade, giving out separate access to people who were particularly interested in exchanging either nude photos of prepubescent boys (aroused or not), photos showing such young boys engaged sexually with each other, or pictures of adult men having sex with these young boys, this particular genre goes by the name of "intergen" (meaning intergenerational).

[…] I believe $25 for six months access (I don't remember exactly). My gains from this approximately covered my expenses for the leased line, that's how I justified to myself taking that money. And since all the people who ever had access to the youngest pictures were already into this activity of exchanging (or trading, as the term was, it was a fully reciprocal process) them, pay was never considered. Besides, I was quite consciouss that there were ethical considerations involved, not to mention criminal, so I did not want to provide access to this material to people that were not already into this.

All my child pornographic images were hidden on my hard drive by an encryption protocol which in some respects is similar to PGP, which was called SFS- Secure File System. So, when I was arrested in November 1998 and all my computers impounded, the police were never able to find this material. The reason for my arrest was somewhat unrelated to this. It involved a burnt CD which contained heterosexual porn which some teenage boys who had been in my apartment asserted that they had received from me. That CD was an anomaly as I had never cared for naked women or girls. It had been left (forgotten maybe) by a teenage boy whom I had become acquainted with, and when some other teenage boys (a little yonger, around 14) were in my home, they discovered it and asked if they could borrow it. Not giving that matter much thought I said fine. I was convicted in the lower courts for having made illegal pornography available to minors, however, when the case was appealed, I was acquitted as it became unclear whether the CD presented in court was the same which I had had in my apartment (and which I had barely glanced at).

— Meco, ConCen.org[129]

In March 2013, Wikipedia critic and Wikipediocracy blogger "Delicious carbuncle" submitted a blog entry to Wikipediocracy documenting Meco's pedophilia and Meco's role in hosting and distributing child pornography on a FTP server.[13] Several days later, in April, Meco was banned from the English Wikipedia,[130] yet the Wikimedia Commons leadership did not take any action against Meco.

On February 18, 2015, Meco uploaded an photo entitled "Child_porn_blurred.png" onto Commons, and it was not noticed and deleted until March 9th of the same year.[131] Despite the child porn being noticed and deleted on March 9th, Meco was not immediately banned from Commons.

On March 17th, Meco contested the deletion of "Child_porn_blurred.png",[132] and it was only at this point that an admin (Steinsplitter) finally reported Meco to the Wikimedia Foundation's legal team.[133] Nevertheless, the local volunteer administrators decided to wait for the legal team to respond instead of immediately banning Meco themselves. On the next day, Meco once again contested the deletion of the photo.[134] Commons administrator Steinsplitter indicated that the Wikimedia Foundation (WMF) had oversighted the image, and he threatened to block Meco (but only threatened).[135][136] Also, despite the WMF oversighting the photo, they did not ban Meco at the same time.

On the 20th, Meco contested the deletion for a third time and complained about Steinsplitter threatening to block him.[137] Instead of acting decisively and following through with his threat to block Meco, Steinsplitter asked for advice from the other administrators.[138] Finally, Commons administrator Natuur12 banned Meco.[139][140]

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 60.2 60.3 60.4 Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. 85.0 85.1 Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. 89.0 89.1 Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. 98.0 98.1 Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. 124.0 124.1 124.2 Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. 129.0 129.1 Lua error in package.lua at line 80: module 'strict' not found.
  130. Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.