Wikipedia talk:STiki

Active discussions



Known Bugs and Feature RequestsEdit

STiki Outstanding Bugs and Feature Requests
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 subsequent minor updates)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


A minor update on 2018-12-08 brought:

  • Added "Verify session at login" to the "Options" menu. This is an attempt to solve the "session dropped" errors experienced intermittently by some users. If checked, immediately after login, a test edit and AGF of that edit will be made to a dummy page in WP:STiki space (a workflow that shows promise in surfacing session issues). If successful, we proceed as normal. If not, credentials are available to transparently re-login and try again. Debugging information will be written to STDOUT. This option is disabled by default and should not be enabled by those not having issues. Hopefully this temporarily patches and helps in identifying the root cause of this ongoing bug.


Thanks for your continued participation and support. West.andrew.g (talk) 15:07, 12 April 2018 (UTC)

Requesting special perm for useEdit

Hi, I am requesting special perm to use STiki as I don't have rollback perm or 1k mainspace edits. I am enrolled in the WP CVUA program which my trainer Cassiopeia (talk · contribs) can verify. I understand STiki is a prividledge and I'm responsible for how I use it. I've been working to improve WP against vandalism using recent changes, but I know STiki will help that greatly. Thank you for your consideration. ToeFungii (talk) 22:48, 5 May 2020 (UTC)

Hi, the tool is no longer being updated, and as such remains largely unusable until further notice, really. Not sure if there will be a resolution for now, unfortunately. Orphan Wiki 22:55, 5 May 2020 (UTC)
Wow. Thanks for quick reply although sad news. TY ToeFungii (talk) 23:02, 5 May 2020 (UTC)
No worries. Keep checking in, you never know. And well done on your anti-vandalism efforts so far :) Orphan Wiki 23:26, 5 May 2020 (UTC)
ToeFungii has been CU-blocked as a sockpuppet. JavaHurricane 05:03, 12 June 2020 (UTC)

Request to use toolEdit

Hi, I was recommended this tool by an admin and would like to have permission to use the tool as I fight vandalism often and am a well-established editor. I understand the tool is 'inactive' and no longer receives updates but would like to experiment and try the tool out. Thanks, --Landihan (talk) 09:06, 13 May 2020 (UTC)

@Landihan: Sorry, but STiki has basically been unusable since March. You could try Huggle, which works pretty similarly, though you'll need the rollback right first.   Ganbaruby!  (Say hi!) 09:23, 13 May 2020 (UTC)
Thanks, I currently have been denied the rollback right as I've only been on Wikipedia for 14 days.--Landihan (talk) 09:26, 13 May 2020 (UTC)
The best thing to do, if you have only been on Wikipedia for 14 days, is to gain experience using Twinkle for now, as you do not need rollback rights to use it. Be careful with it, and only revert edits which are obviously vandalism. As time goes by, if you demonstrate careful and considerate use of the tool, rollback rights are much more likely to be granted. Sadly, as Landihan says, STiki is out of action for now. Orphan Wiki 17:10, 13 May 2020 (UTC)

STiki not functional; added a notice to the project pageEdit

With no updates as to whether or not the tool still works, and with plenty of reports that it no longer does, I've added a notice on the project page to let users know that it currently isn't functional. Feel free to update or remove that message as appropriate. —k6ka 🍁 (Talk · Contributions) 20:48, 28 May 2020 (UTC)

That's great, thanks. The creator West.andrew.g mentioned it would be worth doing when it became clear the tool had ceased to function correctly. Orphan Wiki 13:52, 29 May 2020 (UTC)
Also worth mentioning that since it is currently listed on WP:CUV/T, perhaps it should be removed from there as well, despite other inactive tools being listed there as well. lavender|(formerly HMSSolent)|lambast 07:18, 8 June 2020 (UTC)
Yes, I have noticed there are several tools which have ceased to function/be updated listed on there. I've raised the issue on the talkpage to see what people think. Orphan Wiki 23:13, 24 June 2020 (UTC)

JavaScriptEdit

Hi, is this tool has any script that can be pasted in commons.js to use it? Thank you. Empire AS Talk! 08:01, 14 July 2020 (UTC)

Empire AS, STiki is a Java application that you had to download, and is currently offline Ed6767 talk! 15:16, 23 July 2020 (UTC)

Toolforge as a replacementEdit

I'm wondering what would be in the way technically to getting STiki up on Toolforge so that it's back up and it's less likely to go down hard like this in the future? Jerod Lycett (talk) 01:04, 15 July 2020 (UTC)

If the server source is up, I'd be happy to get it running again is the original author doesn't want to Ed6767 talk! 15:15, 23 July 2020 (UTC)
Return to the project page "STiki".