903:
April 1" the admin can say "policy says it doesn't matter when you do those things". Speaking for my version, I think it does so without being overly harsh or granting any new powers, yet giving clear authority, which was part of the problem at Arb. I wouldn't want to base my policy purely on this Arb case anyway. This isn't my first stab at creating an April 1 policy, this has been a problem for years, this Arb case just brought it to the attention of more people, and frankly, admin aren't sure how tolerant they should be on April 1. Now they will know: a little more, but not infinitely so.
683:
most mundane April Fools day joke such as a prank AfD (since making frivolous AfD nominations violates policy). Additionally, the word "disruption" needs to be more clearly defined, since it does not differentiate between jokes that inconvenience editors for a second or two at most, and jokes that cause a profound interference in the functioning of
Knowledge (XXG). Given these two points, I believe that different people will interpret the proposal in profoundly different ways ranging from a near total ban on APril Fools Jokes outside of user space to a re-affirming of
773:. For example, if we make a rule about needing to clean up a joke by a particular deadline, we will face a dilemma enforcing it: it's more work to take an offender to dispute resolution than to just clean it up oneself. For me, it boils down to not disrupting what our readers read in mainspace and not getting a free pass to violate existing policies. There should be no joke content in article mainspace, and no violations in any space of BLP, NPA, and so forth, nor out-of-hand mass spamming. But we need not take ourselves too seriously. --
806:- This might be a little cleaner, but is similar to what I said above. It is softened just a bit and allows for some humor pages and the like, but still draws a clear line between what is tolerated and what isn't, with enough flexibility to not be wikilawyered. I tend to think WP:DE is the right destination because it is "disruption" in the most general sense. I think we need the "potentially" in front of BLP because if it gets reverted, they need to understand that
637:" If someone makes a hoax page and it is clearly marked, or does something that genuinely does not cause disruption, then so be it, but if they think it is funny to monkey around where it interferes with others who want no part of April Fools, then they shouldn't be shocked if it draws sanctions, no differently than it would on April 2nd. Sadly, this needs to be codified, to make it clear that you can't justify disruption based on the calendar.
1203:
34:
1004:. I didn't mention article space specifically, but a reading makes it obvious that article space isn't the best place for lots of jokes, as editors (should) know that article space has tighter rules on April 2 than meta space, so tread carefully. Basically, we are flipping it: April 1 jokes aren't a Right or free pass, they are simply tolerated if they don't hurt anything or violate any policy.
1065:
is a reasonable place and fits since many of these activities are simple disruption. This would only take a single RFC, and WP:FOOLS can be updated via the normal editing process since it is just an essay and not related to the RFC. To treat disruption on April 1 the same as April 2 means treating it the same in policy (but adding a section to clarify), not giving it a special policy.
1179:
729:
more about giving admins the power, but not necessarily the requirement, to step in on all April Fools jokes (which would allow admin inaction on more harmless jokes, but empower them to step in on more disruptive or just plain obnoxious jokes). Iâve personally seen several instances of editors spamming jokes that were technically in compliance with
1105:
again, just setting the tone and relying on common sense to guide us as to what is and isn't acceptable. Often it will just go to ANI and the community will decide, based on this new section. This is where the general principle will either be understood, or the unnecessary detail will get wikilawyered to death.
1064:
to guideline status, and it still failed even though everyone treats it as policy. I think that what we are saying is that "disruption is disruption, even if it happens on April 1". The simplest and most direct way is to add to WP:DE. While WP:DE isn't the only place you could put the section, it
706:
itself. Besides, admin are held accountable for our actions, if an admin goes too far, other admin and non-admin alike will fix it. Keep in mind, we do NOT want to encourage April Fools pranks, we are just saying they will only be tolerated if there is no collateral damage. If there is collateral
682:
I think that the overarching idea that April Fools Day is not an excuse for breaching the specific policies you listed is a good idea, but I fear that there is some vagueness in your proposal that could cause a lot of drama down the road. Under the suggestion, people could be sanctioned for even the
521:
I wonder if there should also be an explicit deadline for removal or archiving of AFJs, perhaps April 2 at 12:00 UTC (when April 1 has ended practically everywhere in the world); most of the controversy that led to the recent case seems to have erupted only after the material had been up for about a
442:
He closed it with a kind of doubletalk closing message. He never said it was a prank, but just did it and quietly chortled while he watched everyone try to figure out what happened. One of the participants posted a message saying "I don't understand your closing message." Then he said, "oh it was a
166:
The scope of this RfC would solely be to review the state of April Fools' Day jokes on
Knowledge (XXG) in general, not to discuss the details of the arbitration case. I think it's pretty well-established by the case that under current policy, April Fools' Day jokes must adhere to the BLP policy just
890:
I'm a fan of short and general policies/rules, but would this rule have solved the issue that has led to this need for clarification? I don't think it would have. It depends what we're trying to accomplish, I guess. Do we want a guideline that we can point to as justification for sanctions or do we
869:
April 1st and some other days in various places and cultures have traditionally been days for "pranks" and "hoaxes." Knowledge (XXG), however, is not a site for "pranks" or "hoaxes" at any time which might adversely affect any person, religion, culture, group or place in any way, on any page. This
701:
We admin aren't so bad once you get to know us, and most (like myself) will try to get someone to simply back down by pointing to the policy, so we don't have to block. We don't LIKE blocking. This would give us a TOOL, and the vagueness allows for community consensus to interpret, the same as most
287:
I agree that this RfC should not be used to continue the ArbCom case, but I do think we have to address specific guidelines on what is/is not acceptable on April Fools. I think a proposal such as the following would gain support and prevent this type of thing from getting blown our of proportion in
950:
If the joke would be ruined by having (joke) in the article name, then the joke was not good enough in the first place. The purpose of these specific restrictions is to eliminate, as much as possible, judgement calls. The 'noindex' is an attempt to limit, as much as possible, the joke to
Knowledge
902:
It would have made it clear the BLP applied, even for April 1, and that edit warring isn't excused, and that any hoax has to be tagged properly, and that it was ok to block him as he can't use April 1 as an excuse. It would simply give clear authority to admin, so when someone says "Come on, it's
822:
April 1st or "April Fools Day" is a tradition in some western cultures. While the community is tolerant of harmless jokes, the day is not a defense for violating any policy or guideline. This includes (but is not limited to) creating improperly labeled hoaxes and/or humor pages, edit warring and
728:
Two things: first, some of my later statements came off a lot harsher than I intended (sorry about that). Second, I can support your proposal being implemented the way you proposed it. I had interpreted it as being something that would be strictly enforced across the board, but your proposal seems
372:
didn't read that as a prank. Did the closer claim that was a prank at some point? It would probably be a good idea to explicitly forbid jokes at the administrator noticeboards, as many of them are important to the day-to-day operation of the project. For instance, imagine if people decided to spam
325:
Living persons not associated with
Knowledge (XXG) should not be the primary subject of an April Fools joke. For example, nominating a biography of a living person for deletion with a rationale that pokes fun at our processes is fine, but using a rationale that pokes fun at the person is not fine.
321:
Jokes must not create work for other editors. Ideally, jokes should be contained on a single page. (New addition to the guidelines. This makes it explicit that you shouldn't make "joke" edits to a whole bunch of pages and leave other editors to clean up your mess. This is a perennial problem, from
249:
I think an RfC is a good idea. On the most recent April's Fool's Day, an active ANI case was closed with an incomprehensible closing message as an unfunny "joke." Nobody thought it was a joke as it wasn't funny. That sort of stupidity needs to be curbed, if there is such a thing as passing a rule
151:
I'd like to note that the issue in the Arbcom case mentioned above existed well beyond April 1st, and included what I, and many consider to be BLP vios. The options above don't seem to take that into account. Though, I'm personally in favor of not having any "made up" things on
Knowledge (XXG)
1104:
Could we? Yes, but the more specific we are, the more it can be picked to death or more likely people will oppose it. It only needs to set the general tone and empower the community to act. Once you start listing dos and don't, everything starts looking like an exception. We are better off,
973:
is on the right track that a more general approach is superior to a list. it also has to be noted that the point of April Fools' Day is to have people led astray for a moment in thinking a hoax is real. Thus, requiring "joke" in an article name misses the point, though on April 2, I agree that
984:
is entirely appropriate. I also think that abolishing any reference to a living person is overkill, though as part of a general discussion of how BLP works outside of article space, clarification is probably wise, and that clarification can be linked to within the Rules for Fools page.
117:
Well just because they asked the community to consider, does not actually mean one is needed or a good idea. No it won't be abolished, entirely (as much as that might be a good or bad idea) so unless there is a specific strong idea for how to improve it, perhaps we should just move on.
1136:
Generally it's bad practice to have multiple headers with the same title, since a link to any one of them will only go to the first. Would it be a good idea to number these, so that the first proposal's headers are "Support 1/Oppose 1/Discussion 1" and so on, or something similar?
465:
proposed above. I'm not a fan of "strictly prohibited" (sounds too "legal"). Something like "Don't make April Fools jokes at noticeboards and other project pages which are vital to the day-to-day operation of the project." Specific pages should not be linked or listed as per
702:
policies. I think you have to be vague because the more specific you are, the more you get wikilawyered and drawn into long ANI debates, which is exactly what we want to avoid with this change in policy. I assume this RFC could apply to or might be asking for a change to
294:
Keep it in the User, User talk, Knowledge (XXG), and
Knowledge (XXG) talk namespaces. (Current guidelines say nothing in the mainspace, so this extends the no-go zone to namespaces such as Category, Template, etc, all of which generally effect the appearance of mainspace
335:
I'd much rather see an RfC that gauges support/oppose on a series of guidelines like the above rather than an RfC that more broadly asks "Is this ok?". Of course, if "April Fools jokes are generally acceptable" is opposed, we have our answer for that question anyway. ~
999:
That is one reason I specifically used the phrase "potentially" breaching BLP, to stay well outside the lines of poor taste, but still allow mentioning persons. The simpler it is, the more likely it will be followed, and the less likely it will be a problem.
831:
I really think this is all you need; no templates or special sanctions. It makes the simple statement that you can't use the day as an excuse to actually violate policy, and does so using common sense instead of exhaustive lists of dos and don'ts.
1086:'s idea earlier of restricting April Fools' jokes only to the User, User talk, Knowledge (XXG), and Knowledge (XXG) talk namespaces, so that categories and templates aren't affected as well. I understand the concern that too many rules may lead to
1041:
is a good place to put guidelines about disruption in general, but aren't "April Fools' Day jokes" a specific kind of disruption? If administrators want an unambiguous tool to use to combat April 1 disruption, perhaps it would be better to update
132:
True. Another reason I started this was to ask if we should even have such an RfC. Moving on might be prudent, although I feel that a good portion of the community wants to revisit the general issue of April Fools Day jokes this year.
66:
95:
jokes would be difficult to enforce, especially when many jokes (e.g. fake block notices) are localized on user talk pages and otherwise do no harm to the encyclopedia. There was an RfC about April Fools' a couple years ago â see
494:
as you wish but just to be clear, the "joke ANI close" I'm referring to was not an issue in the ANI case. I did raise it in my submission, but as an example of the lengths to which April Fool's Day has become a pain in the butt.
558:
I agree. Maybe a template could be placed on AFJs which would be invisible to readers, but which would prompt a bot to remove the jokes after the deadline? (Or it could be visible, something similar to the {{humor}} template)
270:
This is a very, very minor point, but in anything going forward, it's a good idea to refer to "an RfC about April Fools" instead of "an April Fools RfC", because the latter sound like the RfC itself is intended as a joke.
891:
want a guideline that will prevent the activity that would require sanctions? This general statement would be fine for the former. I don't think it would achieve the latter any better than the current unofficial rules. ~
73:. Now might be a good time to start thinking about how the RfC should be set up, i.e. what questions should be asked? We could have the following basic options that we would vote support/oppose on for each:
185:
I understand, but the umbrella of "April Fools' Day jokes", is awfully large, and if such a thing were to actually get comments in support, would like to have the policy limitations front and center.
611:
Very true. That could probably be added to Rob's guideline above on "Don't make April Fools jokes at noticeboards and other project pages which are vital to the day-to-day operation of the project.".
59:
100:â that had many proposals ranging from banning all April Fools' Day jokes to collaborating with the Wikimedia Foundation to make them better. Should we structure the RfC in a similar way?
347:
I think the above are good princples, but I do think that the RfC needs to address "pranks" like joke ANI closes like the one I mentioned. That might have been a one-off or perhaps not.
667:
April Fool's Day is not a free pass for disruption. Unmarked hoaxes, jokes in article space, BLP violations, etc., are no more acceptable on April 1 than on April 2 or any other time.
522:
week. Not to make it mandatory for the jokers to âclean up after themselvesâ by the deadline, but to underline that a return to âbusiness as usualâ is expected from that point on.â
870:
does not preclude pages clearly marked as "humor" in areas specifically allowed by policy to have such pages. Edits which negatively affect others will be handled as disruption.
443:
joke I see." Then an admin reopened the discussion with an edit summary saying something like "not the place for a joke." I can try to track down the diff if that would help.
631:
Being April 1 is not a defense to any violation of policy, including (but not limited to) creating hoaxes, edit warring and making any edit that potentially breaches
1158:
did it, by repeating the proposal name in the section headers (e.g. "Support independent XfD log/Oppose independent XfD log/Discussion about independent XfD log").
1155:
97:
1189:
711:
and others. I think you have to have a little bit of trust that admin are listening to consensus when applying it and using sanction as the last resort.
875:
As being shorter, and quite easily understood, and making the section not just applicable to 1 April, nor susceptible to any variant interpretations.
827:. Editors should understand that actions which negatively affect others will be handled no differently than disruption on any other day of the year.
17:
1185:
326:
April Fools jokes that contain blatantly false or possibly negative information about living persons may be subject to speedy deletion as a
221:. Anything that does not fall under these criteria is currently considered disruptive and thus may lead to sanctions if they are repeated.
38:
757:
Abolishing April Fool's jokes is a bad idea. just be a bit more strict on the warnings, making sure to not let things get out of hand.
539:
573:
I agree that this would be a good guideline to be included in the RfC. Not sure if it would receive consensus, but worth a shot. ~
330:. (New addition that is mostly a representation of existing policy, although this is probably the most likely to meet resistance.)
733:, so I think itâs probably for the best to have specific April Foolâs day language stating admins can intervene in all jokes.
588:
One other major issue: We need to have a complete ban on April Fools' Day Jokes that mess up policy and guideline pages, like
461:
be. The ArbCom case is closed, and we have to move on. In any event, I agree that we should float a proposal similar to what
71:
to hold an RfC regarding whether the leniency for April Fools Day jokes should be continued and if so, what should be allowed
629:
You can't realistically abolish it, but you can make it clear that no allowances are made for "April Fools". In short, "
413:
993:
960:
951:(XXG). The restriction to article space to keep the jokes to an easily identified space to help eliminate disruption. â
884:
844:
797:
430:
109:
52:
730:
684:
218:
761:
1274:
1241:
1222:
1195:
1167:
1148:
1117:
1099:
1077:
1055:
1016:
915:
897:
858:
782:
764:
742:
723:
696:
677:
649:
620:
599:
579:
568:
546:
504:
480:
452:
379:
356:
342:
280:
259:
244:
230:
194:
180:
161:
142:
127:
738:
692:
123:
635:. Person who dabble with foolish activities on "April Fools" do so at the risk of being blocked for disruption.
769:
In general terms, it will be a losing battle to try to legislate users' sense of humor, and there are risks of
1025:
Right, and if something is in article space, we still expect the content to meet the core content policies of
1001:
811:
1270:
1112:
1082:
That sounds reasonable if it's just the general rule, but do you think we could be more specific? I liked
1072:
1011:
910:
839:
758:
718:
644:
526:
500:
448:
352:
255:
1251:
There is a proposal template at the end of the list of proposals that doesn't contain any of the below:
793:
673:
616:
564:
426:
956:
850:
That general concept works. The longer the list of rules gets, the easier it becomes to game them.
810:
still applies as we always err on the side of caution with real human beings. It would be
Shortcut:
778:
734:
688:
596:
312:
276:
199:
I see what you mean. If we do hold an RfC, we could include a introduction that makes very clear the
119:
168:
1234:
991:
856:
167:
as any other edit. There was another remedy in the case calling for a separate RfC to discuss the
1232:
the discussions rather than actual discussion of the proposals, and the page is long as it is. â
1215:
1087:
1043:
770:
471:
467:
1266:
1141:
1106:
1066:
1005:
970:
904:
880:
833:
712:
660:
638:
553:
523:
496:
444:
388:
363:
348:
251:
1030:
91:
I'm not sure if we should include the second option without adding some exceptions â banning
789:
669:
612:
560:
462:
422:
1061:
1034:
824:
807:
632:
204:
1090:, but I think it helps to explicitly label jokes that affect the mainspace as disruptive.
952:
788:
I'd also suggest a {{Uw-april1}} template, for warning users who are joking disruptively.
774:
606:
593:
474:. We don't want to lay out a road map to where joke-based vandalism is most disruptive. ~
272:
240:
190:
157:
1038:
816:
708:
703:
327:
171:
policy â this scope of this idea lab thread is just the April Fools' Day jokes RfC idea.
986:
978:
851:
302:
211:
83:
After these two starting options, we could have a section that allows users to propose
1026:
1210:
1163:
1095:
1083:
1051:
893:
575:
489:
476:
396:
375:
338:
226:
176:
138:
105:
48:
1138:
876:
236:
186:
153:
665:
That's a very good idea. That can be our general rule for April Fools jokes:
457:
Nah. I shouldn't have even asked the question; this is exactly what this RfC
939:
a bot deletes the article after 48 hours (to account for various time zones)
1178:
1228:
Hope it's ok that I moved this to the talk page. It seems to be a comment
87:
to current practice, as a middle ground between continuing and abolishing.
1159:
1091:
1047:
222:
172:
134:
101:
44:
207:, 2) they must be kept out of mainspace, 3) they must be tagged with
1060:
That could take years and never happen. Look at the battle to get
235:
Thanks, if all 3 criteria are met, I could see myself supporting.
707:
damage, we already have policies to deal with those problems, ie:
77:
Continue April Fools' Day jokes without changing current practice
1177:
923:
Comment: Simpler the betterâApril Fool's page requirements
203:
restrictions on April Fools' jokes: 1) they must adhere to
1154:
Yeah, I noticed this too. We could also try it the way
589:
322:
what I understand. I know it was a problem this year.)
152:
being passed off as real in even the loosest sense.
927:
no real people may be mentioned, by name or position
1261:Content (what the rule or modification would be).
1156:Knowledge (XXG):Requests for comment/April Fools'
930:only in article space, with article name in form
98:Knowledge (XXG):Requests for comment/April Fools'
373:"joke" AIV reports. That would be horrendous. ~
401:Yes. Maybe add to the specific guidelines above
8:
946:because of (joke) required in article name)
291:April Fools jokes are generally acceptable.
1037:â clearly not the right place for a joke.
412:Jokes at noticeboards, village pumps, or
18:Knowledge (XXG) talk:Requests for comment
80:Abolish April Fools' Day jokes entirely
39:Knowledge (XXG):Village pump (idea lab)
965:I generally like the idea of updating
70:
823:making edits that potentially breach
7:
1046:and elevate it to guideline status.
318:. (No change vs. current guidelines)
1265:Should it remain in the RfC page?
24:
1132:Support/Oppose/Discussion headers
1201:
1186:The Blade of the Northern Lights
414:Knowledge (XXG):Main Page/Errors
32:
27:Towards another April Fools' RfC
942:all policies apply (other than
731:Knowledge (XXG):Rules for Fools
685:Knowledge (XXG):Rules for Fools
219:Knowledge (XXG):Rules for Fools
298:All jokes must be tagged with
69:that encourages the community
1:
936:'noindex' placed on the page
1290:
30:
1275:12:11, 5 April 2024 (UTC)
1242:20:10, 11 June 2016 (UTC)
1168:04:08, 10 June 2016 (UTC)
864:I would instead suggest:
217:or similar template. See
1223:02:53, 7 June 2016 (UTC)
1196:02:52, 7 June 2016 (UTC)
1149:18:47, 8 June 2016 (UTC)
1118:20:07, 5 June 2016 (UTC)
1100:20:02, 5 June 2016 (UTC)
1078:16:03, 5 June 2016 (UTC)
1056:15:28, 5 June 2016 (UTC)
1017:12:12, 5 June 2016 (UTC)
994:03:01, 5 June 2016 (UTC)
961:23:45, 4 June 2016 (UTC)
916:13:42, 4 June 2016 (UTC)
898:13:24, 4 June 2016 (UTC)
885:12:45, 4 June 2016 (UTC)
859:03:01, 5 June 2016 (UTC)
845:12:01, 4 June 2016 (UTC)
798:19:49, 3 June 2016 (UTC)
783:18:36, 3 June 2016 (UTC)
765:18:08, 3 June 2016 (UTC)
743:05:33, 4 June 2016 (UTC)
724:23:14, 3 June 2016 (UTC)
697:20:51, 3 June 2016 (UTC)
678:19:47, 3 June 2016 (UTC)
650:18:00, 3 June 2016 (UTC)
621:18:30, 3 June 2016 (UTC)
600:04:10, 3 June 2016 (UTC)
580:00:20, 3 June 2016 (UTC)
569:23:57, 2 June 2016 (UTC)
547:23:21, 2 June 2016 (UTC)
505:22:34, 5 June 2016 (UTC)
481:03:02, 3 June 2016 (UTC)
453:00:36, 3 June 2016 (UTC)
431:02:48, 3 June 2016 (UTC)
380:00:20, 3 June 2016 (UTC)
357:22:50, 2 June 2016 (UTC)
343:21:28, 2 June 2016 (UTC)
281:20:36, 2 June 2016 (UTC)
260:20:06, 2 June 2016 (UTC)
245:19:25, 2 June 2016 (UTC)
231:19:12, 2 June 2016 (UTC)
195:19:06, 2 June 2016 (UTC)
181:19:04, 2 June 2016 (UTC)
162:18:43, 2 June 2016 (UTC)
143:19:04, 2 June 2016 (UTC)
128:18:41, 2 June 2016 (UTC)
110:18:20, 2 June 2016 (UTC)
53:19:44, 6 June 2016 (UTC)
1247:Final proposal template
416:are strictly forbidden.
1182:
873:
829:
1181:
866:
820:
65:will be closing with
250:against stupidity.
61:Gamaliel and others
1183:
815:new subsection of
26:
759:ThePlatypusofDoom
1281:
1239:
1237:
1213:
1205:
1204:
1192:
1146:
989:
983:
977:
854:
664:
610:
557:
543:
536:
533:
530:
493:
400:
392:
367:
317:
311:
307:
301:
216:
210:
63:arbitration case
55:
36:
35:
1289:
1288:
1284:
1283:
1282:
1280:
1279:
1278:
1249:
1235:
1233:
1211:
1202:
1190:
1176:
1142:
1134:
987:
981:
975:
967:Rules for Fools
852:
735:Spirit of Eagle
689:Spirit of Eagle
658:
604:
551:
541:
534:
531:
528:
487:
394:
386:
361:
315:
309:
305:
299:
214:
208:
120:Alanscottwalker
56:
43:
41:
33:
29:
22:
21:
20:
12:
11:
5:
1287:
1285:
1263:
1262:
1259:
1256:
1248:
1245:
1236:Rhododendrites
1226:
1225:
1175:
1174:not this again
1172:
1171:
1170:
1133:
1130:
1129:
1128:
1127:
1126:
1125:
1124:
1123:
1122:
1121:
1120:
1020:
1019:
1002:WP:COMMONSENSE
969:, but I think
948:
947:
940:
937:
934:
928:
921:
920:
919:
918:
862:
861:
802:
786:
785:
767:
754:
753:
752:
751:
750:
749:
748:
747:
746:
745:
653:
652:
626:
625:
624:
623:
586:
585:
584:
583:
582:
519:
518:
517:
516:
515:
514:
513:
512:
511:
510:
509:
508:
507:
420:
419:
418:
417:
409:
408:
407:
406:
405:
404:
403:
402:
333:
332:
331:
323:
319:
296:
292:
285:
284:
283:
268:
267:
266:
265:
264:
263:
262:
247:
149:
148:
147:
146:
145:
89:
88:
81:
78:
31:
28:
25:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
1286:
1277:
1276:
1272:
1268:
1260:
1257:
1254:
1253:
1252:
1246:
1244:
1243:
1238:
1231:
1224:
1221:
1220:
1219:
1214:
1208:
1200:
1199:
1198:
1197:
1193:
1187:
1180:
1173:
1169:
1165:
1161:
1157:
1153:
1152:
1151:
1150:
1147:
1145:
1140:
1131:
1119:
1116:
1115:
1110:
1109:
1103:
1102:
1101:
1097:
1093:
1089:
1085:
1081:
1080:
1079:
1076:
1075:
1070:
1069:
1063:
1059:
1058:
1057:
1053:
1049:
1045:
1040:
1036:
1032:
1028:
1024:
1023:
1022:
1021:
1018:
1015:
1014:
1009:
1008:
1003:
998:
997:
996:
995:
992:
990:
980:
972:
968:
963:
962:
958:
954:
945:
941:
938:
935:
933:
929:
926:
925:
924:
917:
914:
913:
908:
907:
901:
900:
899:
896:
895:
889:
888:
887:
886:
882:
878:
872:
871:
865:
860:
857:
855:
849:
848:
847:
846:
843:
842:
837:
836:
828:
826:
819:
818:
813:
809:
805:
800:
799:
795:
791:
784:
780:
776:
772:
768:
766:
763:
760:
756:
755:
744:
740:
736:
732:
727:
726:
725:
722:
721:
716:
715:
710:
705:
700:
699:
698:
694:
690:
686:
681:
680:
679:
675:
671:
668:
662:
657:
656:
655:
654:
651:
648:
647:
642:
641:
636:
634:
628:
627:
622:
618:
614:
608:
603:
602:
601:
598:
595:
591:
587:
581:
578:
577:
572:
571:
570:
566:
562:
555:
550:
549:
548:
545:
544:
538:
537:
525:
520:
506:
502:
498:
491:
486:
485:
484:
483:
482:
479:
478:
473:
469:
464:
460:
456:
455:
454:
450:
446:
441:
440:
439:
438:
437:
436:
435:
434:
433:
432:
428:
424:
415:
411:
410:
398:
390:
385:
384:
383:
382:
381:
378:
377:
371:
365:
360:
359:
358:
354:
350:
346:
345:
344:
341:
340:
334:
329:
324:
320:
314:
304:
297:
293:
290:
289:
286:
282:
278:
274:
269:
261:
257:
253:
248:
246:
242:
238:
234:
233:
232:
228:
224:
220:
213:
206:
202:
198:
197:
196:
192:
188:
184:
183:
182:
178:
174:
170:
165:
164:
163:
159:
155:
150:
144:
140:
136:
131:
130:
129:
125:
121:
116:
115:
114:
113:
112:
111:
107:
103:
99:
94:
86:
85:modifications
82:
79:
76:
75:
74:
72:
68:
64:
62:
54:
50:
46:
40:
19:
1267:Alfa-ketosav
1264:
1250:
1229:
1227:
1217:
1216:
1206:
1184:
1143:
1135:
1113:
1108:Dennis Brown
1107:
1073:
1068:Dennis Brown
1067:
1012:
1007:Dennis Brown
1006:
971:Dennis Brown
966:
964:
949:
943:
931:
922:
911:
906:Dennis Brown
905:
892:
874:
868:
867:
863:
840:
835:Dennis Brown
834:
830:
821:
803:
801:
787:
719:
714:Dennis Brown
713:
666:
661:Dennis Brown
645:
640:Dennis Brown
639:
630:
574:
554:Odysseus1479
540:
527:
497:Coretheapple
475:
458:
445:Coretheapple
421:
389:Coretheapple
374:
369:
364:Coretheapple
349:Coretheapple
337:
328:blatant hoax
288:the future.
252:Coretheapple
200:
92:
90:
84:
60:
57:
812:WP:FOOLSDAY
790:Chickadee46
670:Chickadee46
613:Chickadee46
561:Chickadee46
463:Chickadee46
423:Chickadee46
313:April fools
37:Moved from
953:Neonorange
932:Foo (joke)
775:Tryptofish
607:Od Mishehu
597:Od Mishehu
273:Tryptofish
169:WP:BLPTALK
988:Montanabw
853:Montanabw
594:ע×× ××׊××
459:shouldn't
295:articles)
1258:Proposer
1088:WP:CREEP
1044:WP:FOOLS
771:WP:CREEP
524:Odysseus
490:BU Rob13
472:WP:CREEP
468:WP:BEANS
397:BU Rob13
67:a remedy
1031:WP:NPOV
974:adding
877:Collect
201:current
1212:Jayron
1191:芹ăăŚä¸ăă
1062:WP:BRD
1035:WP:NOR
825:WP:BLP
814:-: -->
808:WP:BRD
804:UPDATE
762:(Talk)
633:WP:BLP
370:really
205:WP:BLP
1255:Title
1230:about
1039:WP:DE
979:humor
817:WP:DE
709:WP:DE
704:WP:DE
303:Humor
237:Arkon
212:humor
187:Arkon
154:Arkon
16:<
1271:talk
1209:. --
1207:Like
1164:talk
1139:ansh
1096:talk
1052:talk
1033:and
1027:WP:V
957:talk
944:hoax
881:talk
794:talk
779:talk
739:talk
693:talk
674:talk
617:talk
590:this
565:talk
501:talk
470:and
449:talk
427:talk
353:talk
277:talk
256:talk
241:talk
227:talk
191:talk
177:talk
158:talk
139:talk
124:talk
106:talk
58:The
49:talk
1240:\\
1160:Mz7
1144:666
1092:Mz7
1084:Rob
1048:Mz7
894:Rob
576:Rob
477:Rob
376:Rob
339:Rob
308:or
223:Mz7
173:Mz7
135:Mz7
102:Mz7
93:all
45:Mz7
1273:)
1218:32
1194:)
1166:)
1114:2¢
1111:-
1098:)
1074:2¢
1071:-
1054:)
1029:,
1013:2¢
1010:-
982:}}
976:{{
959:)
912:2¢
909:-
883:)
841:2¢
838:-
796:)
781:)
741:)
720:2¢
717:-
695:)
687:.
676:)
646:2¢
643:-
619:)
592:.
567:)
503:)
451:)
429:)
393:,
368:I
355:)
316:}}
310:{{
306:}}
300:{{
279:)
271:--
258:)
243:)
229:)
215:}}
209:{{
193:)
179:)
160:)
141:)
126:)
108:)
51:)
42:â
1269:(
1188:(
1162:(
1094:(
1050:(
955:(
879:(
792:(
777:(
737:(
691:(
672:(
663::
659:@
615:(
609::
605:@
563:(
556::
552:@
542:9
535:7
532:4
529:1
499:(
492::
488:@
447:(
425:(
399::
395:@
391::
387:@
366::
362:@
351:(
275:(
254:(
239:(
225:(
189:(
175:(
156:(
137:(
122:(
104:(
47:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.