User talk:Wugapodes/Archive 16

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 10 ← Archive 14 Archive 15 Archive 16 Archive 17 Archive 18 → Archive 20

Pending Changes

Hello, Wugapodes. Thank you so much for granting me Pending Changes Reviewer, it means a lot. I saw that this rank expires in February, is there any way that I can extend this once February comes along! Thanks. Helpthepeople9 (talk) 15:10, 8 November 2020 (UTC)

@Helpthepeople9: No problem, I hope you find the new tool useful! As for how to extend it, in early February you can either make another request at WP:PERM or post on my talk page. Either way, someone will review how you've used the tool for the last few months. If you've been using it to review pending changes and your reviews have been good, you'll likely get granted the permission indefinitely. Hope that helps! — Wug·a·po·des​ 22:10, 8 November 2020 (UTC)

linguistic-y stuff

Hey, Wugapodes! I grew up in Dayton, Ohio, which currently has its pronounciation rendered as (/ˈdeɪtən/, which looks to me like DAYt'n. Which isn't incorrect, that's how newscasters and extremely careful people would pronounce it, but most locals actually pronounce it with a T-glottalization, sort of DAY'n. I'd like to add it as an alternative pronunciation if appropriate. 1. Do I need some reliable source for this likely-noncontroversial-to-anyone-from-Dayton addition? Because I don't even know where to look for that, and 2. How would that be rendered? Thanks for any help, I tried to figure out how to render it but quickly realized that was't going to happen. —valereee (talk) 19:28, 8 November 2020 (UTC)

Hi Valereee and nice to "hear" from you! Our pronunciations use broad transcription so that we can cover as many accents as possible, and in most dialects phonetic glottal stops are part of the /t/ phoneme. So while some dialects would have [ʔ], it would still be part of the diaphoneme /t/ since few English dialects (none?) have phonemic glottal stop. That said, it may still be worth including a local pronunciation variant because place names can sometimes serve as shibboleths---I vaguely remember an example of Boris Johnson getting laughed at in parliament for using a long-a in Bath (Somerset).
For the local pronunciation, you would probably want a source at least attesting that t-glottalization occurs routinely in the dialect because other possibilities exist. Unfortunately, I don't know of any such sources off the top of my head. The only paper I could find on t-glottalization in American English (after an admittedly cursory search) was Eddington and Taylor (2009) which surveys the whole country but has some participants from Ohio. They look at intervocalic t-glottalization across word boundaries (e.g. right ankle), so different from the Dayton example but still comparable because patterns across word boundaries tend to originate as patterns within words. They find that t-glottalization is favored following front vowels (which is the case for Dayton), most common in young women (which you were, by definition, when growing up), and more frequent in the western US (not applicable).
There is a lot more work on variable t-release (but still not specific to Ohio) which I would view as the alternate hypothesis, but as I mentioned I don't think anyone's looked at this specifically. I think the most likely pronunciation would be [deɪt̚n̩] where the [t] has no audible release, the schwa is deleted, and the [n] is a syllabic consonant. That's an empirical question though, and it's quite possible that this is a change-in-progress to something like [deɪʔn̩]. Sorry that I don't have a more definitive answer, but hopefully this helps! — Wug·a·po·des​ 22:03, 8 November 2020 (UTC)
Inaudible release, glottalization, or glottal reinforcement in /ˈVtən/ is nothing unusual, but rather the norm, in North American English. (That is, you rarely hear a clear, released [t] in this position like you do in syllable onsets.) That doesn't mean /ˈdeɪtən/ is incorrect, but quite the opposite, because [tʰ], [t] [ʔ], [t̚], etc. are in complementary distribution or free variation, thus forming one phoneme, /t/, and the type of notation the IPAc-en template and the Help:IPA/English key it links to use is diaphonemic. I don't see how it would be appropriate to add an allophonic transcription since what you're describing is the normal pronunciation not particular to the region. Nardog (talk) 04:38, 9 November 2020 (UTC)
I was hoping you'd chime in! Nardog has a better knowledge of our IPA transcription style, so I would trust their judgment more than mine. — Wug·a·po·des​ 06:04, 9 November 2020 (UTC)
Well, that's flattering but in principle we should never trust any one person's judgment on Wikipedia. ;) I can also see where Valereee is coming from. "If the IPA is only understood by linguists, what use is there?" is a frequent criticism, and as much as I find that to be the fault of education, not of the IPA or linguistics themselves—you rarely hear the same criticism against the periodic table or mathematical expressions, and that's because even non-chemists and non-mathematicians learn about them in education—I can understand why some people see a problem if e.g. /t/ is so often misunderstood to always represent an audibly released [t], whereas I see a problem in adding allophonic transcriptions predictable from diaphonemic ones from the perspective of theoretical and editorial consistency/efficiency. So adding audio recordings might be a better way to mitigate that. Nardog (talk) 07:44, 9 November 2020 (UTC)
Nardog and Wug, thanks so much! I'd be happy to add an audio recording...I'll look into it further, see if I can figure out how. —valereee (talk) 13:14, 9 November 2020 (UTC)

Tech News: 2020-46

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

Changes later this week

  • There is no new MediaWiki version this week.

Future changes

  • You can see reference previews. This shows a preview of the footnote when you hover over it. This has been a beta feature. It will move out of beta and be enabled by default. There will be an option not to use it. The developers are looking for small or medium-sized wikis to be the first ones. You can let them know if your wiki is interested. [1]
  • From November 16 the categories will not be sorted in order for a short time. This is because the developers are upgrading to a new version of the internationalisation library. They will use a script to fix the existing categories. This can take a few hours or a few days depending on how big the wiki is. You can read more. [2][3]

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

15:49, 9 November 2020 (UTC)

protection of user warning templates

Should the other levels of the Uw-genre warning template be protected (as they are currently not), and also all other warning templates without protection (when they are used by twinkle) be protected? A quick random check of around 10 of them gives me three which have no protection: Template:Uw-thumb1 (levels 1 to 4 are used in twinkle and redwarn), Template:Uw-taxonomy1 (levels 1 to 4 are used used in redwarn) and Template:Uw-color1 (levels 1 to 4 used in redwarn and twinkle). Do you think that all warning templates used by redwarn / twinkle should be at minimum indef semi-protected? Your reasoning about them being presumed to be high use templates if they are in twinkle / redwarn, suggests that ones used in twinkle/redwarn should be protected at some level. I would be inclined to support this based on your reasoning. Dreamy Jazz talk to me | my contributions 13:26, 10 November 2020 (UTC)

@Dreamy Jazz: I'd never taken a systematic look at the series so thank you for doing that! I'd say yes, if you come across user warnings used in Twinkle or RedWarn (and they're not newly created templates) semi-protection is justified. Since user warnings are substituted, cleaning up vandalism is actually a lot harder. With transclusion we can just revert and everything goes back to normal, but because substitution leaves no backlink and reverting the template doesn't affect the substituted code. If a vandalized version gets substituted, we would need to track down the affected substitutions without "What links here" and fix them by hand/bot. Preventing helpful edits from anons and non-AC editors is certainly a cost, but the risk-reward trade-off makes me more liberal with semi-protection on templates substituted by user scripts. — Wug·a·po·des​ 21:12, 10 November 2020 (UTC)
I'll go around and protect the ones which are used by twinkle or red warn. Dreamy Jazz talk to me | my contributions 22:06, 10 November 2020 (UTC)
From what I can tell, all the ones listed in Template:Multi notice links are now at least semi protected. Dreamy Jazz talk to me | my contributions 22:43, 10 November 2020 (UTC)

Credit for COVID-19 map

I see your name on parts of

A publisher wrote in to the WP:Volunteer Response Team asking whom they should credit if they republish this map. There is a lot of media here, including the map, data, the template, and I am not sure what else.

Interactive maps are new for wiki but you seem particularly involved in curating this so I thought I would ask you. How should a publisher give credit for reuse of media like this? Also, are you the chief developer of this? Does any other wiki user come to mind as key in the development of this map? Thanks. Blue Rasberry (talk) 17:55, 12 November 2020 (UTC)

@Bluerasberry: I would recommend attribution in the following way: "Copyright 2020 Wugapodes, Wikipedia contributors, Michael Bostock, and TopoJSON contributors. CC By-SA 3.0 licensed." I chiefly developed the code used on Wikipedia, and to the best of my knowledge the TopoJSON which defines the world map was developed by Michael Bostock. Contributors to the wiki-markup are listed in the page history of {{Interactive COVID-19 maps/common}} and contributors to the TopoJSON file are listed at the GitHub repo. Linking to those pages is highly recommended but not strictly required. All the other templates are just wrappers around {{Interactive COVID-19 maps/common}} so there shouldn't be a need to reference any other templates or pages.
One important caveat is that the data are in the public domain in the United States, but that may not be true of other jurisdiction like the European Union. The US does not provide copyright protections to data, but under some circumstances the EU does provide copyright protections to data sets. If re-users will publish or have their main servers located outside the US, they should be aware of this complication as they are responsible for understanding the copyright laws of their jurisdiction per Wikipedia:Reusing Wikipedia content.
As for what to reuse, our graph extension uses the Vega software (version 2.x) to parse the code located at {{Interactive COVID-19 maps/common}}. You can see all the data subpages at Special:PrefixIndex/Template:Interactive_COVID-19_maps/data, and they are updated daily by a series of scripts which may be reused under the MIT license. Beyond Vega and WugBot scripts, there shouldn't be any other software required to get the map up and running. If downstream re-users have issues they can email me or post on my talk page and I'll do my best to troubleshoot. Hope that helps! — Wug·a·po·des​ 22:29, 12 November 2020 (UTC)
Thanks for this, I thought there would be a more complicated than typical situation.
Are you aware of existing documentation for the general case of giving credit for content in Wikipedia, when that content includes Wikidata, datasets from Commons, and perhaps somehow even datasets from off-wiki somehow oddly brought into Wikipedia? I am a bit interested in starting to draft something, but I think I will ask around first if anyone already did some documentation. If and when I do this I expect that this COVID map is going to be the case study, and I will let you know. Thanks. Blue Rasberry (talk) 23:05, 12 November 2020 (UTC)
@Bluerasberry: In general this would fall under license compatibility which can quickly become a giant mess. On-wiki, I'm not aware of any documentation, but the Free Software Foundation and the Creative Commons (publishers of our two licenses) both maintain compatibility guidance on their websites: GPL/FDL compatibility and CC compatibility. Ignoring a lot of important technicalities, when you combine Component Works with different licenses to form a Larger Work, that Larger Work is governed by the most restrictive license covering a Component Work. So using this template as an example case, TopoJSON is licensed under a variant BSD 2-Clause license, WugBot under MIT, and Wikipedia under CC By-SA. The only major requirements of BSD and MIT licenses are attribution, and because CC By-SA requires attribution, you automatically comply with BSD and MIT licenses simply by complying with the "By" part of CC By-SA. But, because CC By-SA also has a ShareAlike clause, anyone reusing the Larger Work must also comply with the SA clause making the CC By-SA license govern the Larger Work as the most restrictive license. I can say from experience, this is probably as complex as you will need to get for most combinations, but there are some really complex cases and compatibility is not always two-way.
The most complex case that would probably occur with our content is combining our wikitext with GPL code. This is likely to occur when turning javascript gadgets or lua modules into MediaWiki extensions. I will use my experience writing the Extension:ChessBrowser MediaWiki extension (this is technically a lie-to-children, but what follows is close to what happened) as an example of the kind of complex licensing problem that is most likely to arise when turning javascript gadgets into MediaWiki extensions. When reusing our content, downstream projects can choose either the CC By-SA 3.0 license or the GFDL license (or both). However The GFDL is not compatible with the GPL (which is why Debian does not use it) so the only possibility for using our code in a GPL project like MediaWiki is to use it under a Creative Commons license. However, CC By-SA 3.0 is not compatibile with any version of the GPL. Luckily, CC By-SA 3.0 contains a clause (4.b.ii) that allows a re-user to upgrade to any later CC By-SA license at their option, and CC By-SA 4.0 is compatible with the GPLv3 but only that version. So to use the javascript in MediaWiki, it had to be upgraded to CC By-SA 4.0 so that it could be combined with GPL code. However, I wanted to re-use a parser library in ChessBrowser that was licensed under the GPLv2.1 only. Well, that's not possible because unlike CC 3.0, the GPL does not contain an automatic right to upgrade to newer versions. If the code were licensed under GPLv2.1 or any later version, then I could upgrade to GPLv3, but because it didn't I needed to ask the authors to upgrade to GPLv3. Once that code's license was upgraded, I could combine the now-CC By-SA 4.0 code with the now-GPLv3 code into the larger ChessBrowser work, and the entire Larger Work is licensed under the GPLv3.
In reality, the parsing library I used was licensed under the Lesser GPL, but didn't specify any version. The (L)GPL does not allow upgrading when the version number is specified, but it does allow you to choose "any version ever published by the Free Software Foundation" if no version number is specified (LGPLv2.1 Section 13; LGPLv3 Section 6). Since no version number was specified and I needed it to be (L)GPLv3, I was able to pick v3 without a fuss (though I did get them to clarify). Similarly, Kipod clarified that his code was public domain under CC0 which made the CC By-SA problem moot. Had these things not fallen into place though, there would have been larger problems as described above. License compatibility is a massive topic that even lawyers can struggle with, but in most cases it's just reading a chart or documentation page like those I linked you to earlier. — Wug·a·po·des​ 00:43, 13 November 2020 (UTC)

Tech News: 2020-47

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

  • Listings on category pages are sorted on each wiki for that language using a library. For a brief period on 16 November, changes to categories will not be sorted correctly for most languages. This is because the developers are upgrading to a new version of the library. They will then use a script to fix the existing categories. This will take a few hours or a few days depending on how big the wiki is. You can read more. [4][5]

Changes later this week

  • If you merged two pages in a namespace where pages can't redirect this used to break the merge history. This will now be fixed. [6]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 17 November. It will be on non-Wikipedia wikis and some Wikipedias from 18 November. It will be on all wikis from 19 November (calendar).

Future changes

  • The Community Wishlist Survey is now open for proposals. The survey decides what the Community Tech team will work on. You can post proposals from 16 to 30 November. You can vote on proposals from 8 December to 21 December.

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

15:36, 16 November 2020 (UTC)

Vanish

Hi there,

Hope you are doing well. Coudl you please help me to remove my account from wikipedia and all of my comments/presence?

Regards Mirhasanov (talk) 14:14, 17 November 2020 (UTC)

@Mirhasanov: I'm doing well, thanks for asking, though I'm sorry to hear that you've decided to leave. I hope you're doing well aside from this whole mess. Our content licenses forbid account deletion, and in general we don't remove comments and contributions already made; vanishing just changes your name and deletes your userpage. If you want to leave, you can simply stop editing, and I think this is your best option. Not only does it leave the possibility for you to return in the future, you avoid having to stick around to deal with the bureaucratic process of vanishing. I should warn you, like ProcrastinatingReader did, that a request to vanish is likely to be denied, and you will probably just get more frustrated. Personally, I would support you in your request because I have a very expansive view on who is eligible for vanishing, but my view is not shared by most of the community and even with my endorsement you should not expect your request to be honored. Unless you have a really good reason to not want your username associated with your edits, it is probably best to just leave and let us forget about you. However, if you still seriously want to request a courtesy vanishing, you should follow the instructions since I do not have the technical ability to fulfill those requests. — Wug·a·po·des​ 18:28, 17 November 2020 (UTC)
  • Thank you very much. I trust you and see that you understand me. You are right that I don't want go through another frustrated process which makes me emotional, seems like the only way is changing password to some complex one and forget forever. Take care and have a great day.Mirhasanov (talk) 18:35, 17 November 2020 (UTC)

AE sanction

Can I speak to you in relation to this? I've had a few days to gather my thoughts and I want to ask if you could reconsider the sanction. There's much that I woant to say and I will take this opportunity to clear up any confusion/uncertainties that I have about the encyclopedia (in particular its policies on content dispute resolution) now that I am in direct communication with an administrator. This is the first time that I've been subject to an administrative sanction (of any sort) and I will ensure that it will never happen again. Flaughtin (talk) 00:42, 18 November 2020 (UTC)

@Flaughtin: I'm glad you took some time to reflect, but I don't feel comfortable lifting the sanction unilaterally at this point. While ultimately I'm responsible for the ban and paperwork, the sanction came at the end of a discussion where multiple editors supported such a restriction, and so I think it's a bad idea to overturn that just two days later. While your message here is promising, administrators tend to want some evidence that you've contributed productively before lifting a sanction as unneeded. That can easily be shown by continuing to edit outside the topic area. What I recommend is finding a topic or task you like that is completely unrelated to the US-China trade war and do that for a month or two; if you need ideas we have a lot of things at WP:BACKLOG that could use attention. After that, you can ask me again or appeal at WP:AE where it will be heard by uninvolved administrators. If at that point you've been productive and make the same promise you just made to me, I think you have a good chance of success. Worst case, the ban is time limited and will expire in 6 months regardless of what we all do. I hope that helps, and let me know if there's anything I should clarify. — Wug·a·po·des​ 01:57, 18 November 2020 (UTC)

Precious anniversary

Precious
Four years!

--Gerda Arendt (talk) 07:32, 18 November 2020 (UTC)

AN/I

AN/I on user you closed the community topic ban on.--Astral Leap (talk) 09:39, 19 November 2020 (UTC)

Tech News: 2020-48

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

  • Timestamps in Special:Log are now links. They go to Special:Log for only that entry. This is how timestamps work on for example the history page. [7]

Changes later this week

  • There is no new MediaWiki version this week.

Future changes

  • Advanced item The Wikimedia Cloud VPS hosts technical projects for the Wikimedia movement. Developers need to claim projects they use. This is because old and unused projects are removed once a year. Unclaimed projects can be shut down from 1 December. Unclaimed projects can be deleted from 1 January. [8]

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

17:17, 23 November 2020 (UTC)

ArbCom 2020 Elections voter message

Hello! Voting in the 2020 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 7 December 2020. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. 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 site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2020 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 02:44, 24 November 2020 (UTC)

WP:AN#Haleth_and_Jiren_related

Hi Wugapodes, your opinion would be welcome at WP:AN#Haleth_and_Jiren_related. :) Thanks and best regards, ~ ToBeFree (talk) 22:40, 27 November 2020 (UTC)

Looking into it — Wug·a·po·des​ 22:50, 27 November 2020 (UTC)

A simple request

Hi Wugapodes, I have a request. Would you consider removing, in your discretion as an admin, this comment about me at Talk:Antifa (United States)? I think it's clear that a WP:PA should not remain up at an article talk page and I would prefer not having it left there about me. I don't believe that my broaching it with the user involved will be especially productive, so I'd appreciate if you would consider removing it instead. Thank you. Wikieditor19920 (talk) 00:27, 28 November 2020 (UTC)

@Wikieditor19920: I think you should read Law of holes. Whatever it is you're doing now, it's not working, and you need to change soon or you'll be getting a CBAN. Ignore Bacondrum. Ignore that talk page. Assume you're already under a topic ban. Go do something else. Look at WP:BACKLOG and find stuff to do that's completely unrelated to American politics or the Middle East. My assumption of good faith rests on you being helpful outside of those topics, and if you wind up with a topic ban instead of an indef block, you'll need to get used to that anyway. Better to start now. To your immediate request, I looked and don't see a reason to remove it. It's supported by diffs, a day old, and later brought to a noticeboard for discussion. — Wug·a·po·des​ 01:24, 28 November 2020 (UTC)

The Signpost: 29 November 2020

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 17:47, 29 November 2020 (UTC)

advice?

So, this idea of a micro-block. I've literally always tried to give the shortest reasonable block as a way of being less harsh, thinking of it as a way to get some basically-well-intentioned-but-currently-problematic editor's attention after multiple ignored warnings without blocking them for any longer than necessary, but it's clear these aren't seen as positive basically in any way. Can you...okay, the hubs would laugh at me, this is exactly the wording his clients use disingenuously when they're hoping he doesn't actually have firm legal ground to stand on, but can you help me understand? I thought I was being kind not to block longer than required to gain compliance. —valereee (talk) 19:14, 29 November 2020 (UTC)

I think it's a WP:No angry mastodons problem--angry humans just aren't rational ¯\_(ツ)_/¯ A block's a block regardless of the length. From a more philosophical perspective, blocks are always "violent" (in the sense of meatball:NonViolence and symbolic violence), and so if you need to make a block you're already past the point of being kind. If you need to force compliance, it's hard to make a block that's too long; they can always make an unblock request when they're ready to play nice. IMO, if you're thinking about a block under 31 hours, it's not worth your while. It sounds shrewd, but if you're going to draw anger no matter what you do, you might as well take off the kid-gloves. My brain's dead after a long drive, so this is the best thinking I've got right now. Hopefully it helps? — Wug·a·po·des​ 03:37, 30 November 2020 (UTC)
Wug, that does help. Thank you for the insights! I love that meatballwiki site, too —valereee (talk) 15:02, 30 November 2020 (UTC)

Tech News: 2020-49

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

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 1 December. It will be on non-Wikipedia wikis and some Wikipedias from 2 December. It will be on all wikis from 3 December (calendar).

Future changes

  • The iOS Wikipedia app will show readers more of the article history. They can see new updates and easier see how the article has changed over time. This is an experiment. It will first be shown only to some iOS app users as a test. [9][10]
  • Advanced item The Wiki Replicas can be used for SQL queries. You can use Quarry, PAWS or other ways to do this. To make the Wiki Replicas stable there will be two changes. Cross-database JOINS will no longer work. You can also only query a database if you connect to it directly. This will happen in February 2021. If you think this affects you and you need help you can post on Phabricator or on Wikitech. [11]

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

17:43, 30 November 2020 (UTC)

Administrators' newsletter – December 2020

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

Administrator changes

removed Andrwsc • Anetode • GoldenRing • JzG • LinguistAtLarge • Nehrams2020

Interface administrator changes

added Izno

Guideline and policy news

Technical news

Arbitration

Sent by MediaWiki message delivery (talk) 02:37, 1 December 2020 (UTC)

Unblockables

I didn't want to add anything more to a conversation that was becoming a side distraction, but since it's been closed, I want to say thank you for this comment. You hit a nail on the head that I didn't know was sticking out, to take a metaphor somewhere it's not supposed to go. I don't have any followup but you gave me something to think about, and I appreciate that. Sorry to be kind of vague about it but I'm not really here to invite discussion, just to say thanks. Ivanvector (Talk/Edits) 22:33, 5 December 2020 (UTC)

@Ivanvector: I'm actually really glad you dropped this note; I was worrying all day that I was too harsh and was planning on leaving a note on your talk page when I got some time to myself. I'm glad the comment made you think, and I do mean what I said about not faulting you. If anything I really appreciate the intention behind your post and wish more people cared as much as you seem to about helping positive-but-sometimes-disruptive editors (instead of just kicking them). Ironically I think that's why I dug in my heels. If you asked me 6 months ago about repealing the "no third party appeals" thing, I probably would have supported allowing them, but watching how the Linus-as-IP thread went a few weeks ago (and vague memories of other recent threads) I realized that these well meaning discussions can cause a lot more harm than good; caring sometimes just means giving people space. So I hope you don't take my comments or the closure as a criticism of you--many people in that thread expressed a lot of faith in you and appreciation for your consideration. If anything, I saw that discussion as being a community endorsement of you (and other admins) being able to make unilateral judgment calls in situations like this. Looking at the user talk thread, my thinking was that if three of our best editors couldn't be moved to push the unblock button, then who am I to second (quadruple?) guess that? We trust your gut, even in controversial cases like this. And despite the borderline flame war, I think you helped the community move forward in figuring out solutions to Q7 of WP:AHRFC, and that's a substantial bit of progress that you should be proud to have catalyzed. I know you said no discussion, so no need to carry this on, but in my own long-winded way I really do want to thank you and make sure you know that you're appreciated for the thread and not just despite it. — Wug·a·po·des​ 03:59, 6 December 2020 (UTC)

Tech News: 2020-50

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

  • You can now put pages on your watchlist for a limited period of time. Some wikis already had this function. [12][13]

Changes later this week

  • Information from Wikidata that is used on a wiki page can be shown in recent changes and watchlists on a Wikimedia wiki. To see this you need to turn on showing Wikidata edits in your watchlist in the preferences. Changes to the Wikidata description in the language of a Wikimedia wiki will then be shown in recent changes and watchlists. This will not show edits to languages that are not relevant to your wiki. [14][15]
  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 8 December. It will be on non-Wikipedia wikis and some Wikipedias from 9 December. It will be on all wikis from 10 December (calendar).

Future changes

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

16:14, 7 December 2020 (UTC)

WugBot

Hello, Wugapodes

For some reason, WugBot keeps creating Template:Interactive Covid-19 maps/common and then it gets deleted, recreated & deleted, over and over again. Is this template being used or is the bot buggy? Liz Read! Talk! 17:54, 6 December 2020 (UTC)

Thanks for the heads up! There was a typo at User:WugBot/CovidConfig.json that had the bot editing the uncapitalized page rather than the actual template. It should be fixed now. — Wug·a·po·des​ 18:46, 7 December 2020 (UTC)

Thank you

Hello,

This is HauntingStomper. First, I want to say thank you for giving me rollback rights. The fact that you trusted me means a lot. That being said, I never was able to use it like I was hoping for. Thankfully, the rollback rights were temporary. The trust is there, but I'm not ready for rollback. Once I find more of a use, I will request it again. For right now, I'm fine with just being an editor while finding the usual vandal every now and again.

Thank you again,

--HauntingStomper (talk) 18:32, 8 December 2020 (UTC)

@HauntingStomper: Thanks for the note! No worries about not using it; honestly tools like Twinkle, Huggle, and RedWarn do the job better than standard rollback so personally I'm not entirely sure why we keep the usergroup around. If you do think rollback or another permission would make your work easier, feel free to let me know or ask at PERM. We all want to empower editors to maintain the wiki, and it's just a practical matter that we shouldn't hand out power tools to everyone the who makes an account. Keep up the good work and let me know if you need anything else. — Wug·a·po·des​ 23:27, 9 December 2020 (UTC)

New Page Patrol December Newsletter

Hello Wugapodes,

A chart of the 2020 New Page Patrol Queue

Year in review

It has been a productive year for New Page Patrol as we've roughly cut the size of the New Page Patrol queue in half this year. We have been fortunate to have a lot of great work done by Rosguill who was the reviewer of the most pages and redirects this past year. Thanks and credit go to JTtheOG and Onel5969 who join Rosguill in repeating in the top 10 from last year. Thanks to John B123, Hughesdarren, and Mccapra who all got the NPR permission this year and joined the top 10. Also new to the top ten is DannyS712 bot III, programmed by DannyS712 which has helped to dramatically reduce the number of redirects that have needed human patrolling by patrolling certain types of redirects (e.g. for differences in accents) and by also patrolling editors who are on on the redirect whitelist.

Rank Username Num reviews Log
1 DannyS712 bot III (talk) 67,552 Patrol Page Curation
2 Rosguill (talk) 63,821 Patrol Page Curation
3 John B123 (talk) 21,697 Patrol Page Curation
4 Onel5969 (talk) 19,879 Patrol Page Curation
5 JTtheOG (talk) 12,901 Patrol Page Curation
6 Mcampany (talk) 9,103 Patrol Page Curation
7 DragonflySixtyseven (talk) 6,401 Patrol Page Curation
8 Mccapra (talk) 4,918 Patrol Page Curation
9 Hughesdarren (talk) 4,520 Patrol Page Curation
10 Utopes (talk) 3,958 Patrol Page Curation
Reviewer of the Year

John B123 has been named reviewer of the year for 2020. John has held the permission for just over 6 months and in that time has helped cut into the queue by reviewing more than 18,000 articles. His talk page shows his efforts to communicate with users, upholding NPP's goal of nurturing new users and quality over quantity.

NPP Technical Achievement Award

As a special recognition and thank you DannyS712 has been awarded the first NPP Technical Achievement Award. His work programming the bot has helped us patrol redirects tremendously - more than 60,000 redirects this past year. This has been a large contribution to New Page Patrol and definitely is worthy of recognition.

Six Month Queue Data: Today – 2262 Low – 2232 High – 10271

To opt-out of future mailings, please remove yourself here

18:17, 10 December 2020 (UTC)

Incorrect addition in the MajorBuxton Sock Wiki

Thanks again for your help with the sockpuppets. You added BarrelProof who is not a sock of MajorBuxton. Xenophon71 is the sockpuppet I think you wanted to add. Category:Suspected_Wikipedia_sockpuppets_of_Majorbuxton Category:Wikipedia_sockpuppets_of_Majorbuxton. Is this something only you should correct or something I can correct? -- Hyderabad22 (talk) 06:18, 11 December 2020 (UTC)

@Hyderabad22: No problem, thanks for such a helpful report! Took me a second but I figured out the problem. When you want to link to categories you need to add a colon in front of them like I did in your above message. When you posted on BarrelProof's and my talk pages, you accidentally added us to the sock categories instead of linking to them. It should be fixed now. For the sake of completeness, you might want to look at Help:Category#Linking to category pages but it basically says the same thing. — Wug·a·po·des​ 07:13, 11 December 2020 (UTC)

Noticeboard

Hello! I read your message that you left for me. I am really trying to withdraw myself now. But it's good to see that you notice that my changes are not meant to be disruptive in any way. Like I said before there's a bias towards a specific artist. And it's getting really hard and tiring to work against. I'm trying not the give it any attention anymore and just edit what needs to be edit. Best Regards. x Mirrored7 (talk) 09:20, 11 December 2020 (UTC)

Tech News: 2020-51

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

  • There is a Wikipedia app for KaiOS phones. It was released in India in September. It can now be downloaded in other countries too. [16]

Changes later this week

  • Recurrent item The new version of MediaWiki will be on test wikis and MediaWiki.org from 15 December. It will be on non-Wikipedia wikis and some Wikipedias from 16 December. It will be on all wikis from 17 December (calendar).

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

21:33, 14 December 2020 (UTC)

t-ban question

I just have a quick question regarding my t-ban. I'd like to re-arrange the images in the Religion section in the Poland article, just to de-clutter the format a bit (part of an article wide clean up), and a couple of images are related to Christianity, would that violate the t-ban if I move them up a bit or would that be considered just a generic clean up edit? --E-960 (talk) 10:01, 18 December 2020 (UTC)

@E-960: thanks for asking first. Your suggested edits would violate your TBAN. It's not reverting vandalism, and it's not a dispute resolution process, so it doesn't fall under WP:BANEX. — Wug·a·po·des​ 19:45, 18 December 2020 (UTC)

Tech News: 2020-52

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

Tech News

  • Because of the holidays the next issue of Tech News will be sent out on 11 January 2021.

Recent changes

  • The {{citation needed}} template shows when a statement in a Wikipedia article needs a source. If you click on it when you edit with the visual editor there is a popup that explains this. Now it can also show the reason and when it was added. [17]

Changes later this week

  • There is no new MediaWiki version this week or next week.

Future changes

  • You can propose and discuss what technical improvements should be done for geographic information. This could be coordinates, maps or other related things.
  • Some wikis use LanguageConverter to switch between writing systems or variants of a language. This can only be done for the entire page. There will be a <langconvert> tag that can convert a piece of text on a page. [18]
  • Oversighters and stewards can hide entries in Special:AbuseLog. They can soon hide multiple entries at once using checkboxes. This works like hiding normal edits. It will happen in early January. [19]

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

20:52, 21 December 2020 (UTC)

Looking for assistance

Hello, I recently moved some articles that went against consensus at Wikipedia:Village pump (policy)/Archive 159#Resolve the inconsistency between WP:DRAFTIFY and WP:ATD. From that discussion, I interpreted that any editor could move them back from draft where the issues could be addressed, but another editor informed me on my talk page that I must let someone experienced handle this. Is this something you can assist with? Or should I post this to the Help Desk? The drafts include Draft:Cortus, Draft:John K. Grande, Draft:Back to the Roots (company), Draft:Yamirukka Bayamen (TV series), Draft:Black Book (company), Draft:Electra Meccanica, and Draft:Babala Bagotham. thank you, -6runnerr (talk) 21:08, 21 December 2020 (UTC)

Replied on your talk. — Wug·a·po·des​ 01:17, 22 December 2020 (UTC)

Merry Christmas!

Merry Christmas and a Prosperous 2021!

Hello Wugapodes, 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 2021.
Happy editing,
Narutolovehinata5 tccsdnew 01:34, 25 December 2020 (UTC)

Spread the love by adding {{subst:Seasonal Greetings}} to other user talk pages.

The Signpost: 28 December 2020

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 04:26, 28 December 2020 (UTC)

Happy New Year!

Wugapodes,
Thanks for your contributions to Wikipedia, and a Happy New Year to you and yours! CAPTAIN RAJU(T) 00:14, 1 January 2021 (UTC)
– Send New Year cheer by adding {{subst:Happy New Year}} to user talk pages.

Happy New Year, Wugapodes!

Happy New Year!

Wugapodes,
Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.
Moneytrees🏝️Talk🌴Help out at CCI! 02:17, 1 January 2021 (UTC)

   Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Welcome to the 2021 WikiCup!

Happy New Year and Happy New WikiCup! The competition begins today and all article creators, expanders, improvers and reviewers are welcome to take part. If you have already signed up, your submissions page can be found here. If you have not yet signed up, you can add your name here and the judges will set up your submissions page. Any questions on the rules or on anything else should be directed to one of the judges, or posted to the WikiCup talk page. Signups will close at the end of January, and the first round will end on 26 February; the 64 highest scorers at that time will move on to round 2. We thank Vanamonde93 and Godot13, who have retired as judges, and we thank them for their past dedication. The judges for the WikiCup this year are Sturmvogel 66 (talk · contribs · email) and Cwmhiraeth (talk · contribs · email). Good luck! MediaWiki message delivery (talk) 11:11, 1 January 2021 (UTC)

Administrators' newsletter – January 2021

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

Guideline and policy news

Technical news

Arbitration

  • By motion, standard discretionary sanctions have been temporarily authorized for all pages relating to the Horn of Africa (defined as including Ethiopia, Somalia, Eritrea, Djibouti, and adjoining areas if involved in related disputes). The effectiveness of the discretionary sanctions can be evaluated on the request by any editor after March 1, 2021 (or sooner if for a good reason).
  • Following the 2020 Arbitration Committee elections, the following editors have been appointed to the Arbitration Committee: Barkeep49, BDD, Bradv, CaptainEek, L235, Maxim, Primefac.
Sent by MediaWiki message delivery (talk) 00:08, 5 January 2021 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Wugapodes/Archive_16&oldid=1001327564"