Wikipedia talk:STiki

From Wikipedia, the free encyclopedia
Jump to: navigation, search

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[edit]

STiki Outstanding Bugs and Feature Requests
ID Contact Type Description Status Urgency
T#057 Ugog Nizdast Feature Request Resolve the milestone for blocked editor issue. WP:BEANS. Done in Source Medium-High
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#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
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[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

Thanks, West.andrew.g (talk) 04:46, 14 August 2016 (UTC)

CPU overload issue[edit]

STiki has been unusable for the past 10 days or so (2 weekends and in between), due to the old issue with CPU overload by STiki; multiple restarts don't help. Materialscientist (talk) 03:18, 20 March 2017 (UTC)

@Materialscientist: Thanks for the note. This isn't something I was aware of. Is anyone else affected? My daily reports haven't suggested a broad drop off in classifications. I do recall a CPU overload issue in STiki's past. This was attributed to the fact certain WMF servers were doing markup different than the others (a CSS thing, IIRC). Our parser wasn't prepared for the unseen case, and that thread would end up in an infinite loop. That was nasty to track down, but it did resolve the CPU overload issue. Maybe something similar has occurred again. You are on the most recent STiki version, yes? I'll see if I can duplicate the issue on my own machine. Thanks, West.andrew.g (talk) 16:07, 20 March 2017 (UTC)
I had no problems this morning. — Gareth Griffith-Jones | The Welsh | Buzzard |  19:04, 20 March 2017 (UTC)
The problem still persists, and it is quite annoying. It might take up to several dozen edits to reach the overload state, and some PCs can handle CPU overload, which is why Andrew might not see a drop in usage stats. Materialscientist (talk) 23:44, 20 March 2017 (UTC)
I tend to use STiki in 50-100 edit bursts, and only noticed freezing when attempting to load external links to Safari. L3X1 (distant write) 21:19, 21 March 2017 (UTC)
I have also noticed issues when loading links in the browser (typically Firefox). It is normally fine at first, but once you have loaded a load of links, things really start to chug. I have tried closing tabs down, and it doesn't really help. I have taken to navigating to the important pages without clicking on the links in STiki, which seems to work.
Obviously, this work-around isn't ideal as it negates one of the efficiency-improving features of STiki. Andrew, can you think why it might be having this issue? All I can think is that, possibly, the way you are opening the browser might open a listener for a response from the browser and that STiki ends up running hundreds of listeners.
Yaris678 (talk) 11:16, 22 March 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── @Materialscientist: Is the use of to-browser links a common part of your STiki workflow? Does this seem consistent? Sounds like a starting point. West.andrew.g (talk) 13:52, 23 March 2017 (UTC)

I never use to-browser links in Stiki, and instead copy/paste what I need into the browser. CPU overload is not easy to notice if the user works exclusively in the Stiki window (I frequently switch between Stiki and Firefox windows, and then the overload is easily noticeable). Materialscientist (talk) 22:48, 23 March 2017 (UTC)
Do you avoid the links because you know from experience that they make things worse? Yaris678 (talk) 09:05, 24 March 2017 (UTC)
I avoid them because they involve uncontrollable procedures (of connecting to and manipulating with my web browser), and I often do not want that particular Stiki diff, but something else in the Stiki window. I did not investigate, but I had a feeling that copy/paste also works faster than to-browser links. Materialscientist (talk) 03:15, 28 March 2017 (UTC)

STiki permission request[edit]

Hello, I don't have 1000+ edits in the article namespace as I only became active recently but if you have a look at my edits, its mostly to fight vandalism. Presently, I am using Twinle and STiki will help me both find and revert vandalism. I must mention that I have also applied for rollback permision but its not yet granted (pending possibly due to my low edit count). I got excited recently when I crossed 1000 total edits and instantly came here to check just to realize that they all need to be in the article namespace. I also have nominated a few articles for deletion and most of them have been successful (vandalism, notability are some reasons). I have successfully requested and got blocked several users for vandalism as well. This tool will only help me further fight vandalism. Thank You! Yashovardhan (talk) 17:09, 26 March 2017 (UTC)

 Done -- @Yashovardhan Dhanania: A good base of anti-vandalism work. Not perfect in some of his/her patrolling classifications as per talk page messages, but clearly assumes good-faith. Lots of work in user-talk and article-talk spaces to figure things out and clarify situations puts this over the bar for me. Take your time, and happy reverting. West.andrew.g (talk) 22:04, 27 March 2017 (UTC)
@West.andrew.g: thanks a lot! I'll try to be more clear on talk pages as well! :) Yashovardhan (talk) 04:31, 28 March 2017 (UTC)
@West.andrew.g: Can't login! It says I don't have sufficient permissions. Pleach check and revert! Thanks Yashovardhan (talk) 05:05, 28 March 2017 (UTC)
@Yashovardhan Dhanania: Made a tweak. Try again now, please. West.andrew.g (talk) 13:22, 28 March 2017 (UTC)
@West.andrew.g: Thanks! Its working now! Yashovardhan (talk) 13:34, 28 March 2017 (UTC)

Feature request: Dark skin for STiki[edit]

Thank you for making such useful app, Just one request/query, like there's option to change colors in diff-browser, Is it possible to change the color of main body or add a dark skin?, Current skin is little too bright to work in darker rooms.Redhat101 Talk 01:48, 29 March 2017 (UTC)

@Redhat101: Added to the tracking table as T#061. If there is a global look and feel I can apply that changes everything in a line or two of code, this could be implemented very quickly. If instead I have to implement some option into every single GUI component, we're looking at a much longer timeline. Thanks, West.andrew.g (talk) 13:17, 30 March 2017 (UTC)
@West.andrew.g: Thank you for considering my request.Redhat101 Talk 22:35, 30 March 2017 (UTC)
You might want to try UIManager.setLookAndFeel, since its effects are global and theoretically users would be able to customize themes. Morphdog (t - c) 01:48, 31 March 2017 (UTC)
Addendum: If you want to try a different theme for Stiki without changing anything, run java -Dswing.metalTheme=steel -jar location/of/stiki/in/file/system/STiki_2016_08_14.jar in a command prompt/terminal. Morphdog (t - c) 02:02, 31 March 2017 (UTC)
@Morphdog: Do you know if darker themes exist, especially those that otherwise closely mimic the default Java ones? At quick skim it doesn't seem like any are included by default with Java, but presumably I could package one up with the distribution. Thanks, West.andrew.g (talk)
@West.andrew.g: Most of the looks & feels that I've seen are proprietary, however you can use java -cp to set the classpath for a standalone jar (that users can download, and perhaps make their own look and feel), that way you don't have to package them and get into copyright issues. Morphdog (t - c) 18:14, 1 April 2017 (UTC)

Metadata queue switched to default; CBNG down[edit]

I have made the metadata/STiki queue the default. CBNG has been down for 12+ hours. West.andrew.g (talk) 14:14, 31 March 2017 (UTC)

Is that why I've been seeing some weirdness: STiki shows me all the edits done by one IP so many times I investigate it and end up Innocenting them. Then is sends me to Sausages, where I have to look at an 85 day and 2 hour old revision. I then realise it's not running off Cluebot feed, and after a little bit it works. Does this mean CBNG is back up? Or am I in dangerous territory and should switch back to the revQueue? Thanks L3X1 (distant write) 02:39, 1 April 2017 (UTC)
Don't we have a feature where one can "ignore" the work of a single editor when this happens? The "ignore" last for the duration of the session, IIRC. Kinda busy right now but I vaguely remember recently implementing this. Thanks, West.andrew.g (talk) 14:43, 1 April 2017 (UTC)
Yes it's there, I tend to use for it admins when I run across them. I totally forgot about that feature. L3X1 (distant write) 16:34, 1 April 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Metadata/STiki queue remains the default. While CBNG is running, the IRC feeds from which STiki consumes the scoring remains down. I have notified the CBNG team. West.andrew.g (talk) 17:18, 3 April 2017 (UTC)

 Done -- CBNG feed is back up and running; I've restored it as the default. West.andrew.g (talk) 01:24, 7 April 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Not done -- No so fast. CBNG IRC is down again and STiki hit-rates are suffering, so I've made the metadata queue default again. West.andrew.g (talk) 16:17, 10 April 2017 (UTC)

Still down. I've pinged the authors directly (in addition to the talk page message). Thanks, West.andrew.g (talk) 14:04, 12 April 2017 (UTC)
And I am receiving one-year-old STiki edits for review now: how come?! anyone else the same?Super48paul (talk) 11:09, 15 April 2017 (UTC)
Because the worst-scoring still active edit is 1-year old. The metadata queue scoring has no notion of time-decay (although such a feature could be a valid one). Indeed, people have reverted vandalism that is 1+ years old in that queue. However, given that it is now default I've decide to eliminate non-recent edits from the queue. We'll see if that bumps up overall hit-rate performance (which has been hovering around a quite low 20% since CBNG's IRC feed went down). Thanks, West.andrew.g (talk) 01:13, 16 April 2017 (UTC)
Still getting hits as old as 85 days on the CBNG queue. lavender|(formerly HMSSolent)|lambast 00:36, 18 April 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── @HMSLavender: @Super48paul: The CBNG queue is down, and that is precisely why the STiki queue is set as default. You shouldn't be using the CBNG queue since there is nothing fresh going in, and anyone who is using it will just be driving deeper and deeper into a backlog of lower-probability-of-vandalism edits. P.S. does someone else want to give the CBNG authors a poke and see if they can get the IRC running again? The bot itself is running, and their IRC server is up, so I don't understand the difficulty, there. West.andrew.g (talk) 13:15, 18 April 2017 (UTC) ──────────────────────────────────────────────────────────────────────────────────────────────────── Not done -- The CBNG IRC feed continues to be down. I've contacted the authors again. West.andrew.g (talk) 17:44, 24 April 2017 (UTC)

Yet Another STiki permission request[edit]

I stumbled across this tool when it flagged a page that I maintain and watch due to an edit by a self-interested party. I was very impressed that ML had correctly identified the possibility of vandalism in such a subtle change. So I've downloaded the jar to play with it to satisfy some idle curiosity. I've very little experience editing Wikipedia, having only done a handful of edits over the years, but I operate in good faith and I'm judicious with changes.

Unsigned request by User:Bill Michaelson --ProgrammingGeek talktome 00:30, 19 April 2017 (UTC)

Bill Michaelson, there is no doubt that you are a good editor, but starting with Twinkle or enrolling here might be good to get some counter vandalism experience first. Just my 2¢ ProgrammingGeek talktome 00:37, 19 April 2017 (UTC)

@Bill Michaelson: Thank you for your interest... and I second ProgrammingGeek's suggestion. We normally require a couple hundred article namespace edits, slightly variable depending upon vandalism focus. If you are interested in this kind of work, WP:CVUA training would be the fast track. West.andrew.g (talk) 00:12, 20 April 2017 (UTC)

Thanks for your response. Too high a bar for me; I've got other priorities. If Wikipedia had similar barriers to entry its history might have been different. Good luck in your quest for balance in crowd-sourcing. — Preceding unsigned comment added by Bill Michaelson (talkcontribs) 11:42, 20 April 2017 (UTC)