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.

I never went there. My material related to the 1984 incident at the MTC.--Hodgdon's secret garden (talk) 18:44, 22 March 2018 (UTC)

I never said you did. I simply noted the similarity of the text between the two pages. SQL^{Query me!} 18:44, 22 March 2018 (UTC)

In the long section, mostly my contribs, on the allegations?

• (((Hmm. This article is drawn from Weber State archived material, I see. I'd sent somebody on facebook this link, along with [1], direct transcript of this oral history by the faculty member there.... But I'm just getting paranoid!)))--Hodgdon's secret garden (talk) 19:03, 22 March 2018 (UTC)

I've never been to that article before today, and I only viewed the most recent deleted revision. The "early life", and "professional career" sections in that revision were mostly word-for-word copies from the archivesspace page. It looks like Ritchie333 is working on restoring the parts you contributed. SQL^{Query me!}

User:Ritchie333 hooked it up diff. Anyway, thanks!--Hodgdon's secret garden (talk) 19:10, 22 March 2018 (UTC)

Just letting you know that the unblocked range that was reported to WP:OP/R was 207.148.64.0/18 which is from the same webhosting ISP as 207.246.64.0/18 which is currently blocked. I think you had mistaken which range was actually reported to the noticeboard at that time.

207.148.64.0/18 (talk · contribs · WHOIS) - Not blocked

207.246.64.0/18 (talk · contribs · WHOIS) - Already blocked

Thanks, 172.58.40.149 (talk) 08:58, 1 April 2018 (UTC)

Sorry about that, it's blocked now! SQL^{Query me!} 16:28, 1 April 2018 (UTC)

Found another active Choopa range: 144.202.0.0/17 (talk · contribs · WHOIS) Most recently active on 144.202.72.214 (talk · contribs · WHOIS) See: WHOIS. 172.58.43.234 (talk) 01:12, 4 April 2018 (UTC)

Thanks for developing the feed:) Any ideas on why the spam% sort is not working as expected?!~ Winged Blades^Godric 05:58, 12 April 2018 (UTC)

@Winged Blades of Godric: it seems to be sorting for me, albeit slowly. I noticed there are a few invalid entries, and I've removed those. Hopefully that fixes that. SQL^{Query me!} 21:18, 12 April 2018 (UTC)

OH, I see what you mean! Let me see if I can fix that quickly. SQL^{Query me!} 00:28, 14 April 2018 (UTC)

Hello SQL, your recent BRFA (Wikipedia:Bots/Requests for approval/SQLBot 6) has been approved to run without a flag. Should you have future tasks that require a flag, you will need to ensure that your programming for this task does not assert the bot flag. Happy editing, — xaosflux ^Talk 17:12, 15 April 2018 (UTC)

Heads up the bot hasnt updated in couple hours. Bobherry Talk Edits 13:04, 17 April 2018 (UTC)

@Bobherry: - replication lag at tool labs is > 14 hours at the moment - so the data isn't there for the bot to generate. Hopefully it will sort itself out shortly. SQL^{Query me!} 16:39, 17 April 2018 (UTC)

@Bobherry: Sorry I didn't get back to you sooner. Replication lag seems to have quieted down (something about maintenance). I just re-enabled the bot and it seems to be working properly. SQL^{Query me!} 02:33, 20 April 2018 (UTC)

^{[April Fools!]} Welcome to Wikipedia. Although all admins are welcome to delete constructively on Wikipedia, at least one of your recent deletions, such as the one you performed on the Main Page, did not appear to be constructive and has been undeleted. Please use Jimbo Wales' user page for any test deletions or blankings you would like to make, and read about our main page deletion guideline to learn more about deleting things on this encyclopedia. Thank you. Bobherry Talk Edits 13:41, 18 April 2018 (UTC)

HI, I noticed you deleted the page Draft:A.s.car, as an A7. How bad was it? If it has potential, would you mind restoring it? Thanks, Jjjjjjdddddd (talk) 22:56, 20 April 2018 (UTC)

@Jjjjjjdddddd: - The text of the article was literally "a.s.car is a famous business company in world . This company work as a buy/sell luxury auto". I'd be happy to restore it if you'd like. SQL^{Query me!} 02:44, 21 April 2018 (UTC)

If it's that bad, never mind. Thanks! Jjjjjjdddddd (talk) 21:08, 21 April 2018 (UTC)

Thanks for the notification. I'd received a ping from the page, but hadn't had a chance to respond. --Ser Amantio di Nicolao^{Che dicono a Signa?}_{Lo dicono a Signa.} 01:24, 30 April 2018 (UTC)

Hi SQL. First off, I want to say thank you for creating SQLBot's function of removing AIV reports that have lingered for a long time without being acted upon - I think it's very helpful. However, I have a question about this edit by SQLBot. It removed a report from AIV because it had been listed for more than six hours. However, there was ongoing discussion (albeit a slow one) and the most recent comment was newer than six hours. I'm wondering if this is intentional (removing a report when the first comment exceeds more than six hours old, rather then when the most recent comment exceeds six hours old). I'm assuming that since this is probably a rare situation at AIV, it may not have been considered. -- Ed (Edgar181) 20:24, 14 May 2018 (UTC)

@Edgar181:The bot archives based on the original report. My thought process for this design choice was it could possibly otherwise encourage a disruptive situation where editors continually "bump" the report from falling off. SQL^{Query me!} 20:44, 14 May 2018 (UTC)

That makes sense. I guess either way is uncommon enough that it probably doesn't make much difference one way or the other. Anything being discussed for >6 hours at AIV should probably go to ANI anyway. Thanks. -- Ed (Edgar181) 22:34, 14 May 2018 (UTC)

• 216.162.40.0/21 (talk · contribs · WHOIS)

You blocked 216.162.47.18 (talk · contribs · WHOIS) as an open proxy, but it looks like the encompassing IP range (which is 216.162.40.0/21, per this), is a cloud hosting network. Could you block the /21 range please? Thanks. 187.220.107.91 (talk) 04:41, 15 May 2018 (UTC)

• Done! SQL^{Query me!} 21:08, 15 May 2018 (UTC)

Hi, you sent me an e-mail. I doon't know how to open or read it :P --TIAYN (talk) 21:46, 16 May 2018 (UTC)

You have to send it again, It was my old e-mail (which is deleted). --TIAYN (talk) 21:49, 16 May 2018 (UTC)

The last link I added was spam - at the time it did link to the event but this has subsequently been removed. It now appears as an unconstructive edit, but was done so in good faith at the time. 157.203.254.1 (talk) 08:50, 18 May 2018 (UTC)

Seems legit. TonyBallioni (talk) 23:26, 24 May 2018 (UTC)

So many people long gone. I didn't realize I'd gotten a Dlohcierekim support ~10 years ago. Thanks man! SQL^{Query me!} 23:58, 24 May 2018 (UTC)

My pleasure.-- Dlohcierekim (talk) 00:19, 25 May 2018 (UTC)

Hijiri88 - As you incorrectly noted here, I did not unblock DK2149 "for wikilawyering about not having been aware of having technically violated 3RR". If we look at the block log - it clearly reads "Editor understands why they were blocked, and how to avoid violating 3RR in the future. With consent from blocking admin - [2]". I clearly mentioned that the editor's original unblock request was insufficient, and offered some advice on how to correct it (which pretty much directly addressed the lawyering). I came across this block at CAT:RFU. Udarr made no such unblock request.

Darkknight2149 Please stop edit warring over this page. You are already on extremely thin ice for edit warring right now. I'm very tempted to full-protect the page for a while, or worse. The process is bold-revert-discuss, not bold-revert-discuss-revert-revert-revert-revert. No harm will come from the movie being called a remake vs a reboot for a bit while a consensus forms on the talk page. Remember that there is no deadline. Additional advice would be to stop threatening with an arbcom case. Either gather evidence, and go forward - or stop mentioning it. Edits like this, this, this, and more aren't really appropriate for a collaborative environment in my opinion. Either file a case, or let it go.

@ both of you - please stop pinging me. I don't need or want any more notifications or contact unless it's absolutely needed for the good of the project. This is going to sound pretty familiar - so there might be a lesson to be learned here. I will archive this message in a day or two - I don't require any replies. SQL^{Query me!} 03:11, 9 June 2018 (UTC)

There is no edit war. Hijiri88 is just stalking me (reverting me on more than one article) because he's holding a year-old WP:GRUDGE, he is angry because I was blocked and then unblocked, and has been doing stuff like this for well over a year. The whole debacle is complex, has been carried out on various Talk Pages and ANI reports for a really long time, and he and his buddy Curly Turkey don't plan on stopping. I'm going to be spending my weekend preparing a lengthy (and inevitably messy) ArbCom case. Rest in peace, me getting much sleep. DarkKnight2149 03:18, 9 June 2018 (UTC)

Thank you for the ping. I know you meant well, and don't think you actually unblocked him for wikilawyering over the applicability of 3RR and his prior unawareness of said, but I think you took AGF too far in assuming that just because he said he understood it that means he actually understood it -- his post-unblock behaviour shows he doesn't. DK2149 is wrong on the substance, and three editors other than myself have spontaneously come to this conclusion, and he doesn't even have STATUSQUO or BRD to justify his repeated reverts. He has been refusing to use the talk page (the only thing he's written is "the sources say reboot" despite the fact that the flawed logic of this argument had already been demonstrated). I don't think you were "wrong" not to unblock Udar55 as well or even not to check whether they also understood why they were unblocked, but I do think that your telling DK2149 now that he is required to engage in constructive discussion on the talk page in order resolve content disputes or any reverts he makes, regardless of quantity or length of time in between, are considered edit-warring would go a long way to resolving this.

All that said, if you don't want anything more to do with this I completely understand. If DK2149 continues edit warring he's going to shoot himself in the foot, and neither you nor EdJohnston are required to prevent that from happening. I totally understand not wanting to get involved in this -- I didn't even want to, but honestly I don't feel comfortable knowing DK's threats are never far away from me, CT and anyone else who commented in that ANI discussion 16 months ago.

Hijiri 88 (聖やや) 03:43, 9 June 2018 (UTC)

What are you going on about? You briefly replied on the Talk Page, and then immediately reverted me on the main page. That's not WP:BRD. And the only person with "a disruptive pattern with their edits" is you. Here you are again, going on about things that happened in 2016. And you are lying, stalking my recent contributions, WP:CANVASSing your friend Curly Turkey, being upset because I was unblocked (and for no other reason), ETC. You saw an opportunity and you pounced. I'm not even the only user that you have done this with.

"I didn't even want to, but honestly I don't feel comfortable knowing DK's threats are never far away from me, CT and anyone else who commented in that ANI discussion 16 months ago." - That's because you're constantly showing up and continuing your disruption, as you are doing now. This WP:SANCTIONGAMING and "playing the victim" is precisely why the ArbCom case (which you are probably trying to prevent) is now getting filed. DarkKnight2149 04:00, 9 June 2018 (UTC)

Hi SQL. I should point to the EF history.[3] -- zzuuzz ^(talk) 17:20, 11 June 2018 (UTC)

Welp, Deleted! SQL^{Query me!} 17:22, 11 June 2018 (UTC)

Feel free to maintain. I should point out that it works, but revdel'd edits don't appear in the log (only the number of hits increases). -- zzuuzz ^(talk) 17:25, 11 June 2018 (UTC)

Nah, just need one. I tested it against deleted edits, and it matched. I haven't used EF before ever, so good practice. SQL^{Query me!} 17:27, 11 June 2018 (UTC)

There is currently a discussion at Wikipedia:Administrators' noticeboard regarding an issue with which you may have been involved. Thank you. Bbb23 (talk) 17:16, 10 June 2018 (UTC)

Are you the founder of SQL? --84.147.33.60 (talk) 18:57, 17 June 2018 (UTC)

Nope, just a hobby. SQL^{Query me!} 01:01, 18 June 2018 (UTC)

(talk page stalker) Because he’s chill AF. TonyBallioni (talk) 03:11, 18 June 2018 (UTC)

Hello, SQL. Please check your email; you've got mail!
Message added 03:46, 20 June 2018 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the ((You've got mail)) or ((ygm)) template.

TheSandDoctor ^Talk 03:46, 20 June 2018 (UTC)

Hello, SQL. Please check your email; you've got mail!
Message added 05:37, 20 June 2018 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the ((You've got mail)) or ((ygm)) template.

Thanks TheSandDoctor ^Talk 05:37, 20 June 2018 (UTC)

This is the second time you've done this so I know it's not a one time mistake. In closing the unban request on User talk:Krish! you changed their sig and broke their report. I fixed the first time you did this but you might want to fix whatever it is that's causing this. --Tarage (talk) 01:12, 11 July 2018 (UTC)

Tarage - I'm not sure what the need for the accusatory tone is here (I'm clearly not breaking the editors unblock request on purpose. I've handled hundreds of unblock requests without issue), but *I* am the last editor to that page. I don't see where you "fixed" it at all. It appears to do with the editors use of "|" via HTML code & #124; in their sig. I have actually fixed it. It's going to happen using encoding like that in ones sig - I hadn't noticed the little | when I copied it over. SQL^{Query me!} 01:46, 11 July 2018 (UTC)

RE

It wasn't meant to be accusatory and I would have responded as such had you given me a hot second to reply instead of archiving it, but here we are. All I was saying was that in responding you broke it. The one I fixed was the previous request for help, something you also broke when you closed it. Sorry for attempting to tell you about a problem you were having. Obviously I've learned my lesson not to bother. --Tarage (talk) 05:00, 11 July 2018 (UTC)

	The Real Admin Award
	You're a real admin! TonyBallioni (talk) 18:46, 11 June 2018 (UTC)

Thank you for taking care of the "My Privates" user. Wikipedia doesn't need users like that person. I placed a speedy delete tag on his talk page if you feel the page should be deleted. AmericanAir88 (talk) 17:42, 17 July 2018 (UTC)

A tag has been placed on Template:Adminstats/Caulde, requesting that it be deleted from Wikipedia. This has been done under two or more of the criteria for speedy deletion, by which pages can be deleted at any time, without discussion. If the page meets any of these strictly-defined criteria, then it may soon be deleted by an administrator. The reasons it has been tagged are:

• It is an unambiguous misrepresentation of established policy. (See section T2 of the criteria for speedy deletion.)

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. Tyw7  (🗣️ Talk • ✍️ Contributions) Please ping me if you had replied 11:16, 20 July 2018 (UTC)

@Tyw7: - Please don't template me for pages created by a bot a decade or more ago. SQLBot probably created hundreds (if not thousands) of these, and a template / notification for each one would be pretty disruptive. SQL^{Query me!} 13:02, 20 July 2018 (UTC)

I blame WP:Twinkle. It auto sends the warning. --Tyw7  (🗣️ Talk • ✍️ Contributions) Please ping me if you had replied 13:42, 20 July 2018 (UTC)

@Tyw7: "Tag related options -> Uncheck "Notify creator if possible" for these types of things. SQL^{Query me!} 16:49, 20 July 2018 (UTC)

Thanks for the message about the IP block. The page was cleared before I could note a thanks. Donner60 (talk) 03:49, 23 July 2018 (UTC)

Thanks for protecting The X Factor (UK series 15). [4], [5], [6], [7] were created minutes after each other, and were doing the same thing, unsourced changes/vandalism acts. This is a patent sock puppetry case and maybe the accounts should be blocked? Ktrimi991 (talk) 22:59, 5 August 2018 (UTC)

@Ktrimi991: Blocked all but User:Louislouislouisniall - it looked like they were reverting vandalism? I get what you mean tho - some of this is getting hard to follow. SQL^{Query me!} 23:03, 5 August 2018 (UTC)

From a more careful check, yes, Louislouislouisniall reverted vandalism. For a moment I was not able to figure out what was happening, there were many edits in a few minutes. Maybe they were a group of friends trying to spend their free time in a very dumb way. Thanks again SQL. Cheers, Ktrimi991 (talk) 23:07, 5 August 2018 (UTC)

While I was trying to figure out what was happening on that article, they were enjoying their actions [8]. Wikipedia is a real social experiment, not just an encyclopedia. Ktrimi991 (talk) 23:14, 5 August 2018 (UTC)

Oh yeah, I pulled talkpage access. I figure it'll be coming from the others as well soon too. SQL^{Query me!} 23:16, 5 August 2018 (UTC)

Hi,

It looks like you blocked 209.58.128.0/20 (talk · contribs · WHOIS) (which is already globally locked), instead of 209.58.128.0/18 (talk · contribs · WHOIS).

There have been recent edits from IPs, such as 209.58.169.100 (talk · contribs · WHOIS) that are not included the blocked /20 range (and are inherently in the /18 range instead). Thanks. 2601:1C0:4401:24A0:8C08:620D:BCAF:5448 (talk) 04:35, 6 August 2018 (UTC)

The reason for that was the whois only lists the /20. That being said, it looks like all the ranges inside the /18 are also leaseweb, so blocked. SQL^{Query me!} 04:52, 6 August 2018 (UTC)

Sorry to be getting back to you so late: Curse you real world! I was referring to what I perceived as a lack of temperament on the candidate's behalf. I could go further if you'd like me to. Informata ob Iniquitatum (talk) 02:03, 18 August 2018 (UTC)

That ship's already sunk. No thanks. SQL^{Query me!} 02:04, 18 August 2018 (UTC)

Hi,

I was wondering whether the use of SQL/AFC-Ores had been dropped. It does't appear to be updating (assuming it's not my computer, which is always possible!). Obviously if it's meant not to be doing it, that's fine, I just wanted to be sure - for the short time I used it, it was a great help.

Nosebagbear (talk) 16:02, 23 August 2018 (UTC)

@Nosebagbear:Oh my, you're right! It looks like it's been stalled since 8/8/18! I'll get it restarted right away. SQL^{Query me!} 16:06, 23 August 2018 (UTC)

Cheers for the quick fix! Nosebagbear (talk) 20:27, 23 August 2018 (UTC)

	The Technical Barnstar
	For the fantastic AIV analysis tool! Impressive technical work. Enterprisey (talk!) 01:40, 1 September 2018 (UTC)

Hello, SQL. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the ((You've got mail)) or ((ygm)) template.‐‐1997kB (talk) 16:28, 4 September 2018 (UTC)

Thanks again for the very useful tool. Would it be possible to have the task that updates the front page of the tool also add a timestamp, so that I can see what time the front page was last updated? Thanks! Enterprisey (talk!) 19:52, 11 September 2018 (UTC)

@Enterprisey:Yeah, I don't think that would be a problem. I'll work it in ASAP. SQL^{Query me!} 09:56, 12 September 2018 (UTC)

@Enterprisey:  Done SQL^{Query me!} 07:07, 15 September 2018 (UTC)

I currently have a query to find really old uploads:- https://quarry.wmflabs.org/query/29813

It's currently based on pageid.

However more correctly it should be listing any unsourced file that was uploaded prior to Sept 18th 2005 (which is when sourcing rule began to be enforced more vigoursly.) If the query can be tweaked to rely on a timestamp for the first upload instead. ShakespeareFan00 (talk) 19:02, 20 September 2018 (UTC)

@ShakespeareFan00: - If I understand correctly, the answer here is to add something like this:

JOIN logging_logindex on log_action="upload" AND log_namespace=6 AND log_timestamp < 20050918000000 and page_title = log_title

See: my fork. SQL^{Query me!} 19:17, 20 September 2018 (UTC)

Thanks... I think the query might miss a few that pre-date the logs possibly... ShakespeareFan00 (talk) 19:19, 20 September 2018 (UTC)

Hmm. The earliest log entry I can find was in 2004:

MariaDB [enwiki_p]> select min(log_id), log_timestamp from logging_logindex where log_type = "upload" and log_namespace = 6 and log_timestamp < 20050918000000 limit 1;
+-------------+----------------+
| min(log_id) | log_timestamp  |
+-------------+----------------+
|           2 | 20041223032426 |
+-------------+----------------+

I'll do some more digging and get back to you shortly. SQL^{Query me!} 19:22, 20 September 2018 (UTC)

Did a quick check and there's a difference of 664 files between the query with the log entry timestamp join and the one without it. There must be some REALLY old uploads, if they predate the upload log. ShakespeareFan00 (talk) 19:25, 20 September 2018 (UTC)

There are:

MariaDB [enwiki_p]> select min(img_timestamp) from image limit 1;
+--------------------+
| min(img_timestamp) |
+--------------------+
| 20020804195517     |
+--------------------+
1 row in set (0.01 sec)

So, another way to skin the cat is:

JOIN image on img_timestamp < 20050918000000 and page_title = img_name

Which returns 4498 entries. I'm not sure how to use the oldimage table in the same query (for files that were re-uploaded) without involving an outside scripting language like PHP/python/perl/ruby/qbasic. SQL^{Query me!} 19:30, 20 September 2018 (UTC)

Thanks, for the efforts so far. Maybe soemthing to take to Village Pump Technical? ShakespeareFan00 (talk) 20:06, 20 September 2018 (UTC)

Hi SQL. I'm not sure if you're around at the same timezones as I am, but I regularly arrive to an AIV backlog around this time, particularly on certain days, when there are actually very few admins around and even rampant vandals can go unattended for a few hours. To say that enough admins have eyeballed the reports is optimistic. I'd like to see the standard 6 hours extended to 8. I note you and others have previously expressed a preference for this figure, so without a strong consensus against it, perhaps you could have a tweak. At least, register my concern about 6 being too short. Thanks. -- zzuuzz ^(talk) 07:24, 28 April 2018 (UTC)

@Mz7, TomyBallioni, Edgar181, HJ Mitchell, Tazerdadog, and Luk: - As above, my personal preference is 8 hours, and I think Zzuuzz makes a good point. What's your opinions? SQL^{Query me!} 07:44, 28 April 2018 (UTC)

@TonyBallioni: Second try at spelling stuff right. SQL^{Query me!} 07:45, 28 April 2018 (UTC)

I don't have any strong opinions either way. I think I originally suggested 8 hours might be too long because it is rare for a report to go 8 hours without any admin eyes, but it seems Zzuuzz is right that at certain times of the day, there are less admins who watch AIV available. Mz7 (talk) 07:49, 28 April 2018 (UTC)

As an aside - do reports in that timezone really not even see even one single set of admin eyeballs in 6 hours? If so, we are in some sort of desperate need for change. Or are the more-borderline reports being ignored in this timezone because they're borderline on a good day - and eventually the bot will deal with them? SQL^{Query me!} 07:57, 28 April 2018 (UTC)

I've asked for stats on this before, without success. Anecdotally, I have noticed for many years that there is an issue while the US is asleep, and especially at weekends. I wouldn't say that no admins are around, as some obviously are, but I have always thought there was an insufficient number, and in this case not enough to meet the 'enough eyeballs' criteria. Rampant vandals will be blocked before 6 hours, but others which can (or perhaps should) be blocked but aren't urgent will often wait. It's very noticeable to me - I sometimes enjoy the peace and quiet catching up on admin tasks on a weekend morning, other times I seem to be the only person battling rampant vandals. I have an alternative suggestion, which is to set up an intelligent cron job which can deal with US weekends. -- zzuuzz ^(talk) 08:22, 28 April 2018 (UTC)

Looking over the the last 10 that were removed by the bot - there was indeed one that went un-blocked which I probably would have blocked at the time. Some more eyes on those 10 reports going back to 4/1 might be a good idea. SQL^{Query me!} 08:29, 28 April 2018 (UTC)

No strong opinion on the appropriate timeframe. Both 6 and 8 hours are reasonable. Tazerdadog (talk) 10:49, 28 April 2018 (UTC)

In my experience, any report that has been left for more than a few hours is not a blockable offense. Personally I think waiting even 6 hours to clear them is long. I'm in the US and typically editing during busier hours though. -- Ed (Edgar181) 11:19, 28 April 2018 (UTC)

• I was actually thinking we should lower it to 4 hours. I consider overzealous blocking and reporting of high school kids and the like to be worse for the encyclopedia than the vandalism itself. If something has sat here for that long with no action and is not ongoing, we shouldn’t be blocking. If it is ongoing, I’m confident it will be back here within minutes. If we actually mean what we say about blocks being preventative, and AIV only being for clear vandalism, someone who hasn’t edited in 8 hours (or longer) on a dynamic IP shouldn’t be blocked, even if they would have been eligible when initially reported. Accounts are more complex, but I’d much rather take the chance and not block a stale minor vandal and potentially gain a contributor down the line, than block someone for doing dumb stuff that they stopped doing 8+ hours ago and that poses no real threat to the encyclopedia. Maybe I’m too optimistic here, but I see no real downside to waiting to block until someone is actually active and a lot of downside. TonyBallioni (talk) 13:52, 28 April 2018 (UTC)
• Ideally, and I know we don't live in an ideal world, but ideally, the bot would have a sliding scale of retention times, perhaps between 2 to 8 hours, and would change based on how active we (admins) are at blocking accounts reported on AIV already, and how active we are at blocking in general. I don't know whether a compromise approach to this might be to decide on appropriate retention times based on analysis of activity levels for various times, and have the bot change accordingly. Nick (talk) 14:50, 28 April 2018 (UTC)
  • I like that idea (poor SQL) but I think something based on recent admin edits/activity would be better than on AIV blocks. Pretend you have a board filled with 10 bad reports. None of them are blocked because none of them are good, so the bot lets them stay 8 hours. You end up with them staying there and then you get one of the panic threads at AN because no one has blocked the "vandals".
    I dunno. I'm definitely on the less-likely to see vandalism and block side of the spectrum (I was even when I used STiki and wasn't an admin), so I can get the concerns others might have who view things differently than me. I'm afraid though, having watched SQLBot in process, an 8 hour timeframe would largely make the bot useless, and we'd be back to the semi-weekly "the sky is falling" threads at AN/ANI, which it has actually done a pretty decent job of stopping from occurring. TonyBallioni (talk) 14:59, 28 April 2018 (UTC)
  • @Nick and TonyBallioni: - I like this idea. I'll have SQLBot start updating this query here on every run, and we can start to look at what those values should be. SQL^{Query me!} 15:17, 28 April 2018 (UTC)

So lets look at variable timing

I've collected data for a while. Here's the results (by UTC Hour):

   [0] => 64
   [1] => 62
   [2] => 58
   [3] => 52
   [4] => 46
   [5] => 44
   [6] => 42
   [7] => 41
   [8] => 44
   [9] => 47
   [10] => 49
   [11] => 53
   [12] => 62
   [13] => 67
   [14] => 72
   [15] => 75
   [16] => 76
   [17] => 76
   [18] => 77
   [19] => 77
   [20] => 78
   [21] => 78
   [22] => 74
   [23] => 67

• Average active admins: 62
• Max admins active: 107
• Min admins active: 2
• Records used: 5174

In chart form:

Graphs are unavailable due to technical issues. There is more info on Phabricator and on MediaWiki.org.

Here's what I'm thinking:

~60 admins active is roughly the median. As we approach 80 admins active, shorten down to a minimum of 4 hours. As we approach 40 admins active, lengthen out to a max of 8 hours.

I haven't worked on this for a while, so I'll reping TonyBallioni. SQL^{Query me!} 02:13, 28 August 2018 (UTC)

If there's one thing I'm consistently terrible at in this thread, it's pings. @Zzuuzz and Nick: were missed because I can't template right... SQL^{Query me!} 02:14, 28 August 2018 (UTC)

Oh look, SQL being all fancy, yeah, if you can figure out a variable timing piece, that sounds like a good idea. I'd also like it to autoremove any report with the string "genre warring" in it, but doubt that would get approved . TonyBallioni (talk) 02:16, 28 August 2018 (UTC)

Interesting. So my initial comment was right on time :) I'd assume that that more admins are relatively inactive during the summer, roughly in line with the vandals, but I'd also be interested to see a weekday/weekend breakdown, if that's something you can plug in, because I'll bet that's a variable. I'd also be interested to see what proportion of admins deal with AIV reports. But it's a useful proposal. Thanks for the crunching. -- zzuuzz ^(talk) 09:39, 28 August 2018 (UTC)

Thanks for everyone's feedback. This is now live. There's a bit of explanation of the behind-the-scenes stuff at User:SQL/AIVStale. SQL^{Query me!} 11:42, 5 September 2018 (UTC)

SQLBot Error on AIV?

There appears to be an issue with the above bot. It should not have removed just my edit here. If the report with my edit was considered stale, it should have removed the user (Daffa Dilantra) my comment applied to and my comment. KnightLago (talk) 20:16, 18 August 2018 (UTC)

@KnightLago: Unfortunately, this happens when a bot helps with a busy page. You saved your edit at just the right time in the milliseconds between the bot reading the page, and writing the new page. SQL^{Query me!} 20:23, 18 August 2018 (UTC)

Understood. Not a big deal. Thanks. KnightLago (talk) 20:25, 18 August 2018 (UTC)

Link to the test page | Archived TP Discussion | Obsolete notes

So, it's taken a long time (mostly occupied by putting off working on it), but I got a web tool running of the old aivanalysis I would run offline. It works by manually walking and evaluating every one of the 1.5 million revisions to WP:AIV, and saving to a MySQL Database which takes about a week of machine time. I split it into ~1 year chunks, each chunk running a separate process on the open grid. At the moment, 2007, 2008, 2016, and 2017 are still processing, but there are 416,252 processed reports to work off of. Hammersoft, 72, Serial Number 54129, you had comments in the previous discussion, I figured I'd let you know about the update.

There are still some known bugs that affected early versions of the old tool that I'm working on.

•  Fixed The 1= bug
•  Fixed The "User:", "User talk:", and "User_talk" bugs
•  Can't fix The oversight bug (this seems a little more like an issue with mediawiki, but I can work around it pretty easily by screen-scraping - This has been fixed, apparently. I could scrape Special:CentralAuth, but I'd rather not)
•  Can't fix The rangeblock bug (Which is likely not something I will be able to correct).
•  Fixed The non-registered user bug
• The renamed editor bug
•  Fixed There's an issue that I'm aware of - which is fixed in the code, but won't show until the next walk over AIV's revisions: In a limited circumstance (removing characters from a report), you now "own" the report.

Anyhow, as always, any feedback is appreciated. SQL^{Query me!} 03:04, 25 August 2018 (UTC)

Hi SQL. Thanks for the ping. I understand that this is a test page, so it might be something you're already aware of, but when looking at the list, I noticed a few reports dated 2012/13/14/15 which can't be correct since I only registered my account in 2016. There are only a few like this, but I can't say for sure about the accuracy of the rest without going through each one in detail (which would take quite a long time!). It lists the report correctly: example, but says the report was made at "20131029182917". Thanks, 72 (talk) 10:14, 25 August 2018 (UTC)

I think the pattern is that it is relating the timestamp to other AIV reports/entries of the block log. In the case of this report, it says it was made on "20071210101100", which is one minute away from a block made by User:Kafziel. 72 (talk) 10:21, 25 August 2018 (UTC)

• The report for me still shows the same problems, but some of them just aren't rectifiable (see my comments in the archived discussion). The renamed false negatives are perhaps rectifiable, and as you are aware that remains a (minor) problem. Overall, I still think this is a FANTASTIC tool. --Hammersoft (talk) 13:35, 25 August 2018 (UTC)
• I've fixed a lot of the issues. I've got to ponder on how to address 72's issue. SQL^{Query me!} 19:29, 27 August 2018 (UTC)

I've got a query that I've used for this for a while, figured it might benefit others as a tool. Very much a WIP, and unstable. Will move it to it's own project from my incubator before long. https://tools.wmflabs.org/aivanalysis/compare.php.

Tool attempts to compare editor interaction by what category edited pages belong to. Tool attempts to filter out maintenance categories.

TODO:

• More than 2 editors. Possibly up to 5.
• Export to it's own project
• I need to come up with a skin... Not just for this tool, but all of mine.
• Header/footer/link to home, tool is very raw.
• Tool can take a "long" time to run (up to 90s) on editors with a lot of edits. Possibly "LIMIT 500"?. It's already limited to 30 days.

$ignore = array( 
	"All_articles_containing_potentially_dated_statements", 
	"All_articles_with_specifically_marked_weasel-worded_phrases", 
	"All_pages_needing_cleanup", 
	"All_articles_needing_additional_references", 
	"All_articles_that_may_contain_original_research", 
	"Pages_with_missing_files", 
	"Wikipedia_pages_under_discretionary_sanctions", 
	"Redirects_from_other_capitalisations", 
	"Unprintworthy_redirects", 
	"Redirects_from_ambiguous_terms", 
	"Redirects_from_modifications", 
	"Redirects_from_adjectives", 
	"Articles_with_hCards", 
	"Articles_with_inconsistent_citation_formats", 
	"Infobox_person_using_alma_mater", 
	"Pages_using_infobox_scientist_with_unknown_parameters", 
	"Redirects_from_alternative_names", 
	"Redirects_to_sections", 
	"All_articles_lacking_reliable_references", 
	"All_articles_needing_expert_attention", 
	"All_articles_that_are_too_technical", 
	"All_articles_with_broken_links_to_citations", 
	"All_articles_with_dead_external_links", 
	"All_articles_with_failed_verification", 
	"All_self-contradictory_articles", 
	"Interlanguage_link_template_link_number", 
	"Pages_with_missing_ISBNs", 
	"Placeholder_names", 
	"Articles_containing_video_clips", 
	"Articles_incorporating_Cite_DNB_template", 
	"Coordinates_on_Wikidata", 
	"All_article_disambiguation_pages", 
	"All_disambiguation_pages", 
	"Disambiguation_pages", 
	"Disambiguation_pages_with_short_description", 
	"All_Wikipedia_articles_needing_clarification", 
	"Lists_of_lists", 
	"Wikipedia_indefinitely_move-protected_pages", 
	"Wikipedia_indefinitely_semi-protected_pages", 
	"Articles_containing_Danish-language_text",
	"Articles_containing_French-language_text",
	"Articles_containing_German-language_text",
	"Articles_containing_Gothic-language_text",
	"Articles_containing_Icelandic-language_text",
	"Articles_containing_Old_English-language_text",
	"Articles_containing_Old_High_German-language_text",
	"Articles_containing_Punic-language_text",
	"Articles_containing_Swedish-language_text",
	"Articles_containing_Hebrew-language_text",
	"Articles_containing_Russian-language_text",
	"Articles_with_Curlie_links",
	"Articles_with_LibriVox_links",
	"Articles_with_Open_Library_links",
	"All_Wikipedia_GA-Class_vital_articles",
	"All_Wikipedia_level-4_vital_articles",
	"All_Wikipedia_vital_articles",
	"All_Wikipedia_vital_articles_in_Society",
	"Wikipedia_articles_with_LNB_identifiers",
	"Wikipedia_articles_with_MusicBrainz_identifiers",
	"Pages_using_citations_with_accessdate_and_no_URL",
	"Pages_using_web_citations_with_no_URL",
	"Pages_with_broken_reference_names",
	"Pages_with_reference_errors",
	"All_NPOV_disputes",
	"All_articles_with_peacock_terms",
	"All_articles_with_style_issues",
	"All_articles_lacking_sources",
	"All_stub_articles",
	"Webarchive_template_wayback_links",
	"All_articles_with_unsourced_statements" );
$ignore_wild = array(
	"Articles_containing_potentially_dated_statements_from*",
	"Use_dmy_dates_from*",
	"Use_British_English_from*",
	"Articles_lacking_in-text_citations_from*",
	"Articles_lacking_reliable_references_from*",
	"Articles_incorporating_a_citation_from*",
	"Articles_incorporating_text_from*",
	"Articles_lacking_sources_from*",
	"Articles_needing_POV-check_from*",
	"Articles_needing_additional_categories_from*",
	"Articles_needing_additional_medical_references_from*",
	"Articles_needing_expert_attention_from*",
	"Articles_needing_more_viewpoints_from*",
	"Articles_needing_sections_from*",
	"Articles_needing_the_year_an_event_occurred_from*",
	"Articles_needing_translation_from*",
	"Articles_prone_to_spam_from*",
	"Articles_requiring_tables_from*",
	"Articles_slanted_towards_recent_events_from*",
	"Articles_tagged_with_the_inline_citation_overkill_template_from*",
	"Articles_that_may_be_too_long_from*",
	"Articles_with_*",
	"Articles_needing_*",
	"Cleanup_tagged_articles_*",
	"Wikipedia_*",
	"Articles_needing_cleanup_from*",
	"Articles_with_unsourced_statements_from*",
	"Wikipedia_articles_incorporating_a_citation_from*",
	"Articles_with_specifically_marked_weasel-worded_phrases_from*",
	"Articles_needing_additional_references_from*",
	"Articles_with_sections_that_need_to_be_turned_into_prose_from*",
	"Articles_that_may_contain_original_research_from*");

I'd love to hear any feedback, or suggestions. SQL^{Query me!} 01:19, 21 September 2018 (UTC)

Good stuff, nice job! It may be nice to filter categories with JS by typing in a box at the top, but that's low-priority. Enterprisey (talk!) 02:25, 21 September 2018 (UTC)

https://quarry.wmflabs.org/query/18895

It was returning more results than expected...

Intended purpose is to find stuff that's tagged for Commons but shouldn't be. ShakespeareFan00 (talk) 16:33, 21 September 2018 (UTC)

"Added welcome template to user talk page"

Thank you for welcoming hundreds of users, for fighting vandalism with precise messages, for offering service for the Electoral Commission, for providing technical analysis tools, for service from 2007, - repeating (19 February 2009): you are an awesome Wikipedian!

--Gerda Arendt (talk) 23:02, 9 October 2018 (UTC)

Hi, SQL. I see you've already seen the results, but just formally letting you know that you have been appointed by the community as an Electoral Commissioner for WP:ACE2018. The coordination pages can be found at WP:COORD18 and WT:COORD18. Congrats!  Swarm  talk  02:10, 20 October 2018 (UTC)

I just noticed the message. My condolences... Lourdes 23:24, 4 November 2018 (UTC)

Lourdes, I'm sorry I missed this message - I haven't been around a whole lot lately. Thank you for your kind words. SQL^{Query me!} 23:30, 7 November 2018 (UTC)

Hi, SQL. Please see WT:COORD18#Fred Bauder at your earliest convenience. The Commission needs to rule on an emergency situation, and it currently appears that you are needed to be the deciding vote. Thanks,  Swarm  talk  23:53, 11 November 2018 (UTC)

Swarm, understood. Im working. I will catch up as soon as i get home but it is likely to be a couple of hours yet. SQL^{Query me!} 01:26, 12 November 2018 (UTC)

Hello, SQL. You have new messages at Beasting123's talk page.
Message added 21:13, 13 November 2018 (UTC). You can remove this notice at any time by removing the ((Talkback)) or ((Tb)) template.

Sorry. The message that came up when I tried to edit told me to try UTRS or my talk page. I'll try that.

(You don't have anything on my talk page, I've never used twinkle for this before. Sorry.)Beasting123 (talk) 21:13, 13 November 2018 (UTC)

You recently offered a statement in a request for arbitration. The Arbitration Committee has accepted that request for arbitration and an arbitration case has been opened at Wikipedia:Arbitration/Requests/Case/Fred Bauder. Evidence that you wish the arbitrators to consider should be added to the evidence subpage, at Wikipedia:Arbitration/Requests/Case/Fred Bauder/Evidence. Please add your evidence by November 27, 2018, which is when the evidence phase closes. You can also contribute to the case workshop subpage, Wikipedia:Arbitration/Requests/Case/Fred Bauder/Workshop. For a guide to the arbitration process, see Wikipedia:Arbitration/Guide to arbitration. For the Arbitration Committee, --Cameron₁₁₅₉₈ ^(Talk) 21:08, 16 November 2018 (UTC)

Hello, SQL. Please check your email; you've got mail! The subject is Contains the word "ACE 2018".
Message added 07:46, 17 November 2018 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the ((You've got mail)) or ((ygm)) template.

— regards, Revi 07:46, 17 November 2018 (UTC)

Hi SQL

Just a query about User:SQL/AFC-Ores - normally the system updates every couple of hours. I was just wanting to check that it acting as planned rather than frozen - obviously the AfC numbers have dropped enormously recently, so I wasn't sure whether it is acting normally just for those conditions.

Cheers,

Nosebagbear (talk) 21:07, 22 November 2018 (UTC)

Nosebagbear, uh oh! Ill check on it in a bit. SQL^{Query me!} 21:41, 22 November 2018 (UTC)

Nosebagbear, I found the issue - it should work on its next run. SQL^{Query me!} 00:10, 23 November 2018 (UTC)

Howdy. Wanted to check in with you regarding Wikipedia:Bots/Requests for approval/ZackBot 11. I completed the trial with no issues but hadn't heard anything back for a week. If you have some time to take a look, would love any feedback. :-) --Zackmann (^{Talk to me}/_{What I been doing}) 22:07, 27 November 2018 (UTC)

Hey. Just checking in again. Any chance you can give me feedback on my trial run? Wikipedia:Bots/Requests for approval/ZackBot 11? --Zackmann (^{Talk to me}/_{What I been doing}) 00:24, 6 December 2018 (UTC)

Can I just ask is there a reason you aren't responding? I don't mean to be accusatory, but you've been active on here and even left a comment on my self-nomination but haven't responded to any of my pings regarding my BRFA. Just trying to understand what's going on. --Zackmann (^{Talk to me}/_{What I been doing}) 05:33, 6 December 2018 (UTC)

Zackmann08, I typically don't like to approve bots that I set to trial. There should be more than one bag's input. Also, frankly, I haven't had the time to examine all the edits that the trial generated. SQL^{Query me!} 06:33, 6 December 2018 (UTC)

Well thanks for the response. --Zackmann (^{Talk to me}/_{What I been doing}) 07:26, 6 December 2018 (UTC)

Hi SQL, your BRFA (Wikipedia:Bots/Requests for approval/SQLBot-AmazonAffiliateRemoval) has been approved for trial, yada yada yada.. — xaosflux ^Talk 01:30, 11 December 2018 (UTC)

	The Barnstar of Diligence
	For your service as a member of the Electoral Commission in the 2018 Arbitration Committee elections. This year presented new challenges that past commissioners didn't have to face. Thanks for everything you did in your role. Mz7 (talk) 07:28, 14 December 2018 (UTC)

I noticed that you have blocked some previous IP socks of Apollo the Logician with ((colocationwebhost)) for 2 years. I filed new SPI with a fresh IP, 191.101.42.242 (talk · contribs · WHOIS), at Wikipedia:Sockpuppet investigations/Apollo The Logician. Is the new IP a webhost as well, because myip.ms would indicate something like that, but I'm just not sure how to read their website? If so, perhaps you can block the range 191.101.42.0/24 (talk · contribs · WHOIS). --Pudeo (talk) 14:53, 16 December 2018 (UTC)

• 191.101.42.0/24 · contribs · block · log · stalk · Robtex · whois · Google
• 181.215.15.0/24 · contribs · block · log · stalk · Robtex · whois · Google

Pudeo, Yep, looks to be a webhost, along with 181.215.15.0/24. Blocking. SQL^{Query me!} 18:02, 16 December 2018 (UTC)

	Happy Holidays! May your winter holidays be filled with joy, laughter and good health. Wishing you all the best in 2019 and beyond.

--Cameron₁₁₅₉₈ ^(Talk) 04:30, 24 December 2018 (UTC)

	The Random Acts of Kindness Barnstar
	Thank you for the welcome, it really helps! :) Majora majora majora (talk) 02:24, 25 December 2018 (UTC)

Merry Christmas and a Prosperous 2019!

Hello SQL, may you be surrounded by peace, success and happiness on this seasonal occasion. Spread the WikiLove by wishing another user a Merry Christmas and a Happy New Year, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2019. Happy editing, TheSandDoctor Talk 07:58, 25 December 2018 (UTC) Spread the love by adding ((subst:Seasonal Greetings)) to other user talk pages.

Thank you for all that you do for the project, as an administrator, BAG, and editor. Without editors like you, this project would be worse off. Keep up the good work! - From my family to yours, TheSandDoctor ^Talk 07:58, 25 December 2018 (UTC)

Happy New Year!

SQL,
Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.
Donner60 (talk) 07:17, 31 December 2018 (UTC)

   Send New Year cheer by adding ((subst:Happy New Year fireworks)) to user talk pages.

Hello, SQL. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the ((You've got mail)) or ((ygm)) template.TheSandDoctor ^Talk 01:14, 8 January 2019 (UTC)

Please explain [9] and previous removals. Seems to be an error. Tgeorgescu (talk) 19:14, 15 January 2019 (UTC)

Tgeorgescu, Thanks for the heads up. Looks like it was a small regex error. You used a timestamp, "17:42, 5 January 2019 (UTC)" formatted exactly like the timestamp in a signature. The bot read the first timestamp it came across in that line, and used it. I've corrected the regex to end in "$", which specifies that the timestamp must be at the end of the line only. I've just re-ran to make sure, and it has fixed the issue. SQL^{Query me!} 19:27, 15 January 2019 (UTC)

Hi SQL, for Wikipedia:Bots/Requests for approval/OutreachDashboardBot, can you change the expiration to indefinite for 'eventcoordinator' and remove 'confirmed' access at Special:UserRights/OutreachDashboardBot. Thank you, — xaosflux ^Talk 18:34, 29 January 2019 (UTC)

Xaosflux,  Done SQL^{Query me!} 19:36, 29 January 2019 (UTC)

I seem to recall realizing that this needed doing at some point yesterday, but it slipped my mind until now. Thanks for getting that SQL. --TheSandDoctor ^Talk 01:50, 31 January 2019 (UTC)

Thanks for taking over updates of the RFU report. If this is going to be permanent, would you consider getting the bot to add ((shortcut|WP:RFUR|WP:RFUT)) to the top of it? Thanks. O Still Small Voice of Clam 17:54, 31 January 2019 (UTC)

Voice of Clam, It isn't intended to be permanent, just until T213475 is resolved. That being said, I can still add that shortcut code in the meanwhile if you'd like. SQL^{Query me!} 18:08, 31 January 2019 (UTC)

 Done SQL^{Query me!} 19:08, 31 January 2019 (UTC)

Hi SQL, I see you're on call--would you mind looking over my shoulder here? CU revealed a bunch of accounts, and most of their efforts were stopped by the filter, but maybe you have a better idea of how to block and how long to block. Thanks! Drmies (talk) 18:29, 31 January 2019 (UTC)

Drmies, Looks like HostRoyale ( https://hostroyale.com/ ). Hosting only, no residential connectivity. I normally block VPS providers using ((colocationwebhost)) for 2 years. Looks like a lot of it has been blocked already over the last year: rangefinder results SQL^{Query me!} 18:35, 31 January 2019 (UTC)

I've gone ahead and blocked every other host royale range, and a couple other related ranges as well. SQL^{Query me!} 18:39, 31 January 2019 (UTC)

Hey. I opened a phab ticket (phab:T215132) but no one has responded yet - any chance you can give me bot rights over there for a bit? I may be running a bot task here manually, and I want to see how the interface is different (if at all) when you have bot rights - like can you manually choose if an edit should me marked as a bot edit or not, stuff like that. Thanks, --DannyS712 (talk) 02:43, 5 February 2019 (UTC)

DannyS712, Sure, what account, and which wiki? SQL^{Query me!} 02:45, 5 February 2019 (UTC)

@SQL: This account (DannyS712), and on enwiki. Thank you so much --DannyS712 (talk) 03:31, 5 February 2019 (UTC)

DannyS712,  Done SQL^{Query me!} 03:33, 5 February 2019 (UTC)

 You are invited to join the discussion at User talk:DannyS712 test/chance.js. DannyS712 (talk) 08:30, 11 February 2019 (UTC)

Awesome

Ten years!

--Gerda Arendt (talk) 07:37, 19 February 2019 (UTC)

Hey there If you take a look at User:London International Education College it's pretty clear they have a COI or aren't quite familiar with how Wikipedia works. I'm wondering what is the usual course of action in such a case? Should notices be posted to COIN only after the user has made a problematic edit? (I just chose an admin at random to ask) TIA Hydromania (talk) 06:00, 21 February 2019 (UTC)

and never mind, It's already been deleted. Hydromania (talk) 06:03, 21 February 2019 (UTC)

Happy First Edit Day!

Have a very happy first edit anniversary!
From the Birthday Committee, CAPTAIN RAJU^(T) 00:38, 22 February 2019 (UTC)

What made you want to block Oshwah with that strange block expiration 1975 or something like that? LOL "I'M SURE I"LL HAVE TO APOLOGIZE FOR THIS LATER" --Thegooduser Life Begins With a Smile :) 🍁 01:24, 12 March 2019 (UTC)

(talk page stalker) Because he deserved it. TonyBallioni (talk) 01:25, 12 March 2019 (UTC)

for his crazy hair? --Thegooduser Life Begins With a Smile :) 🍁 01:26, 12 March 2019 (UTC)

Sound like a good enough reason. TonyBallioni (talk) 01:28, 12 March 2019 (UTC)

A good reason as any, in my book. ;-) ~Oshwah~^{(talk) (contribs)} 01:29, 12 March 2019 (UTC)

Thegooduser, There's never a bad time to block Oshwah back to 1975... SQL^{Query me!} 07:08, 12 March 2019 (UTC)

Never ;-) ~Oshwah~^{(talk) (contribs)} 07:11, 12 March 2019 (UTC)

Hi, please see my question on this request. Just Chilling (talk) 00:04, 17 March 2019 (UTC)

Hi there,

I'm aware you're busy and this is the definition of non-critical, so obvs wait as RL supercedes.

User:SQL/AFC-Ores isn't functioning, and hasn't for the last 12 days. I'd wondered if this was anything to do with the migration from Trusty to Stretch that knocked a few other things offline a couple of weeks ago.

In any case, cheers Nosebagbear (talk) 10:39, 28 March 2019 (UTC)

Nosebagbear, Good catch. It looks like it was running out of memory. I've allocated 1Gb to it, we'll see if it finishes it's next run. As an aside, with the new AFC tools - is there still a need for afc-ores? SQL^{Query me!} 01:21, 30 March 2019 (UTC)

Nosebagbear, Looks like it's up and running again. Thanks for the notification. Feel free to let me know if it misses a day. SQL^{Query me!} 02:35, 30 March 2019 (UTC)

@SQL: - Cheers for fixing that. Purpose-wise, I usually use it to review large numbers of copyright risk drafts Nosebagbear (talk) 11:31, 30 March 2019 (UTC)

I was looking at this tool for the first time, and I'd just like to double check with you that I'm interpreting the results correctly before I place any block based on it. The edits of 208.84.155.212, which is part of the 208.84.152.0/22 range used by a company called Total Server Solutions L.L.C., raised my suspicions so I used the tool to check that IP address. Can you check the results and confirm my interpretation that this range is a proxy service and/or VPN service? @MusikAnimal: Pinging MusikAnimal too, if you'd like to respond instead. Thank you. -- Ed (Edgar181) 11:49, 2 April 2019 (UTC)

Edgar181, Yep, total server solutions is a webhost, and blocking that range would be appropriate. SQL^{Query me!} 17:44, 2 April 2019 (UTC)

Thanks for taking the time to have a look. Regards, -- Ed (Edgar181) 18:13, 2 April 2019 (UTC)

Just so I'm clear this big wall of text and diffs is "no actual evidence presented"? I am actually asking. - Neutralhomer • Talk • 07:23 on April 10, 2019 (UTC)

Neutralhomer, Would you please point me to an admin action that was taken inappropriately? As Swarm mentions, admins are not required to take actions upon request. As I stated, I cannot look into the CU issues - I lack that access, as most of us do. Your best bet w/r/t inappropriate checks would be ARBCOM or Ombuds. My personal experience with Ombuds on the topic of inappropriate access to PII would be to contact arbcom first :/ SQL^{Query me!} 07:28, 10 April 2019 (UTC)

The big wall of text was the admin action taken inappropriately. But for something more bite-sized, the last bullet on the wall of text, especially him closing the SPI while a CU request was still open is the most egregious. - Neutralhomer • Talk • 07:33 on April 10, 2019 (UTC)

Neutralhomer, Fair enough. I disagree - but as you feel I've closed the topic inappropriately, I would be happy to reverse my close, and leave it for someone else. SQL^{Query me!} 07:35, 10 April 2019 (UTC)

Nah. I accept I was in the vast minority there. So, keeping it open wouldn't help. I just wanted to clarify what you said. We are agreeing to disagree (which is cool). You actually explained it in a calm and cool manner, so I appreciate that. But I'm accepting that the discussion had ran it's course. Thanks... Neutralhomer • Talk • 07:39 on April 10, 2019 (UTC)

I reverted your reopening of the discussion per my comment above. I appreciate your doing that, but again, I accept it's closure and that it has run it's course. I reverted it with the edit summary "Accepting the discussion has ran it's course and reclosing the discussion with SQL's result message. Reverting AGF.". Thanks again... Neutralhomer • Talk • 07:53 on April 10, 2019 (UTC)

• 2604:2D80:803D:8D8F::0/64 (talk · contribs · deleted contribs · filter log · WHOIS · RBLs · block user · block log)
• 2604:2D80:803D:8D8F::0/48 (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log)

It seems a range block of at least the /64 or maybe the /48 would be appropriate? —[AlanM1(talk)]— 03:33, 12 April 2019 (UTC)

AlanM1, Good catch. Time-out applied. SQL^{Query me!} 03:35, 12 April 2019 (UTC)

Hello, SQL. Please check your email; you've got mail!
It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the ((You've got mail)) or ((ygm)) template.

- FlightTime (open channel) 22:10, 19 April 2019 (UTC)

Administrators must secure their accounts The Arbitration Committee may require a new RfA if your account is compromised. Use strong, unique passwords for your Wikipedia account and associated email Change your password now if your Wikipedia account password or email password is reused on another website, exposed, or weak Enable two-factor authentication now for improved security

View additional information

This message was sent to all administrators following a recent motion. Thank you for your attention. For the Arbitration Committee, Cameron11598 02:55, 4 May 2019 (UTC)

ArbCom would like to apologise and correct our previous mass message in light of the response from the community.

Since November 2018, six administrator accounts have been compromised and temporarily desysopped. In an effort to help improve account security, our intention was to remind administrators of existing policies on account security — that they are required to "have strong passwords and follow appropriate personal security practices." We have updated our procedures to ensure that we enforce these policies more strictly in the future. The policies themselves have not changed. In particular, two-factor authentication remains an optional means of adding extra security to your account. The choice not to enable 2FA will not be considered when deciding to restore sysop privileges to administrator accounts that were compromised.

We are sorry for the wording of our previous message, which did not accurately convey this, and deeply regret the tone in which it was delivered.

For the Arbitration Committee, -Cameron11598 21:04, 4 May 2019 (UTC)

Hi For the IP?

It is considered as a proxy. So is it a proxy? In this case, why the IP is owned by french governmental agence? --Panam2014 (talk) 22:46, 8 May 2019 (UTC)

Panam2014, Only one source considers it a proxy - IP Quality Score, whom I've always felt are a little overzealous, and can have a lot of false positives. Obviously, I'm not going to scan that IP as it is a gov't IP, but I don't see anything that makes it stick out as an open proxy. SQL^{Query me!} 23:06, 8 May 2019 (UTC)

But it is possible that the claiming that the IP is gov't IP is false? Because it is accused for doing "Hacking SQL Injection". So I don't think that a real gov't IP would do illegal activities. Sometimes, when only one source claim that an IP is a proxy, it is possible that it is truth? --Panam2014 (talk) 23:12, 8 May 2019 (UTC)

Panam2014, I really can't say. I have no access to that site, and I don't know how or if the reports are vetted. Things like this can be caused by compromised or infected machines. Additionally, it isn't unheard of for governments to have teams to do things like that - but I would think it would be highly unlikely from an obviously government-owned IP address. If those are legitimate reports, my guess would be a compromised machine, or machines on the network behind that IP. This can cause behavior that strongly resembles an open proxy as well. Compromised or infected machines are bought and sold, and even rented/traded by hackers all the time. SQL^{Query me!} 23:17, 8 May 2019 (UTC)

Per Wikipedia:Village_pump_(technical)#Major_schema_changes_coming_to_database_replicas / phab:T223406, I've got to at a minimum update SQLBot's task to clear stale AIV reports by June 3. I'm sure I have other tools that are impacted, but I don't really have the bandwidth right now to track all the uses of these very commonly used tables down and refactor them. Looks like line 72 of parse.php is the starting point. SQL^{Query me!} 05:55, 21 May 2019 (UTC)

In the event that I can't get to this, I can probably disable the active admin logic fairly easily until I can work on it. Link for myself for sometime later: mw:Manual:Actor_table. SQL^{Query me!} 06:01, 21 May 2019 (UTC)

If it helps someone else with the migration, for SQLBot, the offending query:

SELECT count( distinct rc_user ) as active
FROM recentchanges
INNER JOIN user_groups ON ug_user = rc_user
WHERE rc_timestamp > now() - interval 1 hour
        AND ug_group = "sysop";

Needed to be changed to:

SELECT count( distinct rc_actor ) as active
FROM recentchanges
join actor on rc_actor = actor_id
INNER JOIN user_groups ON ug_user = actor_user
WHERE rc_timestamp > now() - interval 1 hour
        AND ug_group = "sysop";

I'm going back to bed. SQL^{Query me!} 06:11, 21 May 2019 (UTC)

This also appears to affect botwatch (I've just shut it down, I'm not sure many used it in any case - so likely permanent), and isprangefinder (I'll either shut it down tomorrow, or update it in the unlikely event that I have time). I'm sure it affects aivanalysis - but to be fair that has needed some TLC for a while, so I've shut it down. I think AFC-Ores will be OK. IPCheck shouldn't be affected. SQL^{Query me!} 06:32, 21 May 2019 (UTC)

Ah, isprangefinder uses the API instead of direct queries against ipblocks. Not depreciating that tool. SQL^{Query me!} 07:17, 21 May 2019 (UTC)

Could you handle a RD#2 on rev 898035474? TIA, --Xover (talk) 06:41, 21 May 2019 (UTC)

Xover,  Done, thanks! SQL^{Query me!} 06:43, 21 May 2019 (UTC)

• 103.228.153.232 (talk) 03:45, 31 May 2019 (UTC)
• 103.43.75.153 (talk) 03:48, 31 May 2019 (UTC)

•  Done SQL^{Query me!} 04:00, 31 May 2019 (UTC)

Hi, I have seen recently your edit here: special:diff/899212467. Please note that ((unsigned)) creates a link to the user's page based on the supplied user name. However, anonymous IP users do not have their user pages. In such case a link to the user's contributions should be created instead. For this purpose please use the ((unsigned IP)) template. --CiaPan (talk) 19:21, 31 May 2019 (UTC)

CiaPan, OK, thanks for the tip... SQL^{Query me!} 19:25, 31 May 2019 (UTC)

Is there scope for SQLBot to remove stale reports from WP:UAA as it does those at AIV? In particular the bot reported usernames, which tends to get very long at times, creating a backlogs for account names that typically not a serious / blatant issue and thus requiring me and other admins to clear them manually. NJA | talk 12:47, 24 May 2019 (UTC)

NJA, That's a good idea. It would require discussion, and consensus to implement - as well as a new BRFA. The development bit should be the easy part of the equation. SQL^{Query me!} 04:46, 25 May 2019 (UTC)

Hi SQL. I know you've done this before, so I was wondering if you had a handy way of blocking AWS, like most of it? (and yes, finding the addresses is the easy bit). -- zzuuzz ^(talk) 12:50, 31 May 2019 (UTC)

Zzuuzz, I have something that I can use to make an easy-to-block list of ranges that aren't blocked. It's been a while since TonyBallioni and I went thru AWS / Google Cloud / Microsoft Azure's ranges. I bet a lot of them are falling off now. I'll get working on it. SQL^{Query me!} 18:31, 31 May 2019 (UTC)

Yeah, that was December/Januaryish 2017/2018. It’s been longer than a year, so they probably need to be reblocked. I’d go with at least two years if the range hasn’t changed since our last round. TonyBallioni (talk) 18:34, 31 May 2019 (UTC)

Thanks. I've seen some Azure ranges being abused recently, but the Amazon ones are definitely a thing. I think I noticed that at least some were soft-blocked before. That's probably sensible and OK for my purposes. -- zzuuzz ^(talk) 18:45, 31 May 2019 (UTC)

Zzuuzz, I think we started off soft-blocking them because of a software issue, and never went back to hard-block them. My plan this go round is probably a 24-36 month hardblock, randomized so everything doesn't expire the same day. SQL^{Query me!} 18:54, 31 May 2019 (UTC)

Ah OK, well as far as I know that would also suit (I'm always a bit wary of parts of these networks that get used by applications being used by schools etc, but if you're happy I'm happy). -- zzuuzz ^(talk) 19:01, 31 May 2019 (UTC)

@Zzuuzz and TonyBallioni: - If either of you are interested in helping, it'll post here when it's done running. I imagine it's going to be a large amount of blocks. I'm probably going to have it auto-update daily once the backlog is cleared out. SQL^{Query me!} 19:24, 31 May 2019 (UTC)

(←) I've got google cloud done. AWS and Azure are gonna take a lot more time. SQL^{Query me!} 19:42, 31 May 2019 (UTC)

AWS is done now too. Azure is the big one however, needing at least 2000 rangeblocks to be applied. I've set up SQLBot to update the page every other hour until the backlog is cleared out, after that I'll probably turn it down to either daily, or weekly. SQL^{Query me!} 17:12, 1 June 2019 (UTC)

/32 range blocks

A /32 IPv4 range block covers just 1 IP… (e.g. 192.168.0.1/32 covers 192.168.0.1 to 192.168.0.1, which simplifies down to 192.168.0.1) -GeniusWorkbench4622 18:35, 2 June 2019 (UTC)

GeniusWorkbench4622 - Looks like a bug that needs fixed with the list generator. Amazon / Google / Microsoft list /32 netblocks in ipv4 on their list of addresses. Hadn't considered that (tho the block should still be as effective). I'll patch it, but there's no reason to go back and change the old /32 (and /128 ipv6 if there are any) blocks to single ip blocks SQL^{Query me!} 18:40, 2 June 2019 (UTC)

Patched. SQL^{Query me!} 18:57, 2 June 2019 (UTC)

Hello I recently made edits to the page Over the edge. I added content that I now see was removed. I’d like to know why as this was not false or unnecessary information. Thanks in advance Dickard Wellington Dickerd (talk) 16:04, 3 June 2019 (UTC)

Your IP address was blocked awhile ago by another administrator due to excessive vandalism. When logged in, you should be able to edit. Cheers! Reaper Eternal (talk) 20:03, 3 June 2019 (UTC)

Hi SQL. We have added you to the list of clerks and subscribed you to the mailing list (info: WP:AC/C#clerks-l). Welcome, and I look forward to working with you! To adjust your subscription options for the mailing list, see the link at mail:clerks-l. The mailing list works in the usual way, and the address to which new mailing list threads can be sent is clerks-llists.wikimedia.org. Useful reading for new clerks is the procedures page, WP:AC/C/P, but you will learn all the basic components of clerking on-the-job.

New clerks begin as a trainee, are listed as such at WP:AC/C#Personnel, and will remain so until they have learned all the aspects of the job. When you've finished training, which usually takes a couple of/a few months, then we'll propose to the Committee that you be made a full clerk. As a clerk, you'll need to check your e-mail regularly, as the mailing list is where the clerks co-ordinate (on-wiki co-ordination page also exists but is not used nearly as much). If you've any questions at any point of your traineeship, simply post to the mailing list.

Lastly, it might be useful if you enter your timezone into WP:AC/C#Personnel (in the same format as the other members have), so that we can estimate when we will have clerks available each day; this is, of course, at your discretion. Again, welcome! Regards, --Cameron₁₁₅₉₈ ^(Talk) 20:33, 3 June 2019 (UTC)

Please comment on https://github.com/ms609/citation-bot/pull/1624 I should note that I do not have access to the tokens myself. AManWithNoPlan (talk) 03:21, 6 June 2019 (UTC)

MusikAnimal, You know my struggles with OAuth... Would you be able to lend a set of eyes here, please? I feel like I would be more of a hindrance than a help. SQL^{Query me!} 03:27, 6 June 2019 (UTC)

Hi SQL. I'm DannyS712 (talk), and I wanted to send you a warning about a change I am making to a script, User:DannyS712/DiscussionCloser, that you currently import. If you are an administrator, feel free to ignore this message. For non-administrators, you should be advised that I am removing the script's automatic addition of ((nac)) to your closes. If you have relied on this to mark such closes for you, please remember to add ((nac)) yourself. If you have any questions, feel free to ask me. Thanks, --DannyS712 (talk)

Delivered by MediaWiki message delivery (talk) at 01:37, 13 June 2019 (UTC) on behalf of DannyS712 (talk)

Hi. Right now the AIV analysis page isn't showing me any reports made by any user after about 27 November 2018. That's confused at least one user, so I added a disclaimer to Template:RfA toolbox. I'm not sure if someone's reported this already, but I couldn't find anything in your talk archives. Thought you'd want to know, in any case. Suffusion of Yellow (talk) 23:18, 24 April 2019 (UTC)

Suffusion of Yellow, I apologize - I'm out of town at the moment. I should be back next week, and I will try to look at the issue then. It might be best to remove it from the RFA toolbox for the time being. I'm going to have a lot of work to catch up on when I get back, and it could be a little bit before I can dedicate much time to it. SQL^{Query me!} 03:35, 25 April 2019 (UTC)

The arbitration clerks are pleased to welcome SQL (talk · contribs) to the clerk team as a trainee!

The arbitration clerk team is often in need of new members, and any editor who would like to join the clerk team is welcome to apply by email to clerks-llists.wikimedia.org.

For the Arbitration Committee, --Cameron₁₁₅₉₈ ^(Talk) 20:35, 3 June 2019 (UTC)

Discuss this at: Wikipedia talk:Arbitration Committee/Noticeboard#SQL appointed trainee clerk

I hope you enjoy clerking, SQL. It's interesting to see how arbitration works from a clerk's point of view and the biggest challenge can be keeping folks calm & orderly when cases can get overheated. Oh, and you use a lot of templates! Enjoy! Liz ^{Read! Talk!} 00:41, 4 June 2019 (UTC)

Liz, Thank you! It's interesting already. I'm working on a couple tools to help make things easier as well. SQL^{Query me!} 20:23, 20 June 2019 (UTC)

Is there a reason OAuth is required so frequently? Is there a possibility of changing this behaviour to a more realistic duration? --qedk (t 桜 c) 19:01, 4 June 2019 (UTC)

QEDK, I can take a look at it tomorrow, but I can't make any hard promises right now. I can't speak for you, but I go around 2 weeks before being asked to oauth again - so it's possible that it's something clientside if you're seeing it more frequently (it does rely on cookies). It's the same backend that WP:UTRS uses, but UTRS forces me to oauth multiple times a day. It doesn't ask for a password - so at least it is relatively painless. SQL^{Query me!} 01:00, 5 June 2019 (UTC)

I hate having to have passwords everywhere so yeah, the OAuth feature is great, but the OAuth cookie always expires within a day. So mostly, it only lasts for half a day for me. Like, last night when I sent you this I was still in (second ACC spree in about 4/5 hours) but now I had to reauthorize again (12 hours later). It's kind of an issue but it's OAuth and clicking buttons is definitely easier but I would think developers would not want this behaviour so I thought I'd let you know. Appreciate it either way. --qedk (t 桜 c) 06:18, 5 June 2019 (UTC)

Hi. Do you think you can take a look at phab:T224809? Thanks, --DannyS712 (talk) 04:17, 20 June 2019 (UTC)

DannyS712,  Done SQL^{Query me!} 20:20, 20 June 2019 (UTC)

For ~2-3 days (conference). So I won't be able to trim my section or make any changes/clarifications/etc. before late Sunday/Monday. Cheers, --_{Piotr Konieczny aka Prokonsul Piotrus| reply here} 14:00, 20 June 2019 (UTC)

You might want to close the Workshop. I'd say "before it gets out of hand" but we're way past that.Volunteer Marek (talk) 16:40, 1 July 2019 (UTC)

Volunteer Marek, Thank you for the reminder. I have closed it. SQL^{Query me!} 03:35, 2 July 2019 (UTC)

In regards to diff, how do I complain about personal attacks VM made during the workshop, after the evidence phase was closed on 23 June?

1. "your manipulative nature",[10]
2. "his chicanery" + "This is about Icewhiz trying to spam a particular source - an "essay" by a photographer full of anti-Polish cliches and stereotypes - into as many articles as he could" (second bit arguably more a BLP violation towards the cited scholar),[11]
3. Calling me a Trump/alt-right supporter without evidence (my record is quite opposite to this)[12]
4. WP:ASPERSIONS towards IP editors (calling them socks of neo-Nazi user(s) without evidence and alleging my support for said editors),[13]
5. "your obvious disgusting behavior",[14]
6. "how we could rescue the puppies you and Icewhiz (potentially) drown?" + " the best way to help the old ladies you and Icewhiz (potentially) mug?".[15]

Clerks and arbs were mostly absent (yes - I know - bigger events afoot) and this will drown out in the sea of bytes. So what's the correct forum to raise this?Icewhiz (talk) 05:39, 2 July 2019 (UTC)

And how do I complain about Icewhiz's repeated false accusations and gross misrepresentations of other editors' statements? What's the correct forum to raise this? One administrator suggested going to AN/I with it, regardless of how the case turned out, but I thought maybe it'd be better to give ArbCom a chance to look these over first.Volunteer Marek (talk) 22:17, 2 July 2019 (UTC)

@Volunteer Marek and Icewhiz: You both need to stop this behavior or I'm going to start issuing sanctions under the authority granted to clerks under the Gun Control Arbitration Case, Arbitration Policy, and Clerk Procedures. --Cameron₁₁₅₉₈ ^(Talk) 00:47, 4 July 2019 (UTC)

If you have issues with conduct that you've seen or been the subject to you are more than welcome to email the Clerks mailing list or the Committee's mailing list. Either group will look at both sides conduct so I'd suggest being sure that is the route you want to go down. --Cameron₁₁₅₉₈ ^(Talk) 00:49, 4 July 2019 (UTC)

Hi SQL, I think you meant to put 6 July 2019 (instead of 24 May 2019) for the Canadian politics case in Template:ArbComOpenTasks/ClosedCases. Hope this helps! — Newslinger talk 23:30, 6 July 2019 (UTC)

Newslinger, Thanks, Fixed! SQL^{Query me!} 01:18, 7 July 2019 (UTC)

Newslinger, Well, 3 fixes later it's fixed... It's been a long day... SQL^{Query me!} 01:26, 7 July 2019 (UTC)

No worries, I'm sure the workload at ArbCom is very high right now. Thanks for the timely response! — Newslinger talk 01:28, 7 July 2019 (UTC)

@SQL: Why is my IP blocked? hueman1 (talk) 11:05, 9 July 2019 (UTC)

HueMan1, You are not blocked (you posted here!) SQL^{Query me!} 11:09, 9 July 2019 (UTC)

@SQL: Sorry for that. It was a mistake sir/ma'am. My VPN (which I never used) just opened up without me noticing it. —hueman1 (talk) 11:27, 9 July 2019 (UTC)

HI

Can you explain to me why I got blocked with the reason being "((Colocationwebhost)) " like I don't understand what did I do to be blocked cause I didn't break any wiki rule.

Thank U

WIKIZILE (talk) 11:57, 13 July 2019 (UTC)

WIKIZILE, Without the IP that is blocked, I am afraid there isn't much I can do to help. You, personally aren't blocked - and you haven't broken any rules.

The most common reason for running into this block is editing via a VPN, or other anonymizing service / app. Per our local and global policies, editing via open proxies or other anonymizing services is not allowed.

If you have a demonstrable need to edit via open or anonymizing proxies, there are instructions here that you should follow to apply for IP Block Exemption, which would allow you to bypass this sort of block. SQL^{Query me!} 15:33, 13 July 2019 (UTC)

Seeing the hidden comment on the block message now - Microsoft Azure is absolutely a webhost. Simply turn your VPN off in order to edit, or follow the directions at WP:IPECPROXY if you need to pursue IPBE. SQL^{Query me!} 15:36, 13 July 2019 (UTC)

Hi, I noticed that you made this edit. Would you or another clerk please log the declined case at Wikipedia:Arbitration/Index/Declined requests? Thank you. Please ((ping)) me when you reply so that I remember to look here. --Pine (✉) 04:35, 14 July 2019 (UTC)

I was just coming here to say the same thing that Pine has just said. I was also surprised to not see the Signpost case logged at Wikipedia:Arbitration/Index/Declined requests. IntoThinAir (talk) 04:39, 14 July 2019 (UTC)

@Pine and IntoThinAir:, Got it, thanks. SQL^{Query me!} 05:16, 14 July 2019 (UTC)

Shouldn't take too long, but bad timing RL-wise. Migrate User:SQL/Non-blocked compute hosts to Meta, globally. If there are any ISPS that aren't listed there, that would be useful, let me know here. SQL^{Query me!} 23:08, 16 July 2019 (UTC)

 Done as far as global goes. I'll move it to meta in a couple weeks perhaps. SQL^{Query me!} 03:37, 20 July 2019 (UTC)

Copied from NinjaRobotPirate's talk page: "Hey! Someone reported 103.212.20.243 as an open proxy over at the WikiProject. As a user not verified, I decided to check this IP to see if I understand it all properly. So what I did is I found out it is not a web server, so I tried finding out the port numbers via Nmap. I got 2 port numbers: 443 and 8080. I logged out of Wikipedia and tried to connect to both, but I wasn't able to load up Wikipedia when I set the IP and port as my proxy. Therefore, it is not an open proxy, right? (Because I am not verified, I haven't made any comments at the WikiProject.)" Could you check if my check is correct? Also, could I become a verified user at Wikipedia:WikiProject on open proxies/verified users. I understand that checks should only be done when there is probable cause to belief that an IP may be an open proxy and that ranges of IP addresses serving as open proxy should be range blocked (I am not an admin but I can leave the blocking up to an admin). --MrClog (talk) 13:17, 20 July 2019 (UTC)

Hello! Thanks for your help (regarding a deleted page content); could you please send it again, due to a still unfixed bug in Wikimedia config? I have changed my email to avoid that bug. Thanks, and sorry for the repeated sending! (Now it's obvious why I didn't get some email sent from enwp…) --grin ✎ 18:23, 6 August 2019 (UTC)

Grin, Tried again, let me know if that doesn't work! SQL^{Query me!} 01:51, 7 August 2019 (UTC)

Got it, thank you very much! --grin ✎ 11:55, 9 August 2019 (UTC)

Hey, as per IRC, please can you look into verifying and possibly adding AS134451 to the non-blocked compute hosts checking bot? Cheers, stwalkerster (talk) 00:45, 27 July 2019 (UTC)

Stwalkerster, Are there certain strings that you think I should look for in the whois? I haven't looked individually at the hosts yet (see: [16]), still unpacking. SQL^{Query me!} 02:52, 27 July 2019 (UTC)

ptwiki's non-blocked compute hosts

Hey man! As we talked on IRC, when you can, please generate a list of ptwiki's non-blocked compute hosts, as I plan on blocking them. Thanks! —Thanks for the fish! ^{talk•contribs} 20:50, 26 July 2019 (UTC)

Tks4Fish, Thanks for leaving me a message, this is on my radar, I'll try to get it banged out this weekend. SQL^{Query me!} 02:11, 27 July 2019 (UTC)

Tks4Fish,  Done, I think, please see User:SQL/Non-blocked compute hosts/pt SQL^{Query me!} 04:00, 27 July 2019 (UTC)

ProcseeBot mirroring

Hi me, I hear we could use a list of blocks currently active on enwiki by procseebot, that are not globally blocked. Mirror params, create lists based on remaining block length: <30d, 30m, 9m, 12+m using makelinks() recycled from compute.php. SQL^{Query me!} 03:30, 27 July 2019 (UTC)

Jon Kolbert, you might want to look at this: User:SQL/ProcseeMirror. There are close to 75,000 blocks that would need to be made. SQL^{Query me!} 23:50, 27 July 2019 (UTC)

Thanks for the arbspam.

– bradv🍁 17:50, 17 August 2019 (UTC)

Hey there,

Can ArbCom impose an I-ban between two commentators (not participants) in a case?

Thanks. François Robere (talk) 13:25, 25 August 2019 (UTC)

François Robere, I can only really speak as a clerk, so: Probably not. The clerks remit is arbitration pages, and we can't issue blanket ibans - as that would include pages outside of arbitration. If there is a problem on a case page that needs to be addressed, I would recommend emailing us at clerks-llists.wikimedia.org . SQL^{Query me!} 16:02, 25 August 2019 (UTC)

@François Robere: Thanks for your question. The term "commentators (not participants)" is not well-defined in arbitration: do you refer to editors who have never participated in a case, or editors who have commented in the arbitration page but are not listed as parties? I would imagine that ArbCom would be less likely to intervene with non-parties and with uninvolved non-participants, but in any event, the concept of a "party" to an arbitration case exists solely for internal administrative convenience; any editor may be added or removed as a party to an arbitration case at the direction of the drafting arbitrators. ArbCom is vested by the arbitration policy with "jurisdiction within the English Wikipedia", where it is the "final binding decision-maker". The answer to the question of whether ArbCom has the power to take any action to resolve a conduct dispute on the English Wikipedia is "absolutely", so the answer to the question of whether ArbCom would act hinges on a number of hypotheticals: in what ways did the two commentators violate policy or disrupt Wikipedia? Why is it necessary for ArbCom to intervene? Why couldn't it be handled by administrators acting alone or through established community processes? Historically, actions outside of cases have been rare but not unheard of. Best, Kevin (aka L235 · t · c) 17:21, 25 August 2019 (UTC)

Thank you both. François Robere (talk) 18:47, 25 August 2019 (UTC)

Remedy 2d. It says there are 3 support votes (there are now 4 but that's immaterial) and no opposes or abstains. It says it needs 2 support votes, which at 3 is correct, but it says it cannot pass. Why?--Bbb23 (talk) 17:25, 7 September 2019 (UTC)

See: [17], and [18]. This appears to use CloudFlare Warp, and gives me endpoints of: 8.6.144.228 / 2a09:bac0:14::806:90e4. I should be able to deal with this via non-blocked compute hosts.  Doing... SQL^{Query me!} 01:52, 12 September 2019 (UTC)

The common ASN is 13335, there are additional ASN's. Looks like this config should work:

:$hosts['cloudflare'] = array( 
:	'name' => "Cloudflare", //Set the name to be displayed in headers
:	'asns' => array( '395747', '394536', '209242', '203898', '202623', '14789', '139242', '133877', '13335', '132892' ), //List of ASNs
:	'searchterms' => array( 'cloudflare', 'cloudflarewarp' ), //List of items to search for in the whois
:	'blockname' => 'Cloudflare / Firefox VPN' ); //Name to display in the block message
:

SQL^{Query me!} 01:57, 12 September 2019 (UTC)

Running now...Results will be at User:SQL/Non-blocked compute hosts#Cloudflare. SQL^{Query me!} 02:05, 12 September 2019 (UTC)

Something is running really slow with running WHOIS requests, and block-status requests. Both of which should be cached? Possibly FS being slow. It's late, I'll have to revisit this tomorrow. SQL^{Query me!} 04:05, 12 September 2019 (UTC)

Hi, my valid report to AIV was removed as stale by your bot. This doesn't look appropriate to me. Perhaps we should increase the elapsed time before deciding that a report is stale? — Martin (MSGJ · talk) 06:58, 17 September 2019 (UTC)

MSGJ, It looks like there were active admins around that time, and I see lots of reports being removed as actioned / blocked in the hours leading up to removal. The reason for removal is keeping unactioned reports from lingering forever. In many cases reports are just left unactioned because some editors tend to get very angry when reports are declined. SQL^{Query me!} 16:04, 17 September 2019 (UTC)

MSGJ, Actually, looking at the logs - that's turned out to be a bug. It removed your report at 3.15 hours instead of 4.3, due to having a space between the IPVandal template, and its parameter. It's incredibly uncommon for templates to be used in that fashion at AIV, I can only find a couple times it's happened in the last year. Fixed, report detection regex adjusted to /\*(?:| )\{\{(?:ip|)vandal(?: |)\|(.*?)\}\}/i. SQL^{Query me!} 16:14, 17 September 2019 (UTC)

I still think that report was actionable and your bot removed it too quickly, even if it was 4.3 hours. Can I suggest 8 hours as a minimum? There is no harm leaving them around for a bit longer. I think a disregarded/removed report is likely to generate much more frustration than a declined report - editors should be given feedback. (I'm just discovering how editing Wikipedia without the admin tools can be a pain ...) — Martin (MSGJ · talk) 06:20, 18 September 2019 (UTC)

Hey there,

Just letting you know we'll be pitching a story for the Signpost soon.[19] Icewhiz has been working on it for a while[20] and will be credited as author, but if a T-ban is in effect I'll be signing the actual post myself as editor or co-author, so as not to have him break it. François Robere (talk) 14:10, 17 September 2019 (UTC)

François Robere, I don't really work AE in an administrative capacity much, so I might not be the best person to notify. If there are clarifications needed after a completed case, WP:ARCA would probably be the best place to get them. SQL^{Query me!} 16:15, 17 September 2019 (UTC)

		The Communication Barnstar
		For your efforts to extend and improve the communication levels of Wikipedia, at a time when tensions were already at a high level, Ched would like to award you the Communication Barnstar.

In relation to your efforts at User talk:Bradv I wanted to commend you for having the humility and maturity to say things like my bad. I'm new and I apologize. My view is that people willing to do that are the ones that command the most respect. While I can find much to complain about, and point to as something that could be improved, I preferred instead to find a silver lining and make note of it. The barnstar isn't completely unique, but it is a rather rare one from my personal collection. And maybe barnstars have become a cliché over the years, but I did want to find a way to say I really appreciated your efforts. Thanks. — Ched (talk) 09:46, 21 September 2019 (UTC)

Ched, Thank you! SQL^{Query me!} 15:31, 21 September 2019 (UTC)

I wanted to let you know that my IP is unblocked but that it also gets blocked sporadically. I tried to use the site you gave me to submit my IP address privately but, because my IP has been sporadically unblocked, it will not let me send an appeal. Basically, I'm clear for now but if there is any other way I can get you my IP address privately as to not get blocked again, that would be appreciated. Snapplepapp (talk) 15:36, 3 October 2019 (UTC)

Snapplepapp, You can always email me via Special:EmailUser/SQL, or directly at sqlatenwikigmail.com. I can't promise that I will be able to lift your block, but I would be happy to take a look at it from a neutral point of view. SQL^{Query me!} 05:33, 4 October 2019 (UTC)

I've been asked to ask ArbCom about ECP. Currently, it is inconsistently applied and people use it with relative frequency when it doesn't apply per WP:ECP and they fail to log it accordingly. Requests to Admins go unanswered, ignored, or just deleted. How and where do I ask this in relation to WP:ARBPIA4? Buffs (talk) 05:20, 8 October 2019 (UTC)

Buffs, If you're wanting to make it part of the case, see this portion of the guide to arbitration. SQL^{Query me!} 06:16, 8 October 2019 (UTC)

tis appreciated; thank you! Buffs (talk) 15:15, 8 October 2019 (UTC)

A year ago ...

"Added welcome template to user talk page"
... you were recipient no. 2041 of Precious, a prize of QAI!

--Gerda Arendt (talk) 06:39, 9 October 2019 (UTC)