Moist towelett

File:Newton Ennis Morton.jpg

Hi, I'm RonBot, a script that checks new non-free file uploads. I have found that the subject image that you recently uploaded was more than 5% in excess of the Non-free content guideline size of 100,000 pixels. I have tagged the image for a standard reduction, which (for jpg/gif/png/svg files) normally happens within a day. Please check the reduced image, and make sure that the image is not excessively corrupted. Other files will be added to Category:Wikipedia non-free file size reduction requests for manual processing. There is a full seven-day period before the original oversized image will be hidden; during that time you might want to consider editing the original image yourself (perhaps an initial crop to allow a smaller reduction or none at all). A formula for calculation the desired size can be found at WP:Image resolution, along with instructions on how to tag the image in the rare cases that it requires an oversized image (typically about 0.2% of non-free uploads are tagged as necessarily oversized). Please contact the bot owner if you have any questions, or you can ask them at Wikipedia talk:Non-free content. See User:RonBot for info on how to not get these messages. RonBot (talk) 18:05, 4 December 2018 (UTC)

"did not appear constructive"

This edit of yours puzzles me. Which edit(s) "did not appear constructive"? -- Hoary (talk) 13:59, 5 December 2018 (UTC)

Bots Newsletter, August 2019

Bots Newsletter, August 2019

Greetings!

Here is the 7th issue of the Bots Newsletter, a lot happened since last year's newsletter! You can subscribe/unsubscribe from future newsletters by adding/removing your name from this list.

Highlights for this newsletter include:

ARBCOM

• Nothing of note happened. Just like we like it.

BAG

• Several (1 + 12 = 13) users have been retired/resigned from the BAG due to inactivity, per our new activity requirements (discussion).

BAG members are expected to be active on Wikipedia to have their finger on the pulse of the community. After two years without any bot-related activity (such as posting on bot-related pages, posting on a bot's talk page, or operating a bot), BAG members will be retired from BAG following a one-week notice. Retired members can re-apply for BAG membership as normal if they wish to rejoin the BAG.

• Two BAG members retired
  • Madman (talk · contribs) retired.
  • BU Rob13 (talk · contribs) vanished and retired.
• Three new BAG members have been voted in, welcome to the BAG!
  • Primefac (talk · contribs) joined on 2018-12-12 (RfBAG). Primefac operates PrimeBOT (talk · contribs) which does a plethora of tasks.
  • TheSandDoctor (talk · contribs) joined on 2019-01-21 (RfBAG). TheSandDoctor operates several bots including DeprecatedFixerBot (talk · contribs).
  • Enterprisey (talk · contribs) joined on 2019-08-07 (RfBAG). Enterprisey operates EnterpriseyBot (talk · contribs), which does a plethora of tasks, RemindMeBot (talk · contribs) which posts reminders, and codes several scripts.

We thank former members for their service and wish Madman a happy retirement. We note that Madman and BU Rob13 were not inactive and could resume their BAG positions if they so wished, should their retirements happens to be temporary.

BOTDICT

Two new entries feature in the bots dictionary

• Editor-hostile wikitext – describes wikitext structuring that is editor hostile, even if it renders correctly
• Spectrum of usefulness – describes how tasks are deemed useful or not

BOTPOL

• Activity requirements: BAG members now have an activity requirement. The requirements are very light, one only needs to be involved in a bot-related area at some point within the last two years. For purpose of meeting these requirements, discussing a bot-related matter anywhere on Wikipedia counts, as does operating a bot (RFC).
• Copyvio flag: Bot accounts may be additionally marked by a bureaucrat upon BAG request as being in the "copyviobot" user group on Wikipedia. This flag allows using the API to add metadata to edits for use in the New pages feed (discussion). There is currently 1 bot using this functionality.
• Mass creation: The restriction on mass-creation (semi-automated or automated) was extended from articles, to all content-pages. There are subtleties, but content here broadly means whatever a reader could land on when browsing the mainspace in normal circumstances (e.g. Mainspace, Books, most Categories, Portals, ...). There is also a warning that WP:MEATBOT still applies in other areas (e.g. Redirects, Wikipedia namespace, Help, maintenance categories, ...) not explicitely covered by WP:MASSCREATION.

BOTREQs and BRFAs

As of writing, we have...

• 20 active BOTREQs, please help if you can!
• 14 open BRFAs and 1 BRFA in need of BAG attention (see live status).
• In 2018, 96 bot task were approved. An AWB search shows approximately 29 were withdrawn/expired, and 6 were denied.
• Since the start of 2019, 97 bot task were approved. Logs show 15 were withdrawn/expired, and 15 were denied.
• 10 inactive bots have been deflagged (see discussion). 5 other bots have been deflagged per operator requests or similar (see discussion).

New things

• All bot-related discussion pages now have a centralized and searchable archive box (see discussion). Discussions are searchable per noticeboard, or globally.
• {{Bot}} now supports |status=expired (see discussion). This led to the deletion of Category:Indefinitely blocked Wikipedia bots as useless (see discussion).
• WP:BOTREQ now mentions WP:SCRIPTREQ and WP:AWBTASKS as alternatives to bot requests.
• The bot creation guide now mentions bot flags, and two new languages Awk and MATLAB. Other minor tweaks have been made.
• AAlertBot has received major code updates. In particular, WP:AALERTS will now report splits, mergers, and AFC submissions.
• Citation bot has received several updates (User talk:Citation bot/Archive 10/11/12/13/14/15/16/17). In particular, the bot stopped the automated removal of |publisher= from {{cite journal}}, and stopped the automated addition of CiteSeerX links, and now uses OAuth to authenticate those who make requests of the bot.

Other discussions

These are some of the discussions that happened / are still happening since the last Bots Newsletter. Many are stale, but some are still active.

• Wikipedia:Bots/Noticeboard/Archive 12#Adminbots requests page
• Wikipedia:Bots/Noticeboard/Archive 12#Double-redirect tagging (2019)
• Wikipedia:Bots/Noticeboard/Archive 12#Long and Winding Road to Parsoid
• Wikipedia:Bots/Noticeboard/Archive 13#Bot-like user scripts
• Wikipedia:Bots/Noticeboard/Archive 13#WP:URLREQ
• Wikipedia:Bots/Noticeboard/Archive 13#Wikipedia:Bots/Status
• Wikipedia talk:Bot Approvals Group#Minimum edits
• Wikipedia talk:Bot policy#Minor update to WP:BOTISSUE
• Wikipedia talk:Bot policy#Semi-automated Portal creation
• Wikipedia talk:Bot policy#Clarification on "Bots operated by multiple users"
• Wikipedia talk:Bot policy#Bots triggered by multiple users
• Wikipedia talk:Bots#How to use Special:ApiFeatureUsage

See also the latest discussions at the bot noticeboard.

Thank you! edited by: Headbomb 17:24, 7 August 2019 (UTC)

---

(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

ArbCom 2019 election voter message

Hello! Voting in the 2019 Arbitration Committee elections is now open until 23:59 on Monday, 2 December 2019. 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 2019 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) 00:18, 19 November 2019 (UTC)

Disambiguation link notification for May 28

Hi. Thank you for your recent edits. An automated process has detected that when you recently edited Simone Niggli-Luder, you added a link pointing to the disambiguation page Burgdorf (check to confirm | fix with Dab solver). Such links are usually incorrect, since a disambiguation page is merely a list of unrelated topics with similar titles. (Read the FAQ • Join us at the DPL WikiProject.)

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:35, 28 May 2020 (UTC)

File:Rick and Morty Pilot.jpg listed for discussion

A file that you uploaded or altered, File:Rick and Morty Pilot.jpg, has been listed at Wikipedia:Files for discussion. Please see the discussion to see why it has been listed (you may have to search for the title of the image to find its entry). Feel free to add your opinion on the matter below the nomination. Thank you. ―Justin (koavf)❤T☮C☺M☯ 08:15, 30 May 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)

Bots Newsletter, December 2021

Bots Newsletter, December 2021

BRFA activity by month

Welcome to the eighth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Maintainers disappeared to parts unknown... bots awakening from the slumber of æons... hundreds of thousands of short descriptions... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.

Our last issue was in August 2019, so there's quite a bit of catching up to do. Due to the vast quantity of things that have happened, the next few issues will only cover a few months at a time. This month, we'll go from September 2019 through the end of the year. I won't bore you with further introductions — instead, I'll bore you with a newsletter about bots.

Overall

• Between September and December 2019, there were 33 BRFAs. Of these, Y 25 were approved, and 8 were unsuccessful (N2 3 denied, ? 3 withdrawn, and 2 expired).

September 2019

Look! It's moving. It's alive. It's alive... It's alive, it's moving, it's alive, it's alive, it's alive, it's alive, IT'S ALIVE!

• Y Monkbot 16, DannyS712 bot 60, Ahechtbot 6, PearBOT 3, Qbugbot 3 · N2 DannyS712 bot 5, PkbwcgsBot 24 · ? DannyS712 bot 61, TheSandBot 4
• TParis goes away, UTRSBot goes kaput: Beeblebrox noted that the bot for maintaining on-wiki records of UTRS appeals stopped working a while ago. TParis, the semi-retired user who had previously run it, said they were "unlikely to return to actively editing Wikipedia", and the bot had been vanquished by trolls submitting bogus UTRS requests on behalf of real blocked users. While OAuth was a potential fix, neither maintainer had time to implement it. TParis offered to access to the UTRS WMFLabs account to any admin identified with the WMF: "I miss you guys a whole lot [...] but I've also moved on with my life. Good luck, let me know how I can help". Ultimately, SQL ended up in charge. Some progress was made, and the bot continued to work another couple months — but as of press time, UTRSBot has not edited since November 2019.
• Article-measuring contest resumed: The list of Wikipedians by article count, which had lain dead for several years, was triumphantly resurrected by GreenC following a bot request.

October 2019

• Y OAbot 3, DannyS712 bot 47, Pathbot 2, PearBOT 2, DannyS712 bot 59, DannyS712 bot 62, HasteurBot 14, PearBOT 4, WOSlinkerBot 4, MilHistBot 5
• Curb Safe Charmer adopts reFill: TAnthony pointed out that reFill 2's bug reports were going unanswered; creator Zhaofeng Li had retired from Wikipedia, and a maintainer was needed. As of June 2021, Curb Safe Charmer had taken up the mantle, saying: "Not that I have all the skills needed but better me than nobody! 'Maintainer' might be too strong a term though. Volunteers welcome!"
  

November 2019

Now you're thinking with portals.

• Y BHGbot 4, YiFeiBot 2, DannyS712 bot III 64 · ? PearBOT
• Old bots do new tricks: DannyS712 bot III 64 prowled redirects, YiFeiBot 2 archived GoCE requests, and BHGbot 4 removed links to portals deleted at MfD (until its authorization was revoked in January at operator BrownHairedGirl's request).

December 2019

• Y DemonDays64 Bot, DannyS712 bot III 66, Bot1058 6, Monkbot 15, MilHistBot 6, PearBOT 5, DannyS712 bot IV 65 · N2 SportsStatsBot · Xinbenlv bot, SteveBot 8
• Redirects to be autopatrolled: A RfC took place at WP:NPP, closing with unanimous consensus that new redirects should be automatically marked as patrolled by bot. DannyS712 wasted no time, and submitted DannyS712 bot III 66 the next day; it passed two days after that.
• 200,000 bios get short descs: Along a similar vein, Bot1058 6 was approved to remove disambiguation pages from Category:Monitored short pages and a new bot (DemonDays64 Bot) changed lots of http links to https using JavaScript Wiki Browser. One particularly neat task, PearBOT 5, automatically generated short descriptions for more than 200,000 biographies.

In the next issue of Bots Newsletter:
What's next for our intrepid band of coders, maintainers and approvers?

• What happens when two bots want to clerk the same page?
• What happens when an adminbot goes hog wild?
• Will reFill ever get fixed?
• What's up with ListeriaBot, anyway?
• Python 3.4 deprecation? In my PyWikiBot? (It's more likely than you think!)

These questions will be answered — and new questions raised — by the January 2022 Bots Newsletter. Tune in, or miss out!

Signing off... jp×g 04:29, 10 December 2021 (UTC)

---

(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Bots Newsletter, January 2022

Bots Newsletter, January 2022

BRFA activity by month

Welcome to the ninth issue of the English Wikipedia's Bots Newsletter, your source for all things bot. Vicious bot-on-bot edit warring... superseded tasks... policy proposals... these stories, and more, are brought to you by Wikipedia's most distinguished newsletter about bots.

After a long hiatus between August 2019 and December 2021, there's quite a bit of ground to cover. Due to the vastness, I decided in December to split the coverage up into a few installments that covered six months each. Some people thought this was a good idea, since covering an entire year in a single issue would make it unmanageably large. Others thought this was stupid, since they were getting talk page messages about crap from almost three years ago. Ultimately, the question of whether each issue covers six months or a year is only relevant for a couple more of them, and then the problem will be behind us forever.

Of course, you can also look on the bright side – we are making progress, and this issue will only be about crap from almost two years ago. Today we will pick up where we left off in December, and go through the first half of 2020.

Overall
In the first half of 2020, there were 71 BRFAs. Of these, Y 59 were approved, and 12 were unsuccessful (with N2 8 denied, ? 2 withdrawn, and 2 expired).

January 2020

Yeah, you're not gonna be able to get away with this anymore.

• Y ST47Bot, Seppi333Bot, Qbugbot 4 · N2 PkbwcgsBot 25, PkbwcgsBot 26
• A new Pywikibot release dropped support for Python 3.4, and it was expected that support for Python 2.7 would be removed in coming updates. Toolforge itself planned to drop Python 2 support in 2022.
• Two new bots dropped in January 2020: ST47Bot, the successor to STBot, and Seppi333Bot, whose task was to perform a weekly update of four "massive" wikitables for WikiProject Molecular Biology.
• Cydebot, an adminbot operated by Cyde since 2006, was blocked after going berserk on categories that hadn't yet been CfD'd.

February 2020

Speaking of WikiProject Molecular Biology, Listeria went wild in February

• Y AnomieBOT 78, Cewbot 2, DannyS712 bot 67, DannyS712 bot III 63, PearBOT 6, DemonDays64 Bot 2 · N2 PearBOT
• On February 1, some concerns were raised about ListeriaBot performing "nonsense" edits. Semi-active operator Magnus Manske (who originally coded the Phase II software|precursor of MediaWiki) was pinged. Meanwhile, the bot was temporarily blocked for several hours until the issue was diagnosed and resolved.
• On February 18, ST47Bot got into a tussle with Amalthea (bot), and had to be partially-blocked from Wikipedia:Sockpuppet investigations/Cases/Overview.

March 2020

• Y MajavahBot, SDZeroBot, TheSandBot 6, TheSandBot 7, Bitbotje, FACBot 6, TheSandBot 8, Qbugbot 5, Cewbot 3, SDZeroBot 2, PrimeBOT 31, WikiCleanerBot 12 · AntiCompositeBot
• In March, a long discussion was started at Wikipedia talk:Bot policy by Skdb about the troubling trend of bots "expiring" without explanation after their owners became inactive. This can happen for a variety of reasons -- API changes break code, hosting providers' software updates break code, hosting accounts lapse, software changes make bots' edits unnecessary, and policy changes make bots' edits unwanted. The most promising solution seemed to be Toolforge hosting (although it has some problems of its own, like the occasional necessity of refactoring code).
• Some of the twelve bot tasks approved this month were TheSandBot 6 (removing blocked users from Category:Wikipedia usernames with possible policy issues), and TheSandBot 7 (removing unblocked users from Category:Wikipedians who are indefinitely blocked for promotional user names). SDZeroBot 2 was approved to refine geographic stub tags. New bots approved this month were MajavahBot (to patrol WP:EFFPR), SDZeroBot (to merge stub tags), and Bitbotje (fixing DISPLAYTITLE modifications, DEFAULTSORT errors and broken behavior switches in draftspace).

April 2020

Listeria being examined

• Y TheSandBot 9, BHGbot 5, DannyS712 bot 69, SDZeroBot 3, ST47ProxyBot, WugBot 4, SDZeroBot 4, DatBot 10, WikiCleanerBot 11, WikiCleanerBot 13, WikiCleanerBot 14, AntiCompositeBot 2, Cewbot 4 · N2 DaedanBot 1 · Creffbot
• A discussion on the bot noticeboard, "Re-examination of ListeriaBot", was started by Barkeep49, who pointed out repeated operation outside the scope of its BRFA (i.e. editing pages in mainspace, and adding non-free images to others). Some said it was doing good work, and others said it was operating beyond its remit. It was blocked on April 10; the next day it was unblocked, reblocked from article space, reblocked "for specified non-editing actions", unblocked, and indeffed. The next week, several safeguards were implemented in its code by Magnus; the bot was allowed to roam free once more on April 18.
• ST47ProxyBot joined the stable in April, after a BRFA started in December was finally completed. As an adminbot, it was authorized to block IP addresses belonging to open proxies, public VPN services, and web hosts. New tasks approved for existing bots included BHGbot 5 (diffusing categories), TheSandBot 9 (taking over some tasks from the inactive RonBot), and WugBot 4 (updating data at {{Interactive COVID-19 maps}}). Also, DatBot 10 was approved to scale down non-free SVGs — I didn't even know that was a thing.
• A discussion at Wikipedia talk:Bot policy was started by Thryduulf about whether WP:BOTCOMM should explicitly specify that bot operators must be responsive to concerns raised on English Wikipedia specifically (as opposed to Phabricator, SourceForge, Toolforge, et cetera). Eventually, the policy was amended to its current form:

Issues and enquiries are typically expected to be handled on the English Wikipedia. Pages reachable via unified login, like a talk page at Commons or at Italian Wikipedia could also be acceptable [...] External sites like Phabricator or GitHub (which require separate registration or do not allow for IP comments) and email (which can compromise anonymity) can supplement on-wiki communication, but do not replace it.

May 2020

We heard you like bots, so we made a bot that reports the status of your bots, so now you can use bots while you use bots

• Y MajavahBot 3, DannyS712 bot 70, CitationCleanerBot 5, Dreamy Jazz Bot 4, QEDKbot, William Avery Bot 2, DannyS712 bot 68, PrimeBOT 32, TheSandBot 10, Bot1058 7, BHGbot 6, EaglesBot 2, Cewbot 5, WikiCleanerBot 17 · N2 MDanielsBot, PhuzBot 3, Gedimon · ? PearBOT 7
• MajavahBot 3, an impressively meta bot task, was approved this month for maintaining a list of bots running on the English Wikipedia. The page, located at User:MajavahBot/Bot status report, is updated every 24 hours; it contains a list of all accounts with the bot flag, as well as their operator, edit count, last activity date, last edit date, last logged action date, user groups and block status.
• Other approvals for this month were William Avery Bot 2 (processing redirects in {{R from scientific name}}), DannyS712 bot 68 (allowing users to schedule bot reminders for themselves), TheSandBot 10 (removing blocked/locked users from Category:User talk pages with conflict of interest notices), Bot1058 7 (updating Wikipedia:Requested moves/Technical requests/Permalink), Dreamy Jazz Bot 4 (adding {{WikiProject Biography|living=no}} to talk pages where their associated article is in a year of death category), and QEDKbot (deleting and nominating empty categories).
• General syntax fixing tasks were approved for DannyS712 bot 70, CitationCleanerBot 5, PrimeBOT 32, BHGbot 6, Cewbot 5, and EaglesBot 2, as well as WikiCleanerBot 15, 16, and 17.
• Seven bots who fell below activity requirements (with neither the bots nor their operators having any edits or logged actions in two years) had their bot flags removed. They were NekoBot, Robert SkyBot, DASHBotAV, VoxelBot, JackieBot, ReferenceBot, and CensusBot.
• On May 12, EmausBot was blocked.

June 2020

A partial block averted at the eleventh hour for the robot that makes Legos

• Y QEDKbot 2, AnomieBOT 79, WOSlinkerBot 6, Yapperbot 2, Yapperbot, AnomieBOT 80, Dreamy Jazz Bot 5, WikiCleanerBot 18, HasteurBot 15, MusikBot II 4, NoSandboxesHere · N2 RedWarn · ? Seppi333Bot 2
• In July 2017, Headbomb made a proposal that a section of the Wikipedia:Dashboard be devoted to bots and technical issues. In November 2019, Lua code was written superseding Legobot's tasks on that page, and operator Legoktm was asked to stop them so that the new code could be deployed. After no response to pings, a partial-block of Legobot for the dashboard was proposed. Some months later, on June 16, Headbomb said: "A full block serves nothing. A partial block solves all current issues [...] Just fucking do it. It's been 3 years now." The next day, however, Legoktm disabled the task, and the dashboard was successfully refactored.
• On June 7, RexxS blocked Citation bot for disruptive editing, saying it was "still removing links after request to stop". A couple weeks later, a discussion on the bots noticeboard was opened, saying "it is a widely-used and useful bot, but it has one of the longest block logs for any recently-operating bot on Wikipedia". While its last BRFA approval was in 2011, its code and functionality had changed dramatically since then, and AntiCompositeNumber requested that BAG require a new BRFA. Maintainer AManWithNoPlan responded that most blocks were from years ago (when it lacked a proper test suite), and problems since then had mostly been one-off errors (like a June 2019 incident in which a LTA had "weaponized" the bot to harass editors).
• David Tornheim opened a discussion about whether bots based on closed-source code should be permitted, and proposed that they not. He cited a recent case in which a maintainer had said "I can only suppose that the code that is available on GitHub is not the actual code that was running on [the bot]". Some disagreed: Naypta said that "I like free software as much as the next person, and I strongly believe that bot operators should make their bot code public, but I don't think it should be that they must do so".
• Two new bots had their first BRFAs approved: Yapperbot, to replace Legobot for handling the Feedback Request Service, and NoSandboxesHere, to remove {{user sandbox}} from articles in draftspace using Category:Non-userspace pages using User sandbox.

Conclusion

• What's next for our intrepid band of coders, maintainers and approvers?

• Will Citation bot ever be set free to roam the project?
• What's the deal with all those book links that InternetArchiveBot is adding to articles?
• Should we keep using Gerrit for MediaWiki?
• What if we had a day for bots to make cosmetic edits?

These questions will be answered — and new questions raised — by the February 2022 Bots Newsletter. Tune in, or miss out!

Signing off... jp×g 23:22, 31 January 2022 (UTC)

---

(You can subscribe or unsubscribe from future newsletters by adding or removing your name from this list.)

Nomination for deletion of Template:Veliko Tarnovo University

Template:Veliko Tarnovo University has been nominated for deletion. You are invited to comment on the discussion at the entry on the Templates for discussion page. Frietjes (talk) 16:59, 9 January 2023 (UTC)

Nomination of The Glacier Trust for deletion

A discussion is taking place as to whether the article The Glacier Trust, to which you have significantly contributed, is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or if it should be deleted.

The discussion will take place at Wikipedia:Articles for deletion/The Glacier Trust until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.

To customise your preferences for automated AfD notifications for articles to which you've significantly contributed (or to opt-out entirely), please visit the configuration page. Delivered by SDZeroBot (talk) 01:01, 22 February 2023 (UTC)

Orphaned non-free image File:The Glacier Trust Logo 1.png

⚠

Thanks for uploading File:The Glacier Trust Logo 1.png. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. 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 Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 03:43, 4 March 2023 (UTC)

"Career Day (That '70s Show Episode" listed at Redirects for discussion

The redirect Career Day (That '70s Show Episode has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 January 20 § Career Day (That '70s Show Episode until a consensus is reached. Utopes _{(talk / cont)} 01:32, 20 January 2024 (UTC)

one of the most creative name ever

Moist towelett () — Preceding unsigned comment added by 186.69.24.72 (talk) 23:46, 10 March 2024 (UTC)

A barnstar

Random Acts of Kindness Barnstar

Moist towelett (Random Acts of Kindness Barnstar)