User talk:West.andrew.g/Archive 3

1271:: "Sorting by the criteria requested by Jimbo, or by vandalism risk, are new ideas that I agree would be very useful. I've designed a rough framework to accomplish all this in JavaScript that would act as a fairly transparent replacement for the standard watchlist functionality. To get the vandalism risk, we would need to have West.andrew.g provide an API to query the STiki database, which stores the scores for all three rating engines, including User:ClueBot NG. While this sounds like a fun thing to do, I'm consumed at the moment rewriting Twinkle before HTML5 gets turned back on and kills it. Perhaps Andrew would be willing to work on the API in the meantime. If Andrew doesn't have time, we could setup our own API server somewhere that would query the STiki database on behalf of clients. If any other developers want to start tackling this, let me know and I'll send you my rather rough notes. I'm a bit concerned by how dependent we are becoming on using non-WMF servers and software to manage the project. When ClueBot NG went down for a weeks earlier this year, it was a major blow to vandalism prevention. If Cobi or Andrew aren't around when there's a problem, we can get into a real bind. We are also so dependent on user scripts like Twinkle that whenever something breaks them, productivity comes to a crashing halt. The MediaWiki developers don't test compatibility with user scripts before deploying changes, as we know all too well. However, we need to keep moving forward and a smart watchlist seems like the next logical step to improving article quality. I'm sure we will find another dozen features to add to it once something is in place." pasted by 1570:

how to identify vandalism and then allow them to practice, and eventually move on to real diffs. (Also, any or all of this could be on Knowledge). User ranking would be rated on their level of agreement with other editors and with gold standard diffs. Users who significantly deviated from either would go lower in the rankings. That algorithm is a harder problem beyond my background, but I'm sure game devs use them all the time. The 'incentive' to this general idea, would be the rich graphic element, the rush of getting to play judge about edits (informed judge), web-based convenience, the game/storyline element, and the hivemind element (3/4 or 4/5 agreement required). I agree this idea is less further along then the interactive tutorial. It's just another game-related application. Advertising for the game would hopefully happen from press. I don't know how much zooniverse advertises, but the game is wildly popular. Of course, people get to explore galaxies, but getting to play God/Editor is appealing to many (as we know). An alternate focus may be just on getting broader adoption for STiki. That's not as exciting in the new-project department, but it may be much more fruitful. Maybe that's the more pragmatic focus to have now.

1555:

if random "users" edits were streamlined into a single master "STiki" account -- seems to be a loss of accountability there. STiki could trivially be implemented as a web applet. But isn't your suggestion just basically lowering the threshold for becoming a STiki user by eliminating the "download" and "create a username on Knowledge" steps? Why would anyone play this game (who wouldn't already register/download)? Wouldn't there need to be some kind of incentive? Of course, we could have users "climb the ladder" by ranking them based on revert-count -- but this seems to encourage over-zealous reverting and edit-count-itis (and would require an account to track persistently?). Plus, there would need to be advertising to get anyone to visit this game in the first place. Not meaning to beat down your idea -- but this seems to suffer from several challenges that don't seem to affect your other proposal. Thanks,

1130:

the younger side, and might be running into some real life changes that might make it harder to keep up. Pure speculation, (and a further nod to their remarkable aptitude anyway), but it might be good reason to try and integrate some of these projects somewhere more central, toolserver, the WMF, WikiProject Vandalism, etc. It's both a wonder and a terror that the primary anti-vandalism method on the world's largest encyclopedia and 5th most popular website is run by two college kids on their home computer! Crazy! (but also very cool). It's not like there aren't layers of redundancy between the other anti-vandal programs (Huggle and STiki) in particular, as well as regular recent changes patrollers, but if we're going to move away from that manual model and crack the vandalism nut for good, it has to be a consistent machine-learning tool.

1536:

rate whether they are harmful (definitely, maybe, not sure). Then take 4/5 ratings and a) feed those to the top of the STiki queue; or b) revert them under some approved 'game' account. You could possibly have users go through a training mode before their entries are counted, and you could weight entries based on past performance (agreement with the group, or gold standard placements). It would be somewhat similar to STiki, except gamified, and web-hosted. The other half of any great code is getting people to use it. This could be a neat project, and it has an academic component in the vein of

1054:

CBNG neural network score, or STiki metadata score (or both) next to each watchlist edit. Perhaps it would color code edits by reliability, or flag them after a certain threshold. Theoretically, users could even set their own threshold, either globally or for individual articles. I have no idea what it would take to implement this, but as long as there was full access to the CBNG/STiki servers (which might require moving them somewhere more robust) then every edit could get scored in this way. I mentioned you at the discussion, since this is your territory. Cheers!

379:, of which I am the author. The tool also places warnings. The reason it reported a level-1-vandalism warning was because that there were no other recent *vandalism* warnings on the page. Had there been a recent level-4-vandalism (or 4im), it would have reported to AIV. However, "blanking" and "unsourced content" warnings could be somewhat orthogonal issues to vandalism (esp. when you consider the entire suite of escalating warnings) -- so the tool assumes good faith. This has been discussed before at 1589: 641: 1770: 31: 1244:

poli-sci-econ studies. But Knowledge has brought be back to my roots as an editor and dilettante and idea networker. One of my great strengths (and perhaps weaknesses) is quickly acquiring a conversational level of intelligence with complex topics, without (necessarily) mastering them. But I'm getting slightly better at the mastery side over time. Anyway, I read and write and research and discourse, those are my areas of expertise.

1118:

but has some fresh rules to keep things interesting. For example, there are some foreign language edits which must be scored, and you are allowed to use features derived from "future" data. Not all this is completely relevant to the detection of "fresh" vandalism on en.wikipedia -- but Martin Potthast also outsourced some fresh en.wikipedia corpus tags -- which can help refine everyone's techniques.

461: 843:. Berkman at Harvard is trying to do a study and wants to post survey invites to 40,000 user talk pages. Needless to say, it's facing a bit of resistance. I think you might be able to offer some insight from an academic and technical perspective, particularly with the experience you've gained from working with the community over the last year. Cheers, 1701:, as it describes there, the reports are not perfectly accurate. Generally the reports are correct (at the time indicated on the report), but the server may have fixed the issue, or there could some anomaly. If it bothers you that it is showing up in "What links here", feel free to delete the report from the page. Thanks, 1436:-- Looking at both practical and academic anti-vandalism progress over the last year. On the practical side, this includes the evolution of the STiki tool, the inclusion of third-party queues (such as ClueBot NG), and recent proposals to integrate anti-vandalism algorithms into "pending changes" and/or "smart watchlists." 1395:. It would be nice to use a longer POST request for a big watchlist, but we could just split up the requests into chunks for now. There is also a security risk that if your server is hacked, it could be used to run evil JavaScript directly on Knowledge as any user who is using the smart watchlist feature. A 1742:

The link works fine on my personal machine. The system just uses the URLs the way the Knowledge database stores them. The "start a download" bit doesn't bother the system at all: there are many many PDF, DOC, ZIP, etc. links on Knowledge that are handled in the same way. No worries, and nothing about

1554:

Is the Zooniverse link correct? Seems like some standard SOE content at that destination. I think the game is a fine idea, but there are some implementation concerns. Some administrators did not not like the idea of new/unregistered editors having access to STiki. I can only imagine what would happen

1482:

Looking at your edit again, it does appear to be a good-faith one, and I apologize. Something about the connotation of the word "lame" and the fact the left-half of that HTML comment wasn't immediately apparent motivated me to pull the trigger. STiki does not have "false positives", but its users can

1165:

I could crank up STiki's accuracy considerably given some time (remember, its original concept was to use only *metadata*). I just really hadn't worried about this since the CBNG folks had a fine general-purpose system and we were interfacing well. I would change STiki (the algorithm) considerably if

1117:

I don't think its a secret. I could have a "real" job and be out-earning my graduate stipend considerably, but a little bit of travel now and then makes the long hours a bit more worth it (and the papers still have to get written, and accepted!). PAN is a competition again (I didn't enter last year),

1087:

Yes, the suggestion that you/Jimbo put forth seems to be a quite reasonable one. If it can gain community consensus, it should be a quite simple interfacing matter with the devs. Score one for my support, as an opt-in extension, at minimum. STIki already writes its scores to an IRC feed, and it would

1081:

The latter should benefit STiki, as it will allow me to improve STiki's *algorithm*, and not just the GUI tool (which has received much of the recent attention). This seems particularly important. CBNG has been offline for 1 week+ now, and if Cobi continues to be inactive, I could even turn the STiki

816:

I see what you are seeing, but this is very difficult to explain. In almost 50,000 other reverts this behavior has never been reported -- and there is dedicated logic in my code to keep it from happening. I wonder if something very funky didn't hiccup on Knowledge's side (race conditions come to mind

768:

Hi there. First, the "correct" casing is "STiki" which originally stood for "(S)patio-(T)emporal analysis over W(iki)pedia." The software has expanded a good bit from those origins, though, so the acronymic nature is now downplayed. Second, I'm all for encouraging use of the tool -- but wouldn't want

527:

To be honest, I used a tool to locate your unconstructive edit and the message I placed was according to a template format. Such warnings intend to start out "polite" so that newcomers are not turned away. However, subsequent vandalisms will earn one increasingly stern messages. I noticed you damaged

273:

using ]", uncheck "Warn Offending Editor?", and click "Vandalism". This will preform the revert without prejudice, allow you to leave a manual warning for the editor using Twinkle (if needed), and most importantly, train the STiki classifier that this was a problematic edit. For the case of attention

1569:

Sorry, .org not .com. The accountability issue is interesting and would involve a less xenophobic mindset. As a tradeoff for using registered editors, the appeal of the game would be its moderation approach. Instead of 1 qualified user making changes, It would have a tutorial to both teach users

1141:

I have been poking my head in over at the CBNG talk page and CBNG IRC just with the hopes of getting their IRC feed restarted (now irrelevant seeing as how the whole bot is down). Not sure what's really going on -- but we know that there exist code which works. If the only problem here is a reliable

798:

I do recall something about toast, but I can't see that that user did anything deserving a revert... and even had they done so (or I thought that they had done so) then surely there ought to have been a revert done at the same time, not just a warning? Any ideas? This seems like more than user error

750:

Hi Andrew, Been a wee while since I've used Stiki (sorry, not sure of CaSiNg) but I'm going to take it out for a wee whirl now, after all it is Saturday night (!) but something just came to my mind... how about a Stiki Race? First to revert 1000 vandalism cases wins, or something of that nature. And

681:

In the meanwhile, I encourage STiki users to switch to the "metadata" queue, which is actively processing/en-queuing fresh edits. You are much more likely to find vandalism in this stack. I also realize, that due to to the CBNG-queue being down, that STiki may take a rather lengthy period of time to

1446:

I'd encourage my supporters to visit the Wikimania site (it can be done under unified login) and indicate your interest in these presentations (only if you feel so inclined). Though I realize few (if any) of you will be in Haifa in August -- you can still benefit. There are plans to tape/stream the

1129:

Concerning about Cobi and CBNG. Have you tried Crispy? That bot does way too much work to be hosted and managed completely externally, even though those guys seem like two of the more competent coders I've run across on the entire project. Not that this is a matter at all, but I think they're on

1535:

I had an idea, which in general terms may sound startlingly like Knowledge but hear it out. Create a website with a catchy name, allow people to register, create a compelling narrative that they are 'guardians of the encyclopedia' or 'protectors of knowledge', present them with diffs, ask them to

1053:

about how he could a) see if he missed anything on his watchlist and b) know which watchlisted edits were more likely to be vandalism. The second part seems like an ideal project for CBNG or STiki, as part of a .js tool that I thought you might have an idea about or interest in. It could add the

594:

Yes, WikiMania is on my radar. I've applied for a scholarship to attend (and will present if received). WikiMania doesn't publish proceedings and is a bit "non-academic" -- so its a tough sell for those who usually reimburse my academic travels. An early version of STiki was presented at WikiMania

1068:

on Friday (more details coming soon!). I also got a partial scholarship to, and will be attending, WikiMania in Israel in the Fall. I plan to write up presentation proposals for that in the coming days (I anticipate one will focus on STiki and anti-vandalism progress over the past year: CBNG, the

616:

Ask Jimbo to write a letter to your funding committee. Maybe a nod from the man himself will turn it over. Heck, maybe the Foundation has funds. I still think widespread use of CBNG combined with STiki and perhaps integration of Pending Changes could be a remarkable combination. If it refines

357:

Thanks for being on top of the further vandalism by User 146.243.4.157. FYI -- the IP had just received a final warning, a bit before your warning (at a much lower level). I would encourage you, when you see vandalism and the user has a very recent final warning, to seek to have them blocked --

246:

So you are proposing two new buttons, a "good faith -- revert" and a "good faith -- tag"? The revert case is pretty straightforward (and something I'm not opposed to), but how do you think the "tag" case should be handled? Tagging the article directly might not be the greatest idea, and encourage

167:

I'm researching how other bots revert vandalism. My AVBOT uses regular expresions and some metadata analysis to detect bad faith edits, but it is not enough. I want to learn about classifiers and machine learning and use Knowledge like a big "automatic" corpus (for example analysing trusted users

148:

I guess my question is, "what are you trying to achieve?" You've done a quite thorough job over at your anti-vandalism census. Are you eventually hoping to eventually build a superior bot? I have lots of ideas about all types of things -- but I'd like to know what direction you are interested in.

1466:

Hello, I recently received a message from you regarding an edit of mine that came up in your STiki results as potential vandalism. I wanted to report this false positive as a portrayal in a feature film is certainly not vandalism. I will be undoing your edit but applaud your in your constructive

1719:

It doesn't bother me at all. I just checked the link out of curiosity. It is a slightly odd url because it does not open a page but starts a download, at least in Chrome. So I wondered a) is the script getting thrown off by the oddball link, and then b) should I have coded it some other way?

946:

The context: there are periodic discussions about perceived trends and issues of concern at Knowledge that suffer from being largely opinion-based. Without a 'dashboard' of thoughtful metrics, that discussion will remain opinion-based, and periodically divisive. But if a set of metrics can be

942:

Is it currently possible to extract from existing Knowledge systems (only English Knowledge) statistics on, for example, the total number of pages, contributors, edits, reverts, admin requests, admin interventions by type, etc? If that is not possible, based on your experience, would it be an

214:

I've found Stiki quite good fun. However, in my view it really needs an "otherwise needs attention" button, for edits that are not vandalism but are otherwise problematic. This button would leave a note of the edits somewhere for further review. Even better, there could be two "needs attention

1505:

A discussion about improving the help documentation inspired an idea--Knowledge tutorials would be best if they were interactive and immersive. The thought of a learning-teaching game came up, one based on a real interface with realistic 'missions'. Would you be interested in providing some

1308:

On (next) Monday I'll be in a position to comment on this and start thinking about API improvements. As a thread with Ocassi over at STiki:Talk describes, I am overwhelmed with work deadlines right now. Please don't interpret my silence between now and then as any sign of ill-will. Thanks,

1153:

As for STiki replacing CBNG as the logic bot, I still don't understand the relative accuracy/efficiency between them. Crispy seemed to thing neural networks under proper tutelage and tinkerage were the way to go, but just hearing him describe CGNB's workings made it seem like the delicate

215:

buttons" - one of which would revert the edits, one of which wouldn't. At present I'm ignoring most stuff as "innocent", while the more egregious things I'm sorting out manually... I don't really like calling either "innocent". Or maybe you could just rename the button to "not vandalism"?

1243:

Frankly, my real world expertise is absorbing information and presenting arguments across different fields. I'm a bit of a generalist, or as they politely say in college, pre-law. But I didn't go to law school (at least not yet) and spent some years teaching (and learning) outside of my

1343:. This format will make it fast and easy to lookup scores using JavaScript's native ability to hash the property names for an object. You might need to check the max JSON size supported on your server and either increase it or limit the number of revids in a single request. 682:

load/initialize. I apologize. Fixes in the near future will allow me to adjust the "default" queue on the server to circumvent such issues. Look for these changes in a couple weeks time -- I am quite bogged down at current trying to prepare some academic work for

1442:-- This is a queue which is in development for STiki, targeting external link spam. The theoretical work is largely complete (and in submission to WikiSym 2011), and I'm currently working (with my co-authors) to leverage the technique in a live/online fashion. 1399:

for this, but it's not implemented by any browsers currently, so forget that. Nevertheless, we could use this technique in the short-term to get the smart watchlist gadget developed. In parallel, we should figure out a long-term solution that is to everyone's

1199:

Off-hand, if you ever want a reader or copy-editor or non-CS assist, I'd love to look at something you're working on. Also, i'm about 20 min outside of Penn, which would have been old stomping grounds for me, if I was a) old and b) went much into the city.

528:

a second article (which I have since fixed). However, since you seem to have taken my first warning to heart -- I won't ding you again. Hopefully you will become a constructive contributor, or at minimum, not introduce more damaging revisions. Thanks,

725:

Err, not so fast. ClueBot is down again. I just suggest users play things by ear. If the ClueBot queue is showing poor performance, the feeds are probably down, and you should transition over to the STiki metadata queue in the meantime. Thanks,

617:

CBNG and your metadata, it will only get more powerful. Seems like a no-brainer why they would want to fund it. Vandalism is every Wiki's problem, and if there's a scalable solution here, it's big freakin news. Anyway, I'm a fan.

1506:

feedback or helping work on it, or know some editors who might? The idea is just getting started and any assistance with the help/policy side, the experienced-editor side, or the coding/game-making side would be great. Cheers,

769:

one to encourage anyone to be too aggressive in the hopes of winning some "race". Perhaps when real-life settles down in the near future I should award my most prolific users with barnstars as a token of appreciation. Thanks,

247:

tagging for minor issues (which is discouraged). Writing "tagged edits" to another location might generate little exposure -- and be the moral equivalent of ignoring them. I'd like to hear your thoughts on the matter. Thanks,

498:

Was your message automated? Because if it wasn't, it was polite and I commend you for it. I Know that may seem silly but when people troll the Mods sometimes have to be real squirmy about it. Thank you for being human :3

1346:

Ideally, I would like a single number that is a combination of the STiki and CBNG scores. I haven't found WikiTrust to be terribly useful myself, but perhaps a really high score from them would be good to factor in.

124:

Hi Andrew, thanks for adding your paper to the anti-vandalism bot census, I have read it and it is very interesting (but I have to learn a bit about classifiers). I'm working in some Knowledge charts, specially this

673:

being completely offline. Bot service has since been restored. However, the IRC feeds on which STiki depends to enqueue scores have not yet been restarted. I have raised this as an issue with the developers (see

840: 1384:. Even supporting IE8 would be difficult because I don't think I could use jQuery to invoke the partial implementation. Nevertheless, most power watchlist users use Firefox or Chrome anyway. 1743:

the link format is too unusual compared to others that are handled just fine. I'm writing this off as an a case where the link's server might have had a split-second hiccup. Thanks,

899:

Some history TA tried to prove Knowledge was a minefield of misinformation by adding some. Editor Arthena caught it in under 30 minutes using STiki. Reddit picked up the story.

105:

Sorry about that... I had been on Stiki for a while and got sort of tired of honestly looking for vandalism so my judgement got kind of hazy... won't happen again.... :) Cheers...

1650:

At current it only actively processes English Knowledge edits. However, it would be straightforward to port a version to any MediaWiki site, given that they share an API. Thanks,

887: 1002:

I have to have a look and play. I've never had reason to concern myself with this side of Knowledge before. But thank you so much for your prompt and helpful reply. Regards —

984:, which basically allows queries to be run against the live Wiki-* database. Is this what you were looking for, is your proposal in some way distinct from this? Thanks, 1632: 358:

rather then give them a reduced warning. If you have thoughts, you can respond here -- I will watch your page for a bit. Many thanks for your anti-vandal efforts.--

908: 1335:

is a good start, but it could use some more features. It will be more efficient to query multiple revids at the same time, much like the MediaWiki API supports with

1177:

If you don't mind, I'll repost the relevant pieces on Jimbo's talk page, and maybe throw up a Village Pump Technical proposal or a note at WikiProject Userscripts.

817:-- or a weird edit conflict condition). I am not going to let this trouble me unless is happens again -- but if it does, report it and I'll start digging. Thanks, 412:

edit to AIV reporting a vandal. In the edit summary it appears that it tried to link ] instead of excluding the colon. Just thought you'd like to know about this.

296:

Perhaps it could tag the talk page? It would be reasonably easy to develop a few boilerplate messages (as well as a custom one) - indeed we already have ones like

229: 274:

needed, either fix it yourself, tag it, leave the editor a note, or click "Pass" and hope that the next STiki user is better equipped to deal with the problem. —

206: 440: 1425:

Hello, everyone. As a bit of a PSA, I'd like to announce that recent Knowledge research (and STiki in particular) figures heavily into my two submissions to

1659: 1016: 993: 735: 712: 1492: 1318: 283: 1414: 1034: 881: 826: 778: 256: 392: 1606: 654: 409: 325: 316:

and so on... I'm pretty sure at this time writing to a log somewhere will indeed end up with a very large list, but then the wiki is never finished ;)

1752: 1729: 1710: 695: 537: 483: 452: 269:

STiki can already do all this. For the case of a non-vandalism revert, change the edit summary on the bottom left as follows: "Reverted edit(s) by ]

1574: 1564: 1275: 1248: 1226: 1204: 1097: 926: 626: 611: 177: 158: 1106:

Australia, Amsterdam, Israel. Surely the CS grad programs keep this little perk a secret. PAN should be exciting, is it a full competition again?

980:

in particular). It might not be the convenient "dashboard" display you describe -- but the raw data is out there. Most of these tools build on the

596: 237:

Hi Egg Centric, and thanks for your use of my tool. There has been a lot of discussion along these lines in the past, with a lot of mixed feelings.

443:-- a fix was rolled out on Jan. 31. If your version is more recent than that, let me know. Regardless, thank you for your use of my tool. Thanks, 1456: 808: 1524: 1166:

it needed to do something like this. Absent that, CBNG is *trivial* to replicate if Cobi/Crispy disappear forever, I have their source code!!

1391:. This would work in all browsers and only requires a small PHP code change on your end. This method only supports HTTP GET requests, which 703:

This feed came back up today! (Let's just hope it sticks around). Assuming that holds true, users can resume using the CBNG queue. Thanks,

1356: 1069:

CLEF competition, etc.) -- I'll put a pointer to them here when they are done. Some email anti-spam work is keeping me busy right now for

947:

agreed on and measured to offer a snapshot of what actually occurs here, such discussions would at least be grounded in cold, hard facts.

218:

Gosh, just realised that reads as a list of demands! It's not supposed to be... it's just my thoughts. Thanks so much for your good work!

129:(updated every hour). You can see the performance of several anti-vandalism tools. Surprisingly, about a half of reverts are classify in 1476: 575:

No idea if you're planning on it, but since STiki has come a long way in the past year, just wanted to pass on this call for WikiMania:

678:) -- but I am yet to receive a response. Perhaps some others can pile on over at that talk page to see if we can't make some traction. 1642: 1288: 683: 661: 347: 1300: 380: 1595: 1588: 1510: 1602: 964: 786: 1682:. The link is not really dead, but launches download of the PDF document. I don't know if there is a better way to handle it. 847: 760: 1617: 1058: 1679: 563: 519: 367: 1628: 1420: 1691: 1517: 950:

If you are the wrong guy to talk to about this, maybe you know where I could ask that question more usefully. Regards —

669:

As you may have noticed, the "ClueBot NG" queue has not been updated in some time. Initially, this was the result of the

866: 431: 1828: 1468: 588: 543:

I plan to do so, good sir. I am hoping I'll get into a Physics college course and contribute to science pages here :3

114: 89: 1820: 1815: 1803: 1798: 194:

actions as the basis for corpus labelling (revert by trusted users). A good software package for machine-learning is

81: 76: 64: 59: 142: 1439: 1548: 333: 1544:. Note, this is not related to the game I've been working at, but it is in the same arena. What do you think? 1392: 1088:

be simple to transfer the Java code onto a Wikimedia server to give everyone some sense of reliability. Thanks,

1499: 1433: 1326: 675: 559: 515: 1675: 1373: 465: 413: 198:-- which makes feature selection one's main responsibility, rather than understanding the complex algorithms. 1461: 1268: 1050: 338:

Cluebot sometimes screws up, but looking at that IP's contribution history, the AIV report was spot-on. --

1777: 1698: 1498: 974:. It seems that many of the counts you describe exist in some form on that page (I'd like to highlight 38: 1748: 1706: 1655: 1560: 1488: 1452: 1314: 1222: 1093: 989: 922: 877: 822: 792: 774: 731: 708: 691: 647: 640: 607: 533: 448: 388: 252: 154: 834: 1786: 1622: 1044: 1010: 958: 47: 17: 110: 1472: 1410: 1352: 1296: 279: 1030: 862: 804: 756: 321: 225: 939:

Not sure you are the right guy to ask, but I'll risk the shoulder-shrug and "WTF" response.

1638: 971: 547: 503: 493: 363: 133:(probably they are handy reverts). If you have any suggestion, please, notice me. Regards. 1627:

Hello, does STicki work for other MediaWiki sites such as Wikia or is it Knowledge only?--

599: 8: 1362:

We would have a problem using the API hosted on your site for the smart watchlist due to

1217:

I'll consider it. Out of curiosity, what is your "real world" area of expertise? Thanks,

943:

achievable project to make such figures accessible and auto-published, say once a month?

745: 126: 1680:

http://ops.unocha.org/ProjectSheet.aspx?appealid=908&projectid=38691&doctype=pdf

1744: 1725: 1702: 1687: 1665: 1651: 1614: 1556: 1484: 1448: 1377: 1363: 1310: 1218: 1089: 1022: 1004: 985: 952: 934: 918: 873: 818: 770: 727: 704: 687: 603: 555: 529: 511: 444: 384: 352: 310: 248: 191: 150: 1332: 106: 1406: 1348: 1292: 570: 474: 422: 400: 275: 1154:

construction of a genius, not something particularly simple to replicate or replace.

1582: 1545: 1507: 1272: 1245: 1201: 1055: 1026: 904: 858: 844: 801: 753: 622: 584: 317: 300: 221: 173: 138: 1467:

effort to aid in Knowledge's goal of "Good Faith Collaboration." Sincerely, Geoff

1447:

presentations and make them available to the entire Knowledge community. Thanks,

893: 670: 401: 376: 359: 343: 1785:

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

119: 576: 1721: 1683: 1521: 852: 751:

they all have to be genuine vandalism, to prevent damage and so on...Cheers,

551: 507: 100: 1366:

on accessing resources from other domains within a script. Our options are:

1530: 469: 417: 978: 1671: 1571: 900: 618: 580: 441:

Wikipedia_talk:STiki/TalkArchive02#Bug_report:_broken_link_in_AIV_summary

169: 134: 1341:{ revid_4781398: 0.0558824660557638, revid_5487332: 0.0518232344557638 } 1082:

logic into a bot that handles the most egregious instances of vandalism.

1021:

You might also be interested in the (somewhat limited) information that

339: 1065: 1380:

specifically permitting the cross-site sharing. This only works with

791:

I seem to have somehow given a stiki warning without a revert... see

598:. I've also got some novel work in progress which I am targeting for 666:

Hello STiki users, and thanks for your continued use of my tool.

1426: 595:

last year in Gdansk (co-located with the more academic WikiSym):

1070: 1369:

Somehow host the API server on en.wikipedia.org/w/stiki_api.php

894:

http://en.wikipedia.org/User_talk:Arthena#Freedmans_Bureau_edit

975: 1388: 1609:

at any time by removing the {{Talkback}} or {{Tb}} template.

1287:

I have created a first cut at a smart watchlist. Please see

657:

at any time by removing the {{Talkback}} or {{Tb}} template.

457:

Oh yeah, I'm probably on a older version. Time to update...

1541: 439:

What is the release date on the version you are using? See

195: 1381: 1064:

Yes, I am a bit deluged right now. Two papers went out to

1396: 981: 577:

http://wikimania2011.wikimedia.org/Call_for_Participation

1537: 888:

History TA proven wrong by STiki assisted vandal-fighter

634: 1331:

Regarding the implementation of a smart watchlist, the

1074: 1540:

and other crowdsourced, crowd-tasked projects (a la

857:

Hello i just wanted to say I STiki is a great tool.

1483:make mistakes, which in this case was me. Thanks, 1440:"Autonomous Detection of Collaborative Link Spam" 1594:Hello, West.andrew.g. You have new messages at 646:Hello, West.andrew.g. You have new messages at 1339:. The result should be a JSON object such as: 1434:"Anti-Vandalism Research: The Year in Review" 1142:hosting provider, that is trivially overcome. 1049:Since you're not busy or anything... Jimbo 381:User_talk:West.andrew.g/TalkArchive02#STiki 1289:User talk:UncleDouggie/smart watchlist.js 917:Awesome story! Thanks for the pointer, 14: 1783:Do not edit the contents of this page. 44:Do not edit the contents of this page. 207:An "otherwise needs attention" button 1764: 1376:, which requires your web server to 458: 25: 1674:. Checking "What links here" I saw 1518:User_talk:Ocaasi/The_Wikipedia_Game 839:Thought you might be interested in 676:User_talk:ClueBot_Commons#IRC_Feeds 23: 1587: 639: 24: 1842: 662:STiki Public Service Announcement 1768: 892:Didn't know if you'd seen this: 459: 29: 168:reverts to anonymous vandals). 1393:limits the query to about 2 kB 787:Oh.... And what happened here? 13: 1: 1676:User:West.andrew.g/Dead links 1516:Please put your responses at 1374:Cross-Origin Resource Sharing 1364:browser security restrictions 927:21:41, 16 December 2010 (UTC) 909:21:25, 16 December 2010 (UTC) 867:06:56, 29 November 2010 (UTC) 348:18:31, 23 February 2011 (UTC) 326:18:14, 14 February 2011 (UTC) 284:05:14, 14 February 2011 (UTC) 257:01:49, 14 February 2011 (UTC) 230:19:10, 13 February 2011 (UTC) 178:18:09, 11 February 2011 (UTC) 159:17:15, 11 February 2011 (UTC) 143:14:06, 11 February 2011 (UTC) 1421:My research @ Wikimania 2011 882:22:20, 7 December 2010 (UTC) 793:User_talk:Carmichael95#Toast 271:identified as test/vandalism 115:21:43, 4 February 2011 (UTC) 7: 1596:ClueBot Commons's talk page 1520:to consolidate discussion. 648:ClueBot Commons's talk page 10: 1847: 1457:04:03, 23 April 2011 (UTC) 1319:18:49, 11 April 2011 (UTC) 1301:08:46, 11 April 2011 (UTC) 827:20:53, 28 March 2011 (UTC) 809:00:43, 27 March 2011 (UTC) 779:20:49, 28 March 2011 (UTC) 761:21:41, 26 March 2011 (UTC) 736:20:44, 28 March 2011 (UTC) 713:21:29, 26 March 2011 (UTC) 696:22:17, 22 March 2011 (UTC) 627:19:05, 10 March 2011 (UTC) 612:17:15, 10 March 2011 (UTC) 589:09:27, 10 March 2011 (UTC) 340:Alan the Roving Ambassador 1753:19:57, 14 July 2011 (UTC) 1730:19:44, 14 July 2011 (UTC) 1711:19:30, 14 July 2011 (UTC) 1692:19:03, 14 July 2011 (UTC) 1415:13:11, 8 April 2011 (UTC) 1357:07:14, 8 April 2011 (UTC) 1276:06:05, 8 April 2011 (UTC) 1249:04:17, 8 April 2011 (UTC) 1227:03:55, 8 April 2011 (UTC) 1205:02:56, 8 April 2011 (UTC) 1098:02:37, 8 April 2011 (UTC) 1059:23:47, 7 April 2011 (UTC) 1035:07:32, 9 April 2011 (UTC) 1017:02:39, 8 April 2011 (UTC) 994:23:38, 7 April 2011 (UTC) 965:22:19, 7 April 2011 (UTC) 848:10:09, 2 April 2011 (UTC) 564:05:15, 8 March 2011 (UTC) 538:05:08, 8 March 2011 (UTC) 520:04:58, 8 March 2011 (UTC) 484:04:30, 8 March 2011 (UTC) 453:04:23, 8 March 2011 (UTC) 432:04:16, 8 March 2011 (UTC) 393:19:20, 3 March 2011 (UTC) 375:This was a tool edit, by 368:19:11, 3 March 2011 (UTC) 1660:23:16, 7 June 2011 (UTC) 1643:22:18, 7 June 2011 (UTC) 1618:13:14, 4 June 2011 (UTC) 1603:13:13, 4 June 2011 (UTC) 1575:18:16, 4 June 2011 (UTC) 1565:23:22, 1 June 2011 (UTC) 1549:06:21, 1 June 2011 (UTC) 1525:11:10, 29 May 2011 (UTC) 1511:03:49, 28 May 2011 (UTC) 1493:14:20, 11 May 2011 (UTC) 1477:10:34, 11 May 2011 (UTC) 1267:Update: Uncle Douggie 334:IP vandal 216.56.48.115 18:User talk:West.andrew.g 1697:See the intro text at 1592: 1382:certain newer browsers 1337:revids=4781398|5487332 1327:STiki API improvements 644: 1781:of past discussions. 1591: 1538:http://zooniverse.org 1397:fix has been proposed 643: 42:of past discussions. 1462:STiki False Positive 972:Knowledge:Statistics 872:Thanks, TucsonDavid 1699:WP:STiki/Dead_links 1378:return HTTP headers 1073:, before I turn to 1607:remove this notice 1593: 1500:The Knowledge Game 1076:in the next month. 1023:Special:Statistics 655:remove this notice 645: 190:My technique uses 1834: 1833: 1793: 1792: 1787:current talk page 1678:, with the link 1333:current STiki API 1025:yields, as well. 567: 550:comment added by 523: 506:comment added by 127:one about reverts 95: 94: 54: 53: 48:current talk page 1838: 1812: 1795: 1794: 1772: 1771: 1765: 1646: 1610: 1342: 1338: 1015: 1013: 1007: 1006:Peter S Strempel 963: 961: 955: 954:Peter S Strempel 835:On-wiki Research 807: 759: 658: 566: 544: 522: 500: 478: 472: 464: 463: 462: 426: 420: 408:I recently made 315: 309: 305: 299: 73: 56: 55: 33: 32: 26: 1846: 1845: 1841: 1840: 1839: 1837: 1836: 1835: 1808: 1769: 1670:I just started 1668: 1636: 1625: 1623:STicki Question 1611: 1600: 1585: 1533: 1503: 1464: 1423: 1340: 1336: 1329: 1047: 1045:Smart watchlist 1011: 1005: 1003: 959: 953: 951: 937: 890: 855: 837: 800: 789: 752: 748: 664: 659: 652: 637: 573: 545: 501: 496: 476: 470: 460: 424: 418: 406: 355: 336: 313: 307: 303: 297: 209: 122: 103: 69: 30: 22: 21: 20: 12: 11: 5: 1844: 1832: 1831: 1826: 1823: 1818: 1813: 1806: 1801: 1791: 1790: 1773: 1762: 1760: 1759: 1758: 1757: 1756: 1755: 1735: 1734: 1733: 1732: 1714: 1713: 1667: 1664: 1663: 1662: 1641:comment added 1629:184.56.245.182 1624: 1621: 1601:Message added 1599: 1586: 1584: 1581: 1580: 1579: 1578: 1577: 1532: 1529: 1528: 1527: 1502: 1497: 1496: 1495: 1463: 1460: 1444: 1443: 1437: 1427:Wikimania 2011 1422: 1419: 1418: 1417: 1403: 1402: 1401: 1385: 1370: 1328: 1325: 1324: 1323: 1322: 1321: 1285: 1284: 1283: 1282: 1281: 1280: 1279: 1278: 1258: 1257: 1256: 1255: 1254: 1253: 1252: 1251: 1234: 1233: 1232: 1231: 1230: 1229: 1210: 1209: 1208: 1207: 1194: 1193: 1192: 1191: 1190: 1189: 1181: 1180: 1179: 1178: 1172: 1171: 1170: 1169: 1168: 1167: 1158: 1157: 1156: 1155: 1148: 1147: 1146: 1145: 1144: 1143: 1134: 1133: 1132: 1131: 1124: 1123: 1122: 1121: 1120: 1119: 1110: 1109: 1108: 1107: 1101: 1100: 1084: 1083: 1078: 1077: 1046: 1043: 1042: 1041: 1040: 1039: 1038: 1037: 997: 996: 936: 933: 932: 931: 930: 929: 912: 911: 889: 886: 885: 884: 854: 851: 836: 833: 832: 831: 830: 829: 788: 785: 784: 783: 782: 781: 747: 744: 743: 742: 741: 740: 739: 738: 718: 717: 716: 715: 663: 660: 651: 638: 636: 633: 632: 631: 630: 629: 572: 569: 541: 540: 495: 492: 491: 490: 489: 488: 487: 486: 405: 399: 398: 397: 396: 395: 354: 351: 335: 332: 331: 330: 329: 328: 291: 290: 289: 288: 287: 286: 262: 261: 260: 259: 241: 240: 239: 238: 208: 205: 204: 203: 202: 201: 200: 199: 183: 182: 181: 180: 162: 161: 121: 118: 102: 99: 97: 93: 92: 87: 84: 79: 74: 67: 62: 52: 51: 34: 15: 9: 6: 4: 3: 2: 1843: 1830: 1827: 1824: 1822: 1819: 1817: 1814: 1811: 1807: 1805: 1802: 1800: 1797: 1796: 1788: 1784: 1780: 1779: 1774: 1767: 1766: 1763: 1754: 1750: 1746: 1745:West.andrew.g 1741: 1740: 1739: 1738: 1737: 1736: 1731: 1727: 1723: 1718: 1717: 1716: 1715: 1712: 1708: 1704: 1703:West.andrew.g 1700: 1696: 1695: 1694: 1693: 1689: 1685: 1681: 1677: 1673: 1661: 1657: 1653: 1652:West.andrew.g 1649: 1648: 1647: 1644: 1640: 1634: 1630: 1620: 1619: 1616: 1615:DamianZaremba 1608: 1604: 1597: 1590: 1576: 1573: 1568: 1567: 1566: 1562: 1558: 1557:West.andrew.g 1553: 1552: 1551: 1550: 1547: 1543: 1539: 1526: 1523: 1519: 1515: 1514: 1513: 1512: 1509: 1501: 1494: 1490: 1486: 1485:West.andrew.g 1481: 1480: 1479: 1478: 1474: 1470: 1459: 1458: 1454: 1450: 1449:West.andrew.g 1441: 1438: 1435: 1432: 1431: 1430: 1428: 1416: 1412: 1408: 1404: 1400:satisfaction. 1398: 1394: 1390: 1386: 1383: 1379: 1375: 1371: 1368: 1367: 1365: 1361: 1360: 1359: 1358: 1354: 1350: 1344: 1334: 1320: 1316: 1312: 1311:West.andrew.g 1307: 1306: 1305: 1304: 1303: 1302: 1298: 1294: 1290: 1277: 1274: 1270: 1266: 1265: 1264: 1263: 1262: 1261: 1260: 1259: 1250: 1247: 1242: 1241: 1240: 1239: 1238: 1237: 1236: 1235: 1228: 1224: 1220: 1219:West.andrew.g 1216: 1215: 1214: 1213: 1212: 1211: 1206: 1203: 1198: 1197: 1196: 1195: 1187: 1186: 1185: 1184: 1183: 1182: 1176: 1175: 1174: 1173: 1164: 1163: 1162: 1161: 1160: 1159: 1152: 1151: 1150: 1149: 1140: 1139: 1138: 1137: 1136: 1135: 1128: 1127: 1126: 1125: 1116: 1115: 1114: 1113: 1112: 1111: 1105: 1104: 1103: 1102: 1099: 1095: 1091: 1090:West.andrew.g 1086: 1085: 1080: 1079: 1075: 1072: 1067: 1063: 1062: 1061: 1060: 1057: 1052: 1036: 1032: 1028: 1024: 1020: 1019: 1018: 1014: 1008: 1001: 1000: 999: 998: 995: 991: 987: 986:West.andrew.g 983: 979: 976: 973: 969: 968: 967: 966: 962: 956: 948: 944: 940: 928: 924: 920: 919:West.andrew.g 916: 915: 914: 913: 910: 906: 902: 898: 897: 896: 895: 883: 879: 875: 874:West.andrew.g 871: 870: 869: 868: 864: 860: 850: 849: 846: 842: 828: 824: 820: 819:West.andrew.g 815: 814: 813: 812: 811: 810: 806: 803: 796: 794: 780: 776: 772: 771:West.andrew.g 767: 766: 765: 764: 763: 762: 758: 755: 737: 733: 729: 728:West.andrew.g 724: 723: 722: 721: 720: 719: 714: 710: 706: 705:West.andrew.g 702: 701: 700: 699: 698: 697: 693: 689: 688:West.andrew.g 685: 679: 677: 672: 667: 656: 649: 642: 628: 624: 620: 615: 614: 613: 609: 605: 604:West.andrew.g 601: 597: 593: 592: 591: 590: 586: 582: 578: 568: 565: 561: 557: 553: 549: 539: 535: 531: 530:West.andrew.g 526: 525: 524: 521: 517: 513: 509: 505: 485: 481: 480: 479: 473: 467: 456: 455: 454: 450: 446: 445:West.andrew.g 442: 438: 437: 436: 435: 434: 433: 429: 428: 427: 421: 415: 411: 403: 394: 390: 386: 385:West.andrew.g 382: 378: 374: 373: 372: 371: 370: 369: 365: 361: 350: 349: 345: 341: 327: 323: 319: 312: 302: 295: 294: 293: 292: 285: 281: 277: 272: 268: 267: 266: 265: 264: 263: 258: 254: 250: 249:West.andrew.g 245: 244: 243: 242: 236: 235: 234: 233: 232: 231: 227: 223: 219: 216: 212: 197: 193: 189: 188: 187: 186: 185: 184: 179: 175: 171: 166: 165: 164: 163: 160: 156: 152: 151:West.andrew.g 147: 146: 145: 144: 140: 136: 132: 128: 117: 116: 112: 108: 98: 91: 88: 85: 83: 80: 78: 75: 72: 68: 66: 63: 61: 58: 57: 49: 45: 41: 40: 35: 28: 27: 19: 1809: 1782: 1776: 1761: 1669: 1626: 1612: 1534: 1504: 1469:76.25.18.197 1465: 1445: 1424: 1407:UncleDouggie 1349:UncleDouggie 1345: 1330: 1293:UncleDouggie 1286: 1048: 949: 945: 941: 938: 891: 856: 838: 797: 790: 749: 680: 668: 665: 600:WikiSym 2011 574: 546:— Preceding 542: 502:— Preceding 497: 494:Your message 475: 468: 423: 416: 407: 356: 337: 276:UncleDouggie 270: 220: 217: 213: 210: 130: 123: 104: 96: 70: 43: 37: 1775:This is an 1672:Budi County 1637:—Preceding 1027:Killiondude 859:TucsonDavid 841:this thread 746:Stiki Races 579:. Cheers, 318:Egg Centric 222:Egg Centric 36:This is an 1829:Archive 10 1666:Dead links 1605:. You can 982:toolserver 935:Statistics 686:. Thanks, 671:ClueBot NG 383:. Thanks, 360:Epeefleche 353:Suggestion 107:Mìthrandir 90:Archive 10 1821:Archive 5 1816:Archive 4 1810:Archive 3 1804:Archive 2 1799:Archive 1 1188:Please do 602:. Thanks 571:WikiMania 311:confusing 82:Archive 5 77:Archive 4 71:Archive 3 65:Archive 2 60:Archive 1 1722:Aymatth2 1684:Aymatth2 1583:Talkback 1522:Dcoetzee 653:You can 560:contribs 552:LegoSaur 548:unsigned 516:contribs 508:LegoSaur 504:unsigned 377:WP:STiki 192:Rollback 149:Thanks, 1778:archive 1639:undated 1066:WikiSym 805:Centric 799:to me. 757:Centric 684:WikiSym 635:ClueBot 301:cleanup 39:archive 1572:Ocaasi 1546:Ocaasi 1508:Ocaasi 1273:Ocaasi 1269:writes 1246:Ocaasi 1202:Ocaasi 1056:Ocaasi 901:Ocaasi 845:Ocaasi 619:Ocaasi 581:Ocaasi 471:Gƒoley 419:Gƒoley 170:emijrp 135:emijrp 120:Thanks 1389:JSONP 1051:asked 853:STiki 402:STiki 131:other 101:Sorry 16:< 1749:talk 1726:talk 1707:talk 1688:talk 1656:talk 1633:talk 1561:talk 1542:GWAP 1531:Idea 1489:talk 1473:talk 1453:talk 1411:talk 1387:Use 1372:Use 1353:talk 1315:talk 1297:talk 1223:talk 1094:talk 1071:CEAS 1031:talk 1012:Talk 990:talk 977:and 970:See 960:Talk 923:talk 905:talk 878:talk 863:talk 823:talk 775:talk 732:talk 709:talk 692:talk 623:talk 608:talk 585:talk 556:talk 534:talk 512:talk 477:Four 449:talk 425:Four 410:this 389:talk 364:talk 344:talk 322:talk 280:talk 253:talk 226:talk 211:Hi, 196:Weka 174:talk 155:talk 139:talk 111:talk 1635:) 1291:. — 802:Egg 754:Egg 404:bug 1825:→ 1751:) 1728:) 1709:) 1690:) 1658:) 1613:- 1563:) 1491:) 1475:) 1455:) 1429:: 1413:) 1355:) 1317:) 1299:) 1225:) 1096:) 1033:) 1009:| 992:) 957:| 925:) 907:) 880:) 865:) 825:) 795:. 777:) 734:) 711:) 694:) 625:) 610:) 587:) 562:) 558:• 536:) 518:) 514:• 482:— 451:) 430:— 391:) 366:) 346:) 324:) 314:}} 308:{{ 306:, 304:}} 298:{{ 282:) 255:) 228:) 176:) 157:) 141:) 113:) 86:→ 1789:. 1747:( 1724:( 1705:( 1686:( 1654:( 1645:. 1631:( 1598:. 1559:( 1487:( 1471:( 1451:( 1409:( 1405:— 1351:( 1347:— 1313:( 1295:( 1221:( 1092:( 1029:( 988:( 921:( 903:( 876:( 861:( 821:( 773:( 730:( 707:( 690:( 650:. 621:( 606:( 583:( 554:( 532:( 510:( 466:— 447:( 414:— 387:( 362:( 342:( 320:( 278:( 251:( 224:( 172:( 153:( 137:( 109:( 50:.

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

Index