Knowledge

User talk:West.andrew.g/Archive 4

Source šŸ“

1666:
male-pharmaceutical/pirated-software game that is usually played with online spam (though we could imagine a publisher conducting such behavior en masse). What I am saying is that in most cases, the publications are always legitimate, so it would be a matter of determining if they are appropriate in that context. (2) Most of these works probably aren't available online, making it difficult to do content/context analysis, (3) I am not sure how consistent the citation format is across Knowledge (I am sure there is one, I don't know to what extent it is followed). This could make it difficult to aggregate all citations to a particular source. (4) While this certainly happens, I would be curious to its prevalence and real impact on the project.
565:"Accuracy of classifications" could have several meanings. I am not especially bothered by false positives in the queues. If I understand correctly, Cluebot gets a lot of low-hanging fruit, the obvious vandalism. I am more concerned with accuracy. I recently stumbled across an article where someone changed "Fourteenth Amendment" to "Fourth Amendment," a major change to the meaning of the article, but hard for machines to identify as vandalism. Even harder to detect are the tiny changes, e.g., to a birth date, which, while not necessarily fatal, reflect badly on the integrity of Knowledge. 930:
because it is the most frequent *actual* reason. That being said, I don't know all the possible "rollback did not succeed" messages -- and don't know that they are enumerated anywhere by the Mediawiki folks. Edit conflicts and MediaWiki server failures are among the other possible reasons, I believe. In the immediate, I can work on some more accurate messages for those few failure cases/messages for which I am aware -- and maybe some logging for ones that have not been seen before (done with talk page responses for now; off to look at some code). Thanks,
1393:, electing not to leave a warning message. (I was being generous; it could well have been intentional.) Then, in STiki, I pressed the Vandalism button, assuming that STiki would do nothing but add the offending editor to its list of people to watch more closely.) STiki issued a "RB'd 1 edit" message but (of course) did not actually revert anything, because I had made a subsequent change. STiki also sent the editor a warning message. No harm done - it was a level 1 - but I assume that STiki would want to send a warning only if it does the revert. 1641:(great!, btw), and particularly that part on link spamming and the difficulties to detect it gave me an idea. While I was watching, I realized it is not only "lucrative" to have a link to your spam website on the bottom of a popular article, but also a reference to a book of yours. Since Knowledge is an encyclopedia, a lot of people use it as a starting point for research on a particular topic. So let's say you just wrote a book on the American Civil War. Wouldn't it be a nice "promotion" to have it refered to in every 2030:
was operating STiki at a very high rate of speed -- not a good quality in a Huggle user, especially since the revert environment has a bit of "competition." Alternatively, maybe the additional warning/tagging functionality of Huggle will serve him well. Regardless, the talk-page message is inappropriate. If you feel so inclined, talk to him about it, and if that fails, perhaps another trip to an administrative noticeboard? Unless he resumes STiki use, however, this issue is now outside my scope. Thanks,
2678: 31: 575:
you are currently doing this, but it seems to me that an editor's history in STiki evaluations should be weighted more heavily than the general survival history of that editor's changes. That is, the fact that an edit survives the scrutiny of an STicki reviewer (who is actively looking for vandalism and other inaccuracies), is a stronger endorsement of the editor's reliability than is the fact the editor has entered a lot of text that has not yet been looked at or changed.
1547:
more debugging code and push it to you in a new STiki build in the next couple of days, and (2) write some WM/WP developers to see if they can help me understand what makes a token go bad. At this point, I don't think your editing speed is of primary concern. Also, I'm hesitant to simply "fetch a new token; try again" because I want to believe there is a reason the token went bad, and a fresh token might not reflect the diff visualized in the STiki browser. Thanks,
267:
contributors in the movement like you. I'll be traveling to Wikimania next month to collect stories for our 2011 Fundraiser. While there I'd love the chance to meet with you and hear your thoughts about Knowledge. Weā€™ll have a schedule of available times for you to sign up if youā€™re interested, but right now, weā€™d like to make the initial contact to gauge your interest. Please let me know by emailing me at vgrigas@wikimedia.org or responding on my talk page.
2093:
my opinion it would be best to start with the article in question. The exact time parameter seems almost redundant as the entries keep coming so often. At least, maybe it could be hidden somehow or be output last in a small font? Perhaps also add headlines so people could just scan the table of contents for their favorite articles? Of course, that could be another tool/interface as well since Dead links seem to have quite a pedigree!
2612: 616:
them. Many of the revisions were extremely similar (i.e., inserted identical content), but indeed took place on different (but similar) articles. The insertion of Russian Characters and a few redirects were particularly common in this batch. I suspect this might be why you thought you saw the same edit more than once (I can email you the classification trace, if you like).
510:
revisions that were presented to me were the same revisions that I had seen the previous time that I was using the WikiTrust queue (and had already marked as innocent). If this isn't the right place to report possible bugs, I apologize. I have also run into a scrolling problem (under Windows Vista). That said, STiki is a very powerful tool. I am already a fan. Thanks.
1412:) and went to work on STiki. When I encountered an edit that was vandalism, I went off-STiki to do the "undo" and then came back to press "vandalism" in STiki. Each time it was correctly reported that I was "beaten to the revert" and no warning was issued. If you try this simple experiment, what happens? If that succeeds, what was so unusual about 1510:
manual link inspection. That being said, if some type of consensus could be secured that this is inappropriate, I would be happy to take it down. If anything, the scope at which this operates speaks to the massive degree of link rot on en.wiki, and the fact that people should be patrolling this page to eliminate those issues. Thanks,
129:
rather than "vandalism"). But the edit summary text for the user warning does not appear to be configurable in this way (or any other way, short of modifying the Java source) ā€” so I've personally decided to disable STiki's user warning entirely (via the checkbox) and send any user warnings via the far more flexible
2112:, which does provide a description of what is going on. Unfortunately, most people seem to arrive at the dead-links pages in archives, which does not carry the header message. Given the large number of archives, I'd probably need to write a bot to pre-pend that message to all the existing archive pages 2204:
Hmmm... The java.awt.Desktop package is responsible for interfacing between Java and your OS applications. For example, if one clicks on a hyperlink in Java, it will open in the default browser of the user via this class. A little forum digging revealed you most likely need to update your Java as the
1671:
I must admit, this is not at the forefront of my research at this time, but it is an interesting problem to think about. I think great progress could be made with only a few simple features, i.e., "how often does this user cite", "what percentage of those are to source , publisher , etc." Much of the
1546:
Hi Peter. I continue to be confused by this, because I have never encountered a 'badtoken' message in my own editing. Before we try to remedy the symptoms (i.e., re-requesting or re-sending the rollback token), I'd like to try to figure out the root of the problem. To this end, I will: (1) write some
1117:
which was uploaded tonight. If you run this version from the terminal/command-prompt, and you encounter a case where there is an editing/revert error, there should be detailed terminal output which you can submit to me. I have also taken the time to include some code to better distinguish the "error"
729:
If this can't be blamed on something specific to your system, there is little I can do programatically to address the problem. I have never heard of anything like this before. Also, I use established Java packages (ui.Swing) to code the GUI elements, so it would not be easy to open them up and adjust
654:
Andrew, I have a lot of garbage on my STiki screen right now. If you are interested in pursuing this, I can email you a screen photo that I took with my smartphone, along with details of my computer configuration. I hate to throw things at you that are not related to STiki core function. I think this
629:
There have been multiple claims that people were re-seeing the same edits, and I'm not trying to discredit you, but we've always traced it back to exactly this type of case. These vandalism detection algorithms, are after all, signature based. If someone is doing something repeatedly (inserting same
525:
Hi Peter, I'll look into this bug shortly. I will run a trace of your classifications and see if, indeed, some of the revisions do show up twice. This is pretty core functionality for something to go wrong and unnoticed for so long -- although maybe it is specific to the WikiTrust queue -- which does
2253:
No luck; same error. I also tried installing Update 10, and that didn't work either. Update 5 said it had already been installed. Admittedly, I haven't done a reboot, but the updates didn't say one was needed. Are there some debugging options that I could try running it with that would help get more
2115:
I had never intended that page to be super human-friendly. Instead, by using the "What links here" functionality of the toolbox -- a user who sees a "dead links" pointer to an article they care about will investigate that link. This has worked (at least) a couple of times in the past -- and tends to
2092:
Hi there! Seems like a nice tool that. However I couldn't find description of it anywhere? Perhaps the output would be more readable if it was slightly rearranged. Currently the output looks to me almost machine readable! First, most people are interested only in certain subjects on Knowledge, so in
2002:
has received so many complaints about his vandalism-detection methods that he has stated on his talk page: "I am sick & tired of inexperienced people who themselves have been involved in editing that has attracted discussions, telling me how my recent revert / edit was wrong." Reasoning with him
692:
About the same time I was getting the screen garbage, I started getting low-memory messages from Chrome. The STiki problem had something to do with re-drawing (the garbage would appear, or change, when I brought STiki out from behind other windows. I will send you the screen shots, in case you still
555:
Andrew, yes, I have always been logged in as Peter Chastain. I agree that the queuing problem is more important than the scrolling one (in which, sometimes, when I use the wheel on my mouse, part of the text in the diff-browser screen is scrolled, while other text there stays put). Your diff-browser
337:
In fact, the rule was not in place (but should have always been). It's now been fixed and the change is active on the STiki server (I am not going to push out a new source-code version for the minor change). A few bot-edits may still pop-up, however, if they existed in the queue prior to the time of
1530:
I continue to get this message a lot. To answer the question you posed, above, the time I spend off-STiki varies, but I do tend to research things before reverting. You mentioned the possibility that the token has expired on WP while I was doing other work. Would it be possible for STiki to re-send
615:
I have run a database report of your STiki activity, and have no evidence that you scored the same RID more than once. In particular, I output the ~250 RIDs which you classified as "innocent" using the WikiTrust queue. Then, I piped them into the Offline Review Tool (ORT) and quickly cycled through
574:
What I am trying to say is that, to root out deliberately inserted inaccuracies, it is necessary to review a lot of perfectly good edits. In evaluating one change by an editor, I look at other things that the editor has changed. Here, I think the WikiTrust queue has great potential. I don't know if
2029:
I'd consider a STiki block, but it seems he has already moved onto using Huggle instead. A quick scan of his edits using that tool might be warranted (a found a few questionable ones, but will not call them out here -- he seems to be a bit "unsourced revert" happy). Moreover, there was evidence he
1983:
who decided to revert your edit. You should take up this issue with him (and I agree that this edit is not indicative of vandalism). If you notice that a STiki user has mis-used the tool multiple times (isolated mistakes do happen), please notify me. A user can have their privilege to use the tool
1692:
Hello, West.andrew.g/Archive 4. Recently when I went to log-in to Knowledge; I saw that you put a nice, big vandalism sticker on a IP Page which was my own. I had never edited with an IP. Probably you gave another guy a warning but it came on to me; as IP's periodically change their digits. By the
891:
in my queue. It was , so I clicked the Revert button. STiki gave me the message, "LAST REVERT 71.251.132.63 (contribs) (talk) RB'd 0 edits beaten to revert? check page hist". But the page history shows that the edit has not been reverted. This happened a few minutes ago, some time around 2100-2110
178:
is that people shouldn't be calling something "vandalism" unless they are really, really sure it's vandalism. If the STiki user warning message's edit summary were visible and configurable in the GUI, the way the edit summary for the article text reversion already is, I wouldn't be as concerned.
2045:
You can see from his talk page that reasoning with him fails. I don't have a link to the administrative noticeboard. He can simply remove any of my inappropriate comments. Thanks for the information, nevertheless. I am delighted to know that my spelling-corrections will now be reverted to the old
1496:
Ive seen your edits repeatedly come up on my stalk lists (irc bot), even though it was a false positive it did lead me to further investigate. I see you have made 24392 edits reporting dead links in your userspace. I think that that is a waste of server resources and should instead be logged to a
1018:
Hi Peter. I was perhaps a little over-zealous in my "run from the command prompt" advice for this particular problem (though it still applies to the other ones). At current, there is no terminal output for this case (nothing is "broken" -- the error case is being caught and that is displaying the
989:
Here is what I would suggest: After an attempted reversion, STiki should check to see whether the article has been updated (by anyone) after the edit in question. If not, there is a problem. (I thought I fixed something, but it wasn't fixed.) In that case, there could be an error message (perhaps
807:
Deleted articles/revisions can introduce some nasty corner-cases in code. Follow my above advice about running STiki from the command-line, and then copy-paste the terminal output the next time you encounter this error (be patient for a couple minutes if it does not produce anything immediately).
772:
in the diff-browser window and went off to look at it and do some off-STiki reversion. By the time I got back to STiki and clicked the Vandalism (Undo) button, the article had been speedily deleted. When I click any of the three classification buttons (Vandalism (Undo), Pass, or Innocent) nothing
743:
One thing you can do to help with this, and all bug reports, is to start STiki from the command line, (i.e., Windows calls this "command prompt"). If something goes wrong, their will be terminal output, instead of silently failing. These messages are extremely helpful to me in tracking down these
715:
This is a tricky issue that I am afraid might be outside my scope. First, I wonder if all this might be related to the "low memory message" you saw in Chrome. I'm not sure what your machine is capable of, but I was able to count ~18 tabs open in one Chrome instance alone. I would think that would
509:
Andrew, I installed STiki (2.0) yesterday and started using it with the Cluebot-NG queue. Later, I changed to the WikiTrust queue. Then I closed STiki and later re-opened it. It started up, using the Cluebot-NG queue, which I used for a while. Then I switched to WikiTrust and noticed that all the
173:
I would suggest "User warning for addition of inappropriate material", or "User warning for unconstructive editing". Calling a reverted edit "test/vandalism" is, IMO, especially wrong because it implies that the editing might have been vandalism, or maybe just a test, or maybe the reverter can't
128:
I believe it would be far better for STiki and similar tools to err on the side of caution. I do appreciate the way the edit summary text for the actual reversion of article text can be configured (and, indeed, I have chosen to modify this text to call the material I am reverting "inappropriate"
1509:
I've had several reports of users utilizing the "what links here" functionality positively with respect to this listing and its archives. If my "dead links" page shows up in the listing for an article, it indicates there is a link in need of monitoring -- and requires much less manual labor than
1080:
Why have you not acquired the rollback permission? I highly suggest you do this. I assume you have the "use rollback" box checked when use STiki. If you don't have the native rollback right (which you don't), STiki uses a lot more logic and bandwidth trying to simulate the behavior for you. Both
864:
Issue resolved (I think). The IRC server server on which the CBNG feeds operate is currently down (I've notified them on the talk page, maybe others should pile on), so not possible to test. Their may still be some old instances residing in the queue, but no new ones will be added in the future.
845:
CBNG actually scores its own edits really poorly sometimes (reason unknown), though I would assume there is some logic to prevent it from reverting itself (maybe some broader rule, like 1RR). STiki just consumes the raw scoring feed on IRC, so sometimes CBNG-queue users will see an edit that was
2321:
I am continuing my digging. It seems things would be greatly simplified if you could get Java version 1.5 to version 1.6, but I assume this didn't happen with the Apple update because your machine is not "Intel-based or 64-bit capable"? What is frustrating is that this error is being thrown at
929:
Hate to sound like a broken record here, but follow above advice regarding run STiki from the command-line. For this particular report, I will note that the "RB'd 0 edits..." message is kind of a fallback case. If the rollback does not succeed for any reason, this is what will be output -- only
788:
I am able to use menu functions, such as changing the queue. After I changed the queue from Cluebot-NG to WikiTrust and then clicked Pass, I got the "you've been using Pass too much" message, but it still did not advance to the next item in the queue. I ended up having to restart STiki. Cheers,
630:
content, massive deletions (which is what redirects look like to some algorithms)), and the algorithm doesn't like it, all of these instances are likely to land close to each other in the queue. Unless some new evidence of this issue arises, I am inclined to mark this issue as "closed." Thanks,
157:
What would you suggest the wording be? I am open to suggestions. However, given that a STiki user has explicitly identified an edit as vandalism, I personally don't see a major issue with labeling it as such (but I would be willing to change the default summary). If there are "valid questions",
1645:
section of Civil War related articles? Certainly not everybody who sees a title listed in the FR section is going to buy it, but even if only a tiny fraction of readers does, there's a lot of money involved, which obviously is the incentive for spamming. (While I was writing this, I found out
179:
STiki is, in my view, highly useful for identifying and reverting misguided, mangled, or disruptive edits, even if they are not indisputably (or indisputably not) "vandalism" ā€” things that definitely need to be reverted ASAP, and why not let people revert them using this good-quality tool?
266:
My name is Victor Grigas and I'm a Storyteller at the Wikimedia Foundation. We're exploring new ways to explain why Knowledge is so special and weā€™ve started a Knowledge Stories Project, where weā€™re chronicling the inspiring stories of the Knowledge community, especially editors and active
118:. My concern is with the use of the word "vandalism": many people are very sensitive to having this term applied to their editing ā€” and if there is any valid question on the motivation of a given edit, we should probably defer to the Knowledge vandalism policy, which explicitly says that 1665:
Hi Bender, and thanks for the kind words about my presentation. Bookspam is an interesting problem and at first glance one that is probably much harder than typical online link spam. Consider that, (1) most things which enter publication are legitimate writings, this isn't exactly the
1434:
What you did, and what I recall doing, sound the same. As I noted above, the rollback right, or lack thereof, doesn't seem to be a factor. I will watch closely to see if it happens again, though I probably will not be on WP very much until 2012. Thanks, and have a happy New Year.
1118:
and "beaten to revert" cases. The corresponding messages/branches are now completely exclusive of each other for clarity; but both have been made bold/red in the GUI in order to give some prominence to the situation. Let me know your experience/output from this. Thanks,
952:
I started STiki from a Windows Vista command window and am getting RB'd 0 edits messages (where there were recent actual edits to the article), but no messages in my command window, unfortunately. (The command window shows a command prompt, followed by my command,
1817:
Nope, you've done all that needs to be done! This is how the dead-link reporting service was intended to be used -- people notice the article on the "What Links Here" page and conducts an appropriate investigation/removal into the (possibly) dead link. Thanks,
1321:
I see that now. Previously, I stumbled across a page that had a list of rollback users with alphabetical "jump to" links (not the page that has the search function -- which showed you did have them). Apparently this former list was out of date or something.
438:
I read your paper on the spam detection tool. I would like to suggest two new features. The first, is whether a user has added a single link to multiple articles. The second, is how similar the IP of the landing site to the IP of the user adding the link.
716:
probably stress Chrome's memory allocation and make in-roads towards total system memory? If memory is hurting, this could cause some havoc with your graphics card. Have you experienced these errors again? If so, what was the system load at that time?
1368:
Curious,:how long are these edits sitting in the STiki window while you do your off-STiki work? I am not sure of how the WP folks treat/handle tokens, but maybe there is some possibility the token has expired while you did this other work? Thanks,
1019:"RB'ed 0 edits message"). I will code up a new version of STiki that *does* print some debugging info to the terminal. It's easy to make the message more prominent. I want to figure out what condition is causing this error to be displayed. Thanks, 2322:
start-up, rather than when you actually try to click on hyper-links in the program (a problem I have seen in the past). Give me a little while to look at this, I might be able to compile a version that does not have this class dependency. Thanks,
2123:
I agree that someone could use this raw data to generate new interfaces into it, and this could certainly be helpful for the community. To be honest, though, this is not at the top of my priorities at this point. Thank you for your comments,
975:
my reversion was unsuccessful. My real concern is knowing whether anybody's reversion (or subsequent edit) was actually done. I suppose I should go to the article's history whenever I see the "RB'd 0 edits" message, but I often forget to do
2119:
Adding a table of contents doesn't make a whole lot of sense. To prevent editing conflicts (given the frequent updates), every single line in the report is itself a section. Thus, a table-of-contents would double the length of every report
1049:
The message should also state the title of the article that was not changed. Currently, even if I check for a "RB'd 0 edits" message, I cannot go check on the article, because I didn't write down what article I was trying to revert.
1709:
are a fact of Internet life -- its why IP blocks are generally temporarily. While it may be interesting to think about who in your vicinity/IP-block might have committed the vandalism, I don't have much else in the way of comment
1764:(a) I don't think this is easy to do in Java swing packages. (b) Why would anyone want to? The gray-ish theme is pretty standard among applications, no? Wouldn't a picture just makes things incredibly busy looking for the user? 1242:
Can you add, to the console message, the name of the article that failed to revert? That would make it easier for me to go back and fix those. (Of course, if the bad-token problem gets fixed, maybe all this will be moot.)
1531:(or re-request; I don't understand the mechanism here) the token at the point when I actually click the revert button? Or would it make sense to retry a rollback that fails with the "badtoken" and "Invalid token" errors? 1285:
Yes, this can be added, but it is too low priority a change to push out a whole new version at this time. It will be included in the next one, and as you say, hopefully we can fix the root of the problem instead. Thanks,
2389:
seems to define a solution to the issue (albeit a bit hacky). Give me a little while to integrate this into my code-base, test it, and push a new version out. I'll ping you on your talk-page when I get it done. Thanks,
1907:
for bots, and various upcoming features and changes. We'd love to have power users, bot maintainers and writers, and template makers at these events so we can all learn from each other and chat about what needs doing.
1798:" with my AWB when I noticed your archive page /Dead links/Archive 73 (Jul 26, 2011 10:42:39 PM GMT). It looks tool generated, so I am not sure what to do and left it as it is. The dead links, however, have been fixed 970:
This is such a frequent occurrence that I have to be a bit skeptical that the most common reason for the message is that someone else reverted or edited the article, but that doesn't really matter. I don't much care
730:
anything. Moreover, it seemed like the "garbage" was not confined to STiki components, but instead to quite randomly-defined boundaries across the screen. Do other applications show/produce "garbage", or only STiki?
2072:. There are multiple places to lodge a complaint if you believe his behavior is inappropriate. It's not my area of expertise, but I would say the talk-page message might be in the "Wikiquette" domain. Thanks, 105: 454:
Thanks for the read. The first one sounds viable, although it would seem to overlap a good significantly with the "times URL added in last ". The second one is a good one, and something already done by
212:
Give me a day or two, and I'll distribute a new version (I prefer "unconstructive"). I probably have some other loose ends and efficiency modifications I'd like to push out at the same time. Thanks,
1882: 1565:
Download the new release. When a 'badtoken' is now encountered, there should be some additional terminal output, now. Send it to me via e-mail. Eventually we'll get this solved. Thanks,
1693:
way can I recommend a suggestion? I use STiki and found it very fast, helpful, and easy to use. Can you kindly change the background picture into a Knowledge based picture if possible?
1337:
In my most recent STiki session, several hours ago, I got five instances of the "badtoken" message and one (legitimate) "allreadyrolled". I will continue to keep you advised. Cheers,
534:
WikiTrust" (assuming everything is working correctly). This is of course, is dependent on a complex set of criteria, how many people have been using a particular queue lately, etc.
584:
At any rate, WP quality control is a fight waged on many fronts, and it is a good thing that STiki accommodates reviewers who find their niche in the various areas of that effort.
149: 1202:, I'll try to implement a fix so to remedy these conditions. Either way, follow my advice to get the rollback permission and you'll have these problems less frequently. Thanks, 2227:
Thanks! Not being a Java programmer (I prefer Perl), I had little idea what was inside your program and what was in the local library/libraries/whatever. I'll give that a try.
2294:
java version "1.5.0_30" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_30-b03-389-9M3425) Java HotSpot(TM) Client VM (build 1.5.0_30-161, mixed mode, sharing)
1943: 830:
Very occasionally, when I am using the Cluebot-NG queue, I am presented with an edit that Cluebot-NG made. For an example, see revision 467440865. Is this normal behavior?
1081:
methods should be sound, but the "native" version is certainly less error-prone and better tested. Regardless, I am still looking into what might be going wrong. Thanks,
1317:
I have rollbacker and reviewer rights, as you do, and I'm pretty sure I have had the "Use Rollback Action" box checked for the entire time that I have been using STiki.
2553:
Give it another try, I changed the file behind (so no Knowledge edit was made), and I am pretty confident this new version should fix your issues. Let me know. Thanks,
808:
Revert actions are forked to produce a separate thread that shouldn't affect GUI advancement, so I am a little curious to see where this error lands in code. Thanks,
529:
Can you describe what the scrolling issue is? I fret this could be a tougher fix -- its not like I actually implement scrolling, this is just something Java provides.
556:
window is useful for a quick look at differences, but when I want to explore further, the Wiki-DIFF and Page-Hist links give me a nicer view with more functionality.
839: 399:). Also, it inserts two hyphens before the signature, which looks a bit silly for those of us who include an em-dash at the start of our signature already. ā€” 1252: 1059: 920: 798: 360:
I greatly appreciate your quick response, and will enjoy fighting leftover vandalism with your tool with no worry of reverting an approved bot. Thank you. --
2081: 2039: 1556: 1444: 1425: 1378: 1361: 1295: 1211: 1169: 1127: 1090: 1028: 999: 939: 855: 817: 753: 702: 683: 639: 602: 546: 2658: 2628: 1773: 1574: 874: 825: 347: 1728: 2151: 2133: 1993: 1843: 1827: 1681: 1352:
Hmm, I wonder what makes these tokens go "bad". The same code is used to retrieve the edit tokens that do succeed the other 98% of the time. Very odd.
468: 249: 221: 427: 2143: 2094: 1346: 1152:
Awesome changes! I love the links in the Last Revert panel. I have been starting STiki from the command line. When I attempted to revert a change to
901: 2580: 2562: 2471: 2433: 2399: 2365: 2331: 2240: 2218: 1719:
I am always interested in suggestions for STiki, but it is unclear what you mean by "background"? What is the current "background picture"? Thanks,
1331: 990:
bold red typeface, but definitely more prominent than the inconspicuous "RB'd 0 edits" message), saying "WARNING: Article was not changed". Thanks,
195: 846:
actually made by CBNG. This isn't indicative on an error, but it seems reasonable that I write some logic to short-circuit this behavior. Thanks,
418:. However, since the issue is so minor, I am not going to rebuild and push out a new version immediately, it might take a couple of days. Thanks, 2650: 2620: 2102: 782: 769: 395:
I've noticed a minor issue with the level one warnings STiki leaves on user talk pages. Specifically, it says "Thank you" twice at the end (see
110:
I see a problem with the user warning messages produced by STiki. The problem is with the edit summary, which (as far as I can tell) is always
1957:
article. And I see nothing of vandalism in any of the edits that were reverted. I think this is a STiki bot issue that needs to be addressed.
1519: 377: 328: 309: 286: 2267: 281: 1601: 674:. I will have more time to look at these issues in the next couple days, when my last minute pre-holiday work and travel concludes. Thanks, 519: 2533: 2309: 2198: 1627: 2665: 1486: 664: 2635: 2061: 2022: 882: 408: 488: 459:, so I didn't feel the need to duplicate the effort (academically), but it might be something worthwhile for practical use. Thanks, 448: 2142:
I found about the Dead links patrolling for recent changes ending up to the page without the intro. Thanks the info and the tools.
1877: 1198:
Yes, you can help by continuing to post these error codes from the terminal window. If it frequently lands on the same case, i.e.,
2420:
Take whatever time you need (I know what it's like being a graduate student!); I certainly have enough other things to work on...
2209:
site, searching for "Java", and installing "Java for Mac OS X 10.5 Update 4" will fix your woes. Let me know how it goes. Thanks,
1540: 2087: 1972: 1402: 315:
Valid concern, I thought I had an explicit rule to prevent this -- apparently not. I am currently enjoying the great sessions at
496: 1650:".) I wondered if you ever considered finding methods to detect bookspammers just the way you want to detect link spammers. -- 2162: 1811: 1697: 2516:
Exception in thread "main" java.lang.NoSuchMethodError: executables.stiki_frontend_driver.setIconImages(Ljava/util/List;)V
2053: 2014: 1503: 1954: 1745:
currently. It is a Light-brownish colour theme in the background (You can see at the log-in corner). I'm trying to tell,
1659: 763: 159: 526:
not see a lot of use. This is the user-name you were using? And you logged in with the same user-name both times, right?
414:
Thanks, Darkwind. I've removed the two hyphens, and removed the extraneous "Thank you", which seems to be the result of
294:
has come up quite a few times when I was using it. Can STiki not queue up edits from accounts with the bot userright? --
2741: 865:
Note, because CBNG feeds are down, I've changed the default queue to "STiki" until CBNG-IRC comes back online. Thanks,
415: 158:
shouldn't the edit be labeled as "pass" or handled via off-STiki channels (as you seem to do with all edits)? See also
94: 1592:. Please be advised it did not work, and if you have admin powers I'd be grateful for a schoolblock. Following your 2733: 2728: 2716: 2711: 2706: 1478: 1153: 261: 120:"Even if misguided, willfully against consensus, or disruptive, any good-faith effort to improve the encyclopedia is 86: 81: 69: 64: 59: 2602: 396: 1912: 1888: 1964: 1452: 957:, followed immediately by another command prompt. Should I be seeing that second prompt before STiki terminates?) 191: 145: 655:
could be a non-problem if STiki had a refresh button. As it is, I will have to stop and restart STiki. Cheers,
504: 387: 291: 532:
Also, you'll generally find that the accuracy of classifications among the queues looks like "Cluebot-NG : -->
2520:(stiki_frontend_driver.java:231) at executables.stiki_frontend_driver.main(stiki_frontend_driver.java:157) 2576: 2529: 2429: 2361: 2305: 2263: 2236: 2194: 1849: 649: 2462:. Let me know how it goes, since I can't really test the fall-back functionality of the library. Thanks, 1582: 1458: 433: 1615: 2685: 2109: 1855: 1623: 1609: 38: 2004: 369: 302: 2558: 2467: 2395: 2327: 2214: 2129: 2077: 2035: 1989: 1839: 1823: 1769: 1724: 1677: 1570: 1552: 1515: 1491: 1421: 1374: 1357: 1327: 1291: 1207: 1123: 1086: 1024: 935: 870: 851: 813: 749: 679: 635: 542: 464: 423: 343: 324: 245: 217: 1916: 1672:
heavy machinery I've used in anti-vandalism and anti-spam seem overkill or impossible here. Thanks,
2057: 2018: 1948: 1930:, Wikimedia Foundation's Volunteer Development Coordinator. Please reply on my talk page, here or 1834:
Sidenote; though I am not really sure your adjustment changed the link to one that works properly?
1536: 1440: 1398: 1342: 1248: 1165: 1055: 995: 916: 897: 835: 794: 778: 698: 660: 598: 515: 474: 2694: 1409: 484: 47: 17: 1525: 2069: 277: 1979:
STiki is *not* a bot, it is intelligent routing tool operated by humans. In this case, it was
1384: 1315:(Moving indention level back to the left, but this is in response to your various comments...) 670:
Send me the screen shot and I will take a look. You can find my email on my personal webpage,
1619: 1605: 1470: 1931: 1158:
A rollback failed to commit. The server returned code "badtoken" and details "Invalid token"
2147: 2098: 2049: 2010: 1960: 1785: 1589: 392:
Hi there, thanks for all your hard work and research that has resulted in this great tool!
2167:
Hi. I'm running OS X 10.5.8, and get the following problem when trying to start up STiki:
1920: 1408:
Strange. I am unable to simply reproduce the error. I logged onto my no-rollback account (
8: 1968: 1807: 1655: 1532: 1436: 1394: 1338: 1244: 1161: 1051: 991: 912: 893: 831: 790: 774: 694: 656: 594: 511: 444: 187: 141: 2554: 2463: 2391: 2323: 2210: 2125: 2073: 2031: 1985: 1835: 1819: 1765: 1720: 1687: 1673: 1647: 1566: 1548: 1511: 1417: 1370: 1353: 1323: 1287: 1203: 1119: 1082: 1020: 931: 866: 847: 809: 745: 675: 631: 538: 480: 460: 419: 404: 339: 320: 241: 213: 1896: 1892: 1939: 1867: 1642: 273: 130: 1900: 2572: 2525: 2425: 2357: 2301: 2259: 2232: 2190: 1999: 1980: 1694: 1632: 1462: 175: 1927: 2459: 1114: 113: 2693:
If you wish to start a new discussion or revive an old one, please do so on the
46:
If you wish to start a new discussion or revive an old one, please do so on the
1803: 1651: 888: 440: 316: 180: 134: 1638: 1498: 1596:
warning and yet another round of vandalism from this IP, another editor gave
1156:, I got the "RB'd 0 edits" message, and the following in the command window: 400: 2173:
Exception in thread "main" java.lang.NoClassDefFoundError: java/awt/Desktop
1935: 1859: 2568: 2521: 2500:
Afraid not working quite yet (exception inside the executable this time):
2421: 2386: 2353: 2297: 2255: 2228: 2205:
one that ships with 10.5.* is a bit out of date. Seemingly, visiting the
2186: 2181:
at executables.stiki_frontend_driver.main(stiki_frontend_driver.java:157)
1799: 456: 1891:
where you can learn more about MediaWiki customization and development,
2644: 1953:
STiki has reverted "theses," which is a mispelling of "these," in this
1795: 2206: 1791: 693:
want to look at them, and will let you know if this persists. Thanks!
1604:
that editor why they did not impose the rootin' tootin' schoolblock.
1854:
I kindly request you to have a look at the suggestion I posted here:
362: 296: 908: 1160:. Thanks, and please let me know if there is any way I can help. 106:
STiki user warning's edit summary is unconfigurable and too strong
1904: 1389:
I went outside of STiki to do an assume-good-faith rollback of
671: 319:, but I will look into this ASAP and report back here. Thanks, 1921:
developers' days preceding Wikimania in July in Washington, DC
1749:, can you change the colour to a picture of Knowledge-related? 2611: 1883:
Invitation to events: bot, template, and Gadget makers wanted
1588:
Hello, In response to persistent IP vandalism I noticed that
1413: 1390: 2352:
That's odd, it is an Intel mac - it is not 64-bit, however.
2185:
Unsurprisingly, clicking on it directly also doesn't work.
2108:
Hi Palosirkka. The main "gateway" to the dead links is via
1706: 112:"User warning for addition of test/vandalism found using 1790:
Hi West.andrew.g, I was updating a change in domain of "
1618:
if you are interested in details. Sorry to bother you.
1614:
This comment was posted by mistake. You can follow the
1113:
Now you should be able to download the new version of
2645:
http://en.wikipedia.org/User:DBigXray/STiki_UserBox_3
892:UTC, but it is not an uncommon occurrence. Cheers, 2519:at executables.stiki_frontend_driver.<init: --> 2178:at executables.stiki_frontend_driver.<init: --> 1984:revoked when it is not used responsibly. Thanks, 2617:awesome, thats what i was looking for, thanks 1461:where you might be able to get some responses. 1646:Knowledge already has a name for this: it's " 160:User_talk:ClueBot_Commons#Why_no_follow_up.3F 2175:at gui_panels.gui_button_panel.<init: --> 826:Cluebot-NG revisions in the Cluebot-NG queue 1416:that it was not handled correctly? Thanks, 2116:be how most people discover this listing. 1590:you gave that IP editor a "last warning" 1893:extending functionality with JavaScript 1887:I thought you might want to know about 14: 2691:Do not edit the contents of this page. 287:STiki queues edits from approved bots? 240:Done, per today's re-compile. Thanks, 44:Do not edit the contents of this page. 2672: 25: 1796:http://www0.parlamento.gub.uy/leyes 23: 2282:Oh. In terms of the java version, 1792:http://www.parlamento.gub.uy/leyes 24: 2755: 1741:Sorry, but there's no background 1154:Teaching grandmother to suck eggs 2676: 2610: 2179:(stiki_frontend_driver.java:201) 1856:Wikipedia_talk:STiki#Flexibility 1639:your anti-vandalism presentation 29: 2088:Suggestion on Dead links output 883:RB'd 0 edits, beaten to revert? 174:tell ā€” but my understanding of 2458:Done. New version uploaded at 1923:, or any other of our events. 1616:this link to VSmith's talkpage 1612:) 17:13, 25 January 2012 (UTC) 500:12:07, 20 September 2011 (UTC) 489:19:54, 19 September 2011 (UTC) 469:08:14, 15 September 2011 (UTC) 449:06:51, 15 September 2011 (UTC) 428:05:30, 15 September 2011 (UTC) 409:02:28, 15 September 2011 (UTC) 13: 1: 2163:STiki not starting up on OS X 2082:16:03, 17 February 2012 (UTC) 2062:15:57, 17 February 2012 (UTC) 2040:15:45, 17 February 2012 (UTC) 2023:15:26, 17 February 2012 (UTC) 1994:02:35, 17 February 2012 (UTC) 1973:02:26, 17 February 2012 (UTC) 1944:16:12, 16 February 2012 (UTC) 1844:17:57, 13 February 2012 (UTC) 1828:17:54, 13 February 2012 (UTC) 1774:17:55, 13 February 2012 (UTC) 1445:20:12, 30 December 2011 (UTC) 1426:15:48, 30 December 2011 (UTC) 1403:13:13, 30 December 2011 (UTC) 1379:20:46, 30 December 2011 (UTC) 1362:20:26, 30 December 2011 (UTC) 1347:20:12, 30 December 2011 (UTC) 1332:20:26, 30 December 2011 (UTC) 1296:15:33, 30 December 2011 (UTC) 1253:11:56, 30 December 2011 (UTC) 1212:15:33, 30 December 2011 (UTC) 1170:11:16, 30 December 2011 (UTC) 1128:09:09, 29 December 2011 (UTC) 1091:03:30, 29 December 2011 (UTC) 1060:00:11, 29 December 2011 (UTC) 1029:00:12, 29 December 2011 (UTC) 1000:23:46, 28 December 2011 (UTC) 940:03:37, 28 December 2011 (UTC) 921:22:36, 27 December 2011 (UTC) 902:21:23, 27 December 2011 (UTC) 875:03:15, 29 December 2011 (UTC) 856:03:21, 28 December 2011 (UTC) 840:15:06, 25 December 2011 (UTC) 818:03:28, 28 December 2011 (UTC) 799:08:48, 23 December 2011 (UTC) 783:08:02, 23 December 2011 (UTC) 754:03:04, 28 December 2011 (UTC) 703:08:02, 23 December 2011 (UTC) 684:19:54, 22 December 2011 (UTC) 665:19:21, 22 December 2011 (UTC) 640:02:41, 29 December 2011 (UTC) 603:11:46, 22 December 2011 (UTC) 547:18:48, 21 December 2011 (UTC) 520:18:40, 21 December 2011 (UTC) 2046:misspellings using Huggle. 1878:15:03, 5 February 2012 (UTC) 1812:17:00, 4 February 2012 (UTC) 1729:05:55, 4 February 2012 (UTC) 1698:05:18, 4 February 2012 (UTC) 1682:18:53, 30 January 2012 (UTC) 1660:14:17, 30 January 2012 (UTC) 1628:17:22, 25 January 2012 (UTC) 1575:03:38, 17 January 2012 (UTC) 1557:16:33, 16 January 2012 (UTC) 1541:10:59, 15 January 2012 (UTC) 1497:text file on your computer. 1487:19:14, 11 January 2012 (UTC) 672:http://www.andrew-g-west.com 7: 2567:Works! Thanks very much... 764:Reverting a deleted article 416:this recent template change 378:23:26, 11 August 2011 (UTC) 10: 2760: 2666:03:19, 18 March 2012 (UTC) 2636:03:19, 18 March 2012 (UTC) 2581:20:10, 12 March 2012 (UTC) 2563:19:49, 12 March 2012 (UTC) 2534:17:32, 12 March 2012 (UTC) 2472:17:05, 12 March 2012 (UTC) 2434:16:29, 12 March 2012 (UTC) 2400:15:53, 12 March 2012 (UTC) 2366:16:29, 12 March 2012 (UTC) 2332:15:40, 12 March 2012 (UTC) 2310:15:11, 12 March 2012 (UTC) 2268:14:31, 12 March 2012 (UTC) 2241:13:58, 12 March 2012 (UTC) 2219:13:43, 12 March 2012 (UTC) 2199:04:07, 12 March 2012 (UTC) 2176:(gui_button_panel.java:91) 2110:Knowledge:STiki/Dead_links 1520:02:00, 9 August 2011 (UTC) 1504:01:47, 9 August 2011 (UTC) 348:15:08, 9 August 2011 (UTC) 329:03:16, 7 August 2011 (UTC) 310:01:44, 7 August 2011 (UTC) 250:15:06, 1 August 2011 (UTC) 2643:also do have a look here 2152:13:15, 6 March 2012 (UTC) 2134:22:31, 5 March 2012 (UTC) 2103:16:52, 5 March 2012 (UTC) 887:Andrew, I got an edit to 282:18:54, 21 July 2011 (UTC) 262:Wikimedia Stories Project 222:03:28, 26 July 2011 (UTC) 196:03:15, 26 July 2011 (UTC) 150:23:18, 20 July 2011 (UTC) 2603:Some bubble tea for you! 1917:Berlin hackathon in June 907:It happened again, with 1453:Your help desk question 1410:User:West.andrew.g.norb 18:User talk:West.andrew.g 2070:Knowledge:Noticeboards 2003:has had no effect, as 1913:Chennai event in March 1903:, how to best use the 1705:IP addresses that use 505:STiki Queue repetition 388:STiki level 1 warnings 2689:of past discussions. 1901:Lua templating system 1899:and Gadgets, the new 42:of past discussions. 1928:Sumana Harihareswara 1889:some upcoming events 1850:Feedback about STiki 955:STiki_2011_12_02.jar 650:STiki screen garbage 338:the change. Thanks, 1583:schoolblock request 434:Spam detection tool 2747: 2746: 2701: 2700: 2695:current talk page 2641: 2640: 2052:comment added by 2013:comment added by 1963:comment added by 1873: 1810: 1643:"Further reading" 1492:Your recent edits 499: 375: 100: 99: 54: 53: 48:current talk page 2751: 2725: 2703: 2702: 2680: 2679: 2673: 2661: 2656: 2653: 2631: 2626: 2623: 2614: 2607: 2606: 2182: 2064: 2025: 2000:User:Arunsingh16 1981:User:Arunsingh16 1975: 1949:STiki is Erratic 1932:at mediawiki.org 1895:, the future of 1874: 1869: 1864: 1806: 1620:NewsAndEventsGuy 1606:NewsAndEventsGuy 1481: 1473: 1465: 1201: 1159: 956: 744:errors. Thanks, 495: 475:Hello, from CLEF 376: 372: 367: 365: 308: 305: 299: 78: 56: 55: 33: 32: 26: 2759: 2758: 2754: 2753: 2752: 2750: 2749: 2748: 2721: 2677: 2659: 2654: 2651: 2629: 2624: 2621: 2605: 2517: 2295: 2207:Apple Downloads 2171:java -jar *.jar 2170: 2165: 2090: 2047: 2008: 1958: 1951: 1926:Best wishes! - 1885: 1868: 1860: 1852: 1788: 1690: 1637:I just watched 1635: 1613: 1600:warning. FYI, 1585: 1528: 1501: 1494: 1479: 1471: 1463: 1455: 1387: 1199: 1157: 954: 885: 828: 766: 652: 507: 494:Hello there! -- 477: 436: 390: 374: 370: 363: 361: 307: 303: 297: 295: 289: 264: 108: 74: 30: 22: 21: 20: 12: 11: 5: 2757: 2745: 2744: 2739: 2736: 2731: 2726: 2719: 2714: 2709: 2699: 2698: 2681: 2670: 2639: 2638: 2615: 2604: 2601: 2600: 2599: 2598: 2597: 2596: 2595: 2594: 2593: 2592: 2591: 2590: 2589: 2588: 2587: 2586: 2585: 2584: 2583: 2515: 2514: 2513: 2512: 2511: 2510: 2509: 2508: 2507: 2506: 2505: 2504: 2503: 2502: 2501: 2485: 2484: 2483: 2482: 2481: 2480: 2479: 2478: 2477: 2476: 2475: 2474: 2445: 2444: 2443: 2442: 2441: 2440: 2439: 2438: 2437: 2436: 2409: 2408: 2407: 2406: 2405: 2404: 2403: 2402: 2377: 2376: 2375: 2374: 2373: 2372: 2371: 2370: 2369: 2368: 2341: 2340: 2339: 2338: 2337: 2336: 2335: 2334: 2293: 2292: 2291: 2290: 2289: 2288: 2287: 2285: 2275: 2274: 2273: 2272: 2271: 2270: 2246: 2245: 2244: 2243: 2222: 2221: 2180: 2177: 2174: 2172: 2164: 2161: 2159: 2157: 2156: 2155: 2154: 2137: 2136: 2121: 2117: 2113: 2089: 2086: 2085: 2084: 2054:63.248.139.209 2043: 2042: 2015:63.248.139.209 1997: 1996: 1950: 1947: 1911:Check out the 1897:ResourceLoader 1884: 1881: 1851: 1848: 1847: 1846: 1831: 1830: 1787: 1784: 1783: 1782: 1781: 1780: 1779: 1778: 1777: 1776: 1755: 1754: 1753: 1752: 1751: 1750: 1734: 1733: 1732: 1731: 1714: 1713: 1712: 1711: 1689: 1686: 1685: 1684: 1668: 1667: 1634: 1631: 1587: 1584: 1581: 1580: 1579: 1578: 1577: 1560: 1559: 1533:Peter Chastain 1527: 1524: 1523: 1522: 1500: 1493: 1490: 1454: 1451: 1450: 1449: 1448: 1447: 1437:Peter Chastain 1429: 1428: 1395:Peter Chastain 1386: 1383: 1382: 1381: 1365: 1364: 1339:Peter Chastain 1335: 1334: 1316: 1313: 1312: 1311: 1310: 1309: 1308: 1307: 1306: 1305: 1304: 1303: 1302: 1301: 1300: 1299: 1298: 1268: 1267: 1266: 1265: 1264: 1263: 1262: 1261: 1260: 1259: 1258: 1257: 1256: 1255: 1245:Peter Chastain 1227: 1226: 1225: 1224: 1223: 1222: 1221: 1220: 1219: 1218: 1217: 1216: 1215: 1214: 1183: 1182: 1181: 1180: 1179: 1178: 1177: 1176: 1175: 1174: 1173: 1172: 1162:Peter Chastain 1139: 1138: 1137: 1136: 1135: 1134: 1133: 1132: 1131: 1130: 1102: 1101: 1100: 1099: 1098: 1097: 1096: 1095: 1094: 1093: 1069: 1068: 1067: 1066: 1065: 1064: 1063: 1062: 1052:Peter Chastain 1040: 1039: 1038: 1037: 1036: 1035: 1034: 1033: 1032: 1031: 1007: 1006: 1005: 1004: 1003: 1002: 992:Peter Chastain 982: 981: 980: 979: 978: 977: 963: 962: 961: 960: 959: 958: 945: 944: 943: 942: 924: 923: 913:Peter Chastain 894:Peter Chastain 889:Iron Man match 884: 881: 880: 879: 878: 877: 859: 858: 832:Peter Chastain 827: 824: 823: 822: 821: 820: 802: 801: 791:Peter Chastain 775:Peter Chastain 765: 762: 761: 760: 759: 758: 757: 756: 736: 735: 734: 733: 732: 731: 722: 721: 720: 719: 718: 717: 708: 707: 706: 705: 695:Peter Chastain 687: 686: 657:Peter Chastain 651: 648: 647: 646: 645: 644: 643: 642: 622: 621: 620: 619: 618: 617: 608: 607: 606: 605: 595:Peter Chastain 588: 587: 586: 585: 579: 578: 577: 576: 569: 568: 567: 566: 560: 559: 558: 557: 550: 549: 535: 530: 527: 512:Peter Chastain 506: 503: 502: 501: 476: 473: 472: 471: 435: 432: 431: 430: 389: 386: 385: 384: 383: 382: 381: 380: 368: 353: 352: 351: 350: 332: 331: 317:Wikimania 2011 301: 288: 285: 263: 260: 259: 258: 257: 256: 255: 254: 253: 252: 231: 230: 229: 228: 227: 226: 225: 224: 203: 202: 201: 200: 199: 198: 166: 165: 164: 163: 107: 104: 102: 98: 97: 92: 89: 84: 79: 72: 67: 62: 52: 51: 34: 15: 9: 6: 4: 3: 2: 2756: 2743: 2740: 2737: 2735: 2732: 2730: 2727: 2724: 2720: 2718: 2715: 2713: 2710: 2708: 2705: 2704: 2696: 2692: 2688: 2687: 2682: 2675: 2674: 2671: 2668: 2667: 2664: 2663: 2662: 2657: 2646: 2637: 2634: 2633: 2632: 2627: 2616: 2613: 2609: 2608: 2582: 2578: 2574: 2570: 2566: 2565: 2564: 2560: 2556: 2555:West.andrew.g 2552: 2551: 2550: 2549: 2548: 2547: 2546: 2545: 2544: 2543: 2542: 2541: 2540: 2539: 2538: 2537: 2536: 2535: 2531: 2527: 2523: 2499: 2498: 2497: 2496: 2495: 2494: 2493: 2492: 2491: 2490: 2489: 2488: 2487: 2486: 2473: 2469: 2465: 2464:West.andrew.g 2461: 2457: 2456: 2455: 2454: 2453: 2452: 2451: 2450: 2449: 2448: 2447: 2446: 2435: 2431: 2427: 2423: 2419: 2418: 2417: 2416: 2415: 2414: 2413: 2412: 2411: 2410: 2401: 2397: 2393: 2392:West.andrew.g 2388: 2385: 2384: 2383: 2382: 2381: 2380: 2379: 2378: 2367: 2363: 2359: 2355: 2351: 2350: 2349: 2348: 2347: 2346: 2345: 2344: 2343: 2342: 2333: 2329: 2325: 2324:West.andrew.g 2320: 2319: 2318: 2317: 2316: 2315: 2314: 2313: 2312: 2311: 2307: 2303: 2299: 2284:java -version 2283: 2281: 2280: 2279: 2278: 2277: 2276: 2269: 2265: 2261: 2257: 2252: 2251: 2250: 2249: 2248: 2247: 2242: 2238: 2234: 2230: 2226: 2225: 2224: 2223: 2220: 2216: 2212: 2211:West.andrew.g 2208: 2203: 2202: 2201: 2200: 2196: 2192: 2188: 2183: 2168: 2160: 2153: 2149: 2145: 2141: 2140: 2139: 2138: 2135: 2131: 2127: 2126:West.andrew.g 2122: 2118: 2114: 2111: 2107: 2106: 2105: 2104: 2100: 2096: 2083: 2079: 2075: 2074:West.andrew.g 2071: 2067: 2066: 2065: 2063: 2059: 2055: 2051: 2041: 2037: 2033: 2032:West.andrew.g 2028: 2027: 2026: 2024: 2020: 2016: 2012: 2006: 2005:his talk page 2001: 1995: 1991: 1987: 1986:West.andrew.g 1982: 1978: 1977: 1976: 1974: 1970: 1966: 1962: 1956: 1946: 1945: 1941: 1937: 1933: 1929: 1924: 1922: 1918: 1914: 1909: 1906: 1902: 1898: 1894: 1890: 1880: 1879: 1875: 1872: 1865: 1863: 1857: 1845: 1841: 1837: 1836:West.andrew.g 1833: 1832: 1829: 1825: 1821: 1820:West.andrew.g 1816: 1815: 1814: 1813: 1809: 1805: 1801: 1797: 1793: 1775: 1771: 1767: 1766:West.andrew.g 1763: 1762: 1761: 1760: 1759: 1758: 1757: 1756: 1748: 1744: 1740: 1739: 1738: 1737: 1736: 1735: 1730: 1726: 1722: 1721:West.andrew.g 1718: 1717: 1716: 1715: 1708: 1704: 1703: 1702: 1701: 1700: 1699: 1696: 1683: 1679: 1675: 1674:West.andrew.g 1670: 1669: 1664: 1663: 1662: 1661: 1657: 1653: 1649: 1644: 1640: 1630: 1629: 1625: 1621: 1617: 1611: 1607: 1603: 1599: 1595: 1591: 1576: 1572: 1568: 1567:West.andrew.g 1564: 1563: 1562: 1561: 1558: 1554: 1550: 1549:West.andrew.g 1545: 1544: 1543: 1542: 1538: 1534: 1521: 1517: 1513: 1512:West.andrew.g 1508: 1507: 1506: 1505: 1502: 1489: 1488: 1485: 1482: 1480:contributions 1477: 1474: 1469: 1466: 1460: 1446: 1442: 1438: 1433: 1432: 1431: 1430: 1427: 1423: 1419: 1418:West.andrew.g 1415: 1411: 1407: 1406: 1405: 1404: 1400: 1396: 1392: 1380: 1376: 1372: 1371:West.andrew.g 1367: 1366: 1363: 1359: 1355: 1354:West.andrew.g 1351: 1350: 1349: 1348: 1344: 1340: 1333: 1329: 1325: 1324:West.andrew.g 1320: 1319: 1318: 1297: 1293: 1289: 1288:West.andrew.g 1284: 1283: 1282: 1281: 1280: 1279: 1278: 1277: 1276: 1275: 1274: 1273: 1272: 1271: 1270: 1269: 1254: 1250: 1246: 1241: 1240: 1239: 1238: 1237: 1236: 1235: 1234: 1233: 1232: 1231: 1230: 1229: 1228: 1213: 1209: 1205: 1204:West.andrew.g 1197: 1196: 1195: 1194: 1193: 1192: 1191: 1190: 1189: 1188: 1187: 1186: 1185: 1184: 1171: 1167: 1163: 1155: 1151: 1150: 1149: 1148: 1147: 1146: 1145: 1144: 1143: 1142: 1141: 1140: 1129: 1125: 1121: 1120:West.andrew.g 1116: 1112: 1111: 1110: 1109: 1108: 1107: 1106: 1105: 1104: 1103: 1092: 1088: 1084: 1083:West.andrew.g 1079: 1078: 1077: 1076: 1075: 1074: 1073: 1072: 1071: 1070: 1061: 1057: 1053: 1048: 1047: 1046: 1045: 1044: 1043: 1042: 1041: 1030: 1026: 1022: 1021:West.andrew.g 1017: 1016: 1015: 1014: 1013: 1012: 1011: 1010: 1009: 1008: 1001: 997: 993: 988: 987: 986: 985: 984: 983: 974: 969: 968: 967: 966: 965: 964: 951: 950: 949: 948: 947: 946: 941: 937: 933: 932:West.andrew.g 928: 927: 926: 925: 922: 918: 914: 910: 906: 905: 904: 903: 899: 895: 890: 876: 872: 868: 867:West.andrew.g 863: 862: 861: 860: 857: 853: 849: 848:West.andrew.g 844: 843: 842: 841: 837: 833: 819: 815: 811: 810:West.andrew.g 806: 805: 804: 803: 800: 796: 792: 787: 786: 785: 784: 780: 776: 771: 770:Chloe Shimmin 755: 751: 747: 746:West.andrew.g 742: 741: 740: 739: 738: 737: 728: 727: 726: 725: 724: 723: 714: 713: 712: 711: 710: 709: 704: 700: 696: 691: 690: 689: 688: 685: 681: 677: 676:West.andrew.g 673: 669: 668: 667: 666: 662: 658: 641: 637: 633: 632:West.andrew.g 628: 627: 626: 625: 624: 623: 614: 613: 612: 611: 610: 609: 604: 600: 596: 592: 591: 590: 589: 583: 582: 581: 580: 573: 572: 571: 570: 564: 563: 562: 561: 554: 553: 552: 551: 548: 544: 540: 539:West.andrew.g 536: 531: 528: 524: 523: 522: 521: 517: 513: 498: 493: 492: 491: 490: 486: 482: 481:West.andrew.g 479:As promised. 470: 466: 462: 461:West.andrew.g 458: 453: 452: 451: 450: 446: 442: 429: 425: 421: 420:West.andrew.g 417: 413: 412: 411: 410: 406: 402: 398: 393: 379: 373: 366: 359: 358: 357: 356: 355: 354: 349: 345: 341: 340:West.andrew.g 336: 335: 334: 333: 330: 326: 322: 321:West.andrew.g 318: 314: 313: 312: 311: 306: 300: 293: 284: 283: 279: 275: 274:Victor Grigas 271: 268: 251: 247: 243: 242:West.andrew.g 239: 238: 237: 236: 235: 234: 233: 232: 223: 219: 215: 214:West.andrew.g 211: 210: 209: 208: 207: 206: 205: 204: 197: 193: 189: 185: 183: 177: 172: 171: 170: 169: 168: 167: 162:. Thanks, -AW 161: 156: 155: 154: 153: 152: 151: 147: 143: 139: 137: 132: 126: 125: 121: 117: 115: 103: 96: 93: 90: 88: 85: 83: 80: 77: 73: 71: 68: 66: 63: 61: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 2722: 2690: 2684: 2669: 2649: 2648: 2642: 2619: 2618: 2518: 2296: 2184: 2169: 2166: 2158: 2091: 2048:ā€” Preceding 2044: 2009:ā€” Preceding 1998: 1959:ā€” Preceding 1952: 1925: 1910: 1886: 1870: 1861: 1853: 1789: 1786:link updated 1746: 1742: 1691: 1636: 1602:I have asked 1597: 1593: 1586: 1529: 1526:RB'd 0 edits 1495: 1483: 1475: 1467: 1456: 1388: 1336: 1314: 972: 886: 829: 767: 653: 508: 478: 437: 397:this example 394: 391: 290: 272: 269: 265: 181: 135: 127: 123: 119: 111: 109: 101: 75: 43: 37: 2683:This is an 1802:. Regards, 1747:if possible 1598:yet another 1464:Vchimpanzee 1385:RB'd 1 edit 533:STiki : --> 457:User:COIBot 270:thank you, 124:vandalism." 36:This is an 2742:ArchiveĀ 10 2144:Palosirkka 2095:Palosirkka 1955:Macroscope 1688:Warning??? 95:ArchiveĀ 10 2734:ArchiveĀ 6 2729:ArchiveĀ 5 2723:ArchiveĀ 4 2717:ArchiveĀ 3 2712:ArchiveĀ 2 2707:ArchiveĀ 1 2387:This page 1965:76.8.8.27 1804:Hoverfish 1652:bender235 1459:this page 773:happens. 593:Thanks, 441:Sole Soul 176:WP:VANDAL 87:ArchiveĀ 6 82:ArchiveĀ 5 76:ArchiveĀ 4 70:ArchiveĀ 3 65:ArchiveĀ 2 60:ArchiveĀ 1 2577:contribs 2530:contribs 2460:WP:STiki 2430:contribs 2362:contribs 2306:contribs 2264:contribs 2237:contribs 2195:contribs 2050:unsigned 2011:unsigned 2007:shows. 1961:unsigned 1695:Dipankan 1648:bookspam 1633:Bookspam 1457:I found 1200:badtoken 1115:WP:STiki 909:Macherla 537:Thanks, 401:Darkwind 371:contribs 304:contribs 292:EmausBot 192:contribs 146:contribs 2686:archive 2286:yields: 1936:Sumanah 1905:web API 1871:talk me 1862:Anbu121 1743:picture 133:tool. 131:Twinkle 39:archive 2569:Allens 2522:Allens 2422:Allens 2354:Allens 2298:Allens 2256:Allens 2254:info? 2229:Allens 2187:Allens 1919:, the 1915:, the 1794:" to " 768:I got 497:ćØ恂悋ē™½ć„ēŒ« 2647::) -- 2120:page! 1710:here. 1414:Nokia 1391:Nokia 184:wales 138:wales 114:STiki 16:< 2660:XŠÆaÉ£ 2630:XŠÆaÉ£ 2573:talk 2559:talk 2526:talk 2468:talk 2426:talk 2396:talk 2358:talk 2328:talk 2302:talk 2260:talk 2233:talk 2215:talk 2191:talk 2148:talk 2130:talk 2099:talk 2078:talk 2068:See 2058:talk 2036:talk 2019:talk 1990:talk 1969:talk 1940:talk 1840:talk 1824:talk 1808:Talk 1770:talk 1725:talk 1707:DHCP 1678:talk 1656:talk 1624:talk 1610:talk 1594:last 1571:talk 1553:talk 1537:talk 1516:talk 1472:talk 1441:talk 1422:talk 1399:talk 1375:talk 1358:talk 1343:talk 1328:talk 1292:talk 1249:talk 1208:talk 1166:talk 1124:talk 1087:talk 1056:talk 1025:talk 996:talk 936:talk 917:talk 898:talk 871:talk 852:talk 836:talk 814:talk 795:talk 779:talk 750:talk 699:talk 680:talk 661:talk 636:talk 599:talk 543:talk 516:talk 485:talk 465:talk 445:talk 424:talk 405:talk 344:talk 325:talk 278:talk 246:talk 218:talk 188:talk 182:Rich 142:talk 136:Rich 2655:ā„¬ig 2625:ā„¬ig 1934:. 1499:Ī”T 976:so. 973:why 122:not 2738:ā†’ 2579:) 2575:| 2561:) 2532:) 2528:| 2470:) 2432:) 2428:| 2398:) 2364:) 2360:| 2330:) 2308:) 2304:| 2266:) 2262:| 2239:) 2235:| 2217:) 2197:) 2193:| 2150:) 2132:) 2101:) 2080:) 2060:) 2038:) 2021:) 1992:) 1971:) 1942:) 1876:) 1858:-- 1842:) 1826:) 1772:) 1727:) 1680:) 1658:) 1626:) 1573:) 1555:) 1539:) 1518:) 1443:) 1424:) 1401:) 1377:) 1360:) 1345:) 1330:) 1294:) 1251:) 1210:) 1168:) 1126:) 1089:) 1058:) 1027:) 998:) 938:) 919:) 911:. 900:) 873:) 854:) 838:) 816:) 797:) 781:) 752:) 701:) 682:) 663:) 638:) 601:) 545:) 518:) 487:) 467:) 447:) 426:) 407:) 346:) 327:) 280:) 248:) 220:) 194:) 190:Ā· 148:) 144:Ā· 91:ā†’ 2697:. 2652:Ɛ 2622:Ɛ 2571:( 2557:( 2524:( 2466:( 2424:( 2394:( 2356:( 2326:( 2300:( 2258:( 2231:( 2213:( 2189:( 2146:( 2128:( 2097:( 2076:( 2056:( 2034:( 2017:( 1988:( 1967:( 1938:( 1866:( 1838:( 1822:( 1800:1 1768:( 1723:( 1676:( 1654:( 1622:( 1608:( 1569:( 1551:( 1535:( 1514:( 1484:Ā· 1476:Ā· 1468:Ā· 1439:( 1420:( 1397:( 1373:( 1356:( 1341:( 1326:( 1290:( 1247:( 1206:( 1164:( 1122:( 1085:( 1054:( 1023:( 994:( 934:( 915:( 896:( 869:( 850:( 834:( 812:( 793:( 777:( 748:( 697:( 678:( 659:( 634:( 597:( 541:( 514:( 483:( 463:( 443:( 422:( 403:( 364:Ī£ 342:( 323:( 298:Ī£ 276:( 244:( 216:( 186:( 140:( 116:" 50:.

Index

User talk:West.andrew.g
archive
current talk page
ArchiveĀ 1
ArchiveĀ 2
ArchiveĀ 3
ArchiveĀ 4
ArchiveĀ 5
ArchiveĀ 6
ArchiveĀ 10
STiki
Twinkle
Richwales
talk
contribs
23:18, 20 July 2011 (UTC)
User_talk:ClueBot_Commons#Why_no_follow_up.3F
WP:VANDAL
Richwales
talk
contribs
03:15, 26 July 2011 (UTC)
West.andrew.g
talk
03:28, 26 July 2011 (UTC)
West.andrew.g
talk
15:06, 1 August 2011 (UTC)
Victor Grigas
talk

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

ā†‘