Wikipedia talk:STiki

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.

STICKY: Known Bugs and Feature Requests

STiki Outstanding Bugs and Feature Requests

ID	Contact	Type	Description	Status	Urgency
T#016	Yaris678	Feature Request	As a consequence of implementing rollback across STiki, sometimes null diffs are displayed, where across multiple edits a user makes no cumulative change. These are uninteresting and therefore should not be displayed to end users.	Pending	Medium
T#017	DBigXray	Minor Mod.	Changes to the metadata panel. Textual changes to clarify that "comment" means "edit summary". Also considering re-organization of fields to bring edit summary to greater prominence and possibility delete "RID" field.	Pending	Medium
T#018	Yaris678	Feature Request	Modifications to the warning system. Better automated logic for warning increments, especially as it pertains to month boundaries. Add option for dialogue box before severe warnings distributed and AIV reports sent.	Pending	Medium
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#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 the 2012-07-18 release

Nothing earth-shattering in this release. However, with no pressing work on the horizon I though it wise to go ahead and push out these few minor improvements we've accumulated lately. As always, thanks for your continued support. West.andrew.g (talk) 20:46, 18 July 2012 (UTC)

• A "recent usage statistics" option has been added to the "Queue" menu. This reports basic numbers about STiki/queue use over the last 1/6 hours. As high rates of use can cause queue exhaustion and lower hit-rates, users can interpret these statistics to determine how best to allocate their STiki usage time and queue choice (T#014).
• Minor changes to the "excessive pass use" and "don't template the regulars" message dialogues per discussion at Wikipedia_talk:STiki (see archives).
• The message displayed in the diff browser that indicates rollback situations (i.e., 2+ edits are encapsulated by the diff and would be reverted) has been revised per Wikipedia_talk:STiki (see archives).
• The default comment left with AGF reverts has been changed per a talk page request from "good faith revert..." to "reverting good faith edit(s)..." Custom AGF messages will need to be re-authored.

fallback to port 80?

Some users are unable to use STiki because port 3306 is blocked. Would it be possible to make STiki default to port 80 in this case? This would be very useful. Thanks! --Ixfd64 (talk) 23:56, 17 August 2012 (UTC)

Notice that this is in the bug/feature table as T#004. Assuming you (or whomever) can't configure the firewall, proxy tunnelling would be one possible solution. A true solution for this is not difficult. Someone just needs to wrap all the native SQL calls to server-side stored procedures with PHP scripts, constructing an API to pass parameters and retrieve results. At the current moment, I have a few other (and too many) things on my plate. I will be frank in saying *I* won't be getting around to this any time soon; though I would be happy to assist anyone interested. Thanks, West.andrew.g (talk) 07:00, 18 August 2012 (UTC)

Wow. Spoken like a true computer scientist. • Jesse V.^(talk) 16:32, 21 August 2012 (UTC)

Question

I downloaded the advanced version of STiki but couldn't figure out which one is the right STiki software (since there are more files and folders). Btw, are there more options like section blanking in this than in the current version 2.1? Torreslfchero (talk) 06:52, 23 August 2012 (UTC)

Hi, I've realised that the page was misleading before. Where is said "advanced users" what it meant was "software developers". So I have changed it now.

Is that what you meant? Or did you mean that you would like to look at the code but you don't know where to start? That is a situation I find myself in.

Yaris678 (talk) 12:46, 24 August 2012 (UTC)

I meant are there more options on STiki like section blanking, adding spam links etc? Torreslfchero (talk) 12:53, 24 August 2012 (UTC)

More concisely here: "no". The formerly "advanced version" is/was the exact same as the "normal" one. The "advanced" download just provided the source code for the "normal" version so individuals can: (1) See how it functions (i.e., audit to ensure I am not stealing your password), (2) re-use or extend the code in their own projects. For the casual user there is nothing of interest here and Yaris' relabelling was appropriate. West.andrew.g (talk) 15:12, 26 August 2012 (UTC)

I think the answer to your question is that there are a number of different queues that you can access. These are accessed using "New queue" at the top of the window. Section blanking is a type of vandalism and so will most likely be caught by the "STiki (metadata)" queue or the default "Cluebot NG" queue. Spam links are different, they have a special queue just for them! Select the anti-spam queue. This even changes the buttons so you now have one marked "spam" instead of "vandalism". When it warns a user, it gives the spam warning, rather than the vandalism warning. Yaris678 (talk) 13:51, 24 August 2012 (UTC)

Thanks for the explanation. Torreslfchero (talk) 14:50, 24 August 2012 (UTC)

No problem. Yaris678 (talk) 15:07, 24 August 2012 (UTC)

Say more about choosing queues?

All,

On the WP:STiki page, do we want to say more about choosing queues? At the moment it lists the available queues in a table in the lead but it doesn't even say how to choose one? Perhaps we should add a subsection to WP:STiki#Using STiki. This could obviously mention aspects such as queue exhaustion and the new feature that indicates which might be the best queue to go for.

Yaris678 (talk) 15:07, 24 August 2012 (UTC)

For my part, I think it would confuse, rather than help newcomers. Best to let things progress as they did for me: after using STiki for several days, I started clicking on the menu just to find out what happens. It all seemed self-explanatory. As a non-technical/new to Wikipedia person, I believe information should be carefully rationed so as not to bewilder.

Sincerely -- Gareth Griffith-Jones (talk) 17:35, 24 August 2012 (UTC)

I wouldn't mind built in functionality so that after say, 200 reviewed diffs, STiki presented a one-time dialogue box introducing the different queues and asking if an editor would like to try a new one. Ocaasi ^{t | c} 20:22, 24 August 2012 (UTC)

Like I like Ocaasi's idea... that would make sense. Theopolisme :) 03:36, 25 August 2012 (UTC)

Certainly feasible. Consensus on the classification count? Any specific bits for the message other than the obvious? Thanks, West.andrew.g (talk) 15:16, 26 August 2012 (UTC)

I think anything between 50 and 200 edits would be a reasonable point to explain this feature. Arguably, Andrew could create a whole "Did you know" feature that explained some of the finer points as the user is going along. Maybe a different fact every 100 edits? Here are some suggestions:

Did you know...

...that the comments box in the bottom-left corner lets you tweak your response?

You can choose whether or not to issue a warning and change the edit summary made in the revert. It has two tabs - one for the message when reverting vandalism and one for the message when reverting good-faith edits.

OK

Did you know...

...that you can select from a number of different queues using the "Rev. Queue" menu?

"Cluebot-NG", "STiki (metadata)" and "WikiTrust" detect vandalism in different ways. "Link Spam" detects the addition of links that may have been added to promote a website, rather than improve the encyclopedia.

OK

Did you know...

...that a warning is not issued to an IP address if the vandalism is more than 24 hours old?

This feature is intended to prevent confusing messages being sent to the users of shared IP address.

OK

Given the discussion below, I would also say that we could say something about the fact that STiki can report users to AIV... altough the way that works is going to change soon so maybe we should wait until the new system comes in and think if any additional info is needed.

Yaris678 (talk) 18:36, 26 August 2012 (UTC)

Beautiful template work up above Yaris. I have no issue with implementing this (as an default-enabled option) if folks want to write out and iterate over the wording of 10+ such facts. I'm tempted to say "let's create a subpage", but no-one will watch and its probably preferable to create a nice enumerated list here. I do imagine that a lot users get to several hundred editors without drilling too deep into WP:STiki or its documentation (hotkeys must be a DYK! I can't imagine using STiki without them). Thanks, West.andrew.g (talk) 08:01, 27 August 2012 (UTC)

Small point, but surely it is 24 hours, isn't it? Cheers!

Sincerely -- Gareth Griffith-Jones (talk) 09:13, 27 August 2012 (UTC)

Correct, on this minor point. West.andrew.g (talk) 08:35, 28 August 2012 (UTC)

CVUA student access request

Hi, may I request access for my CVUA student Zaldax (talk · contribs) please? Thanks in advance, Mdann52 (talk) 15:34, 23 August 2012 (UTC)

 Done - Sorry for the delay, travelling through CDG en route to WikiSym!. Thanks, West.andrew.g (talk) 10:49, 24 August 2012 (UTC)

Automatic AIV reporting

See the "Possibly compromised account?" section of the current version] of WP:ANI and the "68.185.89.83" section of the current version of User talk:Gareth Griffith-Jones. It's possible to set up this tool so that it reports people to WP:AIV without you editing the page, and this can lead to confusion. West.andrew.g is already looking into the issue, but this is probably something that all users should know about. Nyttend (talk) 00:37, 25 August 2012 (UTC)

Responding on the WP:ANI thread of this. Thanks, West.andrew.g (talk) 15:22, 26 August 2012 (UTC)

Erg, forget that, it has already been archived and my addendum doesn't really warrant reviving it. It's not as if STiki makes "magical" AIV posts with *no* notification; as mention of AIV will be made in the "last revert" panel when it happens. As our previous thread (now in Archive #8) discusses this should be made a more concious and pro-actively initiated action. No debate. Out of curiosity, how does Huggle handle this? Thanks, West.andrew.g (talk) 07:53, 27 August 2012 (UTC)

Huggle gives both the option to either submit a report to AIV regardless of warning count on the editor's talk page, as Huggle places the continuing edits of the editors you've personally reverted recently at the top of the queue (ie. rapid edit vandals that need to be immediately blocked); and if the user already haves one of the uw4 templates on the user's talk page (such as subst:uw-vandalism4im or subst:uw-delete4) it will prompt or ask the user that the editor has already been issued a final warning, and would you like to report it to AIV instead. You can either report it, place another warning, or not place a warning and skip to the next edit. The immediately report is one of a number of buttons located at the top of the screen. It will not report an editor without the editor specifically clicking that they want a report sent. Calmer Waters 02:57, 28 August 2012 (UTC)

CVUA Student Access Request

I would like to request access for my student Fox2k11 (talk · contribs) Dan653 (talk) 01:47, 28 August 2012 (UTC)

User only has 113 edits to mainspace. using Stiki requires 1,000 mainspace edits or rollback rights. Kudpung กุดผึ้ง (talk) 02:27, 28 August 2012 (UTC)

(talk page stalker) Um.... at Wikipedia talk:Counter-Vandalism Unit/Academy/Archive_2#New_Requirements_for_using_STiki, the following comment was left...

I would also like to add that Criteria 3 will be specially accepted if the instructors of CVUA request it for their CVUA trainees. --DBigXray"

Please reconsider - thanks - Mdann52 (talk) 09:15, 28 August 2012 (UTC)

When numerical requirements are not met, approval decisions fall to (a) myself, and (b) others who I have delegated this right to (via DB-write access). I tend to be quite generous in this regard, but I'm not particularly inspired by this discussion. It seems "Dan" has asked "Fox" to read WP:VANDAL; he/she responds that this has been completed. Fox has no (or very very few) vandalism reverts in his history but has done some work at AFC. Don't CVUA users generally distribute "lessons" to students? If one of these were complete, I would not hesitate to approve. As a sign of good-faith, I am going to cautiously approve this request (and watch Fox's talk page). I don't want to see a trend develop where certain CVUA instructors become an easy conduit by which to obtain STiki access (though I am making no accusation of that here). Thanks, West.andrew.g (talk) 09:40, 28 August 2012 (UTC)

 Done -- Approved -- West.andrew.g (talk) 09:40, 28 August 2012 (UTC)