User talk:DoRD

SPI not updating

The list of cases hasn't been updating since sometime yesterday. I forget the various convoluted things that can be tried to fix it short of replacing it temporarily with the old one. Any ideas? I'm pinging others just in case someone else is around to help out: @Vanjagenije: @DeltaQuad: @Amalthea: --Bbb23 (talk) 12:01, 14 October 2016 (UTC)

As far as I can tell, there's not much we can do until Amalthea restarts the bot task, so I've swapped the case lists for now. ​—DoRD (talk)​ 12:07, 14 October 2016 (UTC)

...which reminds me to remind DeltaQuad that her list still has edit links in it. ;) ​—DoRD (talk)​ 12:09, 14 October 2016 (UTC)

Thanks!--Bbb23 (talk) 12:32, 14 October 2016 (UTC)

It's never just restarting a bot ;) In this case SSL connection to the api fails, I'm guessing because of WP:VPT#Certificate revocation issue; I'll try and resolve it tonight ... Amalthea 18:14, 14 October 2016 (UTC)

Certificates updated, page is updated again, thanks for the ping! Amalthea 20:39, 14 October 2016 (UTC)

Thank you very much, Amalthea.--Bbb23 (talk) 20:51, 14 October 2016 (UTC)

The case list is not updating again. I tried to swap the lists until Amalthea can fix it, but it didn't work. I don't know why.--Bbb23 (talk) 22:22, 20 October 2016 (UTC)

Looks like you missed a comment close tag. I changed it, but now it looks like DeltaQuad's list is hitting a transclusion limit or something. <sigh> I'm stepping away from the computer for a while, so feel free to revert me, or wait until one of the lists is working correctly, or whatever... ​—DoRD (talk)​ 22:40, 20 October 2016 (UTC)

Oh, well never mind. Her list hasn't been updated since October 14. ​—DoRD (talk)​ 22:43, 20 October 2016 (UTC)

Ah, this one was my fault: An exception thrown following a recent change where I missed that some pages won't have a last case editor, and that's pages in Category:Requests for checkuser, which now lists User talk:Vineetpl7#checkuser needed. Sorry for that. :| Amalthea 23:25, 20 October 2016 (UTC)

Thanks again, Amalthea. ​—DoRD (talk)​ 01:39, 21 October 2016 (UTC)

My issue was completely different in the fact that I wrote the wrong directory for the script to run on (techie: forgot to remove a word for the dir in crontab) from when I fixed the last issue (transcluding headers), therefore the error was fatal. Now fixed. -- Amanda (aka DQ) 02:08, 21 October 2016 (UTC)

Well, thank you, too. ​—DoRD (talk)​ 02:12, 21 October 2016 (UTC)

Not updating again. Haven't tried swapping.--Bbb23 (talk) 21:34, 4 November 2016 (UTC)

I tried, but the preview showed that Amanda's version is borked as well.--Jezebel's Ponyo^{bons mots} 21:39, 4 November 2016 (UTC)

I was waiting to see and...Amalthea's just updated. ​—DoRD (talk)​ 21:41, 4 November 2016 (UTC)

Huzzah! I think us all wishing for it to be so made it happen. I now wish for the clock to strike 5pm and a nice cold pint to appear before my eyes.--Jezebel's Ponyo^{bons mots} 21:44, 4 November 2016 (UTC)

DoRD, I know this nothing to do with the updating, but thanks for fixing the quick checkuser request.--Bbb23 (talk) 21:57, 4 November 2016 (UTC)

You're welcome. ​—DoRD (talk)​ 22:08, 4 November 2016 (UTC)

Oneshot possibly still at it

I suppose there would be no point in filing a formal SPI, because Oneshot is already indeffed, but check out this IP; it's continuing to harass SPECIFICO (a user with whom I have had many disagreements) after vandalizing Foreign policy of the George W. Bush administration (which I recently made this minor edit to) in a way that indicates the quest to frame me goes on. Either way, the IP is clearly being used solely for vandalism.TheTimesAreAChanging (talk) 00:04, 2 November 2016 (UTC)

Er, I guess not. WhatIsMyIPAddress says the IP is from England. Any similarities are apparently purely coincidental. All the socking has made me paranoid.TheTimesAreAChanging (talk) 00:09, 2 November 2016 (UTC)

Another telltale indicator is the way the IP formatted the links it placed on SPECIFICO's talk page: [url | text]; Oneshot never used the |. Sorry to bother you.TheTimesAreAChanging (talk) 00:14, 2 November 2016 (UTC)

Alright, then. Please report them to AIV if they continue the vandalism. ​—DoRD (talk)​ 01:06, 2 November 2016 (UTC)

Filipz123

I missed one: can you please also revdelete this edit? Burninthruthesky indicated it's a copyvio but didn't say of what, but it pretty closely resembles this article. Thanks. Ivanvector (^Talk/_Edits) 14:07, 4 November 2016 (UTC)

@Ivanvector: Yes, that's the source I was referring to. Thanks. Burninthruthesky (talk) 14:12, 4 November 2016 (UTC)

Judging by a quick Google, the material added to Speleology by one of the other accounts is also largely copied verbatim from the cited source. Burninthruthesky (talk) 14:20, 4 November 2016 (UTC)

 Done. Thanks for pointing it out. ​—DoRD (talk)​ 14:39, 4 November 2016 (UTC)

User:Shilpa Bhawana

You may wish to revoke talk page access as well.--Cahk (talk) 08:10, 8 November 2016 (UTC)

Thanks for reverting that, but I think we can wait to see if it happens again before revoking talk. ​—DoRD (talk)​ 12:21, 8 November 2016 (UTC)

A new user right for New Page Patrollers

Hi DoRD.

A new user group, New Page Reviewer, has been created in a move to greatly improve the standard of new page patrolling. The user right can be granted by any admin at PERM. It is highly recommended that admins look beyond the simple numerical threshold and satisfy themselves that the candidates have the required skills of communication and an advanced knowledge of notability and deletion. Admins are automatically included in this user right.

It is anticipated that this user right will significantly reduce the work load of admins who patrol the performance of the patrollers. However,due to the complexity of the rollout, some rights may have been accorded that may later need to be withdrawn, so some help will still be needed to some extent when discovering wrongly applied deletion tags or inappropriate pages that escape the attention of less experienced reviewers, and above all, hasty and bitey tagging for maintenance. User warnings are available here but very often a friendly custom message works best.

If you have any questions about this user right, don't hesitate to join us at WT:NPR. (Sent to all admins).MediaWiki message delivery (talk) 13:46, 15 November 2016 (UTC)

2605:e000:6201:1300::/64

• 2605:e000:6201:1300::/64 (block range · block log (global) · WHOIS (partial))

Hello DoRD,

The IP 2605:e000:6221:5c00:d0ff:ac80:42a9:1b42 (talk · contribs · WHOIS) is just the latest block evading vandal from the specified IP range above, who is continuing to vandalize numerous airport/aviation related articles.

Some IP's that are already blocked include 2605:E000:6201:1300:C91D:E407:574E:1327 (talk · contribs · WHOIS) and 2605:E000:6201:1300:79E6:3550:A1A9:5C57 (talk · contribs · WHOIS).

You may need to implement a rangeblock on 2605:e000:6221:5c00::/64 (talk · contribs · WHOIS) which appears to be the newest IP range for them. Thanks! 2601:1C0:106:D137:1066:6939:3095:7968 (talk) 06:11, 22 November 2016 (UTC)