Knowledge talk:STiki/Archive 5

1139:. Essentially, wiki markup can have some very long tokens, i.e., external URLs, wikilinks pointing to particular sections, some templates, etc. If naively dumped into the diff browser, these would result in a horizontal scrollbars being displayed in the worst case, and hideous justification in most cases. Thus, my code inserts ZWS white space characters in long tokens. These say, "hey, you can break the token/line here if you have to, but if you don't use that break, then don't display anything." While not visible to a human user, those characters are still "there", and show up when copy-paste actions are performed, i.e., copy-pasting a long token like "electroencephalograph" might turn into "elect#roenceph#alograph." This was my motivation in turning off copy-paste (and enabling metadata fields to be copy-pastable). 4161:

issues. In its current version, STiki has never really fallen behind, it keeps pace with the edits just fine. Same with the frontend client work. Computationally, STiki and its associated DB work consistently eat about 50% of one processor. There are elegant ways to get non-critical data at a later time if en.wp servers are suffering, but this ends up being more a PITA than it is probably worth, as some features would require two implementations: "historical" and "immediate" (i.e., the editcount example). The historical versions can be extremely inefficient, and cause more server work than the original (plus if there is some delay, the queries are likely to miss caches).

821:

just target the easily vandalism, leaving behind damage. Secondly, I'd rather see this amount of workload distributed over multiple days. If a competition classifies many-thousand edits over the course of several hours, those users will be deep in the queue and getting a low vandalism hit-rate. Spread that same effort over several days and the net-gain (in terms of vandalism percentage) would be much higher. I think the milestone barnstars are a good step towards rewarding loyal users. Your suggestion of "usage drives" is solid, but needs some refining, and maybe some rules if it is to become reality. Thanks,

2397:

Amsterdam, I believe), and (2) the STiki server (Philadelphia). The farther you are geographically from these locations, then STiki should be marginally slower (but not 30 seconds/edit!). This is surprising because most of the network work happens in the background, *before* an edit becomes the one displayed in the browser (everything is threaded). Where are you geographically, if you don't mind? Have you used a tool like Huggle before? How slow is it? What is your ping time to server "armstrong.cis.upenn.edu"? Answer these question and we can begin troubleshooting the issues. Thanks,

3293:

significant (I'd have to write a very time consuming script to determine if we've ever seen one before, meh). Regardless, *we can't (simply) fix bugs regarding feature calculation*. Because the AD-Tree was trained over a particular implementation, it needs to classify over that same implementation. Changing the implementation would require re-calculation for all corpus instances and the installation of a new tree. Simply not worth it for this. I'll place a TODO in my code, but I am opting not to elevate this to "bug" status. Thanks,

1034:

cause the issue you describe. This also indicates you were classifying pretty fast. Display information is built/cached ~10 edits ahead of where you are working. However, once every 30 secs. or a minute, I scan through the local cache and ensure that no page has been edited while in cache. Seemingly you also evaded that check. Inevitably, someone will ask "why not do the check immediately before the edit is displayed to a user?" Because that is the last place you want the latency of an API call to slow edit advancement.

4520: 31: 2493:

some other research tasks; and one in particular was writing to a table that contained hundreds of billions of entries (and the index updates were a big *ouch* on DB utilization and memory management). I've dumped most of that table to an archival one so writes now happen to a much smaller table. This has the potential to make STiki's DB queries a little snappier (though it may not even be human noticeable). Thanks,

3323:. They are certainly interesting features (that further establish that school children are a major source of vandalism), but they aren't really driving the classifier. As an academic, sometimes I implement these things because they fulfill more theoretical objectives than practical ones (or more accurately, I implement them because they fill theoretical needs in my publications, which I then implement faithfully). 2684:-- and yes, I can help you through the Java syntax. As you note with the templates above, there is a tricky number of corner cases. Before we start worrying about "perceptions", let's see if we can equal whatever the Knowledge parser is doing. Note that if we need to exchange lengthy source code or worry about details too trivial for public consumption it is fine for us to coordinate privately via email. Thanks, 3523:

development it might be helpful to create a sub-page and develop our ideas there. This would be a little less public-facing and could act as more of a sandbox for our ideas. Then when bulk implementation time rolls around, we have a consolidated resource to consult. We could even section out the page by data/query source (i.e., content-features, user-features, article features, etc.). In fact, let's use (

4054:

This does, however, have the side effect that we cannot review these features in hindsight, or possibly use that edit for retraining (at least without computing the full feature set offline). Similar with stopping mid-way through the tree when we have an intuition about relative score (or just know it won't be a poor one). Given ongoing academic intentions, I prefer to follow these things to the end.

2170: 1543: 1382: 3578:

queue (WikiTrust) might be so "bad" is that something like 80% of the RID requests I pass to their API (RIDs just made on the wiki) timeout without yielding the WikiTrust score. We can approximate that score via STiki's user reputation (a more binary version), possibly with normalization by edit count. Point being, I don't think these are viable features for a live implementation. Thanks,

3780:

password inside it). All it would take is an attacker who claims to have compiled an "improved version" of STiki and convince someone to download it and try it out, and they a password. Simply not worth it for the minor inconvenience of entering it each time. Thanks for the suggestion, though, and I am currently considering the "pass message" you describe below. Thanks,

3515:

and incremental way (i.e., whenever a new idea for a feature rolls in) isn't exciting (why be a less distanct second-place behind CBNG?) and a PITA (retraining, install the new ADTree, ensure scalability, etc.). I was also a bit frustrated to hear the CBNG folks claim they had equaled or slightly improved upon our performance in CICLing over the Potthast corpus.

286:

all out. Second, I am well aware that just regex-ing for "*bot*" in a username is not the most robust way to determine permissions. I was following from the logic of Allens last post. I am pretty sure there is a "new account patrol" or "username patrol" or something of the sort that has some edit-filter-like rules to detect obvious violations of

2600:

what links are on a page. However, then I ask the API, "hey, is this link actually one on the page?". Only if the answer is yes do I report it on IRC and feed it to the anti-spam system (note that I don't make clients take this API hit when processing diffs, thus the inaccuracies you report). I can tell you I am right about 95% of the time.

1983:

ended up templating a good vandal fighter. After I realized my mistake I tried to repair it, but not before I got reverted and templated myself (by someone using STiki ironically). This was about 12 hours ago, and since then I've seen the same problem happen twice more, with a total of 5 vandal fighters being templated for vandalism. (

3519:

proposal/dissertation will be essentially will be one and the same. I am writing my dissertation now and just plan to leave one chapter blank = proposal. Write one conference paper about work I've already started and use that to fill in the blank chapter = dissertation. Not exactly the way its supposed to happen, but oh well).

3354:

in mind (as I will for any patches). (Your code is quite clear, BTW; good job!) I understand fully about the retraining problem; anytime I suggest a new or modified tree-feature, assume that I'm suggesting it as something to do in the future whenever enough of them accumulate to make it worth recalculating.

2432:

cmd is of course disabled. I will give you an update as soon as I get home. For my firewall, I use the default Windows Firewall, and my antivirus is Microsoft Security Essentials (usually quite non-intrusive, so I don't believe that is the issue). Thanks for the prompt reply guys, hope you fix it soon :)

4175:

I certainly wouldn't encourage doing anything later that would require a separate implementation and/or be inefficient when done later. I was more thinking of ones that are basically an API request (not altering depending on at the time or later) followed by a database insertion. I note that it would

4053:

First, this is an interesting idea: rather than pre-computing a feature set and providing it to the ADTree model, we could just compute features on-demand if they are encountered along the tree path. This is an implementation detail that deserves serious consideration when I "bit the bullet in bulk."

3975:

I placed it in the "talk" space because I didn't want to have to construct the page with any formality in presentation (i.e., an article), but to be a sandbox for idea development and discussion. I guess talk pages also imply certain norms I wouldn't want to require, either. In my eyes the difference

3600:

Number of edits total should certainly be part of it. How about increasing that threshold based on user reputation, as in (time-decayed) number of "offensive" edits? (Better yet would be number of warnings on the user's talk page, but that would be harder - I know the STiki server is already figuring

3577:

Sidenote, we shouldn't concern ourselves too much with the multiple WikiTrust features (esp. of the CICLING paper). WikiTrust just hasn't been getting the job done quick enough lately, and I suspect might have scalability issues with the pace at which en.wp currently operates. Part of the reason that

3353:

I'm certain that you'd find far more things problematic if you ever read over my academic code than I do with yours - mostly "huh? what's this for?"; intra-code documenting, aside from naming variables and subroutines well, is not a particular strong point of mine unless I'm particularly keeping this

3258:

it fell under, although that should perhaps be a separate characteristic from country to allow for a larger-scale grouping.) The timezone itself is not actually used in the classification; it is used to figure out what the day-of-week and time-of-day it is in the IP's location. If there are enough of

3253:

That's a reasonable solution when it comes to those IPs not classifiable by country; the country is returned as "", which isn't treated as a separate country for reputations, but probably should be if there's a significant number of them. (Actually, even if an IP couldn't be classified by country, it

3238:

Or can you make these IPs be treated as a separate set by the alternating decision tree? I guess partly it depends on how many IPs fall into this category. Could we collect enough data on them? I guess even if we can't collect enough data on the time dependence we could still come up with a decent

2863:

500 links so any additions beyond those would be reported as errors ("Barack Obama" for example). Third, with both of us iterating on these things, how should we manage the code versions we are each working on? FWIW, I'll fix these two bugs I indicate above, let everything run for a while, and try to

2861:

Good observation on the case-insensitivity -- I'll convert to lowercase for the purpose of checking against ground-truth and error reporting. Second, I discovered a bug in the "ground truth". My API query only returns the first 500 external links on the page (as I correctly documented, haha...). I'll

2818:

I thought so on the accuracy from the code & comments in it, unless you had a further set of testcases you were running it over. BTW, I note that some cases of apparent false positives may actually be due to that the "contains" in confirm_urls doesn't compare hostnames case-insensitively (and the

2492:

Yes, STiki does lots of caching to try to speed the user experience. Of course, when you start STiki these caches are empty so a lot of network resources are used trying to fill them. Orthogonally, I just discovered something this morning that might improve performance. STiki shares a machine/DB with

1283:

I think there are probably more polite ways to go about it than calling Huggle out directly. Large portions of the "comparison to other tools" section on the main STiki page are implicit digs at Huggle and the other tools (all in good competition, of course). A statement like "Tired of getting beaten

259:

will give you the first 500, and adding &austart=R will give you the rest. Putting such a list into the STiki backend database then loading it into the program should not be too terribly difficult - I'd produce a patch myself if I knew Java. I am not, however, sure if this is actually necessary -

4313:

Ummm.. that button has been in place for over a year. Try watching it more closely. If you pressed "AGF" or "vandalism" on the previous edit, then you cannot go "back" from that and it will be disabled (you need to handle your screw ups manually, and probably with an apology to the editor involved).

4037:

approach? This seems to fit naturally with the ADTree framework. i.e. You could use an ADTree before making some of the API calls, you would then only make the API call if requested to do so by ADTree. The ADTree would be designed (pruned) so that it doesn't bother getting info if it doesn't make

3623:

Hmm. My inclination was to lean towards simplicity. This also helps end-users know what is going on. Complex solutions also imply more and more queries to Knowledge or my server (and with the lag complaints, I am starting to be a little hyper-aware of this). After all, how many registered users with

2780:

By 95% "accuracy", I mean that after hours/days of running, calls to the method in feature_hyperlinks.java will return 95% (I have this automatically emailed to me 4x daily as part of a larger report). That is, of the links which feature_hyperlinks.java identifies, 95% check out when we ask the API

2676:

Glancing over my code, links are handled in two places. seems to be the more viable effort and is the "backend" method used for link analysis. contains method which does it for the GUI. When I cite 95% accuracy I was speaking of the former. That is the one we can automatically evaluate and should

2302:

I have not retrained since AGF inclusion. I suspect the AGF cases will be discarded given the issues you mention. STiki is foremost an anti-vandalism tool and it is much easier to treat the problem as a two-class one. AGF edits certainly tend to share some characteristics of vandalism, and therefore

2282:

I am curious how "good faith revert"s will be treated for machine learning. If this was learning to create an anti-vandalism bot, then they would probably be considered innocent or simply not counted. For STiki purposes, they could be considered anything from neutral (between innocent and vandalism)

1927:

As well as checking for previous levels of uw-vandalism for the vandalism queues in highest_warn_level, it may be best to check for uw-test# and uw-delete# (and I can see uw-error#, uw-joke#, uw-notcensored#, uw-defamatory#, and uw-unsourcedBLP# as possibilities, although perhaps not for causing AIV

1013:

marked as a rollback situation (as in, it isn't a self-revert, as far as I can tell). Wiki-DIFF does show up changes, although it also indicates that it was already reverted. I suspect the reversion happened between the time the STiki server picked up the diff and it sent the diff to my client, with

285:

Greetings. First, it seems that the "bot" edit in question got in the queue before the rule was written, so I won't consider this a bug. Moreover, the queue tables in the DB are done with numerical identifiers, so its not as if I can just run a "DELETE... WHERE EDITOR LIKE '%BOT%' query to kick them

4358:

Actually its not by choice that the back button gets disabled, once you press vandalism or AGF then you actually revert the article (and template the user as well) this cannot be simple undone by a press of back button and needs to be manually done. while apologizing Please Do not Blame "STiki" or

3957:

On a point of terminology, do we want to use the word "feature"? I gather this is what is used in academic circles. It is the feature of edit that informs the probability of vandalism... but there is the chance that this could get misunderstood as a "feature request" for the software. Perhaps we

3779:

On second thought, I have decided to decline this request for security reasons. STiki's code is open source. The format and location of the properties file is obvious to anyone who opens up the source. Thus, any program on your system will know where to find this file (and the potentially plaintext

3522:

As an aside, you may notice I tend to be quite anal/responsive about keeping up to date with my talk page and all these suggestions. This does tend to get a little fatiguing. That being said, I appreciate your ideas and think they will prove fruitful in the future. For things like long-term feature

2365:

I have used Stiki for a while now, and I have noticed a slight lagging issue in stiki 2.0. Although annoying, it was still endurable. However, with the new Stiki 2.1, I am experiencing Stiki taking up to half a minute to load a page, as well as it hanging for minutes when I make any sort of revert.

2112:

Hi Adjwilley and thanks for your use of the tool. Suffice to say, if the vandalism/damage resides on the left hand side of the diff presentation, then you should certainly give it a good look to see if it is a "revert" situation. Yaris was correct in pointing you to the revision comment. Be careful

4160:

There are graphs out there that will show you the load on en.wp servers. They seem to be having issues with replag lately. However, this seems to rarely happen with normal operations -- high replag generally follow cache clears from version updates, DDOS attacks, etc. Regardless, I can't fix their

3514:

Second, regarding new features. I must admit I haven't been too eager to improve the "STiki (metadata)" approach lately and have been focusing on the interface instead. I too have lots of feature ideas (plus the ones from PAN-CLEF/CICLING papers that need to be brought live). Doing this in a small

3169:

I have mapped your previous classifications in the database to the new username. The change will be reflected on tonight's leadboard update. Do realize that any surviving ignore actions by "WillDude123" could be displayed to "W.D." -- I wouldn't worry about this though, ignores tend not to survive

3071:

Slowed things down to see if that helps. We already waited a little bit after an edit made was made before processing it (for orthogonal and justified reasons). With a little more delay (still in the justifiable range) maybe the parser will get its work done in time. Let's see what an error report

2725:

I agree that feature_hyperlinks.java is the code to start with. In terms of 95% accuracy, are you meaning that it spots 95% of the URLs, that the URLs it spots are external links by the API 95% of the time, or what? If you happen to know a couple example pages where it isn't correct, that would be

2599:

I'll note that link parsing is proven to be a darn hard problem for me. In particular, its one I've spent a whole lot of time on (I mean, I have 2 publications regarding Knowledge link spam), so its not like it was a minor issue. In particular, I use all the logic I currently have to "guess/parse"

2461:

Update. Pinging armstrong.cis.upenn.edu gets me a reply in about 380 ms, so I don't think that's the problem. Also, I tried using the program despite the lag, and found that after about 5 minutes, the lag disappears! However, if I quit and restart the .jar, the lag returns for another few minutes.

2431:

I am in Melbourne, Australia, so it is quite far from the servers. That may explain the issue to an extent. Huggle was fine for me, however. My broadband is usually quite fast, with speedtest giving download speeds of over 10 mbits. As for the ping, I can't do it right now because I'm at work, and

2396:

That is a completely unacceptable amount of lag. For users besides Tony, how long does it take for you to advance between revisions? There is really only one culprit for delay throughout the program: network latency. Your computer needs to talk to (1) the Wikmedia servers (in Florida, Virginia, or

2053:

BTW, which queue were you using? I am guessing it was CluBot NG (the default). This does seem to occasionally pick up edits by experienced editors because it looks at the content of the edit rather than the history of the editor. Maybe there is an argument for filtering CBNGs results, e.g. with

1754:

Yeah, I liked the content, but felt it was a bit buried by going in the image caption. I reorganized things a bit into an explicit "interface" section. When I implement your "redlinks" feature request, I plan to make it an option, so it can also be described in that same section. I still feel that

1259:

Also W.D., I should say thanks and that I appreciate the effort. My most immediate comment is that the "stop asking rhetorical questions" frame doesn't really transmit any information to the reader. The biggest battle the tool probably faces is "well... why not use Huggle?". I wonder if a frame or

1033:

Hmm. I don't compute the diff, I fetch it directly from the API by providing the RID I want the "current page" diff'ed against. This is done after a confirmation that the "current page" is still the one the vandalism score was computed for. If a revert slips in between these two API calls it might

457:

Thanks, fixed the error in my local copy and will roll out with the next release. Yes, this isn't code that I imagined gets called much (if ever). Despite lots of error-catching code in place for CommunicationsExceptions, I am not sure how often the client is actually successful in recovering from

3808:

Hmm. the application wouldn't have to look like STiki or have anything to do with Knowledge in order to steal the password. In fact, this is something some malware does: it has profiles of where plaintext passwords might reside and just checks these paths in bulk. Granted, it is not STiki's fault

3709:

No no no. That is not how you want to compute edit count. See meta=userinfo (ui), which has the downfall of counting across all namespaces. However, using "usercontribs" has bigger issues. "usercontribs" lists at most 500 edits and then you have to start making recursive calls. That user who just

3631:

As the EUROSEC'09 paper explains, the lack of normalization was an acknowledged shortcoming but done for robustness reasons. If you create a feature like that, you give someone a means by which to alter their own reputation by making edits to smooth out the bad ones (e.g., possibly using a bot in

3457:

In terms of info-gain rankings, also keeping in mind in any decisions made whether the feature in question requires a new API query would be good. The first two of the above, incidentally, wouldn't require an API query (except for an occasional update from the educational shared IP category); the

3056:

and then immediately pinged the API to ask which xlinks where there. The link at the end of the edit did NOT appear. Waited about 10 seconds, whala! it appeared. Clearly we are hitting the API before the xlinks can be parsed out of the diff; or replication lag is killing us. In practice, we don't

2603:

Due to the sheer displeasure this causes me, this is something low on my priority list. Is it something you'd like to take a shot at fixing? After all, aren't you Perl folks ninjas with the regexps? It is easy to test any functionality autonomously on the server-side, complete with error reports

2576:

It occurs to me that the code in feature_hyperlinks.java might be reusable for this (or at least could be unified with whatever more-reliable solution is created). I do note that that code has the assumption that citation urls are always prefixed with "url\s*=\s*" (such as in parse_url_and_desc),

820:

I'm open to discussion on this, but I have my doubts. Foremost, the idea of a "race" could have ill consequences. If someone classifies so quickly that they make mistakes, this is not a good reflection on the tool. Such a mindset could also cause one to pass on edits that require "extra work" and

768:

Umm... why? Sure, it looks like this user was moving pretty quick through classifications, but not terribly so. I picked out 5 or so reverts at random, and all of them were pretty legitimate cases of vandalism. What evidence of wrongdoing do you have? Checking his user-talk, the user only got one

691:

I haven't done enough investigation with these other diff algorithms to really speak about them. However, I can confirm that STiki does use the diff provided by the Mediawiki API, which is HTML and CSS markup. The Java object which handles the diff browser (an "HTMLPane" or something of the sort)

113:

I'm seeing a SD5bot edit (485184267 for Thomas Veazey) showing up in the STiki queue. I've taken a look at the STiki source, and while I know Perl, not Java, I can't offhand see any problem with edit_process_thread's should_queue function. About all I can think of is that this is an old insertion

4081:

Think carefully about what information could actually be extracted after the event. Some information will change... but some you will always be able to get. For example, you could always get the en.wp server to give you the diff between two versions and it will always be the same... unless the

3879:

This has been encoded on my local machine and will be included in the next release. Use of "pass" will now be tracked persistently (although because it is based on a "setting" and not a DB query, this count will not be persistent across different machines). Experienced users will see the warning

2557:

Hi Allens, at this point I think the link-parsing is in need of some serious inspection and re-thinking. When my time affords it, I'll dig in and address all of these link-related issues you've pointed out. If I recall, it turns out to be more non-trivial than it should be; but I have to imagine

2537:

in add_hyperlinks would work? I admittedly don't know Java regexes. (BTW, if they work anything like Perl's, it will be more efficient for XLINK_REGEX to be "(https?|ftp)://(\\s\\|]+|" + gui_globals.BRACKETED_REGEX + ")*" - non-greedy regexps like BRACKETED_REGEX cause a lot of backtracking.) If

1982:

I tried out STiki for the first time yesterday and after a few edits I was shown the diff of someone else's revert of obvious vandalism. I guess that seeing the vandalism (something about POO being the best food) distracted me from noticing that the vandalism had been reverted, so I reverted and

168:

The CHANGELOG.txt file agrees with you; good point - I'll keep an eye out for when the CBNG ones are from. (BTW, it isn't going off of the "bot" "permission" directly, but instead from having "bot" in their names, which should be limited to only approved bots and similar. The same is true of not

3838:

I also respect your approach to the problem and believe you are vigilant in keeping your machine clean. However, I have to program for a general purpose audience who may not meet the same standard. The last thing I need is irate talk page traffic over such a minor thing. Plain-text passwords in

3418:

All very good points. I'll note I am aware of (and have an implementation + ADTree model for) many other features. See my CICLING and PAN-CLEF papers. I simply haven't gotten around to bringing them all live (and there may also be scalability issues with certain features, or a large quantity in

3292:

IP addresses, which are generally not publicly routed, and therefore STiki would never see them. The tiny remainder map to "United States Armed Forces" and "Satellite Providers." Bottom line, even if we mapped all these users to their own "special group" I don't think it would be statistically

1635:

After a single edit has been classified with the mouse (thereby giving the button panel "focus"), the keys "V", "G", "P", and "I" will mark edits as "vandalism", "good-faith", "pass" and "innocent" respectively. While in the same mode, the PG_UP, PG_DOWN, UP_ARROW, and DOWN_ARROW keys will also

3489:

Hi Allens. First off, thanks for the code contribution sent via email. Those statistics look great! I will integrate this into the code base when an opportunity presents itself (just got your second email, I'll wait for an update!). One minor question, though. We've been addressing thet ask of

3364:

may well be of interest, especially if expanded from the current single IPs to the surrounding /24 or so. Admittedly, it also includes some college and university addresses - but only ones from which there has been vandalism previously, as far as I can tell. There may be some other listings of

2250:

Your post above (which was signed) and SineBot's subsequent and redundant appearance here should give us some indication what is happening. This is not an issue with STiki (it has placed 75,000+ talk page warnings; there would have been many many complaints by this point if STiki did not sign

1142:

However, I must admit this even bugs me at times. I think the solution might be to leave the ZWS characters in place and then manipulate how clipboard actions work (filter out any ZWS characters whenever a copy action is performed). I've assigned this ticket T#012 in the table up top and will

3979:

Feel free to add such a description for "features" to the page. However, the very impetus for creating that page was so that there didn't have to be an excess of "hand-holding" descriptions. Add a warning to this effect you like. I tend to be rather generous in describing technical bits with

2649:

need to be accounted for; these don't require http://, and none would be noted by feature_hyperlinks.java as far as I can tell), or whether ones that a person would perceive should be checked also. Admittedly, we won't have ground-truth from the API for the latter, which would be a headache.

662:. Schnark's diff is then accessed using tabs that appear above and below the diff. This means you can look at wikEdDiff and Schnark's varient and the same time (if you really want to). The last tab in Schnark's diff gives you some parameters you can tweak. These are described further at 2259:. In particular, the latter has a sandbox that you can test the bot in. Browsing your contribution history it seems like most your edits outside the main namespace are with STiki, thus why it seems like STiki is the problem. Hope you get this sorted out, and thanks for your use of my tool. 3518:

I need to bite the bullet, do it in bulk, and include some novel features to retake "first place". My current situation doesn't afford the time for this. However, I will make a promise that I *will* make this happen once my proposal is defended in a month or two (I should note that my

3419:

combination). The vast majority of features require a new API query, and at several edits a second at peak times, this puts some stress on the system. I really need to do an info-gain ranking and start the consideration from there (which I might have already done, somewhere). Thanks,

2125:

Second, the tool does not have an explicit mechanism to filter by things like "edit count". However, features like this are *implicit* in the scoring algorithms. A prolific editor who uses the word "poo" will produce a lower vandalism probability than a brand new editor that does the

2906:

Well, once you can send me how to convert feature_hyperlinks.java into an offline testbed, I can start directly working on the code instead of doing setup for it. Then you can worry about dissertation writing instead of coding for a bit, unless I need to ask for help on something...

730:

OK. Looks like its not quite as simple as I thought... But if Andrew could get Schnark's code working from inside STiki that would be cool. In the mean time, I recommend everyone accesses it the normal way and clicks on the "wiki-diff" link to see the diff in their web browser.

3604:(BTW, is there some reason that user reputation as used inside STiki is purely focused on number of offending edits and doesn't take into account the user's total number of edits and/or total number of recent edits? I'm particularly surprised on this given the PAN-CLEF results.) 2781:

about the URLs on the page. Note that we can't ask the API about links in hindsight, it will only tell us what links are on a page "now." Note also that this approach doesn't speak to the accuracy of the inverse: i.e., the number of links that our approach misses altogether.

2366:

This renders the software completely unusable. Any programmers out there want to take a look into this issue? For more detailed descriptions of the issue, please comment on my talk page. Oh, and btw, good job on that good faith revert option. It has been long missed by me!!!

944:

1. It will cause a lot of rubbish reverts and 2. It will turn into a full on scramble if several thousand people were unleashed onto the limited number of vandalism available. God knows what will happen if hundreds of people clicked on revert at exactly the same time...

769:

warning for templating a regular (which isn't terrible considering his quantity of reverts). Also, mass rollback is going to be pretty worthless, given that the user hasn't edited in over a month's time and there will be plentiful intermediate edits on articles. Thanks,

3710:

reached 1 million edits and then used STiki for the first time? Yeah, I tried to "usercontrib" his edit count for milestone page reporting.... The operation ran for 5+ minutes and then overflowed something like 128MB of memory. No thank you! 15:59, 26 May 2012 (UTC)

2746:) and am analyzing it. Converting feature_hyperlinks.java into an offline testbed would indeed be very helpful (at some point in the future, getting it to read in an outside file for testing instead of a built-in one would be nice, but I can get along without that). 3186:

WD, can you please explain to me how you realized this username change? What do you actually login with? I note that even after my manual update above, that I began seeing "WillDude123" appear again on the leaderboard. Is this all just a bunch of redirects? Thanks,

707:

Since both Cacycle's and my diff are implemented in JavaScript there is no direct way to access them via an external application. So the only way to use an alternative diff in STiki is to re-implement one of the diffs in Java. The code for the diff algorithm is at

397:

Yes. I think having a local list of bots on the STiki server is the best way. This can be updated using the API call once per day (or a different frequency). This means that you don't need the millions and millions of API queries a month that Andrew is worried

1947:

Acknowledged! Though I'd imagine many of these rarely get used in practice, it may be nice to detect them and push a level higher using vandalism warnings. I need to stop with the talk page chatter for now, it's a busy office day and I have thesis writing to do!

3713:? Why would you need to know if the person had a higher edit count than the threshold? Just specify that, which should be less than 500, as the number of entries to return. If you don't get back that number of entries, the person hasn't edited enough yet. 1057:

Oh, right (regarding not computing diffs locally), now I remember. Whoops! (In terms of classifying quickly, I read at something over 1000 words a minute.) Just a bit ago, I was seeing a high replication lag for watchlist updates, so that may well be it.

290:(including having "bot" in a username without the bot-flag). I just thought I'd let the burden fall on that group. This little shortcut saves STiki millions and millions of API queries a month (or the pain of setting up some type of local cache). Thanks, 3901:

No. The queue which is selected at start-up is not *always* CBNG as one might think. This is set via a query to my DB. When CBNG has been down for long periods, I have set the default queue to "STiki (metadata)" and I intend to retain control over this.

3690:

Edit count in article-space, gotten via list=usercontribs w/ucnamespace=0, may be preferable for the threshold. Having among the buttons ones that automatically open the article's talk page (good thought) after the revert/innocent-marking would be nice.

4489:

I should probably emphasize the "Offline" in "Offline Review Tool." You can't undo edits via ORT. Moreover, there is no guarantee the content still exists in the most recent article version. It's useful for ex post facto review (i.e., corpus building).

3980:

intuitive descriptions on this talk page. This takes a long time. I don't mean to sound rude, but in the spirit of getting things done, sometimes I/we cannot cater to everyone -- and the talk page split was designed so this would happen more naturally.

1239:. A lot of them are quite busy. There is some way to add your own ad (i.e., a STiki advert) to this category and it becomes part of a rotation that is randomly displayed for those who choose to add the advert template to their user (talk) page. Thanks, 835:

I feel it's very important to distinguish been a "good faith" revert and a vandalism revert. If I'm correct, warnings are not distributed for GF reverts? If so, then the tool good be ill-used in order to garner extra edits in a competitive environment.

114:

into the queue, from before whenever should_queue was put in. I've also been seeing a number of instances of such from the CBNG queue (I hadn't realized that these shouldn't be showing up until I looked at the source), perhaps also from old insertions.

4141:

I'm certain that the en.wp server load varies - I've seen the maxlag warning popping up on my watchlist a number of times. The STiki server would be under variable load from two sources: Keeping up with en.wp changes and keeping up with STiki clients.

4108:

How about a compromise? Put any data retrieval that isn't immediately necessary into a separate thread with low priority, using API calls with the "maxlag" parameter set (and pausing as appropriate if it comes back as needing a pause due to high lag).

3551:

In terms of your proposal/dissertation, you might find interesting how most (all?) of Europe does dissertations - they're basically a compendium of the person's papers stuck together with some introductory material and linkages explaining how it fits

3218:

This essentially assumes that any IP address with an undecidable timezone is in the UK (GMT+0 timezone). I suggest it would be better to have it return whatever's the most common IP-address editor timezone - probably the east or west coast of the US.

3823:

Personally, I prefer software to automate as much as possible, and I'm willing to take responsibility for keeping my computer free of malware and other nasties. But I won't press the issue any further; it's your program and I respect your decision.

2213:

I've noticed that when STiki adds a warning to a user's talk page, it doesn't sign it at all (with four "~"s). Am I missing something? I'm a bit tired of SineBot spamming my talk page with warnings about not signing my posts. Could you fix this?

1783:

Would it be possible to include HTTPS support when connecting to the Knowledge API? I would revert vandalism while at work, but I would prefer not to have my password floating around in corporate network logs. Thanks, and keep up the great work!

3625:

50 edits actually vandalize? As long as their is a low false-positive rate it won't annoy the end-user. Moreover, its not like we will stop the revert/template altogether, just say "hey, you might want to take a second look at the edit and the

4424:

Please be assured that I fully understand that any "undoing" has to be done manually. I take full responsibility for any action that I may perform here on Knowledge. May I also state that I value the support that I have received from fellow

1037:

Unless this becomes something frequent, I am not going to worry about it. Now that I think about it, replication lag between WMF servers could be another possible explanation (which I think people at Village Pump have been reporting values :

4479:

Yes, there is, I would possibly interested in even getting the users in a category, for instance, educational institutions and patrolling the edits of such category. On a side note, does STiki add anything to the score if it is a shared IP?

2730:, to expand on the existing test cases imbedded in feature_hyperlinks.java:main; I'm planning on writing some perl code to extract URLs from the resulting HTML output for comparison with feature_hyperlinks.java's output (I doubt I'll get it 3510:

Can this happen? Or are diffs always split at token granularity? I feel like I saw this case once in my studies about two years ago. I'll need to strip out such font tags before processing, but can you think of any other considerations?

3458:

third one should be able to "piggyback" on another API query for the categories (adding "categoryinfo" to "prop="). I'll keep in mind whether an API query is required for what suggestions to make about new features (I've got a list...).

3285:

Foremost, it absolutely terrifies me that Allens is reading my code; I can only imagine how many more of these posts I might wake up to :-)! Yes, this is some inelegant code, but no, I don't think it is a serious problem. First, my IP-:

2530:', with only the last link being active (or not, if it ends with a "}}"). This gets bad enough in some cases (490032557, 489906611) that one side of the diff is expanded widthwise while the other side is compacted into a narrow column. 1693:

Good point, I feel I've written it out a couple of times in talk-page history, as well. Would one of my friendly talk page watchers like to take on this task? I know I move about 10x quicker when using shortcuts vs. the mouse. Thanks,

3287:

GMT+/- database has complete Internet coverage, that is, there is an entry for every IP address. However, it is true that not all IPs have a populated GMT+/- field, but this figure is less than 0.01%. The *vast* majority of these are

3938:

I think having a subpage for features is a good thing. Ideas get suggested now and then and if keeping the info in one place probably means that Andrew doesn't have to explain multiple times why the same thing would be practical.

4176:

be valuable for the STiki server requests to be able to use the "bot" flag, to request more data per API call, and a request for this (or continuing to have this) would be more likely successful if using maxlag whenever possible.

2618:

I can take a look at it, although you will need to look over any Java-specific syntax... One question is whether we actually need to be just looking for what the system will turn into an external link (I just realized that

3002:

the URLs, and my browser converts the hostnames to lower-case for interpreting them (as browsers are supposed to - alterations in the case of the hostname won't make any difference), but it isn't actually doing so for the

1134:

Hi guys. I don't think the problem here is with Java's HTMLPane implementation, as this is an issue most browsers face. That pane can have copy-paste functionality, I have just explicitly turned it off due my inclusion of

692:

cannot handle things like CSS, so some modifications are made to "simplify" the API diff into very basic HTML. On top of this, some logic is added for line-breaks. Is there a way to query for these modified diffs? Thanks,

493: 4038:

much impact on the probability of vandalism. This pruning would include (but not be limited to) cases where the probability of vandalism is so low either way that the edit is unlikely to reach the top of the queue.

2116:

We also need to distinguish between STiki (the GUI) and the backend algorithm/queue that determines what edits you are displayed. It is likely you were using a third-party queue called CBNG, (based on the logic of

3357:

That's interesting regarding those not being killer features, and on the schoolchildren (I think you mentioned that in a paper and I forgot it...). Three thoughts that I had earlier that this brings back to mind:

1084:

It would be really useful to be able to select text from the diff and copy it to the clipboard. Unless I'm being extremely thick, this doesn't seem possible at present. Is it possible to add this functionality?

1928:

postings - instead, do a uw-vandalism4 or 4im warning). Similarly, checking for uw-advert# for the link-spam queue may be preferable. Corresponding modifications to im_warn_present would be advisable, of course.

3490:

finding diffs in an article. However, part of the motivation for this was to be able to accurately detect links in diff presentation. This doesn't present major differences. However I can imagine a case where

2121:). Because of its third party nature, I do not modify the logic, and yes, this queue does have an unusual habit of displaying reverts (I would agree with Yaris that it is "rare"). If you go to the menu-: --> 1966:

Understand on dissertation writing; luck! In regard to frequency of usage, I was looking specifically for ones used by Twinkle, which I figure are likely to be used more frequently. Uw-test# is also used by

1109:

Would it be doable to render the HTML using different out-of-the box code? A Google search throws up a few things that look interesting... but I don't know enough details to know what would work for you.

367:

bots. Anti-vandalism bots tend to operate without this flag but (as with users reverting vandalism) with the minor edit flag, however; this makes it particularly important to whitelist the anti-vandal bots.

237:

In terms of the current issue. Could it be something as simple as case sensitivity on the word "bot"? I'm afraid I don't know which bit of the code you are looking at and I've never looked at it before.

2698:

It should also be fairly straightforward to setup as an offline testbed for your work (it already has a main method to this effect), as it is has no real serious dependencies on other classes. Thanks,

4504:

Re Sidenote: It does not at this time. Such a feature is in development, though it is difficult to detect exhaustively (more realistically, we would just be looking for the existing category members).

1922: 3213: 3950:. That way the page is not about threads of talk but is a collection of information. This means it is easier to suggest ideas in the associated talk page and then summarise what it all means on 2122:"queue", you can change the prioritization logic. I administrate the "STiki (metadata)" queue, and have hard-coded rules against this sort of thing (but perhaps lower accuracy across the board). 598:

STiki actually simply takes the HTML of the standard MediaWiki diff and edits it to make it usable in the Java window (including adding external links if desired); it doesn't do a separate diff.

2277: 1809:

Yes, this seems like a very good idea. I've filed it as T#013 in the tracking table up top. Barring any unexpected difficulty, this change should be expected in the next distribution. Thanks,

1458:

I'm American, and I think "beaten" sounds more appropriate. Anyone picky enough to care about such things can easily copy the template to their userspace and make the trivial change. Thanks,

3809:

that you got malware on your machine (or the hacked version of STiki, or whatever the point of entry is...). However, shouldn't STiki have some responsibility not to exacerbate the problem?

3951: 3947: 626:

If the displaying of diffs is based on reading it from MediaWiki html, it should be quite straight forward to display a wikEdDiff or Schnark's diff in the STiki GUI. That would be awesome.

3794:

Sorry, I don't follow. If an attacker wished to use a supposedly "improved" STiki to harvest passwords, couldn't they just modify STiki to transmit the password once it has been entered?

3053:

More problems! Ground-truth doesn't hold!!!! I started noticing that URLS were appearing verbatim in my error log as they were in my subsequent manual API xlinks queries. I then made edit

1843:, but it'd still hide the password and other credentials. If possible, I'd consider letting the user decide which connection type they'd like to use, balancing speed and security. Thanks! 701: 554:

wikEd includes wikEdDiff. Have you seen the diff aspects of it though? When looking at a diff, click on the Δ icon underneath it. It took me a while to realise the button was there!

2143:

Thank you. I was in fact using the default cluebot setting, and yes, by being more careful with my lefts and rights I would have avoided the situation. I appreciate the responses here.

313: 1103:

This one has come up before. Andrew decided to make the text non-selectable because he had to add invisible characters to it to make it work with the Java HTML pane that he is using.

530: 356:

For the remainder, the possibility of an edit being by an authorized bot may be checked for in a couple of ways - note that neither is necessary if the username doesn't match "BOT"!

1584:

Nice! I've also added the hard-coded template (that pointing only to the STiki advert) to the main STiki page so others can show support if they wan. Thanks for your contribution.

1442:

Would you prefer "beat" to "beaten". I know Americans say "beat"... but I don't know if that is seen as colloquialism or standard English. I could always parameterise the choice!

1326:

ironically is used in Stiki, but it happens very rarely with Stiki and hapens very frequently with other tools. In fact this is one of the main reasons why I love STiki so much. --

3536: 2413:

Another thing that might help (Though i cannot explain why it worked before) - are you using any form of firewall or antivirus that does real-time web scanning? Personally i use

4314:

Otherwise (if you last pressed "pass" or "vandalism") you can go back at most one edit. Let me know if it does not exhibit this behavior (or if anyone else has issues). Thanks,

3958:

should add a qualifying term. e.g. say "informing feature" or something like that. At the very least there should be an explanation at the top of the page about what you mean.

2077:

so read the edit summary compare the diff, and try not to restore vandalism. being human, one can make mistake sometimes but if you are careful, this wont happen often. regards--

1656:

yes, I guess a lot of new users don't know this (including me, until Andrew informed me in my early days with stiki), So this makes a strong case to include the shortcuts in the

3595: 1200: 142:

If you were on the CBNG queue, that would fit with your theory that it was enqueued and then not removed from the queue because bots weren't removed from that until 2012-04-12.

3632:

user space). This another one of those things that you should probably implement in practice, but might attract considerable criticism when getting a paper reviewed. Thanks,

2054:

the Huggle white list. However, even if this were done, there would still be the chance of a good edit by a new editor showing up so the biggest thing to say is: be careful.

805:

To promote usage of the tool, we could have an annual STiki-athon where the person who fights the most vandalism in one day wins! If you think it is a rubbish idea then say.

2417:

on my main PC, but its webshield in combination with Huggle causes a 5 second slowdown while Huggle loads a diff. Once it is disabled revisions are loaded almost instantly.

3232: 434:

It should be "submit_agf", not "submit_vandalism". Hopefully, this won't have caused any problems aside from some errors in the database, since the old gui_revert_and_warn

3375:

Checking to see whether the page title and/or any categories matched "chool" might well be informative, particularly in combination with the educational IP classification.

1941: 2296: 4127:

To what extent are there quiet periods (and busy periods) for STiki and the en.wp server? If they exist then doing things this way seems like the best of both worlds.

108: 1260:

two might be more effective if they addressed "comparison of STiki with other tools" aspects, i.e., reservation system, intelligent routing, score memory, etc. Thanks,

3361: 3201:

Before I realized my username changed, I made a few edits. It seems I can login with both but only W.D. has all my contribs. So I can use both, which is a bit strange.

1499: 227:

Gosh. That's not the greatest way to detect a bot. It's obviously open to abuse by vandals (although how far such an account would actually get is another matter).

423: 146: 2524: 1977: 3999: 985:. I'm sure we could design such a system... perhaps based on my idea... whether Andrew would want to / have time to program such a system is another question. 4345: 4323: 249: 3617: 1521:

page, rather than the image file. 3. Perhaps a template is best for this purpose? 4. Other than possible inclusion in the rotation, how can we use it? Thanks,

4075:

I guess if you did implement something like this you could also have a script that extracted the missed-off information when called. However, you'd have to:

2019: 1884: 1862: 1834: 1818: 1645: 127: 3527:). You could get a start there by (a) listing what STiki already has, (b) transferring ideas from the CICLING paper, and (c) dumping your own ideas. Thanks, 2538:

you'd like, I can try modifying a local copy to make sure it'll compile, at least (I haven't yet due to the need to download a couple additional libraries).

3007:" part. Uppercase is allowed (and can have an effect) for the directory path, but I am not terribly worried about the extraction process altering the case. 451: 4438: 4405: 4377: 4371: 2784:

If you see the , I am going to uncomment the that reports the errors. I will let it run like that, and send you some of that output for analysis. Thanks,

2551: 2186: 2089: 1672: 1559: 1338: 889: 584: 563: 545: 230:

For the benefit of Andrew, does anyone know a good way to extract a user's permissions from the Knowledge API? A clunky way would be to regex a page like

209: 2529:

I am seeing a repeated problem in which, IF STiki is in "Activate Ext-Links" mode, the display contains repeated instances of the link followed by '": -->

4255: 4033:

Given that one of the issues with new informing features is whether or not it is worth getting the data from an API call, would it be possible to take a

618: 3889: 3332: 3081: 1910: 1703: 762: 485: 4003: 3995: 3542:

Quite welcome on the code; I've sent the revised version. I'm afraid that the diff in use is indeed capable of breaking things down within URLs - see

845: 830: 792: 778: 3946:

the right structure to go for? I think splitting the page by feature type makes sense.... but I think you want a page in the WP: name space, maybe

3660:

We may want the user to double check. And then have a think about what the most appropriate action is. Three things which may be a good idea are:

2518: 2502: 2406: 2157: 1517:

Neat. A couple of questions. 1. How do we get this into the Knowledge adverts rotation? 2. At minimum, we need to turn the image into a link to the

1503: 1425:

I am a big fan of this one! It will get the standard treatment and be up on the main page within the day (ugh, its going to be a long one). Thanks,

936: 859: 4095: 4063: 4020: 3989: 3685: 2138: 1678: 1565: 1481: 1467: 1453: 1434: 1344: 1269: 1248: 1152: 919: 748: 2025:

Slightly related comment: A wonderful feature to have (IMO) would be if STiki showed the edit summary of the offending edit, along with the diff.

969: 725: 505:

which STiki served me. The edit confused the standard MediaWiki diff (and the diff browser in STiki, which I assume is also based on solving the

4396: 4362: 4273: 4189: 4170: 3740: 3641: 3587: 3568: 3471: 3428: 3393: 3302: 3129: 3066: 3020: 2965: 2920: 2873: 2832: 2793: 2759: 2708: 2693: 2663: 2613: 2590: 2567: 2352: 2330: 2314: 2251:

correctly). Instead, something about your custom signature formatting seems not appease SineBot. However, I am not sure what the problem is. See

2177: 2080: 2005:

vandalism)? My second question is: is there a way to opt out of receiving edits performed by established users who have, say, more than X edits?

1957: 1764: 1733: 1663: 1550: 1329: 1071: 1048: 994: 895: 880: 467: 329: 299: 200: 3848: 3833: 3818: 3803: 3761:

Since STiki remembers the WP username, I assume it's saving some state somewhere. I wonder if it would also be possible for STiki to remember:

2486: 2456: 2390: 2039: 1512: 1180: 1166: 4499: 4484: 4474: 4072:

Ha ha. Yes. Maybe that is a good definition of satisficing "Something that works well in practice but doesn't help with academic intentions."

3205: 3196: 3179: 2425: 2233: 2192: 2068: 1593: 1530: 1293: 1278: 982: 2095: 1610:

I may be simply missing something, but are there keyboard shortcuts available for STiki? I've found them very useful when using Huggle, etc.

740: 4155: 4136: 4122: 3704: 3272: 3248: 2558:

there is a relatively straightforward solution to address a bunch of corner cases regarding "space usage" and "special characters". Thanks,

877:

and Andrew's comment above. Such a thing will do more harm to the wikiproject than good. We already have Milestones for such felicitation --

679: 409: 276: 215: 182: 159: 4307: 3154:

I have changed my username, and I now login with the W.D. username. Everything has been transferred. Would it be possible to merge the two?

1125: 3726: 2956:. Upper-case is certainly allowed on the directory path and that example has one link with "NOAA" (capitalized) in the host name. Thanks, 1629: 1226: 389: 3969: 3789: 2360: 1803: 498:

I'd like to recommend that all STiki users use wikEdDiff. The easiest way is by ticking the box in "Gadgets" tab of "my preferences".

431:} catch(CommunicationsException e){ parent.reset_connection(false); submit_vandalism(); // If con failure - reconnect - reattempt 260:

the account creation software may well prevent anyone without a "bot" flag from creating an account with "bot" as part of the username.

3319:

I'll also note that time-of-day and day-of-week are not killer features, i.e., they are not among those with the greatest quantity of

1579: 4078:

Allow it to just get the data for a given period, rather than all missing data. That could take a long time and clog up the servers.

1856: 1797: 1623: 4421:

that the 'BACK' button was permanently disabled and had just been made 'alive'. Andrew has now made this point clear to me above.

3880:

far-far-far less often, and eventually, never. I do agree that seeing it every session after 10 passes was a bit excessive. Thanks,

1212:

Hmmm... I'm generally against adverts... especially ones that change... although your one does have the redeeming feature of humour.

3943: 3524: 2268: 1027: 4455:

Could I create a text file (through a script or something) to get the revision IDs of a user's edits, to then put in to the ort?

4047: 3925: 3372:

article, to indicate whether a day is a local weekend, might make DOW significant enough to actually (indirectly) be in the tree.

2734:

congruent short-term, but I can get it closer than it is now). I've located the MediaWiki code for parsing external links (e.g.,

4459: 2509:

Errr... Actually a pretty big improvement in latency on my end. I'll write an alert script so this never happens again. Thanks,

1094: 4232: 713: 814: 231: 3976:

is a minor one; if someone feels strongly, move it and maybe redirect the talk page back to it (and correct any pointers).

3930: 3054: 1495: 753:

Joey836 Seemed to go rather edit manic, should I use mass rollback because by chance, some of these edits were vandalism?

3259:

these unknown timezone ones, then perhaps that characteristic could be treated as a separate datum for the decision tree.

3163: 169:

entering bot edits into the CBNG queue. I don't see anything filtering out bot edits from the WikiTrust queue currently.)

1996: 1417: 1136: 350: 3646:

I agree that simple is good. You could base it on a simple edit count or possibly edit count + confirmed/autoconfirmed.

3544: 506: 3057:

want to hold up vandalism processing in a thread while links are parsed. I'll need to rethink this strategy. Thanks,

2954: 2577:

when "(?:archive)?url\s*=\s*" is preferable ("archiveurl" refers to a page replaced via web.archive.org or WebCite).

1206: 4332:

Yes, I can understand that you should not be allowed to return to the last edit after a Vandalism and an AGF revert

2252: 2166:

and make sure you dont end up templating yourself, I have seen that with Stiki some have already managed to do that

1990: 1987: 1984: 1993: 663: 516: 256: 4586: 4450: 4434: 4341: 4303: 4251: 3756: 2477: 2447: 2381: 2321:

P.S. Congratulations on second-place on the leaderboard! I actually look forward to the day you pass me! Thanks,

1000: 960: 580: 541: 97: 4578: 4573: 4561: 4556: 4548: 4281: 1079: 89: 84: 72: 67: 59: 134: 4359:"BOT" as you did in past. This discourages new users and scares them from editing and contributing. regards-- 4212:

I think the title here is pretty self explanatory. Also what do the other headings on the leaderboard mean?

2241: 1850: 1791: 1617: 1014:

the client code fetching the old page and a current version of the page instead of the actual next revision.

3649:

I think a bigger issue is what the message says. We don't want to imply that the STiki user should either:

4228: 4207: 4185: 4151: 4118: 4028: 3722: 3700: 3613: 3564: 3467: 3389: 3268: 3228: 3125: 3016: 2916: 2828: 2755: 2659: 2586: 2547: 2348: 2292: 1937: 1729: 1394: 1236: 1067: 1023: 614: 536:

I have had WikEd checked since April 12. That is the same isn't it? The result is well worth having. --

447: 385: 325: 272: 178: 123: 512:

wikEdDiff displays this diff in a much more helpful way so I was able to see that there was no vandalism.

4261: 3380:

I may try working some of the above up into a patch (the educational IPs one would be difficult for me).

2057:

Also, you may like to try the STiki queue. Click on "Rev Queue" at the top and select "STiki (metadata)"

1572:

I think it is already in the rotation. If it is displayed on the Knowledge Ads template then it links to

874: 2681: 4527: 4430: 4337: 4299: 4247: 3255: 1605: 651:'//de.wikipedia.org/search/?title=Benutzer:Schnark/js/diff.js&action=raw&ctype=text/javascript' 576: 537: 38: 3149: 2623: 2208: 287: 3116:

That may be because the server lag is high today - it was up to close to 10 minutes earlier, IIRC.

2677:

try modifying first. Once satisfied with that, we can trivially transfer its logic to the GUI side.

1844: 1785: 1611: 659: 3765:

The user's WP password (this would need to be optional, of course, for those on shared computers)

977:- Having a leaderboard is already a little bit competitive... but in a much more manageable way. 4495: 4470: 4319: 4269: 4166: 4059: 3985: 3907: 3885: 3873: 3844: 3814: 3785: 3773: 3736: 3637: 3583: 3532: 3424: 3328: 3298: 3192: 3175: 3077: 3062: 2961: 2869: 2789: 2704: 2689: 2609: 2563: 2514: 2498: 2402: 2326: 2310: 2264: 2134: 1953: 1906: 1880: 1830: 1814: 1778: 1760: 1699: 1641: 1589: 1526: 1463: 1430: 1289: 1265: 1244: 1215:

Can you reduce the frame rate? I don't get time to read one thing before it goes on to the next.

1176: 1148: 1044: 826: 774: 697: 481: 463: 295: 257:

http://en.wikipedia.org/w/api.php?action=query&list=allusers&augroup=bot&aulimit=500

1535:

looks cool, I like the inherent relationship between STiki, stick (both the wooden stick and

353:, ImageRemovalBot, SD5bot, and any others that people can suggest - can be hardwired in as OK. 3289: 1657: 932: 855: 841: 810: 788: 758: 263:

Regarding the case sensitivity, it converts the username to uppercase before the comparison.

3072:

gives us tonight (if nothing else, there will be fewer errors on the basis of this change).

363:

If rvprop=flags will give whether or not the "bot" flag was in use, then it can be used for

4536: 4216: 2229: 1192: 912: 800: 709: 47: 17: 3669:

Revert edit and discuss it on the article talk page (but no templating the user talk page)

2001:

My first question is: does such a thing happen often (STiki flagging reverts of vandalism

8: 3994:

So long as the page isn't in article space, the rules are pretty flexible. For example,

2743: 2727: 2633: 2470: 2440: 2374: 2152: 2034: 2014: 953: 3548:

as an example. It looks like the tokens/segments it uses are split by something like \b.

2604:(given that the API has ground-truth). Let me know and we can set something up. Thanks, 2050:

The edit summary is shown on STiki at the bottom of the window, where it says "comment".

1840: 1322:

as this makes perfect sense, It is not defamatory to any other tool, in fact, this line

4491: 4466: 4315: 4265: 4162: 4132: 4091: 4055: 4043: 4016: 3981: 3965: 3903: 3881: 3869: 3840: 3810: 3781: 3769: 3732: 3681: 3633: 3579: 3528: 3420: 3324: 3294: 3244: 3188: 3171: 3073: 3058: 2957: 2865: 2785: 2700: 2685: 2605: 2559: 2510: 2494: 2398: 2322: 2306: 2260: 2130: 2064: 1949: 1902: 1876: 1826: 1810: 1756: 1695: 1637: 1585: 1522: 1477: 1459: 1449: 1426: 1413: 1285: 1261: 1240: 1222: 1172: 1144: 1121: 1040: 990: 822: 770: 736: 693: 675: 559: 526: 477: 459: 405: 291: 245: 155: 3865:

The fact that the "you've used the pass button several times" warning has been given.

515:

Users may also be interested in a variant developed by Schnark, which is described at

145:

However, I think bots were stopped from entering the STiki queue in August 2011. See

3672:

Mark the edit as innocent for STiki purposes but discuss it on the article talk page.

2237: 721: 458:

one (I think there is a dialogue message popped if it successfully happens). Thanks,

428:

In gui_support/gui_fb_handler.java's submit_agf function, the following is in error:

4224: 4181: 4147: 4114: 3718: 3696: 3609: 3560: 3463: 3385: 3320: 3264: 3224: 3121: 3012: 2912: 2824: 2751: 2655: 2582: 2543: 2344: 2288: 1933: 1825:

Am I correct in my assumption that HTTPS is needed only for login actions? Thanks,

1725: 1063: 1019: 928: 851: 837: 806: 784: 754: 610: 443: 381: 321: 268: 174: 119: 1361:

I like the point about being beaten to the revert. How about this as a user box?

1157:

Thank you both for your helpful explanations. I'll look forward to the next rev.

3921: 3829: 3799: 2118: 1573: 1518: 1389: 1171:

This feature request was included in the 2012_05_22 release. Now closed. Thanks,

1162: 1111: 1090: 906: 502: 4535:

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

2739: 2735: 46:

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

4481: 4456: 3202: 3159: 2463: 2433: 2367: 2163: 2146: 2028: 2008: 1839:

If I'm correct, making only making the login actions use HTTPS would allow for

1576: 1509: 1275: 1203: 1143:

investigate shortly and hopefully have a solution at the next release. Thanks,

946: 4336:, and that the BACK button should at these times be disabled. Thank you. -- 3998:

contains backgound info, structured discussion and more free-form discussion;

197:

please look into this, even i am fed up of marking bots as innocent, regards--

4264:. In STiki we call the action an "AGF revert". What other terms confuse you? 4128: 4087: 4039: 4012: 3961: 3677: 3240: 2418: 2060: 1473: 1445: 1409: 1218: 1117: 986: 732: 671: 555: 522: 401: 241: 151: 314:

Knowledge:Administrators' noticeboard/IncidentArchive747#Niabot_block_review

147:

User talk:West.andrew.g/TalkArchive04#STiki queues edits from approved bots?

2643: 2256: 717: 3170:

long, especially given the influx of new users we've seen lately. Thanks,

1875:

Good point. Bug and feature table up top updated to reflect this. Thanks,

494:

Recommendation to STiki users: WikiEdDiff and/or Schnark's variant thereof

4220: 4177: 4143: 4110: 4034: 3714: 3692: 3605: 3556: 3459: 3381: 3260: 3220: 3117: 3008: 2908: 2820: 2747: 2651: 2578: 2539: 2340: 2284: 1929: 1721: 1059: 1015: 606: 439: 377: 317: 264: 170: 115: 2113:

with your actions and don't get in too big of a hurry classifying edits.

903:

to promote the use of Stiki. We should also have awards for the top 3.--

3917: 3825: 3795: 3368:

Combining the day-of-week data with the country and information in the

1968: 1158: 1086: 1006: 575:, I have been using that symbol since April 12 ... it's excellent. -- 4246:

being vandalism, but being unconstructive and should be "undone". --

2073:

AS yaris has already stated, the best and the most important thing is

370:

If it doesn't, then an API query (or a local cache) will be necessary.

4417:

My reason for starting this section was merely that up until May 25,

3502:

and the right-hand side of diff would be formatted as something like

3155: 601:

How does one substitute Schnark's variant for that used by wikEdDiff?

509:). This makes it hard to decide if there has been vandalism or not. 4294:... is this new, or has it not been functioning since I began using 2744:

http://svn.wikimedia.org/doc/GlobalFunctions_8php_source.html#l00771

2303:

this should lead to a queue ordering that looks like VANDALISM-: -->

4009:

I have added an explanation of "features" to the top of that page.

2047:

I have been presented with a revert of vandalism, but only rarely.

3369: 3214:

db_geolocation.java: get_gmt_offset returning 0.0 as error value?

2533:

Regarding the already-reported problem with "}}", perhaps adding

2174:

which as, it appears, will truely be an unfortunate situation. --

1923:

Other templates in gui_revert_and_warn.java's highest_warn_level

4465:

Why yes, you could! Is there a non-hypothetical question here?

2414: 1901:

Included in this evening's release. Matter now closed. Thanks,

1235:

I'll have more time to comment on this later, but @Yaris, see:

1199: 981:

we were to go any more competitive, then we'd definitely need

3868:

Hmmm. Maybe. Even experienced users need a jostle sometimes.

2305:

INNOCENT, which in my opinion is a desirable result. Thanks,

1381: 3601:

out user reputation so could send that info to the client.)

2740:

http://svn.wikimedia.org/doc/Parser_8php_source.html#l00090

2736:

http://svn.wikimedia.org/doc/Parser_8php_source.html#l01168

3498: 3362:

Category:Shared IP addresses from educational institutions

2726:

helpful. I've started to construct a set of test cases in

629:

To use Schnark's diff (in the normal wiki interface), put

3663:

Conclude edit is actually innocent and press that button.

476:

ACK, fixed in the 2012_05_22 release. Matter now closed.

4000:

Knowledge talk:Pending changes/Request for Comment 2012

3555:

Good thought on the subpage - will start work on that.

312:

Erm. It appears that my logic above was incorrect. See

4414:... and that is exactly what I had already understood. 3768:

Yes. Would probably be stored in plain-text, though.

3492: 2278:

Treatment of "good faith revert" in machine learning?

3596:

Warnings about templating regulars: Who's a regular?

2953:

Errr. I am not so sure about the lowercase bit. See

2819:

MediaWiki software lowercases hostname characters).

1720:

I've put it in; not sure if it's in the best place.

3365:

educational IP addresses - will take a look around.

109:

SD5bot edit (changing template) seen in STiki queue

4004:Knowledge:Pending changes/Request for Comment 2012 3996:Knowledge:Pending changes/Request for Comment 2012 3004: 2535:link_desc = link_desc.replaceAll("\\}\\}.*" , ""); 346:This situation can be solved in a couple of ways: 2998:Fascinating. It's converting it to lowercase for 424:Bug in gui_support/gui_fb_handler.java:submit_agf 2525:Bug report (addition?): Link parsing and display 1978:STiki pitting vandal fighters against each other 1284:to reverts?" is not inappropriate, IMO. Thanks, 1197:I have created an advertisment for STiki here: 4286:For the first time this afternoon, I have the ' 1755:section is about at its limit, though. Thanks, 438:have already taken care of reverting the edit. 2864:get you an error report this evening. Thanks, 2253:Knowledge:Signature#Customizing_your_signature 2862:need to fix this, as some articles have : --> 1274:I presume it cannot be defamatory to Huggle. 501:An excellent example of why it is useful is 2680:In terms of Java regex, you'll want to see 1009:) shows up as completely blank, and it is 3666:Revert edit and template user (as usual). 3655:Revert the edit without warning the user. 3944:Knowledge talk:STiki/Feature development 3525:Wikipedia_talk:STiki/Feature development 1358:I note the reduced frame rate. Thanks. 749:Should I use mass rollback on this user? 1971:(as is uw-articlesig, for that matter). 14: 4533:Do not edit the contents of this page. 3254:could at least be classified by which 1403:|| {{User:Yaris678/STiki UserBox 2}} 1320:"Tired of getting beaten to reverts? " 1314:I agree, lets simply replace the line 714:de:Benutzer:Schnark/js/diff.js/core.js 44:Do not edit the contents of this page. 4242:The editor's revision is regarded as 4002:contains discussion about what is on 4514: 3505:http://www.<font color="red": --> 2167: 1540: 1494:Replaced Rhetorical questions slide. 1376: 25: 3952:Knowledge:STiki/Feature development 3948:Knowledge:STiki/Feature development 1539:ing on the wall), and Beat/beaten 23: 4400: 4366: 2361:Constant lag? (Update: improved?!) 2181: 2084: 1667: 1554: 1333: 1316:"stop asking rhetorical questions" 1237:Template:Wikipedia_ads#Current_ads 884: 507:Longest common subsequence problem 204: 24: 4600: 1636:scroll the diff browser. Thanks, 1137:Zero White Space (ZWS) characters 983:some kind of peer checking system 4518: 4429:ans" ... with kind regards, -- 2168: 1541: 1380: 1198: 1039:1000 seconds recently). Thanks, 1005:Diff 492685257 (for the article 664:De:Benutzer:Schnark/js/diff/core 517:De:Benutzer:Schnark/js/diff/core 255:Regarding the user permissions, 29: 4406: 4372: 2187: 2090: 1673: 1560: 1339: 890: 210: 4397: 4363: 3839:general are not a great idea. 3239:time-independent classifier. 2471: 2441: 2375: 2178: 2081: 1664: 1551: 1508:Oops! I wasn't logged in then. 1330: 954: 881: 394:Niabot... good find by Allens. 349:The most important bots - the 201: 13: 1: 2464: 2434: 2368: 2222: 947: 4006:, including what to do next. 3931:Feature development sub page 2217: 850:Maybe a monthly STiki drive. 7: 2478: 2448: 2382: 1658:Knowledge:STiki#Using_STiki 1395:seldom beaten to the revert 961: 10: 4605: 3256:Regional Internet Registry 2426:14:16, 26 April 2012 (UTC) 2407:13:55, 26 April 2012 (UTC) 2391:11:13, 26 April 2012 (UTC) 2225:22:11, 19 May 2012 (UTC) 875:STiki is not a competition 680:07:53, 30 April 2012 (UTC) 619:01:57, 30 April 2012 (UTC) 585:06:33, 30 April 2012 (UTC) 564:22:50, 29 April 2012 (UTC) 546:22:38, 29 April 2012 (UTC) 531:22:22, 29 April 2012 (UTC) 452:19:06, 29 April 2012 (UTC) 277:00:02, 30 April 2012 (UTC) 250:21:19, 29 April 2012 (UTC) 216:14:29, 29 April 2012 (UTC) 183:13:00, 29 April 2012 (UTC) 160:12:18, 29 April 2012 (UTC) 128:06:23, 29 April 2012 (UTC) 3898:The last selected queue? 4500:01:05, 27 May 2012 (UTC) 4485:17:40, 26 May 2012 (UTC) 4475:12:34, 26 May 2012 (UTC) 4460:08:44, 26 May 2012 (UTC) 4439:09:12, 26 May 2012 (UTC) 4378:08:15, 26 May 2012 (UTC) 4346:07:14, 26 May 2012 (UTC) 4324:18:19, 25 May 2012 (UTC) 4308:17:24, 25 May 2012 (UTC) 4274:12:30, 25 May 2012 (UTC) 4256:10:42, 25 May 2012 (UTC) 4233:10:35, 25 May 2012 (UTC) 4190:17:04, 28 May 2012 (UTC) 4171:15:05, 28 May 2012 (UTC) 4156:14:08, 28 May 2012 (UTC) 4137:12:31, 28 May 2012 (UTC) 4123:11:58, 28 May 2012 (UTC) 4096:11:44, 28 May 2012 (UTC) 4064:12:28, 25 May 2012 (UTC) 4048:08:12, 25 May 2012 (UTC) 4021:11:34, 28 May 2012 (UTC) 3990:12:21, 25 May 2012 (UTC) 3970:08:12, 25 May 2012 (UTC) 3926:15:08, 23 May 2012 (UTC) 3890:05:32, 26 May 2012 (UTC) 3849:01:01, 27 May 2012 (UTC) 3834:17:16, 26 May 2012 (UTC) 3819:12:31, 26 May 2012 (UTC) 3804:08:03, 26 May 2012 (UTC) 3790:04:07, 26 May 2012 (UTC) 3741:00:57, 27 May 2012 (UTC) 3727:16:29, 26 May 2012 (UTC) 3705:12:43, 26 May 2012 (UTC) 3686:12:32, 23 May 2012 (UTC) 3642:19:29, 22 May 2012 (UTC) 3618:19:13, 22 May 2012 (UTC) 3588:00:20, 25 May 2012 (UTC) 3569:23:24, 24 May 2012 (UTC) 3537:21:24, 24 May 2012 (UTC) 3472:17:54, 24 May 2012 (UTC) 3429:19:31, 21 May 2012 (UTC) 3394:19:09, 21 May 2012 (UTC) 3333:15:58, 21 May 2012 (UTC) 3303:15:43, 21 May 2012 (UTC) 3273:14:41, 21 May 2012 (UTC) 3249:12:33, 21 May 2012 (UTC) 3233:10:06, 21 May 2012 (UTC) 3206:17:40, 26 May 2012 (UTC) 3197:16:29, 21 May 2012 (UTC) 3180:14:39, 15 May 2012 (UTC) 3164:07:12, 15 May 2012 (UTC) 3130:19:00, 22 May 2012 (UTC) 3082:18:56, 22 May 2012 (UTC) 3067:18:32, 22 May 2012 (UTC) 3021:19:00, 22 May 2012 (UTC) 2966:17:50, 22 May 2012 (UTC) 2921:19:00, 22 May 2012 (UTC) 2874:16:31, 22 May 2012 (UTC) 2833:15:50, 22 May 2012 (UTC) 2794:14:16, 22 May 2012 (UTC) 2760:10:31, 22 May 2012 (UTC) 2709:19:36, 21 May 2012 (UTC) 2694:19:21, 21 May 2012 (UTC) 2664:18:39, 21 May 2012 (UTC) 2614:16:49, 21 May 2012 (UTC) 2591:15:03, 18 May 2012 (UTC) 2519:17:54, 21 May 2012 (UTC) 2503:16:25, 21 May 2012 (UTC) 2353:19:11, 21 May 2012 (UTC) 2331:16:36, 21 May 2012 (UTC) 2315:15:53, 21 May 2012 (UTC) 2297:15:03, 21 May 2012 (UTC) 2269:23:35, 19 May 2012 (UTC) 2193:19:46, 18 May 2012 (UTC) 2158:19:06, 18 May 2012 (UTC) 2139:18:49, 18 May 2012 (UTC) 2096:18:41, 18 May 2012 (UTC) 2069:18:29, 18 May 2012 (UTC) 2040:17:02, 18 May 2012 (UTC) 2020:16:58, 18 May 2012 (UTC) 1958:15:33, 18 May 2012 (UTC) 1942:15:23, 18 May 2012 (UTC) 1911:00:53, 22 May 2012 (UTC) 1885:13:56, 19 May 2012 (UTC) 1863:11:46, 19 May 2012 (UTC) 1835:05:00, 19 May 2012 (UTC) 1819:14:32, 18 May 2012 (UTC) 1804:11:46, 18 May 2012 (UTC) 1765:15:15, 18 May 2012 (UTC) 1734:14:52, 18 May 2012 (UTC) 1704:14:19, 18 May 2012 (UTC) 1679:06:13, 18 May 2012 (UTC) 1646:02:15, 18 May 2012 (UTC) 1630:01:17, 18 May 2012 (UTC) 1594:14:11, 19 May 2012 (UTC) 1580:07:43, 19 May 2012 (UTC) 1566:19:41, 18 May 2012 (UTC) 1531:19:38, 18 May 2012 (UTC) 1513:19:30, 18 May 2012 (UTC) 1504:19:11, 18 May 2012 (UTC) 1482:16:11, 18 May 2012 (UTC) 1472:Cool. "Beaten" it is. 1468:14:39, 18 May 2012 (UTC) 1454:14:31, 18 May 2012 (UTC) 1435:14:24, 18 May 2012 (UTC) 1418:06:59, 18 May 2012 (UTC) 1345:06:20, 18 May 2012 (UTC) 1294:00:57, 18 May 2012 (UTC) 1279:20:20, 17 May 2012 (UTC) 1270:19:38, 17 May 2012 (UTC) 1249:19:34, 17 May 2012 (UTC) 1227:17:11, 17 May 2012 (UTC) 1207:15:54, 17 May 2012 (UTC) 1181:00:51, 22 May 2012 (UTC) 1167:17:16, 16 May 2012 (UTC) 1153:15:34, 16 May 2012 (UTC) 1126:12:30, 16 May 2012 (UTC) 1095:11:25, 16 May 2012 (UTC) 1072:15:18, 15 May 2012 (UTC) 1049:14:56, 15 May 2012 (UTC) 1028:13:08, 15 May 2012 (UTC) 995:15:30, 15 May 2012 (UTC) 970:02:46, 13 May 2012 (UTC) 937:21:20, 11 May 2012 (UTC) 927:- per my comment above. 920:15:56, 11 May 2012 (UTC) 630: 486:00:50, 22 May 2012 (UTC) 4451:Would this be possible? 3757:Could STiki remember... 3499:http://www.otherurl.com 3156:Willdude123|Ƹ21ɘbublliW 2568:16:50, 1 May 2012 (UTC) 2552:00:36, 1 May 2012 (UTC) 2487:07:17, 6 May 2012 (UTC) 2457:00:12, 1 May 2012 (UTC) 2283:to equal to vandalism. 1001:Blank non-rollback diff 896:16:16, 7 May 2012 (UTC) 860:16:00, 7 May 2012 (UTC) 852:Willdude123|Ƹ21ɘbublliW 846:14:41, 7 May 2012 (UTC) 831:14:04, 7 May 2012 (UTC) 815:12:47, 7 May 2012 (UTC) 807:Willdude123|Ƹ21ɘbublliW 793:19:19, 1 May 2012 (UTC) 785:Willdude123|Ƹ21ɘbublliW 779:19:12, 1 May 2012 (UTC) 763:18:03, 1 May 2012 (UTC) 755:Willdude123|Ƹ21ɘbublliW 741:12:06, 9 May 2012 (UTC) 726:07:20, 8 May 2012 (UTC) 702:16:40, 1 May 2012 (UTC) 468:16:32, 1 May 2012 (UTC) 410:11:37, 9 May 2012 (UTC) 390:01:47, 9 May 2012 (UTC) 330:05:47, 8 May 2012 (UTC) 300:16:26, 1 May 2012 (UTC) 139:That's from 2012-04-02. 3731:Valid point. Will do. 1080:Text selection/copying 4531:of past discussions. 4431:Gareth Griffith-Jones 4338:Gareth Griffith-Jones 4300:Gareth Griffith-Jones 4248:Gareth Griffith-Jones 4082:article gets deleted. 577:Gareth Griffith-Jones 538:Gareth Griffith-Jones 42:of past discussions. 4262:WP:Assume good faith 4208:What does AGF% mean? 4029:Satisficing approach 710:User:Cacycle/diff.js 18:Knowledge talk:STiki 4394:Thanks for that, ' 3506:other</font: --> 3493:http://www.url.com 2682:this documentation 1606:Keyboard Shortcuts 1324:"beaten to revert" 4592: 4591: 4543: 4542: 4537:current talk page 4282:The 'BACK' button 4236: 4219:comment added by 3150:STiki Leaderboard 2483: 2453: 2387: 2339:Blush... thanks! 2246: 2232:comment added by 1841:Session Hijacking 1407: 1406: 1401: 1400: 966: 918: 232:this CBNG example 103: 102: 54: 53: 48:current talk page 4596: 4570: 4545: 4544: 4522: 4521: 4515: 4408: 4402: 4399: 4374: 4368: 4365: 4235: 4213: 3547: 3501: 3495: 3321:information gain 2648: 2642: 2638: 2632: 2628: 2624:official website 2622: 2536: 2484: 2479: 2475: 2468: 2462:Hope that helps. 2454: 2449: 2445: 2438: 2423: 2388: 2383: 2379: 2372: 2245: 2226: 2223: 2219: 2189: 2183: 2180: 2173: 2172: 2171: 2156: 2149: 2092: 2086: 2083: 2075:Revert Carefully 2038: 2031: 2018: 2011: 1675: 1669: 1666: 1562: 1556: 1553: 1546: 1545: 1544: 1384: 1377: 1364: 1363: 1341: 1335: 1332: 1202: 1114:looks promising. 967: 962: 958: 951: 917: 915: 904: 892: 886: 883: 655: 652: 649: 646: 643: 640: 637: 634: 351:anti-vandal bots 212: 206: 203: 81: 56: 55: 33: 32: 26: 4604: 4603: 4599: 4598: 4597: 4595: 4594: 4593: 4566: 4519: 4453: 4284: 4214: 4210: 4031: 3933: 3759: 3652:Ignore the edit 3598: 3543: 3508: 3497: 3491: 3216: 3152: 3005:http://HOSTNAME 2646: 2640: 2636: 2630: 2626: 2620: 2534: 2527: 2419: 2363: 2280: 2227: 2211: 2209:Feature Request 2169: 2150: 2144: 2119:User:ClueBot_NG 2032: 2026: 2012: 2006: 1980: 1925: 1860: 1854: 1848: 1801: 1795: 1789: 1781: 1779:Feature Request 1627: 1621: 1615: 1608: 1542: 1402: 1393:, this user is 1195: 1082: 1003: 913: 905: 803: 751: 657: 656: 653: 650: 647: 644: 641: 638: 635: 632: 496: 432: 426: 288:username policy 111: 77: 30: 22: 21: 20: 12: 11: 5: 4602: 4590: 4589: 4584: 4581: 4576: 4571: 4564: 4559: 4554: 4551: 4541: 4540: 4523: 4512: 4510: 4509: 4508: 4507: 4506: 4505: 4502: 4482:User Talk:W.D. 4457:User Talk:W.D. 4452: 4449: 4448: 4447: 4446: 4445: 4444: 4443: 4442: 4441: 4422: 4419:I had believed 4415: 4412: 4385: 4384: 4383: 4382: 4381: 4380: 4351: 4350: 4349: 4348: 4327: 4326: 4283: 4280: 4279: 4278: 4277: 4276: 4258: 4209: 4206: 4205: 4204: 4203: 4202: 4201: 4200: 4199: 4198: 4197: 4196: 4195: 4194: 4193: 4192: 4101: 4100: 4099: 4098: 4085: 4084: 4083: 4079: 4073: 4067: 4066: 4030: 4027: 4026: 4025: 4024: 4023: 4010: 4007: 3977: 3932: 3929: 3914: 3913: 3912: 3911: 3895: 3894: 3893: 3892: 3877: 3862: 3861: 3860: 3859: 3858: 3857: 3856: 3855: 3854: 3853: 3852: 3851: 3777: 3758: 3755: 3754: 3753: 3752: 3751: 3750: 3749: 3748: 3747: 3746: 3745: 3744: 3743: 3675: 3674: 3673: 3670: 3667: 3664: 3658: 3657: 3656: 3653: 3647: 3628: 3627: 3597: 3594: 3593: 3592: 3591: 3590: 3572: 3571: 3553: 3549: 3504: 3496:is changed to 3487: 3486: 3485: 3484: 3483: 3482: 3481: 3480: 3479: 3478: 3477: 3476: 3475: 3474: 3442: 3441: 3440: 3439: 3438: 3437: 3436: 3435: 3434: 3433: 3432: 3431: 3405: 3404: 3403: 3402: 3401: 3400: 3399: 3398: 3397: 3396: 3378: 3377: 3376: 3373: 3366: 3355: 3342: 3341: 3340: 3339: 3338: 3337: 3336: 3335: 3310: 3309: 3308: 3307: 3306: 3305: 3278: 3277: 3276: 3275: 3215: 3212: 3211: 3210: 3209: 3208: 3203:User Talk:W.D. 3183: 3182: 3151: 3148: 3147: 3146: 3145: 3144: 3143: 3142: 3141: 3140: 3139: 3138: 3137: 3136: 3135: 3134: 3133: 3132: 3099: 3098: 3097: 3096: 3095: 3094: 3093: 3092: 3091: 3090: 3089: 3088: 3087: 3086: 3085: 3084: 3038: 3037: 3036: 3035: 3034: 3033: 3032: 3031: 3030: 3029: 3028: 3027: 3026: 3025: 3024: 3023: 2981: 2980: 2979: 2978: 2977: 2976: 2975: 2974: 2973: 2972: 2971: 2970: 2969: 2968: 2938: 2937: 2936: 2935: 2934: 2933: 2932: 2931: 2930: 2929: 2928: 2927: 2926: 2925: 2924: 2923: 2889: 2888: 2887: 2886: 2885: 2884: 2883: 2882: 2881: 2880: 2879: 2878: 2877: 2876: 2846: 2845: 2844: 2843: 2842: 2841: 2840: 2839: 2838: 2837: 2836: 2835: 2805: 2804: 2803: 2802: 2801: 2800: 2799: 2798: 2797: 2796: 2782: 2769: 2768: 2767: 2766: 2765: 2764: 2763: 2762: 2716: 2715: 2714: 2713: 2712: 2711: 2696: 2678: 2669: 2668: 2667: 2666: 2601: 2596: 2595: 2594: 2593: 2571: 2570: 2526: 2523: 2522: 2521: 2506: 2505: 2429: 2428: 2410: 2409: 2362: 2359: 2358: 2357: 2356: 2355: 2334: 2333: 2318: 2317: 2279: 2276: 2274: 2272: 2271: 2210: 2207: 2206: 2205: 2204: 2203: 2202: 2201: 2200: 2199: 2198: 2197: 2196: 2195: 2127: 2123: 2114: 2103: 2102: 2101: 2100: 2099: 2098: 2058: 2055: 2051: 2048: 2045: 1979: 1976: 1975: 1974: 1973: 1972: 1961: 1960: 1924: 1921: 1920: 1919: 1918: 1917: 1916: 1915: 1914: 1913: 1892: 1891: 1890: 1889: 1888: 1887: 1868: 1867: 1866: 1865: 1858: 1852: 1846: 1822: 1821: 1799: 1793: 1787: 1780: 1777: 1776: 1775: 1774: 1773: 1772: 1771: 1770: 1769: 1768: 1767: 1743: 1742: 1741: 1740: 1739: 1738: 1737: 1736: 1711: 1710: 1709: 1708: 1707: 1706: 1686: 1685: 1684: 1683: 1682: 1681: 1649: 1648: 1625: 1619: 1613: 1607: 1604: 1603: 1602: 1601: 1600: 1599: 1598: 1597: 1596: 1577:User Talk:W.D. 1570: 1569: 1568: 1510:User Talk:W.D. 1496:81.178.188.181 1492: 1491: 1490: 1489: 1488: 1487: 1486: 1485: 1484: 1443: 1440: 1405: 1404: 1399: 1398: 1385: 1375: 1372: 1371: 1368: 1356: 1355: 1354: 1353: 1352: 1351: 1350: 1349: 1348: 1347: 1303: 1302: 1301: 1300: 1299: 1298: 1297: 1296: 1276:User Talk:W.D. 1254: 1253: 1252: 1251: 1230: 1229: 1216: 1213: 1204:User Talk:W.D. 1194: 1191: 1190: 1189: 1188: 1187: 1186: 1185: 1184: 1183: 1140: 1129: 1128: 1115: 1112:The DJ Project 1107: 1104: 1101: 1081: 1078: 1077: 1076: 1075: 1074: 1052: 1051: 1035: 1002: 999: 998: 997: 972: 939: 922: 898: 867: 866: 865: 864: 863: 862: 802: 799: 798: 797: 796: 795: 750: 747: 746: 745: 744: 743: 689: 688: 687: 686: 685: 684: 683: 682: 669: 668: 667: 660:your common.js 631: 627: 604: 603: 602: 599: 588: 587: 569: 568: 567: 566: 549: 548: 495: 492: 491: 490: 489: 488: 471: 470: 430: 425: 422: 421: 420: 419: 418: 417: 416: 415: 414: 413: 412: 399: 395: 375: 374: 373: 372: 371: 368: 358: 357: 354: 337: 336: 335: 334: 333: 332: 305: 304: 303: 302: 280: 279: 261: 225: 224: 223: 222: 221: 220: 219: 218: 188: 187: 186: 185: 163: 162: 149: 143: 140: 137: 110: 107: 105: 101: 100: 95: 92: 87: 82: 75: 70: 65: 62: 52: 51: 34: 15: 9: 6: 4: 3: 2: 4601: 4588: 4585: 4582: 4580: 4577: 4575: 4572: 4569: 4565: 4563: 4560: 4558: 4555: 4552: 4550: 4547: 4546: 4538: 4534: 4530: 4529: 4524: 4517: 4516: 4513: 4503: 4501: 4497: 4493: 4492:West.andrew.g 4488: 4487: 4486: 4483: 4478: 4477: 4476: 4472: 4468: 4467:West.andrew.g 4464: 4463: 4462: 4461: 4458: 4440: 4436: 4432: 4428: 4423: 4420: 4416: 4413: 4411: 4409: 4404: 4403: 4393: 4392: 4391: 4390: 4389: 4388: 4387: 4386: 4379: 4376: 4375: 4370: 4369: 4357: 4356: 4355: 4354: 4353: 4352: 4347: 4343: 4339: 4335: 4334:automatically 4331: 4330: 4329: 4328: 4325: 4321: 4317: 4316:West.andrew.g 4312: 4311: 4310: 4309: 4305: 4301: 4297: 4293: 4289: 4275: 4271: 4267: 4266:West.andrew.g 4263: 4259: 4257: 4253: 4249: 4245: 4241: 4240: 4239: 4238: 4237: 4234: 4230: 4226: 4222: 4218: 4191: 4187: 4183: 4179: 4174: 4173: 4172: 4168: 4164: 4163:West.andrew.g 4159: 4158: 4157: 4153: 4149: 4145: 4140: 4139: 4138: 4134: 4130: 4126: 4125: 4124: 4120: 4116: 4112: 4107: 4106: 4105: 4104: 4103: 4102: 4097: 4093: 4089: 4086: 4080: 4077: 4076: 4074: 4071: 4070: 4069: 4068: 4065: 4061: 4057: 4056:West.andrew.g 4052: 4051: 4050: 4049: 4045: 4041: 4036: 4022: 4018: 4014: 4011: 4008: 4005: 4001: 3997: 3993: 3992: 3991: 3987: 3983: 3982:West.andrew.g 3978: 3974: 3973: 3972: 3971: 3967: 3963: 3959: 3955: 3953: 3949: 3945: 3940: 3936: 3928: 3927: 3923: 3919: 3909: 3905: 3904:West.andrew.g 3900: 3899: 3897: 3896: 3891: 3887: 3883: 3882:West.andrew.g 3878: 3875: 3871: 3870:West.andrew.g 3867: 3866: 3864: 3863: 3850: 3846: 3842: 3841:West.andrew.g 3837: 3836: 3835: 3831: 3827: 3822: 3821: 3820: 3816: 3812: 3811:West.andrew.g 3807: 3806: 3805: 3801: 3797: 3793: 3792: 3791: 3787: 3783: 3782:West.andrew.g 3778: 3775: 3771: 3770:West.andrew.g 3767: 3766: 3764: 3763: 3762: 3742: 3738: 3734: 3733:West.andrew.g 3730: 3729: 3728: 3724: 3720: 3716: 3712: 3711: 3708: 3707: 3706: 3702: 3698: 3694: 3689: 3688: 3687: 3683: 3679: 3676: 3671: 3668: 3665: 3662: 3661: 3659: 3654: 3651: 3650: 3648: 3645: 3644: 3643: 3639: 3635: 3634:West.andrew.g 3630: 3629: 3622: 3621: 3620: 3619: 3615: 3611: 3607: 3602: 3589: 3585: 3581: 3580:West.andrew.g 3576: 3575: 3574: 3573: 3570: 3566: 3562: 3558: 3554: 3550: 3546: 3541: 3540: 3539: 3538: 3534: 3530: 3529:West.andrew.g 3526: 3520: 3516: 3512: 3503: 3500: 3494: 3473: 3469: 3465: 3461: 3456: 3455: 3454: 3453: 3452: 3451: 3450: 3449: 3448: 3447: 3446: 3445: 3444: 3443: 3430: 3426: 3422: 3421:West.andrew.g 3417: 3416: 3415: 3414: 3413: 3412: 3411: 3410: 3409: 3408: 3407: 3406: 3395: 3391: 3387: 3383: 3379: 3374: 3371: 3367: 3363: 3360: 3359: 3356: 3352: 3351: 3350: 3349: 3348: 3347: 3346: 3345: 3344: 3343: 3334: 3330: 3326: 3325:West.andrew.g 3322: 3318: 3317: 3316: 3315: 3314: 3313: 3312: 3311: 3304: 3300: 3296: 3295:West.andrew.g 3291: 3284: 3283: 3282: 3281: 3280: 3279: 3274: 3270: 3266: 3262: 3257: 3252: 3251: 3250: 3246: 3242: 3237: 3236: 3235: 3234: 3230: 3226: 3222: 3207: 3204: 3200: 3199: 3198: 3194: 3190: 3189:West.andrew.g 3185: 3184: 3181: 3177: 3173: 3172:West.andrew.g 3168: 3167: 3166: 3165: 3161: 3157: 3131: 3127: 3123: 3119: 3115: 3114: 3113: 3112: 3111: 3110: 3109: 3108: 3107: 3106: 3105: 3104: 3103: 3102: 3101: 3100: 3083: 3079: 3075: 3074:West.andrew.g 3070: 3069: 3068: 3064: 3060: 3059:West.andrew.g 3055: 3052: 3051: 3050: 3049: 3048: 3047: 3046: 3045: 3044: 3043: 3042: 3041: 3040: 3039: 3022: 3018: 3014: 3010: 3006: 3001: 2997: 2996: 2995: 2994: 2993: 2992: 2991: 2990: 2989: 2988: 2987: 2986: 2985: 2984: 2983: 2982: 2967: 2963: 2959: 2958:West.andrew.g 2955: 2952: 2951: 2950: 2949: 2948: 2947: 2946: 2945: 2944: 2943: 2942: 2941: 2940: 2939: 2922: 2918: 2914: 2910: 2905: 2904: 2903: 2902: 2901: 2900: 2899: 2898: 2897: 2896: 2895: 2894: 2893: 2892: 2891: 2890: 2875: 2871: 2867: 2866:West.andrew.g 2860: 2859: 2858: 2857: 2856: 2855: 2854: 2853: 2852: 2851: 2850: 2849: 2848: 2847: 2834: 2830: 2826: 2822: 2817: 2816: 2815: 2814: 2813: 2812: 2811: 2810: 2809: 2808: 2807: 2806: 2795: 2791: 2787: 2786:West.andrew.g 2783: 2779: 2778: 2777: 2776: 2775: 2774: 2773: 2772: 2771: 2770: 2761: 2757: 2753: 2749: 2745: 2741: 2737: 2733: 2729: 2724: 2723: 2722: 2721: 2720: 2719: 2718: 2717: 2710: 2706: 2702: 2701:West.andrew.g 2697: 2695: 2691: 2687: 2686:West.andrew.g 2683: 2679: 2675: 2674: 2673: 2672: 2671: 2670: 2665: 2661: 2657: 2653: 2645: 2635: 2625: 2617: 2616: 2615: 2611: 2607: 2606:West.andrew.g 2602: 2598: 2597: 2592: 2588: 2584: 2580: 2575: 2574: 2573: 2572: 2569: 2565: 2561: 2560:West.andrew.g 2556: 2555: 2554: 2553: 2549: 2545: 2541: 2531: 2520: 2516: 2512: 2511:West.andrew.g 2508: 2507: 2504: 2500: 2496: 2495:West.andrew.g 2491: 2490: 2489: 2488: 2485: 2482: 2476: 2474: 2469: 2467: 2459: 2458: 2455: 2452: 2446: 2444: 2439: 2437: 2427: 2424: 2422: 2416: 2412: 2411: 2408: 2404: 2400: 2399:West.andrew.g 2395: 2394: 2393: 2392: 2389: 2386: 2380: 2378: 2373: 2371: 2354: 2350: 2346: 2342: 2338: 2337: 2336: 2335: 2332: 2328: 2324: 2323:West.andrew.g 2320: 2319: 2316: 2312: 2308: 2307:West.andrew.g 2301: 2300: 2299: 2298: 2294: 2290: 2286: 2275: 2270: 2266: 2262: 2261:West.andrew.g 2258: 2254: 2249: 2248: 2247: 2243: 2239: 2235: 2231: 2224: 2221: 2194: 2191: 2190: 2185: 2184: 2165: 2161: 2160: 2159: 2154: 2148: 2142: 2141: 2140: 2136: 2132: 2131:West.andrew.g 2128: 2124: 2120: 2115: 2111: 2110: 2109: 2108: 2107: 2106: 2105: 2104: 2097: 2094: 2093: 2088: 2087: 2076: 2072: 2071: 2070: 2066: 2062: 2059: 2056: 2052: 2049: 2046: 2044:Hi Adjwilley, 2043: 2042: 2041: 2036: 2030: 2024: 2023: 2022: 2021: 2016: 2010: 2004: 1999: 1997: 1994: 1991: 1988: 1985: 1970: 1965: 1964: 1963: 1962: 1959: 1955: 1951: 1950:West.andrew.g 1946: 1945: 1944: 1943: 1939: 1935: 1931: 1912: 1908: 1904: 1903:West.andrew.g 1900: 1899: 1898: 1897: 1896: 1895: 1894: 1893: 1886: 1882: 1878: 1877:West.andrew.g 1874: 1873: 1872: 1871: 1870: 1869: 1864: 1861: 1855: 1849: 1842: 1838: 1837: 1836: 1832: 1828: 1827:West.andrew.g 1824: 1823: 1820: 1816: 1812: 1811:West.andrew.g 1808: 1807: 1806: 1805: 1802: 1796: 1790: 1766: 1762: 1758: 1757:West.andrew.g 1753: 1752: 1751: 1750: 1749: 1748: 1747: 1746: 1745: 1744: 1735: 1731: 1727: 1723: 1719: 1718: 1717: 1716: 1715: 1714: 1713: 1712: 1705: 1701: 1697: 1696:West.andrew.g 1692: 1691: 1690: 1689: 1688: 1687: 1680: 1677: 1676: 1671: 1670: 1659: 1655: 1654: 1653: 1652: 1651: 1650: 1647: 1643: 1639: 1638:West.andrew.g 1634: 1633: 1632: 1631: 1628: 1622: 1616: 1595: 1591: 1587: 1586:West.andrew.g 1583: 1582: 1581: 1578: 1575: 1571: 1567: 1564: 1563: 1558: 1557: 1538: 1534: 1533: 1532: 1528: 1524: 1523:West.andrew.g 1520: 1516: 1515: 1514: 1511: 1507: 1506: 1505: 1501: 1497: 1493: 1483: 1479: 1475: 1471: 1470: 1469: 1465: 1461: 1460:West.andrew.g 1457: 1456: 1455: 1451: 1447: 1444: 1441: 1438: 1437: 1436: 1432: 1428: 1427:West.andrew.g 1424: 1423: 1422: 1421: 1420: 1419: 1415: 1411: 1396: 1392: 1391: 1386: 1383: 1379: 1378: 1374: 1373: 1369: 1366: 1365: 1362: 1359: 1346: 1343: 1342: 1337: 1336: 1325: 1321: 1317: 1313: 1312: 1311: 1310: 1309: 1308: 1307: 1306: 1305: 1304: 1295: 1291: 1287: 1286:West.andrew.g 1282: 1281: 1280: 1277: 1273: 1272: 1271: 1267: 1263: 1262:West.andrew.g 1258: 1257: 1256: 1255: 1250: 1246: 1242: 1241:West.andrew.g 1238: 1234: 1233: 1232: 1231: 1228: 1224: 1220: 1217: 1214: 1211: 1210: 1209: 1208: 1205: 1201: 1182: 1178: 1174: 1173:West.andrew.g 1170: 1169: 1168: 1164: 1160: 1156: 1155: 1154: 1150: 1146: 1145:West.andrew.g 1141: 1138: 1133: 1132: 1131: 1130: 1127: 1123: 1119: 1116: 1113: 1108: 1105: 1102: 1099: 1098: 1097: 1096: 1092: 1088: 1073: 1069: 1065: 1061: 1056: 1055: 1054: 1053: 1050: 1046: 1042: 1041:West.andrew.g 1036: 1032: 1031: 1030: 1029: 1025: 1021: 1017: 1012: 1008: 996: 992: 988: 984: 980: 976: 973: 971: 968: 965: 959: 957: 952: 950: 943: 940: 938: 934: 930: 926: 923: 921: 916: 910: 909: 902: 899: 897: 894: 893: 888: 887: 876: 872: 871:strong oppose 869: 868: 861: 857: 853: 849: 848: 847: 843: 839: 834: 833: 832: 828: 824: 823:West.andrew.g 819: 818: 817: 816: 812: 808: 794: 790: 786: 782: 781: 780: 776: 772: 771:West.andrew.g 767: 766: 765: 764: 760: 756: 742: 738: 734: 729: 728: 727: 723: 719: 715: 711: 706: 705: 704: 703: 699: 695: 694:West.andrew.g 681: 677: 673: 670: 665: 661: 628: 625: 624: 623:Interesting: 622: 621: 620: 616: 612: 608: 605: 600: 597: 596: 594: 593: 592: 591: 590: 589: 586: 582: 578: 574: 571: 570: 565: 561: 557: 553: 552: 551: 550: 547: 543: 539: 535: 534: 533: 532: 528: 524: 520: 518: 513: 510: 508: 504: 499: 487: 483: 479: 478:West.andrew.g 475: 474: 473: 472: 469: 465: 461: 460:West.andrew.g 456: 455: 454: 453: 449: 445: 441: 437: 429: 411: 407: 403: 400: 396: 393: 392: 391: 387: 383: 379: 376: 369: 366: 362: 361: 360: 359: 355: 352: 348: 347: 345: 344: 343: 342: 341: 340: 339: 338: 331: 327: 323: 319: 315: 311: 310: 309: 308: 307: 306: 301: 297: 293: 292:West.andrew.g 289: 284: 283: 282: 281: 278: 274: 270: 266: 262: 258: 254: 253: 252: 251: 247: 243: 239: 235: 233: 228: 217: 214: 213: 208: 207: 196: 195: 194: 193: 192: 191: 190: 189: 184: 180: 176: 172: 167: 166: 165: 164: 161: 157: 153: 150: 148: 144: 141: 138: 136: 132: 131: 130: 129: 125: 121: 117: 106: 99: 96: 93: 91: 88: 86: 83: 80: 76: 74: 71: 69: 66: 63: 61: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 4567: 4532: 4526: 4511: 4454: 4426: 4418: 4410: 4395: 4361: 4360: 4333: 4295: 4291: 4287: 4285: 4243: 4215:— Preceding 4211: 4032: 3960: 3956: 3942:However, is 3941: 3937: 3934: 3915: 3760: 3603: 3599: 3521: 3517: 3513: 3509: 3488: 3217: 3153: 2999: 2731: 2532: 2528: 2480: 2472: 2465: 2460: 2450: 2442: 2435: 2430: 2420: 2384: 2376: 2369: 2364: 2281: 2273: 2257:User:SineBot 2228:— Preceding 2216: 2215: 2212: 2176: 2175: 2079: 2078: 2074: 2002: 2000: 1981: 1926: 1782: 1662: 1661: 1609: 1549: 1548: 1536: 1408: 1388: 1360: 1357: 1328: 1327: 1323: 1319: 1315: 1196: 1193:Advertisment 1083: 1010: 1004: 978: 974: 963: 955: 948: 941: 924: 907: 900: 879: 878: 870: 804: 801:STiki-athon! 783:Good point! 752: 690: 595:Two things: 572: 521: 514: 511: 500: 497: 435: 433: 427: 364: 240: 236: 229: 226: 199: 198: 135:This edit... 112: 104: 78: 43: 37: 4525:This is an 4035:satisficing 1387:Because of 929:Orphan Wiki 838:Orphan Wiki 316:. Sorry... 36:This is an 4587:Archive 10 3935:Hey guys, 3290:"RESERVED" 3000:displaying 2728:my sandbox 2634:plain link 1660:section.-- 1007:Jim Saleam 908:Deathlaser 503:this edit, 98:Archive 10 4579:Archive 7 4574:Archive 6 4568:Archive 5 4562:Archive 4 4557:Archive 3 4549:Archive 1 3552:together. 3545:this diff 2304:AGF-: --> 2164:Adjwilley 2147:Adjwilley 2029:Adjwilley 2009:Adjwilley 1100:Hi Jakew, 90:Archive 7 85:Archive 6 79:Archive 5 73:Archive 4 68:Archive 3 60:Archive 1 4229:contribs 4217:unsigned 4186:contribs 4152:contribs 4129:Yaris678 4119:contribs 4088:Yaris678 4040:Yaris678 4013:Yaris678 3962:Yaris678 3916:Thanks! 3723:contribs 3701:contribs 3678:Yaris678 3614:contribs 3565:contribs 3468:contribs 3390:contribs 3269:contribs 3241:Yaris678 3229:contribs 3126:contribs 3017:contribs 2917:contribs 2829:contribs 2756:contribs 2732:entirely 2660:contribs 2587:contribs 2548:contribs 2466:P0150neD 2436:P0150neD 2421:Excirial 2370:P0150neD 2349:contribs 2293:contribs 2242:contribs 2230:unsigned 2129:Thanks, 2061:Yaris678 1938:contribs 1730:contribs 1519:WP:STiki 1474:Yaris678 1446:Yaris678 1410:Yaris678 1367:User Box 1219:Yaris678 1118:Yaris678 1068:contribs 1024:contribs 987:Yaris678 949:P0150neD 873:because 733:Yaris678 672:Yaris678 615:contribs 556:Yaris678 523:Yaris678 448:contribs 402:Yaris678 386:contribs 326:contribs 273:contribs 242:Yaris678 179:contribs 152:Yaris678 133:Hmmm... 124:contribs 4528:archive 4290:button 3507:url.com 3370:Weekend 2234:Rocks25 1439:Thanks. 1106:Andrew, 975:Comment 901:Support 718:Schnark 39:archive 4298:? -- 4292:"live" 4260:AGF = 4221:Zibart 4178:Allens 4144:Allens 4111:Allens 3715:Allens 3693:Allens 3606:Allens 3557:Allens 3460:Allens 3382:Allens 3261:Allens 3221:Allens 3118:Allens 3009:Allens 3003:href=" 2909:Allens 2821:Allens 2748:Allens 2742:, and 2652:Allens 2639:, and 2579:Allens 2540:Allens 2415:Avast! 2341:Allens 2285:Allens 2162:sure 1930:Allens 1722:Allens 1060:Allens 1016:Allens 942:Oppose 925:Oppose 639:loader 607:Allens 440:Allens 436:should 398:about. 378:Allens 318:Allens 265:Allens 171:Allens 116:Allens 4427:STiki 4296:STiki 4288:BACK' 3918:Jakew 3826:Jakew 3796:Jakew 3626:user" 3624:: --> 2481:asian 2451:asian 2385:asian 2126:same. 1969:28bot 1574:STiki 1537:stick 1390:STiki 1370:Code 1318:with 1159:Jakew 1087:Jakew 964:asian 914:Chat 658:into 16:< 4496:talk 4471:talk 4435:talk 4407:XЯaɣ 4373:XЯaɣ 4342:talk 4320:talk 4304:talk 4270:talk 4252:talk 4225:talk 4182:talk 4167:talk 4148:talk 4133:talk 4115:talk 4092:talk 4060:talk 4044:talk 4017:talk 3986:talk 3966:talk 3922:talk 3908:talk 3886:talk 3874:talk 3845:talk 3830:talk 3815:talk 3800:talk 3786:talk 3774:talk 3737:talk 3719:talk 3697:talk 3682:talk 3638:talk 3610:talk 3584:talk 3561:talk 3533:talk 3464:talk 3425:talk 3386:talk 3329:talk 3299:talk 3265:talk 3245:talk 3225:talk 3193:talk 3176:talk 3160:talk 3122:talk 3078:talk 3063:talk 3013:talk 2962:talk 2913:talk 2870:talk 2825:talk 2790:talk 2752:talk 2705:talk 2690:talk 2656:talk 2610:talk 2583:talk 2564:talk 2544:talk 2515:talk 2499:talk 2473:r1Ce 2443:r1Ce 2403:talk 2377:r1Ce 2345:talk 2327:talk 2311:talk 2289:talk 2265:talk 2255:and 2238:talk 2188:XЯaɣ 2153:talk 2135:talk 2091:XЯaɣ 2065:talk 2035:talk 2015:talk 1954:talk 1934:talk 1907:talk 1881:talk 1831:talk 1815:talk 1761:talk 1726:talk 1700:talk 1674:XЯaɣ 1642:talk 1590:talk 1561:XЯaɣ 1527:talk 1500:talk 1478:talk 1464:talk 1450:talk 1431:talk 1414:talk 1340:XЯaɣ 1290:talk 1266:talk 1245:talk 1223:talk 1177:talk 1163:talk 1149:talk 1122:talk 1091:talk 1064:talk 1045:talk 1020:talk 991:talk 956:r1Ce 933:talk 891:XЯaɣ 856:talk 842:talk 827:talk 811:talk 789:talk 775:talk 759:talk 737:talk 722:talk 716:. -- 698:talk 676:talk 645:load 611:talk 581:talk 560:talk 542:talk 527:talk 482:talk 464:talk 444:talk 406:talk 382:talk 365:most 322:talk 296:talk 269:talk 246:talk 211:XЯaɣ 175:talk 156:talk 120:talk 4401:ℬig 4367:ℬig 4244:not 3286:--> 2644:URL 2182:ℬig 2085:ℬig 1998:.) 1859:(c) 1853:(t) 1847:(u) 1800:(c) 1794:(t) 1788:(u) 1668:ℬig 1626:(c) 1620:(t) 1614:(u) 1555:ℬig 1334:ℬig 1038:--> 1011:not 885:ℬig 712:or 573:Yes 205:ℬig 4583:→ 4553:← 4498:) 4473:) 4437:) 4344:) 4322:) 4306:) 4272:) 4254:) 4231:) 4227:• 4188:) 4184:| 4169:) 4154:) 4150:| 4135:) 4121:) 4117:| 4094:) 4062:) 4046:) 4019:) 3988:) 3968:) 3954:. 3924:) 3888:) 3847:) 3832:) 3817:) 3802:) 3788:) 3739:) 3725:) 3721:| 3703:) 3699:| 3684:) 3640:) 3616:) 3612:| 3586:) 3567:) 3563:| 3535:) 3470:) 3466:| 3427:) 3392:) 3388:| 3331:) 3301:) 3271:) 3267:| 3247:) 3231:) 3227:| 3195:) 3178:) 3162:) 3128:) 3124:| 3080:) 3065:) 3019:) 3015:| 2964:) 2919:) 2915:| 2872:) 2831:) 2827:| 2792:) 2758:) 2754:| 2738:, 2707:) 2692:) 2662:) 2658:| 2647:}} 2641:{{ 2637:}} 2631:{{ 2629:, 2627:}} 2621:{{ 2612:) 2589:) 2585:| 2566:) 2550:) 2546:| 2517:) 2501:) 2405:) 2351:) 2347:| 2329:) 2313:) 2295:) 2291:| 2267:) 2244:) 2240:• 2220:cs 2137:) 2067:) 2003:as 1995:, 1992:, 1989:, 1986:, 1956:) 1940:) 1936:| 1909:) 1883:) 1833:) 1817:) 1763:) 1732:) 1728:| 1702:) 1644:) 1592:) 1547:-- 1529:) 1502:) 1480:) 1466:) 1452:) 1433:) 1416:) 1292:) 1268:) 1247:) 1225:) 1179:) 1165:) 1151:) 1124:) 1093:) 1070:) 1066:| 1047:) 1026:) 1022:| 993:) 979:If 935:) 911:: 858:) 844:) 829:) 813:) 791:) 777:) 761:) 739:) 724:) 700:) 678:) 654:); 633:mw 617:) 613:| 583:) 562:) 544:) 529:) 519:. 484:) 466:) 450:) 446:| 408:) 388:) 384:| 328:) 324:| 298:) 275:) 271:| 248:) 234:. 181:) 177:| 158:) 126:) 122:| 94:→ 64:← 4539:. 4494:( 4469:( 4433:( 4425:" 4398:Ð 4364:Ð 4340:( 4318:( 4302:( 4268:( 4250:( 4223:( 4180:( 4165:( 4146:( 4131:( 4113:( 4090:( 4058:( 4042:( 4015:( 3984:( 3964:( 3920:( 3910:) 3906:( 3884:( 3876:) 3872:( 3843:( 3828:( 3813:( 3798:( 3784:( 3776:) 3772:( 3735:( 3717:( 3695:( 3680:( 3636:( 3608:( 3582:( 3559:( 3531:( 3462:( 3423:( 3384:( 3327:( 3297:( 3263:( 3243:( 3223:( 3191:( 3174:( 3158:( 3120:( 3076:( 3061:( 3011:( 2960:( 2911:( 2868:( 2823:( 2788:( 2750:( 2703:( 2688:( 2654:( 2608:( 2581:( 2562:( 2542:( 2513:( 2497:( 2401:( 2343:( 2325:( 2309:( 2287:( 2263:( 2236:( 2218:R 2179:Ð 2155:) 2151:( 2145:~ 2133:( 2082:Ð 2063:( 2037:) 2033:( 2027:~ 2017:) 2013:( 2007:~ 1952:( 1932:( 1905:( 1879:( 1857:C 1851:w 1845:C 1829:( 1813:( 1798:C 1792:w 1786:C 1759:( 1724:( 1698:( 1665:Ð 1640:( 1624:C 1618:w 1612:C 1588:( 1552:Ð 1525:( 1498:( 1476:( 1462:( 1448:( 1429:( 1412:( 1397:. 1331:Ð 1288:( 1264:( 1243:( 1221:( 1175:( 1161:( 1147:( 1120:( 1110:[ 1089:( 1062:( 1043:( 1018:( 989:( 931:( 882:Ð 854:( 840:( 825:( 809:( 787:( 773:( 757:( 735:( 720:( 696:( 674:( 666:. 648:( 642:. 636:. 609:( 579:( 558:( 540:( 525:( 480:( 462:( 442:( 404:( 380:( 320:( 294:( 267:( 244:( 202:Ð 173:( 154:( 118:( 50:.

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

Knowledge

talk:STiki/Archive 5 - Knowledge

Index