Wikipedia talk:STiki
| 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.
Contents
Known Bugs and Feature Requests[edit]
| ID | Contact | Type | Description | Status | Urgency |
|---|---|---|---|---|---|
| T#059 | Adotchar | Feature Request | Identify a mechanism to notify users when they have a message within STiki, possibly with options regarding how prominent this notification should be. | Pending | Medium |
| T#060 | Materialscientist | Bug Fix | After the STiki window has been left inactive for a period (hours), if the first edit classified is "vandalism" the "beaten to revert" message will be erroneously displayed. Interestingly, there is no issue if an AGF classification is applied. This is presumably due to a failed check/renewal of the expiration on the rollback token. | 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#062 | Benzband | Feature Request | Display the edit count of the user under inspection, perhaps with some notion of "recency", to help users determine if it is worthwhile to scrutinize the user's edit history. | Pending | Medium |
| T#061 | Redhat101 | Feature Request | For those who use STiki at night or simply prefer a darker interface, that option should be available alongside the other color-change options. Hopefully we can rely on a Java "look and feel" configuration to do this quickly and globally without having to modify individual components. | 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#056 | Materialscientist | Bug Fix | If the article currently being displayed in the STiki browser is deleted (i.e., by the STiki user in a traditional browser), it will cause the STiki browser to stall when the article is subsequently classified. | Pending | 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 2016-08-04 release (and 2018-04-10 minor update)[edit]
Greetings STiki-ers... The first update in a long time that isn't an emergency release! As always, your participation and continued feedback is appreciated. This is likely the STiki version that will take us over 1 MILLION reverts. This update brings us:
- The "ignore" button (adjacent to the "user" line of the "metadata panel") enables a session-length ignore of edits made by a particular user (e.g., repeated maintenance tasks that are not vandalism). The ignore list resets when STiki is restarted. The link will change from a blue "ignore" to red "ignored" if the action succeeds (T#053).
- Implemented API "thank" functionality. A revision/editor can be "thanked" by using the button adjacent to the "REVISION_ID" line of the "metadata panel". "Thanking" is tied to specific revision-ids, justifying this placement. It was not made an explicit classification button and tied to the "innocent" outcome as such a promotion seems like mission-creep for an anti-vandalism tool. The link will change from a blue "thank" to red "thanked" if the action is successful. Note that only registered editors can be thanked, and the link will be hidden for edits made by unregistered users (T#055).
- The fact an article is CSD ("candidate for speedy deletion") can now be noted atop diffs, similar to how the "this will rollback 'n' edits" note already appears. This functionality is enabled by default, but is in "options" menu (T#052).
- First attempt at solving macOS GUI layout issues. These seemed to stem from the fact macOS enforces a border on JButtons (T#054).
- A situation was identified where rollback tokens were sometimes failing to be acquired. This was in turn causing those rollbacks to silently fail and block subsequent ones. This probably caused some of the "I did work; but made no edits" sessions.
- Minor change w.r.t. to height of "watchlist options" drop-down, which seems to have no default minimum height
- Minor change to make login error messages more descriptive
A minor update on 2018-04-10 brought:
- Edits made by STiki (reverts/rollbacks/warnings) will now be tagged with the "STiki" label. A backend process is available to label all prior revert/rollback actions in this manner, if this is determined desirable by community consensus.
- Resolved the "milestone for blocked editor" issue; WP:BEANS (T#057)
- The edit comment for an AIV posting regarding a registered user will link to that user's contributions, not their talk page
- Minor changes and test suite for IRC feeds
- Building in (redundant?) checks to ensure that rollback/edit tokens are acquired; still addressing session drop/fail issues
- Added minor utility script that allows one to grant explicit access to users with Unicode characters in usernames
Thanks for your continued participation and support. West.andrew.g (talk) 15:07, 12 April 2018 (UTC)
CBNG queue has returned!![edit]
The team that runs CluebotNG has fixed their IRC issues and are once again broadcasting edit vandalism probabilities. STiki ingests these scores as the basis for an alternative queue to the "STiki (metadata)" one that has been the lone (and therefore, default) option for quite some time. CBNG's model outperforms the metadata one, and if historical trends hold, STiki users should expect to encounter vandalism 2-3x more often using CBNG data. The feed has been implemented and the CBNG model is now the default queue at startup. Happy reverting. West.andrew.g (talk) 17:39, 24 September 2018 (UTC)
- Yayy! Great news. This queue was historically the best one, as you say :) Orphan Wiki 22:06, 24 September 2018 (UTC)
At long last. Muchas gracias to all involved. Thanks, L3X1 ◊distænt write◊ 15:20, 25 September 2018 (UTC)
- Just for perspective, the revert-rate has been around 35% for the past couple of days, I'd estimate we were < 10% using the metadata queue! West.andrew.g (talk) 20:29, 27 September 2018 (UTC)
- Great news. RC patrols certainly seem more productive using this queue. Orphan Wiki 21:13, 2 October 2018 (UTC)
STiki for mobile[edit]
Is it possible or is possible in future to use STiki on mobile devices? — Preceding unsigned comment added by Jackfield1122 (talk • contribs) 16:10, 2 October 2018 (UTC)
- Last I heard you can't run Java on mobile platforms without seriously rebuilding it or porting to another language. Thanks, L3X1 ◊distænt write◊ 17:03, 2 October 2018 (UTC)
- Accurate. This is an unlikely effort given limited STiki usage as of late. The entire UI would have to be redesigned for a mobile device; I don't think Java Swing is easily portable. There would also have to be some type of packaging; most devices don't have native Java/JAR support. My source is on GitHub for anyone feeling adventurous, though! West.andrew.g (talk) 10:09, 5 October 2018 (UTC)
STiki is down (UPDATE: Back up again)[edit]
The machine that hosts STiki has gone offline. I've sent an email to colleagues onsite at UPenn to investigate. West.andrew.g (talk) 20:51, 4 October 2018 (UTC)
- Thank you for the update Andrew. I was wondering why it wasn't uploading. Orphan Wiki 20:54, 4 October 2018 (UTC)
- And we are back up again, in record time! West.andrew.g (talk) 22:53, 4 October 2018 (UTC)
Request Access[edit]
I would like to use STiKi, may I please have access. So said The Great Wiki Lord. (talk) 14:54, 21 October 2018 (UTC)
Done -- @TheGreatWikiLord: Access granted. Happy reverting. West.andrew.g (talk) 15:04, 21 October 2018 (UTC)
Request[edit]
Despite not having reverting Vandalism since I started editing, I like someone give me a tool please. Thank You Sheldybett (talk) 03:22, 1 November 2018 (UTC)
- Real life is crazy. Can one of the STiki regulars provide a recommendation on this access request? Thanks, West.andrew.g (talk) 12:49, 3 November 2018 (UTC)
- Hi Andrew, I'm not so sure. Less than 700 total edits, and less than 200 Twinkle/Undo edits so far. No rollback user rights. User has been editing just 4 months, and while it seems like they are doing some very good work, there is evidence that they are still on a learning curve, and there has been some erroneous AfD/Speedy deletion requests recently too. Maybe Sheldybett should be encouraged to try again in a few more months, when a greater understanding of Wikipedia policy is obtained? Orphan Wiki 22:40, 4 November 2018 (UTC)
Not done -- @Sheldybett: On the basis of the community recommendation above. West.andrew.g (talk) 19:21, 5 November 2018 (UTC)