|Threads older than 7 days may be archived.|
|Please discuss STiki on this talk page. This software has a single author, West.andrew.g. Unless there is an urgent matter involving the tool, it is preferred to conduct all related conversation here, rather than on his personal talk page.|
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
|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#053||Liance||Feature Request||Queues sometimes display many repetitive edits by the same user, characteristic of AWB use. There should be a way to temporarily (session-length) ignore a particular user's edits.||Pending||Medium-Low|
|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|
|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.
- 2016-01-22 EMERGENCY RELEASE: Updates to the MW SessionManager conflicted with how STiki was constructing its session cookies. An invalid session meant that rollback/edit tokens were not validating, and no reverts/edits could be made. This fundamentally broke earlier versions, thus a forced updated was been issued.
- 2016-02-12 EMERGENCY RELEASE: Authentication changes are upcoming (we'll try to integrate them before they break us, for once!) and some method deprecation warnings were added to the API login process accordingly. These messages broke our expected response format, parsing, and all of login as a result. Forced update issued.
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)
- Update: it is not reversing any of my vetted edits now. FoCuS contribs; talk to me! 21:20, 28 January 2016 (UTC)
- Confirming. STiki isn't reverting anything currently. Widr (talk) 18:09, 29 January 2016 (UTC)
I've been offline for the past week. The fact that things magically fix themselves indicate the problem is unlikely to be on STiki's side. Moreover, the symptoms will need to be active for me to do any meaningful troubleshooting. Seems like it has been a few days since someone last posted. Please let me know if the issues continue. I do have a few STiki maintenance tasks on my docket, but I don't imagine they will have any dramatic affect. Thanks, West.andrew.g (talk) 20:02, 4 February 2016 (UTC)
- Thanks for that! I am also seeing buttons clicking twice in a row, but I'm also assuming that's on my side. FoCuS contribs; talk to me! 20:42, 5 February 2016 (UTC)
- It won't even close for me. Need to restart the computer every time (dunno which process it is from task manager). FoCuS contribs; talk to me! 01:40, 9 February 2016 (UTC)
- Re- Task Manager FoCuSandLeArN, Java (TM) Platform SE binary (32 bit)
— Gareth Griffith-Jones | The Welsh | Buzzard | 11:14, 9 February 2016 (UTC)
Hello fellow Wikipedians, I've been an experienced IP editor for years (I didn't see any need for an account until now). I help out regularly in the #wikipedia-en-help IRC channel on freenode. I enjoy reverting vandalism and am a new pages and recent changes patroller. I use Twinkle regularly. I think that STiki will help me revert vandalism even more effectively on Wikipedia. Thanks, and happy editing! Tom29739 [talk] 20:55, 5 February 2016 (UTC).
- Hello Tom, Your enthusiasm speaks absolutely in favour of your request. The only thing is that both Twinkle and Huggle edits are very very few. I know about your IP-pre-history, but that doesn't show in the figures (obviously). So I hesitate what is wisdom: whether you should gain access now - or just carry on with the means at your disposal for some more time. Well, as usual, thinking out loud, and leaving the ultimate decision to Andrew....Super48paul (talk) 10:02, 6 February 2016 (UTC)
We just aren't seeing any negative fallout from the borderline cases I am approving. Even the occasional complaint is probably a net gain. Moreover, when I look at the status report every night I am seeing revert rates of 30%+ or even 40%+. This speaks to the fact there is no shortage of vandalism out there and a bigger labor pool can help in this effort. Thanks, West.andrew.g (talk) 17:16, 12 February 2016 (UTC)
- Possibly Wikipedia:Village_pump_(technical)#.22Keep_me_logged_in_for_up_to_30_days.22_not_working. Investigating. West.andrew.g (talk) 02:05, 12 February 2016 (UTC)
- Have you tried using the 2.1 release from 2016-01-22? There was a fix for HTTP cookie handling made to support MediaWiki 1.27.0 internal changes. Authenticating with that version seems to work for me (although I don't have rollback perms so the app halts me just after login). --BDavis (WMF) (talk) 16:37, 12 February 2016 (UTC)
- Now distributed via STiki's main page and GitHub. All housecleaning complete. Please verify functionality. Thanks, West.andrew.g (talk) 17:08, 12 February 2016 (UTC)