Knowledge:Community response to the Wikimedia Foundation's ban of Fram/Archive 2

3478:

long time admin. He had the main account Janneman, a second " Edith Wahr" and a third one and last by the name "Judith Wahr". The word "wahr" means "truth" in german and "Edith Wahr" sounds like "edit war" and indeed he was on many occasions not very polite. Jannemann was for some years more and more in anger about the use of "US-american" instead of "american" especially in his "own" articles. In the german wikipedia both is possible, in the academic circles and wide parts of the public "american" is traditionally used. A lot of other german wikipedia editors think nowadays "US-american" the more specific choice to be used for example in short characterizations in biographies, don´t think twice about it and see this as common usage (to older people with slight reminiscences to 68er times or the GDR). At one point Janneman as "Judith Wahr" lost his nerve and threatened one such user in a totally inacceptable manner. He had a prehistory of bans and his two older accounts were banned indefinitely on his own request some time ago- meaning he gave up editorial work under his main user name. Technically this was not a permanent ban (he could have applied for reactivation of his account). Under his last account Judith Wahr he was immediately sanctioned and first blocked three days, than by another admin infinitely (December 9, 2018,

698:. This has been one of the possibilities I've been considering if they don't back down in the next few days. This will surely grab attention, and is strong but less openly hostile than repeatedly wheel-warring with OFFICE, which I feel is likely to be the least effective option. Another option (discussed above) is more passive but it gets more effective the longer it persists: simply refuse to handle any admin tasks, and post a banner on all major admin areas (XfD, ANI, etc.) so that anyone who wishes to join the strike may do so. Other than posting the banners (necessary to prevent those who have not heard about this incident from becoming inadvertent strikebreakers), simply do nothing, don't proactively cause disruption. In the end we'll see what happens: If everything is still running smoothly, then looks like the WMF has won, the community has implicitly endorsed their actions. But if everything grinds to a halt, WMF will be forced into action. The advantage of this method is that it actually uses the only true leverage we have against the WMF if they want to go all out: they can't force volunteers to do anything. -- 4372:

growing since 2010. The community was totally fine in pre-T&S era, why it suddenly become such a huge deal for the Foundation to work this out? More importantly, does it solve anything? If Fram does anything wrong off-wiki, the T&S team should ban Fram from off-wiki activities; if Fram curse on-wiki, then other admins should take care of that. Banning a user for one year on English Knowledge does not solve anything. The T&S team has been becoming more active and making decisions that local communities made up by volunteers instead of paid employees in the Foundation feeling inappropriate. The list of users blocked by WMF linked above started in 2012, and spiked since 2015, with three users so far in 2019 and probably more because they are now able to partly ban a user. The Foundation shall learn step away from communities, which are working hard to fight exactly the same problem the T&S is designed to do.

4905:

allowing English Knowledge to govern itself, and at root about respect for us, the editors. The WMF are not our bosses and even if they were, this high-handed action without even a clear explanation to Fram himself shows a disrespect that puts them in the wrong. I would not go so far as to support the suggestion that admins make retaliatory bans on WMF accounts editing here: blocks are supposed to be preventative, and besides it's useful to have the visual reminder of who's on the payroll. But whatever Fram's reputation or one's opinion of them, this is unacceptable conduct towards the community and the WMF have lost the right to have us assume they must have had adequate justification. Their action toward Floquenbeam makes it worse. We are a community of volunteers, not a village of serfs, and the important thing right now is to get the WMF to back down and apologize.

6076:

push the issue away and choose not to deal with it--however, they should be doing so with a public record, explaining the issue. If ARBCOM was one of the targets, does that mean that the complaint came from someone at ARBCOM? I don't know, but that is terribly inappropriate and I sincerely hope (and frankly, do not think) that that is not the case. Not because people at ARBCOM should not be safe from harassment, but because they should have to follow the same procedures as the rest of us, regardless of any political fallout which may occur by doing so. Again, I hate making a legal analogy, but that's like a judge recusing herself and then tampering with the court of appeals case by contacting the new judge. If there is an issue raised and ARBCOM has a COI, that needs to be publicly noted. There is no reason for this issue not to go through ARBCOM.

3486:). The german admins saw therefore no reason for further action. But according to the rules of the german wikipedia this was no permanent ban, in principle he could reappear under a new user name, though this would have certainly be detected in view of his former behavior. There was a complaint to the wikimedia foundation and office action followed two month later (February 19, 2019) resulting in a permanent ban (in the german wikipedia, not in other projects). The german admins hat no clue and were taken by surprise (in my view a serious communication problem and likewise here). Some came to the conclusion, that the WMF mistrusted the german Admin-community of volunteers as a whole and that the WMF should handle all such cases of permanent ban in the future by themselves. -- 3502:

themselves, but it was clear that it was said in a fit of rage. You are right that there are no unappealable permanent bans in German-language Knowledge; any infinite ban (such as this one was) can, in theory, be appealed at "Sperrprüfung". German-language Knowledge also has not developed the intricate distinction between "blocking" and "banning" that English Knowledge has (the blocking policy is short, there is no distinct banning policy). It is understood that accounts are blocked if issues with that account can't be solved otherwise, but usually, if people come back with a different account and behave well, these are not blocked. Vice versa, there is a standard blocking reason "Sperrumgehung, keine Besserung erkennbar", that is "block evasion, no improvement shown" - so,

3398:

do not distinguish whether a user writes or improves content, builds and provides tools or other tools for other volunteers, or helps by acting as a functionary of the administrative, checkuser, or oversight buttons. Occasionally, however, community members come to us with strong hints that local communities in some cases have long term difficulties not only maintaining their own rules in these cases, but also maintaining the structure of ToU . We will continue to address these rare cases brought to us within the framework of the Office Actions Policy. Sincerely, --WMFOffice (discussion) 10:54, Feb. 21, 2019 (CET)

730:, don't forget that there are several hundred users in the admin tribe but only a couple of dozen are real warriors or community leaders. If we simply refuse our admin tasks, there are hundreds of others who will continue to gnome away at AIV, CSD, XfD, and RFPP, etc., indeed, they may not even be aware of this issue, and if they were, just choose to ignore it. Wheelwarring would have the most impact because the WMF would have to desysop a lot of prominent and productive admins, but it would be guerilla tactics, and I'm not sure that the current Arbcom would support the community it is supposed to represent. 5826:(long-time listener, first-time caller) First point at least makes a little sense to me, second point doesn't. Fram wasn't the first to say scary mean words to ArbCom and probably won't be the last. Sure, there's some conflict of interest if ArbCom is handling a matter involving abusive behavior toward ArbCom, but I would hope that ArbCom would be mature enough to handle that neutrally. From what little I gleaned from that statement, I'm getting the feeling that T&S should have told the complainer to go through ArbCom, or at least asked permission to share information with ArbCom. 3565:

people felt the need to suddenly ban someone whose account had been blocked for months and did not do any harm on-wiki since, suddenly, without consulting anyone in the community and without giving a proper reason the only logical conclusion for me was that they were afraid of making some legally contestable statements in face of a potential trial in court. I did not comment in the discussion about the office action at that time precisely because I did not know any reason for it and I did not want to speculate. I would see things different now, probably other people would, too.--

3296:, former sysop, former ArbCom member, author of uncounted great aricles, including several featured articles about American history and literature. The WMF was invading in a case, that was solved by the local community (the account was blocked indefinitely after a rant, but there would have been open steps to search for an appeal or the involvement of the arbcom, to hopefully re-integrate a long-time productive member again in the community), and they gave an explanation comparable to here, which means: long text saying nothing. You can read details (of course in German) here: 4368:

while imposing the ban while their Google Translator stopped working after the bans. Their protection on "privacy" put us volunteers at the risk of being framed by others. If, say, some admin deletes my article, maybe I could look out which off-wiki event he/she went, then write an email to the Foundation claiming I have been harassed by the admin - as easy as that. You got warned by the Foundation, you asked why, and they tell you to protect victim's privacy I can't tell you. After you said "fuck" or any curse word once, you got banned, and you got no chance for appeal.

3852:, except that your broad-brush attack on the community is unwarranted IMHO. The fact that a small minority have engaged in disgraceful behaviour should not detract from the fact that the community is legitimately angry about what has happened and feels that something has gone badly wrong in the management and running of the encyclopedia. To you that may be "toxic" but to us it is an attack on our values, which are all about openness and due process except where there is demonstrably reason not to be open (and so far there's no evidence of that here). — 4782:, after this time, they know not to do it.) Even having ArbCom handle it privately would have been suboptimal, if everything was indeed on-wiki, but that still would be better than it coming from San Fran. Knowledge was here first, and the WMF was created to serve it and its community. Not the other way around. The relation between the community and WMF has always been one of uneasy cordiality at best, but if WMF attempts to interfere with the project's editorial independence, it should expect a reaction like this one every last time. 2723:

community declines to take action, the TOU has not been breached. The only time the Foundation should overrule the community is when legally required to (no way around that), or if the Foundation possesses knowledge which is too sensitive to be shared even with ArbCom, generally in areas such as child protection or threats. If private evidence could be submitted to ArbCom for a decision (and it usually can, ArbCom members must all sign the privacy and confidentiality agreement), they should do that rather than acting unilaterally.

4421:

have unequivocal support for the aforementioned banned users like enwiki do for fram from what I gather. I don't think it's possible to abolish the office action policy if that's what you're suggesting. The suspicious nature of this office action lies in the possible conflicts of interest between the office and fram, I also don't think that's the case for these two users on zhwiki. Nonetheless, should the office decide to hear appeals, I do agree these two members of the community deserve a chance, and not indef bans.

4318:

Chinese Knowledge locally. I have personally spoken to both users, and they both showed me the emails they get from the Trust and Safety team. After they were globally banned, lengthy discussions were triggered again - of course, they won't be as lengthy as this one in English Knowledge as zhwiki has a smaller community, but one of them was severe enough to cause articles created on Chinese Knowledge in that month saw a significant decrease because everyone went discussing what was going on.

31: 3300:. I resigned as a sysop in the follow-up to this (from my point) totally unnecessary invasion in a community process on behalf of an undisclosed complaint from an insider, that used the WMF to make project-politics from the hidden. My explanation was: "Since the WMF recently started, to rule the local projects in their own non-transparent and unrevisable way, I see no need for local administratorship any more. So I don't want to waste my time any longer in just an alibi function." ( 4577:

failing that, a block review on the administrators' noticeboard. If we elect someone to ArbCom who turns out to be awful, we have the chance to vote them out when their term expires, and if they're really, really awful, there are processes in place to have them removed from the committee. These processes are not perfect, in part because they're implemented by people, who are also not perfect, but they are there because having some documented procedure for fixing mistakes is vital.

4443:

had enwiki arbcom cases saying salty language alone doesn't constitute personal attacks or harassment, but clearly I think we all agree that slurs, on the other hand, do. If T&S is applying vocabulary-based civility standards instead of just behavioral factors, those need to be made far more explicit than the current language. It's clear the community as a whole reacts far worse to slurs than mere expletives, but slurs do not seem to have resulted in T&S issuing warnings.

2160:. Fram may also be operating under a sincere belief that the three incidents linked were the sole cause, but I suspect that Fram is far more intelligent than that. Let's just say that people don't get banned from WP solely on account of tagging articles and saying the f-word. There's more and we all know there's more. We just don't know what and Fram's choice of words sounds like someone trying to deflect blame, not someone trying to defend themselves against a false accusation. 3524:) were happy with those unspecific statements of this ominous office account: Since his accounts were already blocked, there was no perceivable change of the status quo and more importantly, since he was already blocked and apparently had not contributed with a new account it seemed obvious to me that the reason for it had to be something he did outside of Wikimedia projects (and hence to be dealt with off-wiki, with possible off-wiki consequences for him).-- 2237:, there's a style of outraged denial that indicates innocence and there's a style of denial that is a type of deflection and manufactured outrage that usually indicates wrongdoing. Someone who is remorseful about their wrongdoing or someone who is falsely accused responds with a different style from someone who is merely unhappy that they finally got called out on their shit. Whatever the actual incident, Fram finally crossed a line and got called on it. 3374:

and Safety Program. Some of the overhaul of policies in the program, which began in July 2018, had an impact on the investigation and had to be completed before we could close the case. So, while the case went through the same procedure as earlier Office Actions involving German-speaking Knowledge, as part of the 2018/2019 Annual Plan, new and less powerful measures became available within the existing, stable framework of Office Action Policies.

2156:, You are half correct, but be very careful not to manipulate my words. I do think that we cannot, at this time, "gauge the true extents of the alleged misdeeds, which led to his ban." But I specifically did not say he was "lying," though that is certainly one possibility. He may have been typing fast and given an incomplete answer. Or such behavior could also occur because Fram is utterly clueless as to the harm s/he has caused, or is in 378:, and I will remind you all that Knowledge is one of the biggest websites in the world. This is a huge story and it would likely spread like wildfire. I don't want that. In the minds of the public, it will likely translate to Knowledge's leadership being corrupt, so even if the WMF deserves to be publicly humiliated, it may well mar our project's reputation by extension, and I don't know how easy to recover from such a blow. 2084:

explanation, but I also do not believe Fram's self-serving examples were the real reason. Frankly, Fram's utter and complete refusal to acknowledge any responsibility at all is not the behavior of an innocent person, it's the behavior of someone who is doubling down on whatever they did. I do think that we as a community have repeatedly failed to properly address severe, long-term patterns of incivility. I concur with

4858:"Definitely not arguing the WMF has handled this perfectly." Understatement of the millenium. Not only did they not handle it "perfectly", they could hardly have handled it any worse. If I were to try and think of a way to enrage the community, it would be quite a challenge to top what the WMF did. Every single thing they did was wrong and it's troubling that all you can say is they "didn't handle it perfectly." 4581:

part of the reason that the community is acting with such revulsion at the way the WMF is conducting itself. If we recognize that every organization is capable of making errors from time to time, the natural question is "what is the process for getting them fixed?" The answer cannot be "none, because we are infallible." So, WMF, what is the process we should use for getting a mistaken T&S action corrected?

4117:

speculations about board members' personal lives. Those are the kind of tangents that will only help the WMF make its case that the community isn't to be trusted. Let's get back to the core issue: We need to force the WMF to realize that Knowledge wouldn't exist without us and that they can't risk alienating us. We should discuss how to make this clear to them and leave all this other crap alone.--

228:

me) highlights whatever the public stuff they think the press will be interested in. In other words, if anyone does wish to do that, remember that even if you succeed, it may not be the way you envision and it could be something that will be uncomfortable for people besides the WMF whether Fram or anyone else. (But I think the chance anyone except certain minor outlets interested is small anyway.)

2509:

to be issuing "warnings" for on-wiki conduct on the English Knowledge? Has anyone other than Fram received them? (I can confirm that I have not, though we'll see after today.) English Knowledge editors and administrators issue conduct warnings all the time, so that is clearly not an issue which the community here is incapable of handling. If we do not issue such a warning, it means that we have

4363:

on Chinese Knowledge - why no one on zhwiki acted but the Foundation's team have to act? So that means there is someone constantly and secretly reporting to the T&S, who may be personally in opposition to the one being reported trying to fabricate against them. After the first warning by T&S, you got watched by our big brother and even after you said fuck for once, you're done.

2690:

then yes they should delete the article as an office action (if they believe this is the best action they have the ability to take) - but they should be clear they are doing so because it violates the terms of use rather than making any judgement about whether it does or does not breach en.wp policy. The only definite fault with the block of Fram is the communication of it.

1582:. The community endorsed ArbCom's creation of arbcom enforcement sanctions, which effectively ended the issue of "unblockables" quite some time ago. The WMF is setting no standards at all. The action was taken by T&S, who decided to act themselves on a complaint rather than refer the matter to the local ArbCom, quite likely in contradiction of their own aims (see 1208:

you want to ask arbcom to do something, open a request for arbitration or whatever. This current thing is about WMF. d) The "independent committee" is silly and the petition overall is much too pompous. Let's see what Doc James and Jimbo say though. e) WMF staff is already accountable to the Board but the Board for the most part is not particularly accountable to

2678:

and indeed some sites very legally do allow that. So, let's say an English Knowledge AfD discussion concludes that an article has some promotional tone but is salvageable, and should be retained. Should the WMF then come along, say "Nope, this violates the TOU", and delete the article as an OFFICE action, or respect the decision made by the community?

2026:- You can't say this is intended to cause a cultural change if they won't actually say what happened. The WMF spends a lot on lawsuits to demonstrate points without us asking for them. For them to refuse to say anything because it aids their legal position, whatever the morals, is reprehensible, hypocritical and nothing more than moral cowardice. 4325:

zhwiki only. Another difference is, both users on Chinese Knowledge were highly controversial - you can tell by looking at their block logs. However, in both cases, the two banned users were behaving far less controversial without actions too aggressive, and there were no community discussions around these users by the time the ban was imposed.

406:

banned them without consulting the Knowledge community and without involving Arbcom! This is an outrage!" "So, that stuff about harassing someone and telling people to go fuck themselves, you're fine with that, are you?" "Well, idk, but we haven't seen adequate evidence of it and most importantly the WMF didn't follow the existing procedure..."

3543:. So why do we have to speculate about something, that has no evidence? And why this stadium of not knowing the real background from the people, who are respondible for the ban, makes you happy? Are we in Knowledge not all dedicated to the principle of easy access to knowledge, so that people don't have to speculate but are able to know? -- 1477:

accountable to WMF management, who signs off on all OFFICE actions, and accountable to elected members of the global community who have the opportunity to review every action. I think that the latter should also be extended to local ArbComs for project-specific actions, to be fair, but the accountability structure is there. --

4656:

the norm. But anyway, there's no reason not to be cautiously optimistic that progress on this front is forthcoming, including but not limited to safeguarding that this incident does not repeat. This has been an enormous distraction, with likely some heavy costs attached to the project. Let's make sure it doesn't happen again.

2065:, in its current form, causes more harm than good. It's far too common for civil POV pushers to engage in tendentious editing and then run to AN/I complaining about incivility the second somebody does a swear at them. If the worst thing Fram ever did was be incivil to ArbComm, they don't deserve one whit of punishment for it. 5959:

be a community process, they should also have come up with an appeal mechanism. I strongly disagree with the notion of an undefendable complete ban with no chance for appeal. I know some wikis do permanent bans with no appeal but we never have on English Knowledge. Any editor who earns a ban or indefinite block

1462:

where that fringe lies. The solution to "long-term incivility issues" is not to place resolution in the hands of an unaccountable group, but to strengthen our own, accountable, procedures. The damage caused to the community by one ban that is widely seen as unfair is more than a hundred "Fuck ArbCom"s. --

5946:

involved, instead of a vague hand wave about the Foundation knowing best. I had a suspicion that conflict of interest between Fram and Arbcom has been a factor recently, and I was curious how Arbcom was going to handle that. I guess we have our answer: the WMF did it for them (apparently, according to

1239:

were not removed. Once the ban is either lifted or expired, Fram should automatically be an admin and the community can take action if it so chooses, but absent evidence that the event triggering the ban had anything to do with misuse of admin tools, I can't think of any justification for the de-sysop?

6086:

unethical and unwise, and not at all conducive to the kind of environment we need in The 💕. Read that again. The 💕. In fact, I daresay that the way this was handled (not the action itself, but how it was handled) was directly in contrast to the values of a community of people wishing to build a 💕.

6075:

If ARBCOM faced a COI issue in taking this issue up, then that is for them to decide. Not to make stretchy legal analogies, but a judge or a lawyer recuses himself or herself--they are not removed from a case by a higher authority automatically to "protect" them. I can absolutely see why ARBCOM might

5847:

ArbCom has, in many instances, had to hear a case which involved a vocal critic of ArbCom, and in some cases parties even criticized the Committee or particular members of it harshly during the case. So, that's absolutely nothing new to any arbitrator. If criticizing ArbCom were a way to escape their

5780:

Regarding "not having all the facts", the one overwhelming fact I do have is that he is free to edit any other project. Therefore, there cannot be any personal-safety-related, child-safety-related, legal-related, or similar reasons. For the same reasons, I am not touching the double secret iban that

4838:

again. Equally, I have plenty of personal experience (from all kinds of settings) of situations where someone has behaved unacceptably, complaints have been made in private (because they can't or shouldn't be made in public), someone has been banned/kicked out/fired as a result, and a bunch of people

4265:

In theory, the Terms of Service either allow or don't allow something. (ignoring the intentional lawyer-mumble such things always have). So in theory, any editor, whether "warned" about TOS issues or not, either violates or does not violate TOS by the same criteria. Unfortunately, Knowledge policy

3373:

All kinds of Office Actions are only carried out after a thorough investigation and after a detailed review by various Foundation employees. This procedure usually takes about four weeks. In the present case, this procedure was delayed, because it coincided above all with the current Improving Trust

3036:

Right, but such an authorized representative allowed to speak for the community would first have to determine what the community has to say. I think that would end up looking very similar to an RFC, with the authorized representative required to read the discussion, determine the consensus, and then

2882:

Ah ok, but they didn't notify WP or Arbcom about the iban? Did they notify Fram about it, prior to the block? Are any non-blocked editors under any WMF sanctions that the community and arbcom don't know about? If yes, I'd encourage them to, at minimum, communicate the matters privately to arbcom.

2650:

Thanks, I think I better understand what you mean now. (And copyright may not be a great example, since it's also a legal issue, and the WMF has always been able to act on those.) However, in the case of civility and interaction with other users, that's also covered by local policy, so in that case I

6081:

I have no issue with year-long bans. I don't personally know Fram at all but I can understand that some people can change with time. Given the alleged nature of the issue (problems with ARBCOM and/or members of ARBCOM), I can maybe even see why you would only ban Fram from enwiki. But WMF still must

5958:

better if the entire Committee is forcibly recused in this kind of situation. I'm not entirely on board with the precedent this sets, but I at least have confidence that the WMF is acting in what it believes to be the project's best interest. But, since this is the WMF supplanting what's supposed to

4442:

does explicitly forbid harassment, but on civility, only says, "support a civil environment," and "we encourage you to be civil and polite," which to me does not seem to forbid the kind of language you might expect to find in PG-13 movies or a typical non-customer facing workplace environment. We've

4420:

Be reminded that the T&S revised the office ban policy earlier this year to allow for temporary and limited-scope ban, previous only global indef ban was allowed. However, I do share your concern in respect to the non-disclosed nature of the bans. With that in mind, the zhwiki community does not

4362:

The most noticeable difference between cases from zhwiki and Fram's case is that no one in the Trust and Safety team nor the Wikimedia Foundation understands Chinese, but somehow they are capable to judge cases in a language that none of them understands, which was like a slam on my face as an admin

4336:

who was banned by the WMF as well, while most local Wikipedians at least consider WMF's banning was an over-kill - they might need blocks/bans but not something like infinitely banning them from all Wikimedia projects. But again, by the time of the bans, they behaved normally. Actually, one of these

4164:

Then resign. Because this isn't accurate at all: we edit at the pleasure of the WMF, who can take away that privilege at any time. And there's no way they're going to hand over all decision-making to this (frankly bonkers) community. So you're not going to get what you want without forking Knowledge

4116:

Why should we care about the names of WMF employees who perform these actions? Can't we just assume that the WMF is acting as a block and then agree or disagree with those actions? I care about protecting the Knowledge community's right to govern itself, not about singling out WMF employees or about

3477:

In this case, although the T&S gave in typical manner of lawyers in "ongoing trials" no details its pretty clear what happened. Janneman was as mentioned a long time editor esteemed especially in english and american literature (his major editorial activity dates some time in the past) and was a

3457:

I am a 100% bilingual, but I often let a machine do the typing. I spent many minutes cleaning it up for syntax, false cognates (and there were a lot of those), etc, but I forgot to think of the names. Thank you for your diligence - it also demonstrates that some people do indeed take the trouble to

3397:

Trust and Safety, as the team that conducts Office Actions investigations, begins all cases by assuming that volunteers themselves decide how to exercise their free time under the terms of use and autonomously within the community within Section 10 of the Terms of Use created by us. The terms of use

3362:

Dear members of the German-speaking community,Several volunteers approached us with questions about the current office action; the Partial Foundation Ban of User: Janneman / Edith Wahr / Judith Wahr in respect of your project. Since we have seen similar questions in your discussion above, we decided

3332:

The most baffling aspect of that specific case was the, in the view of many in German-language's community, unnecessary "extra ban" as a "partial Foundation ban" in that project, after the user was already locally banned. So the WMF suddenly appearing long after the case was thought to be closed and

2722:

being acceptable interpretations of the "Do not violate copyrights" portion of the TOU. Similarly, the English Knowledge implements certain policies related to civil conduct to implement the user conduct portions of the TOU, and takes action (or declines to) when a breach of those is alleged. If the

1277:

indication of the fact that the Office action was poorly thought out and doubly poorly executed. There's already been a lot of pre-emptive talk about another RFA, but as far as I can see, there's no cloud here, just a bunch of obfuscation from WMF which doesn't relate in any sense to Fram's ability

391:

Or, and as I personally think this will how it play out: "Knowledge bans an harasser. The community rebels." or something like that will be the headline, and then the article will talk about the problems of Knowledge with women editors (especially easy to tie into considering many incidents Fram has

5903:

Question: is there a way for admins/oversight to conveniently view all of Fram's revdel'd/suppressed edits and check whether any of them harassed anyone? I agree with the idea of not telling the rest of us who specifically was harassed. The rest of us can check Fram's still-visible edits but that

5758:

Again, NOTHING. Wait, oh wow, now I get it!!! Thanks WMF for the clarification!!!!! Not in any way shape or form. The community now takes precedence. There's nothing here that requires the "office" to prevent harm, that's utter claptrap. Unblock Fram and seek an RFC on the role of the Office.

5556:

It's unfortunate that so far as I know they only knew about the deadline when I finally was able to reach someone in the office, and that was only a couple of hours ago. Give them a chance to make a proper reply, which they've told me they are preparing. I'm sure it will be today now that they know

4732:

they should have done so). There are a lot of things that WMFOffice and the people behind that account should have done, but did not do, instead just claiming everything - even things that wouldn't have implicated ANY sort of privacy issues (i.e. that Fram had been warned twice before and that this

4655:

It sounds like Jimbo and Doc James are actively trying to bring this crisis to a close. Since there has been no further escalation, I say let's give them a chance. I am hoping this tone-deaf interaction with the community on the part of this Foundation role account will prove an anomaly rather than

4576:

Because the Knowledge community recognizes that is not omniscient and sometimes makes mistakes, we have processes in place to recognize and correct those mistakes. If an article is wrongly deleted, we have Deletion Review. If an editor is wrongly blocked, we have a guide to requesting unblocks, and

4367:

I don't even think the Foundation's account WMFOffice will actually come out and respond to public's condemn because the WMFOffice account never made a public appearance on zhwiki at all, and the inquiry email the third user sent out ends up with no reply. They seem to be able to understand Chinese

4343:

Again, no details or diffs were provided in the email saying what exactly you did was wrong. However, the email did ambiguously mentioned several broad scopes of what the T&S team thought what he did was deemed not appropriate, but no diffs. Unlike previous bans, the user who was warned behaved

3380:

The Foundation strives for Office Actions to be as transparent as possible. However, we also balance the privacy and security of all parties involved, as well as legal issues, as provided in the general information section of the Office Actions page. That's why we do not share the information about

2662:

Just because en.wp and the ToU both include "civility" does not mean that the standards are the same or that it is impossible to violate one without violating the other. To use the copyright example, Commons policy is a lot more strict than the WMF ToU provision - it is perfectly possible to upload

2508:

Fram's statement alluded to the fact that he had received two "conduct warnings" from the WMF. I think that's gotten drowned out by the more serious sanctions imposed, but I think that should also be part of the discussion. Is it appropriate for the WMF, rather than the English Knowledge community,

1544:

Yes, the comms should have been better. I hope that conversations are being had within the WMF on how to better communicate these types of actions to the community, and I will certainly follow up with them on that. I'll note that my opinions here are as a member of this community, and are made with

1238:

While many here feel that the decision to ban and block was mishandled, I'd like to specifically discuss the decision to de-sysop. I don't see that the triggering incident had anything to do with the use of tools. I can't think of anything that a blocked and banned editor could do if the admin bit

1207:

a) The Terms of Service are not a legal obligation (of course they are enforceable, I just mean that the law does not require them to be what they are, since otherwise we wouldn't need them). b) The part about handling stuff locally when possible is fine, but they already opted against that; c) If

1064:

From my years of military service, I've learned, never give the agency you're requesting something a chance to deny your request; if the prescribed form has "APPROVE/DISAPPROVE", and you want it approved, always pre-circle APPROVED before you ask them to sign it. That being said, I think you should

1005:

the WMF is permitted to take office actions, in order to protect the safety of users of Knowledge and enforce the Terms of Use and other legal obligations, or in order to enforce local and global policies, when local processes have failed or the disclosure of details to local processes could pose a

910:

I have, on various occassions, spoken with the press about government programs where I worked, and about a private organization I belonged to. (The instances when I spoke to the press about my places of employment were with the approval of my supervisors.) Be warned, you cannot control how what you

227:

What people want to do is ultimately their choice but a reminder that it can be quite difficult to predict how the press will see things, even if you get them interested. They may see things the way you outlined, or maybe they will see things differently when someone (to be clear this will never be

5862:

We needed actual, usable information, not more canned non-responces. Right now, Fram has told us more useful information in a single paragraph than WMFOffice has told us in two replies, which is more an indictment of WMFOffice and their legal team than anything else. If you want us to get on board

5695:

The issue is...well, many but primarily the interference in a local issue and a manufactured crisis (a la Trump's border wall.) They shouldn't be claiming this was some egregious abuse and an issue of trust or safety, or both but that it somehow doesn't exist on other projects and won't exist in a

4604:

And when the WMF ignores that statement entirely, then enwiki should boycott the next annual fundraiser, including blocking the WMF's advertising banners for it and/or ensuring that each one is accompanied by an enwiki-wide banner that explains the community consensus to boycott the fundraiser and

4580:

When it comes to the WMF Trust & Safety team, however, I am unclear on what the process is to deal with a mistaken action. The answer appears to be "We do not make mistakes. Therefore, there is no process for correcting them." That is, to put it mildly, disturbing, and in my opinion is a large

4371:

The T&S team is exactly the opposite of what Knowledge's transparency: every log is traceable and will keep forever, we don't even have a way to PM others, and almost all discussions are visible to everyone. The true irony is the English Knowledge (and global north) Knowledge community stopped

4317:

were banned by the Foundation in 2017 and 2018 respectively. These users are probably the most controversial Wikimedians contributing Chinese Knowledge, with their block (by "block," I mean blocking from editing by local administrators instead of WMF) triggered countless discussions and arguing on

4140:

by the community to handle tricky stuff. I will not accept unimpeachable decisions from nameless bureaucrats (not meaning our own 'crats, of course) that never were elected. Whatever Fram did or didn't, whomever filed a complaint against them, all that is irrelevant to me. It's the process that is

2735:

I'm going to look at this from another angle, if I may, Seraphimblade: those conduct warnings were issued upon the action of a Wikipedian-in-Residence, or following some sort of monitoring system for WiR. I can tell you, for sure, that the Foundation would not do so if you or me or some other poor

2689:

If the standards are the same and the evidence available is the same then there will never be a reason to disagree with the community decision. If the standard is different and/or the foundation has relevant evidence the community does not and the foundation judge that it breaches the terms of use

2677:

Like I said, copyright violations are a poor example, because they also implicate legal considerations. So, take promotion/advertising, which both English Knowledge policy and the TOU prohibit, but isn't against the law. We could legally allow people to post all the promotional material they want,

1461:

On the contrary, the real problem with "not addressing long-term incivility issues" is that you won't find two enwiki editors who will consistently agree on most of the issues that get labelled "incivility". There is no "fringe of what's acceptably CIVIL", because everybody has a different view on

1031:

an independent panel, including one (1) member of the Trust and Safety Team (T&S), one (1) member of the Community Relations team, one (1) member of the Legal team, one (1) member of the Board, three (3) members elected globally by the community, and one (1) member of the Arbitration Committee

1012:

the WMF should refer to local processes any complaint it receives that they could effectively handle, share with Stewards and any relevant local privileged users, such as the Arbitration Committee and Check Users, as much information as legally and safely possible regarding any office actions, and

558:

The question is, will the WMF forcibly prevent us from doing this, by, say, threatening to ban anyone who makes that front page edit? (Or by bringing "SuperProtect" back from the dead?) I don't know the answer to that. Is it worth trying, assuming that after the June 14 board meeting the situation

356:

I mean, no-one outside (a small slice of) the Knowledge community is going to see this as a problem. No-one else cares enough about the sanctity of Knowledge processes - to everyone else it just looks like the WMF banned someone for persistent antisocial behaviour, to which they'll probably go ...

4904:

Things are getting removed from this page to other places, and the discussions are widening with some repetition, so please excuse my making this a response to you rather than in a better place; I looked for one. The WMF exhausted my assumption of good faith a long time ago. This is totally about

4699:

What Grandpallama said. Established admin editor making a disclosure (however unreliable it may be) vs. faceless entity enacting a one-year ban and following up with non-responses. Fram could be literally any other editor (including an LTA) and this whole process would still leave a sour taste in

4277:

happen - it is conceivable that an editor could be told that he is "just short of the line" (but here it is, and it's not moving) or "given a pass just this one time" (implying that only behavior of equal severity or worse will trigger a ban). The question here is: does WMF stick to that, or are

3564:

You are right, sorry for the speculation, I have no evidence to suggest that Janneman did something wrong exept for the onwiki-things described above. What I meant to say is: Before the current case opened my eyes, I trusted the WMF-office account more than I did trust Janneman. If the WMF-office

3538:

I did not want to discuss the case here in detail, because it does not belong in this project. But you pinged me and made some speculations, that do not seem to have much insight in the case. I know the past development of Janneman and the reason of his growing dissent to the project in detail, I

3238:

The WMF has at least two other responsibilities: developing MediaWiki software, and establishing communities of editors in other languages. Furthermore, due to the whole "paid editing" thing, most WMF members aren't active editors, here at enwiki or on any other wiki. Doc James is on the board,

819:

Can this actually be carried out - is such a banner within community control? I remember when the community wanted to place a banner/logo across the main page in celebration of achieving 5 million articles on en:wp, and the WMF came along and told us we could only have it up there for 24 hours (I

550:

We know we do not have the power to override the WMF's bad decisions with unblocks or resysops, at least not in the long term; they run the servers and can block and ban and desysop whomever they wish. The only power we as a community have is our words. We can say what's troubling us about what's

451:

There was no attempt to make a narrative that Fram was a sexist harasser until the Chair got called out for having a COI that motivated the ban. Raystorm's narrative is not credible. You can't bury this as "Gamergate". The fact that the Chair would employ the "sexism" defense after a female admin

1476:

Agreed, the enwiki community has repeatedly demonstrated its inability to deal with long-term incivility issues. Just because the community can't agree on the extent of the problem doesn't mean that the problem doesn't exist. The WMF is setting the standard. And the WMF's process is accountable:

611:

to harm the WMF or its reputation. The WMF shares our goals of having a successful community-governed 💕 project. They're on our side. This is not a war, it's an internal disagreement about delegation of certain responsibilities. The WMF leadership is quite clear on the fact that they do not run

516:

To the naysayers: The press is interested in conflicts of interest and scandals at WMF (which is no stranger to them), and to lack of transparency at WMF, and to scandals/conflicts this massive within Knowledge. Another point to consider is that, generally speaking and historically, WMF does not

281:

Whether or not it's a good idea (as to my feelings on that, let's say it certainly won't be me calling up the newspapers), I think this is a bit too "inside baseball" at this point for them to care about. If it turns into a bigger blowup, with multiple desysops or bans, that might be significant

4324:

As the message from the Foundation suggests, the ban on Fram was only limited on English Knowledge, partly because they updated the terms which allowed them to do so. However, these two users I mentioned were banned entirely from all Wikimedia projects even though both of them mostly contribute

3827:

So the enwiki community can harass them like they are Laura and Raystorm? No. I applaud the WMF for taking reasonable measures, such as the use of the WMFOffice account, in an attempt to shield their employees from the toxicity of the enwiki community at this current time. It is a credit to the

3428:

I suppose that's a machine translation? For it also translates the names of Janneman's other accounts "Edith Wahr" and "Judith Wahr" into English, which doesn't make sense... I fixed this part and added "machine translation" for clarity; if it's actually a human translation, feel free to remove

405:

I think getting anyone outside of Knowledge interested in this is sort of a hard sell. "OMG the WMF banned someone!" "Why did they do that?" "It's not exactly clear but something to do with harassing someone and telling people to go fuck themselves" "Ok why are you protesting?" "Because the WMF

1559:

Good luck with that. WMF and better communications is rather oxymoronic. In any event, the communication needs to start before the action, and the LauraHale links supplied by Fram appeared to have nothing to do with civility. If civility is indeed at the heart of this, Fram's statement doesn't

5945:

I know this isn't exactly going to be a popular statement given the current environment, but here goes. I, for one, appreciate this new, more detailed statement, which actually seems to make an effort to explain the situation and address various concerns while considering the privacy of those

373:

You're blind if you think the media wouldn't pick up a story about this shocking and unprecedented rebellion by Knowledge's editors against the WMF, in response to clear corruption coming from a supposed humanitarian nonprofit. This is probably the biggest scandal Knowledge's ever seen since

6085:

We deserve an apology, and frankly, if Fram is a decent enough person by your measure to receive only a partial ban of 1 year, then Fram likely deserves an apology as well. You cannot document every single bit of evidence that went into this decision, we get it. But saying nothing at all was

3501:

Just a clarification: Janneman/Judith Wahr used completely inacceptable words against that user, but he did not actually "threat" them, that is, he did not use words threatening to do something to them; what his outburst contained was, when read literally, a request to the user to do harm to

2717:

Alright, then I think we just fundamentally disagree in that case. I do not think the Foundation should be using "TOU" to overrule local community decisions, as community policies and practices are that community's interpretation of how the TOU applies there, as with your example of Commons'

2083:

I concur that "WMF can't allow Fram to expose them to liability." We don't know what happened, and until we do, what we all know is that Fram has frequently crossed the lines of the widest possible gray area into some truly vicious behavior. I do think WMF needed to present a less weaselly

2446:

One possible source of legal liability is if the WMF says "you can email us confidentially", and then they violate that confidentiality, that could result in getting sued. Hence, they won't tell us who made the complaint, and they won't post diffs because the diffs would reveal who made the

3964:

if they are filed there. That doesn't mean I don't condemn it, though, as you do. I'm sorry that you are feeling disengaged from the community and want to leave - your contributions will be missed if you do. Perhaps I'm a deluded optimist but I continue to believe that most people here are

3812:

to review postings? Do they have to provide expedited access to official or covert government agencies to make these decisions? Are they subject to a coordinated program of censorship with other social media that requires a uniform business model, terms and conditions, and procedures for

5398:

I'm appalled by what the Foundation did here, but I doubt they never prepare for consequences. The way we've probably experienced it is that when they do bother to try to anticipate the consequences of their actions, it leads them to moderated measures which aren't seen as objectionable.

4773:

off-wiki evidence (if there was), without revealing anything about what it was. That would have at least indicated the need for private handling rather than community review. The second was attempting to usurp the community, and by now, after VisualEditor, after Superprotect/MediaViewer,

4282:

of their policy seem to be wholly unjustifiable, since all they will do once they get properly under way is increase editor turnover to the point where everyone gets warned once, then knows to leave. (except for the paid editors who have a support team to back them up in their good work)

5781:

apparently exists, because that is, indeed, something I don't know enough about. But with a project-specific ban like this, there is no possibility of lasting damage to an unblock now, and going thru local processes is an option if whatever the problematic behavior was continues. --

2133:, to summarize, you are saying that Fram is hiding some stuff and/or lying, (when he says that his dealings with T&S have been limited to those three episodes), thus preventing us from gauging the true extents of the alleged misdeeds, which led to his ban. Am I correct enough? 4302:

Hi there. This is Yan from Chinese Knowledge. I would like to share two WMF-imposed bans on Chinese Knowledge. These cases share many similarities so I hope sharing them here will lead to a more in-depth discussion for Fram's ban and hopefully the WMF's banning policy in general.

4665:

I still don't know on what basis people are confidently stating this action was a mistake. There seems to be a quite a lot of assumption that anything done on the basis of non-public information is automatically an error, and quite a lot of taking Fram's word against the WMF's.

2736:

sod had to deal with this mess. Now, I'm no firebreather, but, suffice it to say, I have questions regarding the propriety of the WiR system, insofar as improper Foundation influence is concerned; and, quite frankly, about the propriety of paid editing overall, including WiR.

541:

You want press? Here's what you do. Gain a consensus for adding a small banner to the top of the main page for, say, 3 days. Give it a compelling title like "The Knowledge editing community is under attack. Click here to learn more." Link that to an information page that

1137:

Agreed, we need not be obsequious in our entreaty. I tend to initially be over-tactful when I surmise the possibility of retaliation from the other side and softened language can be more diplomatic in the long run; but by no means am I stating we need to grovel, either.

4340:

Another Wikimedian on zhwiki, who is a close college working with me on China's Knowledge community recently got an email from the Trust and Safety team, saying this is a "conduct warning" and he told me the context of that email suggests this is a type 2 warning.

6118:

BTW, just as an aside, I stopped taking any of this "statement" seriously after the first phrase: "Over the last few days ...". Can't these people get even the most basic facts about their own actions right? The ban was enacted a mere 24 hours ago. Seriously... –

2942:

As has been mentioned numerous times, neither ARBCOM nor the WMF are intended to represent the interests of the editing community (such as the community's interest in due process for disciplinary measures). Perhaps it is time some organization existed to do so?

1032:

from each project on which the targets are active (or a locally-active Check User or Steward if no arbitration committee exists), be called to review and approve each office action and prepare a statement to be released to the Community regarding the action; and

6082:

understand that performing an action of this nature with a newish policy (and who instated that policy again?) on a well-known editor, without any documentation or explanation of why, was foolish, inconsiderate, and disrespectful to our community here at enwiki.

3261:

Arbcom does this to an extent, and there are WMF Liasons editing, plus some active editors are board members, plus there is Jimbo. Jimbo and Doc James are pursuing discussions right now and I hope some good comes out of it. But we have to think about the

4684:

be more transparent about in terms of their decision here that they haven't been. There've been a number of pointed questions about procedure and process that have been ignored, which could have easily been answered without getting into particulars here.

3037:

act on that consensus. In short - we already have that, with the "authorized representative" being whatever admin or experienced closer closes the relevant discussion, and the "speaking on the community's collective behalf" being the closing statement.~

1792:

The ban being only on one project is the part that leaves me the most baffled. Hazarding a guess, Fram might not be active on other projects (I haven't checked), the one who raised a grievance might only operate on WP:EN, or there might be jurisdiction

4843:

never had a problem with him", or "it's OUTRAGEOUS due process hasn't been followed", "But what about ALL the vital work they do?", or "ZOMG conspiracy, someone is out to get him". So I am fairly open to the possibility that that's what happened here.

2905:

The WMF certainly has the right to issue conduct warnings and punishments, even when there is an existing community with their own policies and guidelines. If that existing community is not enforcing certain points of the TOU themselves, the WMF will,

5535:

No new information. No decent justification. Not good enough. I suspect there is a large element of score-settling going on here - we know Fram has had interaction with someone in a relationship with a member of WMF, let alone his role as a critic. -

546:

lays out what has transpired so far, and asks readers to help by signing a petition to the WMF, or contacting the WMF to express their views, or some other appropriate action. One of the many, many journalists who use Knowledge will see it and click.

3828:

Foundation that they are respecting the duty of care they owe their employees by preventing a single individual employee from facing widespread harassment for merely publishing a statement that is coming from the WMF as a whole. Perhaps reflect upon

4596:

My guess as to what the WMF will say: Many, many words that say absolutely nothing and boil down to "None, because we are infallible," even though Jimbo and others have pointed out that there is always the last-resort appeal to the Board (via him,

6047: 4198: 3676: 4483:

I am just catching up to what happened and I am speechless. So many thoughts right now (and sadly no time) to express them, but the fact we already lost 4 admins (Fram, Floq, Ansh and Rob) with 5th being in danger for desysop as well now....oof.

5726:

of harassment. If putting maintenance templates on two pages constitutes "harassment" worthy of an IBAN, I think their definition is suspect, to put it about as politely as I can. (The product of a bull which is not a steak comes more to mind.)

4352:

The third case which a user received "conduct warning" sent an inquiry email with no reply; the first two cases were set, there was someone wrote to their email and did get replies, but there was still no meaningful information contained in it.

4768:

Exactly. Even if it turns out that banning Fram was indisputably justified, the WMF still made at least one error here, perhaps two. The first was in communication. Without revealing any private information, the WMF could have said that there

2467:

Fram "exposed them to legal liability", regardless of what he has told us, can you point to some edit he made that has recently been revdeleted as an Office Action? I mean, if the comment invites liability, they would have done that, right?

5863:

with your (increasingly) ludicrous ban, you need to both give us a valid explanation that doesn't encroach on any privacy rights and you need to quit it with these asinine responces that only seem to serve the purpose of riling editors up. —

2778:

So, said WiR was on the radar. That resolves one question. Thanks, Winged Blades of Godric; I appreciate the explanation. I mean it. The other question, however, remains up in the air, but probably isn't a topic to be fully explicated here.

2548:

WMF hosts the servers, pays the bills, and has a multitude of legal concerns that come along with hosting Knowledge. Of course they have the remit to police what they own. Like it or not, the TOS overrides the community consensus on on-wiki

1637:, that may be the case. But we as a wiki have NDA'd users who could be informed of greater specifics and give a statement to the community. I don't know whether or not the ban was the correct result, but I do have problems with the process. 5874: 5509: 98:

or CNN online, etc. would love to hear how WMF is overriding/ignoring/bypassing long-established Knowledge procedures, unilaterally blocking/banning/desysopping long-term admins in good standing, and refusing to openly discuss the matter.

3369:

As described in the Meta page on Office actions, we investigate the need for an Office Action either when we receive complaints from the community or when it is required by law. In this case, we reacted to complaints from the community.

1525:... accountable to elected members of the global community, who are out of touch with the community, (how else, will we push our pet civility-police efforts?!) and one of whom even asserted to Tony about how Fram's block was superb ..... 5588: 5923:

the WMF post sounds like a statement of no confidence in the community. We probably have to respond to it on that basis. (Btw I don't have much confidence in the community either, but it has a better track record than the WMF does.)

4452: 4389: 5603: 5545: 3959:

Well, speaking for myself, I am at work today and just dipping in and out of this discussion. So unfortunately don't have time to investigate and bring action right now. I will look in more depth later, or support motions to block at

2340:

If WMF provided some clarity beyond this vague "there were complaints a month ago," response, we might be able to adjudicate this. Absent that though, all we can say is this is a poor example of transparency in policy implementation.

3866:

Respectfully, what actions have you taken today to bring a stop to the harassment of Raystorm and Laura? Where are the blocks? Warnings? Discussions? If the community does not address these issues, they are complicit as a whole. ~

1372:

The community should probably be concerned about the implications that the WMF had to step in to enforce the TOS- I agree with whoever said this shows the WMF doesn't have confidence in the community to enforce compliance with the

4331:

Claim these two users controversial is because, if we held a request for comments on Chinese Knowledge by the time of those bans, there wouldn't be most people opposing the ban like Fram's case on this page, and there wouldn't be

4266:

has a bad habit of telling any editor caught doing 60 in a 55 mph zone that now he has to drive at 45 or less. We don't do that IRL because it is designed to fail (except, of course, in the probation and parole system, where it

6029: 4477: 3645: 2628:

Copyright violations are also against en.wp policy. When we block editors who repeatedly violate copyright we are enforcing en.wp policy not the ToU. That some actions violate both en.wp policy and the ToU does not alter this.

470:

Sorry, I totally missed where the "Chair got called out for having a COI". I thought part of the motivation for the office taking action rather than ArbCom was the conflict of interest with our common. Is this something else I

517:

particularly care about editors or administrators or what they need and want (this entire saga is a case in point), and does not really care about the quality of Knowledge articles or whether the mainpage is updated. What WMF

751:

If we all unite against the WMF's decision and protest via a banner and petition on the main page, then they will be pressured into unbanning Fram, because at the end of the day, WMF relies on us all to keep Knowledge alive.

3813:

enforcement, as well as a gag on their motivations and procedures? Yeah, they're not going to answer those either. But my paranoia can, and my paranoia is more reliable than most other sources of information I have here.

3688: 2412:

Not a legal issue per "or as required by law. In this case we acted on complaints from the community.". Wouldn't be a liability issue if they produced a list of edits as the reason for the block. So no that defence doesn't

3539:

also have read the rant, he was blocked for, and it gave a legitimate reason for the block in de-wp. But I don't know of any evidence, that there was some kind of off-wiki incident after, and he denied that explicitly in

5111: 1843: 6064: 4292: 6126: 4297: 1446:

Ah yes, the long-standing justification for not addressing long-term incivility issues on enwiki: there are other bad/worse people. They only need to do enough to start a cultural change, not do it all themselves. --

976: 3743: 2826: 2591:

Enforcement of the TOU is something that the WMF and only the WMF should be doing. Accordingly breaches and near breaches should met with warnings and bans (as appropriate to the individual situation) from the WMF.

5491: 3897:

I had a look at their talk pages and the histories of those, but only see polite notices that they have been mentioned here. Please give me links/diffs where the harassment takes place and I'll see what I can do.

3618: 81: 76: 71: 59: 4600:

What the community should say in response: "Well, then, it's time for the Board to fire you, install a new set of T&S people, and institute a formal method of final appeal short of demanding action from the

4126: 2960: 2795: 2773: 2350: 1418:

A sensible comment. It's no secret that Fram has had a long-term civility problem. The community (and ArbCom) should be considering how to better enforce that policy in the future so the WMF doesn't need to. --

6144: 2166: 2146: 1554: 1539: 1410: 1090:- This phrasing maintains a friendly tone to ArbCom, while reframing the WMF aspect as something that it will benefit from. I don't love "RECOMMENDS", so if you have a better word, feel free to just change it. 3194: 1869: 1132: 893:. As others have stated here, this issue is not accessible enough to the average reader for a main page banner to have any effect other than to sow confusion. cf Seraphimblade's first comment in this section. 212:

Let's face it, unless WMF reverses course immediately, this is going to hit the press sooner or later. Plenty of journos watch and report on Knowledge, and a scandal this big is very hard to keep under wraps.

5933: 4255: 2800:

Wikimedians in residence prove just how unfit for purpose all of en.wp's focus on (undisclosed) paid editors rather than non-neutral editing is. But as you say that's very much a topic for a different place.

2203: 2182: 5777:

That response had essentially no content. Consensus is clear, and Fram said yesterday "Any non-violent action taken by enwiki individuals or groups against this WMF ban has my support", so I have unblocked

3495: 2387:

The only thing that is clear is that WMF have acted incredibly poorly. If the smoke you describe isn’t even actually smoke, it’s worse: WMF have acted negligently and people should consider their positions.

1786: 876:- At this question, while there are questions about process, it is unclear teh reason for the block and therefore we are not in a position to directly go against it. Also, press just won't help anyone here. 5913: 3774: 3623: 3415: 3312: 3168: 2257: 2243: 2229: 1518: 6095: 5379: 3393:

Because the Partial Foundation Ban is the result of a regular office action investigation, it is subject to the same rules that are known by the Foundation Global Bans: there is no possibility for appeal.

2892: 2837: 2316: 1770: 1755: 1727: 1692: 1666: 5365: 4210: 3342: 3275: 3219: 2542: 1287: 1221: 6052: 4802: 4788: 3795: 2877: 2586: 2397: 337:

Most news websites have a contact us/submit a tip link somewhere on their front page. I've already submitted a couple of tips to my favorite technology news websites, I encourage you all to do the same

292: 5979: 5967:

as an appeal mechanism, and so the Foundation's block in this case goes against one of our fundamental best practices. I would appreciate if the Foundation would reconsider the parameters of their ban.

5772: 5456:

Thanks to Black Kite for hitting me up on my talk page; I checked this page for WMF input at 18:58 and was about to hit the button. I'm not an idiot or a jerk, so I'll hold off until we get this info.

4829:

Definitely not arguing the WMF has handled this perfectly. Even if it was appropriate for them to do this as an office action rather than via Arbcom, I certainly agree that more communication probably

4030: 3452: 3256: 3233: 3150: 1202: 1188: 1167: 1147: 1099: 1082: 530: 251: 222: 5896: 5611:

I mean, honestly, what would you expect a "good" statement to look like in a case that we now know involved harassment? "Here's the diffs so people can go harass the person who reported harassment"? ~

5011: 4473:

Clearly just unfamiliarity with the tools when resetting the block but it does make them look less than competent with the use of the blocking tool. I have asked the office d to clarify their intent .

4468: 4174: 2752: 2651:

would assert that the WMF should respect local decisions in regards to them, including a decision to take no action at all. (Unless there were also a legal issue there, such as an actual court order.)

2497: 1305: 829: 637: 5996: 4547: 4058: 4044: 3843: 3118:

What do you mean by the community? The people who shout the loudest? Because that's who makes most of the decisions around here, but that certainly isn't representative of the entire editing body. --

2699: 2684: 2672: 2657: 2638: 2616: 2601: 1996: 847: 652: 5854: 5733: 5527: 5393: 4999: 4561: 4404: 4150: 4007:

A secret trial, with secret and unaccountable judges, no opportunity for the accused to defend themselves, secret accusers, secret accusations, secret evidence, and to top it off, no appeal possible?

3669: 3327: 3104: 2569: 2441: 1933: 1875:

At 84 edits, you're not "involved". Jumping right into an ArbCom statement from years away with under twenty edits means you're bullshitting hard if you're claiming Rivselis is your primary account.

1323: 794: 739: 718: 585: 274: 237: 207: 6109: 5447: 5195: 4752: 4694: 4529: 4507: 4430: 4102: 4084: 3992: 3533: 3515: 2929: 2049: 1982: 1646: 1334: 915: 690: 670: 590:

I don't think that they would. But should things devolve further, I think that this is the best course of action: it remains civil and is more effective than wheel-warring the site into oblivion. --

366: 310: 154: 129: 17: 6013: 5790: 5566: 5257: 5243: 5211: 5070: 4957: 4824: 4709: 4493: 3467: 3438: 2810: 2035: 885: 349: 5705: 5686: 5659: 5639: 5351: 4914: 3907: 2368: 2074: 1814: 1038:

the position that the WMF should forthwith conduct an investigation into their communication practices and take appropriate measures to assist in improving communication regarding office actions.

932: 138: 5819: 5408: 5080: 4864: 4462: 4187: 3979:

Really? I have nothing against you, but you were an admin up until yesterday, and if you felt those actions needed to be taken against certain editors as a result of their behavior on this page,

3822: 2459: 2124: 2098: 1918: 1888: 1428: 868: 811: 602: 503: 484: 386: 5835: 5677: 5622: 5313: 4680:

In fairness, that's in large part due to the fact that WMF hasn't said much. Even those who are arguing for privacy over transparency should be able to acknowledge that there are things the WMF

4648: 4346:

He replied T&S's email, with no reply or further explanations at all, even he said his email asked several answer-able questions that won't be too difficult or requires privacy information.

2362:

The lack of clarity has poured fuel on the fire, I can agree with that. But there may be safety concerns and legal issues we don't know about. There's enough smoke, we know something blew up.

621: 434: 326: 6165: 5129: 5042: 4853: 4675: 4614: 3974: 3940: 3878: 3861: 3574: 3552: 2984: 1971: 1569: 1500: 775: 761: 193: 47: 5466: 5143: 5053: 4898: 4590: 4075:

Arbs are accountable to the community, WMF is not (or at least feels it's not). And just informing them that an action is being prepared without any details is not what I had in mind above. --

1613: 1599: 1486: 1471: 1268: 1049:

I think this captures the ideas discussed on the talk page, but I'm also open to modification. I intend this as a middle line between going bonkers and blindly trusting the WMF in perpetuity.

417: 5429: 5320:

What does "shortly" mean in your lexicon, please? I assume you posted this because Floquenbeam is set to unblock right about... seven minutes ago. If you want to prevent that, please specify

5295: 5284: 5164: 4975: 4723: 4260: 4234: 2422: 1949: 1456: 1441: 5747: 3080: 3050: 3029: 3007: 2477: 949: 460: 5485: 5332: 5181: 4660: 902: 3804:

Assuming they won't do that, I wonder if they would tell us whether they intend to limit access to the account and control over the "Trust and Safety" bans to personnel within the actual

5275: 4049:

It was mentioned to Opabinia in such a way that she did not feel a pressing need to follow up, and buried in the minute notes for everyone else. That doesn't feel robust enough to me.

2729: 2519: 4889:

I take Fram's word against the WMF's because I have observed and interacted with both of them for the better part of a decade and have found Fram to be more credible. Simple as that.

3387:

The investigation took into account the community's discussions late last year, as well as the fact that not all three of the person's accounts were affected by the community block.

2577:

I have not received them, but I believe that there may be cases in which they are appropriate, such as if the WMF has received a cease and desist about a particular user's behaviour.

4218:+1 to Randkitty. AFAIK, I've had no intereaction with Fram, good or bad, nor ever even crossed paths, so I've no way of knowing of any bad behavior. The handling of any, given there 3594:

him as a community on 22 November 2017. Whose brilliant idea at WMF was it to waste two more months "investigating" him before concluding that yes, in fact, he should be banned, and

2883:

I can understand if Fram didn't do that though, given Fram's apparent dim view of Arbcom. I note that Fram made good contributions to several arbitration cases in the past though.

4327:

The Trust and Safety team failed to give any reason, not even exact edit diffs which Fram received from previous warnings. Additionally, both users were banned without any warnings.

3297: 1250: 3624: 3520:

As someone active in the German-language Knowledge but not involved in the case of Janneman/Judith Wahr I would like to explain why many editors like me (with few exceptions like

5904:

leaves the edits we can't see. I've seen the occasional abrasive discussion post or obsessive argumentation from Fram but don't remember anything that would rise to this level.

4934: 4222:

any, is deeply troubling, especially given the sense I've gotten in the past of indifference to complaints & unfairness of (supposedly) fair processes--& those were the

2831:

Fram's statement on Commons indicated that the WMF had placed him under an interaction ban with a WiR because he placed maintenance templates on two articles which she started.

1588:

ask them five questions: “What power have you got? Where did you get it from? In whose interests do you exercise it? To whom are you accountable? And how can we get rid of you?”

1058: 568: 4093:

A meeting, it should be noted, was held at 1AM EDT (6AM BST). On a worknight. I wasn’t there due to the timing, but it certainly wasn’t anything brought up in alarm on-list.

3443:

Addition: As the rest of the translation looks fine and quite natural, I removed "machine" from the heading myself, probably translating "Wahr" as "True" was just a mistake?

4005:

Rob, I agree with everything you say about harassment and I also agree that the level of aggression and foulmouthed abuse being hurled around is too high here at enWP. BUT:

4963: 4605:

links to WP:FRAM to explain why. It's becoming increasingly clear that the only way to get the WMF to listen to the community is to hit 'em where it hurts... the wallet.

1378:

The fact that the WMF statement doesn't really go into detail isn't surprising at all- WMF isn't going into specifics if it's going to give ammo to a potential plaintiff.

2040:

Agreed that the WMF should have handled the comms better on this. There should be a middle ground between avoiding liability and letting the community know what's up. --

108: 5280:

Odds: More boilerplate 5/6; More boilerplate with some information we didn't actually know 2/1; An actually good explanation of their actions 5/1; Fram unblocked 10/1.

3928:

We could start by archiving the section, as Raystorm has clarified she had no role in the decision to ban, rendering the section irrelevant to the overall discussion. –

3057:

I believe the idea is that the community selects this person (more likely a group of people) based off what they and not without guidance. Based off the statements from

4013:

practices. At a minimum, ArbCom should have been informed, with Fram being allowed to defend themselves, again at a minimum, by email to the Arbs. It's not so much the

3208:

We have active editors on the Board, and Doc James (will bring it up next board meeting) and Jimbo (investigating) are working on trying to get to the bottom of this. —

3185:: those who are loudest often think they "represent the community." The only way to find out the "will" of the community as a whole is to poll ALL of us anonymously. 6091: 6039: 6021: 1340: 4375:

The T&S team did more than banning users. (UPDATE: I just saw someone shared a similar ban on dewiki above.) But I don't feel like sharing more at this moment.

3722: 3718: 3714: 1019:

the WMF to brief the English Knowledge Arbitration Committee and the Board of Trustees of the Wikimedia Foundation regarding the office actions taken against Fram;

3693: 1176: 5425:

Whatever you do, please don't think you need to respond just because the masses are lining up by the door. Respond because we want transparency to what happened.

4350:

It's also worth mentioning that, in all three cases on Chinese Knowledge that I know so far, T&S repeatedly use "privacy" to deny any meaningful explanations.

3725:

identify themselves and who they represent? For transparency and accountability to the community. Also requesting future identifications while using the account.

3129:"The community" is a group of people, with size somewhere between me and everyone with a Knowledge account. If there weren't such obvious issues, I'd suggest a 2606:

I don't understand the assertion that that "enforcement of the TOU" is something that "the WMF and only the WMF" should be doing. For example, the TOU prohibits

6004:, I agree - I mean, I would like more information, but I can see how that would be difficult while keeping the identity of the complainant(s) etc confidential. 4793:

I'd say there is a third significant mistake in not realizing that an explanation, of some greater sort, would be needed to accompany the initial announcement.

3809: 3283: 2937: 5356:

Amazing that they’ve had hours to respond, as humans would, but leave it until two minutes before Fram is unblocked. This is fucking literally unbelievable.

282:

enough, but I'm not sure they'd understand "Well, they banned someone, and they're allowed to, but only because they gave themselves the authority, and they

6087: 5696:

year. It's an overreach. I'm no fan of Fram's behavior but it's hardly the worst thing that's been said on Knowledge by a generally respected user/sysop.

5384:

The Foundation has never been prepared for the consequences of its actions, I see no reason to suspect that they would have changed their ways for this.

802:- Right now, this is premature. That said, if this is not resolved within 12 hours of the board meeting on the 14th, this is the best possible response. 4333: 3591: 400:

puts it extremely well as to how an ordinary person/journalist, who haven't been exposed to the community's constant downplaying of abuse, would see it.

396:

effors by women editors and such similar things) and paint a picture of a WMF that is attempting to "fix" issues in the community but is being stymied.

492:

I now see that this is a reference to a huge section that was removed from the page. Not sure that was a good call, but that was done by someone else.

2663:

an image to Commons that breaches that project's policy but which is perfectly acceptable according to the ToU (e.g. every fair use image on en.wp).

5498:

We take these actions only in situations where we believe no other option is available that will preserve the health and/or safety of the community.

911:

say, or the information you point to, is used by the press. I particularly cringe at the memory of how one of my quotes was used in an editorial. -

820:

think that was the timescale). I thought it outrageous interference at the time, but everyone else just toed the WMF line as if they had no choice.

5719: 4835: 4778:. They have had that experience; they know that is going to cause a huge, massively damaging storm, they know not to do it. (At least I damn well 783:

as counterproductive. Most people who're on the Main Page generally aren't the sort of people who would have any interest in the backstage shit. —

4945: 6149:

Since we know that they told some people in advance (though we don't know exactly how much they told or to whom), we can presume that at least

4243: 3703: 1761:

OK, I'll try and be nicer - your gut instinct is of no value. It might be right, it might be wrong, but deductions based on it are pointless.

1604:

I don't lack any information about this case or how the "community" feels about it, I just happen to disagree with the majority sentiment. --

940:

pending the outcome of the meeting on the 14th. If that goes sideways, I'd likely support something like this (wording may need some help).

559:

has not improved, or has deteriorated further? I don't know the answer to that either. But if you want press coverage, that's how you get it.

6043: 6025: 3133:; the lack of any remuneration to define members, as well as the multi-national jurisdiction make anything that formal deeply problematic. 970: 2610:

Does that mean we ought to quit deleting copyright violations and blocking editors who repeatedly upload them, and leave that to the WMF?

6100:

In such cases in the past, Arbcom referred the issue to community sanctions processes by explicit motion. The T&S action was absurd.

5022: 4344:

quite well on Chinese Knowledge, with no bans or even warnings from local users/admins against any problems mentioned in T&S's email.

2173:

Looking back into the past, via links given above, it seems Fram's explanation, even if all of it was true, was far from being complete.

1586:), or at the very least in contravention of the spirit of them. There is nothing accountable in what you describe. A great man once said 4278:

they judging editors they 'warned' like Fram more harshly than they judge un-tarred editors? If they do, then the protestations of the

145:

I sincerely hope that anyone speaking to press about this does so with care and neutrality; the question seems to imply a lack thereof.

5266:

Give credit for realising the urgency, and that communication, even a placeholder if that's the best they got, is absolutely needed. --

3483: 1193:

Many minds tweaked the petitions and supplications of old after a brilliant laid a more than suitable foundation. Good work yourself.

1013:

publicly disclose, except when prohibited by law or precluded by safety concerns, which policy was being enforced by an office action;

4537: 2304: 2284: 1120: 521:

care about, individually and collectively, is its reputation(s), and its/their money. Both of those are affected by public exposure.

4458:

Yet again, EllenCT nails it. Strange that after a billion bytes of argument (including mine), it can be summed up in one paragraph.

4571: 1025:

that the English Knowledge Arbitration Committee pass a motion expressing their support for the office actions taken against Fram;

626:

To be blunt, we're not the ones doing the reputational damage. The WMF is by botching the handling of this as badly as they have. —

4925:

And in the latest developments, WJBScribe has restored Floq's admin permissions. Personally, I agree strongly with that action. --

4815:

At least then the recurring comment I am seeing here of a systemic problem on Knowledge re: "the unblockables" can be validated.--

5594:

Welp, we've gotten the new statement, which is nothing but more boilerplate with no new information. Exactly what we expected...

3710: 4834:

possible and would have avoided quite such a raging trashfire of a discussion. Probably time for me to wheel out my essay on

4516:, citing it as "the straw that broke the camel's back". I see for Rob if true. I won't comment on the "drama" part and using 966: 3363:

to make the explanation publicly available here, where it is most easily accessible to interested members of the community:

2526: 1849:

I've been lurking on WP over ten years. A recent stint of unemployment meant I've had more time on my hands to get involved.

1358:. If Fram is known to be publicly on the fringe of what's acceptably CIVIL, how are they off-wiki and out of the public eye? 5925: 5905: 4396: 3763: 3732: 3658: 3612: 3319: 3288:

It may have been unnoticed in the Wikimedia-world, because it happened outside the focus of the en.wp, but some months ago

3267: 2884: 2818: 1213: 712: 317:"wikipedian banned for criticizing the WMF" is the kind of inaccurate summary that frankly no-one should be propagating... 3301: 6123: 4226:

processes. This does not bode well for any of us, all the way down to beginners--maybe worst even for the inexperienced.

1354:

Fram is an inflammatory administrator who I believe has benefited from the Community going easy on them when it comes to

682: 4306: 3586:

The de and zh wikipedia examples show that WMF office bans are being applied in strange and arbitrary ways in general.

3250: 3144: 3098: 2954: 2870: 3014:

I think it is meant the authorized representatives of the community that are made to speak on our collective behalf. –

1433:

If the enwp community is going to upload civility enforcement to T&S, then they’re going to need a bigger staff. –

4728:

Yet they didn't even do this, or attempt to escalate the ban on Fram when he did discuss this (which, if privacy was

4310: 3087:

Hopefully somebody can be appointed to act as a fiduciary, rather than just creating another sea of RFC discussions.

2771: 2538: 2201: 2144: 1841: 1537: 1301: 3832:

a WMF employee would want/need a degree of separation from the atrocious behavior of the community at the moment. ~

2214:

Fram's utter and complete refusal to acknowledge any responsibility at all is not the behavior of an innocent person

5974: 5159: 4498:

No, Ansh did not leave because of this, and Rob said a few weeks ago he was leaving - this was just a diva quit. -

2790: 2747: 1781: 865: 598: 1363:

The complaints WMF received indicated to the WMF Legal Team that Fram's activity exposed them to legal liability.

4132:

I agree with that. WMF employees should just be executors, following instructions from the communities that they

3266:

and to some extent that means figuring out what the WMF is really about. I think we are naive some of the time.

3595: 1655:

The complaints WMF received indicated to the WMF Legal Team that Fram's activity exposed them to legal liability

1380:

Not to mention the privacy considerations of having a T&S team that doesn't out people who bring grievances.

6120: 6020:

Floquenbeam did the right thing and I await whatever WMF is going to do to make this worse than it already is.

5804:

major breaches of trust performed by Wikimedia functionaries or other users with access to advanced tools that

4631: 4395:

Thanks, Yan. The German bans had been mentioned before, but this is the first I've heard of the Chinese one.

3479: 2092:

going on in general, but it's not use of the word "fuck" that got Fram banned and in our gut, we all know it.

5869: 4747: 4356:

I recalled everything from my memory (I have no time for referencing), so some details might not be correct.

3937: 3214: 2492: 2311: 2291: 2253: 2225: 1766: 1723: 1705: 1662: 1514: 1212:. All we can really do is tell them that if they want to run Knowledge directly, they can do it without us. 1127: 789: 632: 580: 431: 298: 1775:

Since we're all speculating: if there were legal considerations, why was Fram banned from only one project?

923:

what is it going to take for some of you to realize that we should be fighting back by any means available?

3756:- you okay with merging your topic into mine? It seems that we both had similar ideas at the same time...? 2761: 2503: 2191: 2153: 2134: 1831: 1583: 1527: 6153:

of the people they told objected, so they may, indeed, have been hearing about it over the last few days.

2846:

indicated, there was quite a long history of conflict (the perennial trope of following-to-clean-up-after

1292:

See, if memory serves, a blocked admin still has access to deleted revisions and similar read-only stuff.

5802:

Note that the policy for office-action removal of advanced rights limits when that action can be done to

5038: 4714:

The WMF could have denied Fram's statement (if it isn't true) without putting anyone's privacy at risk.

2718:"Absolutely no nonfree content" and our "Nonfree content may be accepted in some limited circumstances" 5768: 5361: 5253: 5207: 3164: 2393: 1330:

I wonder if WMF had forgotten (or indeed, weren't aware) that admins can no longer unblock themselves?

1283: 825: 536: 38: 6135:

Perhaps the T&S team were experiencing internal dissent before the action, one would hope anyway.

5738:"we screwed up and we dumped the matter on arbcom in the hope they will make us look slightly better". 3983:

could have taken them. Castigating others for not doing what you also chose not to do is a bad look.

3190: 1233: 661:, speak for yourself. You must be talking about a different WMF, not about the Wikimedia Foundation. 5987:, I appreciate this well-reasoned and level-headed reply. I wish that people weren't going bonkers. 5929: 5909: 5864: 4742: 4400: 3769: 3738: 3664: 3607: 3323: 3271: 3209: 2888: 2842:

True as far as it goes, but appears to have been more of a ‘last straw’ than a cause in itself. As

2822: 2487: 2297: 2277: 2249: 2234: 2221: 1762: 1719: 1701: 1658: 1510: 1217: 1113: 784: 707: 627: 575: 5810:(emphasis mine}, so the WMF would be breaching its own policy by carrying out a desysopping here. 2482:

The claim that Fram exposed them to legal liability is absurd on its face. If that were the case,

5964: 5505: 4920: 4314: 4199:

Knowledge:Community response to the Wikimedia Foundation's ban of Fram/Proposals about WMF Office

3677:

Knowledge:Community response to the Wikimedia Foundation's ban of Fram/Proposals about WMF Office

2565: 2534: 2120: 1992: 1929: 1914: 1865: 1810: 1751: 1688: 1672:

Gut instinct. I believe the WMF wouldn't have banned Fram in the absence of legal considerations.

1406: 1297: 912: 686: 2760:, that particular WiR had been subject to enough controversies and IIRC, 2 ArbCom cases ....... 1154:

Thoughts on my changes? Overall, I do like what you wrote, and I think it encompasses the solid

5992: 5516: 5248:

Are you joking? This placeholder was posted two minutes before Fram was about to be unblocked.

5191: 5125: 5008: 4942:

return admin rights - neither ArbCom nor any other community process has mandated their removal

4798: 4690: 4525: 4489: 4040: 3988: 3511: 3448: 3434: 3338: 3244: 3229: 3138: 3092: 2948: 2857: 2582: 2436: 1642: 1390:. Fram dug this grave for himself, and there's no way in hell the WMF Is going to bend on this. 1198: 1184: 1163: 1143: 1095: 1078: 1054: 881: 526: 247: 218: 104: 5950:, with no prompting). If the Foundation is stepping in with that in mind, well, okay I guess. 4156:

WMF employees should just be executors, following instructions from the communities that they

5786: 5764: 5563: 5462: 5375: 5357: 5249: 5217: 5203: 5139: 4994: 4910: 4558: 4122: 3791: 3160: 3062: 2608:

Infringing copyrights, trademarks, patents, or other proprietary rights under applicable law.

2389: 2031: 1966: 1279: 928: 821: 666: 574:

If they try, that would exacerbate the situation. As it is, they're risking open rebellion. —

6038:

Also how long until someone makes a userbox with something like "I do not support the WMF"?

3206:

Belay this discussion until Jimbo and Doc James can find out just what the hell is going on.

5954:

trust members of Arbcom to be able to handle a personal conflict of interest, but maybe it

5763:" are you being serious? ARE YOU BEING SERIOUS? You're a bunch of cowards. Disgusting. 5701: 5683: 5636: 5584: 5443: 5389: 5347: 5292: 5281: 5155: 5066: 4930: 4543: 4459: 4232: 4146: 4098: 4080: 4054: 4026: 3903: 3318:

Thanks for recounting this. It was mentioned earlier but it's good to get more specifics.

3186: 2786: 2743: 1895: 1331: 1245: 807: 595: 551:

going on, and if we say it in a prominent enough place, people will listen. They might not

498: 478: 135: 3506:

there is improvement, we don't always block users evading their block with a new account.

1560:

provide any evidence of prior relevant warning nor of any generally announced standard. -

642:

If the WMF would be embarrassed to have people know about what they're doing, they should

8: 6009: 5894: 5476:

I have changed the title of this section and moved the original title below the heading.

4953: 3781: 3758: 3727: 3653: 3602: 3599: 3123: 2806: 2695: 2668: 2634: 2597: 2346: 2070: 2045: 1882: 1609: 1550: 1482: 1452: 1424: 1109: 835: 727: 702: 699: 617: 413: 272: 233: 203: 4360:

So here's my speculation and personal feelings after seeing 4 cases by the T&S team.

4309:, which so far I haven't seen anyone discussing them. Two users from Chinese Knowledge, 4246:

may give some insights as to the foundation's position (four years ago at any rate). --

6160: 5940: 5849: 5842: 5831: 5797: 5728: 5714: 5673: 5599: 5541: 5523: 5501: 5481: 5329: 5223: 5177: 5091: 4849: 4783: 4763: 4671: 4637: 4610: 4513: 4503: 4167: 3947: 3570: 3540: 3529: 3491: 2850: 2832: 2724: 2679: 2652: 2645: 2623: 2611: 2561: 2555: 2530: 2514: 2454: 2324: 2116: 2110: 2056: 1988: 1925: 1910: 1904: 1861: 1855: 1806: 1800: 1747: 1741: 1684: 1678: 1402: 1396: 1355: 1312: 1293: 982: 771: 757: 647: 362: 322: 306: 287: 173: 150: 122: 4813:"We do not trust the existing community processes to handle this particular scenario." 6140: 6105: 5988: 5404: 5187: 5121: 5005: 4894: 4820: 4794: 4705: 4686: 4586: 4521: 4485: 4448: 4385: 4251: 4201:, but got reverted on this section. Someone else will have to move it if they want. 4136:. It's things like ArbCom that take responsibility and have accountability. They are 4036: 3984: 3970: 3933: 3857: 3635: 3548: 3507: 3463: 3444: 3430: 3411: 3334: 3308: 3240: 3225: 3134: 3088: 3058: 2944: 2925: 2915: 2854: 2578: 2431: 2430:

Fram's summary of what happened is accurate, then I don't see the legal risk to WMF.

2178: 1638: 1194: 1180: 1172: 1159: 1139: 1091: 1087: 1074: 1050: 877: 735: 564: 522: 427: 339: 243: 214: 161: 100: 5120:, thank you for providing more information. I appreciate your attempting to engage. 4307:

There is a list published by the Foundation showing users banned by the WMF (mostly)

3298:

de:Wikipedia_Diskussion:Kurier/Archiv/2019/02#Office Aktion der Wikimedia Foundation

3239:

which is great, but it would be nice if there was some organization backing him up.

1894:

You are not the arbitrator of whether I am involved in the project or not, and your

1545:

the knowledge that I am in a small minority of those who agree with this action. --

198:

Nope nope nope. Please don't do that. Won't help anything, will harm many things. --

6059: 5881: 5814: 5806:

are not possible to be shared with the Wikimedia communities due to privacy reasons

5782: 5558: 5458: 5371: 5308: 5169: 5135: 4986: 4906: 4718: 4553: 4426: 4118: 4035:

It seems that ArbCom was informed that action was being investigated against Fram.

3787: 3751: 3046: 3003: 2336:

whether there was anything other than being incivil to ArbComm behind this action;

2027: 1958: 1565: 1496: 924: 842: 662: 5300:

No, it's the 2/1; I don't believe the WMF ever made the claim that, for instance,

6001: 5984: 5969: 5697: 5580: 5439: 5426: 5385: 5343: 5271: 5151: 5062: 5047:

Trypto and the others commenting actually agreed with the action. You disagreed.

5034: 5018: 4926: 4539: 4227: 4142: 4094: 4076: 4050: 4022: 3899: 3675:

note: I'm trying to start a split to a subpage for WMFOffice-specific actions at

3384:

Why did the Foundation act, even though all three accounts were already blocked?

2782: 2757: 2739: 2157: 2062: 1877: 1776: 1595: 1467: 1240: 945: 858: 803: 592: 493: 473: 4197:

Note: I tried to move this section with the other WMFOffice specific actions to

4009:

Sorry, but for me that's a bridge too far and I will not stand for this kind of

3333:

imposing an add-on ban (that effectively changed nothing) seemed quite strange.

3292:

has infinite banned a long time very productive editor in the German wikipedia,

1735:

Thank you for your well-reasoned and civil rebuttal to my read of the situation.

46:

If you wish to start a new discussion or revive an old one, please do so on the

6005: 5885: 5743: 5117: 5048: 5021:, I disagree as well. To the level that I cannot in good conscience keep mine. 4971: 4949: 4859: 4185: 3706: 3695: 3631: 3587: 3289: 3182: 3119: 3039: 2996: 2843: 2802: 2691: 2664: 2630: 2593: 2418: 2363: 2342: 2329: 2238: 2161: 2130: 2093: 2089: 2085: 2066: 2041: 2021: 1977: 1954:

Rivselis was blocked for sockpuppetry. He was bullshitting, believe it or not.

1945: 1605: 1579: 1546: 1478: 1448: 1439: 1420: 1266: 898: 658: 613: 409: 263: 229: 199: 4741:, and their rationale for limiting the ban the way they did) was privileged. — 6156: 5947: 5827: 5669: 5649: 5612: 5595: 5537: 5519: 5477: 5325: 5235: 5173: 5103: 4884: 4845: 4667: 4624: 4620: 4606: 4517: 4499: 4288: 4206: 3961: 3954: 3868: 3849: 3833: 3818: 3684: 3566: 3525: 3487: 3293: 3072: 3021: 2976: 2551: 2473: 2450: 2273: 2106: 1900: 1851: 1827: 1796: 1737: 1713: 1674: 1634: 1392: 1387: 1318: 767: 753: 397: 393: 358: 318: 302: 185: 146: 115: 89: 5682:

Of course it does. If the WMF disappeared anyone who abused anyone else ...

5668:

Whichever way, you've missed the point, which comes as no great surprise. -

3965:

fundamentally good, and want the best for each other and the readership. —

766:

No, let's not abuse the main page of an encyclopedia for biased propaganda.

6136: 6101: 5400: 5186:

That would definitely be advisable. No harm in waiting a few more minutes.

4890: 4816: 4701: 4641: 4582: 4474: 4444: 4415: 4380: 4247: 3966: 3929: 3853: 3559: 3544: 3521: 3459: 3423: 3407: 3304: 2921: 2911: 2187: 2174: 838:. Thus, this is clearly (from a technical perspective) within its purview. 731: 560: 423: 18:

Knowledge:Community response to the Wikimedia Foundation's ban of Fram

5370:

I don't understand why they weren't prepared for the inevitable backlash.

1940:

Rivselis is not bullshitting, so you guys can stop with your witch hunt.--

1317:

yes on that, and also some "writeable" things I'm not going in to here. —

1065:

remove "or lack thereof" when asking for ArbCom's motion. I'd also change

6056: 5811: 5492:

Discussion about second WMFOffice comment, now that it is actually posted

5305: 4715: 4422: 4270:

designed to fail, because the politicians want 'criminals' in 'prison').

4017:

that I object to (for all I know, it was completely justified), it's the

3130: 2817:

Can someone explain a little more what WiR has to do with this? Thanks.

1561: 1492: 839: 3355:

Translation of the message from the WMF to the German-speaking community

5267: 5026: 4365:

This is a chilling effect that prevents contributors from standing out.

4337:

users was just unblocked by a local admin after a years-long blockade.

1591: 1463: 1105: 941: 489: 465: 453: 379: 2990:

Wouldn't any organization that effectively "represents the community"

1657:" come from? (Genuine question, I don't remember seeing it anywhere). 5739: 4967: 4657: 4180: 4010: 2414: 1941: 1434: 1261: 894: 166:

this is such a bad idea. It's also a good idea, but it's also a real

4439: 957:

to think the rest of the world actually cares about, of all things,

5848:

jurisdiction, a whole lot of people would be saying "Fuck ArbCom".

5761:

We know this action came as a surprise to some within the community

5230: 5098: 4733:

was his third strike, that it was specifically based on harassment

4469:

WMF have extended the ban by two days to 12/6/20 instead of 10/6/20

4284: 4202: 3814: 3680: 3625:

Knowledge:Administrators' noticeboard#User:WMFOffice - Ban Proposal

3067: 3016: 2971: 2469: 180: 5202:

Fucking outrageous. WMF are treating this like some kind of joke.

4512:

While he had intentions of leaving, Ansh left because of this per

2969:

the creation of some organization that represents the community. –

2218:

Ah yes, pleading innocent is exactly what a guilty person would do

1505:

No, by imposing an unexplained and unappealable ban, they are not

4298:

Two similar bans & one "conduct warning" on Chinese Knowledge

3786:

All good, I removed my comment, as it is not needed any longer.--

1273:

No, indeed, no abuse of the tools at all. The de-sysop was just

1491:

Setting a standard usually requires that the bar is divulged. -

5472:...Withdrawn question about role account edits moved to talk... 3679:. (but I didn't remove anything from this particular section) 1175:, I like your changes, I think that they improve how it reads. 375: 297:

A website by the name of reclaimthenet.org covered the ban in

5880:

This response is just as vague as the last one. I agree with

4700:

people's mouths, however justified the ban turns out to be.--

3263: 1179:- We may agree on that, but we want the WMF to be agreeable. 5085:

Original title: "Discussion about second WMFOffice comment"

3808:, or whether they are using or will use subcontractors like 3390:

What kind of appeal is possible against this office action?

242:

Please don't! That isn't good for the project or any of us.

1509:. For a standard to be a standard, it has to be explained. 114:

The best you are going to do is Brietbart or the Register.

5172:, finger off the trigger - for a little while as least. - 1578:

You're a long way out of touch with the enwiki community,

4321:

Here are some differences and similarities I discovered:

4021:

that is completely, utterly, and totally unacceptable. --

1041:

We humbly give our supplications as fore to with stated.

5302:

Arbcom was one primary target of the person in question

2276:, however accurate we think they are; also, who's "we"? 1260:. It seems the userright should have remained in place – 555:

with us, of course, but at least the case will be made.

134:

I'm pretty sure they meant actual press, not those two.

1590:

We know the answers for ArbCom, but not for T&S. --

965:

don't care about us. Talk about delusions of grandeur.

5648:

Does that affect the point I was making in any way? ~

5081:

Discussion about the "Forthcoming shortly" placeholder

4261:

Are "warned" editors subject to harsher examination?

3224:

What would prevent this becoming just like the WMF?

1699:

We really don't give a fuck about your gut instinct.

94:

Has anyone contacted the press about this? I'm sure

5579:This is pretty lackluster for even a canned reply. 2216:", you do realise that sounds perilously close to " 452:overruled the WMF's action here alone is shameful. 422:Unfortunately, this is exactly what will happen. – 5500:" Let me be the first to say, fuck that bullshit. 5023:Knowledge:Bureaucrats'_noticeboard#Desysop_(TheDJ) 4244:a section on WMFOffice's talk page archive on Meta 2920:(struck as reasoning is not yet confirmed/certain 4179:The volunteers are the hand that feeds the WMF. – 3630:Hi all, I've proposed a indef ban & block on 2527:Knowledge:Office actions#Secondary office actions 2248:And your expertise in criminal psychology is...? 1341:WMF is protecting themselves from legal liability 3848:I agree with basically everything you say here, 1365:WMF can't allow Fram to expose them to liability 857:Press will only make a bad situation way worse. 392:been involved are regards to quality control of 3458:read additional content in collapsed sections. 1898:that this is not my main account are unwelcome. 646:. The community didn't start the problem here. 5438:Will the last one out turn off the lights... 4273:Now I don't mean to say that a warning should 3381:from whom the complaints were referred to us. 3377:Who contacted the Foundation with complaints? 3366:Why did the Foundation act and why just now? 3284:FYI: Similar incident in de.wp some months ago 2938:Who does represent the editing community here? 5342:I'm not good at math but sounds about right. 4334:most people supporting the ban like INeverCry 2486:, as opposed to banned on en.wp for a year. — 1069:to something stronger, but stopping short of 961:? Hell, the way we speak of each other shows 5148:We would like to hear what you have to say. 4839:have strutted around afterwards going "well 1976:Indeed. Should the sock comments be struck? 1108:, either; remind the WMF of their position. 2061:Frankly I've long been of the opinion that 836:has the ability to run arbitrary javascript 3651:Note: discussion closed as a non-starter. 3159:That'll be "the editing community" then. 1795:(This last point feels the weakest to me.) 1257: 1256:I’m grappling with this as well, above at 5324:shortly. In 15 minutes? An hour? A week? 5291:5/6 wins. Bookies always do, don't they? 5722:, we now know that the case involved an 4739:for all possible parties, Fram included) 5515:Comment moved to discussion section in 5088:Which there almost inevitably will be. 4438:I feel compelled to point out that the 14: 5635:"Harassing OR abusing". Get it right. 1346:Here's my take on this turn of events: 44:Do not edit the contents of this page. 4141:absolutely and irredeemably wrong. -- 2484:he'd've been globally banned for good 3484:Discussion "Vandalismusmeldung" 2018 1584:m:Trust and Safety #Trust and Safety 955:Knowledge editors are so egotistical 25: 6040:2001:4898:80E8:2:A5F:2E62:10E4:D7D1 6022:2001:4898:80E8:2:A5F:2E62:10E4:D7D1 4165:and starting your own community. — 23: 5220:: They haven't said anything yet? 3634:. Comments/!votes are welcomed. - 1073:(appeal, entreat, petition, etc) 24: 6181: 4735:(since this was and is, at most, 999:The English Knowledge Community, 4572:A broader question about process 967:The Blade of the Northern Lights 29: 5134:Very, erm, interesting timing. 3590:is another example. We already 3061:this has more the feeling of a 301:, so I guess that's something. 4552:No, Rob left because of this. 2908:as with this case and civility 1006:real and imminent danger; and 13: 1: 4836:Foundation-community dynamics 1718:Apologies, I've struck that. 3702:Will the posters behind the 3698:posters identify themselves? 2918:) 18:45, 11 June 2019 (UTC) 2558:) 16:21, 11 June 2019 (UTC) 2525:FWIW, they are mentioned in 2113:) 17:43, 11 June 2019 (UTC) 1907:) 17:33, 11 June 2019 (UTC) 1858:) 16:41, 11 June 2019 (UTC) 1830:, what's your main account? 1803:) 18:04, 11 June 2019 (UTC) 1744:) 16:41, 11 June 2019 (UTC) 1681:) 16:24, 11 June 2019 (UTC) 1507:setting any standards at all 1399:) 16:08, 11 June 2019 (UTC) 7: 5502:Only in death does duty end 2513:not to, not that we can't. 2296:17:50, 11 June 2019 (UTC). 1708:) 16:34, 11 June 2019 (UTC) 10: 6186: 1523:Correcting that for you:- 6166:20:51, 11 June 2019 (UTC) 6145:20:23, 11 June 2019 (UTC) 6127:20:03, 11 June 2019 (UTC) 6110:20:23, 11 June 2019 (UTC) 6096:20:01, 11 June 2019 (UTC) 6065:19:59, 11 June 2019 (UTC) 6048:19:57, 11 June 2019 (UTC) 6030:19:55, 11 June 2019 (UTC) 6014:20:12, 11 June 2019 (UTC) 5997:19:59, 11 June 2019 (UTC) 5980:19:55, 11 June 2019 (UTC) 5934:19:52, 11 June 2019 (UTC) 5914:19:52, 11 June 2019 (UTC) 5897:19:51, 11 June 2019 (UTC) 5875:19:45, 11 June 2019 (UTC) 5855:19:54, 11 June 2019 (UTC) 5836:19:45, 11 June 2019 (UTC) 5820:19:46, 11 June 2019 (UTC) 5791:19:41, 11 June 2019 (UTC) 5773:19:43, 11 June 2019 (UTC) 5748:20:07, 11 June 2019 (UTC) 5734:19:46, 11 June 2019 (UTC) 5706:19:39, 11 June 2019 (UTC) 5687:19:45, 11 June 2019 (UTC) 5678:19:37, 11 June 2019 (UTC) 5660:19:37, 11 June 2019 (UTC) 5640:19:36, 11 June 2019 (UTC) 5623:19:33, 11 June 2019 (UTC) 5604:19:31, 11 June 2019 (UTC) 5589:19:30, 11 June 2019 (UTC) 5567:19:29, 11 June 2019 (UTC) 5546:19:32, 11 June 2019 (UTC) 5528:19:42, 11 June 2019 (UTC) 5510:19:29, 11 June 2019 (UTC) 5486:19:40, 11 June 2019 (UTC) 5467:19:11, 11 June 2019 (UTC) 5448:19:21, 11 June 2019 (UTC) 5430:19:09, 11 June 2019 (UTC) 5409:19:25, 11 June 2019 (UTC) 5394:19:18, 11 June 2019 (UTC) 5380:19:15, 11 June 2019 (UTC) 5366:19:14, 11 June 2019 (UTC) 5352:19:08, 11 June 2019 (UTC) 5333:19:07, 11 June 2019 (UTC) 5314:19:37, 11 June 2019 (UTC) 5296:19:34, 11 June 2019 (UTC) 5285:19:06, 11 June 2019 (UTC) 5276:19:06, 11 June 2019 (UTC) 5258:19:12, 11 June 2019 (UTC) 5244:19:07, 11 June 2019 (UTC) 5212:19:03, 11 June 2019 (UTC) 5196:19:03, 11 June 2019 (UTC) 5182:19:02, 11 June 2019 (UTC) 5165:19:01, 11 June 2019 (UTC) 5144:19:00, 11 June 2019 (UTC) 5130:19:00, 11 June 2019 (UTC) 5112:19:01, 11 June 2019 (UTC) 5071:21:46, 13 June 2019 (UTC) 5054:14:08, 13 June 2019 (UTC) 5043:11:16, 13 June 2019 (UTC) 5012:08:53, 13 June 2019 (UTC) 5000:01:57, 13 June 2019 (UTC) 4976:00:26, 13 June 2019 (UTC) 4958:23:48, 12 June 2019 (UTC) 4935:23:44, 12 June 2019 (UTC) 4915:20:45, 12 June 2019 (UTC) 4899:18:35, 12 June 2019 (UTC) 4865:02:51, 13 June 2019 (UTC) 4854:19:12, 12 June 2019 (UTC) 4825:18:46, 12 June 2019 (UTC) 4803:18:43, 12 June 2019 (UTC) 4789:18:38, 12 June 2019 (UTC) 4753:20:40, 12 June 2019 (UTC) 4724:18:34, 12 June 2019 (UTC) 4710:18:30, 12 June 2019 (UTC) 4695:18:25, 12 June 2019 (UTC) 4676:18:14, 12 June 2019 (UTC) 4661:17:25, 12 June 2019 (UTC) 4649:17:15, 12 June 2019 (UTC) 4615:16:07, 12 June 2019 (UTC) 4591:15:59, 12 June 2019 (UTC) 4562:14:18, 12 June 2019 (UTC) 4548:07:54, 12 June 2019 (UTC) 4530:07:47, 12 June 2019 (UTC) 4508:07:43, 12 June 2019 (UTC) 4494:07:40, 12 June 2019 (UTC) 4478:05:31, 12 June 2019 (UTC) 4463:23:20, 11 June 2019 (UTC) 4453:23:14, 11 June 2019 (UTC) 4431:13:01, 12 June 2019 (UTC) 4405:22:45, 11 June 2019 (UTC) 4390:21:48, 11 June 2019 (UTC) 4293:15:43, 12 June 2019 (UTC) 4256:23:05, 13 June 2019 (UTC) 4235:09:16, 13 June 2019 (UTC) 4211:12:56, 12 June 2019 (UTC) 4188:13:42, 13 June 2019 (UTC) 4175:13:35, 13 June 2019 (UTC) 4151:13:09, 12 June 2019 (UTC) 4127:13:02, 12 June 2019 (UTC) 4103:13:07, 12 June 2019 (UTC) 4085:12:55, 12 June 2019 (UTC) 4059:12:50, 12 June 2019 (UTC) 4045:12:32, 12 June 2019 (UTC) 4031:12:24, 12 June 2019 (UTC) 3993:16:01, 12 June 2019 (UTC) 3975:13:41, 12 June 2019 (UTC) 3941:13:30, 12 June 2019 (UTC) 3908:13:49, 12 June 2019 (UTC) 3879:13:15, 12 June 2019 (UTC) 3862:13:06, 12 June 2019 (UTC) 3844:12:12, 12 June 2019 (UTC) 3823:11:55, 12 June 2019 (UTC) 3796:13:08, 12 June 2019 (UTC) 3775:11:42, 12 June 2019 (UTC) 3744:11:37, 12 June 2019 (UTC) 3689:12:37, 12 June 2019 (UTC) 3670:02:53, 13 June 2019 (UTC) 3646:08:05, 12 June 2019 (UTC) 3619:02:51, 13 June 2019 (UTC) 3575:21:55, 12 June 2019 (UTC) 3553:20:14, 12 June 2019 (UTC) 3534:19:14, 12 June 2019 (UTC) 3516:10:58, 12 June 2019 (UTC) 3496:09:38, 12 June 2019 (UTC) 3468:02:52, 12 June 2019 (UTC) 3453:02:23, 12 June 2019 (UTC) 3439:02:18, 12 June 2019 (UTC) 3416:02:14, 12 June 2019 (UTC) 3343:00:00, 12 June 2019 (UTC) 3328:23:11, 11 June 2019 (UTC) 3313:21:27, 11 June 2019 (UTC) 3276:22:05, 11 June 2019 (UTC) 3257:20:34, 11 June 2019 (UTC) 3234:20:31, 11 June 2019 (UTC) 3220:20:27, 11 June 2019 (UTC) 3195:17:22, 12 June 2019 (UTC) 3169:20:26, 11 June 2019 (UTC) 3151:20:29, 11 June 2019 (UTC) 3105:20:45, 11 June 2019 (UTC) 3081:20:44, 11 June 2019 (UTC) 3051:20:35, 11 June 2019 (UTC) 3030:20:27, 11 June 2019 (UTC) 3008:20:25, 11 June 2019 (UTC) 2985:20:20, 11 June 2019 (UTC) 2961:20:18, 11 June 2019 (UTC) 2930:19:01, 11 June 2019 (UTC) 2893:21:14, 11 June 2019 (UTC) 2878:19:24, 11 June 2019 (UTC) 2838:18:44, 11 June 2019 (UTC) 2827:18:29, 11 June 2019 (UTC) 2811:17:05, 11 June 2019 (UTC) 2796:16:58, 11 June 2019 (UTC) 2774:16:54, 11 June 2019 (UTC) 2753:16:50, 11 June 2019 (UTC) 2730:18:00, 11 June 2019 (UTC) 2700:17:16, 11 June 2019 (UTC) 2685:17:09, 11 June 2019 (UTC) 2673:17:02, 11 June 2019 (UTC) 2658:16:56, 11 June 2019 (UTC) 2639:16:51, 11 June 2019 (UTC) 2617:16:37, 11 June 2019 (UTC) 2602:16:26, 11 June 2019 (UTC) 2587:16:22, 11 June 2019 (UTC) 2570:04:26, 12 June 2019 (UTC) 2543:16:20, 11 June 2019 (UTC) 2520:16:18, 11 June 2019 (UTC) 2498:04:56, 12 June 2019 (UTC) 2478:21:16, 11 June 2019 (UTC) 2460:21:16, 11 June 2019 (UTC) 2442:20:51, 11 June 2019 (UTC) 2423:20:01, 11 June 2019 (UTC) 2398:18:34, 11 June 2019 (UTC) 2369:18:32, 11 June 2019 (UTC) 2351:17:51, 11 June 2019 (UTC) 2317:17:50, 11 June 2019 (UTC) 2258:18:41, 11 June 2019 (UTC) 2244:18:32, 11 June 2019 (UTC) 2230:17:59, 11 June 2019 (UTC) 2204:17:56, 11 June 2019 (UTC) 2190:, clarification, please. 2183:17:53, 11 June 2019 (UTC) 2167:18:23, 11 June 2019 (UTC) 2147:17:45, 11 June 2019 (UTC) 2125:04:26, 12 June 2019 (UTC) 2099:17:37, 11 June 2019 (UTC) 2075:16:56, 11 June 2019 (UTC) 2050:16:47, 11 June 2019 (UTC) 2036:16:38, 11 June 2019 (UTC) 1997:04:26, 12 June 2019 (UTC) 1983:03:35, 12 June 2019 (UTC) 1972:02:22, 12 June 2019 (UTC) 1950:18:29, 11 June 2019 (UTC) 1934:04:26, 12 June 2019 (UTC) 1924:Unwelcome, because true. 1919:04:26, 12 June 2019 (UTC) 1889:17:26, 11 June 2019 (UTC) 1870:04:26, 12 June 2019 (UTC) 1844:16:35, 11 June 2019 (UTC) 1815:04:26, 12 June 2019 (UTC) 1787:16:54, 11 June 2019 (UTC) 1771:16:52, 11 June 2019 (UTC) 1756:04:26, 12 June 2019 (UTC) 1728:18:08, 11 June 2019 (UTC) 1693:04:26, 12 June 2019 (UTC) 1667:16:20, 11 June 2019 (UTC) 1647:16:13, 11 June 2019 (UTC) 1614:00:47, 12 June 2019 (UTC) 1600:00:41, 12 June 2019 (UTC) 1570:17:04, 11 June 2019 (UTC) 1555:16:59, 11 June 2019 (UTC) 1540:16:50, 11 June 2019 (UTC) 1519:16:48, 11 June 2019 (UTC) 1501:16:50, 11 June 2019 (UTC) 1487:16:46, 11 June 2019 (UTC) 1472:16:31, 11 June 2019 (UTC) 1457:16:15, 11 June 2019 (UTC) 1442:16:13, 11 June 2019 (UTC) 1429:16:11, 11 June 2019 (UTC) 1411:04:26, 12 June 2019 (UTC) 1335:15:53, 11 June 2019 (UTC) 1324:16:00, 11 June 2019 (UTC) 1306:15:52, 11 June 2019 (UTC) 1288:15:50, 11 June 2019 (UTC) 1269:15:49, 11 June 2019 (UTC) 1251:15:47, 11 June 2019 (UTC) 1222:17:43, 11 June 2019 (UTC) 1203:16:55, 11 June 2019 (UTC) 1189:16:51, 11 June 2019 (UTC) 1168:16:48, 11 June 2019 (UTC) 1148:16:52, 11 June 2019 (UTC) 1133:16:47, 11 June 2019 (UTC) 1112:, and all. Otherwise OK. 1100:16:34, 11 June 2019 (UTC) 1083:16:30, 11 June 2019 (UTC) 1059:16:16, 11 June 2019 (UTC) 977:18:22, 12 June 2019 (UTC) 950:13:37, 12 June 2019 (UTC) 933:12:08, 12 June 2019 (UTC) 916:11:50, 12 June 2019 (UTC) 903:10:28, 12 June 2019 (UTC) 886:10:24, 12 June 2019 (UTC) 869:08:05, 12 June 2019 (UTC) 848:20:55, 12 June 2019 (UTC) 830:07:13, 12 June 2019 (UTC) 812:04:56, 12 June 2019 (UTC) 795:04:18, 12 June 2019 (UTC) 776:04:05, 12 June 2019 (UTC) 762:04:06, 12 June 2019 (UTC) 740:05:25, 12 June 2019 (UTC) 719:02:45, 12 June 2019 (UTC) 691:02:20, 12 June 2019 (UTC) 671:04:07, 12 June 2019 (UTC) 653:04:05, 12 June 2019 (UTC) 638:02:34, 12 June 2019 (UTC) 622:02:27, 12 June 2019 (UTC) 603:02:26, 12 June 2019 (UTC) 586:02:24, 12 June 2019 (UTC) 569:02:15, 12 June 2019 (UTC) 531:23:04, 12 June 2019 (UTC) 504:20:16, 12 June 2019 (UTC) 485:18:48, 12 June 2019 (UTC) 461:10:32, 12 June 2019 (UTC) 435:10:25, 12 June 2019 (UTC) 418:09:47, 12 June 2019 (UTC) 387:07:36, 12 June 2019 (UTC) 367:06:48, 12 June 2019 (UTC) 350:02:30, 12 June 2019 (UTC) 327:06:48, 12 June 2019 (UTC) 311:02:54, 12 June 2019 (UTC) 293:01:45, 12 June 2019 (UTC) 275:01:42, 12 June 2019 (UTC) 252:01:38, 12 June 2019 (UTC) 238:01:37, 12 June 2019 (UTC) 223:01:36, 12 June 2019 (UTC) 208:01:32, 12 June 2019 (UTC) 194:01:29, 12 June 2019 (UTC) 155:01:28, 12 June 2019 (UTC) 139:01:31, 12 June 2019 (UTC) 130:01:28, 12 June 2019 (UTC) 109:01:25, 12 June 2019 (UTC) 4982:He did the right thing. 4811:if) that explanation is 834:The Knowledge community 4807:Even if (and arguably, 4776:they should know better 4440:Foundation Terms of Use 4169:The Hand That Feeds You 2154:Winged Blades of Godric 2088:that there is too much 1987:I'm striking them now. 5517:Special:Diff/901426089 4730:that much of a concern 4138:democratically elected 1258:#Hypothetical question 408: 4940:The log summary was " 3063:collective bargaining 403: 42:of past discussions. 2504:WMF conduct warnings 5557:Floq's intentions. 4964:Arbitration Request 4619:I like your ideas, 2338:that's the problem. 2250:Boing! said Zebedee 2235:Boing! said Zebedee 2222:Boing! said Zebedee 1763:Boing! said Zebedee 1720:Boing! said Zebedee 1702:Boing! said Zebedee 1659:Boing! said Zebedee 1511:Boing! said Zebedee 1110:Servus servorum dei 1104:And we need not be 5866:A little blue Bori 4744:A little blue Bori 4514:User talk:Ansh.666 3541:User talk:Janneman 3211:A little blue Bori 2489:A little blue Bori 1388:Right Great Wrongs 1106:'er so ever 'umble 786:A little blue Bori 629:A little blue Bori 577:A little blue Bori 5963:has at least the 5944: 5853: 5846: 5801: 5732: 5718: 5684:Black Kite (talk) 5657: 5637:Black Kite (talk) 5620: 5530: 5473: 5293:Black Kite (talk) 5282:Black Kite (talk) 5227: 5095: 4787: 4767: 4740: 4647: 4460:Black Kite (talk) 3951: 3876: 3841: 3403: 3402: 3107: 3083: 3065:representative. – 3053: 3049: 3032: 3010: 3006: 2933: 2836: 2728: 2683: 2656: 2649: 2627: 2615: 2572: 2518: 2440: 2328: 2127: 2060: 1921: 1872: 1817: 1758: 1731: 1695: 1413: 1332:Black Kite (talk) 1234:Why the de-sysop? 1177:SerialNumber54129 1046: 1045: 651: 291: 286:be doing it...". 177: 136:Black Kite (talk) 128: 87: 86: 54: 53: 48:current main page 6177: 6164: 6163: 5938: 5892: 5882:User:Floquenbeam 5872: 5852: 5840: 5795: 5765:The Rambling Man 5762: 5731: 5712: 5653: 5616: 5561: 5514: 5471: 5358:The Rambling Man 5250:The Rambling Man 5242: 5233: 5221: 5204:The Rambling Man 5163: 5110: 5101: 5089: 5030: 4998: 4997: 4992: 4989: 4888: 4786: 4761: 4750: 4734: 4644: 4638:Talk to Nihonjoe 4634: 4630: 4627: 4556: 4419: 4383: 4230: 4170: 3958: 3945: 3872: 3837: 3785: 3766: 3761: 3755: 3735: 3730: 3661: 3656: 3643: 3642: 3639: 3615: 3610: 3605: 3563: 3427: 3351: 3350: 3253: 3247: 3217: 3161:The Rambling Man 3147: 3141: 3101: 3095: 3086: 3079: 3070: 3056: 3045: 3042: 3035: 3028: 3019: 3013: 3002: 2999: 2994:the community?~ 2989: 2983: 2974: 2957: 2951: 2919: 2874: 2867: 2864: 2861: 2835: 2794: 2769: 2764: 2751: 2727: 2682: 2655: 2643: 2621: 2614: 2559: 2517: 2495: 2458: 2457: 2434: 2390:The Rambling Man 2366: 2322: 2314: 2309: 2302: 2294: 2289: 2282: 2270:know in our guts 2241: 2199: 2194: 2164: 2142: 2137: 2114: 2096: 2054: 2025: 1970: 1969: 1964: 1961: 1908: 1887: 1885: 1880: 1879:Ben · Salvidrim! 1859: 1839: 1834: 1804: 1745: 1717: 1709: 1682: 1535: 1530: 1400: 1367:, hence the ban. 1321: 1316: 1280:The Rambling Man 1248: 1243: 1158:necessary here. 1130: 1125: 1118: 988: 987: 973: 863: 822:PaleCloudedWhite 792: 715: 710: 705: 650: 635: 583: 501: 496: 481: 476: 458: 384: 347: 346: 343: 290: 270: 192: 183: 171: 165: 125: 120: 118: 68: 56: 55: 33: 32: 26: 6185: 6184: 6180: 6179: 6178: 6176: 6175: 6174: 6159: 6154: 6062: 6061:it has begun... 5977: 5961:on this project 5886: 5870: 5817: 5816:it has begun... 5760: 5656: 5619: 5559: 5494: 5311: 5310:it has begun... 5231: 5229: 5149: 5099: 5097: 5083: 5028: 4987: 4985: 4984: 4983: 4944:". See ongoing 4923: 4921:Floq re-sysoped 4882: 4748: 4721: 4720:it has begun... 4642: 4632: 4625: 4574: 4554: 4471: 4413: 4379: 4315:Galaxyharrylion 4300: 4263: 4228: 4168: 3952: 3875: 3840: 3779: 3764: 3759: 3749: 3733: 3728: 3700: 3659: 3654: 3640: 3637: 3636: 3628: 3613: 3608: 3603: 3592:globally banned 3557: 3460:Kudpung กุดผึ้ง 3421: 3408:Kudpung กุดผึ้ง 3404: 3356: 3286: 3251: 3245: 3215: 3187:Megalibrarygirl 3145: 3139: 3099: 3093: 3068: 3066: 3047:problem solving 3040: 3017: 3015: 3004:problem solving 2997: 2972: 2970: 2955: 2949: 2940: 2872: 2865: 2862: 2859: 2853:) before then.— 2780: 2765: 2762: 2737: 2506: 2493: 2453: 2448: 2364: 2312: 2305: 2298: 2292: 2285: 2278: 2239: 2195: 2192: 2162: 2138: 2135: 2094: 2019: 1959: 1957: 1956: 1955: 1883: 1878: 1876: 1835: 1832: 1793:considerations. 1784: 1711: 1531: 1528: 1386:Stop trying to 1343: 1319: 1310: 1246: 1241: 1236: 1128: 1121: 1114: 1047: 993: 985: 971: 859: 845: 844:it has begun... 790: 732:Kudpung กุดผึ้ง 713: 708: 703: 633: 581: 539: 537:Press, you say? 499: 494: 479: 474: 454: 380: 344: 341: 340: 264: 258:This could end 181: 179: 159: 123: 116: 92: 64: 30: 22: 21: 20: 12: 11: 5: 6183: 6173: 6172: 6171: 6170: 6169: 6168: 6130: 6129: 6115: 6114: 6113: 6112: 6083: 6078: 6077: 6072: 6071: 6070: 6069: 6068: 6067: 6060: 6033: 6032: 6018: 6017: 6016: 5999: 5973: 5965:standard offer 5936: 5926:67.164.113.165 5917: 5916: 5906:67.164.113.165 5900: 5899: 5860: 5859: 5858: 5857: 5824: 5823: 5822: 5815: 5807: 5779: 5775: 5755: 5754: 5753: 5752: 5751: 5750: 5736: 5709: 5708: 5693: 5692: 5691: 5690: 5689: 5680: 5663: 5662: 5654: 5643: 5642: 5628: 5627: 5626: 5625: 5617: 5592: 5591: 5577: 5576: 5575: 5574: 5573: 5572: 5571: 5570: 5569: 5533: 5532: 5531: 5493: 5490: 5489: 5488: 5474: 5469: 5453: 5452: 5451: 5450: 5433: 5432: 5422: 5421: 5420: 5419: 5418: 5417: 5416: 5415: 5414: 5413: 5412: 5411: 5337: 5336: 5318: 5317: 5316: 5309: 5288: 5287: 5278: 5264: 5263: 5262: 5261: 5260: 5200: 5199: 5198: 5167: 5146: 5132: 5082: 5079: 5078: 5077: 5076: 5075: 5074: 5073: 5016: 5015: 5014: 4980: 4979: 4978: 4922: 4919: 4918: 4917: 4880: 4879: 4878: 4877: 4876: 4875: 4874: 4873: 4872: 4871: 4870: 4869: 4868: 4867: 4759: 4758: 4757: 4756: 4755: 4719: 4663: 4653: 4652: 4651: 4602: 4598: 4573: 4570: 4569: 4568: 4567: 4566: 4565: 4564: 4534: 4533: 4532: 4470: 4467: 4466: 4465: 4436: 4435: 4434: 4433: 4408: 4407: 4397:67.164.113.165 4299: 4296: 4262: 4259: 4240: 4239: 4238: 4237: 4195: 4194: 4193: 4192: 4191: 4190: 4162: 4114: 4113: 4112: 4111: 4110: 4109: 4108: 4107: 4106: 4105: 4088: 4087: 4066: 4065: 4064: 4063: 4062: 4061: 4002: 4001: 4000: 3999: 3998: 3997: 3996: 3995: 3977: 3943: 3919: 3918: 3917: 3916: 3915: 3914: 3913: 3912: 3911: 3910: 3886: 3885: 3884: 3883: 3882: 3881: 3873: 3838: 3825: 3801: 3800: 3799: 3798: 3782:Starship.paint 3707:User:WMFOffice 3699: 3696:User:WMFOffice 3692: 3673: 3672: 3627: 3622: 3588:User:INeverCry 3584: 3583: 3582: 3581: 3580: 3579: 3578: 3577: 3475: 3474: 3473: 3472: 3471: 3470: 3401: 3400: 3358: 3357: 3354: 3349: 3348: 3347: 3346: 3345: 3320:67.164.113.165 3290:User:WMFOffice 3285: 3282: 3281: 3280: 3279: 3278: 3268:67.164.113.165 3259: 3222: 3203: 3202: 3201: 3200: 3199: 3198: 3197: 3172: 3171: 3156: 3155: 3154: 3153: 3116: 3115: 3114: 3113: 3112: 3111: 3110: 3109: 3108: 3084: 2939: 2936: 2935: 2934: 2903: 2902: 2901: 2900: 2899: 2898: 2897: 2896: 2895: 2885:67.164.113.165 2880: 2819:67.164.113.165 2815: 2814: 2813: 2715: 2714: 2713: 2712: 2711: 2710: 2709: 2708: 2707: 2706: 2705: 2704: 2703: 2702: 2589: 2575: 2574: 2573: 2505: 2502: 2501: 2500: 2480: 2462: 2444: 2425: 2410: 2409: 2408: 2407: 2406: 2405: 2404: 2403: 2402: 2401: 2400: 2376: 2375: 2374: 2373: 2372: 2371: 2320: 2319: 2266: 2265: 2264: 2263: 2262: 2261: 2260: 2220:", don't you? 2210: 2209: 2208: 2207: 2206: 2171: 2170: 2169: 2128: 2081: 2080: 2079: 2078: 2077: 2017: 2016: 2015: 2014: 2013: 2012: 2011: 2010: 2009: 2008: 2007: 2006: 2005: 2004: 2003: 2002: 2001: 2000: 1999: 1938: 1937: 1936: 1826:84 net edits, 1824: 1823: 1822: 1821: 1820: 1819: 1818: 1780: 1650: 1649: 1631: 1630: 1629: 1628: 1627: 1626: 1625: 1624: 1623: 1622: 1621: 1620: 1619: 1618: 1617: 1616: 1576: 1575: 1574: 1573: 1572: 1521: 1503: 1415: 1414: 1383: 1375: 1369: 1360: 1342: 1339: 1338: 1337: 1328: 1327: 1326: 1290: 1271: 1235: 1232: 1231: 1230: 1229: 1228: 1227: 1226: 1225: 1224: 1214:67.164.113.165 1205: 1152: 1151: 1150: 1135: 1044: 1043: 995: 994: 991: 986: 984: 981: 980: 979: 952: 935: 918: 905: 888: 871: 852: 851: 850: 843: 814: 797: 778: 764: 745: 744: 743: 742: 728:King of Hearts 722: 721: 693: 676: 675: 674: 673: 657:With respect, 655: 640: 605: 588: 538: 535: 534: 533: 513: 512: 511: 510: 509: 508: 507: 506: 487: 463: 442: 441: 440: 439: 438: 437: 401: 370: 369: 353: 352: 334: 333: 332: 331: 330: 329: 295: 278: 277: 255: 254: 240: 225: 210: 196: 157: 143: 142: 141: 91: 88: 85: 84: 79: 74: 69: 62: 52: 51: 34: 15: 9: 6: 4: 3: 2: 6182: 6167: 6162: 6158: 6152: 6148: 6147: 6146: 6142: 6138: 6134: 6133: 6132: 6131: 6128: 6125: 6122: 6117: 6116: 6111: 6107: 6103: 6099: 6098: 6097: 6093: 6089: 6088:Prometheus720 6084: 6080: 6079: 6074: 6073: 6066: 6063: 6058: 6054: 6053:Negative time 6051: 6050: 6049: 6045: 6041: 6037: 6036: 6035: 6034: 6031: 6027: 6023: 6019: 6015: 6011: 6007: 6003: 6000: 5998: 5994: 5990: 5986: 5983: 5982: 5981: 5976: 5971: 5966: 5962: 5957: 5953: 5949: 5942: 5941:edit conflict 5937: 5935: 5931: 5927: 5922: 5919: 5918: 5915: 5911: 5907: 5902: 5901: 5898: 5895: 5893: 5891: 5890: 5883: 5879: 5878: 5877: 5876: 5873: 5868: 5867: 5856: 5851: 5850:Seraphimblade 5844: 5843:edit conflict 5839: 5838: 5837: 5833: 5829: 5825: 5821: 5818: 5813: 5809: 5805: 5799: 5798:edit conflict 5794: 5793: 5792: 5788: 5784: 5776: 5774: 5770: 5766: 5757: 5756: 5749: 5745: 5741: 5737: 5735: 5730: 5729:Seraphimblade 5725: 5721: 5716: 5715:edit conflict 5711: 5710: 5707: 5703: 5699: 5694: 5688: 5685: 5681: 5679: 5675: 5671: 5667: 5666: 5665: 5664: 5661: 5658: 5652: 5647: 5646: 5645: 5644: 5641: 5638: 5634: 5633: 5632: 5631: 5630: 5629: 5624: 5621: 5615: 5610: 5609: 5608: 5607: 5606: 5605: 5601: 5597: 5590: 5586: 5582: 5578: 5568: 5565: 5562: 5555: 5554: 5553: 5552: 5551: 5550: 5549: 5548: 5547: 5543: 5539: 5534: 5529: 5525: 5521: 5518: 5513: 5512: 5511: 5507: 5503: 5499: 5496: 5495: 5487: 5483: 5479: 5475: 5470: 5468: 5464: 5460: 5455: 5454: 5449: 5445: 5441: 5437: 5436: 5435: 5434: 5431: 5428: 5424: 5423: 5410: 5406: 5402: 5397: 5396: 5395: 5391: 5387: 5383: 5382: 5381: 5377: 5373: 5369: 5368: 5367: 5363: 5359: 5355: 5354: 5353: 5349: 5345: 5341: 5340: 5339: 5338: 5334: 5331: 5327: 5323: 5319: 5315: 5312: 5307: 5303: 5299: 5298: 5297: 5294: 5290: 5289: 5286: 5283: 5279: 5277: 5273: 5269: 5265: 5259: 5255: 5251: 5247: 5246: 5245: 5241: 5239: 5234: 5225: 5224:edit conflict 5219: 5215: 5214: 5213: 5209: 5205: 5201: 5197: 5193: 5189: 5185: 5184: 5183: 5179: 5175: 5171: 5168: 5166: 5161: 5157: 5153: 5147: 5145: 5141: 5137: 5133: 5131: 5127: 5123: 5119: 5116: 5115: 5114: 5113: 5109: 5107: 5102: 5093: 5092:edit conflict 5086: 5072: 5068: 5064: 5060: 5057: 5056: 5055: 5052: 5051: 5046: 5045: 5044: 5040: 5036: 5032: 5024: 5020: 5017: 5013: 5010: 5007: 5003: 5002: 5001: 4996: 4990: 4981: 4977: 4973: 4969: 4965: 4961: 4960: 4959: 4955: 4951: 4947: 4943: 4939: 4938: 4937: 4936: 4932: 4928: 4916: 4912: 4908: 4903: 4902: 4901: 4900: 4896: 4892: 4886: 4866: 4863: 4862: 4857: 4856: 4855: 4851: 4847: 4842: 4837: 4833: 4828: 4827: 4826: 4822: 4818: 4814: 4810: 4806: 4805: 4804: 4800: 4796: 4792: 4791: 4790: 4785: 4784:Seraphimblade 4781: 4777: 4772: 4765: 4764:edit conflict 4760: 4754: 4751: 4746: 4745: 4738: 4731: 4727: 4726: 4725: 4722: 4717: 4713: 4712: 4711: 4707: 4703: 4698: 4697: 4696: 4692: 4688: 4683: 4679: 4678: 4677: 4673: 4669: 4664: 4662: 4659: 4654: 4650: 4645: 4643:Join WP Japan 4639: 4635: 4628: 4622: 4618: 4617: 4616: 4612: 4608: 4603: 4599: 4595: 4594: 4593: 4592: 4588: 4584: 4578: 4563: 4560: 4557: 4551: 4550: 4549: 4545: 4541: 4538: 4535: 4531: 4527: 4523: 4519: 4515: 4511: 4510: 4509: 4505: 4501: 4497: 4496: 4495: 4491: 4487: 4482: 4481: 4480: 4479: 4476: 4464: 4461: 4457: 4456: 4455: 4454: 4450: 4446: 4441: 4432: 4428: 4424: 4417: 4412: 4411: 4410: 4409: 4406: 4402: 4398: 4394: 4393: 4392: 4391: 4387: 4382: 4376: 4373: 4369: 4366: 4361: 4357: 4354: 4351: 4347: 4345: 4338: 4335: 4329: 4328: 4322: 4319: 4316: 4312: 4308: 4304: 4295: 4294: 4290: 4286: 4281: 4276: 4271: 4269: 4258: 4257: 4253: 4249: 4245: 4236: 4233: 4231: 4225: 4221: 4217: 4216: 4215: 4214: 4213: 4212: 4208: 4204: 4200: 4189: 4186: 4184: 4183: 4178: 4177: 4176: 4173: 4171: 4163: 4161: 4159: 4154: 4153: 4152: 4148: 4144: 4139: 4135: 4131: 4130: 4129: 4128: 4124: 4120: 4104: 4100: 4096: 4092: 4091: 4090: 4089: 4086: 4082: 4078: 4074: 4073: 4072: 4071: 4070: 4069: 4068: 4067: 4060: 4056: 4052: 4048: 4047: 4046: 4042: 4038: 4034: 4033: 4032: 4028: 4024: 4020: 4016: 4012: 4008: 4004: 4003: 3994: 3990: 3986: 3982: 3978: 3976: 3972: 3968: 3963: 3956: 3949: 3948:edit conflict 3944: 3942: 3939: 3936: 3935: 3931: 3927: 3926: 3925: 3924: 3923: 3922: 3921: 3920: 3909: 3905: 3901: 3896: 3895: 3894: 3893: 3892: 3891: 3890: 3889: 3888: 3887: 3880: 3877: 3871: 3865: 3864: 3863: 3859: 3855: 3851: 3847: 3846: 3845: 3842: 3836: 3831: 3826: 3824: 3820: 3816: 3811: 3807: 3803: 3802: 3797: 3793: 3789: 3783: 3778: 3777: 3776: 3773: 3771: 3767: 3762: 3753: 3748: 3747: 3746: 3745: 3742: 3740: 3736: 3731: 3724: 3720: 3716: 3712: 3708: 3705: 3697: 3691: 3690: 3686: 3682: 3678: 3671: 3668: 3666: 3662: 3657: 3650: 3649: 3648: 3647: 3644: 3633: 3626: 3621: 3620: 3616: 3611: 3606: 3601: 3597: 3593: 3589: 3576: 3572: 3568: 3561: 3556: 3555: 3554: 3550: 3546: 3542: 3537: 3536: 3535: 3531: 3527: 3523: 3519: 3518: 3517: 3513: 3509: 3505: 3500: 3499: 3498: 3497: 3493: 3489: 3485: 3481: 3469: 3465: 3461: 3456: 3455: 3454: 3450: 3446: 3442: 3441: 3440: 3436: 3432: 3425: 3420: 3419: 3418: 3417: 3413: 3409: 3399: 3395: 3391: 3388: 3385: 3382: 3378: 3375: 3371: 3367: 3364: 3360: 3359: 3353: 3352: 3344: 3340: 3336: 3331: 3330: 3329: 3325: 3321: 3317: 3316: 3315: 3314: 3310: 3306: 3302: 3299: 3295: 3294:User:Janneman 3291: 3277: 3273: 3269: 3265: 3260: 3258: 3254: 3248: 3242: 3237: 3236: 3235: 3231: 3227: 3223: 3221: 3218: 3213: 3212: 3207: 3204: 3196: 3192: 3188: 3184: 3181:I agree with 3180: 3179: 3178: 3177: 3176: 3175: 3174: 3173: 3170: 3166: 3162: 3158: 3157: 3152: 3148: 3142: 3136: 3132: 3128: 3127: 3125: 3121: 3117: 3106: 3102: 3096: 3090: 3085: 3082: 3078: 3076: 3071: 3064: 3060: 3055: 3054: 3052: 3048: 3044: 3043: 3034: 3033: 3031: 3027: 3025: 3020: 3012: 3011: 3009: 3005: 3001: 3000: 2993: 2988: 2987: 2986: 2982: 2980: 2975: 2968: 2965: 2964: 2963: 2962: 2958: 2952: 2946: 2931: 2927: 2923: 2917: 2913: 2909: 2904: 2894: 2890: 2886: 2881: 2879: 2876: 2875: 2869: 2868: 2856: 2852: 2849: 2845: 2841: 2840: 2839: 2834: 2833:Seraphimblade 2830: 2829: 2828: 2824: 2820: 2816: 2812: 2808: 2804: 2799: 2798: 2797: 2792: 2788: 2784: 2777: 2776: 2775: 2772: 2770: 2768: 2759: 2756: 2755: 2754: 2749: 2745: 2741: 2734: 2733: 2732: 2731: 2726: 2725:Seraphimblade 2721: 2701: 2697: 2693: 2688: 2687: 2686: 2681: 2680:Seraphimblade 2676: 2675: 2674: 2670: 2666: 2661: 2660: 2659: 2654: 2653:Seraphimblade 2647: 2646:edit conflict 2642: 2641: 2640: 2636: 2632: 2625: 2624:edit conflict 2620: 2619: 2618: 2613: 2612:Seraphimblade 2609: 2605: 2604: 2603: 2599: 2595: 2590: 2588: 2584: 2580: 2576: 2571: 2567: 2563: 2562:Beyond My Ken 2557: 2553: 2550: 2546: 2545: 2544: 2540: 2539:contributions 2536: 2532: 2531:Jo-Jo Eumerus 2528: 2524: 2523: 2522: 2521: 2516: 2515:Seraphimblade 2512: 2499: 2496: 2491: 2490: 2485: 2481: 2479: 2475: 2471: 2466: 2463: 2461: 2456: 2452: 2445: 2443: 2438: 2433: 2429: 2426: 2424: 2420: 2416: 2411: 2399: 2395: 2391: 2386: 2385: 2384: 2383: 2382: 2381: 2380: 2379: 2378: 2377: 2370: 2367: 2361: 2360: 2359: 2358: 2357: 2356: 2355: 2354: 2353: 2352: 2348: 2344: 2339: 2335: 2331: 2326: 2325:edit conflict 2318: 2315: 2310: 2308: 2303: 2301: 2295: 2290: 2288: 2283: 2281: 2275: 2272:are actually 2271: 2267: 2259: 2255: 2251: 2247: 2246: 2245: 2242: 2236: 2233: 2232: 2231: 2227: 2223: 2219: 2215: 2211: 2205: 2202: 2200: 2198: 2189: 2186: 2185: 2184: 2180: 2176: 2172: 2168: 2165: 2159: 2155: 2152: 2151: 2150: 2149: 2148: 2145: 2143: 2141: 2132: 2129: 2126: 2122: 2118: 2117:Beyond My Ken 2112: 2108: 2105: 2102: 2101: 2100: 2097: 2091: 2087: 2082: 2076: 2072: 2068: 2064: 2058: 2057:edit conflict 2053: 2052: 2051: 2047: 2043: 2039: 2038: 2037: 2033: 2029: 2023: 2018: 1998: 1994: 1990: 1989:Beyond My Ken 1986: 1985: 1984: 1981: 1980: 1975: 1974: 1973: 1968: 1962: 1953: 1952: 1951: 1947: 1943: 1939: 1935: 1931: 1927: 1926:Beyond My Ken 1923: 1922: 1920: 1916: 1912: 1911:Beyond My Ken 1906: 1902: 1899: 1897: 1892: 1891: 1890: 1886: 1881: 1874: 1873: 1871: 1867: 1863: 1862:Beyond My Ken 1857: 1853: 1850: 1847: 1846: 1845: 1842: 1840: 1838: 1829: 1825: 1816: 1812: 1808: 1807:Beyond My Ken 1802: 1798: 1794: 1790: 1789: 1788: 1783: 1778: 1774: 1773: 1772: 1768: 1764: 1760: 1759: 1757: 1753: 1749: 1748:Beyond My Ken 1743: 1739: 1736: 1733: 1732: 1729: 1725: 1721: 1715: 1707: 1703: 1700: 1697: 1696: 1694: 1690: 1686: 1685:Beyond My Ken 1680: 1676: 1673: 1670: 1669: 1668: 1664: 1660: 1656: 1652: 1651: 1648: 1644: 1640: 1636: 1633: 1632: 1615: 1611: 1607: 1603: 1602: 1601: 1597: 1593: 1589: 1585: 1581: 1577: 1571: 1567: 1563: 1558: 1557: 1556: 1552: 1548: 1543: 1542: 1541: 1538: 1536: 1534: 1526: 1522: 1520: 1516: 1512: 1508: 1504: 1502: 1498: 1494: 1490: 1489: 1488: 1484: 1480: 1475: 1474: 1473: 1469: 1465: 1460: 1459: 1458: 1454: 1450: 1445: 1444: 1443: 1440: 1438: 1437: 1432: 1431: 1430: 1426: 1422: 1417: 1416: 1412: 1408: 1404: 1403:Beyond My Ken 1398: 1394: 1391: 1389: 1384: 1382: 1381: 1376: 1374: 1370: 1368: 1366: 1361: 1359: 1357: 1352: 1351: 1350: 1349: 1348: 1347: 1336: 1333: 1329: 1325: 1322: 1314: 1313:Jo-Jo Eumerus 1309: 1308: 1307: 1303: 1302:contributions 1299: 1295: 1294:Jo-Jo Eumerus 1291: 1289: 1285: 1281: 1276: 1272: 1270: 1267: 1265: 1264: 1259: 1255: 1254: 1253: 1252: 1249: 1244: 1223: 1219: 1215: 1211: 1206: 1204: 1200: 1196: 1192: 1191: 1190: 1186: 1182: 1178: 1174: 1171: 1170: 1169: 1165: 1161: 1157: 1153: 1149: 1145: 1141: 1136: 1134: 1131: 1126: 1124: 1119: 1117: 1111: 1107: 1103: 1102: 1101: 1097: 1093: 1089: 1086: 1085: 1084: 1080: 1076: 1072: 1068: 1063: 1062: 1061: 1060: 1056: 1052: 1042: 1039: 1037: 1033: 1030: 1029:PETITIONS FOR 1026: 1024: 1020: 1018: 1014: 1011: 1007: 1004: 1000: 997: 996: 990: 989: 978: 974: 968: 964: 960: 956: 953: 951: 947: 943: 939: 936: 934: 930: 926: 922: 919: 917: 914: 913:Donald Albury 909: 906: 904: 900: 896: 892: 889: 887: 883: 879: 875: 874:Strong oppose 872: 870: 867: 864: 862: 856: 853: 849: 846: 841: 837: 833: 832: 831: 827: 823: 818: 815: 813: 809: 805: 801: 798: 796: 793: 788: 787: 782: 779: 777: 773: 769: 765: 763: 759: 755: 750: 747: 746: 741: 737: 733: 729: 726: 725: 724: 723: 720: 716: 711: 706: 701: 697: 694: 692: 688: 684: 683:50.106.16.170 681: 678: 677: 672: 668: 664: 660: 656: 654: 649: 648:Seraphimblade 645: 644:stop doing it 641: 639: 636: 631: 630: 625: 624: 623: 619: 615: 612:Knowledge. -- 610: 606: 604: 601: 600: 597: 594: 589: 587: 584: 579: 578: 573: 572: 571: 570: 566: 562: 556: 554: 548: 545: 532: 528: 524: 520: 515: 514: 505: 502: 497: 491: 488: 486: 482: 477: 472: 467: 464: 462: 459: 457: 450: 449: 448: 447: 446: 445: 444: 443: 436: 433: 430: 429: 425: 421: 420: 419: 415: 411: 407: 402: 399: 395: 390: 389: 388: 385: 383: 377: 372: 371: 368: 364: 360: 355: 354: 351: 348: 336: 335: 328: 324: 320: 316: 315: 314: 313: 312: 308: 304: 300: 296: 294: 289: 288:Seraphimblade 285: 280: 279: 276: 273: 271: 269: 268: 261: 257: 256: 253: 249: 245: 241: 239: 235: 231: 226: 224: 220: 216: 211: 209: 205: 201: 197: 195: 191: 189: 184: 175: 174:edit conflict 169: 163: 158: 156: 152: 148: 144: 140: 137: 133: 132: 131: 126: 119: 113: 112: 111: 110: 106: 102: 97: 83: 80: 78: 75: 73: 70: 67: 63: 61: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 6150: 5989:StudiesWorld 5960: 5955: 5951: 5920: 5888: 5887: 5865: 5861: 5803: 5723: 5650: 5613: 5593: 5497: 5321: 5301: 5237: 5188:StudiesWorld 5122:StudiesWorld 5105: 5087: 5084: 5058: 5049: 4941: 4924: 4881: 4860: 4840: 4831: 4812: 4808: 4795:Grandpallama 4779: 4775: 4770: 4743: 4736: 4729: 4687:Grandpallama 4681: 4579: 4575: 4522:Jovanmilic97 4486:Jovanmilic97 4472: 4437: 4377: 4374: 4370: 4364: 4359: 4358: 4355: 4349: 4348: 4342: 4339: 4330: 4326: 4323: 4320: 4305: 4301: 4279: 4274: 4272: 4267: 4264: 4241: 4223: 4219: 4196: 4181: 4166: 4157: 4155: 4137: 4133: 4115: 4037:StudiesWorld 4018: 4014: 4006: 3985:Grandpallama 3980: 3932: 3869: 3834: 3829: 3805: 3757: 3726: 3704:role account 3701: 3674: 3652: 3629: 3585: 3522:User:Magiers 3508:Gestumblindi 3503: 3476: 3445:Gestumblindi 3431:Gestumblindi 3406:provided by 3405: 3396: 3392: 3389: 3386: 3383: 3379: 3376: 3372: 3368: 3365: 3361: 3335:Gestumblindi 3287: 3241:power~enwiki 3226:StudiesWorld 3210: 3205: 3135:power~enwiki 3089:power~enwiki 3074: 3059:power~enwiki 3038: 3023: 2995: 2991: 2978: 2966: 2945:power~enwiki 2941: 2907: 2871: 2858: 2847: 2766: 2719: 2716: 2607: 2579:StudiesWorld 2560:CU-blocked. 2547: 2510: 2507: 2488: 2483: 2464: 2427: 2337: 2333: 2321: 2307:SerialNumber 2306: 2299: 2287:SerialNumber 2286: 2279: 2269: 2217: 2213: 2196: 2139: 2115:CU-blocked. 2103: 1978: 1909:CU-blocked. 1893: 1860:CU-blocked. 1848: 1836: 1805:CU-blocked. 1791: 1746:CU-blocked. 1734: 1698: 1683:CU-blocked. 1671: 1654: 1639:StudiesWorld 1587: 1532: 1524: 1506: 1435: 1401:CU-blocked. 1385: 1379: 1377: 1371: 1364: 1362: 1353: 1345: 1344: 1274: 1262: 1237: 1209: 1195:Trumblej1986 1181:StudiesWorld 1173:Trumblej1986 1160:Trumblej1986 1155: 1140:Trumblej1986 1123:SerialNumber 1122: 1115: 1092:StudiesWorld 1088:Trumblej1986 1075:Trumblej1986 1070: 1066: 1051:StudiesWorld 1048: 1040: 1035: 1034: 1028: 1027: 1022: 1021: 1016: 1015: 1009: 1008: 1002: 1001: 998: 962: 958: 954: 937: 920: 907: 890: 878:StudiesWorld 873: 860: 854: 816: 800:Weak Support 799: 785: 780: 748: 695: 679: 643: 628: 608: 591: 576: 557: 552: 549: 543: 540: 523:Softlavender 518: 469: 455: 426: 404: 381: 299:this article 283: 266: 265: 259: 244:StudiesWorld 215:Softlavender 187: 167: 162:Softlavender 101:Softlavender 95: 93: 65: 43: 37: 5783:Floquenbeam 5560:Doug Weller 5459:Floquenbeam 5372:Lepricavark 5136:Lepricavark 4995:Talk to me! 4988:Oshawott 12 4907:Yngvadottir 4597:typically). 4555:Doug Weller 4242:As an FYI, 4119:Carabinieri 3788:Schreibvieh 3752:Schreibvieh 3723:Statement D 3719:Statement C 3715:Statement B 3711:Statement A 3131:trade union 2851:WP:HOUNDING 2447:complaint. 2274:assumptions 2028:Nosebagbear 1967:Talk to me! 1960:Oshawott 12 1653:Where did " 1278:to admin. 1275:yet another 1242:S Philbrick 992:My Proposal 925:Lepricavark 861:Captain Eek 663:Yngvadottir 495:S Philbrick 475:S Philbrick 357:"...good?" 36:This is an 6057:* Pppery * 6002:Ivanvector 5985:Ivanvector 5970:Ivanvector 5812:* Pppery * 5724:allegation 5698:Praxidicae 5581:Praxidicae 5520:~ ToBeFree 5478:~ ToBeFree 5440:Shearonink 5427:Sir Joseph 5386:DuncanHill 5344:Praxidicae 5306:* Pppery * 5304:, before. 5152:Javert2113 5063:Tryptofish 5019:Tryptofish 4927:Tryptofish 4809:especially 4716:* Pppery * 4540:Tazerdadog 4229:TREKphiler 4143:Randykitty 4095:Courcelles 4077:Randykitty 4051:Tazerdadog 4023:Randykitty 3900:Randykitty 2783:Javert2113 2758:Javert2113 2740:Javert2113 2334:don't know 2090:WP:BAITing 1896:aspersions 1777:Ivanvector 1017:CALLS UPON 983:A Proposal 840:* Pppery * 804:Tazerdadog 768:~ ToBeFree 147:~ ToBeFree 6121:Fut.Perf. 6010:pingó mió 6006:Galobtter 5889:Susmuffin 5720:BU Rob 13 5118:WMFOffice 4950:Yair rand 4946:BN thread 4280:necessity 4011:Stalinist 3810:Cognizant 3709:posts of 3632:WMFOffice 3596:doubly so 3183:Ajraddatz 3120:Ajraddatz 3041:ONUnicorn 2998:ONUnicorn 2844:Ymblanter 2803:Thryduulf 2692:Thryduulf 2665:Thryduulf 2631:Thryduulf 2594:Thryduulf 2365:Montanabw 2343:Simonm223 2330:Montanabw 2240:Montanabw 2163:Montanabw 2131:Montanabw 2095:Montanabw 2086:Simonm223 2067:Simonm223 2042:Ajraddatz 2022:Ajraddatz 1606:Ajraddatz 1580:Ajraddatz 1547:Ajraddatz 1479:Ajraddatz 1449:Ajraddatz 1421:Ajraddatz 1156:via media 1010:BELIEVING 1003:ACCEPTING 659:Yair rand 614:Yair rand 607:We don't 544:concisely 414:pingó mió 410:Galobtter 284:shouldn't 267:Susmuffin 230:Nil Einne 200:Yair rand 82:Archive 5 77:Archive 4 72:Archive 3 66:Archive 2 60:Archive 1 5948:BU Rob13 5828:creffett 5670:SchroCat 5596:rdfox 76 5538:SchroCat 5326:Bishonen 5174:SchroCat 5039:contribs 5004:Agreed. 4885:The Land 4846:The Land 4668:The Land 4621:Rdfox 76 4607:rdfox 76 4500:SchroCat 3955:BU Rob13 3850:BU Rob13 3760:starship 3729:starship 3655:starship 3567:Debenben 3526:Debenben 3488:Claude J 3480:log book 2967:Support. 2855:Odysseus 2552:Rivselis 2549:conduct. 2268:What we 2107:Rivselis 2063:WP:CIVIL 1901:Rivselis 1852:Rivselis 1828:Rivselis 1797:Rivselis 1738:Rivselis 1714:Rivselis 1675:Rivselis 1635:Rivselis 1393:Rivselis 1356:CIVILITY 1320:xaosflux 1036:ENDORSES 1023:ENTREATS 754:X-Editor 398:The Land 359:The Land 319:The Land 303:X-Editor 260:horribly 117:Gamaliel 6137:EllenCT 6102:EllenCT 5943:× many) 5921:Comment 5401:EllenCT 5156:Siarad. 5009:Snowman 4891:28bytes 4817:WaltCip 4737:implied 4702:WaltCip 4601:Board." 4583:28bytes 4475:Spartaz 4445:EllenCT 4416:Techyan 4381:Techyan 4248:Dolotta 3967:Amakuru 3854:Amakuru 3600:King of 3560:Magiers 3545:Magiers 3429:it :-) 3424:Kudpung 3305:Magiers 2922:Vermont 2912:Vermont 2787:Siarad. 2744:Siarad. 2188:Thincat 2175:Thincat 1071:DEMANDS 921:Support 908:Comment 817:Comment 749:Support 700:King of 696:Comment 680:Support 561:28bytes 471:missed? 456:~Swarm~ 382:~Swarm~ 39:archive 5050:Enigma 4861:Enigma 4518:WP:AGF 4423:Viztor 4019:method 4015:action 3962:WP:ANI 3806:office 3765:.paint 3734:.paint 3721:, and 3660:.paint 3641:ASTILY 2511:chosen 2158:denial 2104:Agreed 1979:Enigma 1562:Sitush 1493:Sitush 1247:(Talk) 972:話して下さい 938:Oppose 891:Oppose 855:Oppose 781:Oppose 500:(Talk) 480:(Talk) 394:WP:WIR 376:Essjay 345:ASTILY 170:idea. 6157:Leviv 5975:Edits 5871:v^_^v 5740:©Geni 5268:Xover 5059:Sigh. 5006:Giant 4749:v^_^v 4682:could 4623:. ··· 4311:守望者爱孟 4275:never 4158:serve 4134:serve 3694:Will 3598:? -- 3303:). -- 3264:BATNA 3216:v^_^v 2494:v^_^v 2451:Leviv 2437:bleep 2415:©Geni 2413:work. 2313:54129 2293:54129 2212:Re: " 1782:Edits 1592:RexxS 1464:RexxS 1129:54129 942:Hobit 791:v^_^v 634:v^_^v 582:v^_^v 553:agree 490:Swarm 483:|TB| 466:Swarm 96:Wired 90:Press 16:< 6151:some 6141:talk 6106:talk 6092:talk 6044:talk 6026:talk 5993:talk 5930:talk 5910:talk 5832:talk 5800:× 2) 5787:talk 5778:him. 5769:talk 5744:talk 5702:talk 5674:talk 5600:talk 5585:talk 5564:talk 5542:talk 5524:talk 5506:talk 5482:talk 5463:talk 5444:talk 5405:talk 5390:talk 5376:talk 5362:talk 5348:talk 5330:talk 5272:talk 5254:talk 5238:Talk 5208:talk 5192:talk 5178:talk 5170:Floq 5140:talk 5126:talk 5106:Talk 5094:× 2) 5067:talk 5035:talk 4993:)== 4972:talk 4968:ST47 4966:... 4962:And 4954:talk 4948:. -- 4931:talk 4911:talk 4895:talk 4850:talk 4821:talk 4799:talk 4780:hope 4706:talk 4691:talk 4672:talk 4658:El_C 4611:talk 4587:talk 4559:talk 4544:talk 4526:talk 4504:talk 4490:talk 4449:talk 4427:talk 4401:talk 4386:Talk 4313:and 4289:talk 4252:talk 4224:open 4207:talk 4182:xeno 4147:talk 4123:talk 4099:talk 4081:talk 4055:talk 4041:talk 4027:talk 3989:talk 3971:talk 3930:Tera 3904:talk 3858:talk 3819:talk 3792:talk 3770:talk 3739:talk 3685:talk 3665:talk 3571:talk 3549:talk 3530:talk 3512:talk 3492:talk 3464:talk 3449:talk 3435:talk 3412:talk 3339:talk 3324:talk 3309:talk 3272:talk 3230:talk 3191:talk 3165:talk 3124:talk 3075:Talk 3024:Talk 2979:Talk 2926:talk 2916:talk 2889:talk 2823:talk 2807:talk 2720:both 2696:talk 2669:talk 2635:talk 2598:talk 2583:talk 2566:talk 2556:talk 2535:talk 2474:talk 2419:talk 2394:talk 2347:talk 2254:talk 2226:talk 2179:talk 2121:talk 2111:talk 2071:talk 2046:talk 2032:talk 1993:talk 1965:)== 1946:talk 1942:Jorm 1930:talk 1915:talk 1905:talk 1866:talk 1856:talk 1811:talk 1801:talk 1767:talk 1752:talk 1742:talk 1724:talk 1706:talk 1689:talk 1679:talk 1663:talk 1643:talk 1610:talk 1596:talk 1566:talk 1551:talk 1515:talk 1497:talk 1483:talk 1468:talk 1453:talk 1436:xeno 1425:talk 1407:talk 1397:talk 1373:TOS. 1298:talk 1284:talk 1263:xeno 1218:talk 1199:talk 1185:talk 1164:talk 1144:talk 1096:talk 1079:talk 1067:ASKS 1055:talk 946:talk 929:talk 899:talk 895:ST47 882:talk 826:talk 808:talk 772:talk 758:talk 736:talk 687:talk 667:talk 618:talk 609:want 599:7754 596:chen 565:talk 527:talk 519:does 424:Tera 363:talk 323:talk 307:talk 248:talk 234:talk 219:talk 204:talk 188:Talk 176:× 4) 151:talk 124:talk 105:talk 6161:ich 5884:. ― 5808:... 5651:Rob 5614:Rob 5322:how 5232:MJL 5218:TRM 5100:MJL 4991:==( 4832:was 4771:was 4626:日本穣 4285:Wnt 4203:Wnt 3981:you 3934:tix 3870:Rob 3835:Rob 3830:why 3815:Wnt 3681:Wnt 3069:MJL 3018:MJL 2973:MJL 2767:WBG 2470:Wnt 2455:ich 2332:we 2197:WBG 2140:WBG 1963:==( 1837:WBG 1533:WBG 428:tix 262:. ― 182:MJL 168:bad 6155:– 6143:) 6108:) 6094:) 6055:. 6046:) 6028:) 6012:) 5995:) 5978:) 5972:(/ 5956:is 5932:) 5912:) 5834:) 5789:) 5771:) 5746:) 5704:) 5676:) 5655:13 5618:13 5602:) 5587:) 5544:) 5526:) 5508:) 5484:) 5465:) 5457:-- 5446:) 5407:) 5392:) 5378:) 5364:) 5350:) 5328:| 5274:) 5256:) 5210:) 5194:) 5180:) 5142:) 5128:) 5069:) 5061:-- 5041:) 5037:• 5031:DJ 5027:Th 4974:) 4956:) 4933:) 4913:) 4897:) 4852:) 4823:) 4801:) 4708:) 4693:) 4674:) 4640:· 4636:· 4633:投稿 4629:· 4613:) 4589:) 4546:) 4536:5 4528:) 4520:. 4506:) 4492:) 4451:) 4429:) 4403:) 4388:） 4378:-- 4291:) 4268:is 4254:) 4220:is 4209:) 4149:) 4125:) 4101:) 4083:) 4057:) 4043:) 4029:) 3991:) 3973:) 3906:) 3898:-- 3874:13 3860:) 3839:13 3821:) 3794:) 3717:, 3713:, 3687:) 3617:♠ 3573:) 3551:) 3532:) 3514:) 3504:if 3494:) 3482:, 3466:) 3451:) 3437:) 3414:) 3341:) 3326:) 3311:) 3274:) 3255:) 3249:, 3232:) 3193:) 3167:) 3149:) 3143:, 3126:) 3103:) 3097:, 2992:be 2959:) 2953:, 2928:) 2910:. 2891:) 2848:vs 2825:) 2809:) 2698:) 2671:) 2637:) 2600:) 2585:) 2568:) 2541:) 2537:, 2529:. 2476:) 2465:If 2449:– 2432:R2 2428:If 2421:) 2396:) 2349:) 2300:—— 2280:—— 2256:) 2228:) 2181:) 2123:) 2073:) 2048:) 2034:) 1995:) 1948:) 1932:) 1917:) 1868:) 1813:) 1785:) 1779:(/ 1769:) 1754:) 1726:) 1691:) 1665:) 1645:) 1612:) 1598:) 1568:) 1553:) 1517:) 1499:) 1485:) 1470:) 1455:) 1427:) 1409:) 1304:) 1300:, 1286:) 1220:) 1210:us 1201:) 1187:) 1166:) 1146:) 1116:—— 1098:) 1081:) 1057:) 975:) 963:we 959:us 948:) 931:) 901:) 884:) 828:) 810:) 774:) 760:) 738:) 717:♠ 689:) 669:) 620:) 593:Rs 567:) 529:) 468:, 416:) 365:) 325:) 309:) 250:) 236:) 221:) 206:) 153:) 107:) 6139:( 6124:☼ 6104:( 6090:( 6042:( 6024:( 6008:( 5991:( 5952:I 5939:( 5928:( 5908:( 5845:) 5841:( 5830:( 5796:( 5785:( 5767:( 5759:" 5742:( 5717:) 5713:( 5700:( 5672:( 5598:( 5583:( 5540:( 5522:( 5504:( 5480:( 5461:( 5442:( 5403:( 5388:( 5374:( 5360:( 5346:( 5335:. 5270:( 5252:( 5240:‐ 5236:‐ 5228:– 5226:) 5222:( 5216:@ 5206:( 5190:( 5176:( 5162:) 5160:¤ 5158:| 5154:( 5150:— 5138:( 5124:( 5108:‐ 5104:‐ 5096:– 5090:( 5065:( 5033:( 5029:e 5025:— 4970:( 4952:( 4929:( 4909:( 4893:( 4887:: 4883:@ 4848:( 4841:I 4819:( 4797:( 4766:) 4762:( 4704:( 4689:( 4670:( 4646:! 4609:( 4585:( 4542:( 4524:( 4502:( 4488:( 4447:( 4425:( 4418:: 4414:@ 4399:( 4384:（ 4287:( 4250:( 4205:( 4172:: 4160:. 4145:( 4121:( 4097:( 4079:( 4053:( 4039:( 4025:( 3987:( 3969:( 3957:: 3953:@ 3950:) 3946:( 3938:₵ 3902:( 3856:( 3817:( 3790:( 3784:: 3780:@ 3772:) 3768:( 3754:: 3750:@ 3741:) 3737:( 3683:( 3667:) 3663:( 3638:F 3614:♣ 3609:♦ 3604:♥ 3569:( 3562:: 3558:@ 3547:( 3528:( 3510:( 3490:( 3462:( 3447:( 3433:( 3426:: 3422:@ 3410:( 3337:( 3322:( 3307:( 3270:( 3252:ν 3246:π 3243:( 3228:( 3189:( 3163:( 3146:ν 3140:π 3137:( 3122:( 3100:ν 3094:π 3091:( 3077:‐ 3073:‐ 3026:‐ 3022:‐ 2981:‐ 2977:‐ 2956:ν 2950:π 2947:( 2932:) 2924:( 2914:( 2887:( 2873:9 2866:7 2863:4 2860:1 2821:( 2805:( 2793:) 2791:¤ 2789:| 2785:( 2781:— 2763:∯ 2750:) 2748:¤ 2746:| 2742:( 2738:— 2694:( 2667:( 2648:) 2644:( 2633:( 2626:) 2622:( 2596:( 2581:( 2564:( 2554:( 2533:( 2472:( 2439:) 2435:( 2417:( 2392:( 2345:( 2327:) 2323:( 2252:( 2224:( 2193:∯ 2177:( 2136:∯ 2119:( 2109:( 2069:( 2059:) 2055:( 2044:( 2030:( 2024:: 2020:@ 1991:( 1944:( 1928:( 1913:( 1903:( 1884:✉ 1864:( 1854:( 1833:∯ 1809:( 1799:( 1765:( 1750:( 1740:( 1730:) 1722:( 1716:: 1712:@ 1710:( 1704:( 1687:( 1677:( 1661:( 1641:( 1608:( 1594:( 1564:( 1549:( 1529:∯ 1513:( 1495:( 1481:( 1466:( 1451:( 1423:( 1405:( 1395:( 1315:: 1311:@ 1296:( 1282:( 1216:( 1197:( 1183:( 1162:( 1142:( 1094:( 1077:( 1053:( 969:( 944:( 927:( 897:( 880:( 866:⚓ 824:( 806:( 770:( 756:( 734:( 714:♣ 709:♦ 704:♥ 685:( 665:( 616:( 563:( 525:( 432:₵ 412:( 361:( 342:F 338:- 321:( 305:( 246:( 232:( 217:( 202:( 190:‐ 186:‐ 178:– 172:( 164:: 160:@ 149:( 127:) 121:( 103:( 50:.

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge

:Community response to the Wikimedia Foundation's ban of Fram/Archive 2 - Knowledge

Index