User talk:Mz7/September–November 2021

4599:, you once asked if my vote-history tool caught duplicate votes. It did at the time... sorta - all it did was use the vote appearing the furthest down the page, throwing the others away. But that was then, and this is now; I've fixed it to actually show a list of the duplicates. A tiny thing, but it merited a talk page post because it happened to be my final notification! I started at 74 notifications a while ago and went through them all, and now that I'm done with yours, my inbox is empty and I can finally... move on to my overgrown talk page ( 4210: 1966: 1180: 2771:, that other forms of evidence including historical correspondence which I have painfully made efforts to collect, is now rejected by wikipedia due to new dogma.) Anyway, the article has been shredded to 30% of its original length by junior folks, and I will soon disengage from this failing platform. This article was written as a joint effort between the my mother, the wife of Donald B. Gillies, and myself, son of Donald B. Gillies. But the good folks at Knowledge choose to apply dogma to erase history. So be it. Enough. 1113: 4173: 1945: 325: 4221: 4183: 2429: 1977: 1955: 1886: 335: 31: 4162: 1865: 314: 62: 349: 4293: 4255: 1876: 1120: 3621: 796: 4371: 2065: 452: 4777: 2332: 2296: 2241: 1700: 1449: 1399: 593: 5053: 4534: 3853: 3442: 2661: 2225: 1727: 1383: 916: 3653: 4345: 2029: 428: 4434: 2111: 478: 2801:". This isn't a "new dogma"; it has been a fundamental principle of Knowledge since its founding. Basically, we can only publish information that has already been published elsewhere—this is because we are an encyclopedia, not a publisher of original thought. For this reason, if you have new information about your father that no one else has ever published before, I'm afraid Knowledge is not in the best position to be the 4282: 1934: 1249:, thanks for your message. I've put the SPI "on my radar", so to speak. Unfortunately, the case seems a little complicated, involving potentially a whole different sockmaster whose case we may have to merge (SheryOfficial) I don't have as much free time these days as I've had in the past to edit Knowledge, but I will see if I can take a deeper dive into the case as soon as I can. (Fortunately, it seems we may be getting 4244: 4315: 1995: 368: 3740: 3316: 1272: 747: 4236: 1926: 306: 1220:) could really do with some CU attention. This master seems to have created multiple accounts at once in the last few weeks, and may have revived an older one at the same time. They edit profusely and disruptively, and always seem to have some sleeper at the ready to take over. TNT normally deals with this one, but she seems to be on a break. Feel free to point me to another CU. Thanks! 3126:. Although you can't confirm this, it then sounds like Vuehallo's assertion that he used the 185. IP must be false. As far as I can tell with the limited tools at my disposal, that IP is not a proxy and, although it's been a long time and I don't have access to recent CU results, I don't recall Dopenguins ever using a legitimate English IP. BTW, curiosity trivia, how do you and Mz7 813:. However, the image is currently not used in any articles on Knowledge. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Knowledge (see 3092:

81. himself is editing from an English ISP). If I've incorrectly blocked Vuehalloo, the block should be lifted, but I'm also suspicious of IP 81.'s behavior. Obviously, I'm not expecting you to disclose anything that connects IPs to named accounts, but whatever you believe you can do would be helpful. Thanks.--

3275:), but to use such a proxy requires a nontrivial amount of money and interest, and I don't think we've ever seen Dopenguins use this kind of proxy in the past. Overall, I feel like the next step here is a bit of a reluctant unblock of Vuehalloo because of the uncertainty of the evidence. What do you think? 3289:

Thanks for your comments. I had in fact noticed the 194. pblock and the reason for it. Everything about this event (filing of the SPI report) was odd. I'm afraid I'm still suspicious of everyone involved, but I agree with you that I must unblock the user. Of course, you haven't weighed in on the most

2538:

Many editors believe it would be unpleasant to have so much attention focused on them. This includes being indirectly a part of watchlists and editors going through your edit history with the chance that some event, possibly a relatively trivial event, becomes the focus of editor discussion for up to

715:

Knowledge; you can still log into your account even if the IP address is blocked, and in most cases, you should still be able to edit after logging in, even from a blocked IP address. The next time that you find yourself unable to edit Knowledge because of a block affecting your IP address, could you

3091:

I'm having trouble with all of this. Although I know from my own experience that checks of possible Dopenguins socks can be problematic, especially if they've made very few edits, because of Dopenguins' use of proxies. Still, as IP 81. says, Dopenguins doesn't edit from legitimate IPs in England (IP

3075:

having to do with an MOS issue that Vuehalloo misinterpreted. Vuehalloo's stated purpose for creating an account was to file the SPI. I deleted the SPI as meritless (implicitly a personal attack against ZH8000). In looking through the Dopenguins archive, I noticed that Dopenguins socks have attacked

2805:

to publish that new information. The other issue I want to discuss is your closeness to the article subject. In general, Knowledge strongly discourages editors from editing any article subject that they have an external relationship with. This is because you have a conflict of interest with respect

1175:

If you are no longer very active on Knowledge or you no longer wish to be part of the New Page Reviewer user group, please consider asking any admin to remove you from the list. This will enable NPP to have a better overview of its performance and what improvements need to be made to the process or

2208:

A more efficient way of sending changes from Wikidata to Wikimedia wikis that show them has been enabled for the following 10 wikis: mediawiki.org, the Italian, Catalan, Hebrew and Vietnamese Wikipedias, French Wikisource, and English Wikivoygage, Wikibooks, Wiktionary and Wikinews. If you notice

605: 3188:

Hmm, the Vuehalloo account doesn't appear to be using proxies, and it doesn't look like they're on a range frequented by Dopenguins. From a purely technical standpoint, I do not think there is sufficient evidence to conclude definitively that Vuehalloo is Dopenguins. I do, however, share your

243:

I do not have any Dispute with any editors in Knowledge but this user remove all my edits , this user refuse put Kurdish and Arabic names in articles and I required for him discuss with me , he was did not answer me and removed all my edits. This user was block for one week before few weeks

691:

along with my family. I'll be here for 3 years from today. Unfortunately I can't login to Knowledge from some places here. I think many IP addresses are blocked here due to which I cannot work in Wikimedia projects. Humbly requesting you to add me to the IP block exemption. Thank you, --

596:

In 2017, the provided jQuery library was upgraded from version 1 to 3, with a compatibility layer. The migration will soon finish, to make the site load faster for everyone. If you maintain a gadget or user script, check if you have any JQMIGRATE errors and fix them, or they will break.

1758:

will no longer work. They will also have problems with many other websites. Users who have updated their software in the last five years are unlikely to have problems. Users in Europe, Africa and Asia are less likely to have immediate problems even if their software is too old. You can

2102:

to use the discretionary sanctions procedure in topic areas where it is authorised to facilitate consensus in RfCs. This includes, but is not limited to, enforcing sectioned comments, word/diff limits and moratoriums on a particular topic from being brought in an RfC for up to a

3385:. Your duties may require some private communications with the other commissioners, traditionally wikimail and/or email has been used for this, along with IRC - but this is up to you to decide. Again, thank you for volunteering for this important position. Best regards, — 2766:

It is so frustrating that the article about my father which has been hosted more or less intact for 15Y on Knowledge is being systematically destroyed by so-called editors following new dogma about wikipedia (that wikipedia is a digest of magazine articles and journal papers

1770:

when someone leaves a comment on user talk page or mentions you in a talk page comment. Clicking the notification link will now bring you to the comment and highlight it. Previously, doing so brought you to the top of the section that contained the comment. You can find

1350:

A technical change was made to the MonoBook skin to allow for easier maintenance and upkeep. This has resulted in some minor changes to HTML that make MonoBook's HTML consistent with other skins. Efforts have been made to minimize the impact on editors, but please ping

3978:

process has begun. Following feedback on Phase 1, in order to ensure that the largest number of people possible can see all proposals, new proposals will only be accepted for the for the first 7 days of Phase 2. The 30 day discussion is scheduled to last until

1344:

MediaWiki had a feature that would highlight local links to short articles in a different style. Each user could pick the size at which "stubs" would be highlighted. This feature was very bad for performance, and following a consultation, has been removed.

1186:

Various awards are due to be allocated by the end of the year and barnstars are overdue. If you would like to manage this, please let us know. Indeed, if you are interested in coordinating NPR, it does not involve much time and the tasks are described

1043:

deleting that information along with that YouTube video reference,so please look at that matter if that reference is not appropriate then I will not add that reference again but if YouTube video can be added as a reference and please stop that user

4400: 3907: 1154:

are also a serious issue. Most non-regular contributors do not understand why, and most of our Reviewers are not experts on copyright law - and can't be expected to be, but there is excellent, easy-to-follow advice on COPYVIO detection

1067:. I'm not familiar with this subject matter, so I can't help with the specifics of the dispute. However, in general, YouTube is not considered a reliable enough source for Knowledge purposes. This is primarily because it is considered a " 3189:

suspicion about the peculiarity of certain aspects of this situation. It is unusual for a random IP (81.147.178.170) to take notice of an obscure sockpuppetry block, and also interestingly, the IP that Vuehalloo accused ZH8000 of using,

3087:

was the same as Vuehalloo's. I reverted IP 81. as having no business in any of this, but Vuehalloo reinstated the IP's edit, and I left it alone. Today, the IP posted an extensive analysis of Dopenguins that is impressive in its depth.

3271:, is in a range that is partially blocked because it is used by Dopenguins. There is a very small chance that Vuehalloo is using a novel kind of proxy that we've really only started seeing this year (I'm hesitant to share more per 2712: 3911: 3107:

I ran a check on Vuehalloo when investigating the unblock request. If I remember correctly, it was consistent but not conclusive, as is common with Dopenguins socks. Mz7 may have better luck or see something I didn't.

3500:

for those who use a lot of information from the Wikimedia projects on other sites. It is a way to get big commercial users to pay for the data. There will soon be a copy of the Wikimedia Enterprise dataset. You can

609: 1164:

At the time of the last newsletter (#25, December 2020) the backlog was only just over 2,000 articles. New Page Review is an official system. It's the only firewall against the inclusion of new, improper pages.

439:

The Score extension has been re-enabled on public wikis. It has been updated, but has been placed in safe mode to address unresolved security issues. Further information on the security issues can be found on the

1267:

Hi Mz7! Not sure if the fact that they have now actually confessed to be SheryOfficial (as well as a bunch of other accounts) makes things easier, or rather more difficult... Great news about the new CUs though!

568:

deployed have been part of A/B testing since deployment, in which some newcomers did not receive the new features. Now, all of the newcomers on 21 of the smallest of those wikis will be receiving the features.

3366: 2134: 3311:

Heh, I was scrolling through my talk page and realized that I had embarrassingly missed your question. I say "doe penguins" (like the female deer), precisely because it sounds kind of like "dope penguins".

3203: 3068: 463: 409: 3568:, and the bot appears to have stopped updating the list around 5.5 hours ago. There have been various updates at SPI since then, and I wanted to make sure you were aware of the bot's malfunctioning. — 2845: 2793:

I'm sorry that you feel frustrated by your experience here. There are a couple different issues involved here. Firstly, has the historical correspondence you are referring to ever been published in a

4804:. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose 3374: 930:

Starting this week, Knowledge in Italian will receive weekly software updates on Wednesdays. It used to receive the updates on Thursdays. Due to this change, bugs will be noticed and fixed sooner.

2584:

There is a large gap between the permissions an editor can obtain and the admin toolset. This brings increased scrutiny for RFA candidates, as editors evaluate their feasibility in lots of areas.

4718: 2806:

to those subjects, which is not a judgment of your character, but rather a description of a situation. For more information on editing with a conflict of interest, please read our guideline at

380: 384: 3878: 790: 1734:

of MediaWiki will be on test wikis and MediaWiki.org from 28 September. It will be on non-Knowledge wikis and some Wikipedias from 29 September. It will be on all wikis from 30 September (

1390:

of MediaWiki will be on test wikis and MediaWiki.org from 21 September. It will be on non-Knowledge wikis and some Wikipedias from 22 September. It will be on all wikis from 23 September (

923:

of MediaWiki will be on test wikis and MediaWiki.org from 14 September. It will be on non-Knowledge wikis and some Wikipedias from 15 September. It will be on all wikis from 16 September (

3769: 3370: 3472: 531: 4710: 4487: 3915: 5060:

of MediaWiki will be on test wikis and MediaWiki.org from 30 November. It will be on non-Knowledge wikis and some Wikipedias from 1 December. It will be on all wikis from 2 December (

4820: 2175: 608:

is ready. Moving forward, the Anti-Harassment Tools team is looking for projects that are willing to experiment with restricting IP editing on their wiki for a short-term experiment.

4541:

of MediaWiki will be on test wikis and MediaWiki.org from 2 November. It will be on non-Knowledge wikis and some Wikipedias from 3 November. It will be on all wikis from 4 November (

3860:

of MediaWiki will be on test wikis and MediaWiki.org from 26 October. It will be on non-Knowledge wikis and some Wikipedias from 27 October. It will be on all wikis from 28 October (

3449:

of MediaWiki will be on test wikis and MediaWiki.org from 19 October. It will be on non-Knowledge wikis and some Wikipedias from 20 October. It will be on all wikis from 21 October (

2668:

of MediaWiki will be on test wikis and MediaWiki.org from 12 October. It will be on non-Knowledge wikis and some Wikipedias from 13 October. It will be on all wikis from 14 October (

837: 4790: 4300: 4296: 4274: 4270: 4266: 4262: 4258: 2232:

of MediaWiki will be on test wikis and MediaWiki.org from 5 October. It will be on non-Knowledge wikis and some Wikipedias from 6 October. It will be on all wikis from 7 October (

4893: 4847: 2559:

There are too few candidates. This not only limits the number of new admin we get but also makes it harder to identify other RfA issues because we have such a small sample size.

1749:

provide a better onboarding experience. Since the vast majority of Wikipedias now have access to the Growth features, GettingStarted will be deactivated starting on 4 October.

1628: 1550: 4999: 1453: 939:

again. You do this by connecting the page to a Wikidata item. The new Vector skin has moved the language links but the new language selector cannot add language links yet.

4138: 3378: 3130:

Dopenguins in your head? I "say" Doe-penguins, but I have no idea if that's "correct". Just thought I'd ask while I was here as I've been typing the name now repeatedly.--

2099: 1760: 1148:

have been infiltrated. The good news is that detection is improving, but the downside is that it creates the need for a huge clean up - which of course adds to backlogs.

3197: 2831: 1905: 1901: 1897: 1893: 1239: 2708: 4925: 4901: 4666: 4202: 4194: 4190: 4186: 4100: 2936: 2600: 2126:

expanding the trial of Growth Features from 2% of new accounts to 25%, and the share of newcomers getting mentorship from 2% to 5%. Experienced editors are invited to

2044: 1598: 2081: 1172:

New Page Reviewers plus a further 1,080 admins, but as much as nearly 90% of the patrolling is still being done by around only the 20 or so most regular patrollers.

338: 4917: 4909: 4074: 4042: 2780: 1558: 1456:

change to how you obtain tokens from the API has been delayed to September 21 because of an incompatibility with Pywikibot. Bot operators using Pywikibot can follow

2627: 2123: 3988: 2611: 1742: 2256:

for unsuppressed log entries about suppressed edits. If your bot needs to know this, do a separate revision query. Additionally, the property will have the value

4961: 4885: 4423: 4404: 4050: 4010: 3752: 3382: 3362: 2077: 1889: 1566: 467: 4224: 2704: 2577:

Because RfA carries with it lifetime tenure, granting any given editor sysop feels incredibly important. This creates a risk adverse and high stakes atmosphere.

2320: 1980: 1131: 936: 4949: 4941: 4877: 4326: 4066: 4058: 4018: 3971: 2528:

The atmosphere at RfA is deeply unpleasant. This makes it so fewer candidates wish to run and also means that some members of our community don't comment/vote.

1590: 1582: 1574: 1518: 1213: 5079: 4736: 4560: 3933: 3528: 3101: 2730: 2388: 1816: 1475: 1188: 983: 627: 294: 4334: 3076:

ZH8000, although not, as far as I know, gone as far as filing an SPI against them. For those reasons, I blocked Vuehalloo as a suspected sock of Dopenguins.

2931: 2819: 733: 4144: 3577: 5010:

Is the question that I asked of the ArbCom candidates considered one question, or two questions? So, am I allowed to ask another non-follow-up question?

4869: 4638: 4026: 3781: 3510: 2999: 2605:

which will last for the next 1-2 weeks. This will be followed by Phase 2, a 30 day discussion to consider solutions to the problems identified in Phase 1.

2088: 1526: 1207: 1197: 5099: 4756: 4596: 4580: 3953: 3636: 3613: 3599: 3548: 2750: 2408: 1847: 1836: 1495: 1003: 647: 4933: 4090: 4082: 2844:

that was reverted on ARBPIA 30/500 grounds. This after being inactive since the SPI discussion you closed in March, and within a few hours of me opening

2502: 1707:(article tools) part of the skin. A recent change to the HTML may have made those links a different font-size. This can be fixed by adding the CSS class 1294: 1262: 490: 284: 275:, I will not be granting you this permission at this time. You are welcome to request the permission again at the same place after some time has passed. 5019: 1084: 3170: 3153: 3139: 3117: 2797:

outside of Knowledge? Perhaps, for example, on a biographical page on a university website? The principle that I think the editors referred you to is "

2610:

There are 2 future mailings planned. One when Phase 2 opens and one with the results of Phase 2. To opt-out of future mailings, please remove yourself

391: 2549:

It used to be far easier to pass RfA however the standards necessary to pass have continued to rise such that only "perfect" candidates will pass now.

2489: 2018: 1090:

So then why most of wikipedia contents added without references?then we have to remove that editings whenever we find any editing without references?

4670: 3801: 3342: 3328: 3299: 3284: 342: 328: 262: 3487: 2841: 1217: 4612: 4520:

There is a limit on the amount of emails a user can send each day. This limit is now global instead of per-wiki. This change is to prevent abuse.

3903: 3714: 3502: 1913: 945: 4464: 4034: 2871: 2852:. Strange behavior for sure – I have no knowledge of the SPI area but figured I'd drop you a note just in case you feel any action is warranted. 2152: 2080:

has standardised the 500/30 (extended confirmed) restrictions placed by the Arbitration Committee. The standardised restriction is now listed in

1958: 1785: 1534: 1431: 1369:

There was a problem with search last week. Many search requests did not work for 2 hours because of an accidental restart of the search servers.

508: 701: 4983: 4969: 4650: 4122: 4108: 3661:

Message added 05:35, 24 October 2021 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can

2442: 1948: 1612: 1745:

was built in 2013, and provides an onboarding process for new account holders in a few versions of Knowledge. However, the recently developed

1136:- there is increase in the abuse of Knowledge and its processes by POV pushers, Paid Editors, and by holders of various user rights including 878: 4469: 2876: 2157: 1542: 1099: 1057: 885:

about the features. This translatable FAQ covers the description of the features, how to use them, how to change the configuration, and more.

513: 207: 187: 167: 147: 127: 107: 87: 4176: 3468: 1746: 870: 565: 4629:, although I suppose marking them as read as soon as they come in has indeed led to incidents where I've forgotten to follow-up on them... 4330: 3391: 2761: 2471: 4767: 4658: 2948: 1156: 1141: 3493: 711:. Unfortunately, I was not able to identify the IP address block that is affecting your account. Note that blocks only prevent you from 4459: 3427: 3016: 2147: 2127: 1879: 600: 503: 785: 441: 202: 182: 142: 122: 102: 3838: 3083:, but I have no way of knowing if Yamla ran a check. Then along comes the IP 81. who asked Vuehallo about 185., an IP whose edit to 1767: 895: 2021:, there is consensus to treat discord logs the same as IRC logs. This means that discord logs will be oversighted if posted onwiki. 5087: 5075: 5039: 5025: 4744: 4732: 4690: 4676: 4568: 4556: 4508: 4494: 3941: 3929: 3825: 3811: 3536: 3524: 3411: 3397: 2738: 2726: 2647: 2633: 2396: 2384: 2196: 2182: 1824: 1812: 1649: 1635: 1483: 1471: 1317: 1303: 991: 979: 857: 843: 825: 635: 623: 552: 538: 2367: 2137:

of the 2021 CheckUser and Oversight appointments process is open for editors to provide comments and ask questions to candidates.

2007: 1506: 1403: 4987: 4857: 4126: 3559: 2899: 1704: 1616: 724:? Importantly, please submit this form from the IP address that is blocked. This is so that we can verify the problem. Thanks, 402: 5083: 4740: 4564: 4149: 3998: 3937: 3532: 3209: 2734: 2392: 1852: 1820: 1479: 987: 805: 631: 405:

to decide when, if ever, should discord logs be eligible for removal when posted onwiki (including whether to oversight them)

299: 3881:

will allow the text in the diff for before and after to be treated as separate columns and will remove any unwanted syntax.

1104: 4995: 4843: 4662: 4483: 4198: 4134: 3708: 2966: 2942: 2623: 2171: 1909: 1793: 1624: 1439: 1338: 1334: 1145: 527: 3780:

You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself

3034: 247:

I hope you give me this permission , I wrote in Knowledge 3 years and I do not have any problem with any one I promise you

3719: 3478:

3–5% of editors may be blocked in the next few months. This is because of a new service in Safari, which is similar to a

3010: 2678: 2505:

of the RfA 2021 review. 8 out of the 21 issues discussed were found to have consensus. Thanks to our closers of Phase 1,

3426:

is a catalogue to make it easier to find software tools that can be used for working on the Wikimedia projects. You can

1418:. API users should update their code to avoid unrecognized parameter warnings. Pywikibot users should upgrade to 6.6.0. 3663: 197: 177: 157: 137: 117: 97: 5038: