Jump to content

User talk:Wugapodes

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
(Redirected from User talk:WugBot)
Latest comment: 13 hours ago by MediaWiki message delivery in topic Administrators' newsletter – November 2026

Quick question

[edit]

Hey, i noticed you template-protected {{Help me}}. I was wondering if you could lower the protection to ECP, as the template only has 11 transclusions and all of them are outside the mainspace. Sure, this template is often applied and replaced with {{Help me-helped}}, but that is still not a risk in any sense of the word. In my opinion, there is not enough potential for disruption to justify template-protection in this case. (Per the High-risk templates policy, there is consensus to permanently extended-confirmed protect templates with roughly 2500–5000 transclusions.) FaviFake (talk) 21:40, 23 October 2026 (UTC)Reply

@FaviFake: I'm open to it, but I'm going to need you to explain the risks versus benefits to me. It seems like similar considerations to the Merge and AFD templates with many uses in page histories, but this one seems to have less day-to-day use while being very newbie-facing/customer service rather than article quality. It's highly visible, being linked in the first line of the widespread {{Help me-helped}}, but {{Admin help}} and the other {{help me-*}} templates are all semi-protected without incident. It was template protected a year before ECP was allowed to be used on templates, so we also have a new tool now that we didn't then. Per WP:HRT There are generally no fixed criteria, and no fixed transclusion count that is used to decide whether a template or module is high-risk; each page is considered separately., so those are the things that would convince me more than the current transclusion count on a removable message template.
If you're interested in working through protected templates that could have protection lowered, I'd also recommend reading the discussion that allowed ECP to be used for templates and some of the older context that led to it. Frankly, the HRT guideline does a bad job explaining that discussion. Opinions on the threshold ranged widely. Some suggested an ECP threshold as low as 250, some opposed any thresholds, at least one suggested templates be protected by default, and most were silent on the threshold but supported the principle to allow the use of ECP. Later in the discussion, the proposer and another editor both stated that the question under discussion was not the numerical thresholds but whether ECP should be allowed at all. So there's really wide latitude here that the number range in the guideline doesn't capture, and a lot that the community wants us to keep in mind when deciding what protection level fits the risk. — Wug·a·po·des 03:16, 26 October 2026 (UTC)Reply
I'm open to it, but I'm going to need you to explain the risks versus benefits to me.
That template would usually be protected so that people who are told to "use the {{Help me}} template" don't accidentally edit the template page itself. But ECP is more than enough for that. It's also never used on mainspace and is usually replaced with {{help me-helped}} within one day, so its usage in page histories is
The benefit is that experienced editors like myself, or those who often respond to helpme requests, can freely and gradually improve the template based on their experience. For example, if the people using this template are confused by the way it's worded, the wording can be clarified. FaviFake (talk) 10:49, 27 October 2026 (UTC)Reply
Based on your description, do you think semi-protection would be more appropriate than ECP? How likely is it that someone autoconfirmed edits this template by accident? {{Admin help}} for example is semi-protected, but I don't know if that's used by newbies more or less than {{help me}}. Also pinging Primefac whose opinion I trust and who happens to be actively engaged on its talk page. — Wug·a·po·des 20:10, 28 October 2026 (UTC)Reply
I have no opinion on whether semi-protection would be more appropriate than ECP.
I do think {{admin help}} should remain semi protected as it's not used as much as {{help me}}. FaviFake (talk) 20:12, 28 October 2026 (UTC)Reply
I am mildly opposed to dropping protection; {{help me-helped}} has 16k transclusions, which means that as an aggregate {{help me}} has at least that many (noting direct removals and conversions to the other "help closed" templates would add to the total). As mentioned the template is used by brand-new users, so any vandalism would be impacting our most inexperienced colleagues. ECP for templates is useful when a template needs to be edited often and there are enough eyes to merit a drop in protection, otherwise I don't think it's necessary.
I also find the argument of "well I might want to muck about with it from time to time" somewhat concerning; there have been two enacted TPERs in the last six years, and all vandalism to the page (prior to the protection being added) was by users who were autoconfirmed. The page apparently thus doesn't need to be edited and lowering protection would open the door to vandalism. (please do not ping on reply) Primefac (talk) 14:30, 31 October 2026 (UTC)Reply

Feedback request: All RFCs request for comment

[edit]

Your feedback is requested at Talk:Stranger Than Heaven on a "All RFCs" request for comment. Thank you for helping out!
You were randomly selected to receive this invitation from the list of Feedback Request Service subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name.

SodiumBot (botop|talk|contribs) 05:30, 27 October 2026 (UTC)Reply

Notification of administrators without tools

[edit]
Greetings, Wugapodes. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
  • Thank you for supporting this effort. Your contributions are an integral part of overall success, and an example for others to follow.
  • To stop receiving these notifications, remove your name from the list.

TolBot (talk) 21:01, 29 October 2026 (UTC)Reply

Notification of administrators without tools

[edit]
Greetings, Wugapodes. You are receiving this notification because you've agreed to consider endorsing prospective admin candidates identified by the process outlined at Administrators without tools. Recently, the following editor(s) received this distinction and the associated endearing title:
  • Thank you for supporting this effort. Your contributions are an integral part of overall success, and an example for others to follow.
  • To stop receiving these notifications, remove your name from the list.

TolBot (talk) 21:00, 31 October 2026 (UTC)Reply

WikiCup 2026 November newsletter

[edit]

The 2026 WikiCup has come to an end. Our top scorers, based on the tournament point rankings (which can be seen here), are:

  1. Generalissima (submissions) with 1077 tournament points, will receive the 1st place award.
  2. Ohio Bgsu98 (submissions) with 1046 tournament points, will receive the 2nd place award.
  3. MCE89 (submissions) with 762 tournament points, will receive the 3rd place award.
  4. A.Cython (submissions) with 606' tournament points
  5. Vestrian24Bio (submissions) with 537 tournament points
  6. Reconrabbit (submissions) with 349 tournament points
  7. Delaware BeanieFan11 (submissions) with 297 tournament points
  8. Palestine Arconning (submissions) with 183 tournament points

Our three high scorers in the final round, who each got over 1,000 points, happen to all be among the top 8 as well:

  1. Generalissima (submissions) with 2846 round points from 40 good articles, 4 pieces of featured content (including 2 featured articles), 11 DYK articles, and various reviews.
  2. Ohio Bgsu98 (submissions) with 2603 round points from 43 good articles, 5 pieces of featured content (1 featured article and 4 featuyred lists), and various reviews.
  3. Vestrian24Bio (submissions) with 1141 round points from 20 good articles, a good topic, a featured list, and 30 good article reviews.

The final round was very productive, and contestants had 29 featured articles, 8 featured lists, 1 featured picture, 150 good articles, 43 good topic articles, 189 article reviews, 28 did you know articles, and 4 in the news articles. Altogether, Wikipedia has benefited greatly from the activities of WikiCup competitors all through the contest. Well done everyone!

The top eight scorers will receive awards shortly. The following special awards will be made, based on high performance in particular areas of content creation. These prizes are awarded to the competitor who scored the highest in any particular field over the course of the competition.

  • Generalissima (submissions) wins the following prizes:
    • The featured article prize, for 12 featured articles.
    • The featured picture prize, for submitting the only featured picture for the second year in a row.
    • The good article prize, for 82 good articles.
  • Ohio Bgsu98 (submissions) wins the following prizes:
    • The featured list prize, for 21 featured lists.
    • The featured content reviewer prize, for 72 featured article reviews.
  • Vestrian24Bio (submissions) wins the following prizes:
    • The featured topic prize, for 8 pages in featured topics.
    • The good topic prize, for 26 pages in good topics.
    • The good article reviewer prize, for 84 good article reviews.
  • Sweden BabbaQ (submissions) wins the ITN prize, for 9 ITN pages.
  • Delaware BeanieFan11 (submissions) wins the DYK prize, for 47 DYK pages.

A special mention also goes to these users who scored the highest in a particular category in a single round:

Next year's competition will begin on 1 January. You are invited to sign up to participate. We are also looking for an experienced editor to help write the bimonthly newsletter. If you would like to help write next year's newsletters, please contact Epicgenius at his talk page.

The WikiCup is open to all Wikipedians, both novices and experienced editors, and we hope to see you all in the 2027 competition. Until then, it only remains to once again congratulate our worthy winners, and thank all participants for their involvement!

On behalf of the judges, Cwmhiraeth (talk · contribs · email), Epicgenius (talk · contribs · email), Frostly (talk · contribs · email), Guerillero (talk · contribs · email) and Lee Vilenski (talk · contribs · email):

MediaWiki message delivery (talk) 01:13, 1 November 2026 (UTC)Reply

WikiCup 2026 November newsletter (update)

[edit]

In our November 2026 newsletter, there was a mistake in calculating the final tournament point rankings (which have been updated here). We regret the error.

  1. Generalissima (submissions) with 1461 tournament points, will receive the 1st place award.
  2. Ohio Bgsu98 (submissions) with 1302 tournament points, will receive the 2nd place award.
  3. Vestrian24Bio (submissions) with 793 tournament points, will receive the 3rd place award.
  4. MCE89 (submissions) with 762 tournament points
  5. A.Cython (submissions) with 606 tournament points
  6. Delaware BeanieFan11 (submissions) with 425 tournament points
  7. Reconrabbit (submissions) with 349 tournament points
  8. Palestine Arconning (submissions) with 183 tournament points

On behalf of the judges, Cwmhiraeth (talk · contribs · email), Epicgenius (talk · contribs · email), Frostly (talk · contribs · email), Guerillero (talk · contribs · email) and Lee Vilenski (talk · contribs · email):

MediaWiki message delivery (talk) 01:43, 1 November 2026 (UTC)Reply

The Signpost: 1 November 2026

[edit]
  • By the numbers: Wikipedian Nobel Prize 2026
    Which language versions of Wikipedia had biographies of laureates before Nobel announcements?
  • On the bright side: Gone fishing
    Touring Thailand, exploring iridescence, and translating prairie dog.

Administrators' newsletter – November 2026

[edit]

News and updates for administrators from the past month (October 2026).

Administrator changes

added
readded
removed

Guideline and policy news

  • Following an RfC, election to ArbCom now requires at least 60% support. Successful candidates normally serve two-year terms, with one-year terms retained for filling vacancies. Proposals to change the election rules may now be added throughout the year and discussed on the talk page; formal discussion remains in September.
  • Following an RfC, first-time reviewers’ reviews require an experienced reviewer’s check, and GA requirements now include alt text and accessible tables. Featured articles may receive GA status during removal discussions if they meet GA criteria. Backlog drives will run every five months, with a points leaderboard and awards for the top five participants.

Miscellaneous