|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#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|
|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 (+ 2014-12-12 bug fix)
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).
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)
- Wonderful. Thanks, Melonkelon (talk) 05:23, 1 December 2014 (UTC)
Force people to download the latest version of STiki?
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:
- 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.
- 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.
- Good idea; I had experienced very buggy behavior from an older version, which disappeared as soon as I updated to a more recent one. HGilbert (talk) 13:14, 14 December 2014 (UTC)
Now easier to see the changes made to the good-faith-revert messages
When Andrew updated the page on good-faith-revert messages 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 this diff now shows the changes more clearly. I thought this would be handy to improve the transparency of the change.
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.