User talk:AmandaNP

Wikipedia:Babel

enThis user is a native speaker of the English language.

fr-3Cet utilisateur peut contribuer avec un niveau avancé de français.

es-1Este usuario puede contribuir con un nivel básico de español.

Search user languages

Contact information
Email: Email me (Email rules) IRC: @wikipedia/DeltaQuad, under nicks similar to DeltaQuad or Izhidez. (See IRC channel at the top for my home)

Archives

2009: Dec 2010: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sept, Oct, Nov, Dec 2011: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sept, Oct, Nov, Dec 2012: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sept, Oct, Nov, Dec 2013: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sept, Oct, Nov, Dec 2014: Jan, Feb-Jun, Jul, Aug, Sept, Oct, Nov, Dec 2015: Jan, Feb, Mar-Jul, Aug-Nov, Dec 2016: Jan-Feb, Mar-May, Jun-Oct, Nov-Dec 2017: 2017 2018: 2018 2019: 2019 2020: 2020 2021: 2021 2022: 2022 2023: 2023 2024: 2024 Special ISI Archive

Administrators' newsletter – June 2020

News and updates for administrators from the past month (May 2020).

Administrator changes

CaptainEek • Creffett • Cwmhiraeth

Anna Frodesiak • Buckshot06 • Ronhjones • SQL

CheckUser changes

SQL

Guideline and policy news

• A request for comment asks whether the Unblock Ticket Request System (UTRS) should allowed any unblock request or just private appeals.
• The Wikimedia Foundation announced that they will develop a universal code of conduct for all WMF projects. There is an open local discussion regarding the same.

Arbitration

• A motion was passed to enact a 500/30 restriction on articles related to the history of Jews and antisemitism in Poland during World War II (1933–45), including the Holocaust in Poland. Article talk pages where disruption occurs may also be managed with the stated restriction.

---

• Discuss this newsletter
• Subscribe
• Archive

Sent by MediaWiki message delivery (talk) 13:27, 1 June 2020 (UTC)

DeltaQuadBot and the weird message

(Section title sounds like it could be the name of a children's book, doesn't it?)

Anyways... DeltaQuadBot left me a weird message on my talkpage and I have no idea what it's about. Do you have any idea? Here's the diff if you need it: Special:Permalink/960944129 Thanks, Ghinga7 (talk) 19:59, 5 June 2020 (UTC)

Did you use the OAuth login at UTRS? That is what likely generated it. -- Amanda (aka DQ) 21:33, 8 June 2020 (UTC)

Maybe. I do a lot of stuff on here, so I don't know. Ghinga7 (talk) 23:45, 8 June 2020 (UTC)

my block

thank you so much for unblocking me. also when the blocked user was vandalising the saint pauls school article they were adding themselves Clone commando sev (talk) 03:18, 9 June 2020 (UTC)

I'm not sure I understand the second part of your message or if there is anything for me to do. -- Amanda (aka DQ) 17:48, 9 June 2020 (UTC)

i was just saying that i found it funny that they were adding themselves to the article Clone commando sev (talk) 03:24, 10 June 2020 (UTC)

Ahh ok. -- Amanda (aka DQ) 03:42, 10 June 2020 (UTC)

Why im blocked..? Im vinayreddy (talk) 16:55, 31 July 2020 (UTC)

DQB

Just regarding its "UTRS Account not meeting requirements" message, it seems to have a typo, "agian" for "again"? All the best! ——Serial ^# 18:20, 9 June 2020 (UTC)

(talk page watcher) I noticed that too. Ghinga7 (talk) 20:34, 9 June 2020 (UTC)

@Serial Number 54129: Just so you know, the code was removed today that issued it, so it won't come up again. -- Amanda (aka DQ) 06:57, 16 June 2020 (UTC)

ip block?

Hey, DeltaQuad! I had a weirdness just now, kept being told "Sorry! We could not process your edit due to a loss of session data. Please try saving your changes again. If it still does not work, try logging out and logging back in." But when I tried to log out I got an error 'invalid csrf token'. So I tried the hubs' machine to see if it was a problem my machine, and I got an error page saying you'd blocked the IP for being a web host or colocation provider. I filed a ticket and minutes later it seems to be fixed, but I wasn't sure what happened and thought I'd ask! :D —valereee (talk) 19:34, 11 June 2020 (UTC)

• (tps) WP:VPT, bottom thread. Happening to many people. Apparently fixed now. --Floquenbeam (talk) 19:36, 11 June 2020 (UTC)

  Thanks! lol...I was like how can I not log OUT? —valereee (talk) 11:50, 12 June 2020 (UTC)

Did I get fired from Wikipedia?

Did I get fired from Wikipedia? Cyphoidbomb (talk) 00:15, 16 June 2020 (UTC)

Cyphoidbomb, Bot didn't get enough botsnacks and is having a hissy fit, no big deal. —moonythedwarf (Braden N.) 00:21, 16 June 2020 (UTC)

Whew! Cyphoidbomb (talk) 00:24, 16 June 2020 (UTC)

Told you elsewhere, but lest the wikilawyers come for my head: I blocked your bot. Feel free to unblock whenever it’s fixed, etc. TonyBallioni (talk) 00:19, 16 June 2020 (UTC)

Mind taking a look into what is causing this? RandomCanadian (talk / contribs) 00:23, 16 June 2020 (UTC)

Ah, you apparently already noticed this. Nevermind. RandomCanadian (talk / contribs) 00:24, 16 June 2020 (UTC)

• Apologies to all who will and are here. I was trying to fix this and forgot to turn off the notification while testing. -- Amanda (aka DQ) 00:28, 16 June 2020 (UTC)

• And apologies for another round and forgetting the cron job that auto does that script. -- Amanda (aka DQ) 00:33, 16 June 2020 (UTC)

• I took away it's notification rights as it's a patch job anyway. -- Amanda (aka DQ) 00:44, 16 June 2020 (UTC)

UPE meatpuppet case

Hi Amanda,

About this, "Not sure if there is a proxy on that whole range." I'm not sure why you don't see them. I clicked on eight random ones from the first page of anon edits on that range and six of them were proxies:

• 1
• 2
• 3
• 4
• 5
• 6

I stopped there but I'm pretty sure that there are a lot more.

"not the first issue I've seen today on that range" It's late for me so I haven't checked yet but we may want to look again more closely at what you think is collateral damage. I may look tomorrow. I'm not entirely sure that what I have seen so far has been collateral damage. See Wikipedia:Articles for deletion/NIX (company). Check the cu log for that range you softened and see the casename that I checked and then find that case on the cu wiki. You will see that the only other keep vote besides the article writer in that AfD is KressInsel and he was confirmed as a sock of that precise master and blocked on uk.wiki and mentioned in the last addition on the cu wiki.

I just searched for that casename in my gmail and found an email from NickK to the cu mailing list on March 28 but no one answered him. It mentions a subrange of the one in question. If you don't have a copy then I can email it to you. I've pinged him because he may have more to add or may want to investigate more closely. It looks like we have at least one confirmed but unblocked UPE sock and there may be more.
 — Berean Hunter (talk) 01:48, 16 June 2020 (UTC)

@Berean Hunter: As far as I understood IPQS was an indicator, not a determinant, like the rest of the sections that have VPN/proxy and are showing Xs. I could be wrong, so crossping @SQL: and @Stwalkerster: might also know. I also looked at the service, and they do say they are the "most accurate" - I've never really seen an accurate site that doesn't list ports and even then those are sometimes out of date.

I'm not to concerned about the reason behind the block itself, I just feel like it's a residential or mobile range. I'll try and dig a little deeper tomorrow and we can see what the range caught since. -- Amanda (aka DQ) 02:41, 16 June 2020 (UTC)

DeltaQuad, One of the earliest reasons for developing IPCheck was the frequency with which people pointed at IPQS, and the hair-trigger-to-flat-out-wrong results that it could give sometimes.

I haven't looked at these ranges really, but your understanding of indicator vs determinant matches my own. SQL^{Query me!} 04:40, 16 June 2020 (UTC)

SQL, the proxy checker is an aggregate tool that queries multiple sites for existent reports and scans, correct? I'm under the impression that no real scanning occurs from our queries. (I realize that there had been the check box for port scanning which is now removed but I'm not talking about that.) Our queries through your tool does not initiate any kind of serious scan on the part of those services does it? It just queries their databases, right? There doesn't seem to be enough time for anything beyond the most cursory of scans.

With my understanding laid out above, I would not take the absence of a report on certain sites as meaning that the report filed at IPQS is therefore negative. From your view, as well as Amanda's being welcome also, how do we get to that determinant state for the purposes of blocking? What further steps do you take? Is it expected of all admins/checkusers that they should run their own nmap scans at that point? Does your tool become more of a determinant when a consensus of the aggregate results agree? Is there a guide that I don't know about?
 — Berean Hunter (talk) 15:30, 16 June 2020 (UTC)

@Berean Hunter: Correct, as far as I know, it's just a collection of information with databases and no scans are done. True that absence does not mean negative. So the determinant side for me is solely through manually checking google for proxy lists with the IP and seeing their last active date. I never do port scans. Most proxies (at least in the sense I talk about them - aka not webhosts, colocators or zombies) leave within a short period of time and are on single IPs.

If you have an entire range you think is full of proxies, that's more likely an entire compromised network ({{zombie proxy}}) which I normally would defer to asking User:zzuuzz or SQL about because I don't have the knowledge to even certify that. I can say that I can count on my hands how many times ive done that.

The thing you will (or I at least) issue the most blocks for are webhosts ({{webhostblock}} - hardblocks only) and colocators ({{colocationwebhost}} - softblocks only). These are easy to determine. Run a whois and look for the company name or the domain on an email associated with the company. Then look up their website. If they offer servers of any kind, it's normally a webhost. If they offer residential and servers or they use the terms IP Transit or Colocation, or give any indication they provide entire networks to regular businesses, it's a colocator. I only softblock colocators because that means business that are just forcing their users to use that network while at work could get caught in the middle and very frequently do. You will block the range that is attached with the company based on the whois.

There are some solid examples of webhostblocks and colocationwebhost blocks in my block log which would provide a basis for an example. -- Amanda (aka DQ) 00:20, 17 June 2020 (UTC)

Since I was pinged I'll add a brief comment. I hardly ever use nmap, and I just don't trust blacklists beyond a very rough indicator. When it comes to all the different types of anonymiser available, performing an actual proper confirmation scan is rarely a successful strategy. A good proportion of what I get up to asking, what is this network up to? One of the things I look at is whether the edits are appropriate for the location, and looking at the edits here, yes there might have been a socker or two on there in the past, but much of the editing appears geo-appropriate (including the CU logs). If there was significant proxy usage then you'd expect much more variation. The ISP has no website that works (or meaningful company name) from what I can tell, which is never a good sign. It does some hosting - for example dipromisto.gov.ua is in the range at 82.193.97.114. Like any large network there might an open proxy or two floating around, but I can't find anything overly dodgy about it in terms of proxies as a whole network. A CU block is of course another matter. One thing I wouldn't expect from the range is too many new users arriving on to it at once. -- zzuuzz ^(talk) 03:19, 17 June 2020 (UTC)

Thank you both as this is good information. Please start a guide on the cu wiki when you get a chance as this would be good info for future checkusers as well as the present ones. Good strategy and sources could be developed on such a page if many CUs are contributing to it. I do look some companies up for colocation and webhosts. "I never do port scans" and "I hardly ever use nmap"...probably because it takes so long and if you are dealing with a hardened up proxy then you have to try different combinations to discover open ports. I took a random IP and tried a few combinations on it yesterday. It took a long time to complete although the port shows up in the first 20 minutes of the scan.

• nmap -p 1-65535 -T4 -A -v -Pn 82.193.98.4
  • Discovered open port 54362/tcp on 82.193.98.4

82.193.98.0/24 was indicated by the uk checkuser as the most problematic subrange on cu-l on March 28. It would indeed take a long time to scan the various IPs. If you try your hand at spot checking, I recommend using the no ping option -Pn
 — Berean Hunter (talk) 14:28, 17 June 2020 (UTC)

Current blocks on IPs in the /19 range on other projects are exclusively proxy blocks:

• 82.193.125.77 globally blocked by Jon Kolbert (Open Proxy)
• 82.193.111.126 blocked by RonaldB (Open proxy) on nl.wiki
• 82.193.123.230 blocked by Mardetanha (proxy list) on fa.wiki
• 82.193.114.204 on ja.wiki blocked by 竹麦魚 as Open Proxy (this block is really old and an indef)
• 82.193.121.122 is blocked indef on three different Portuguese projects by Sir Louis Point du Lac Bot as "No open proxies" and "Tor nodes"
• 82.193.105.203, 82.193.115.112, and 82.193.122.137 are all indeffed on vi.wiki by Ctmt as open proxies

Huge number of active proxy blocks on ru projects by proxy bot

ru.wikiquote.org 2018-Jul-25 — 2020-Dec-28: 82.193.108.186 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.108.88 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.171 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.241 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.252 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.7 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.87 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.118.46 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.103.161 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.103.245 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.113.162 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.115.193 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.116.134 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.116.173 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.118.78 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.121.175 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.126.177 blocked by QBA-bot (Blocked proxy ) 2018-Jul-26 — 2020-Dec-29: 82.193.103.241 blocked by QBA-bot (Blocked proxy ) 2018-Jul-26 — 2020-Dec-29: 82.193.114.41 blocked by QBA-bot (Blocked proxy ) 2018-Jul-26 — 2020-Dec-29: 82.193.119.197 blocked by QBA-bot (Blocked proxy ) 2018-Jul-27 — 2020-Dec-30: 82.193.112.182 blocked by QBA-bot (Blocked proxy ) 2018-Jul-27 — 2020-Dec-30: 82.193.116.223 blocked by QBA-bot (Blocked proxy ) 2018-Jul-29 — 2021-Jan-01: 82.193.123.181 blocked by QBA-bot (Blocked proxy ) 2018-Sep-12 — 2020-Aug-29: 82.193.104.166 blocked by QBA-bot (Blocked proxy ) 2018-Sep-28 — 2020-Oct-15: 82.193.112.15 blocked by QBA-bot (Blocked proxy ) 2018-Sep-28 — 2020-Oct-15: 82.193.126.105 blocked by QBA-bot (Blocked proxy ) 2018-Oct-20 — 2020-Oct-06: 82.193.123.230 blocked by QBA-bot (Blocked proxy ) 2019-Jan-30 — 2020-Jul-17: 82.193.101.241 blocked by QBA-bot (Blocked proxy ) 2019-Feb-17 — 2020-Aug-05: 82.193.106.49 blocked by QBA-bot (Blocked proxy ) 2019-Apr-15 — 2020-Sep-19: 82.193.100.148 blocked by QBA-bot (Blocked proxy ) 2019-Apr-17 — 2020-Oct-03: 82.193.123.217 blocked by QBA-bot (Blocked proxy ) 2019-Jun-02 — 2020-Jul-03: 82.193.117.144 blocked by QBA-bot (Blocked proxy ) 2020-Feb-28 — 2021-Mar-30: 82.193.125.77 blocked by QBA-bot (Blocked proxy ) 2020-Apr-06 — 2021-Apr-06: 82.193.103.5 blocked by QBA-bot (Blocked proxy ) 2020-May-28 — 2020-Nov-28: 82.193.111.126 blocked by QBA-bot (Blocked proxy ) ru.wikipedia.org 2016-Nov-27 — 2021-Apr-06: 82.193.103.5 blocked by QBA-bot (Blocked proxy ) 2017-Oct-03 — 2020-Oct-06: 82.193.123.230 blocked by QBA-bot (Blocked proxy ) 2018-Mar-26 — 2020-Aug-29: 82.193.104.166 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.108.186 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.108.88 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.171 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.241 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.252 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.7 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.116.87 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-28: 82.193.118.46 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.103.161 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.103.245 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.113.162 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.115.193 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.116.134 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.116.173 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.118.78 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.121.175 blocked by QBA-bot (Blocked proxy ) 2018-Jul-25 — 2020-Dec-29: 82.193.126.177 blocked by QBA-bot (Blocked proxy ) 2018-Jul-26 — 2020-Dec-29: 82.193.103.241 blocked by QBA-bot (Blocked proxy ) 2018-Jul-26 — 2020-Dec-29: 82.193.114.41 blocked by QBA-bot (Blocked proxy ) 2018-Jul-26 — 2020-Dec-29: 82.193.119.197 blocked by QBA-bot (Blocked proxy ) 2018-Jul-27 — 2020-Dec-30: 82.193.112.182 blocked by QBA-bot (Blocked proxy ) 2018-Jul-27 — 2020-Dec-30: 82.193.116.223 blocked by QBA-bot (Blocked proxy ) 2018-Jul-29 — 2021-Jan-01: 82.193.123.181 blocked by QBA-bot (Blocked proxy ) 2018-Sep-28 — 2020-Oct-15: 82.193.112.15 blocked by QBA-bot (Blocked proxy ) 2018-Sep-28 — 2020-Oct-15: 82.193.126.105 blocked by QBA-bot (Blocked proxy ) 2019-Jan-30 — 2020-Jul-17: 82.193.101.241 blocked by QBA-bot (Blocked proxy ) 2019-Feb-17 — 2020-Aug-05: 82.193.106.49 blocked by QBA-bot (Blocked proxy ) 2019-Apr-15 — 2020-Sep-19: 82.193.100.148 blocked by QBA-bot (Blocked proxy ) 2019-Apr-17 — 2020-Oct-03: 82.193.123.217 blocked by QBA-bot (Blocked proxy ) 2019-Jun-02 — 2020-Jul-03: 82.193.117.144 blocked by QBA-bot (Blocked proxy ) 2020-Feb-28 — 2021-Mar-30: 82.193.125.77 blocked by QBA-bot (Blocked proxy ) 2020-May-28 — 2020-Nov-28: 82.193.111.126 blocked by QBA-bot (Blocked proxy )

 — Berean Hunter (talk) 15:30, 17 June 2020 (UTC)

Looking for help re suspected sockpuppet

Hi - I am sorry but I don't know how to do SPI so I am contacting you in the hope that you might assist me, as you placed the ban on the user whom I consider now to be socking. A quick glance at Reshma Shetty edit history shows the user you banned making many edits and then a user, whom I consider to be the sock, continuing to make edits to the same page. Exactly the same pattern emerges on other pages, such as List of Royal Pains characters, Before I fall, Deep Katdare and several others. Silly English Kniggits appears to be editing almost the exact same set of pages as the banned user. I apologise for drawing your attention to this but as the admin who placed the ban, I thought you might be willing to help ensure it's enforced.NEDOCHAN (talk) 11:08, 26 June 2020 (UTC)

I have filled the SPI for you: Wikipedia:Sockpuppet investigations/Fourlaxers. -- Amanda (aka DQ) 18:33, 26 June 2020 (UTC)

Many thanks.NEDOCHAN (talk) 21:37, 26 June 2020 (UTC)

You've got mail!

Hello, AmandaNP. Please check your email; you've got mail! The subject is DeltaQuad Account.
Message added 11:21, 26 June 2020 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.

Jack Frost (talk) 11:21, 26 June 2020 (UTC)

@Jack Frost: While I appreciate the effort, things like this really make a mess of things. I had to block and get the account locked as it's technically controlled by 2 people which should never happen, even if I changed the settings. Also the software is build to prevent the creation again as I'm pretty sure you had to check ignore spoofing checks to create it. It also made a snafu of proper redirects when I had to rename the account. I also had plans in the works for moving my alt there, just hadn't gotten to it yet. So just advice for next time, but it's best to approach the person with this sort of issue so they can solve it. -- Amanda (aka DQ) 18:12, 26 June 2020 (UTC)

Welcome back

I have been editing sporadically recently and just noticed you were back. Great news. Welcome back. Donner60 (talk) 04:54, 27 June 2020 (UTC)

High DeltaQuadBot login rate

Hello!

Your bot is logging into Wikimedia projects near 3K times in a 48H period, which is excessive, and shouldn't be necessary.

See https://phabricator.wikimedia.org/T256533#6261565

Can you do anything about this?

https://www.mediawiki.org/wiki/API:Login#Additional_notes

>If you are sending a request that should be made by a logged-in user, add assert=user parameter to the request you are sending in order to check whether the user is logged in. If the user is not logged-in, an assertuserfailed error code will be returned.

Reedy (talk) 15:23, 27 June 2020 (UTC)

@Reedy: I'm using mwclient, and it appears it deletes the cookies and therefore the login information each time the script finishes, so if I'm reading right, it requires a new login. Is there a better way to be doing this, or am I going to have to rewrite code/choose a new library to properly login? There are several scripts that are all logging in various times per hour, so I can understand where the high number is. It's just a matter of what to do to fix it. -- Amanda (aka DQ) 16:02, 27 June 2020 (UTC)

It might be worth a request upstream to the mwclient developers, to see if they could do anything to persist sessions, or something else. It may be that some bots do need higher login rates... But 3K/48H is just over 60, meaning one a minute. Looking at Special:Contributions/DeltaQuadBot, I don't see the bot doing that many actions per hour; there's 100 edits in 5.5 hours. Obviously looking at Special:Log/DeltaQuadBot, Contributions aren't the whole picture. Reedy (talk) 16:39, 27 June 2020 (UTC)

For the time being, I've reduced at least 1,152 logins (per 2 days) with this change -- Amanda (aka DQ) 23:56, 27 June 2020 (UTC)

Also over the next bit, i'll run down my individual bot tasks and get them to compare previous text with proposed new text and only login and save if it's different. -- Amanda (aka DQ) 00:05, 28 June 2020 (UTC)

And @Reedy: i've upstreamed the request. -- Amanda (aka DQ) 00:10, 28 June 2020 (UTC)

@Reedy: Sorry one more ping...I saw elsewhere that using OAuth could help reduce this. Is that true? If so, that's a pretty simple change I can employ I think. -- Amanda (aka DQ) 00:16, 28 June 2020 (UTC)

Thanks! Potentially, yeah, as you can keep hold of tokens and re-use those. Noting, OAuth 1.0 might not work so well (due to the auth workflow etc), but 2.0 might work for your usec case; but it can be a little buggy! :) Reedy (talk) 00:21, 28 June 2020 (UTC)

DeltaQuadBot and renaming

Hi. Can you please update the redirect target of User talk:DeltaQuadBot? Its fully protected. Also, at Wikipedia:Usernames for administrator attention/Bot (and probably elsewhere) the bot is linking to pages under your old name, which are now redlinks. Can those be updated? Thanks --DannyS712 (talk) 20:45, 27 June 2020 (UTC)

Global watchlist - Update 7

Updates associated with DannyS712's Global watchlist script and the Global watchlist extension:

Future development

I have received a grant from the WMF to develop this script into an extension. As a result, I do not plan on any further developments being made to the user script. Please see the grant page for more information. Those interested in reviewing and providing feedback for the extension should follow the new phabricator board, phabricator:tag/mediawiki-extensions-globalwatchlist.

Translations

Many thanks to those that have contributed translations for the script's messages. Now that I am working on an extension, translation has migrated to translatewiki. Please see:

• translatewiki:Special:Translate/ext-globalwatchlist
• translatewiki:Special:Translate/ext-globalwatchlist-api
• translatewiki:Special:Translate/ext-globalwatchlist-script

To subscribe or unsubscribe from future updates, see the distribution list.

Thanks, --DannyS712 (talk) 04:41, 1 July 2020 (UTC)

---

Global watchlist user script: About • Updates • Code
Global watchlist extension: documentation

Administrators' newsletter – July 2020

News and updates for administrators from the past month (June 2020).

Administrator changes

Malcolmxl5

John • TheCoffee • Tim!

Creffett → GeneralNotability

DeltaQuad → AmandaNP

CheckUser changes

Bbb23

Interface administrator changes

TonyBallioni

Guideline and policy news

• A request for comment is in progress to remove the T2 (template that misrepresents established policy) speedy deletion criterion.

Technical news

• Protection templates on mainspace pages are now automatically added by User:MusikBot II (BRFA).

Arbitration

• Following the banning of an editor by the WMF last year, the Arbitration Committee resolved to hold an RfC regarding on-wiki harassment. The RfC has been posted at Wikipedia:Arbitration Committee/Anti-harassment RfC and is open to comments from the community.
• The Medicine case was closed, with a remedy authorizing standard discretionary sanctions for all discussions about pharmaceutical drug prices and pricing and for edits adding, changing, or removing pharmaceutical drug prices or pricing from articles.

---

• Discuss this newsletter
• Subscribe
• Archive

Sent by MediaWiki message delivery (talk) 10:25, 1 July 2020 (UTC)

SPI request

Hello, I saw that you are an active SPI clerk and that you have processed many of the recent CU requests. I was wondering if you could approve the CU request at Wikipedia:Sockpuppet investigations/Theedardanian. I'm one the editors, which the editor who filed the report is claiming that they are connected. A quick CU would resolve it all, so I have left the same request in several clerks' talkpages.--Maleschreiber (talk) 21:05, 1 July 2020 (UTC)

I am a CheckUser actually, and with respect, this is not the way to go about this. You have only filled yesterday. As seen here, there are several cases open longer than this one. I only stopped today because I was out of energy and had a migraine. Also the longer an SPI gets with all the comments with back and forth discussion between the users, the longer it takes to process, think through and decide. Please be patient, and someone will get around to your case. -- Amanda (aka DQ) 21:09, 1 July 2020 (UTC)

I apologize if it sounded a bit like a "customer request". I'll try to limit my responses to that page to help other clerks process the request without having to read through countless pages worth of content.--Maleschreiber (talk) 21:24, 1 July 2020 (UTC)

Hi, AmandaNP. Thanks for taking a look at this . I was wondering whether you only CU'd the three suspected socks in relation to the suspected sock master (Theedardanian) or if you cross-checked all three suspected socks against each another. The accounts that stand out in particular are Maleschreiber and Crazydude1912, which were registered and started editing minutes apart. Amanuensis Balkanicus (talk) 21:35, 2 July 2020 (UTC)

I checked all 3 suspected against themselves, the master was stale. -- Amanda (aka DQ) 22:06, 2 July 2020 (UTC)

Amanda, thanks a lot about the very quick and straightforward approach! --Maleschreiber (talk) 07:07, 3 July 2020 (UTC)

You've got mail! 2

Hi there,

What is happening with this investigation that I created https://en.wikipedia.org/wiki/Wikipedia:Sockpuppet_investigations/Dikaiosyni .

Kind Regards,

James James Richards (talk) 18:32, 3 July 2020 (UTC)

@Jamesrichards12345: Since you included oversightable information by outing someone or attempting to, I suppressed it in an abundance of caution because of the concern that more personal information may exist. Please do realize that outing can get you blocked from editing really fast and is not tolerated. My suggestion is that you recreate the SPI with only information you can find on Wikipedia, do not reference anything you search up on the web about a person's identity and affiliation. If you find that you absolutely can't make your case based on onwiki information only (which is rare that you can't), then you should contact either CheckUsers or ArbCom privately. If you need a copy of what you wrote, I can email it to you, and you can remove or recreate from that. I'll unprotect the SPI now. -- Amanda (aka DQ) 18:44, 3 July 2020 (UTC)

Thanks a lot it is all good I will recreate it, I had copy and pasted the code earlier so no need to email it to me. I wasn't aware of that policy. --James Richards (talk) 18:48, 3 July 2020 (UTC)

Hi there, sorry to bother you again, I recreated the page https://en.wikipedia.org/wiki/Wikipedia:Sockpuppet_investigations/Dikaiosyni without the info that got it removed last time. But I must have done it wrong since the page is not appearing in the currently listed investigations. Would you be able to sort it out please, thanks a lot of the help :D --James Richards (talk) 18:53, 3 July 2020 (UTC)

Jamesrichards12345 I've suppressed that again - please re-read Amanda's comment about not including anything found on external websites in the public report. As Amanda said, if you find that you absolutely can't make your case based on onwiki information only (which is rare that you can't), then you should contact either CheckUsers or ArbCom privately. Do not re-add links to external websites like that again, or you're highly likely to find yourself blocked. stwalkerster (talk) 19:02, 3 July 2020 (UTC)

Ok I will message it privately then, because a key peice of this evidence are videos by this Diaspora organisation creating a 'Wikipedia Taskforce' --James Richards (talk) 19:07, 3 July 2020 (UTC)

Rollback block

Hi, I was reverting vandaliism on Hetton-le-Hole so it is not edit warring and I had discussed it with the ip last night at 80.225.208.29 (talk · contribs) who is the obvious sockpuppet of 79.65.78.3 (talk · contribs). It is obvious vandalism as it is a recognised town and has a town council and the ip vandals keep changing it to city or village.The ip last posted okay lol on their talkpage so they were obviously not serious. Also I asked for page protection last night and reported the ips at AIV today. Regarding my block history I've had one block for one hour a year ago so removal of rollback is very unfair, regards Atlantic306 (talk) 21:05, 3 July 2020 (UTC)

I think it's a fair and proportionate measure. I'd have blocked you fully for a number of days for edit warring/disruptive editing. I think a partial block and rollback being removed is incredibly generous. Your behaviour, whether right or wrong, was disruptive and is particularly inappropriate coming from an experienced editor who should know better. Nick (talk) 21:32, 3 July 2020 (UTC)

• Well, how is it disruptive to revert vandalism ? Also see the external link on Hetton-le-Hole to the Town Council Atlantic306 (talk) 22:05, 3 July 2020 (UTC)

The edits to the article are not obvious vandalism - therefore their reversion constitutes edit warring. They're also not appropriate edits to be using rollback on, additionally edit warring is reasonable grounds to remove rollback regardless of whether or not rollback was used to edit war. Nick (talk) 22:16, 3 July 2020 (UTC)

• I had discussed this last night with the first ip and given him evidence that it is a town with a town council so discussion was involved Atlantic306 (talk)

• Discussion does not mean consensus and evidence to the contrary does not mean vandalism. Please read up on what isn't vandalism, especially about disruptive editing. People seem to forget that vandalism is adding "your mom" to things, aka something that very clearly doesn't belong. Being wrong isn't vandalism. AIV reporting doesn't excuse your behavoir. The proper thing to do is let it be, allow for a block if it's warranted, and THEN revert a single time. But neither a block is warranted nor is the excessive reversion. Plus you did it on the same article in 2019. I'm not trying to insult you, but you really need to reread policy on vandalism. (Hell most of AIV reporters need to also) -- Amanda (aka DQ) 22:34, 3 July 2020 (UTC)

• • The 2019 reversion on the page was two reverts so it was not really edit warring although perhaps I shouldn't have used rollback then or now but really if something obviously false such as calling London a village does seem like vandalism. I commit to being sparing with rollback if I get it back, regards Atlantic306 (talk) 22:53, 3 July 2020 (UTC)

Mistaken deletion

Hi, if you have a moment the most recent deletion here should be undone (and the more recent version of the file should be deleted). The most recent revision appears to have removed the transparency layer, and changed it to white. That edit was made by a blocked sockpuppet of a user who has made many errors in regards to images. -Pete Forsyth (talk) 03:46, 7 July 2020 (UTC)

Rollback

Hi, thanks for temp approving my rollback.

I wanted to ask mention about the diffs you posted:

• Special:diff/964435523 - Looks like the edits were being corrected by an IP editor. I reverted and then I realised my mistake a minute later and then restored to the LGV (Special:diff/964435651)
• Special:diff/965250873 - No idea what happened here. I'll try and pay closer attention.

What does "missing oversightable content" mean?

Thanks! -OXYLYPSE (talk) 14:56, 9 July 2020 (UTC)

Yes, I definitely get they are small mistakes and fixable, but that is why I said lets trial run so we can reduce the concern that you may be processing things to fast and reduce the chance of mistakes. Vandalism doesn't have to be gone in split seconds, its fine to wait a couple of seconds most times. Missing oversightable content is like phone numbers, blatant outing, things like that which need to be reported. I don't remember the exact diff, and can't discuss it anyway. I'm happy to individually review after the time if you wish. -- Amanda (aka DQ) 01:38, 11 July 2020 (UTC)

Lovely stuff, thank you for being so understanding! -OXYLYPSE (talk) 08:41, 12 July 2020 (UTC)

Rename DeltaQuadBot

You have changed your username from DeltaQuad to AmandaNP. If possible, can you please rename DeltaQuadBot to AmandaNPBot or AmandaBot? GlobBETT ☎️ 🖋 18:04, 9 July 2020 (UTC)

Globbett, as a BAG member I can say that there is zero requirement for a bot name to match (or even indicate ownership by) the bot operator's username if they do not want to. Primefac (talk) 21:55, 10 July 2020 (UTC) For transparency, I was asked to look into this matter by Amanda.

I was also just replying, but I won't be renaming the bot. It's clearly identified on the userpage who the owner is, it would break all my edit summaries and force me to go through all my code and redo them, it's already well known under that name, and a rename of almost 1 million edits would put a stupid strain on the server that developers would not be happy with me about. -- Amanda (aka DQ) 21:57, 10 July 2020 (UTC)

rename of almost 1 million edits would put a stupid strain on the server that developers would not be happy with me about renames of accounts with lots of edits are no longer expensive after the actor migration. * Pppery * _{it has begun...} 03:30, 12 July 2020 (UTC)

@Pppery: Fair enough, I was told this for the first time last night. Either way, I still don't see a reason for the rename. -- Amanda (aka DQ) 06:14, 12 July 2020 (UTC)

Partial block

I have been partially blocked for some time now. I did take some time after that to read the username policy and the UAA instructions, which I misunderstood and applied incorrectly in two of my last reports before the partial block. However, I was reluctant at first to ask if the scope of the block was too broad, as it applies to an entire namespace. I do not know if this is too much to ask for, but is it possible to narrow the scope to at least UAA and AIV only, as those were the noticeboards where my reporting have been indeed problematic? I am worried because the block is also affecting other noticeboards, such as ITNC and SPI, where my contributions were relatively less but not controversial. LSGH (talk) (contributions) 04:08, 10 July 2020 (UTC)

LSGH, weren't you pblocked something like four days ago? That's not really "some time"... it was Monday. Primefac (talk) 01:24, 11 July 2020 (UTC) (talk page stalker)

While I agree with Primefac, I did take a look back over things. I am willing to go down to UAA and AIV only, and reduce it to a month. My reasoning behind that is you have already been asked to review the username policy on Jun 20th, and from then until the time of the block you could have asked questions or read closer. The one month gives you a chance to fully review the relevant policies, and then try again. But for now, it takes you away from the venues that see heavy volume - where the most issues can be caused and the most cleanup would be needed. I also looked back on your talkpage and saw that it wasn't as bad as I initially had read through, and that you were trying to understand the processes at least, even if you potentially were not understanding. So that's why I've reduced the block to what it is. Please note if issues continue after that one month...then we are going to be right back where we started.

Since I can't include my personal opinion in with a block and it's solely related to policy, I will add my comment here instead, noting that it was not part of the review, as I would of left the block for a longer length and maybe more broad. When I approached your talkpage, your explanation was less than the level I expect from a fellow contributor. It felt like you were trying to avoid the issue especially by pointing out that it would have been blocked anyway. Yes, it would have, and that's why I blocked it still. But throwing any accusation around and then when it's dealt with another way say "the ends justify the means" makes Wikipedia a less safe/good place to edit by driving away people (Something mentioned in the DE policy). What made it worse is that was used as a justification to explain a concern about potential racism (which maybe I didn't clearly note) and then say that 'some groups resort to violence' without specifying that it's only parts of those groups. That's why I mentioned the painting a picture issue. I know some other Wikipedia users may say i'm just being oversensitive or that Wikipedia isn't therapy to me, as one of the largest websites in the world we have the chance to address systemic discrimination of all kinds. And that's my concern is that with that report and then saying ends justify the means, we are just brushing it under the rug. Now of course this is my personal opinion and some advice, you can technically throw it in the trash can or tell me to fuck off after reading it and it wouldn't matter, but if you are here to be open to change and be receptive to feedback, this is the chance to take it in. Up to you what you do with it. -- Amanda (aka DQ) 02:10, 11 July 2020 (UTC)

@LSGH: I've been stalking Amanda's talk page and saw this. I think Amanda has given you a great opportunity here to improve. I highly suggest you visit the relevant policies again for vandalism and usernames and anything you're interested in contributing to. If you have questions, please feel free to ask and clarify before making a questionable report. You'll find many contributors here at Wikipedia who will help you learn the ropes and answer questions. -- Dane ^talk 02:23, 11 July 2020 (UTC)

Thanks. I feel that there really is a need for me to slow down, as I have not much of an experience to deal with those matters, unlike the others who also report there regularly and have been around for years now. As they say, it's really better to leave some things to more experienced editors. I may have thought that asking others about the best possible interpretation of policy would disturb them, especially if the questions come from those with less experience, though that seems not to be the case. The least thing we want to do at WP is to drive away people who would be potentially productive, and I don't want to do it out of carelessness and misinterpretation. Thank you anyway for the learning experience. LSGH (talk) (contributions) 03:28, 11 July 2020 (UTC)

Note about Noob42069

The bot you operate, DeltaQuadBot, forgot to add that the username matched 69 on the blacklist. It is commonly associated with oral sex and is commonly used for vandalism-only accounts. GlobBETT ☎️ 🖋 01:11, 12 July 2020 (UTC)

It didn't forget. Due to performance reasons and not putting excessive strain on the servers, the bot will only ever file based on the first thing it matches on the blacklist. I've had issues before where the bot will choke if there are too many usernames/entries to process, and delay the next round from getting launched with a snowball effect to the point it will barely edit or not at all. At one point, it didn't edit for over 3 months because of this type of issue and something got stuck. Any admin patrolling should be fully aware that 42069 is a very commonly used combination and that there are two different concerns. If not...well then someone can rereport it or it can be dealt with at another venue. -- Amanda (aka DQ) 06:29, 12 July 2020 (UTC)

Wikipedia:Sockpuppet investigations/Sash84/Archive

Hi Amanda. I've unblocked the accounts listed in this SPI since ArbCom received an explanation that they are (Redacted). I hope you don't mind me doing this boldly without checking with you first – the explanation just seemed cut-and-dry and I wanted the students to be able to return to editing as soon as possible. Thanks. – Joe (talk) 08:06, 13 July 2020 (UTC)

Mail Notice

Hello, AmandaNP. 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 at any time by removing the {{You've got mail}} or {{ygm}} template.

Celestina007 (talk) 16:36, 16 July 2020 (UTC)

 Replied many hours ago. -- Amanda (aka DQ) 07:11, 17 July 2020 (UTC)

You've got mail!

Hello, AmandaNP. Please check your email; you've got mail! The subject is Revision deletion request.
Message added 07:06, 17 July 2020 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can at any time by removing the {{You've got mail}} or {{ygm}} template.

Thanks for the help! Field Marshal (talk) 07:06, 17 July 2020 (UTC)

@Field Marshal Aryan: I was about to go to bed when I luckily decided to refresh the page to see your mail. Please use WP:RFO in the future so it won't get missed until i'm awake. Thanks. -- Amanda (aka DQ) 07:09, 17 July 2020 (UTC)

AmandaNP, Alright. I just happened to see you on the active admin list. Good night. Field Marshal (talk) 07:24, 17 July 2020 (UTC)

Thanks for letting me know, I've re-requested I be exempt from that list. -- Amanda (aka DQ) 20:36, 17 July 2020 (UTC)

Why have you blocked me?

You seem to have blocked me as a potential sock puppet. I’m really not one. How can I prove it? Florapostewrites (talk) 12:10, 18 July 2020 (UTC)

NB i am fairly new to editing so have made multiple changes to the two articles I’ve created so far. As I get more experienced, I hope I’ll get better at this. I have contributed to numerous other articles and I’m working on 2 other articles about living people at the moment (an internationally acclaimed author and an actor. Florapostewrites (talk) 12:16, 18 July 2020 (UTC)

@Florapostewrites: You are not blocked, and I don't see anything in your public block log. I don't think AmandaNP is currently active so I'm gonna ping @DGG: who does appear recently active to see if they or another admin can help you. Jerod Lycett (talk) 01:26, 19 July 2020 (UTC)

@Jerodlycett: Thanks - I seem to have been unblocked again pretty quickly. Florapostewrites (talk) 09:08, 19 July 2020 (UTC)

Category:Non-free files with orphaned versions more than 7 days old

Hi Amanda/DQ,

I noticed your robot stopped revdeling non-free files. The backlog in this category has grown to more than 2000. The last time the bot revdeled the file was back on 26 June 2020. I posted a message on the ANB about the backlog problem. Can you tell me if there is anything that is up? Aasim 18:09, 20 July 2020 (UTC)

@Awesome Aasim: Fixed several days ago. -- Amanda (aka DQ) 20:50, 23 July 2020 (UTC)

Page Merging

Hello, could you please merge the page history of User:Hurricane Noah/2018 EPAC into 2018 Pacific hurricane season? I already merged all the content over to the main page and blended it within some of the existing content. Also, I am aware I broke a couple of refs and plan to rectify that shortly. Noah^Talk 00:04, 24 July 2020 (UTC)

@Hurricane Noah: This is completely ill-advised per WP:PV. -- Amanda (aka DQ) 03:17, 24 July 2020 (UTC)

About the possible sock

Hello! How are you? Can I know the reason why you declined my checkuser request here? The relation between these two users are really worrying me. After the partial block of GevHev4, he basically disappeared, and stopped responding to the discussion as seen here, and Գարիկ Ավագյան took over the additions, which GevHev4 was usually publishing. --► Sincerely: SolaVirum 18:08, 25 July 2020 (UTC)

I declined it exactly for the reasons stated on the SPI. Editing the same page and having the same opinion, especially with a different account that is 9 years old with about 2,000 edits on a highly political article that would drag in a lot of people does not meet probable cause. You need diffs of evidence that show they have the same opinion on multiple topics. -- Amanda (aka DQ) 20:23, 25 July 2020 (UTC)

Tech News: 2020-31

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Recent changes

• The Starter kit is now available for wiki communities. This page lists technical resources, tools, and recommendations. These are essential to operate a wiki project. This is mostly useful for smaller wikis where the community has limited experience with this. [1]
• The first features of the Desktop Improvements project are available for logged-in users on all wikis. In order to use them, uncheck Use Legacy Vector in your local or global preferences in section Skin preferences. More improvements are planned. Feedback is welcome.
• On multiple wikis, a UTCLiveClock gadget is available. For wikis that import the gadget directly from mediawiki.org, end users can now choose a different timezone to show instead of UTC.

Problems

• The deployment train for MediaWiki has been blocked this week. [2][3]
• Translation Notification Bot was sending the same message multiple times to every translator. This has been fixed. [4]
• Some users were receiving the same notification multiple times. This has been fixed. [5]

Changes later this week

• The new version of MediaWiki will be on test wikis and MediaWiki.org from July 28. It will be on non-Wikipedia wikis and some Wikipedias from July 29. It will be on all wikis from JUly 30 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

13:51, 27 July 2020 (UTC)

RFU Table

Hey!

Is the source for the RFU table on github somewhere? Looks like it's recording only the first bit of IPv6 addresses in the table. SQL^{Query me!} 03:03, 28 July 2020 (UTC)

While we're here... I can't seem to see any requests on UTRS2 anymore. I think my account was auto-demoted when I gave up the bits on enwiki. I tried manually reloading the perms, no dice there - also relogging. Any ideas on other stuff I can try? SQL^{Query me!} 15:38, 4 August 2020 (UTC)

​(talk page stalker) If you view your account (from the navigation bar) does it show the permission table show that you have the sysop bit on enwiki? – Majavah ^{talk · edits} 15:45, 4 August 2020 (UTC)

Majavah, Yep. SQL^{Query me!} 15:46, 4 August 2020 (UTC)

@SQL: Have you tried logging out and back in? If that doesn't help it I'm unfortunately out of ideas and as far as I'm aware Amanda is currently busy with IRL stuff. – Majavah ^{talk · edits} 15:57, 4 August 2020 (UTC)

Majavah, I have, but I appreciate the ideas! SQL^{Query me!} 15:58, 4 August 2020 (UTC)

@SQL: Well, I wrote the authorization system used in UTRS so I'm rather worried if it's malfunctioning and I have no ideas why. Can you also check if you can access individual appeals (list is at CAT:UNBLOCK) and do you have the "user" permission on enwiki (according to the same list)? – Majavah ^{talk · edits} 16:01, 4 August 2020 (UTC)

Majavah, I do have access to the individual appeals. SQL^{Query me!} 16:03, 4 August 2020 (UTC)

Majavah, My permission list does include "user" (See: here) SQL^{Query me!} 16:04, 4 August 2020 (UTC)

@SQL: Well, then the problem is on the main page logic rather than the permission logic. I have a couple of ideas why but I can't really tell without checking a couple of things from the database (which I can't do). – Majavah ^{talk · edits} 16:23, 4 August 2020 (UTC)

SQL should have access to the required fields for the database, and if not, then we can always ask Wikitech admins to grant him access as I won't have DB access for the immediate future at minimum. You can use this diff as my sign-off if needed. -- Amanda - mobile (aka DQ) 23:12, 4 August 2020 (UTC)

AmandaNP, I probably do, now that you mention it. I haven't logged into WMCS since I left. While I'm not entirely sure where to get started with fixing this, but I suppose I could simply drop my row from the DB completely, and start over. SQL^{Query me!} 00:30, 5 August 2020 (UTC)

SPI cases overview?

I've been writing some tools to work with SPI cases. I'm parsing Wikipedia:Sockpuppet investigations/Cases/Overview to get the list of active cases, but I see WP:SPI actually transcludes User:AmandaNP/SPI case list. Why are there two of them?

I also notice that the later is transcluded with {{User:AmandaNP/SPI case list}}|}, which to my unexpert eye looks more like a syntax error than anything else (mismatched curlies). Is this intentional? Is it some obscure piece of wiki-markup I've just never seen before? -- RoySmith (talk) 13:28, 28 July 2020 (UTC)

My version was originally a backup. Amalthea's bot handles it normally, i'm just on backup duty. Looks like it got switched back. Special:Diff/969971986. Regarding the extra text, it's removed. I think it used to be part of a table. -- Amanda (aka DQ) 02:45, 30 July 2020 (UTC)

2604:6000:B445:A100:AD63:E6B6:69:47A9

Can user:2604:6000:B445:A100:AD63:E6B6:69:47A9 please be blocked ASAP. She probably won't stop until blocked. CLCStudent (talk) 02:39, 30 July 2020 (UTC)

Administrators' newsletter – August 2020

News and updates for administrators from the past month (July 2020).

Administrator changes

Red Phoenix

Euryalus • SQL

Jujutacular • Monty845 • Rettetast • Madchester

Oversight changes

GB fan

Keegan • Opabinia regalis • Premeditated Chaos

Guideline and policy news

• There is an open request for comment to decide whether to increase the minimum duration a sanction discussion has to remain open (currently 24 hours).
• Speedy deletion criterion T2 (template that misrepresents established policy) has been repealed following a request for comment.
• Speedy deletion criterion X2 (pages created by the content translation tool) has been repealed following a discussion.
• There is a proposal to restrict proposed deletion to confirmed users.

---

• Discuss this newsletter
• Subscribe
• Archive

Sent by MediaWiki message delivery (talk) 08:20, 1 August 2020 (UTC)

Tech News: 2020-32

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Problems

• All queries to the Wikidata Query Service failed between 17:50 and 17:59 UTC on Thursday 23 July. Some queries failed during a longer period. [6]
• Interlanguage links were ordered incorrectly for the past few weeks. This problem was also mentioned in Tech News two weeks ago. The problem is now fixed. [7]
• There is a problem with the global preferences for the "Use Legacy Vector" option. Developers are working on fixing it. [8]
• A bug in the Wikibase extension had disabled the "move" and "create" types of protection in the main (Gallery) namespace on Wikimedia Commons. New protections could not be added, and existing protections were not enforced, allowing some page moves and page creations that should not have been possible. This has now been fixed. [9]

Changes later this week

• The video player will change to be simpler and more modern. This week, the current beta feature will become the video player for everyone on most non-Wikipedia wikis. The old player will be removed. [10]
• Users' global.js and global.css pages will now also be loaded on the mobile site. You can read documentation for how to avoid applying styles to the mobile skin. [11]
• In the MonoBook skin, the searchGoButton identifier is now searchButton. This may affect CSS and JS gadgets. Migration instructions can be found in T255953. This was previously mentioned in issue 27.
• Bot operators can use Pywikibot to regularly archive discussions. The behavior when the bot uses counter to prevent large archives was changed. [12]
• The new version of MediaWiki will be on test wikis and MediaWiki.org from August 4. It will be on non-Wikipedia wikis and some Wikipedias from August 5. It will be on all wikis from August 6 (calendar).

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

15:43, 3 August 2020 (UTC)