User talk:Nixeagle
Welcome to Eagle's Archives!
I respond to all comments here, as it becomes difficult to keep up with the volume otherwise; if I believe immediate notice is necessary, I may copy the response to your talk page.
Please note that I have changed my name from Eagle 101 to nixeagle.
I am an admin on both the english wikipedia (here) and on the meta wiki.'
Disputes between editors, especially content disputes, belong in formal dispute resolution, not here; if you raise them here, I'm just going to say "I don't get involved" and send you to dispute resolution, so save time and head there now.
I archive obsessively, often several times a day; if you do not see a comment you left here, it has probably been archived, please look in my archives. Users are welcome to bring archived discussions back if they have additional comments.
If you left a comment and didn't get a response from me, ninety-nine times out of one hundred, I was busy and forgot to answer; poke me, and I'll be sure to do it. However, if you left a comment that you expected would elicit an angry response, and instead received no response, then I probably didn't forget, I just didn't respond. I reserve the right to archive personal attacks, incivility, or canvassing separately and immediately. Severe instances may simply be deleted.
Others are encouraged to help out and respond to posts here. Plenty of angry and clueless posts find their way here, and to my email; in the vast majority, I find that the writer has misunderstood some difficult aspect of Wikipedia. Though I may seem to have everything under control, I appreciate having others help out and back me up.
If you came here because I removed a link that you posted onto Wikipedia. Please read and understand
this first.
Archives
old stuff
• March 2006
• April 2006
• May 2006
• June 2006
• July 2006
• August 2006
• September 2006
• October 2006
• November 2006
• December 2006
• January 2007
• Febuary 2007
• March 2007
• April 2007
• May 2007
• June 2007
• July 2007
• August 2007
• September 2007
• October 2007
• November 2007
If you think that this notice was placed here in error, you may contest the deletion. To do this, add {{hangon}} on the top of the page (just below the existing speedy deletion or "db" tag) and leave a note on the page's talk page explaining your position. Please do not remove the speedy deletion tag yourself.
If the page you created was a test, please use the sandbox for any other experiments you would like to do. You may also want to move the page to EverythingWiki. Feel free to leave a message on my talk page if you have any questions about this. SpitfireTally-ho! 16:13, 6 October 2008 (UTC)
- Umm...Testing isn't permited, and defintly not in a mainname space article, any way please contact the deleting admin if you have any further problems, cheers SpitfireTally-ho!
- Righto, thats OK SpitfireTally-ho! 16:24, 6 October 2008 (UTC)
RFPP
Wanna stop copying me? Edit summaries are ok though. :P Just kidding, keep up the good work! Master of Puppets Call me MoP! :) 08:25, 14 November 2008 (UTC)
- I replied to you on the requests page; whatever decision you make I'm fine with, really (as long as no harm comes to my loved ones). Master of Puppets Call me MoP! :) 08:30, 14 November 2008 (UTC)
3RR bot reports
Hi, I like the new revert monitoring bot - could I make a suggestion?
It would be helpful if, on User:3RRBot/bot reported disruption and 3RR violations, rather than listing the article in question with [[Article name]] it was listed with its relevant links i.e. {{la|Article name}}
Thanks. CIreland (talk) 02:15, 15 November 2008 (UTC)
- Thanks for the suggestion, it should be implemented now, took me all of 5 seconds to change the brackets to the template. Now the titles will be more informative. :D —— nixeagle 04:20, 15 November 2008 (UTC)
3RR bot code
I'm interested to read the code for the 3RR bot to see what heuristic it's using, if you don't mind sharing it. You didn't create a talk page for the bot, by the way. — Carl (CBM · talk) 21:55, 16 November 2008 (UTC)
- I can probably get you the source code this weekend. I don't want to hand it out right now as the framework I setup for the config files is not completed yet, and more importantly there is a bug in my rc parser which I want to clean up my ugly hack. —— nixeagle 17:24, 17 November 2008 (UTC)
- As far as the hueriestic, it is basically reading the RC feed with the following "filters" on it.
- Discard all non-mainspace edits/logentries.
- Discard all edits by bots/admins
- Place all edits onto the end of a 300 edit buffer. (Assuming buffer is full do next step).
- If buffer is full, take the item at the start of the buffer and check the rest of the buffer for an edit that is by the same user on the same article. If the user has another edit in the queue, discard the top edit and wait. (This prevents multiple pointless checks on users doing many edits in a short period of time... we only check when the editor has left the article alone for about 10 minutes).
- If the edit has not yet been discarded, do a mysql query that returns the revisions that the user has edited the page in the last 24 hours. If there are fewer then 4 revisions returned, discard the edit... there is no way the user can violate 3RR without doing at least 4 edits to a page in one day.
- Finally if all these prior steps don't cause an edit to be discarded we must check the diffs themselves, load each diff, strip information that will screw up the MD5 hash. (Timestamp, comments etc), and hash it. Compare the hashes.
- There is a subcheck that is done, if the count of matching hashes is "1" (means no edits are the same change), and there is only 1 edit left to check, we simply say there is no 3RR violation.
- —— nixeagle 17:32, 17 November 2008 (UTC) I'll get you the code, but that is the algorithm in english.
3RR report
[1] triggered a bot 3RR report, but it looks like he was just very very indecisive. MBisanz talk 13:42, 18 November 2008 (UTC)