User talk:Furry

nou Smuff ^{[The cake is a lie]} 21:13, March 12, 2011 (UTC)

Vandalism

Sorry. I got carried away. I will stop. 99.249.133.245 16:38, February 11, 2012 (UTC)

Wait, are you a admin here? 99.249.133.245 16:40, February 11, 2012 (UTC)

Good job on reverting this guy, keep up the great work! :) -- UserTalkContributions 18:13, February 11, 2012 (UTC)

Dittos

Thanks for the help at AF19 with tonight's problem. See also my enabling of AF12 to throttle newbie edits. Quibbles: The guy doesn't specify just me and Simsie but any Admin on duty, and even fixated on a new user yesterday. Also, the guy has shown himself able to adapt to countermeasures and I would not do him the favor of giving a warning. Simsie with a fancier computer than mine, is repairing the damage; the problem is that simple rollback doesn't work, as he has touched many pages from multiple IPs. Spıke ¬ 03:39 17-May-13

No problem. I opted for the warning because I didn't know if there would be any false positives or not - I'll talk to sannse about removing that later today. As for targeting specific users other than you two, I'll probably be able to work around that. I will leave the details of that in the filter, though. -- Furry ^(talk) 11:40, May 17, 2013 (UTC)

Concur regarding the details. He gave up when AF12 kicked in. Initially AF12 took itself out of service when it matched more than 5% of the edits on the wiki--I complained to Sannse about this self-described "safety feature"--but disabling and re-enabling seemed to solve that. His last move (see Special:AbuseLog) was a multi-thread effort to hit every page on the wiki. I think reducing the damage he can do is a better strategy than trying to identify specific edits; he is quick to adapt.

PS--If Wikia is going to help us find and repair remaining damage, I bet you won't use the Uncyclopedia search function! Spıke ¬ 11:45 17-May-13

Tweaked #19 to be a bit more intuitive. As for helping clean, I'm not entirely sure if I am authorised to do so - the VSTF have never had rights on Uncyclopedia in the past, and I was only given them now to help with the AbuseFilter. -- Furry ^(talk) 12:03, May 17, 2013 (UTC)

Very well. We have resisted VSFT help in the past, as we are usually able to patrol everything, and I was the loudest opponent of the robot Welcome messages that signed other users' names, which are now disabled here. Spıke ¬ 12:09 17-May-13

Too many $%$% Unpatrolled flags on this $%$% wiki!

Furry, there is another piece of technical work we need: There are perhaps thousands of vandal edits left where the text of the page has been manually repaired but the edits are still officially "unpatrolled." My only way of clearing these flags so that the Patrol feature becomes useful once again is to walk through individual edits; this takes me more than a minute to repair a single article. Could we get a JavaScript button to mark every edit shown in a page history as Patrolled? (Ideally, any edit window should give a trusted editor the ability to click that he considers the entire page patrolled.) Separately, many of the old pages in Forum: have not been repaired. This might be doable by 'bot, though not merely by rollback of the last IP edit. Spıke ¬ 11:52 18-May-13

Broken redirects

Here is another chronic technical problem: Eight of the items at Special:BrokenRedirects have been there for a long time, and it is impossible to remove these entries by deleting the redirect. (You get told it has already been deleted.) Spıke ¬ 16:04 20-May-13

You seem to have gotten the first few. The last ones are articles with (1) an initial space or (2) an initial lowercase letter or (3) a prefix that is the name of a userspace but with different capitalization. I think the reason I can't delete these is that MediaWiki translates the name before interpreting my request. They must have been created at some time when translation was disabled or malfunctioning. Spıke ¬ 00:32 25-May-13

Those are harder to do, because I need to dig through the API to get at them. -- Furry ^(talk) 19:26, May 29, 2013 (UTC)

Done - BrokenRedicts should be cleared. -- Furry ^(talk) 16:15, June 1, 2013 (UTC)

I see them in the Delete Log (which is farther than I have gotten) and confirmed on Special:BrokenRedirects. The final test will be to see if the report is cleared when regenerated tomorrow morning, but no reason it shouldn't be. Congrats! Spıke ¬ 16:36 1-Jun-13

VSTF rights

Just a note to viewers of this page: Furry has agreed to use his VSTF rights to block spammers and obvious vandals on this wiki (and any other similar actions needed). This is with admin agreement. -- sannse (talk) 16:49, May 21, 2013 (UTC)

Yes, I agreed to this. Spıke ¬ 17:24 21-May-13

In regards to preceding requests from SPIKE, I'll be doing those along with anti-vandalism activity as well. I will start on them as my schedule allows, I should be able to get to them by the weekend, though. -- Furry ^(talk) 20:07, May 21, 2013 (UTC)

Thanks. See also User talk:Simsilikesims#Vandal repair on remaining pages damaged on the 15th. At the moment we can't seem to agree even that we are looking at the same report. Spıke ¬ 20:12 21-May-13

Just to add my support as well as an admin. Long as we stick to the tech issues rather than matter of tastes (besides the obvious pornography/shock image/blatant bullying which were always banned anyway). --RomArtus*Imperator ITRA (Orate) ® 07:16, May 22, 2013 (UTC)

Dittos. When Patrol was installed, overnight patrollers were tasked merely to verify that an unpatrolled edit was not overt vandalism and leave it to the article's owner to decide whether it was an improvement. In our current state, many articles' owners are not in the house, and I revert without explanation any Anon who lengthens a list or makes a contribution with flagrant errors in English and no Change Summary. I would not want VSTF to help us set the threshold. Spıke ¬ 10:34 22-May-13

Test

I assume today's test on your user page is a test of AF15, which seemed to catch your anonymous edits to a user page. Please mark these edits patrolled (something I would normally do) unless the patrol flag is part of the test.

My edit to your AF19 on 20-May was only to disable and re-enable it, because it had taken itself out of service. Wolvy was back with 16 edits from 3 IPs (Sannse has details); AF19 caught none of them, either because it was out of service or because Wolvy has inferred its contents and adjusted his scripts. But I think that Wikia's throttling is removing the attraction from vandalizing us. Spıke ¬ 22:30 22-May-13

---

As requested by the Change Summary, I won't patrol your edits right away. AF15 again caught the logged-out modification to a registered user's page. It seems to be working as designed. Spıke ¬ 15:26 2-Jun-13

In digging around through the API, I've discovered that there is no easy way to make a button to patrol all of the edits in a page's history. At this point, my options are limited as to how I can fix the issue of the leftover unpatrolled edits — would it be okay if I just did a blanket patrol of all edits within the forum namespace? -- Furry ^(talk) 15:40, June 2, 2013 (UTC)

Simsilikesims did this, brute-force (and got my nomination for Uncyclopedian of the Month). If you click on Special:RecentChanges and "hide patrolled edits," you'll see that there are no remaining unpatrolled edits from the vandalism week. There are remaining unpatrolled edits from the past three days that I expect to get to today. Spıke ¬ 15:53 2-Jun-13

Rollback-with-prompt

On a related issue, when we use Rollback, it patrols the edits we are undoing, but does not let us give a Change Summary. When we use Undo, we can tell the previous editor how we disagree, but it does not patrol his edit and all of us, sooner or later, fail to do so manually. Some other editor scolds us (or I scold someone) because it's irritating patrolling an edit that someone else has already seen to. These are additional situations where new click-button tools would be useful.

Bizzeebeever's JavaScript tool lets me see "patrol these changes" when I'm looking at Special:RecentChanges. It takes effect and, instead of calling up a different page, simply changes the contents of the report I'm looking at. I would like it if the button on the diff report ("Mark this edit patrolled") worked the same way, and if there were a button on a diff report encompassing multiple changes to mark them all patrolled (though you may be saying above that this isn't feasible). Spıke ¬ 15:53 2-Jun-13

I could write some JS to append a rollback link which prompts for a custom edit summary to diff / history pages, if it'd be helpful. -- Furry ^(talk) 16:25, June 2, 2013 (UTC)

I'd use it! The code should be per-user, so it doesn't change the behavior for other users; and documented or advertised at UN:HAX for people who want it. Spıke ¬ 12:31 5-Jun-13

Done. It can be viewed here, and I'll document it on UN:HAX later today. -- Furry ^(talk) 15:20, June 5, 2013 (UTC)

My "rollback" graphic, plus sheriff's-star for Admins.

Thanks! I've just used it successfully and the Change Summary in the History is what I typed into the box. The double legend appears in the first (but not every) edit listed in Special:RecentChanges. (Custom code on my PC uses a graphic instead of "rollback" and I now get two identical ones.) A quibble: A user who selects this option probably wants your implementation to replace the built-in implementation of rollback rather than see two rollback options. Another quibble: I would rather get some visual confirmation on RecentChanges than be taken to a separate page. Spıke ¬ 15:44 5-Jun-13

PS--The Bizzeebeever script I refer to above is at User:Bizzeebeever/scripts/patrol.js. It's worth looking at to see how he handled the user interface, and maybe merging with yours. I'm no JS whiz, and this script uses JS that is not even in my old textbooks, so the best I could do is mimic it, trial-and-error, until I got stuff to work. Spıke ¬ 23:30 5-Jun-13

I implemented the changes you asked for, but also added a configuration variable to let users use the previous version of the script if they want. I was unable to replicate the "graphic" you are seeing for the rollback links, so if it doesn't play nicely please let me know and I'll look into it further. -- Furry ^(talk) 13:53, June 6, 2013 (UTC)

Thanks again. Again, the rollback "graphic" is custom code on my PC and not on the website. Spıke ¬ 13:58 6-Jun-13

What do you use to implement it? I'm rather curious to see if my code works for it anyway... -- Furry ^(talk) 14:15, June 6, 2013 (UTC)

Also, what section should I place it under at UN:HAX? -- Furry ^(talk) 14:26, June 6, 2013 (UTC)

It is a local CSS substitution involving content=none and background-image=something. UN:HAX is mostly managed by PuppyOnTheRadio; I don't have a preference on section organization that would take precedence over what seems logical to you. Spıke ¬ 16:06 6-Jun-13

Regarding the "configuration variable," is there something I have to do to pick up your most recent work? Right now rollback isn't asking me for a summary at all. I studied your code but do not know how to read something of the form var = var || {}. Spıke ¬ 13:50 7-Jun-13

Ooh, look! Furry has a sock! Spike sockpuppet (talk) 17:25, June 7, 2013 (UTC)

Being the genius I am, I forgot to iterate over all of the rollback link containers on the page, so only the first rollback link would have been prompting for a summary. This should be fixed now. Code like the following:

window.furry = window.furry || {};

can be read as "If window.furry is defined, keep its current value. If window.furry is not defined, then define it as an empty object." Probably. I'm bad with verbalising code. -- Furry ^(talk) 18:13, June 7, 2013 (UTC)

What a fine though colloquial way to code something you'd often want to do. Once I was at the Help Desk trying to explain to co-eds why they couldn't just tell the FORTRAN compiler to test whether I .EQ. 6 .OR. 7--but now it seems you can. I have just verified your fixes on the first and not-first changes in RecentChanges. However, I expected to be prompted regarding my rollback at Rubber bands (Anon blunts joke in order to mention Penis). I saw that on Special:RecentChanges where I had clicked on "Hide patrolled edits," the report I usually use to patrol the site and from which I most frequently hit Rollback--and about the only case where I run with JavaScript switched on. Does this context makes your script fail? Spıke ¬ 18:34 7-Jun-13

Please ignore the possible bug above--although that Rollback came after your edit to the .js, I think I had not yet purged my cache to pick up your changes. Spıke ¬ 18:39 7-Jun-13

Is it now correctly working for you? I tried it on RC with ?hidepatrolled=1 and it worked fine. -- Furry ^(talk) 19:20, June 7, 2013 (UTC)

I am already using your work to replace silent rollbacks with messages that might be useful to the editors whose work I have had to undo. Thanks! Spıke ¬ 01:12 8-Jun-13

I have announced your work at Forum:Rollback with custom Change Summary. Spıke ¬ 11:19 8-Jun-13

And I've set off a new section at UN:HAX where the documentation of this will fit. Don't hurry to do this; I'll eventually do it. (This is what I do for a living.)

It was not obvious how to override the defaults with a configuration variable.

When I override the default to allow a null change summary, the script should still treat pressing ESC or clicking on Cancel as a desire to abort the rollback, not to just abort the typing of a change summary and complete the rollback. Spıke ¬ 17:08 9-Jun-13

Fixed. -- Furry ^(talk) 00:01, June 13, 2013 (UTC)

Also, is there anything else you'd like me to design (or attempt to, anyway) in the meantime? My final exams are next week so I have half of the school day off to do whatever, and I'd enjoy spending that time programming to my heart

s content. -- Furry ^(talk) 00:11, June 13, 2013 (UTC)

I appreciate your correction to my summary at UN:HAX. I was unsure of some of the stuff I wrote, but it has been a tenet of my writing career that, if you don't know the facts about a piece of software, take a guess; writing something wrong swiftly elicits the right answer, as it did here.

Regarding your free half-day: One thing I need to make my personal hack work is that, when you change the text of the rollback button (to "gone!") that you also remove its class=mw-rollback-link.

The way I usually use your custom rollback is not from RecentChanges but from a diff report (as I like to see what I'm rolling back, especially while formulating my custom Change Summary). Some of your Ajax code looks specific to RecentChanges.

Beyond that, you now have experience walking through each line of a change log, and I wonder if you are now more able than you were at the start of this discussion to implement the button that declares every edit to a page is patrolled. Spıke ¬ 03:52 13-Jun-13

The problem lies not in running a $.each() for all of the elements on a change log — it's that none of the entries on history pages give any sort of indication if they are patrolled or not. I'll see if there's any API queries that can be run, but I'm still not sure. -- Furry ^(talk) 11:36, June 13, 2013 (UTC)

Before I forget, are there any local rights that could be given to me so I may patrol edits? That will probably help with the development of the script (and I'll forfeit them when I'm done). -- Furry ^(talk) 11:39, June 13, 2013 (UTC)

Also, fixed the AJAX issue so it now works on all pages. -- Furry ^(talk) 11:55, June 13, 2013 (UTC)

I have given you autopatrolled, though you already had rollback and their edits are also autopatrolled. But if you were not seeing the various patrol buttons, you should now. Your other account, of course, has neither. Spıke ¬ 12:28 13-Jun-13

On the first test of removeLinkClass (after getting the case-sensitivity right!) it succeeded in not invoking the alternate window, but did not succeed in modifying the RecentChanges report. To be clear, it is the <SPAN> that has class=mw-rollback-link. My local CSS has the following to replace the "rollback" legend with a graphic, and the goal is to disable this once you have achieved the rollback:

.mw-rollback-link A
 { ...
   background-image: url(Graphics/Rollback.png) !important;
   background-repeat: no-repeat !important;
 }

Spıke ¬ 00:41 14-Jun-13