Jump to content

Wikipedia talk:STiki

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Gaurav kasotiya (talk | contribs) at 11:00, 28 December 2015. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.



Welcome to the talk page for the WP:STiki tool. It works just as any other talk page. However, before you report a bug or feature request, please check the table of the first section to see if the issue is already known. Please do not edit that table manually, instead just start a discussion and STiki's developers will update the table as appropriate.

Known Bugs and Feature Requests

STiki Outstanding Bugs and Feature Requests
ID Contact Type Description Status Urgency
T#052 Rsrikanth05 Feature Request Note if an article has been tagged as a candidate for speedy deletion (CSD). This can be done similar to how "rollback situations" are noted in purple text atop the diff, but using a different color. Pending Medium
T#039 Ugog Nizdast Feature Request The user should have the capability to display some form of article history, primarily/all in the form of metadata, for the edit under inspection. Pending Medium
T#045 Chess Feature Request Current custom AGF messages hide behind opaque names and are fixed in number. There should be a more dynamic CRUD + naming scheme for AGF messages, which if not an in-STiki interface, could depend on user editing of the configuration files. Pending Medium-Low
T#040 Yaris678 Feature Request Rather than the current "last revert" message having a very "error" tone, shift that to something more positively reflecting the classification was still useful. Better yet, detect when conflicting edits are by STiki user to change message tone accordingly. Pending Medium-Low
T#010 Allens Feature Request There is a desire to somehow represent (possibly with underlining or a color) whether a wikilink has an existing article destination or is a "red-link". Some investigation is needed to determine how to best do this with the Mediawiki API, and the performance penalty it causes. Could also be a STiki option whether or not this should be done. On Hold Medium-Low
T#028 John of Reading Feature Request Expand processing to include some alternative namespaces, namely "portal" and "help". Existing classification models would be re-used and there would be an explicit new queue for these edits. Pending Medium-Low
T#027 Arc de ciel Feature Request More careful recording of "pass" actions. This would also permit a feature allowing a user to view, ex post facto, how the edits they passed on were eventually classified. On Hold Medium-Low
T#004 West.andrew.g Feature Request The STiki client currently talks to the backend using only MySQL. MySQL communication could be firewalled by some organizations, making the move to HTTP/PHP communications a good idea. However, this remains low priority given that such little mention has been made of this shortcoming. Pending Low
T#003 Chicocvenancio and Meiskam Feature Request STiki exists only in English, and should perhaps put structure in place for localization. Meiskam wrote some initial structure for this, but I am holding on trunk integration. To move forward, we need someone who has the time, expertise, resources (a server), and willingness to run a STiki backend and do all text translation. On Hold Very Low
T#999
-
 Feature Request Note that all requests pertaining to the inclusion of back-end classifier features should be lodged and discussed in the sandbox at Wikipedia talk:STiki/Feature development
-
-


CHANGELOG for 2014-12-01 release (+ subsequent bug fixes and ERs)

Greetings STiki-ers... We have a substantial release this iteration, fulfilling many months of feature requests and minor bug discoveries. This is the first version in a while whose release was not forced by an emergency circumstance (i.e., unannounced WMF change), and I am excited to get out meaningful features that demonstrate my commitment to the tool and the anti-damage community. This version brings us:

  • The "Options" menu now has a setting that allows clients to be notified via pop-up if an AIV post has been lodged (T#018; T#046).
  • Null diffs should no longer be displayed (T#038). This was a bug introduced when STiki enabled custom color options for users.
  • Users will not be displayed their own edits from the queues, as this is a conflict of interest (T#043).
  • More AGF messages were added, including some pulled in from a GitHub merge (our first community code contribution!). Some category labels were pre-pended to help better manage this growing list. The code copy was also synced with community copy at: WP:STiki/Good-faith-revert_messages.
  • The metadata panel content now has "mouseover" support. In particular, this should permit the full display of comments which are truncated because they are too lengthy to fit in the fixed-size placeholder.
  • A "small numerical edits" filter has been created. Sometimes monotonous and difficult to casually assess, this filter can allow users to skip edits where "only a single numerical value is changed, and the magnitude of that change is (0.5 < change < 2.0)" (T#049).
  • Additional watchlisting options (reverts/warns/both/preferences/never) are now accessible via a drop-down menu in the login panel (T#042).
  • Additional user/article-talk links added to metadata panel (T#036).
  • Removed reference to "editing anonymously" in login dialog (T#044).
  • The "don't template the regulars" option/dialog was re-focused such that it is now labeled: "warn if reverting regular" (T#050).
  • A classification button was added to support reversion and immediate "4im" issuance (assuming warning criteria are met and escalation wouldn't already result in an AIV report)(T#041)
  • There have been reports of user's edit session's dropping, resulting in editing while logged out. This results in privacy loss and community confusion. This is believed to be a bug on the WMF server-side. However, using the "assert=true" check, STiki can now at least detect the error state -- it pops a dialog and forces a restart (T#048).
  • Due to a WMF API change, we were forced to change the way user edit counts are performed. The WMF changed the way pagination is done, breaking our earlier parser in some cases. This code was used to determine STiki permissions (>1000 NS0 edits), "don't template the regulars" logic, and non-critical aspects of milestone reporting.
  • Minor improvements to warning increment logic; in particular, better handling when duplicate section headers exist.
  • Documentation changes in support of above
    • 2014-12-01: An additional space character in some of the pre-formatted AGF messages was causing them to be parsed in a non-conventional boxed style with monospace font, characteristic of the "pre" environment. This was fixed and and a new file was uploaded under the same filename.
    • 2014-12-12: Something seems to have changed with the way Mediawiki parses new line instructions, causing section headers to not be displayed, and causing warnings to run together. STiki has changed line breaks on talk pages messages from "/r" (carriage return) to "/n" (newline).
    • 2015-06-13 EMERGENCY RELEASE: The WMF switch to support only HTTPS caused widespread breakage due to hard-coded HTTP API calls. Paths were updated and the version was marked as a required upgrade. This also pushed T#051 to production which addressed a bug with the persistence of custom AGF messages.
    • 2015-07-02 EMERGENCY RELEASE: Mediawiki is changing the way pagination/continuation is handled for API queries that produce many results. This decision breaks existing code, but curiously, legacy functionality is still supported if an extra parameter is passed (if this sounds dumb, it is). The old methodology will be switched off sometime on 2015-JUL-02. Internal to STiki this primarily affects/affected the permission check of "1000+ edits in NS0". This new version fixes that issue; users who who rely on that entry criteria will likely require an immediate upgrade.

I have tested the code, but as we develop features around infrequent use-cases (4im, AIV, etc.) it becomes increasingly difficult to verify correctness in the wild. Your continued monitoring, innovation, and support is greatly appreciated. West.andrew.g (talk) 03:46, 1 December 2014 (UTC)[reply]

Issue using STiki

Extended content

After I try to login using STiki, I get an error message saying there's an error in the user login interface, likely caused by a network error, and that there was an exception thrown to terminate the thread. Anyone know how to fix this? The StormCatcher (talk) (contribs) 19:53, 7 December 2015 (UTC)[reply]

STiki communicates with its backend server using MySQL (port 3306, I think). Some firewalls (particularly corporate, but also educational) will block this outgoing port by default. It could also be a rule specific to your local firewall. That is the most common reason for this message. West.andrew.g (talk) 21:07, 7 December 2015 (UTC)[reply]
  • Two of the criteria for using STiki is either rollback permission or 1000 main space edits. You have currently 726 main space edits (Automated edits 456 (63%) Non-automated edits 270 (37%)). You have applied at WP:PERM/R for rollback 3 times the last few weeks. The latest decline (Diff of Wikipedia:Requests for permissions/Rollback) mentioned concerns about your reverts, and asked you to complete your CVUA training, followed by at least two full months of active counter-vandalism before requesting rollback again. - Sam Sailor Talk! 23:11, 7 December 2015 (UTC) P.S. Stiki works fine for me.[reply]
  • Double-checked and the username is entered correctly into the explicit permissions table (although I will assume good faith with respect to the fact that might have been a bit premature, given the evidence above). Can you try running STiki from a terminal and seeing what type of exceptions get printed there? West.andrew.g (talk) 04:28, 8 December 2015 (UTC)[reply]
  • Windows calls the "terminal" the "command prompt", I think. I am not sure how much that output is going to help though. Even though this a home network there is the possibility that your router or ISP is blocking the port upstream. What does [1] tell you? Thanks, West.andrew.g (talk) 00:27, 9 December 2015 (UTC)[reply]

The StormCatcher (talk) (contribs) 17:10, 9 December 2015 (UTC)[reply]

@CatcherStorm: I'm pretty perplexed here to be honest. Your browser can reach [2] (its a redirect to my personal page)? That is the server where STiki lives, but it does not respond to terminal pings for security reasons. Next step is that I'll dig into server network logs, though its unclear if your request is even making it this far. Thanks, West.andrew.g (talk) 19:01, 11 December 2015 (UTC)[reply]
I'm having this issue also. I've used STiki for years, not sure why it's happening now. Orphan Wiki 00:38, 12 December 2015 (UTC)[reply]
@CatcherStorm: I saw on the "milestones" page that you were able to use the tool. What worked? West.andrew.g (talk) 03:31, 14 December 2015 (UTC)[reply]
@West.andrew.g: I used another computer at the library, but now I'm stuck with my other laptop which still isn't working with STiki. The StormCatcher (talk) (contribs) 04:31, 14 December 2015 (UTC)[reply]
Well that certainly indicates it is something with the home network or the laptop (duh!). You are able to visit the website I linked just above? West.andrew.g (talk) 17:44, 16 December 2015 (UTC)[reply]
*@West.andrew.g: Yes, I can reach your page using my laptop. The StormCatcher (talk) (contribs) 02:30, 17 December 2015 (UTC)[reply]
I'm gonna throw this open to the community; any ideas out there? I could spin up a dead simple program that just connects to the STiki server and then disconnects, but I don't think that Java's error handling is going to be able to give us much insight as to what is happening along the network path. I'm gaining confidence this is a firewall issue somewhere along the way. Anyone got ideas on how to pinpoint where? West.andrew.g (talk) 04:47, 17 December 2015 (UTC)[reply]
@CatcherStorm: I haven't touched a Windows box in years, so I can't comment, but I find it unlikely. Most online sources also suspect firewall issues, i.e., [3]. Thanks, West.andrew.g (talk) 22:12, 17 December 2015 (UTC)[reply]
@West.andrew.g: So I turned my firewall on but added port 3306. I tried logging in with no luck, so I proceeded to just turn my firewall off and tried logging in with the same result. If port 3306 weren't open for me, I wouldn't even be able to get into the program. I can open STiki and the login screen will open, I just won't be able to login. When I try using STiki at school, because port 3306 isn't open, I won't even be able to open STiki itself to try logging in. So my port's open.. The StormCatcher (talk) (contribs) 22:20, 17 December 2015 (UTC)[reply]
@CatcherStorm: Does an edit show up in the diff-window? I realize you can't classify it because you aren't logged in, but does the diff text appear? Thanks, West.andrew.g (talk) 22:31, 17 December 2015 (UTC)[reply]
@West.andrew.g: The diff-window is blank. After I try logging in, the error window says it's a problem with the login panel. The StormCatcher (talk) (contribs) 22:36, 17 December 2015 (UTC)[reply]
@CatcherStorm: Even if you let it sit for, say, 5 minutes without attempting to login, does the diff-window ever populate? West.andrew.g (talk) 00:24, 18 December 2015 (UTC)[reply]
@West.andrew.g: Yeah it doesn't look like it's populating. I'm pretty sure it has something to do with my computer because I was able to get my hands on a laptop temporarily and it worked fine. Thing is I can't use the laptop I'm on right now (a Win7 Thinkpad) forever, so I need a solution to this. The StormCatcher (talk) (contribs) 00:53, 18 December 2015 (UTC)[reply]
@CatcherStorm: For clarity, you have a laptop that works on your network, whereas your primary computer does not work on the same network? West.andrew.g (talk) 01:08, 18 December 2015 (UTC)[reply]
@West.andrew.g: Yes, that's correct. The StormCatcher (talk) (contribs) 01:10, 18 December 2015 (UTC)[reply]
@CatcherStorm: Relatively recent version of Java installed? What OS? Is an anti-virus running? West.andrew.g (talk) 01:59, 18 December 2015 (UTC)[reply]
@West.andrew.g: For the working laptop, Java is up to date and it's running Windows 7, and no antivirus is running. For the non-working laptop, Java is up to date, it's running Windows Vista in safe mode, and no anti-virus is running. The StormCatcher (talk) (contribs) 02:02, 18 December 2015 (UTC)[reply]
@CatcherStorm: The fact you throw out "safe mode" here is an obvious red flag. Why "safe mode"? Presumably "safe mode w/networking"? I can't find this exact problem in online forums, but I get the general sense that MySQL and safe mode do not play nice. It's hard to tell what services might be disabled or why MySQL doesn't work, but I suggest you do some digging along these lines. West.andrew.g (talk) 03:02, 18 December 2015 (UTC)[reply]
@West.andrew.g: Yeah I was assuming it was safe mode. Yes I'm running safe mode with networking, because the laptop I'm using can hardly operate in normal mode. It looks like safe mode isn't affecting my ability to use STiki at all, which is very perplexing. The port's open, doesn't look like STiki needs any services either.The StormCatcher (talk) (contribs) 04:00, 18 December 2015 (UTC)[reply]
I've tried to be as much help as possible here, but as we've determined this is not a network problem, nor am I a Windows expert -- this is probably something best troubleshot locally and maybe with the help of some more focused Internet forums. I do wish you the best of luck in getting everything working. West.andrew.g (talk) 01:17, 21 December 2015 (UTC)[reply]
@West.andrew.g: There aren't many online forum threads with solutions on how to fix issues with a program like STiki from working. Could you link me to a few threads that you've found? CatcherStorm talk 08:22, 22 December 2015 (UTC)[reply]
{@CatcherStorm: STiki is pretty unremarkable as a program aside from the fact it communicates over MySQL (port 3306). With very high probability I believe this to be the issue. Outside of this, the external communications are basically just HTTPS ones to WMF servers (akin to using Wikipedia in a browser). If I find the cycles this holiday I'll try to write you a test program that tests your connection in the most basic terms. If you want to dig around until then, I would look for people who have difficulty getting MySQL applications (clients; not servers) running on Window's boxes. West.andrew.g (talk) 14:37, 22 December 2015 (UTC)[reply]
@West.andrew.g: Alright, let me know when you've written it. CatcherStorm talk 09:52, 24 December 2015 (UTC)[reply]

Small issue with STiki using the Cluebot-NG rev. queue

Not sure if this is the right place to report this (as it is using Cluebot's revision queue), but I just thought I would let the STiki managers know. Template:Long comment is showing up a lot on my STiki client, although it is being used in a perfectly acceptable way and I haven't seen it being used inappropriately. Is this an issue with Cluebot's ANN scoring or STiki? -Liancetalk/contribs 02:19, 22 December 2015 (UTC)[reply]

Are bots exempted from review? I wonder if it's because these are being done en masse by a user and not through WP:BRFA. Qzd (talk) 04:52, 22 December 2015 (UTC)[reply]
The STiki backend consumes ClueBot_NG's ANN scores verbatim, but I do filter such that edits performed by bots are not enqueued. I'll assume this is work being done by an individual editor? It's not uncommon to find that an editor who mass adds/deletes content on a lot of pages very quickly will find themselves under scrutiny from anti-vandalism algorithms -- and therefore getting their edits popped repeatedly from the STiki queue. Consider: (1) quick addition of content across many pages is an atypical editing pattern, (2) given the number of pages involved, some of these changes might get reverted by persons trying to exercise ownership of a page or because they feel the issue wasn't discussed on the talk page. Someone who is adding a lot of content and incurring a multiple reverts in short duration is a pretty suspicious signature. That said, I understand why this is a pain to tool users. I've imagined a "temporary ignore" function that one could level against a particular editor, but a clean implementation has never really coalesced in my mind. How often do people encounter this? Thanks, West.andrew.g (talk) 06:50, 22 December 2015 (UTC)[reply]
This comes up from time to time. Liance is talking about Dcirovic (talk · contribs), whose edits fill up the Cluebot (and hence Stiki) queue. Yes, other anti-vandalism tools have a button to ignore edits by selected ("this") user/IP, but I imagine there are other solutions too. Materialscientist (talk) 07:51, 22 December 2015 (UTC)[reply]

STiki Freezes

After every time I click one of the choice buttons on the left side, it freezes for three seconds and then skips one of the possible vandalism changes. Any fixes? Also, if you need some of my PC information feel free to ask me. Dat GuyTalkContribs 12:22, 25 December 2015 (UTC)[reply]

Feature Request: Pass notes

Just was thinking today, it would be nice if, when we hit "pass", we could leave a note for the next editor to see it. I don't use the button very often, but when I do, its usually just that I don't feel 100% comfortable making the action, or need someone who might know a bit more about the subject to make the call. --allthefoxes (Talk) 17:34, 25 December 2015 (UTC)[reply]

While you might want to leave a note, I question if the average STiki user would take the time to read it. Moreover, what would a note say besides "this is a borderline edit, I can't verify this fact to determine if it is vandalism". Isn't that the implicit meaning of all "pass" actions? West.andrew.g (talk) 16:13, 26 December 2015 (UTC)[reply]

STiki down?

Around here, STiki seems to be down and out. Exactly at Xmas time.. Anyone else?! Super48paul (talk) 08:11, 26 December 2015 (UTC)[reply]

It's working fine for me. I just opened it and reverted some edits. Melonkelon (talk) 08:16, 26 December 2015 (UTC)[reply]
Yep! It got back to life. Must have been out for a short while only.Super48paul (talk) 09:46, 26 December 2015 (UTC)[reply]
Monitoring systems indicated no downtime. Thanks, West.andrew.g (talk) 15:56, 26 December 2015 (UTC)[reply]

Que depletion or reboot needed?

Andrew, I'm getting lots of 80-90-100+ days old edits no matter which rev queue I use, would you look into it, please. Thanks, Sam Sailor Talk! 19:07, 26 December 2015 (UTC)[reply]

Yes, this has been happening to me in the past few hours. All was fine yesterday. -_Rsrikanth05 (talk) 08:14, 27 December 2015 (UTC)[reply]
When I used it yesterday I was getting old edits, like 40+ days old, but I'm getting edits made a couple of minutes ago now. Melonkelon (talk) 21:47, 27 December 2015 (UTC)[reply]
I'm getting those stale edits in between the few recent revisions, just as I returned from a week-long Wikibreak. lavender|(formerly HMSSolent)|lambast 01:28, 28 December 2015 (UTC)[reply]
Till Yesterday, I was getting a few recent edits in the midst of a bunch of stale ones. --Rsrikanth05 (talk) 05:41, 28 December 2015 (UTC)[reply]

11:00, 28 December 2015 (UTC)11:00, 28 December 2015 (UTC)11:00, 28 December 2015 (UTC)~ how I create my page without any speedy deletion

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:STiki&oldid=697121961"