Wikipedia talk:STiki

Known Bugs and Feature Requests

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)

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)

STiki permission

@West.andrew.g: I'm requesting it because I'm in the CVUA and they said it would be good if you could increase your edits because sTiki is going to help you. But since I'm still bit far from 1000 mainspaces, I would like it because it will help me in the CVUA. Thanks. The4lines (talk) 15:44, 24 November 2019 (UTC)The4lines

 Done -- @The4lines: Permission granted. West.andrew.g (talk) 14:50, 29 November 2019 (UTC)

Requesting STiki Permission for CVUA

@West.andrew.g: Firstly, thank you for creating such tools. I would like to request access for this tool in order to assist me with certain tasks assigned to me in the CVUA programme along with the fact that it makes life a million times easier in reverting vandalism. I'll be 100% honest with you, I was recently unblocked about a week ago after an indefinite ban of sock puppetry and also had a rollback rights request denied (I originally wanted the rollback rights for Huggle, but they were denied and I was told to finish CVUA + Establish myself as an editor in good standing). After being given a second chance by the community, I've started contributing by helping out with anti-vandalism along with enrolling for a CVUA programme and I really feel this tool would be of great assistance, especially to help me in the next task of finding pages which may need protection requested on them MikeTheEditor104 (talk) 16:06, 29 November 2019 (UTC)

@MikeTheEditor104: Greetings, and sorry for a slow response after a holiday weekend for me. I don't have the time to delve into the subtleties of your past, nor am I on an expert on user policy matters -- but I am inclined to assume good faith. As long as (@CASSIOPEIA:) will drop by here and vouch for you (this is your CVUA "trainer", yes?) I'll grant the permission. Thanks, West.andrew.g (talk) 14:07, 2 December 2019 (UTC)

West.andrew.g Good day. I have accepted on the request from @MikeTheEditor104: as the WP:CVUA trainer to give him a fresh start after he had been granted an indef unblock for sock 5 years ago. As he has limited mainspace edits since he is back and it would be a little bit difficult for him to sport 3RR edits and pages needed protection from new edit log alone. Having the STiki counter vandalism tool would definitely help him to work on CVUA program and would appreciate if you would grant him the access for the tool. Thank you. CASSIOPEIA^(talk) 14:44, 2 December 2019 (UTC)

 Done -- @MikeTheEditor104: Access granted. West.andrew.g (talk) 22:59, 2 December 2019 (UTC)

Automated edits

Hello. I am editing using STIKI. An anonymous IP appears to be making automated edits (see anonymous IP contributions here). On December 11, 2019 UTC, they have made about 300 single edits on approximately 300 Wikipedia pages that describe operas. They have placed the italic title template {{italic title}} on each page. STIKI is following these edits so I am going through them one by one.

These edits appear to be correct according to WP:ITALICTITLE and MOS:ITALICTITLE. So, I am marking each one as innocent. Still, this seems kind of disruptive if 300 stubs did not have italicized titles in the first place. Also, is an anonymous IP allowed to use a bot on Wikipedia? And where is the appropriate venue on Wikipedia to address this? I'm thinking it would have to be ANI or WP:AN. ---Steve Quinn (talk) 06:22, 12 December 2019 (UTC)

I have also queried them on their talk page (here) just before I posted the above. ---Steve Quinn (talk) 06:27, 12 December 2019 (UTC)

@Steve Quinn: Bot accounts need to be registered 2x: (1) a registered account, and (2) a registered account registered as a bot, unless editing in one's own userspace. I am nowhere near an expert on policy, but AN/ANI seems like a reasonable starting place. As far as STiki is concerned, I believe there is an "ignore user" function/list somewhere in the software, so you don't have to endlessly review repetitive cases like this. West.andrew.g (talk) 14:44, 12 December 2019 (UTC)

@West.andrew.g:. Thanks very much for your response. It was very helpful. ---Steve Quinn (talk) 17:16, 12 December 2019 (UTC)

Username change

Hi, sorry for not notifying about my username change, if you can reassign my STiki contributions from my previous username (EdisonLin27) to this username that would be great. Sorry for any confusion I've caused and thanks for creating this tool! Edi7 ^{(Message Me! • 📜)} 11:11, 28 December 2019 (UTC)

 Done -- @Edi7*: 1141 contributions re-mapped. Changes will appear when leaderboard regenerates within 24h. Thanks, West.andrew.g (talk) 14:06, 28 December 2019 (UTC)

STiki request

@West.andrew.g: hello. Despite me being under 1,000 mainspace edits, I would like to request permission to use STiki because (1) My recent changes tab is not working. I have started a discussion, which you can see here, and (2) CASSIOPEIA told me here that I should contact here to try and gain STiki powers. Thanks, Thatoneweirdwikier Say hi 06:23, 7 January 2020 (UTC)

 Done -- @Thatoneweirdwikier: Permission granted. Thanks, West.andrew.g (talk) 21:29, 7 January 2020 (UTC)

CBNG has been down

CBNG has been down for at least 2 days (at least in IRC land). I'm making the "metadata" queue the default until its back up. West.andrew.g (talk) 11:38, 18 January 2020 (UTC)