Knowledge talk:STiki/Archive 18

535:

block from atop the queue. These reservations all have a "time-to-live" (TTL) of ~10 minutes. If the edits aren't classified in 10 minutes after receipt, the reservation is released on the server side (despite the fact they still may be cached and enqueued locally for subsequent display). This is a practical necessity: We can't let an attacker own the entire database by taking out infinite reservations on everything, and if someone does not close STiki correctly (or it hits a bug) then the reservation will not be elegantly released (and we want someone else to classify these edits). There are *also* checks ran every couple seconds to de-queue locally cached edits that have since incurred an edit conflict. In all probability, a pause/delay/slowdown/break by one user caused the edit to be re-issued, and the timing was narrow enough to avoid the aforementioned checks. I don't see this is a significant problem (the edit conflict was noted); this is lots of checking and my timing evidence shows 99.9%+ of edits are classified within their 10 minute reservation window (or elegantly released).

718:. although they have done some with vandalism, and warn users pretty consistently, it seems like there are some issues with false positives, ie, reverting constructive contributions. a related concern is that the user has not always fully replied to reponses made by users whose edits they reverted. i think CVUA would help EoRdE6 get a better sense of how to deal with ambiguous cases, discussion with other editors, using the talk page, etc. aside from some sparse contributions on an old account from over a year ago, EoRdE6 has only been editing for about a month. i think it's a good idea to take more time to become familiar with counter-vandalism efforts. ~ 2560:"Provides for" is an interesting one. Similar to "support" really, but slightly different connotation... like it is less likely that the collaborative approach would exist without STiki. "Empowers" doesn't work for me. "Employs" is a new way of looking at it. It's like the collaborative way of working was already there and STiki just uses it. Kind of the opposite of "provides for" but also kind of true. Makes me wonder if there is a word that means something does both. Likes "Fits in with"... "coheres with".... although we've still got the problem of it not being clear that this collaborative approach wouldn't exist without STiki. 211:

add emphasis (a la red text)? I'm not sure Java's bare bones browser can handle the "spans" and other techniques used in the current Mediawiki style. As a bit of a hypothetical is there even a need to try to show this white-space? If it doesn't effect rendering, who cares? If rendering is not affected, could it just be treated as a null diff? Maybe a note could be added when excess whitespace is present (acknowledging the fact it might not be rendered)? Point being, I can't imagine a completely elegant/straightforward solution at the moment. Does the community have any thoughts?

1348:

restart interfaces in Linux, things like "service network restart", "ifup eth0", sending commands to the specific network manager, etc.). I emailed my on-site colleague within one hour, but unfortunately it was caught in a spam filter, and the correction was not completed until he returned to the office on Monday AM. These maintenance windows have slowed dramatically now that classes are back in session at the hosting site, so I am hopeful we will have a good long run -- and if not -- I am hopeful I have finally found something that works on the auto-reconnect front. Thanks,

2780:, STiki was responsible for the trailing "2014 (UTC)" instance at the document's end, but the diff-parse suggests it pre-pended a ""2014 (UTC)" to its section creation, and then awkwardly "in-line inserted" (vs. "appended") a warning without a full date to instead use the date that was associated with the previous warning (tough to describe; sorry). Clearly, this is not how the edit happened in practice. This is something I've only seen very recently, and I suspect this weirdness may be confusing the MediaWiki parser about the section creation. 1593:

is obviously not obvious vandalism: at first sight, the figures look plausible. So only a thorough check somewhere else will uncover whether this is a constructive edit or not. I actually hate such edits. I do check sometimes; but at other times I say to myself: please, let the soccer fans or movie afficionados concerned do the checking themselves - it is just so time-consuming. Subsequently, I press 'Pass' (leaving it to someone else). What are your opinions about this?! How do you co-patrollers handle such edits?! Thanks for any feedback.

1562:

exact title, which STiki created just seconds earlier. STiki's policy and that of other tools is to append warnings to the existing section (assuming there is one that matches the month/year). Why this happened is a bit perplexing, but 'replag' (replication lag on the WMF servers) is a leading candidate since the two warnings were made only a couple of seconds apart (the failure to escalate the warn-level on the second warning also corroborates this). This might not be STiki's fault, but STiki poorly handled the situation after that.

937:

your name not appearing at the top of the window, or the "You are not logged in. Your IP address will be publicly visible if you make any edits." warning that appears above an edit window. However, when making automated edits with a tool like STiki, none of that happens. STiki thinks it is logged in, and it would be difficult for it to detect that it no longer is. Bots are supposed to use something called "assert=user" to check they are logged in, but I don't know if there is a good way of doing that for a tool like STiki.

3188:: Those individual clicks are recorded privately on my server and not publicly released. Internal to my tool that feedback is used to: (1) Determine if someone else needs to review the edit (no duplicate reviews), (2) For ongoing algorithmic refinement (i.e., training of machine learning models), and (3) Analyzed in aggregate to prevent tool abuse (if someone submits 1000 "innocent" classifications per minute, we have a problem). Externally, aggregates of your classification behaviors will become publicly available at 31: 1158: 601: 704: 1498:

router. Chances are this shared IP resides at some institution (school, business, etc.) that has blocked the MySQL port (3306) from sending/receiving traffic. This can be done for security reasons, content policy, bandwidth savings, etc. You may be able to speak with a network administrator about opening that port in the institutional firewall, but this is nothing STiki has control over (STiki is never even seeing your connection attempt). Thanks,

1988: 1977: 3060: 2962: 2899: 2012: 1312: 1742:. so by default, these edits are still presented for assessment, but the user could have the option to tick a box and turn thr filter on. this way, the editors who just want to "pass" all of them can skip a step in the process, while users who have time/patience to be more thorough can handle these edits. maybe there could even be an option to 1780:

STiki-initiated edits to be associated to user's IP addresses. If there is any concern a STiki user was "outed" in this fashion, contact me privately and I'll use my admin bit to REVDEL the edits into oblivion. This version will break previous ones; old versions should no longer work and pop a dialogue about the new version. Aside from this:

914:

session key and I don't think we even have "log out" code that could be mis-firing -- so something has to be happening on the WMF side to preliminary terminate things. I'm not privy to what that is, and it might be hard to file a bug report with the WMF given this strange junction of my third-party tool and their server-side behavior.

2040:

side (login panel, classification) doesn't seem to be resizable. This isn't a big issue for me because I happen to know that that's the 4im button, etc, but I thought I'd let you know. One thought is if the left side cannot be resizable then perhaps we could reduce the width of the Back button. Here's a link to a screenshot:

1702:

indeed, but make an exception for numerical-only-changes that change numbers and make them very much larger or very much smaller (say by a factor 10 or more)? With me such large changes always trigger the alarm bells.3. Deciding on such numerical-only-edits will remain a matter of judgment I presume.

734:. However, how many of those ever return to classify as part of the STiki team? To some extent this might speak to the fact the user wasn't *that* interested, but conversely, we could be losing participants due to borderline circumstances (trying to imagine through some cost-benefit-risk ratios here). 3486:

I wouldn't mind if this option were added, but at some point the wish to have a message for every case runs up against the need to keep the list to a manageable size. We have Unsourced and Unsourced-BLP messages; we can always see when a new addition is unsourced, but often can't tell if it really is

3415:

As a matter of interest, if a user posted (for example) a uw-biog1 message on a user's page and then STiki reverted a different edit, would STiki give a uw-vandalism1 or uw-vandalism2? Some of the warnings seem very similar to vandalism. For example, the difference between a test edit and vandalism

3236:

I know what you mean, as I have had to make manual edits/changes myself. Other cases include situations which require a revert across more than one vandal account/IP. This cannot be done via standard rollback, and so the only options left are "Pass" or "Innocent". It would hesitate to use the former,

2859:

I made about 25-50 reverts last night (see my contributions) using a version that replaced "\r" with "\n". Going through the talk page notifications, I observed no issues, though I am unsure if I hit any cases that would have been problematic previously (not really sure what characterizes these cases

2763:

In the initial diff that Materialscientist provided there is a single carriage return -- by design -- after the previous warning before the section header that STiki placed (if there wasn't, the first two equals signs would likely be on the previous line). STiki's source code has been adding a single

2190:

Do you do any unusual login/logout behaviors? Run any other external tools in parallel that require login? What version of STiki are you using? The new version released yesterday-ish can detect this as described in item T#048 (see the CHANGELOG thread above). Could you download the new version; spot

2178:

Greetings, and thank you for your work. It appears all your actions are being logged by the STiki tool (and captured on our "leaderboard"). However, when I spot check the RIDs (you have provided feedback for) on the encyclopedia, I see many of them have been reverted by the STiki tool, but associated

2072:

As a preface, GUI development is super un-fun work. Producing something that looks natural and aligned as resolutions change and whitespace disappears probably consumes 2/3 of the STiki code-base (as opposed to interesting anti-vandal logic). Your entire display is a bit "spacier" than mine, which is

1898:

Hello everyone: I think the message could be rephrased like has been said (this is a regular editor - are you sure you want to revert him/her?); gives one an incentive to think twice. But after that thinking-twice I have enough buttons to live with (good faith with several messages; vandalism without

1567:

At every subsequent warning STiki asked "does this user talk page have a 'November 2014'" section on it?". My code was always returning the first such section, parsing it to find the highest level (the level 1), and saying "give this user a level 2 warning". Then that warning was getting appended the

913:

I'm on a plane (and therefore a sub-par connection). Can someone search/link the archive on this? I recall this coming up before, but I am not sure I had a great explanation. STiki continues to record the username in its databases, so it seems the WMF is dropping the session? STiki never modifies the

738:

doesn't seem like a terrible burden to me. How long does it ordinarily take to complete (absent communications delays)? Others may have noticed our "milestones" page has been a little sluggish lately, and we haven't been on-boarding new users at the typical rate. Daily classification counts have also

269:

Be bold in making that change if you think it appropriate. I will investigate the possibility of displaying byte change counts somewhere in the metadata panel, although things are already quite tight. As you mentioned, a raw plus/minus doesn't always tell the whole story. The back-end classifier uses

3365:. This lets you give all sorts of messages in an efficient way. You can then unselect "warn offending editor" in STiki and press "vandalism". When you go to the vandal's talk page and use Twinkle, it will have already filled in the name of the article you reverted in the form for the user message. 3254:

If an article edit is made external to STiki while that article is displayed in the STiki window, any subsequent (attempted) edits via STiki will fail due to an edit conflict. This conflict will be reported in the "last revert" panel. No matter which button is pressed, STiki will record the feedback

2305:

Not at this time. We've only had ~50 tickets in STiki's history so a dedicated platform may well be more cumbersome than it is worth. Moreover, there is some convenience in having it adjacent to our project discussion. I think the current approach well serves non-technical portions of the user base,

2137:

I have been using STiki over the last few days, and went back to one article to see how the vandalism reversion was logged. To my surprise, neither this, nor any other of the article edits I have been able to check on, were affected by my classifying them in the STiki interface. In other words, when

2092:

Yes, I believe the back button has always been that big. Things never aligned perfectly but that is of little concern. The important part is the functionality which is clearly there. Here the only thing I see bothering someone who's never used the tool is that we don't see all of the 4im button. The

1717:

I'd recommend caution before assuming these edits are innocent, because even small changes to numbers and dates surprisingly often turn out to be inconsistent with other parts of the article (lead, body, infobox, tables, persondata) or with an adjacent citation. One can imagine a young person saying

1526:

for vandalism, I selected Vandalism classification in Login panel for this purpose. To my observation warnings for vandalism were issued as "User warning for unconstructive editing found using STiki". Initially i thought user might have been blocked from editing as i have issued him many warnings(as

1446:

I don't know about this, but recently, I tried opening STiki up on a shared IP address and it showed me the error message. At home, it always works but I can't seem to ge it to work in shared IP addresses. Is it because that I can't operate it under a shared IP or I can't operate it under an IP that

454:

It is perhaps worthwhile to look into how easy it would be to turn STiki into a Java applet that could run inside a browser (though I imagine some aspects of the GUI might not transfer simply). Anyone have any perspective on this? Otherwise, a thorough re-coding is probably not on my agenda (heck, a

197:

There is a larger shortcoming here, though, and that is that the diff display is essentially a bare-bones HTML browser. HTML renders multiple space characters as a single one. This is true also of actual Knowledge pages. Notice that although wikitext may contain multiple spaces, they are rendered as

2840:

My code has been using the "\r" code (carriage return) in the Java string formatting to achieve these line breaks. This is noteworthy, because myself and other programmers usually default to "\n" (new line) to achieve the same effect. This leads me to believe (and I can almost recall), I tried "\n"

2077:

Has your "back" button always been that wide? On my machine (by code design) it is probably not a pixel wider than the vertical text it contains (and then everything in that panel fits nicely). Would you be willing to email me to open a thread whereby we can exchange screenshots and new versions to

2039:

Hi, thanks for the awesome update! I use OSX 10.9, and with the update some parts of the interface are not completely visible. This includes the 4im button, the watchlist options dropdown, and the links in the edit properties box. The latter you can fix by resizing the whole interface, but the left

1592:

certain numerical data: like a footbalclub, the number of goals made goes up from 8 to 9, when we move from 2013 to 2014. Or a baseball pro has a new score, up from 88 to 90, as we move from 2012 to 2014. Or a certain movie has new box-office results. Etcetera etcetera. Variations are endless. This

1561:

STiki has considerable logic to auto-increment warning levels in an intelligent manner (designed to play nice with Huggle's system and other tools), and some aspects of that failed here. First, STiki should have never created a second section labeled "November 2014". There was already one with that

1225:

That sounds a bit more like an "alternate" server, in which both servers run simultaneously, syncing data between each other, and one can take over when one goes down. Because the STiki server stores edits, having a temporary server that only runs when the main server is down would probably mean no

1195:

As soon as one the aforementioned colleague walks down to the server room and presses a button. As pre-condition to this, he'd need to actually be in the office. We're getting dangerously close to the weekend, so I just sent an email to an additional contact who can help. There is nothing technical

974:

which "cannot" happen; it is a bot which has not noticed that it is logged out). Similar incidents have been reported in the past, although I've never seen a direct explanation. Apparently some bots (wmflabs?) access Knowledge directly without going through the Internet, so private IP addresses are

936:

has had claims from people that they get logged out while doing normal editing. When manually editing, if something logs you out you might notice any of several clues such as your skin changing (if you have a non-default skin), or your signature not appearing in a preview (if posting a comment), or

534:

At any given time, a STiki user has ~15 edits on their machine that are queued up for display and have a "reservation" against them in the back-end database. Generally, this means that no other users can have these edits in their queues, nor will others receive these edits when they ask for a fresh

519:

Oh. So it is not a problem that I have only on my end. Apparently, the STiki software works so that "when a user is shown an edit, they have a "reservation" so that no other STiki users are viewing the edit simultaneously ... redundant work (edit conflicts, multiple reviews of good edits) is being

344:

Most of the time, they won't show up. However, as the queues empty, more and more will be the higher scoring ones, so will go to the top of the queue. Ignoring all admin/experienced edits can be a bad thing; If the account is hijacked and starts vandalising, if no one reviews the edits, how will we

233:

Thanks for that explanation. It may seem obvious to you techie folk, but for mere users, like yours truly, maybe a little note in the Using STiki section overleaf to the effect that in the unlikely event that an edit shows up on the diff display as having no apparent change, it's worth checking the

2819:

I swear I did not change the text at all... and yet we don't get a null diff. I think that when you edit manually, MediaWiki must automatically replace the "wrong" new line character with the "right" new line character. This theory also explains why, on the left of the diff, you have an apparent

1701:

OK, thanks for the suggestions everybody. Just a few last remarks. 1. On encountering a minor numerical edit, that looks more or less OK, I will henceforth press Innocent (and not Pass and shift the burden to someone else). 2. About the proposed filter: would it be an idea to introduce that filter

1497:

There is no blanket problem with "shared IP addresses" on Knowledge or STiki. Even if an IP address is blocked (including Tor nodes), that does not prevent someone with a registered account from using that IP address. The more likely issue here is the configuration of the shared IP address and its

583:

Hi all, 'd like to be permitted to use STiki. I'm nowhere near 1,000 article edits, but have been using and somewhat editing Knowledge for almost a decade. Lately I encountered vandalism in an article I've been editing, and so started doing some manual vandalism tracking and reverting. I've read a

242:

s, for example, but such changes would show up anyway on the diff display. On second thought, maybe the above suggestion is overkill... On the other hand, I don't remember a byte count showing up on the STiki diff display, and while for larger edits there's really no need, 'cos red text adequately

210:

In the code behind, STiki has all this whitespace and is coloring it red -- it just gets squished and you can't color whitespace. Can/how do we fix this? One can force whitespace to display, but this could cause some font and line-breaking weirdness. Even if we get it to render visually, how do we

187:

First, I hope you don't mind I changed the section title to something a bit more descriptive for archival purposes. Second, without digging into the source code, I acknowledge this is likely a deficiency of STiki's diff display. The color scheme and use of bold red text to indicate changes mirrors

3017:

I notice that there has been no further bug reports since the latest version of STiki was made available on the 12th. I think that it would make sense to use the feature of STiki that prevents old versions from working and tells people to download the latest version. I say this for two reasons:

1347:

Nothing grand to report here. The connection went down because of planned maintenance, and while my scripts used to *detect* the downtime were accurate, the reconnection code once again failed. I have already authored an alternative strategy for next time (these are all based on ways to check and

3290:

If the displayed edit is half-undoing some previously done vandalism, I usually press good-faith revert. I can see arguments for the other options. It feels right to me because the displayed editor was probably acting in good faith but the edit is semi-unhelpful because it buries the remaining

3277:

Noyster, Orphan wiki, To expand on what Andrew has said, when I am in the situation you describe, I edit the article using the normal wiki interface. I then go back to STiki and press the button that best describes the edit displayed. Sometimes this can be tricky. To go through some examples:

2234:

The back button *never* becomes activated? By design the back button will disable itself when: (1) There is no previous edit (i.e., when STiki starts or you change queues), (2) After you have pressed the the "vandalism" or "AGF" buttons (trying to undo the revert action and any warnings would be

615:

First off, thank you for your long-term participation on the project. This certainly demonstrates good-faith in your request. However, just 60 edits across this time interval doesn't speak much about your knowledge of the warning system and some of the other practicalities by which the vandalism

3156:

No, only if you revert an edit is your action stored in the page history of that article. "Pass" and "innocent" just register within the workings of STiki: if you select "pass" the edit will be displayed again to another STiki user, but if you select "innocent" it will be removed from the STiki

1779:

Greetings STiki-ers... An emergency release was issued this morning because of slight extensions the WMF did to their login procedure (seems geo-location is now part of the process). Our code was not generic enough to handle this rather minor change, breaking login in some respects, and causing

3390:

To add one thing: A vandal shouldn't need a description of how they have erred, it should be obvious. Moreover, we need to use standardized warnings on talk pages because all tools look for these as part of their warning escalation logic. We could add some additional notes/text inside of those

1663:

Of course Yaris' suggestion to actually validate the number is the best policy, but absent that, I think an "innocent" label is appropriate so long as the change in numerical value is minor. These are pretty unsatisfying cases, I agree. In fact, it shouldn't be too hard to write a user filter

3297:

If I have manually edited the article to correct errors introduced by the displayed edit then I will either press "innocent" or "good-faith revert". It mostly depends on how severe the correction was. If in doubt, I usually go for "good-faith revert". Although I haven't, strictly speaking,

2977:

STiki access has been granted. The user has done exclusively patrol/anti-vandal work since joining the project. In the course of this, he/she has demonstrated appropriate use of the warning system, AIV reporting, and the detection of inappropriate usernames. Java expertise lends potential for

2793:

There is no issue with the newline code. It's no problem to add a second carriage return so there is a blank line in the wikitext in these cases. However, some systems (including STiki and Huggle) leave a line of trailing whitespace after warnings that could create a larger-than-expected gap.

2184:

This looks symptomatic of your "edit session dropping" (essentially, the WMF servers are logging you out when they shouldn't, rendering the authentication tokens STiki obtained on your behalf worthless). This page's archives mention this issue a couple of times recently, and there is evidence

1832:

Good catch, and it is an easy fix (if that is the desiresdoutcome). However, I wonder if the real power of the "DTTR" dialog has nothing to do with people changing whether or not a warning is issued, but instead notifying a STiki user they are about to revert someone with a certain degree of

3214:

Got a question myself. Quite often when using STiki I find it necessary to go into the article itself and make an edit that may be more than, less than, or different from a straight revert of the diff on STiki. So which classification to choose when returning to STiki, or doesn't it

243:

covers 99.9% of edits, could a byte count be incorporated as a default setting in the edit properties box (the Wiki-diff link doesn't show this –as I pointed out above, it's necessary to go to the page history to check that)? Or would you also consider this overkill? Regards, --

2823:

My guess is that the code that generates the "December 2014" heading uses the wrong new line character. Has this code changed at all recently? Maybe the MediaWiki API used to correct the new line characters it was given but this has been removed... that would also explain

1608:

Same here, I used to worry about it at first, but then soon started just pressing "Innocent" for such edits. While we are talking about certain edit types which pop up, I got one: those edits by IPs or newusers who blank articles and redirect them--what do you do for this?

3373:

Note that good-faith revert messages are not warnings and shouldn't be used for clear cases of vandalism. In these cases the standard messages produced by STiki are usually sufficient but if you feel like being more specific then Twinkle is probably a good option for

328:

Greetings. Edits by senior editors (admins, reviewers, more than a fixed number of contributions, etc.) are not likely to be unconstructive. So why are they showing up on Stiki? If we remove these edits from the feed, it will be easier to focus on actual vandalism.

2703:

Yep, pretty sure I caught all of these in that initial fix Yaris referenced. It didn't seem worthwhile to issue a new "date of release" and cause confusion, although I guess I maybe should have appended some type of numerical identifier to the filenames. Thanks,

1423:

I agree with Yaris' logic here. Through 600k+ reverts I cannot think of a single time that 3RR has been brought to my attention, and it seems exceedingly unlikely given the criteria above. I don't feel this is something that needs to be implemented at this time.

779:, which does not actually mention Huggle etc. not sure if there is some other message that does? i don't think it would hurt for this message to direct users to the additional tools that are made available by receiving rollback. might also be worth mentioning on 664:

I would like to use STiki. For awhile now I have been patrolling Real Time Recent Changes (Beta) and using Twinkle to revert vandalism. I think STiki could help increase my speed and ease of anti-vandalism. Note: I have made over 500 edits and created a new page

2882:. I picked these people because they are frequent users. I wasn't aware of them having this problem before. The Widr example is interesting because it shows that the problem is there even when no section heading is created. I say roll out the new version. 3336:

Hi there, I'm new to STiki. I understand STiki looks at the vandal's talk page to determine the warning level, and I would like to ask if there is a way to select the type of warning placed on the vandal's talk page; for example the blanking of pages warning.

2235:

messy business), and (3) After you have just pressed the "back" button (the depth is limited to one). If you classify an edit as "innocent" or "pass", then the back button should be enabled and you should be able to go back that one edit. Is that not the case?

1030:

STiki can be a little temperamental when my Internet speed is slow, which means it sometimes stops responding and refuses to close. I can't find the process in task manager, so how can I close it? I can always open a new process, but prefer to close previous.

3419:

By the way, I agree that there isn't much point in being specific about the type of vandalism. But if hz wants to be specific then hz may as well do it in the most efficient way. (Having said that, I don't know how helpful my advice was, given that the page

2185:(including third-party evidence) this is something the WMF servers are screwing up. We've always assumed this "session dropping" to be an unusual event. However, your history indicates otherwise, with it happening to you across multiple days and IP addresses. 2603:

Sorry, but "STiki gives a collaborative approach" is just not idiomatic English. Several other suggestions are better: supports, facilitates, provides. "Supports" is not "wishy-washy"; it is a standard term in the documentation of computing systems.

556:

Thank you for the explanation. The problem is that I was shown the screen just a few seconds before the other edit was being made. When Onel5969 made the revision, it may have been handed to me by accident. It may be a one-time error, though. –

2179:

with an IP address instead of your login account. There are a couple of IPs in this set that are nearly adjacent in address space, but I'll decline to mention these to protect your privacy (contact me privately if you'd like to know them).

3107:

The page works like any other page so if there is a change you don't like you can change it back or discuss it on this talk page. Changes don't get put into code automatically though so Andrew still gets the final say on what's in STiki.

2841:

in STiki's early development, found it not to work when parsed by Mediawiki, and then shifted to "\r" and found it to work. So yes, something new in the Mediawiki parser may be to blame here (and I'll see what "\n" does these days).

754:

Some admins issue a template when they award rollback rights. If I recall correctly, this mentions Huggle and some of the other new capabilities available to rollback users. I don't think STiki is on that list; can and should we be?

1833:

experience (perhaps giving the edit a second look with a widened margin of "good faith"). If this is the case, maybe we should change the wording slightly and pop the dialog regardless of the "warn user?" checkbox status. Thoughts?

1788:

I realize there were some other minor items on the TODO list (null edits, AGF messages). Those have been pushed to the next release due to the haste with which this copy needed to be released. Thank you for the continued support.

1568:

2nd "November 2014" section. Rinse and repeat; the process continued through several warnings. To wrap-up, identically named sections were a problem spot, and I've coded up a fix that will be pushed in the next release. Thanks,

1401:

The STiki workflow means that the revert is normally a few minutes or hours after the original edit, unlike in Huggle. The vandal has normally got bored and gone away before the revert happens, reducing the chance of follow-up

3237:

because there's no need to pass on the diff to anyone else, but at the end of the day, one assumes that the pending diff will be removed from the system when a further edit has been made by an established user to the article.

1931:

Paul, I wasn't suggesting that STiki should enable automation of all the things in the bullet-pointed list. The idea was that the list is part of the message to users. To help them think of what might be appropriate in the

1378:

with Huggle before, not paying close attention to the articles. I don't want that to happen again. Could there be a message box that pops up and prompts you to continue or abondon. That would save a lot of worrying. Thanks,

2940:

Hello, I would like to request permission to use the STiki tool in spite of a relatively few number of edits. I've been involved quite a bit recently in vandalism reversion as you will see from my contribs, relying on the

2764:

carriage return before placing new sections for a long time; so I think its worthwhile to question what has changed. Moreover, a single carriage return should be sufficient, as casual sandbox experimentation will reveal.

1531:. Is there any option which could be added in STiki; where in case of such emergency(where User/IP is vandalizing wikipedia) we can issue him warnings in increasing order of their wrong actions like General Note : --> 1210:

Is it possible to set up an alternative 'temporary' server for Stiki to run when the main server is down? Or to act as a switch to switch it back on or something? I suck at programming, my opinion does sound stupid.

1286:

It doesn't seem like anyone wants to work weekends, especially considering how over there DST just ended, so everyone gets an extra hour of sleep (may as well sleep in rather than work!). Monday it is, then. --I am

2073:

frustrating given that: (a) I write tons of constraint code to keep components displayed in full, but tightly aligned, and (2) I expect the cross-platform nature of Java to standardize things better </rant: -->

2812:

of new line. Believe it or not, there are at least two new line characters in common use. I believe that MediaWiki uses the character that is commonly used in Unix, which is different to that used in Windows.

148:

Hmmm... I wouldn't have expected STiki to highlight the change in red, because, in the diff style STiki uses only the "black" pixels become red. The "blank" pixels stay "blank"... if you see what I'm saying.

2442:, a knob affords twisting but it doesn't enforce it. I like Paul's word "implements". Similar options would be "employs" and "practices". "Effects" would be good, but it could be confused for "affects". 1967: 965:

Oh, you are using the API for the work? I guess you have to ... should think before talking. So, yes, assert=user should be a simple fix for whatever is the underlying problem. For some related humor, check

413:

accounts, not just sysops/crats et al. As Mdann52 stated, in the event the account gets hijacked, like say thru the OpenSSL HeartBleed vulnerability or if their network is intercepted, can't help it right?

3084: 989:

By the way, for testing I think you can log on using a browser and STiki. Then use STiki, then go to the browser and log off. I think that will also log off the STiki session without STiki's knowledge.

3294:

If the displayed edit is innocent and doesn't need reverting, I usually press innocent. I would use this if I had undone a previous edit or done "manual" edit that was unrelated to the displayed edit.

1899:

any message). If needed, just switch to the diff and you find every entry and button that one could need to leave messages etc. So do not complicate this issue - just change the wording, that is all.

300:

Much as I get a kick out o' being bold, with all due respect, I'll wait for some more feedback on that one, especially as to how to phrase it succinctly if the consensus is to include it. Regards, --

440:

Implementation of a web interface for STiki might be a good idea, for those that can't install software, or for those on devices that don't support java app downloading (e.g. Chromebooks). Grognard

270:

a more helpful metric "bytes of churn in edit", but trying to explain/communicate the meaning of this to editors familiar with the current plus/minus one is probably more confusing than beneficial.

2845:

might suggest an alternative method, although that prints the formatting instructions in the wikitext, rather than just making the whitespace appear (the latter probably being preferable). Thanks,

2794:

Regardless, I think someone should open a Mediawiki technical thread or bug report. The fact the document parses two different ways as the result of trailing text like this is quite odd behavior.

1004:

This was confirmed as a bug last month I believe. I think the session issue is a WMF thing. I have found myself logged out multiple times in the past within a few minutes while making an edit. --

3255:

internally, for reasons described in the thread immediately above. For that reason, it is preferred to press the classification button that most accurately describes the diff displayed. Thanks,

865:

It's a registered editor who has WP:STiKi, but, somehow, sometimes the editor's IP address is recorded as using WP:STiki; I noticed the matter earlier this year regarding my own IP address, and

2321: 3409: 2860:

yet, or how prevalent they are). Does anyone see differences in my work and that being produced by the current STiki version? How bad are these issues, do I need to push out a new release?

3133:. I am new to STiki and I am uncertain regarding two of its classifications—"pass" and "innocent". When we click one of them, does it go public. I mean does this store history somewhere?-- 1803: 1647:

If I can't find the answer fairly quickly and the new number looks plausible I will press innocent. (Pressing pass would just mean that other STiki users have to do the same search.)

1527:

what happens in other tools like Huggle, Igloo etc.) but when i saw his talk page, no final warning was added, So i used Twinkle to issue him Final warning & reported the case at

3025:

People that have got one of the two versions that were released on the 1st of December will have issues with the user messages they give, which could potentially confuse other users.

2003: 951:

Thank you for the pointer on the "assert" extension. I wasn't aware of this and it seems straightforward to implement. I've tracked the issue as T#048 in the above table. Thanks,

152:

What is STiki actually showing? A blank diff browser? The exact same text each side? The same text, but with the new spaces inserted (but not highlighted, as explained above)?

3119: 3100:

a while ago, he apologised for making a messy diff. I have temporarily brought back the old messages in the new order and then brought the new ones back again. This means that

3291:

vandalism. If there is a short time between the displayed edit and the vandalism, it seems more likely that the burying was deliberate so I am more likely to press "vandalism".

3287:

If the displayed edit was good-faith but needing a revert and the edits before also needed reverting, I press good-faith revert, even if some of the other edits were vandalism.

2138:

I click on "Vandalism" or "Good Faith Revert", nothing happens: the article remains the same. (Some of the many recent articles that should have been reverted but were not are

3514:

I can think of a theoretical example, but it is so complicated that it would be better to write a bespoke message in that sort of situation. But maybe I am missing something.

2191:

check your contribution history from time to time, and let us know if you get a pop-up indicating the problem has come back (or the problem comes back and you get no pop-up)?

3012: 1528: 2554: 107:

Greetings. Not sure if this classifies as a bug, but I just came across an edit on the STiki diff browser in which no actual changes could be seen. So I popped over to the

2290:

Are there any plans to move the bug tracking over from a table on the project talk page to something that's designed more specifically for bug tracking, like Phabricator?

2264:

Thanks for this clarification; the back button is functioning as designed, then. It seems that updating to the newest version has cleared up the problem entirely. Thanks!

1908: 3022:

People that have got a version from before the 1st of December will not have the "assert=true" check and so could potentially give away their IP address unintentionally.

2372: 1826: 1718:"look mates! I changed this and nobody noticed!" Recommend checking these edits where possible, especially when made by a new user or IP or one with previous warnings 730:

I'll agree with this recommendation. However, I'd also like to have a broader discussion on STiki recruitment and participation. We recommend a lot of people over to

1746:

show numerical edits, for users who want to do some real menial labor. of course, these are just some ideas, and i'm not sure how easy they would be to implement. ~

2745:

the diff suddenly recognizes the line breaks and the message displays correctly. Anyone know what's going on here? My best guess is that STiki is using the wrong

3037: 1583: 234:

revision history to see if the number of bytes has been modified. It's true that the byte count doesn't show vandalism of the type that substitutes all the letter

2058:. Side note – I didn't upload to enwiki or commons as I wasn't sure of copyright concerns. It seems we'd inherently need permission from you. Thanks a million! — 1588:

Hello co-STiki-patrollers, I have a question that keeps coming back to my mind while patrolling. Often enough, an edit (on top of the queue) gets presented which

3508: 2209:

I have downloaded the most recent version (mine was well over a year old) and it seems to run without problems. The back button still does not function, however.

823: 1711: 1602: 1196:

about the solution -- and we've long been troubleshooting code so that the server will re-attach itself to the network, but clearly that isn't working yet.

1040: 2869: 1687: 764: 505:- Hi. This happens to me as well from time to time. Especially when I'm doing two or more things at once, and the Stiki engine sits for a few minutes. 2758: 2698: 3264: 2953: 2122: 2105: 2087: 1923: 1507: 1357: 1342: 1220: 1025: 3004: 2987: 2645: 2627: 2613: 2527: 2028: 1632: 1618: 923: 566: 544: 423: 397: 309: 279: 252: 220: 3435: 3400: 3321: 3076: 2915: 2891: 2854: 2835: 2803: 2713: 2273: 2247: 2221: 2200: 1943: 1890: 1842: 1673: 1433: 1146: 1069: 999: 984: 960: 3201: 2315: 1798: 1205: 1190: 1055: 651: 629: 487:

was performed at the same time as I was going to revert it, also using STiki. Is it supposed to show edits to multiple editors at the same time? –

2580: 2481: 2391: 1957: 1658: 1577: 1492: 1477: 1418: 1013: 805: 787: 722: 693: 684:

Due to above referenced travel, can an experienced STiki community member perform the usual due diligence and make a recommendation here? Thanks,

369: 3245: 2935: 2513: 1733: 1046:

Nevermind, it's the javaw.exe process. I suspected it could've been but wasn't sure, so I just opened multiple processes and sure enough it was.

946: 529: 514: 464: 142: 2733: 2674: 1850:

This user has X edits. Are you sure you want to revert? Sometimes, with more established users, a more bespoke response is appropriate. e.g.:

1764: 1328: 900: 882: 388:

I think I will uncheck the Edits by Privileged Users. Btw, keeping their account secure is part of the requirements for extra privileges right?

383: 178: 124: 3556: 3385: 3101: 3052: 2598: 1457: 643: 610: 585: 163: 3525: 3502: 1304: 1257: 1243: 1132: 3480: 2777:

One thing that looks odd to me is the way Mediawiki is parsing these diffs, specifically the "2014 (UTC)" portion. Intuitively, returning to

2499: 2425: 3172: 1750: 1389: 496: 3352: 3093: 2451: 1547: 2400:

is not idiomatic English; it reads like something written by a non-native speaker of the language. The customary verb characterizing the

2066: 338: 1664:(similar to the one we already have for edits by privileged users) that examines if numerical changes are the only edits to an article. 3303:

In all cases, as Andrew says, the important thing is to do the editing to the article before pressing a classification button in STiki.

3097: 2724:(piling up warnings, breaking section headers due to a missing space - I know it could be superfluous depending on the previous edit). 2110:

Out of curiosity, how many STiki users see something more like MuskiAnimal's screenshot than the "official" one from the project page:

1114: 3043:

Good idea; I had experienced very buggy behavior from an older version, which disappeared as soon as I updated to a more recent one.

2663: 1173: 748: 102: 3284:

If the displayed edit is vandalism but the there were edits before that were good-faith but in need of reverting, I press vandalism.

169:

Greetings, Yaris678. On the two occasions referred to above, "The exact same text each side". No highlights. No inserts. Regards, --

2165: 1774: 1280: 3445: 3230: 2361:

a collaborative approach. I like the word "gives", but I thought it would be good to discuss it here and see what people think.

2113:. Ignore the fact my screenshot is a bit outdated with the new version release. Is this a Mac only thing? I run Linux + Windows. 2238:

Being logged in inside the browser should be no big deal; I think we all do that. I was just looking for something odd. Thanks,

1623:

Oh well, much less in number than those 'numerical' edits. Anyway, I just go in and check and hope I take the right decision...

3368:

Do a good-faith revert. STiki has several good-faith revert messages that can helpfully inform the user where they went wrong.

3281:

If the displayed edit is vandalism but the there were edits before that were vandalism too, I press vandalism. (simplest cases)

1517: 1441: 1226:

edits in the server for STiki users to check, unless the edits on the main server are synced with the alternate server. --I am

2093:

rest of it they'll figure out, and I don't think you should wear yourself out trying to get it perfect ;) You can email me at

1398:

STiki is chiefly about finding and reverting vandalism. Obvious vandalism is exempt from the 3RR. Most vandalism is obvious.

678: 3331: 1395:

Can you describe how you think this will be an issue? I can think of a few reasons why this might not be much of an issue:

1099: 593: 859: 835: 470: 2299: 1784:

The "Revision Filter" menu title was changed to "Displayed Edits" in order to clear up some abiguity over sub-menu items.

1369: 448: 2778: 2742: 2722: 2662:

Stiki adds an extra space that results in a clumsy appearance of (the newly added) warning messages. A typical example

2153:

The other symptom I've noticed is that the "Back" button does not come into focus or function (it remains greyed out).

2657: 967: 130: 2816: 620:? We typically use that process to onboard requesting users who might already have several *hundred* edits. Thanks, 3150: 2034: 1271:

I'm assuming that Stiki won't be up till after 8am on Monday morning which would be more than 16hours from now? --

3530:

Sure. I'll find some. It was just that I was STiking yesterday and noticed about 10 edits that it would have been

3416:

is mostly in the interpretation, so it would make sense for STiki to escalate if it found warnings for test edits.

2633: 2586: 2327: 1809: 323: 94: 86: 81: 69: 64: 59: 2357:

For me the word "supports" is a bit wishy-washy. STiki actually changes the flow of information to practically

1644:

Most of the time the edit is innocent, but I like to do the search so I feel like I can catch stealth vandalism.

3542:. One thing I learned when doing AfCs is that keeping things as specific as possible is a good idea. Cheers, -- 3104:

now shows the changes more clearly. I thought this would be handy to improve the transparency of the change.

2820:

new line after the heading and yet it is all shown in one box... i.e. it all treated as one line by MediaWiki.

2132: 2094: 353: 869:

explained the matter to me. He explained it better than I just did to you, which is why I've pinged him via

3209: 1082:

I can't connect to the STiki server for some reason today. Is it down for maintenance or just down? --I am

3189: 2942: 2729: 2670: 374:

You can stop these edits appearing by going to Displayed Edits and unchecking Edits by Privileged Users.

112: 3507:

I'm inclined to agree with Noyster on this. L235, can you give an example where uw-nor1 would help but

1755:

I agree with Boomur. I get these edits thrown in quite often and end up clicking pass in most cases. --

1297: 1236: 1092: 1077: 659: 475:

The server doesn't seem to have reserved one of the edits that I was reviewing. When I was being shown

38: 2687:. That was fixed but if you downloaded after that point then it mustn't've been done for all messages. 1972:

Some of the pre-formatted messages have a space before the message, causing them to render like this:

1405:

The STiki workflow means that follow-up vandalism is likely to be passed on to a different STiki user.

793: 2623: 2609: 2518:

Yes. "provides" is good... although... there is a shorter word that means the same thing... "gives".

2509: 2212:

I am often logged in to WP simultaneously on my browser; could this have been causing the behavior?

1815:(I had also already blocked the vandal, although I don't necesarily expect STiki to check for that.) 480: 476: 2042: 1164:

Scheduled maintenance at UPenn took us offline. Still awaiting a response from my local colleague.

829: 3396: 3260: 3197: 3072: 2983: 2911: 2865: 2850: 2799: 2709: 2311: 2243: 2196: 2118: 2083: 2024: 1919: 1838: 1794: 1683: 1669: 1573: 1523: 1503: 1429: 1353: 1324: 1201: 1169: 956: 919: 801: 773: 760: 744: 689: 625: 578: 540: 460: 275: 216: 2683:

Did you download your copy before 15:45 (UTC) on 1 December? This could be the bug discussed as

2438:

I think I'm saying is that STiki involves more than an affordance. To use the first example in

841: 3537: 2725: 2666: 2111: 1614: 435: 393: 334: 2504:

I suggest "provides"... "Implements" is also good. "effectively implements" is superfluous. --

3552: 3476: 3408:

I don't think hz wants to do non-standard messages as such. I think the question relates to

2550: 2477: 2387: 2019:-- A new version has been uploaded under the previous version/filename with the fix. Thanks, 1953: 1904: 1760: 1707: 1628: 1598: 1490: 1455: 1387: 1338: 1276: 1253: 1216: 1128: 1065: 1009: 419: 2842: 2879: 2684: 2619: 2605: 2505: 2306:

and is immediately apparent to those who might drop in to make a duplicate request/report.

2285: 2156:

I'm a little disappointed that a good many reviews were wasted. Any idea what's happening?

2143: 1999: 1142: 1051: 1036: 932:

I don't have any insight into what might cause a STiki session to be become logged-out but

896: 855: 562: 525: 492: 379: 111:

page, where I could see that 66 bytes (blank spaces) had been added, and from there to the

47: 17: 3466:

a lot when using STiki. Could this be added to the list of common AGF messages? Cheers, --

1738:

i think an ideal situation would be having the omission of "numerical" edits simply be an

739:

been down, despite revert rates holding steady to previous numbers. How can we do better?

8: 1812:

in STiki. This seems a bit odd because I had already unselcted "warn offending editor?"

815: 305: 248: 174: 138: 120: 3358:

This is not possible. However, there are a couple of options you may wish to consider.

792:

The template seems to be substituted, but this is an example of what I was thinking of:

3547: 3521: 3471: 3431: 3392: 3381: 3345: 3317: 3256: 3193: 3183: 3130: 3115: 3068: 3048: 3033: 2979: 2907: 2887: 2861: 2846: 2831: 2795: 2754: 2705: 2694: 2641: 2594: 2576: 2523: 2447: 2368: 2307: 2269: 2239: 2217: 2192: 2161: 2114: 2079: 2020: 1939: 1915: 1886: 1834: 1822: 1790: 1679: 1665: 1654: 1569: 1499: 1473: 1466:

What is the error message that you get? That will help Andrew to diagnose the problem.

1425: 1414: 1349: 1320: 1197: 1165: 995: 980: 952: 942: 915: 797: 756: 740: 685: 666: 621: 551: 536: 510: 456: 271: 212: 159: 199: 3496: 3362: 3224: 3166: 2808:

Hi Andrew, I don't think it is a question of one new line or two. I think it is the

2295: 1727: 1610: 1185: 1060:

It also happens when I click on pass at times even though my internet is not slow. --

878: 647: 589: 404: 389: 361: 330: 108: 3461: 3449: 3238: 3142: 2546: 2473: 2383: 2099: 2060: 1949: 1900: 1756: 1703: 1624: 1594: 1483: 1448: 1380: 1334: 1272: 1249: 1212: 1124: 1061: 1005: 674: 415: 3124: 2997: 2972: 2946: 1995: 1138: 1120: 1047: 1032: 971: 892: 851: 558: 521: 502: 488: 444: 375: 46:

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

1535:

Request Block & so on such that Bots/Admin could block User/IP immediately(

1295: 1234: 1110: 1090: 870: 735: 731: 715: 639: 617: 301: 244: 170: 134: 116: 891:

Okay, so it's a bug. Got it (kind of; still need that explanation, though). –

3543: 3517: 3467: 3427: 3421: 3377: 3338: 3313: 3111: 3044: 3029: 2883: 2874:

I think this problem is pretty wide-spread. I can see the problem with both

2827: 2750: 2690: 2637: 2590: 2572: 2519: 2495: 2443: 2421: 2364: 2265: 2213: 2173: 2157: 2139: 1935: 1882: 1869: 1863: 1818: 1650: 1469: 1410: 1375: 991: 976: 938: 933: 866: 780: 506: 484: 155: 3488: 3487:

original research, or if the bod read it somewhere and didn't tell us where

3298:

reverted the edit, I would like STiki to highlight similar edits in future.

3216: 3158: 2291: 1719: 1180: 874: 346: 3391:

warnings, but the vast majority of these will never even be seen. Thanks,

188:

the Wikimedia default back in 2009/2010 when STiki was initially authored.

3134: 1747: 1641:. I normally find a sports stats website or similar that has the answer. 1556: 1537: 784: 719: 711: 670: 1847:

Yes. Not sure what the message should say. Maybe something like this.

2685:#Single space in front of good faith messages causes rendering problems 2545:

Stiki enables, provides for, employs. How do they seem? Or empowers? --

2439: 2401: 441: 1968:

Single space in front of good faith messages causes rendering problems

616:

machinery operates. Would you be willing to participate in a round of

3410:

Knowledge:Template messages/User talk namespace/Multi-level templates

1288: 1227: 1106: 1083: 3085:

Now easier to see the changes made to the good-faith-revert messages

1529:

Knowledge:Administrator_intervention_against_vandalism#User-reported

2569:

Of all the words that ARK suggests, I think I prefer "facilitates".

2491: 2417: 1637:

Hi Paul, In this situation, I normally Google it. e.g. search for

2875: 2746: 850:

Is this a bug, or are IP users now allowed to edit using STiki?

2147: 1987: 1976: 2097:

and I'll be more than happy to work with you further. Best —

1877:

It depends on what the editor's other contributions are like.

1808:

I got a "don't template the regulars" message when reverting

2906:-- New version up, let's see if that fixes things. Thanks, 2322:

How would you characterise STiki's effect on collaboration?

1856:

Leave a specially written message on the user's talk page

2721:

Thanks, that helped, but Stiki still does a lot of this

198:

one (look at the rendering of the version you reverted,

2636:

and tweaked the other words to simplify it slightly.

1179:

Is there an ETA for having the server back online? -

409:. Keeping an account secure is a basic requirement of 3013:

Force people to download the latest version of STiki?

3307: 2563:

I think "confers" kinda works, but is a bit obscure.

584:

lot of material about it, and wish to help. Thanks.

1447:is blocked. Is there any way to fix this? Thanks, 970:(for onlookers, that shows current editing from a 2490:a collaborative approach to reverting vandalism. 1319:-- Back online. More details as my time permits. 2350:a collaborative approach to reverting vandalism. 2338:a collaborative approach to reverting vandalism. 1804:Unnecesary "don't template the regulars message" 1522:I used STiki version 2.1,to warn following user 847:, was using STiki, at least in their summaries. 1119:I think a status indicator should be put up on 520:avoided." Maybe it's not doing that anymore. – 2354:What do people think is the best description? 1862:Start are discussion at a noticeboard such as 2585:O.K. Discussion seems to have stopped. I've 1248:I was right then. It was a stupid idea. :p -- 769:i think the most common rollback message is 1868:Block (if you are and admin), or report at 1859:Start a discussion on the article talk page 1584:'Numerical updates': cases for inspection?! 113:article's Difference between revisions page 1026:How to close STiki if it stops responding? 820:Yesterday, it seems as though an IP user, 455:mobile application would be much cooler). 2936:Requesting permission to use STiki tool 1482:Error: Backend Connection is required. 14: 44:Do not edit the contents of this page. 115:, where all was revealed. Regards, -- 1374:I have gotten into trouble with the 25: 3424:already said that hz uses Twinkle.) 2741:This is very strange. If I look at 2618:Ok. My vote goes to "facilitates". 2589:but happy to discuss further here. 1994:Could you please fix this? Thanks, 23: 2404:of a piece of software is in fact 1948:OK OK Yaris, so we agree on this.. 24: 3572: 3306:(See also feature request T#040, 2396:As indicated in my edit summary, 1853:Revert without a template message 968:Special:Contributions/10.68.16.32 103:Whitespace in Diff Representation 3058: 2960: 2897: 2010: 1986: 1975: 1775:CHANGELOG for 2014-03-25 release 1310: 1156: 702: 599: 29: 3458:I've found myself want to use 1518:Vandalism warnings & block 1442:STiki not working in shared IP 794:User_talk:Tony_Tan_98#Rollback 13: 1: 3509:the unsourced content message 3332:Different messages to vandals 3265:19:48, 31 December 2014 (UTC) 3246:13:48, 31 December 2014 (UTC) 3231:13:36, 31 December 2014 (UTC) 3202:17:22, 30 December 2014 (UTC) 3173:17:16, 30 December 2014 (UTC) 3151:16:51, 30 December 2014 (UTC) 3129:I have recently been granted 3120:18:17, 20 December 2014 (UTC) 3077:03:43, 15 December 2014 (UTC) 3053:13:14, 14 December 2014 (UTC) 3038:12:59, 14 December 2014 (UTC) 3005:23:02, 12 December 2014 (UTC) 2988:21:10, 12 December 2014 (UTC) 2954:17:20, 12 December 2014 (UTC) 2916:20:59, 12 December 2014 (UTC) 2892:09:41, 12 December 2014 (UTC) 2870:15:55, 11 December 2014 (UTC) 2855:21:00, 10 December 2014 (UTC) 2836:17:24, 10 December 2014 (UTC) 2804:16:46, 10 December 2014 (UTC) 2759:09:42, 10 December 2014 (UTC) 2646:13:19, 11 December 2014 (UTC) 2581:19:18, 30 November 2014 (UTC) 2555:20:03, 28 November 2014 (UTC) 2528:09:46, 27 November 2014 (UTC) 2514:22:25, 26 November 2014 (UTC) 2500:14:18, 26 November 2014 (UTC) 2482:12:20, 26 November 2014 (UTC) 2452:10:28, 26 November 2014 (UTC) 2426:10:05, 26 November 2014 (UTC) 2392:19:57, 25 November 2014 (UTC) 2373:19:00, 25 November 2014 (UTC) 2316:16:56, 10 December 2014 (UTC) 2095:Special:EmailUser/MusikAnimal 2053:/0B7RNXFFBKTc3c0tWQVV6bUpyRVU 1958:19:48, 25 November 2014 (UTC) 1944:18:43, 25 November 2014 (UTC) 1924:15:38, 25 November 2014 (UTC) 1909:14:13, 25 November 2014 (UTC) 1891:12:54, 25 November 2014 (UTC) 1843:19:08, 24 November 2014 (UTC) 1827:15:06, 24 November 2014 (UTC) 1765:14:49, 16 November 2014 (UTC) 1578:01:03, 14 November 2014 (UTC) 1548:11:26, 13 November 2014 (UTC) 2734:21:59, 9 December 2014 (UTC) 2714:16:27, 3 December 2014 (UTC) 2699:13:36, 3 December 2014 (UTC) 2675:12:09, 3 December 2014 (UTC) 2628:06:03, 5 December 2014 (UTC) 2614:05:50, 5 December 2014 (UTC) 2599:14:08, 3 December 2014 (UTC) 2300:05:27, 8 December 2014 (UTC) 2274:20:36, 3 December 2014 (UTC) 2248:17:51, 3 December 2014 (UTC) 2222:17:27, 3 December 2014 (UTC) 2201:05:28, 3 December 2014 (UTC) 2166:03:31, 3 December 2014 (UTC) 2123:17:55, 3 December 2014 (UTC) 2106:17:19, 1 December 2014 (UTC) 2088:15:59, 1 December 2014 (UTC) 2067:15:39, 1 December 2014 (UTC) 2029:15:45, 1 December 2014 (UTC) 2004:06:29, 1 December 2014 (UTC) 1751:15:06, 8 November 2014 (UTC) 1734:11:17, 8 November 2014 (UTC) 1712:10:02, 8 November 2014 (UTC) 1688:17:38, 7 November 2014 (UTC) 1674:17:28, 7 November 2014 (UTC) 1659:09:21, 7 November 2014 (UTC) 1633:15:52, 5 November 2014 (UTC) 1619:15:27, 5 November 2014 (UTC) 1603:12:04, 5 November 2014 (UTC) 1508:17:10, 7 November 2014 (UTC) 1493:13:49, 7 November 2014 (UTC) 1478:09:11, 7 November 2014 (UTC) 1458:20:55, 6 November 2014 (UTC) 1434:17:03, 7 November 2014 (UTC) 1419:09:10, 7 November 2014 (UTC) 1390:21:22, 6 November 2014 (UTC) 1358:16:54, 7 November 2014 (UTC) 1343:20:11, 3 November 2014 (UTC) 1329:20:06, 3 November 2014 (UTC) 1305:19:25, 2 November 2014 (UTC) 1281:13:32, 2 November 2014 (UTC) 1258:15:20, 1 November 2014 (UTC) 1244:14:00, 1 November 2014 (UTC) 1221:09:48, 1 November 2014 (UTC) 1206:21:59, 31 October 2014 (UTC) 1191:21:02, 31 October 2014 (UTC) 1174:20:25, 31 October 2014 (UTC) 1147:20:00, 31 October 2014 (UTC) 1133:18:49, 31 October 2014 (UTC) 1115:14:28, 31 October 2014 (UTC) 1100:11:20, 31 October 2014 (UTC) 1070:18:50, 31 October 2014 (UTC) 1056:22:35, 30 October 2014 (UTC) 1041:22:29, 30 October 2014 (UTC) 1014:18:47, 31 October 2014 (UTC) 1000:10:46, 31 October 2014 (UTC) 985:01:27, 31 October 2014 (UTC) 961:16:19, 30 October 2014 (UTC) 947:09:34, 30 October 2014 (UTC) 924:01:36, 30 October 2014 (UTC) 901:17:27, 29 October 2014 (UTC) 883:14:45, 29 October 2014 (UTC) 860:14:39, 29 October 2014 (UTC) 806:20:40, 30 October 2014 (UTC) 788:17:05, 30 October 2014 (UTC) 765:16:35, 30 October 2014 (UTC) 749:16:32, 30 October 2014 (UTC) 723:04:54, 30 October 2014 (UTC) 694:02:03, 30 October 2014 (UTC) 679:18:56, 29 October 2014 (UTC) 652:14:16, 25 October 2014 (UTC) 630:13:51, 24 October 2014 (UTC) 594:10:29, 24 October 2014 (UTC) 567:16:42, 24 October 2014 (UTC) 545:16:22, 24 October 2014 (UTC) 530:16:15, 24 October 2014 (UTC) 515:16:12, 24 October 2014 (UTC) 497:15:45, 24 October 2014 (UTC) 465:16:07, 24 October 2014 (UTC) 449:14:02, 24 October 2014 (UTC) 424:08:39, 21 October 2014 (UTC) 398:13:30, 13 October 2014 (UTC) 384:13:14, 13 October 2014 (UTC) 370:12:52, 13 October 2014 (UTC) 339:12:32, 13 October 2014 (UTC) 7: 3557:19:07, 4 January 2015 (UTC) 3526:13:55, 4 January 2015 (UTC) 3503:10:33, 4 January 2015 (UTC) 3481:04:19, 4 January 2015 (UTC) 3436:21:35, 1 January 2015 (UTC) 3401:20:32, 1 January 2015 (UTC) 3386:12:05, 1 January 2015 (UTC) 3353:05:07, 1 January 2015 (UTC) 3322:11:54, 1 January 2015 (UTC) 1370:Feature Request:3RR caution 310:17:08, 6 October 2014 (UTC) 280:15:09, 6 October 2014 (UTC) 253:14:35, 6 October 2014 (UTC) 221:02:59, 6 October 2014 (UTC) 179:15:25, 5 October 2014 (UTC) 164:15:10, 5 October 2014 (UTC) 143:17:02, 4 October 2014 (UTC) 125:16:52, 4 October 2014 (UTC) 10: 3577: 3098:good-faith-revert messages 2945:anti-vandal tool. Thanks! 2843:Help:Formatting#Paragraphs 1991:Hello, this is a warning. 1980:Hello, this is a warning. 1914:Tracked as T#050. Thanks, 1799:16:11, 25 March 2014 (UTC) 1678:Tracked as T#049. Thanks, 2658:A bug in warning messages 2634:used the word facilitates 638:Thanks a lot. I will try 2978:back-end contributions. 2408:. Alternatives might be 2035:Spacing issue on Mac OSX 481:another edit using STiki 1639:Joe Bloggs goals scored 1524:User talk:125.34.54.177 710:: to me, it seems like 324:Edits by senior editors 2470:effectively implements 2078:troubleshoot? Thanks, 2996:Thank you very much! 2680:Hi Materialscientist. 2587:gone back to "gives", 2566:I still like "gives". 2133:STiki not functioning 42:of past discussions. 3210:Classification query 3190:WP:STiki/leaderboard 2144:Christmas traditions 1300:See what I have done 1239:See what I have done 1095:See what I have done 873:to this discussion. 18:Knowledge talk:STiki 714:would benefit from 447:Ping when replying 345:ever catch them? -- 131:And again (4 bytes) 3553:Ping when replying 3477:Ping when replying 3131:rollback privilege 2440:the linked article 1534:Final Warning: --> 1078:STiki not working? 667:Achievement Hunter 660:Request for Access 471:Edit "reservation" 238:s in the text for 3187: 2726:Materialscientist 2667:Materialscientist 1983:Instead of this: 1546: 368: 100: 99: 54: 53: 48:current talk page 3568: 3555: 3541: 3499: 3494: 3479: 3465: 3453: 3350: 3343: 3243: 3227: 3222: 3181: 3169: 3164: 3147: 3139: 3066: 3062: 3061: 3002: 2976: 2968: 2964: 2963: 2951: 2905: 2901: 2900: 2177: 2102: 2063: 2057: 2018: 2014: 2013: 1990: 1979: 1730: 1725: 1560: 1544: 1543: 1536: 1488: 1453: 1385: 1318: 1314: 1313: 1302: 1292: 1241: 1231: 1188: 1183: 1163: 1160: 1159: 1105:Yep, it's down. 1097: 1087: 846: 845: 826: 778: 772: 706: 705: 614: 606: 603: 602: 555: 408: 366: 360: 358: 351: 109:revision history 78: 56: 55: 33: 32: 26: 3576: 3575: 3571: 3570: 3569: 3567: 3566: 3565: 3551: 3535: 3497: 3490: 3475: 3459: 3456: 3454:to AGF messages 3447: 3346: 3339: 3334: 3239: 3225: 3218: 3212: 3167: 3160: 3149: 3143: 3135: 3127: 3087: 3059: 3057: 3015: 2998: 2970: 2961: 2959: 2947: 2938: 2898: 2896: 2815:Take a look at 2660: 2324: 2288: 2171: 2135: 2100: 2061: 2054: 2052: 2050: 2048: 2046: 2044: 2041: 2037: 2011: 2009: 1981: 1970: 1806: 1777: 1728: 1721: 1586: 1554: 1539: 1538: 1520: 1484: 1463:Hi TheQ Editor, 1449: 1444: 1381: 1372: 1311: 1309: 1301: 1298: 1290: 1240: 1237: 1229: 1186: 1181: 1161: 1157: 1096: 1093: 1085: 1080: 1028: 972:private network 827: 822: 821: 818: 776: 770: 703: 662: 608: 604: 600: 581: 579:Request to join 549: 473: 438: 402: 362: 354: 347: 326: 105: 74: 30: 22: 21: 20: 12: 11: 5: 3574: 3564: 3563: 3562: 3561: 3560: 3559: 3515: 3512: 3455: 3444: 3443: 3442: 3441: 3440: 3439: 3438: 3425: 3417: 3413: 3406: 3375: 3371: 3370: 3369: 3366: 3333: 3330: 3329: 3328: 3327: 3326: 3325: 3324: 3311: 3304: 3301: 3300: 3299: 3295: 3292: 3288: 3285: 3282: 3270: 3269: 3268: 3267: 3249: 3248: 3211: 3208: 3207: 3206: 3205: 3204: 3176: 3175: 3141: 3126: 3123: 3086: 3083: 3082: 3081: 3080: 3079: 3027: 3026: 3023: 3014: 3011: 3010: 3009: 3008: 3007: 2991: 2990: 2937: 2934: 2933: 2932: 2931: 2930: 2929: 2928: 2927: 2926: 2925: 2924: 2923: 2922: 2921: 2920: 2919: 2918: 2825: 2821: 2813: 2786: 2785: 2784: 2783: 2782: 2781: 2770: 2769: 2768: 2767: 2766: 2765: 2719: 2718: 2717: 2716: 2688: 2681: 2659: 2656: 2655: 2654: 2653: 2652: 2651: 2650: 2649: 2648: 2616: 2570: 2567: 2564: 2561: 2543: 2542: 2541: 2540: 2539: 2538: 2537: 2536: 2535: 2534: 2533: 2532: 2531: 2530: 2459: 2458: 2457: 2456: 2455: 2454: 2431: 2430: 2429: 2428: 2352: 2351: 2340: 2339: 2323: 2320: 2319: 2318: 2287: 2284: 2283: 2282: 2281: 2280: 2279: 2278: 2277: 2276: 2255: 2254: 2253: 2252: 2251: 2250: 2236: 2227: 2226: 2225: 2224: 2210: 2204: 2203: 2187: 2186: 2181: 2180: 2134: 2131: 2130: 2129: 2128: 2127: 2126: 2125: 2075: 2036: 2033: 2032: 2031: 1974: 1969: 1966: 1965: 1964: 1963: 1962: 1961: 1960: 1933: 1929: 1928:Thanks Andrew. 1896: 1895: 1894: 1893: 1880: 1879: 1878: 1875: 1874: 1873: 1866: 1860: 1857: 1854: 1805: 1802: 1786: 1785: 1776: 1773: 1772: 1771: 1770: 1769: 1768: 1767: 1699: 1698: 1697: 1696: 1695: 1694: 1693: 1692: 1691: 1690: 1648: 1645: 1642: 1585: 1582: 1581: 1580: 1564: 1563: 1519: 1516: 1515: 1514: 1513: 1512: 1511: 1510: 1467: 1464: 1443: 1440: 1439: 1438: 1437: 1436: 1408: 1407: 1406: 1403: 1399: 1371: 1368: 1367: 1366: 1365: 1364: 1363: 1362: 1361: 1360: 1299: 1269: 1268: 1267: 1266: 1265: 1264: 1263: 1262: 1261: 1260: 1238: 1154: 1153: 1152: 1151: 1150: 1149: 1094: 1079: 1076: 1075: 1074: 1073: 1072: 1027: 1024: 1023: 1022: 1021: 1020: 1019: 1018: 1017: 1016: 987: 930: 929: 928: 927: 926: 906: 905: 904: 903: 886: 885: 824:108.21.111.234 817: 814: 813: 812: 811: 810: 809: 808: 774:rollbackgiven3 728: 727: 726: 725: 697: 696: 661: 658: 657: 656: 655: 654: 633: 632: 580: 577: 576: 575: 574: 573: 572: 571: 570: 569: 472: 469: 468: 467: 437: 436:Web interface? 434: 433: 432: 431: 430: 429: 428: 427: 426: 325: 322: 321: 320: 319: 318: 317: 316: 315: 314: 313: 312: 289: 288: 287: 286: 285: 284: 283: 282: 260: 259: 258: 257: 256: 255: 226: 225: 224: 223: 205: 204: 203: 202: 192: 191: 190: 189: 182: 181: 146: 145: 104: 101: 98: 97: 92: 89: 84: 79: 72: 67: 62: 52: 51: 34: 15: 9: 6: 4: 3: 2: 3573: 3558: 3554: 3549: 3545: 3539: 3538:uw-unsourced1 3534:helpful than 3533: 3529: 3528: 3527: 3523: 3519: 3516: 3513: 3510: 3506: 3505: 3504: 3501: 3495: 3493: 3485: 3484: 3483: 3482: 3478: 3473: 3469: 3463: 3451: 3437: 3433: 3429: 3426: 3423: 3422:User:Hz.tiang 3418: 3414: 3411: 3407: 3404: 3403: 3402: 3398: 3394: 3393:West.andrew.g 3389: 3388: 3387: 3383: 3379: 3376: 3372: 3367: 3364: 3360: 3359: 3357: 3356: 3355: 3354: 3351: 3349: 3344: 3342: 3323: 3319: 3315: 3312: 3309: 3305: 3302: 3296: 3293: 3289: 3286: 3283: 3280: 3279: 3276: 3275: 3274: 3273: 3272: 3271: 3266: 3262: 3258: 3257:West.andrew.g 3253: 3252: 3251: 3250: 3247: 3244: 3242: 3235: 3234: 3233: 3232: 3229: 3223: 3221: 3203: 3199: 3195: 3194:West.andrew.g 3191: 3185: 3184:edit conflict 3180: 3179: 3178: 3177: 3174: 3171: 3165: 3163: 3155: 3154: 3153: 3152: 3148: 3146: 3140: 3138: 3132: 3122: 3121: 3117: 3113: 3109: 3105: 3103: 3099: 3095: 3090: 3078: 3074: 3070: 3069:West.andrew.g 3065: 3056: 3055: 3054: 3050: 3046: 3042: 3041: 3040: 3039: 3035: 3031: 3024: 3021: 3020: 3019: 3006: 3003: 3001: 2995: 2994: 2993: 2992: 2989: 2985: 2981: 2980:West.andrew.g 2974: 2967: 2958: 2957: 2956: 2955: 2952: 2950: 2944: 2917: 2913: 2909: 2908:West.andrew.g 2904: 2895: 2894: 2893: 2889: 2885: 2881: 2877: 2873: 2872: 2871: 2867: 2863: 2862:West.andrew.g 2858: 2857: 2856: 2852: 2848: 2847:West.andrew.g 2844: 2839: 2838: 2837: 2833: 2829: 2826: 2822: 2818: 2814: 2811: 2807: 2806: 2805: 2801: 2797: 2796:West.andrew.g 2792: 2791: 2790: 2789: 2788: 2787: 2779: 2776: 2775: 2774: 2773: 2772: 2771: 2762: 2761: 2760: 2756: 2752: 2748: 2744: 2743:the next edit 2740: 2739: 2738: 2737: 2736: 2735: 2731: 2727: 2723: 2715: 2711: 2707: 2706:West.andrew.g 2702: 2701: 2700: 2696: 2692: 2689: 2686: 2682: 2679: 2678: 2677: 2676: 2672: 2668: 2664: 2647: 2643: 2639: 2635: 2631: 2630: 2629: 2625: 2621: 2617: 2615: 2611: 2607: 2602: 2601: 2600: 2596: 2592: 2588: 2584: 2583: 2582: 2578: 2574: 2571: 2568: 2565: 2562: 2559: 2558: 2557: 2556: 2552: 2548: 2529: 2525: 2521: 2517: 2516: 2515: 2511: 2507: 2503: 2502: 2501: 2497: 2493: 2489: 2485: 2484: 2483: 2479: 2475: 2471: 2467: 2466: 2465: 2464: 2463: 2462: 2461: 2460: 2453: 2449: 2445: 2441: 2437: 2436: 2435: 2434: 2433: 2432: 2427: 2423: 2419: 2415: 2411: 2407: 2403: 2399: 2395: 2394: 2393: 2389: 2385: 2381: 2377: 2376: 2375: 2374: 2370: 2366: 2362: 2360: 2355: 2349: 2345: 2344: 2343: 2337: 2333: 2332: 2331: 2329: 2317: 2313: 2309: 2308:West.andrew.g 2304: 2303: 2302: 2301: 2297: 2293: 2275: 2271: 2267: 2263: 2262: 2261: 2260: 2259: 2258: 2257: 2256: 2249: 2245: 2241: 2240:West.andrew.g 2237: 2233: 2232: 2231: 2230: 2229: 2228: 2223: 2219: 2215: 2211: 2208: 2207: 2206: 2205: 2202: 2198: 2194: 2193:West.andrew.g 2189: 2188: 2183: 2182: 2175: 2170: 2169: 2168: 2167: 2163: 2159: 2154: 2151: 2149: 2145: 2141: 2140:Chemical bond 2124: 2120: 2116: 2115:West.andrew.g 2112: 2109: 2108: 2107: 2104: 2103: 2096: 2091: 2090: 2089: 2085: 2081: 2080:West.andrew.g 2076: 2071: 2070: 2069: 2068: 2065: 2064: 2056: 2030: 2026: 2022: 2021:West.andrew.g 2017: 2008: 2007: 2006: 2005: 2001: 1997: 1992: 1989: 1984: 1978: 1973: 1959: 1955: 1951: 1947: 1946: 1945: 1941: 1937: 1934: 1930: 1927: 1926: 1925: 1921: 1917: 1916:West.andrew.g 1913: 1912: 1911: 1910: 1906: 1902: 1892: 1888: 1884: 1881: 1876: 1871: 1867: 1865: 1861: 1858: 1855: 1852: 1851: 1849: 1848: 1846: 1845: 1844: 1840: 1836: 1835:West.andrew.g 1831: 1830: 1829: 1828: 1824: 1820: 1816: 1813: 1811: 1801: 1800: 1796: 1792: 1791:West.andrew.g 1783: 1782: 1781: 1766: 1762: 1758: 1754: 1753: 1752: 1749: 1745: 1741: 1737: 1736: 1735: 1732: 1726: 1724: 1716: 1715: 1714: 1713: 1709: 1705: 1689: 1685: 1681: 1680:West.andrew.g 1677: 1676: 1675: 1671: 1667: 1666:West.andrew.g 1662: 1661: 1660: 1656: 1652: 1649: 1646: 1643: 1640: 1636: 1635: 1634: 1630: 1626: 1622: 1621: 1620: 1616: 1612: 1607: 1606: 1605: 1604: 1600: 1596: 1591: 1579: 1575: 1571: 1570:West.andrew.g 1566: 1565: 1558: 1553: 1552: 1551: 1549: 1545: 1542: 1530: 1525: 1509: 1505: 1501: 1500:West.andrew.g 1496: 1495: 1494: 1491: 1489: 1487: 1481: 1480: 1479: 1475: 1471: 1468: 1465: 1462: 1461: 1460: 1459: 1456: 1454: 1452: 1435: 1431: 1427: 1426:West.andrew.g 1422: 1421: 1420: 1416: 1412: 1409: 1404: 1400: 1397: 1396: 1394: 1393: 1392: 1391: 1388: 1386: 1384: 1377: 1359: 1355: 1351: 1350:West.andrew.g 1346: 1345: 1344: 1340: 1336: 1333:Thank you! -- 1332: 1331: 1330: 1326: 1322: 1321:West.andrew.g 1317: 1308: 1307: 1306: 1303: 1296: 1294: 1293: 1285: 1284: 1283: 1282: 1278: 1274: 1259: 1255: 1251: 1247: 1246: 1245: 1242: 1235: 1233: 1232: 1224: 1223: 1222: 1218: 1214: 1209: 1208: 1207: 1203: 1199: 1198:West.andrew.g 1194: 1193: 1192: 1189: 1184: 1178: 1177: 1176: 1175: 1171: 1167: 1166:West.andrew.g 1148: 1144: 1140: 1136: 1135: 1134: 1130: 1126: 1122: 1118: 1117: 1116: 1112: 1108: 1104: 1103: 1102: 1101: 1098: 1091: 1089: 1088: 1071: 1067: 1063: 1059: 1058: 1057: 1053: 1049: 1045: 1044: 1043: 1042: 1038: 1034: 1015: 1011: 1007: 1003: 1002: 1001: 997: 993: 988: 986: 982: 978: 973: 969: 964: 963: 962: 958: 954: 953:West.andrew.g 950: 949: 948: 944: 940: 935: 931: 925: 921: 917: 916:West.andrew.g 912: 911: 910: 909: 908: 907: 902: 898: 894: 890: 889: 888: 887: 884: 880: 876: 872: 868: 864: 863: 862: 861: 857: 853: 848: 843: 840: 837: 834: 831: 825: 807: 803: 799: 798:West.andrew.g 795: 791: 790: 789: 786: 782: 775: 768: 767: 766: 762: 758: 757:West.andrew.g 753: 752: 751: 750: 746: 742: 741:West.andrew.g 737: 733: 724: 721: 717: 713: 709: 701: 700: 699: 698: 695: 691: 687: 686:West.andrew.g 683: 682: 681: 680: 676: 672: 668: 653: 649: 645: 641: 637: 636: 635: 634: 631: 627: 623: 622:West.andrew.g 619: 612: 598: 597: 596: 595: 591: 587: 568: 564: 560: 553: 552:West.andrew.g 548: 547: 546: 542: 538: 537:West.andrew.g 533: 532: 531: 527: 523: 518: 517: 516: 512: 508: 504: 501: 500: 499: 498: 494: 490: 486: 482: 478: 466: 462: 458: 457:West.andrew.g 453: 452: 451: 450: 446: 443: 425: 421: 417: 412: 406: 401: 400: 399: 395: 391: 387: 386: 385: 381: 377: 373: 372: 371: 367: 365: 359: 357: 352: 350: 343: 342: 341: 340: 336: 332: 311: 307: 303: 299: 298: 297: 296: 295: 294: 293: 292: 291: 290: 281: 277: 273: 272:West.andrew.g 268: 267: 266: 265: 264: 263: 262: 261: 254: 250: 246: 241: 237: 232: 231: 230: 229: 228: 227: 222: 218: 214: 213:West.andrew.g 209: 208: 207: 206: 200: 196: 195: 194: 193: 186: 185: 184: 183: 180: 176: 172: 168: 167: 166: 165: 161: 157: 153: 150: 144: 140: 136: 133:. Regards, -- 132: 129: 128: 127: 126: 122: 118: 114: 110: 96: 93: 90: 88: 85: 83: 80: 77: 73: 71: 68: 66: 63: 61: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 3531: 3491: 3457: 3347: 3340: 3335: 3240: 3219: 3213: 3161: 3144: 3136: 3128: 3110: 3106: 3096:the page on 3092:When Andrew 3091: 3088: 3063: 3028: 3016: 2999: 2965: 2948: 2939: 2902: 2809: 2720: 2661: 2544: 2487: 2469: 2413: 2409: 2405: 2397: 2379: 2363: 2358: 2356: 2353: 2347: 2341: 2335: 2325: 2289: 2286:Phabricator? 2155: 2152: 2136: 2098: 2059: 2038: 2015: 1993: 1985: 1982: 1971: 1897: 1817: 1814: 1807: 1787: 1778: 1743: 1739: 1722: 1700: 1638: 1611:Ugog Nizdast 1589: 1587: 1540: 1533:Caution: --> 1532:Warning: --> 1521: 1486:ΤheQ Editor 1485: 1451:ΤheQ Editor 1450: 1445: 1383:ΤheQ Editor 1382: 1373: 1315: 1289: 1270: 1228: 1155: 1137:Still down. 1084: 1081: 1029: 849: 838: 832: 819: 729: 707: 663: 582: 474: 439: 410: 405:Jayakumar RG 390:Jayakumar RG 363: 355: 348: 331:Jayakumar RG 327: 239: 235: 154: 151: 147: 106: 75: 43: 37: 3241:Orphan Wiki 2547:Rsrikanth05 2474:Super48paul 2384:Super48paul 2328:this change 2101:MusikAnimal 2062:MusikAnimal 1950:Super48paul 1901:Super48paul 1757:Rsrikanth05 1704:Super48paul 1625:Super48paul 1595:Super48paul 1335:Rsrikanth05 1273:Rsrikanth05 1250:Rsrikanth05 1213:Rsrikanth05 1125:Rsrikanth05 1062:Rsrikanth05 1006:Rsrikanth05 816:IP editing? 416:Rsrikanth05 364:talk to me! 36:This is an 3511:would not? 3405:Hi Andrew, 3363:WP:Twinkle 3192:. Thanks, 3067:. Thanks, 3000:Mediavalia 2973:Mediavalia 2949:Mediavalia 2817:this diff. 2632:O.K. I've 2620:Greenmaven 2606:Greenmaven 2506:Greenmaven 2414:facilitate 2402:affordance 2380:implements 1996:Melonkelon 1932:situation. 1402:vandalism. 1139:Melonkelon 1048:Melonkelon 1033:Melonkelon 893:Epicgenius 852:Epicgenius 796:. Thanks, 559:Epicgenius 522:Epicgenius 503:Epicgenius 489:Epicgenius 376:Melonkelon 95:Archive 25 87:Archive 20 82:Archive 19 76:Archive 18 70:Archive 17 65:Archive 16 60:Archive 15 3102:this diff 2410:allow for 2326:I notice 1810:this edit 477:this edit 302:Technopat 245:Technopat 171:Technopat 135:Technopat 117:Technopat 3518:Yaris678 3428:Yaris678 3378:Yaris678 3361:Install 3314:Yaris678 3137:FrankBoy 3112:Yaris678 3089:Hi All, 3045:HGilbert 3030:Yaris678 2884:Yaris678 2828:Yaris678 2751:Yaris678 2691:Yaris678 2638:Yaris678 2591:Yaris678 2573:Yaris678 2520:Yaris678 2444:Yaris678 2365:Yaris678 2348:supports 2266:HGilbert 2214:HGilbert 2174:Hgilbert 2158:HGilbert 1936:Yaris678 1883:Yaris678 1819:Yaris678 1651:Yaris678 1470:Yaris678 1411:Yaris678 1121:WP:Stiki 992:Johnuniq 977:Johnuniq 939:Johnuniq 867:Johnuniq 836:contribs 708:Not sure 507:Onel5969 485:Onel5969 156:Yaris678 3492:Noyster 3462:Uw-nor1 3450:Uw-nor1 3220:Noyster 3215:matter? 3162:Noyster 3125:Public? 3094:updated 2880:Flyer22 2747:newline 2406:support 2359:enforce 2292:APerson 2045:.google 1723:Noyster 1590:updates 1541:!dea4u 1182:Cwobeel 875:Flyer22 871:WP:Echo 736:WP:CVUA 732:WP:CVUA 716:WP:CVUA 644:Ehudzel 640:WP:CVUA 618:WP:CVUA 611:Ehudzel 586:Ehudzel 39:archive 3498:(talk) 3226:(talk) 3168:(talk) 3145:(Buzz) 2749:code. 2488:offers 2486:STiki 2346:STiki 2334:STiki 2148:Phylum 2146:, and 1870:WP:AIV 1864:WP:ANI 1748:Boomur 1740:option 1729:(talk) 1557:!dea4u 1376:WP:3RR 1187:(talk) 975:used. 934:WP:VPT 785:Boomur 781:WP:RBK 720:Boomur 712:EoRdE6 671:EoRdE6 445:(talk) 3308:above 3157:queue 2943:Lupin 2336:gives 2330:from 2296:talk! 2055:/view 2049:/file 2043:drive 842:WHOIS 442:Chess 349:Mdann 16:< 3548:talk 3544:L235 3532:more 3522:talk 3472:talk 3468:L235 3446:Add 3432:talk 3397:talk 3382:talk 3374:you. 3348:zec! 3318:talk 3261:talk 3198:talk 3116:talk 3073:talk 3064:Done 3049:talk 3034:talk 2984:talk 2966:Done 2912:talk 2903:Done 2888:talk 2878:and 2876:Widr 2866:talk 2851:talk 2832:talk 2810:type 2800:talk 2755:talk 2730:talk 2710:talk 2695:talk 2671:talk 2642:talk 2624:talk 2610:talk 2595:talk 2577:talk 2551:talk 2524:talk 2510:talk 2496:talk 2478:talk 2468:Or: 2448:talk 2422:talk 2398:give 2388:talk 2369:talk 2312:talk 2270:talk 2244:talk 2218:talk 2197:talk 2162:talk 2119:talk 2084:talk 2047:.com 2025:talk 2016:Done 2000:talk 1954:talk 1940:talk 1920:talk 1905:talk 1887:talk 1839:talk 1823:talk 1795:talk 1761:talk 1744:only 1708:talk 1684:talk 1670:talk 1655:talk 1629:talk 1615:talk 1599:talk 1574:talk 1504:talk 1474:talk 1430:talk 1415:talk 1354:talk 1339:talk 1325:talk 1316:Done 1291:k6ka 1277:talk 1254:talk 1230:k6ka 1217:talk 1202:talk 1170:talk 1143:talk 1129:talk 1123:. -- 1111:talk 1107:Widr 1086:k6ka 1066:talk 1052:talk 1037:talk 1010:talk 996:talk 981:talk 957:talk 943:talk 920:talk 897:talk 879:talk 856:talk 830:talk 802:talk 783:! ~ 761:talk 745:talk 690:talk 675:talk 648:talk 626:talk 590:talk 563:talk 541:talk 526:talk 511:talk 493:talk 461:talk 420:talk 394:talk 380:talk 335:talk 306:talk 276:talk 249:talk 217:talk 175:talk 160:talk 139:talk 121:talk 3341:hey 2969:-- 2824:it. 2492:ARK 2472:?! 2418:ARK 2412:or 2382:?! 2378:Or 2342:to 607:-- 483:by 479:, 411:ALL 3550:) 3540:}} 3536:{{ 3524:) 3500:, 3489:: 3474:) 3464:}} 3460:{{ 3452:}} 3448:{{ 3434:) 3399:) 3384:) 3320:) 3263:) 3228:, 3217:: 3200:) 3170:, 3159:: 3118:) 3075:) 3051:) 3036:) 2986:) 2914:) 2890:) 2868:) 2853:) 2834:) 2802:) 2757:) 2732:) 2712:) 2697:) 2673:) 2665:. 2644:) 2626:) 2612:) 2597:) 2579:) 2553:) 2526:) 2512:) 2498:) 2480:) 2450:) 2424:) 2416:. 2390:) 2371:) 2314:) 2298:) 2272:) 2246:) 2220:) 2199:) 2164:) 2150:) 2142:, 2121:) 2086:) 2051:/d 2027:) 2002:) 1956:) 1942:) 1922:) 1907:) 1889:) 1841:) 1825:) 1797:) 1763:) 1731:, 1720:: 1710:) 1686:) 1672:) 1657:) 1631:) 1617:) 1601:) 1576:) 1550:) 1506:) 1476:) 1432:) 1417:) 1356:) 1341:) 1327:) 1279:) 1256:) 1219:) 1211:-- 1204:) 1172:) 1145:) 1131:) 1113:) 1068:) 1054:) 1039:) 1012:) 998:) 983:) 959:) 945:) 922:) 899:) 881:) 858:) 804:) 777:}} 771:{{ 763:) 747:) 692:) 677:) 669:) 650:) 642:. 628:) 592:) 565:) 543:) 528:) 513:) 495:) 463:) 422:) 414:-- 396:) 382:) 356:52 337:) 308:) 278:) 251:) 219:) 201:). 177:) 162:) 141:) 123:) 91:→ 3546:( 3520:( 3470:( 3430:( 3412:. 3395:( 3380:( 3316:( 3310:) 3259:( 3196:( 3186:) 3182:( 3114:( 3071:( 3047:( 3032:( 2982:( 2975:: 2971:@ 2910:( 2886:( 2864:( 2849:( 2830:( 2798:( 2753:( 2728:( 2708:( 2693:( 2669:( 2640:( 2622:( 2608:( 2593:( 2575:( 2549:( 2522:( 2508:( 2494:( 2476:( 2446:( 2420:( 2386:( 2367:( 2310:( 2294:( 2268:( 2242:( 2216:( 2195:( 2176:: 2172:@ 2160:( 2117:( 2082:( 2074:. 2023:( 1998:( 1952:( 1938:( 1918:( 1903:( 1885:( 1872:. 1837:( 1821:( 1793:( 1759:( 1706:( 1682:( 1668:( 1653:( 1627:( 1613:( 1609:- 1597:( 1572:( 1559:: 1555:@ 1502:( 1472:( 1428:( 1413:( 1352:( 1337:( 1323:( 1275:( 1252:( 1215:( 1200:( 1168:( 1162:C 1141:( 1127:( 1109:( 1064:( 1050:( 1035:( 1008:( 994:( 979:( 955:( 941:( 918:( 895:( 877:( 854:( 844:) 839:· 833:· 828:( 800:( 759:( 743:( 688:( 673:( 665:( 646:( 624:( 613:: 609:@ 605:C 588:( 561:( 554:: 550:@ 539:( 524:( 509:( 491:( 459:( 418:( 407:: 403:@ 392:( 378:( 333:( 304:( 274:( 247:( 240:E 236:A 215:( 173:( 158:( 137:( 119:( 50:.

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

Knowledge

talk:STiki/Archive 18 - Knowledge

Index