Jump to content

User talk:Animum/Archives/2009/June

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


Are you okay?

Your recent edits have been rather erratic and inexplicable. Everything alright? --MZMcBride (talk) 16:57, 3 June 2009 (UTC)

Everything's fine. I was trying to figure out why I wasn't in Category:Successful requests for adminship, but I clicked on the wrong RFA link. —Animum (talk) 17:08, 3 June 2009 (UTC)
:-) Good to hear everything's okay. --MZMcBride (talk) 19:48, 3 June 2009 (UTC)

fail

lolwut. –Juliancolton | Talk 21:06, 6 June 2009 (UTC)

Well, I messed up the first time. I think that working so extensively on a block script is starting to get to my head, no? ;-) —Animum (talk) 21:09, 6 June 2009 (UTC)
And here I was, thinking you can only block for lengths of time, not everything. SoWhy 21:10, 6 June 2009 (UTC)

What's the big idea?

I went to check on a page, and YOU are listed as having blanked it!

I want to know what gives you the right to blank a page that wasn't vandalism????

99.149.121.199 (talk) 21:08, 10 June 2009 (UTC)

WP:USER and WP:IAR do. —Animum (talk) 21:16, 10 June 2009 (UTC)

Your easyblock.js script - requested addition (I've asked someone else, but your code is complicated!)

Hi Animum,

I'm sending you this message to ask you to add another feature to your easyblock.js script, which is already brilliant. I can see that it shows sockpuppets then Suspected / Confirmed Sockpuppets.

I was wondering if you could add another option, called SPI Case or something thereof especially for WP:SPI, which is sockpuppet investigations. Basically, it would need to be used for both IPs and users to block those that have been checked and agreed to be sockpuppets.

The script would really only need to ask for one thing, the main sockpuppeteer's name, for example Test. Then, for the user, it should block them indef with the summary of: "Abusing multiple accounts: Please see: Wikipedia:Sockpuppet investigations/Test", therefore only requiring to add the "Test" part to the block summary. Then for the IP addresses, it would have the same block summary, but the admin would have to choose the block time (you might need to have SPI Case User, SPI Case IP if the script can't tell the difference between the two).

Finally, for the user, the user page will need to be tagged with "{{blockedsockpuppet|Test|evidence=[[Wikipedia:Sockpuppet investigations/Test]]}}", again where Test is whatever the user enters. For the user talk page (for users only), can you add the message of "Blocked as a sockpuppet", like I used on User_talk:RNaidu#Sockpuppetry (with your script before).

If you have any questions, feel free to ask.

Thanks for your help,

The Helpful One 23:32, 26 May 2009 (UTC)

Bump thread to stop archiving. The Helpful One 09:52, 29 May 2009 (UTC)
checkY I've modified the sockpuppet options to do just that and, in the case of a confirmed sock, to use {{CheckedSockpuppet}} with the requisite parameters. Tell me if you have malfunctions; ask me for a new option if you think of another. —Animum (talk) 01:06, 30 May 2009 (UTC)
Hi there, that's great! One more thing, sometimes we don't block the users indef for being socks, so can you create another option that allows you to set a duration for user blocks (what would the format for the duration be?). Thanks, The Helpful One 10:24, 30 May 2009 (UTC)
I will; the format is anything that the block form will accept (most commonly: 24 hours, 1 day, 6 months, etc.). —Animum (talk) 01:14, 31 May 2009 (UTC)
checkY Done. —Animum (talk) 01:49, 31 May 2009 (UTC)

Return to!

How about an option for the script to return to a page of the editor's choosing, say, to a pre-purged AIV? –xenotalk 19:47, 2 June 2009 (UTC)

checkY Done. See the documentation page for the usage instructions. —Animum (talk) 15:46, 3 June 2009 (UTC)
Freakin' sweet! In lieu of "no good deed goes unpunished", did you ever get a chance to look at my suggestion for your "$" script? ( User talk:Animum/Archives/2009/April#Suggestion for your $ script ) –xenotalk 15:58, 3 June 2009 (UTC)
I indeed can, but I won't be able to detect username changes. It's easy to find the new account from the old one, but the same isn't true the other way around. —Animum (talk) 16:03, 3 June 2009 (UTC)
That's fine, the basic functionality will still be nice. –xenotalk 16:24, 3 June 2009 (UTC)
checkY Done. Enjoy User:Animum/RFA-finder.js. :-) —Animum (talk) 17:46, 3 June 2009 (UTC)
After I had added it to my monobook.js it broke down completely — I wasn't even able to revert it (well, only 15 minutes later). ;) — Aitias // discussion 17:53, 3 June 2009 (UTC)
Varry noice ! –xenotalk 17:59, 3 June 2009 (UTC)

{{Uw-vaublock}}

Hey Animum. :) How are you? Just wanted to ask whether you could add {{Uw-vaublock}} to your easyblock.js? Thank you, — Aitias // discussion 15:45, 3 June 2009 (UTC)

checkY Done. I added it to the "vandalism" list because the username part seems to be more of a secondary reason. —Animum (talk) 15:53, 3 June 2009 (UTC)
Thank you! :) — Aitias // discussion 15:55, 3 June 2009 (UTC)
You're welcome! —Animum (talk) 15:57, 3 June 2009 (UTC)

Broken?

For whatever reason, the block tab has disappeared from all pages related to IPs (contribs, user talk, user page) with the exception of Special:Block/. :-( — Aitias // discussion 01:21, 5 June 2009 (UTC)

It was actually a problem with User:Animum/RFA-finder.js. Fixed. —Animum (talk) 18:07, 5 June 2009 (UTC)
Many thanks for fixing that, Animum. :) — Aitias // discussion 23:31, 9 June 2009 (UTC)

SUL

I confirm that I am "Animum from en.wp" on the French Wikipedia and that I made the usurpation request. —Animum (talk) 19:48, 9 June 2009 (UTC)

 Done! Cheers, Popo le Chien throw a bone 23:05, 9 June 2009 (UTC)
Thanks! —Animum (talk) 23:07, 9 June 2009 (UTC)

RFA finder

Why didn't it find this RFA ? –xenotalk 21:11, 9 June 2009 (UTC)

I'm working on fixing it. The RfA has to be displayed in Category:Successful requests for adminship, and it won't unless the category link is piped with the subpage name. Thing is, though, the changes to the category links don't have immediate effects; they'll take a little while to become apparent in the category.
As a side note, once I've piped the category links, I'm going to incorporate a search tool for Category:Redirects to requests for adminship to try to compensate for renames. —Animum (talk) 23:12, 9 June 2009 (UTC)
That would be hot. Piggybacking the RFA finder off your "$" script would be even cooler, to save on tabs. If this is possible. –xenotalk 23:18, 9 June 2009 (UTC)
checkY Rename-detection added — I can make a version for you that integrates the two scripts, but I would like to keep the "master copies" separated. And if I did make a version for you, I suppose you'd ask me to include the same functionality for RfBs. :-) —Animum (talk) 01:23, 10 June 2009 (UTC)
DIABOLICAL! I hadn't thought of RFBs, to be honest. ;p Don't worry about the piggyback script if it will take a lot of time. But it would be nifty. –xenotalk 01:30, 10 June 2009 (UTC)
I've fixed I'm fixing the problem with not finding RfAs that were present in the category but hidden in its bowels. —Animum (talk) 02:27, 10 June 2009 (UTC)
And one inflated edit count later, the job's finished. :-) If you stumble upon a user whose RfA the script can't detect, it will be because that user had a rename after the RfA had been closed and there is no redirect (Wikipedia:Requests for adminship/NEW NAME) that uses the new name to the RfA (Wikipedia:Requests for adminship/OLD NAME). So create such a redirect if you need to and can, and remember to tag it with [[Category:Redirects to requests for adminship|NEW NAME]]. —Animum (talk) 18:29, 10 June 2009 (UTC)
Nice =) I saw also that you built the rfa finder into the $ script, but now the $ script has gone an disappeared .. ?? I'm sure it'll show up sometime in the future though. Cheers mate. –xenotalk 18:33, 10 June 2009 (UTC)
That's odd. I still see the "$" tab even after purging my cache. —Animum (talk) 18:37, 10 June 2009 (UTC)
Yea, I dunno. Your scripts are haunted, they do this from time to time. I'm sure it'll turn up eventually =) –xenotalk 18:38, 10 June 2009 (UTC)
Juliancolton had a similar problem with one of my scripts, which actually turned out to be a conflict between that script and one from the Twinkle collection. Try running the script in question on your alternate account. If it works there, it's conflicting with one of the other scripts you've installed. —Animum (talk) 18:51, 10 June 2009 (UTC)
Turned off all 3 gadgets, and did this, still no dice. I wonder if it has anything to do with how it imports your css or something. –xenotalk 18:58, 10 June 2009 (UTC)
No, importStylesheet() is the correct function; you're testing this on highest-level pages (i.e., not subpages), right? (If you use IRC, we can continue this in ##Animum.) —Animum (talk) 19:20, 10 June 2009 (UTC)
ohhhh I see how it is!... first you re-write history to hide your grammar errors and now you want to shuffle me off to some corner of irc to discuss your haunted scripts ! ;> (i'm there , but it's awful quiet!) –xenotalk 20:13, 10 June 2009 (UTC)
Sorry, I'm there now. :-) I don't check my channel too often because it often is extremely quiet. —Animum (talk) 20:15, 10 June 2009 (UTC)

Nubio(2) account request

I confirm that I requested an account on X!'s Nubio2 tool. —Animum (talk) 04:05, 10 June 2009 (UTC)

sorry, just kidding around the sandbox.

As long as that wasn't your real credit card number, it's okay. :-) I was actually making some test/dummy edits of my own. —Animum (talk) 20:03, 12 June 2009 (UTC)

regarding twinkle and friendly

Hi: Is there a possibility that your recent changes to Twinkle and Friendly might have disabled the script for me? Thanks, RayTalk 22:53, 23 June 2009 (UTC)

I'm not having any problems with the Twinkle installation I have, though I don't use Friendly; try purging your cache again if you have not already done so. —Animum (talk) 23:02, 23 June 2009 (UTC)
Other users are having problems as well, see Wikipedia talk:TW#Can't use Twinkle. I'm not having any problems with twinkle, but maybe users who use it as a gadget are? Something like that. –xenotalk 23:04, 23 June 2009 (UTC)
(ec)Your changes have disabled Twinkle and Friendly for all not just the intended users, see: Wikipedia:Administrators'_noticeboard#My_Changes_to_MediaWiki:Gadget-Twinkle.js and Wikipedia_talk:Twinkle#Can.27t_use_Twinkle (Purging the cache does not fix the problem and I'm using a monobook installation that has worked for years) -MBK004 23:06, 23 June 2009 (UTC)
Hmm. I stand corrected "Your account is too new to use Twinkle". –xenotalk 23:07, 23 June 2009 (UTC)

Please don't make changes to the live scripts without first testing. --MZMcBride (talk) 23:09, 23 June 2009 (UTC)

I assumed that the change I made was minor and simple. The fault is in my assuming. For some reason, the code on twinkleblacklist.js was not being imported. I have reverted myself. —Animum (talk) 23:12, 23 June 2009 (UTC)


You have been blocked from editing for a period of a trout, battered and fried in accordance with Wikipedia's blocking policy for making a mistake. Once the block has expired, you are welcome to make constructive contributions. If you believe this block is unjustified, you may contest the block by adding the text {{unblock|Your reason here}} below, but you should read our guide to appealing blocks first. –xenotalk 23:13, 23 June 2009 (UTC)

After testing the code in my own monobook, it appears to be working. I'm tentatively unreverting myself. If you have problems, first purge your cache; if the problem persists, revert me. —Animum (talk) 23:21, 23 June 2009 (UTC)

It breaks anything that uses morebits.js so . . re-reverting. Q T C 23:25, 23 June 2009 (UTC)

importScript doesn't work like your typical import statement. You can't expect that imported code was executed before the importScript statement returns. In fact, any current browser will keep executing morebits.js and execute the imported script a fair while later, once it's been downloaded. Amalthea 23:32, 23 June 2009 (UTC)

So how do we make it so that the code executes once the imported code has been downloaded? —Animum (talk) 23:33, 23 June 2009 (UTC)
Importing the blacklist at the top of User:AzaToth/twinkle.js would work for all users of all Twinkle modules, i.e. users who don't just pick the modules they want and add it to their monobook (which is a documented and "supported" way of using Twinkle), since the script tags added to the head are, I believe, always executed in order (by at least Firefox and Opera, not 100% about Safari & Chrome). What you tested in your monobook worked since the onloadhook apparently only executes once all scripts in the head are loaded and executed. I'm not too sure about any details of all the javascript engines, but I think they all work that way. However, a number of modules expect twinkleConfigExists to be defined right at the top (like twinklefluff), and not only inside an onload function (like twinklespeedy).
So, if the evaluation of twinkleConfigExists in the modules isn't changed, and we want to support only importing morebits + twinklefluff, I see no way except adding the blacklist definition & evaluation straight at the top of morebits.
A cleaner way would be to make sure that twinkleConfigExists is only ever evaluated inside the onload hooks that all modules have. This should work in all browsers Twinkle supports, but would need testing. Amalthea 23:48, 23 June 2009 (UTC)
So twinkleConfigExists should work if used in addOnloadHook? I tested it ([1]), and it didn't work. :-( But maybe I'm doing something wrong. —Animum (talk) 00:26, 24 June 2009 (UTC)
Am I doing something wrong? —Animum (talk) 02:30, 24 June 2009 (UTC)

In your test User:Animum's Electric Pajamas/morebits.js you are still importing a script and trying to use the results right away. That will always fail. What I was thinking about was something like 

importScript("User:AzaToth/twinkleblacklist.js");
addOnloadHook(function(){
  jsMsg( "Onload hook: " + ( typeof(twIsBlacklisted)=="undefined" ? "Nope" : "Twinkleblacklist imported and executed") );
});

But it turns out that only (seems to) work reliably in Firefox, other browsers aren't working as I expected.
In Firefox and Opera, the following should work: 

importScript("User:AzaToth/twinkleblacklist.js");
importScript("User:AzaToth/morebits.js");
importScript("User:AzaToth/twinklefluff.js");

IE and Safari can fail there though, and probably Chrome as well.
I can't really offer a clean solution, Twinkle itself has the same race condition which User:TheDJ/twinkle.js tries to workaround for Safari, but that's really beyond ugly. A clean way to resolve this mess of indeterministic loading and executing would be to add custom event hooks, like having a global mapping of script URI to list of functions that will be called once the script has been loaded and executed. That way, we could still import/load all scripts in parallel, but delay their execution until all prerequisites have executed successfully. Amalthea 11:05, 24 June 2009 (UTC)

Would the simplest and most elegant solution be to have the array itself (not an importScript() statement) at the bottom of morebits.js, followed by something like if(twinkleBlacklistUsers.indexOf(wgUserName) != -1) twinkleConfigExists = false;? —Animum (talk) 19:26, 24 June 2009 (UTC)
Ah, yes, that works as I said above ("adding the blacklist definition & evaluation straight at the top of morebits"), and I see you already did that. :)
Cheers, Amalthea 09:41, 26 June 2009 (UTC)

User:Animum/usergroups.js

Hey Animum. :) User:Animum/usergroups.js seems to break twinkle, cf. [2]. Do you have any idea how to fix that? Many thanks, — Aitias // discussion 21:02, 24 June 2009 (UTC)

The script doesn't fuss with my Twinkle configuration; perhaps it's the result of a recent change to another script. —Animum (talk) 21:30, 24 June 2009 (UTC)
Or, alternatively, maybe, for some reason, you still need to purge your cache after I accidentally broke Twinkle yesterday. —Animum (talk) 21:31, 24 June 2009 (UTC)
Hmm, well I have just tried adding it once again; though, as soon as I add it, the "warn" tab of twinkle disappears. Also, I have purged my cache... Strange. :( — Aitias // discussion 21:39, 24 June 2009 (UTC)
Strange indeed—even after logging out, your monobook still works in its entirety for me. I've fixed what I found to be the only problem, and I have removed the comment tags from the importScript("User:Animum/usergroups.js"); statement. Re-add the comment tags if the problems persist. —Animum (talk) 22:20, 24 June 2009 (UTC)
While the warn tab does appear on non-existing user talk pages (i. e. red-linked ones), it's still gone on existing ones... — Aitias // discussion 22:31, 24 June 2009 (UTC)
Also, it does work on existing ones as well while viewing diff-links. — Aitias // discussion 22:51, 24 June 2009 (UTC)
And now? —Animum (talk) 23:36, 24 June 2009 (UTC)
Hmm, unfortunately, it does still not work. :( — Aitias // discussion 10:08, 25 June 2009 (UTC)
Can you come into ##Animum on Freenode? —Animum (talk) 13:12, 25 June 2009 (UTC)
I'm sorry for the late reply, I just saw your above comment (many thanks for the reminder :-). I'll come there as soon as possible. — Aitias // discussion 19:05, 25 June 2009 (UTC)
I'm there now. :) — Aitias // discussion 19:10, 25 June 2009 (UTC)

Found it?

Hey. :) It appears to be this one, i. e., if I remove it, everything works. Best wishes, — Aitias // discussion 20:24, 25 June 2009 (UTC)

Hm, well, this is embarrassing. :-P I'll try to locate the error. —Animum (talk) 20:27, 25 June 2009 (UTC)
There's nothing in your Error Console that relates to this script, right? —Animum (talk) 20:31, 25 June 2009 (UTC)
Now, there is one (it was not there when we talked on IRC):

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIXMLHttpRequest.send]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: http://wiki.riteme.site/w/index.php?title=User:Animum/easyblock.js&action=raw&ctype=text/javascript :: anonymous :: line 189" data: no]

— Aitias // discussion 20:39, 25 June 2009 (UTC)
See if it's fixed now. —Animum (talk) 20:44, 25 June 2009 (UTC)
Unfortunately, no. :( — Aitias // discussion 20:50, 25 June 2009 (UTC)
Also, there is another error, though, I don't know whether it's related to easyblock.js, as there is no particular relation displayed in the error console. The error message is in German (the other one above was in English from the first), thus, this one is a transtaled version (by me):

Error: The permission for the call of the method Location.toString has been denied.

(word-for-word translation.) — Aitias // discussion 21:03, 25 June 2009 (UTC)
Interesting. None of the scripts in your monobook use the location.toString() method; what gadgets do you have enabled? —Animum (talk) 23:37, 25 June 2009 (UTC)
“Add a clock in the personal toolbar that displays the current time in UTC (which also provides a link to purge the current page)” and “Allow up to 50 more characters in each of your edit summaries. Works in Internet Explorer, Firefox, and Opera.” Best wishes, — Aitias // discussion 23:43, 25 June 2009 (UTC)
Nope, none of those scripts use the location.toString() method. :-/ I think you'll have to ask at WP:VPT. —Animum (talk) 23:54, 25 June 2009 (UTC)
Interesting, now I'm getting the same error from Wikipedia:WikiProject User scripts/Scripts/Fix lowercase first letter problem, which I can't find in your monobook even as an imported script of an imported script. I've uninstalled it, but the error still persists; so I've started a VPT thread on the matter. —Animum (talk) 02:48, 27 June 2009 (UTC)
It's probably an error from another Web site. If you want to be sure, you can clear your Error Console and then reload a page here on enwiki; if the bug isn't there, which is what I suspect, the error isn't with one of your scripts. —Animum (talk) 22:54, 27 June 2009 (UTC)

You know, there once was a time I could understand the discussion on this page.... Newyorkbrad (talk) 23:46, 25 June 2009 (UTC)

Eureka! I have found something that Newyorkbrad has trouble understanding! —Animum (talk) 23:49, 25 June 2009 (UTC)

easyblock

At times it preforms the block, but doesn't go through with the talk page notice... is this an issue with my browser, or something else? –Juliancolton | Talk 23:25, 29 June 2009 (UTC)

How long are these blocks? —Animum (talk) 23:36, 29 June 2009 (UTC)
Most recent one was 1 week, but I've encountered issues with everything from 31 hours to indef. –Juliancolton | Talk 23:37, 29 June 2009 (UTC)
The hack that the script was using was a remnant of the time when index.php had to be used instead of the API. As far as I can tell, it's checkY fixed. —Animum (talk) 01:11, 30 June 2009 (UTC)
Retrieved from "https://wiki.riteme.site/w/index.php?title=User_talk:Animum/Archives/2009/June&oldid=1086803514"