This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |
Hey Andrew. I think Stiki is great and I use it a lot. Here's another bug report for a small bug. There's a small error in the edit summary that Stiki automatically generates when creating a report to AIV. The edit summary looks like this (Reporting 75.151.66.225 for repeated vandalism, found using STiki.), where the IP adress is a link. The problem is that this link is broken, it incorrectly leads to http://en.wikipedia.org/wiki/Special:Contributions/:75.151.66.225. The correct address would be http://en.wikipedia.org/wiki/Special:Contributions/75.151.66.225 (the difference is the colon before the IP adress). For example see this diff [1]. I hope that you can fix it in one of the future versions. Thanks for making Stiki and good luck with your research. Arthena (talk) 19:02, 13 January 2011 (UTC)
Great job on the new version!
After about 50 reviews with the Cluebot-NG queue, I clicked Innocent, the button highlighted, and the program froze. Couldn't click anything else or exit. Had to force quit. CPU usage was 90% idle while hung. I restarted and it immediately resumed pulling reviews. I was using OS X. — UncleDouggie ( talk) 06:14, 26 January 2011 (UTC)
I marked a review as innocent in the Cluebot-NG queue, later switched to WikiTrust, and got the same review again! I understand why, but it's annoying. How many others am I re-reviewing that someone else has already judged from a different queue? — UncleDouggie ( talk) 06:24, 26 January 2011 (UTC)
STiki just gave me my own revert from the Cluebot-NG queue, which is where I also did the revert from. Not a big issue if that's the way it needs to work. — UncleDouggie ( talk) 04:05, 27 January 2011 (UTC)
... for unexpected maintenance. Hope to have it back up later today. Thanks West.andrew.g ( talk) 06:49, 28 January 2011 (UTC)
I take it that the server is down. I just got a small, blank pop-up window with the title of "Error: Internet connectivity is required". However, I had good Internet service both before and after the window appeared. I couldn't close the pop-up or STiki itself; I had to force quit the app. Upon restarting, I got an immediate error that there was no connectivity to the back-end and the app then gracefully exited. It would be nice to handle this more gracefully when it happens mid-session. — UncleDouggie ( talk) 06:52, 28 January 2011 (UTC)
Now it starts up and just sits there without ever opening any windows. At least it lets me quit gracefully. — UncleDouggie ( talk) 07:06, 28 January 2011 (UTC)
I just got on and was using the CBNG queue. STiki gave me a rather obviously correct revert by CBNG itself to review! Is this because others have drained the CBNG queue to the point that it didn't have anything better to show me, or did CBNG somehow rate its own action as high risk? It would be really nice to see the queue scores in the STiki client to help fine-tune CBNG and other queues. — UncleDouggie ( talk) 04:50, 31 January 2011 (UTC)
The following is the CHANGELOG from the 2011/01/31 release:
Thanks, West.andrew.g ( talk) 08:23, 31 January 2011 (UTC)
Nice work on the new version. Cool to see it coming along so well and quickly. My thought is that if a common vandal-fighter comes to this page, and doesn't really care about documentation, or machine learning, or anything really--they just want the link to the download with a date telling them the version--that it could be a little more user-friendly to find it on the page. Vandal-fighting is a salesmanship game on Wikipedia since there are so many competitors, and while I'm glad STiki hasn't been overrun by hordes of itchy fingers, the program is so superior to others that it really deserves the widest userbase possible. That's my thought. Thanks again, Ocaasi ( talk) 03:34, 1 February 2011 (UTC)
STiki scored more than 1000 reverts in the last 24 hours. Pretty sure this is a record day. Thanks to all the user-base! West.andrew.g ( talk) 05:12, 4 February 2011 (UTC)
Yet another old problem is back. After restarting STiki, the first edit was this one, which I had clicked innocent on about 25 minutes earlier in my last session (long before the revert failures above started happening.) Both edits were from the CBNG queue. — UncleDouggie ( talk) 22:42, 6 February 2011 (UTC)
Is it just my computer, or does STiki not show edit summaries? If this is the case, it should be fixed; otherwise, there is a greater chance of reverting legitimate edits. -- Ixfd64 ( talk) 23:57, 13 February 2011 (UTC)
STiki doesn't seem to want to warn offending users at the moment. I've reloaded it, but the problem is still there... Orphan Wiki 00:14, 16 February 2011 (UTC)
I sometimes need to copy the name of an article out of the STiki window. The only thing selectable is the bold name at the top of the diff window. However, this leads to a confusing mess. — UncleDouggie ( talk) 23:14, 5 February 2011 (UTC)
An old problem is back. STiki just gave me this edit. I clicked vandalism (with a custom edit summary and no user warning). However, STiki didn't perform the rollback and instead said that I was beaten to the revert. I then did a Twinkle rollback instead. I then noticed that it had been 6 minutes since my previous revert, but I know that I had several cases of vandalism during that time. I just hadn't paid much attention to the STiki revert status pane because it often lags significantly. Beyond the obvious problem of why STiki thought I was beaten when I wasn't, we should make the revert failure condition much more prominent like putting it in a red font. By the time I noticed the problem, I had no way to go back to the edits I had recently classified. The only way out of this situation based on my past experience is to close and reopen STiki. — UncleDouggie ( talk) 22:36, 6 February 2011 (UTC)
For the second time one of my edits has been dinged as vandalistic by an inexperienced editor using STiki, and for the second time this editor ( Ankit Maity ( talk · contribs)) shows a pattern of abusing the tool to mass-revert non-vandalistic edits and label them as vandalism. Either this tool needs some serious improvements (How about a whitelist?) or its use needs to be restricted to more experienced editors.-- ShelfSkewed Talk 18:22, 19 February 2011 (UTC)
Just thought I'd clarify the situation. Ankit Maity, it was not I who declined your request for rollback rights, it was declined by Skier Dude. This was because it was thought that you weren't quite ready yet to be granted rollback rights, and also based on the evidence that you weren't quite used to automated tools (I simply provided a link to this discussion to help in the decision process). I didn't do this to prevent you from earning rollback rights, I did it to make sure the right decision was made at that particular time. Nevertheless, that doesn't mean you couldn't be granted rollback rights in time to come. I suggest you maybe keep on patrolling the recent changes old school style? That way you can be certain of what really needs reverting and what doesn't, thus proving to the people over at Requests for Rollback proof that you deserve the tool. If you would like further help with all this, I am more than happy to assist you. Just give me a shout on my talkpage. Regards, Orphan Wiki 11:46, 25 February 2011 (UTC)
A very minor release here. As far as GUI users are concerned, it only addresses one issue raised by UncleDouggie (pertaining to copy-paste of text from STiki). Regardless, I have no major changes on the immediate horizon, so I thought I'd go ahead and push this out.
CHANGELOG:
Thanks for everyone's continued support, West.andrew.g ( talk) 00:39, 24 February 2011 (UTC)
STiki seems to be mostly detecting the level of warning already given to a vandal and responding appropriately. However, take a look at User talk:Tosspot345 and it didn't seem to have worked properly. I noticed that there were lots of messages and posted on WP:AIV manually. I don't think it was just STtiki that got confused, ClueBot NG seems to have got confused too. Any thoughts? Yaris678 ( talk) 19:40, 1 March 2011 (UTC)
During this conversation, it was suggested that only rollbackers should be allowed to use STiki. The conversation then got distracted by a specific case... so I would like to return to the general point.
I think that only rollbackers should be able to use STiki. This wouldn't just reduce abuse and errors, it would also ensure that the learning aspects of STiki isn't learning from false data.
I think that if someone logs in to STiki with an account that doesn't have rollback rights, it should politely suggest that the user request them. Something like...
"You do not appear to have rollback rights, which are now required to use STiki. If you have a contribution history that demonstrates an ability to distinguish well-intentioned edits with minor issues from unconstructive vandalism, please request rollback rights."
Yaris678 ( talk) 09:58, 9 March 2011 (UTC)
STiki is well-built and the project page's wording makes it sound high-tech. It's definitely simpler than Huggle, but that's possibly a good thing, especially for newer vandal fighters. However, it would be nice if the screen displayed the change in bytes (e.g., "-566" or "+44") like Huggle does. Guoguo12 --Talk-- 20:20, 14 March 2011 (UTC)
It would be nice if you could decide if STiki adds articles you edit through it to your watchlist. I assume most editors wouldn't want most articles edited this way to their watchlists. I know I don't. No More Mr Nice Guy ( talk) 16:21, 1 March 2011 (UTC)
Thank You. I love STiki and this will make it even better.-- Nyswimmer ( talk) 17:39, 1 March 2011 (UTC)
The changes work for me-- Nyswimmer ( talk) 19:01, 1 March 2011 (UTC)
Hello STiki users, and thanks for your continued use of my tool.
As you may have noticed, the "ClueBot NG" queue has not been updated in some time. Initially, this was the result of the ClueBot NG being completely offline. Bot service has since been restored. However, the IRC feeds on which STiki depends to enqueue scores have not yet been restarted. I have raised this as an issue with the developers (see User_talk:ClueBot_Commons#IRC_Feeds) -- but I am yet to receive a response. Perhaps some others can pile on over at that talk page to see if we can't make some traction.
In the meanwhile, I encourage STiki users to switch to the "metadata" queue, which is actively processing/en-queuing fresh edits. You are much more likely to find vandalism in this stack. I also realize, that due to to the CBNG-queue being down, that STiki may take a rather lengthy period of time to load/initialize. I apologize. Fixes in the near future will allow me to adjust the "default" queue on the server to circumvent such issues. Look for these changes in a couple weeks time -- I am quite bogged down at current trying to prepare some academic work for WikiSym. Thanks, West.andrew.g ( talk) 22:16, 22 March 2011 (UTC)
My copy of STiki seems to be picking up the ClueBot NG feed now. I guess the problem has been fixed. Yaris678 ( talk) 17:24, 25 March 2011 (UTC)
Sometimes using STiki, when I click "Vandalism (Undo)", the revert doesn't go through. Sometimes the reverts do work, but the warning doesn't go through, even when the "Warn offending editor" check box is checked. What causes this? - Porchcrop ( talk| contributions) 01:38, 22 April 2011 (UTC)
If I make a classification using one of the built-in hotkeys (alt-v, alt-p, alt-i), it seems like this classification is not only applied to the current diff, but also immediately to the next diff. It's not a big problem, I just have to use the mouse instead. Arthena (talk) 07:11, 24 April 2011 (UTC)
Greeting, STiki users. Over the next several hours (possibly stretching into the next day), the STiki database will be undergoing some maintenance tasks. This could result in intermittent dysfunctional behavior and downtime. Please do not report these as bugs until everything stabilizes.
These updates: (1) should result in some minor speed improvements in the client-side, (2) lay the foundation for the inclusion of the "anti-link-spam" queue, and (3) help prevent "forced updates", and keep legacy versions of STiki in good working order, even as improved versions get rolled out. Thanks, -AW
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |
Hey Andrew. I think Stiki is great and I use it a lot. Here's another bug report for a small bug. There's a small error in the edit summary that Stiki automatically generates when creating a report to AIV. The edit summary looks like this (Reporting 75.151.66.225 for repeated vandalism, found using STiki.), where the IP adress is a link. The problem is that this link is broken, it incorrectly leads to http://en.wikipedia.org/wiki/Special:Contributions/:75.151.66.225. The correct address would be http://en.wikipedia.org/wiki/Special:Contributions/75.151.66.225 (the difference is the colon before the IP adress). For example see this diff [1]. I hope that you can fix it in one of the future versions. Thanks for making Stiki and good luck with your research. Arthena (talk) 19:02, 13 January 2011 (UTC)
Great job on the new version!
After about 50 reviews with the Cluebot-NG queue, I clicked Innocent, the button highlighted, and the program froze. Couldn't click anything else or exit. Had to force quit. CPU usage was 90% idle while hung. I restarted and it immediately resumed pulling reviews. I was using OS X. — UncleDouggie ( talk) 06:14, 26 January 2011 (UTC)
I marked a review as innocent in the Cluebot-NG queue, later switched to WikiTrust, and got the same review again! I understand why, but it's annoying. How many others am I re-reviewing that someone else has already judged from a different queue? — UncleDouggie ( talk) 06:24, 26 January 2011 (UTC)
STiki just gave me my own revert from the Cluebot-NG queue, which is where I also did the revert from. Not a big issue if that's the way it needs to work. — UncleDouggie ( talk) 04:05, 27 January 2011 (UTC)
... for unexpected maintenance. Hope to have it back up later today. Thanks West.andrew.g ( talk) 06:49, 28 January 2011 (UTC)
I take it that the server is down. I just got a small, blank pop-up window with the title of "Error: Internet connectivity is required". However, I had good Internet service both before and after the window appeared. I couldn't close the pop-up or STiki itself; I had to force quit the app. Upon restarting, I got an immediate error that there was no connectivity to the back-end and the app then gracefully exited. It would be nice to handle this more gracefully when it happens mid-session. — UncleDouggie ( talk) 06:52, 28 January 2011 (UTC)
Now it starts up and just sits there without ever opening any windows. At least it lets me quit gracefully. — UncleDouggie ( talk) 07:06, 28 January 2011 (UTC)
I just got on and was using the CBNG queue. STiki gave me a rather obviously correct revert by CBNG itself to review! Is this because others have drained the CBNG queue to the point that it didn't have anything better to show me, or did CBNG somehow rate its own action as high risk? It would be really nice to see the queue scores in the STiki client to help fine-tune CBNG and other queues. — UncleDouggie ( talk) 04:50, 31 January 2011 (UTC)
The following is the CHANGELOG from the 2011/01/31 release:
Thanks, West.andrew.g ( talk) 08:23, 31 January 2011 (UTC)
Nice work on the new version. Cool to see it coming along so well and quickly. My thought is that if a common vandal-fighter comes to this page, and doesn't really care about documentation, or machine learning, or anything really--they just want the link to the download with a date telling them the version--that it could be a little more user-friendly to find it on the page. Vandal-fighting is a salesmanship game on Wikipedia since there are so many competitors, and while I'm glad STiki hasn't been overrun by hordes of itchy fingers, the program is so superior to others that it really deserves the widest userbase possible. That's my thought. Thanks again, Ocaasi ( talk) 03:34, 1 February 2011 (UTC)
STiki scored more than 1000 reverts in the last 24 hours. Pretty sure this is a record day. Thanks to all the user-base! West.andrew.g ( talk) 05:12, 4 February 2011 (UTC)
Yet another old problem is back. After restarting STiki, the first edit was this one, which I had clicked innocent on about 25 minutes earlier in my last session (long before the revert failures above started happening.) Both edits were from the CBNG queue. — UncleDouggie ( talk) 22:42, 6 February 2011 (UTC)
Is it just my computer, or does STiki not show edit summaries? If this is the case, it should be fixed; otherwise, there is a greater chance of reverting legitimate edits. -- Ixfd64 ( talk) 23:57, 13 February 2011 (UTC)
STiki doesn't seem to want to warn offending users at the moment. I've reloaded it, but the problem is still there... Orphan Wiki 00:14, 16 February 2011 (UTC)
I sometimes need to copy the name of an article out of the STiki window. The only thing selectable is the bold name at the top of the diff window. However, this leads to a confusing mess. — UncleDouggie ( talk) 23:14, 5 February 2011 (UTC)
An old problem is back. STiki just gave me this edit. I clicked vandalism (with a custom edit summary and no user warning). However, STiki didn't perform the rollback and instead said that I was beaten to the revert. I then did a Twinkle rollback instead. I then noticed that it had been 6 minutes since my previous revert, but I know that I had several cases of vandalism during that time. I just hadn't paid much attention to the STiki revert status pane because it often lags significantly. Beyond the obvious problem of why STiki thought I was beaten when I wasn't, we should make the revert failure condition much more prominent like putting it in a red font. By the time I noticed the problem, I had no way to go back to the edits I had recently classified. The only way out of this situation based on my past experience is to close and reopen STiki. — UncleDouggie ( talk) 22:36, 6 February 2011 (UTC)
For the second time one of my edits has been dinged as vandalistic by an inexperienced editor using STiki, and for the second time this editor ( Ankit Maity ( talk · contribs)) shows a pattern of abusing the tool to mass-revert non-vandalistic edits and label them as vandalism. Either this tool needs some serious improvements (How about a whitelist?) or its use needs to be restricted to more experienced editors.-- ShelfSkewed Talk 18:22, 19 February 2011 (UTC)
Just thought I'd clarify the situation. Ankit Maity, it was not I who declined your request for rollback rights, it was declined by Skier Dude. This was because it was thought that you weren't quite ready yet to be granted rollback rights, and also based on the evidence that you weren't quite used to automated tools (I simply provided a link to this discussion to help in the decision process). I didn't do this to prevent you from earning rollback rights, I did it to make sure the right decision was made at that particular time. Nevertheless, that doesn't mean you couldn't be granted rollback rights in time to come. I suggest you maybe keep on patrolling the recent changes old school style? That way you can be certain of what really needs reverting and what doesn't, thus proving to the people over at Requests for Rollback proof that you deserve the tool. If you would like further help with all this, I am more than happy to assist you. Just give me a shout on my talkpage. Regards, Orphan Wiki 11:46, 25 February 2011 (UTC)
A very minor release here. As far as GUI users are concerned, it only addresses one issue raised by UncleDouggie (pertaining to copy-paste of text from STiki). Regardless, I have no major changes on the immediate horizon, so I thought I'd go ahead and push this out.
CHANGELOG:
Thanks for everyone's continued support, West.andrew.g ( talk) 00:39, 24 February 2011 (UTC)
STiki seems to be mostly detecting the level of warning already given to a vandal and responding appropriately. However, take a look at User talk:Tosspot345 and it didn't seem to have worked properly. I noticed that there were lots of messages and posted on WP:AIV manually. I don't think it was just STtiki that got confused, ClueBot NG seems to have got confused too. Any thoughts? Yaris678 ( talk) 19:40, 1 March 2011 (UTC)
During this conversation, it was suggested that only rollbackers should be allowed to use STiki. The conversation then got distracted by a specific case... so I would like to return to the general point.
I think that only rollbackers should be able to use STiki. This wouldn't just reduce abuse and errors, it would also ensure that the learning aspects of STiki isn't learning from false data.
I think that if someone logs in to STiki with an account that doesn't have rollback rights, it should politely suggest that the user request them. Something like...
"You do not appear to have rollback rights, which are now required to use STiki. If you have a contribution history that demonstrates an ability to distinguish well-intentioned edits with minor issues from unconstructive vandalism, please request rollback rights."
Yaris678 ( talk) 09:58, 9 March 2011 (UTC)
STiki is well-built and the project page's wording makes it sound high-tech. It's definitely simpler than Huggle, but that's possibly a good thing, especially for newer vandal fighters. However, it would be nice if the screen displayed the change in bytes (e.g., "-566" or "+44") like Huggle does. Guoguo12 --Talk-- 20:20, 14 March 2011 (UTC)
It would be nice if you could decide if STiki adds articles you edit through it to your watchlist. I assume most editors wouldn't want most articles edited this way to their watchlists. I know I don't. No More Mr Nice Guy ( talk) 16:21, 1 March 2011 (UTC)
Thank You. I love STiki and this will make it even better.-- Nyswimmer ( talk) 17:39, 1 March 2011 (UTC)
The changes work for me-- Nyswimmer ( talk) 19:01, 1 March 2011 (UTC)
Hello STiki users, and thanks for your continued use of my tool.
As you may have noticed, the "ClueBot NG" queue has not been updated in some time. Initially, this was the result of the ClueBot NG being completely offline. Bot service has since been restored. However, the IRC feeds on which STiki depends to enqueue scores have not yet been restarted. I have raised this as an issue with the developers (see User_talk:ClueBot_Commons#IRC_Feeds) -- but I am yet to receive a response. Perhaps some others can pile on over at that talk page to see if we can't make some traction.
In the meanwhile, I encourage STiki users to switch to the "metadata" queue, which is actively processing/en-queuing fresh edits. You are much more likely to find vandalism in this stack. I also realize, that due to to the CBNG-queue being down, that STiki may take a rather lengthy period of time to load/initialize. I apologize. Fixes in the near future will allow me to adjust the "default" queue on the server to circumvent such issues. Look for these changes in a couple weeks time -- I am quite bogged down at current trying to prepare some academic work for WikiSym. Thanks, West.andrew.g ( talk) 22:16, 22 March 2011 (UTC)
My copy of STiki seems to be picking up the ClueBot NG feed now. I guess the problem has been fixed. Yaris678 ( talk) 17:24, 25 March 2011 (UTC)
Sometimes using STiki, when I click "Vandalism (Undo)", the revert doesn't go through. Sometimes the reverts do work, but the warning doesn't go through, even when the "Warn offending editor" check box is checked. What causes this? - Porchcrop ( talk| contributions) 01:38, 22 April 2011 (UTC)
If I make a classification using one of the built-in hotkeys (alt-v, alt-p, alt-i), it seems like this classification is not only applied to the current diff, but also immediately to the next diff. It's not a big problem, I just have to use the mouse instead. Arthena (talk) 07:11, 24 April 2011 (UTC)
Greeting, STiki users. Over the next several hours (possibly stretching into the next day), the STiki database will be undergoing some maintenance tasks. This could result in intermittent dysfunctional behavior and downtime. Please do not report these as bugs until everything stabilizes.
These updates: (1) should result in some minor speed improvements in the client-side, (2) lay the foundation for the inclusion of the "anti-link-spam" queue, and (3) help prevent "forced updates", and keep legacy versions of STiki in good working order, even as improved versions get rolled out. Thanks, -AW
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 | Archive 3 | Archive 4 | Archive 5 |