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#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 2013-01-26 release

Greetings STiki users. Below is the CHANGELOG for the 2013_1_26 release (available for download on WP:STiki). I have done some changes to my hardware and OS, so I am hopeful we do not run into any issues with Java versioning. I am excited there is some new GUI functionality in this release. This is likely to be the final version I release as a graduate student (!), but as always, I appreciate your suggestions and bug fixes! Thanks, West.andrew.g (talk) 03:38, 26 January 2013 (UTC)

• When making an "AGF revert" classification, a dialog will now appear that allows users to post custom notifications/explanations to the offending user's talk page. This dialog can be disabled via the "options" menu. The dialog contains a text field in which any message can be authored, but more likely, user's will take advantage of the pre-written/template-esque options provided in a drop-down menu. There is also the capability to store custom messages if an editor is so inclined. Overall, it is hoped this will result in less WP:BITE behavior towards those being reverted (T#019).

• The "edit properties" panel now displays the relevant "permissions" or "groups" which the editor under inspection has obtained. These are placed parenthetically next to the user name, and are listed below. If a registered user has none of these, then "no permissions" will be displayed. No information is displayed about IP editors (as they can have no such permissions) (T#022).
  • "autoconf" -> autoconfirmed
  • "conf" -> confirmed
  • "review" -> reviewer
  • "rb" -> rollbacker
  • "admin" -> sysop

• Minor organizational changes to the "edit properties" window to bring greater prominence to the "summary" and "editor" fields, since these are often vandalism indicators (T#024).

• Users can now generate a "live" leaderboard for their own viewing purposes inside the tool, via "Rev. Queue" -> "Generate leaderboard". It is a slightly simplified version of the one at WP:STiki/leaderboard, but should serve the edit-count-itis folks quite nicely until the nightly updates are made on Wikipedia (T#023).

• A previous change prevented "null diffs" from being pointlessly displayed to end users. That change essentially caused such RIDs to be ignored. This caused them to stay in the queue, often accumulating and forcing the program to process (but re-skip them) at start-up. A fix now dequeues null diffs upon their discovery.

• The "WikiTrust" and "Link Spam" queues have been disabled. The former is dependent on third-party computation which has been broken for some time (and no one ever used the queue, anyways). The link spam queue is not really used either, but that queue is computed on a local machine. The primary reasoning for disabling it is cost. The classification model is dependent on queries to the Alexa API, which are not free, and we make many thousand monthly ($65+) (T#021).

Feature Request

After going through recent changes old school with the help of twinkle, this is a great improvement. But more warning templates would be great, because we can't choose a level of warning, nor most of templates for specific kinds of disruptive editing. If I'm wrong, could you tell me how to get more warning templates? Thanks! ―Rosscoolguy 23:54, 7 February 2013 (UTC)

Hi! When reverting AGF revisions with STiki, I always use WP:TWINKLE –
 – Gareth Griffith-Jones |The Welsh Buzzard| 23:57, 7 February 2013 (UTC)

Well, if you press the "vandalism" button the level of warning will automatically increment based on the recent vandalism warnings on the user talk page. This is a practical necessity -- via this progression is how the blocking process usually proceeds. Vandalism is "vandalism" and when damage is intentionally performed, I don't think we should be too subtle in parsing out its motivations. However, if you classify an edit as a "good faith revert", a dialogue should pop that provides more subtle, descriptive, and customized options. Similarly, as Gareth mentioned, Twinkle actions fired from STiki hyperlinks can always cover the corner cases... Thanks, West.andrew.g (talk) 04:44, 8 February 2013 (UTC)

Little Error Report

When choosing an AGF template, for the template called "unencyclopedic details", I noticed a small error, in which the words "may" and "collaborate" were connected together. Cheers, Kevin12xd (contribs) 01:51, 8 February 2013 (UTC)

Thanks, the error will be corrected in the next distribution. As has been mentioned here and elsewhere, anyone who has suggestions for existing and/or novel template suggestions will certainly be entertained. Thanks, West.andrew.g (talk) 04:46, 8 February 2013 (UTC)

Hi Andrew, As I suggested at Wikipedia talk:STiki/Archive 10#General message, you could facilitate further suggestions by creating a page such as WP:STiki/Good-faith-revert messages.

I also noticed some typos and there's also a few wording changes I could suggest. But it would be a lot easier make these suggestions if the text was already on a page in this wiki. That would also, obviously, make it easier to do a diff, make further suggestions etc.

Yaris678 (talk) 11:41, 14 February 2013 (UTC)

As I believe I also said there, I support this notion and will integrate any changes that the community makes to the text(s) (or any new templates they come up with). Be bold, if you wish, and copy-paste what we already have inside STiki onto that wiki page (I'm sure you can come up with a better way to format it than I can). Thanks, West.andrew.g (talk) 13:50, 14 February 2013 (UTC)

OK. It may be a while until I am on a machine that lets me use STiki but I'll set something up next time I have an opportunity (unless someone else beats me to it). Yaris678 (talk) 15:01, 14 February 2013 (UTC)