Paine Ellsworth

Joined 27 February 2009

This is an old revision of this page, as edited by Aron Manning (talk | contribs) at 19:38, 16 June 2019 (→‎Close notes – 737 Max: Maybe there... sorry for the... disturbance :-)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.


Latest comment: 5 years ago by Aron Manning in topic Close notes – 737 Max
head of giraffe
'Wikipedia is a community effort of staggering proportions!'
'to help us keep our minds sharp!'


Newly registered?


Discussions and notifications...collapsed

Wikipedia:WikiProject Portals update #029, 13 Feb 2019

Where we are at:

Single-page portals: 4,704
Total portals: 5,705

The Ref desks survived the proposal to shut them down

You might be familiar with the Ref desks, by their link on every new portal. They are a place you can go to ask volunteers almost any knowledge-related question, and have been a feature of Wikipedia since August of 2005 (or perhaps earlier). They were linked to from portals in an effort to improve their visibility, and to provide a bridge from the encyclopedia proper to project space (the Wikipedia community).

Well, somebody proposed that we get rid of them, and the community decided that that was not going to happen. Thank you for defending the Ref desks!

Here's a link to the dramatic discussion:

https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(proposals)/Indefinitely_semiprotecting_the_refdesk#Proposal_II:_Shut_down_the_Ref_Desks

The cleanup after sockpuppet Emoteplump continues...

The wake of disruption left by Emoteplump and the admins who reverted many (but not all) of his/her edits is still undergoing cleanup. We could use all the help we can get on this task...

Almost all of the speedy deleted portals have been rebuilt from scratch.

For the portals he/she restarted (many of which were done mistakenly, overwriting restarts and further development that had already been done), and/or tagged as the maintainer, see https://en.wikipedia.org/w/index.php?title=User:Emoteplump&oldid=881568794#Additional_Portals_under_my_watch

10,000 portals, here we come...

We're at 5,705 portals and counting.

New portals since issue #28

  1. Portal:Abitibi-Témiscamingue
  2. Portal:Ahold Delhaize
  3. Portal:AKB48
  4. Portal:Åland Islands
  5. Portal:Alaska Airlines
  6. Portal:Albanian Civil War
  7. Portal:Albertsons
  8. Portal:Alevism
  9. Portal:All in the Family
  10. Portal:Alternative metal
  11. Portal:Ambient music
  12. Portal:Ancient Near East mythology
  13. Portal:Ancient Roman religion
  14. Portal:Andrew Cuomo
  15. Portal:Anti-consumerism
  16. Portal:Antimatter
  17. Portal:Arameans
  18. Portal:Arianism
  19. Portal:Australian Crawl
  20. Portal:Bali
  21. Portal:Banten
  22. Portal:Bengkulu
  23. Portal:Black Lives Matter
  24. Portal:Bluegrass music
  25. Portal:Bonnie Tyler
  26. Portal:Breakbeat
  27. Portal:Calypso music
  28. Portal:Cambridgeshire
  29. Portal:Camila Cabello
  30. Portal:Capcom
  31. Portal:Capsicum
  32. Portal:Celtic music
  33. Portal:Central American music
  34. Portal:Central Java
  35. Portal:Central Kalimantan
  36. Portal:Central Sulawesi
  37. Portal:Chanel
  38. Portal:Cinema of Australia
  39. Portal:Cognitive psychology
  40. Portal:Communication studies
  41. Portal:Conservatism in the United States
  42. Portal:Cortina d'Ampezzo
  43. Portal:Cross-Strait relations
  44. Portal:Cryptozoology
  45. Portal:Danish folk music
  46. Portal:Disco
  47. Portal:Dyslexia
  48. Portal:East Java
  49. Portal:East Kalimantan
  50. Portal:East Nusa Tenggara
  51. Portal:Easy listening
  52. Portal:Ed Sheeran
  53. Portal:Ehime
  54. Portal:Electricity
  55. Portal:Electronica
  56. Portal:Electronic rock
  57. Portal:English folk music
  58. Portal:Environmental technology
  59. Portal:Experimental music
  60. Portal:Extreme metal
  61. Portal:Fall Out Boy
  62. Portal:Finnish Defence Forces
  63. Portal:Finnish folk music
  64. Portal:Football in Croatia
  65. Portal:Football in Jordan
  66. Portal:Funk
  67. Portal:Gamelan
  68. Portal:General Mills
  69. Portal:Germanic languages
  70. Portal:German language
  71. Portal:Government of Canada
  72. Portal:Government of Hong Kong
  73. Portal:Government of Indonesia
  74. Portal:Government of Ireland
  75. Portal:Government of Malaysia
  76. Portal:Government of Russia
  77. Portal:Government of Singapore
  78. Portal:Government of Spain
  79. Portal:Government of Thailand
  80. Portal:Grapes
  81. Portal:Green Party of the United States
  82. Portal:Grinspoon
  83. Portal:Gwen Stefani
  84. Portal:Hardcore punk
  85. Portal:Hardcore techno
  86. Portal:Haskell (programming language)
  87. Portal:History of art
  88. Portal:History of North America
  89. Portal:History of Thailand
  90. Portal:Hollywood
  91. Portal:Hotels
  92. Portal:House music
  93. Portal:Hungarian folk music
  94. Portal:Hunters & Collectors
  95. Portal:Hydrogen
  96. Portal:Icelandic folk music
  97. Portal:Indigenous music of North America
  98. Portal:Insomniac Games
  99. Portal:International field hockey
  100. Portal:International trade
  101. Portal:Iranian music
  102. Portal:Islamophobia
  103. Portal:Jambi
  104. Portal:Jet engines
  105. Portal:Jordin Sparks
  106. Portal:Julius Caesar
  107. Portal:Kannur
  108. Portal:Kansas City Spurs
  109. Portal:Kelly Rowland
  110. Portal:Kirby
  111. Portal:Kraft Heinz
  112. Portal:Krasnoyarsk Krai
  113. Portal:Kroger
  114. Portal:Kuala Lumpur
  115. Portal:Lampung
  116. Portal:Larry Kramer
  117. Portal:LeBron James
  118. Portal:Lehigh Valley
  119. Portal:Leicestershire
  120. Portal:Liège
  121. Portal:Liguria
  122. Portal:Los Angeles Aztecs
  123. Portal:Los Angeles Wolves
  124. Portal:Macedonian language
  125. Portal:Magnetism
  126. Portal:Maithripala Sirisena
  127. Portal:Maluku (province)
  128. Portal:Mangoes
  129. Portal:Marco Pierre White
  130. Portal:McLaren
  131. Portal:Menstrual cycle
  132. Portal:Metalcore
  133. Portal:Miami FC
  134. Portal:Microblogging
  135. Portal:Microtonal music
  136. Portal:Midnight Oil
  137. Portal:Minnesota Kicks
  138. Portal:Mission: Impossible
  139. Portal:Modernism (music)
  140. Portal:Moheener Ghoraguli
  141. Portal:Mondelez International
  142. Portal:Music genres
  143. Portal:Music of Bangladesh
  144. Portal:Music of India
  145. Portal:Music of Italy
  146. Portal:Music of Japan
  147. Portal:Music of Korea
  148. Portal:Music of Latin America
  149. Portal:Music of Micronesia
  150. Portal:Music of North Africa
  151. Portal:Music of Pakistan
  152. Portal:Music of Serbia
  153. Portal:Music of the Philippines
  154. Portal:Music of the United States
  155. Portal:Mutations
  156. Portal:National Rugby League
  157. Portal:Neoclassicism (music)
  158. Portal:Netball
  159. Portal:New York City Fire Department
  160. Portal:Nick Jr.
  161. Portal:Nobility
  162. Portal:Nordic countries
  163. Portal:North Africa
  164. Portal:North Kalimantan
  165. Portal:North Maluku
  166. Portal:North Pole
  167. Portal:North Queensland
  168. Portal:North Sulawesi
  169. Portal:North Sumatra
  170. Portal:Norwegian folk music
  171. Portal:Papua (province)
  172. Portal:Peaches
  173. Portal:Politics of Abkhazia
  174. Portal:Politics of Afghanistan
  175. Portal:Politics of Albania
  176. Portal:Politics of Algeria
  177. Portal:Politics of Andorra
  178. Portal:Politics of Angola
  179. Portal:Politics of Antigua and Barbuda
  180. Portal:Politics of Argentina
  181. Portal:Politics of Artsakh
  182. Portal:Politics of Bahrain
  183. Portal:Politics of Bangladesh
  184. Portal:Politics of Bavaria
  185. Portal:Politics of Belarus
  186. Portal:Politics of Belgium
  187. Portal:Politics of Belize
  188. Portal:Politics of Benin
  189. Portal:Politics of Bhutan
  190. Portal:Politics of Bosnia and Herzegovina
  191. Portal:Politics of Botswana
  192. Portal:Politics of Brazil
  193. Portal:Politics of Brunei
  194. Portal:Politics of Bulgaria
  195. Portal:Politics of Burkina Faso
  196. Portal:Politics of Burundi
  197. Portal:Politics of Cambodia
  198. Portal:Politics of Cameroon
  199. Portal:Politics of China
  200. Portal:Politics of São Tomé and Príncipe
  201. Portal:Politics of South Sudan
  202. Portal:Politics of Sudan
  203. Portal:Politics of Tanzania
  204. Portal:Politics of the Republic of the Congo
  205. Portal:Politics of Togo
  206. Portal:Politics of Tunisia
  207. Portal:Politics of Uganda
  208. Portal:Pop rock
  209. Portal:Rap rock
  210. Portal:Ras Al Khaimah
  211. Portal:Riau
  212. Portal:Riau Islands
  213. Portal:Ricky Martin
  214. Portal:Royal Canadian Air Force
  215. Portal:Rutland
  216. Portal:Saxophones
  217. Portal:Semiotics
  218. Portal:Ska
  219. Portal:Soca music
  220. Portal:Soul music
  221. Portal:Sound sculptures
  222. Portal:Southeast Sulawesi
  223. Portal:South Kalimantan
  224. Portal:South Sulawesi
  225. Portal:South Sumatra
  226. Portal:Space: 1999
  227. Portal:Special Region of Yogyakarta
  228. Portal:Swedish folk music
  229. Portal:Tamil language
  230. Portal:Techno
  231. Portal:Terry Brooks
  232. Portal:The Living End
  233. Portal:Thrissur
  234. Portal:Trance music
  235. Portal:Tyrant flycatchers
  236. Portal:Veterinary medicine
  237. Portal:Wayanad
  238. Portal:Welsh folk music
  239. Portal:West Champaran district
  240. Portal:Western dress codes
  241. Portal:West Flanders
  242. Portal:West Java
  243. Portal:West Kalimantan
  244. Portal:West Nusa Tenggara
  245. Portal:West Papua (province)
  246. Portal:West Sulawesi
  247. Portal:West Sumatra
  248. Portal:Wildlife of India
  249. Portal:Wildlife of Nepal
  250. Portal:Windows 10
  251. Portal:Winter War
  252. Portal:Woodpeckers
  253. Portal:Worcestershire
  254. Portal:World economy
  255. Portal:World Ocean
  256. Portal:World Rally Championship
  257. Portal:World views
  258. Portal:XTC
  259. Portal:Yahoo!
  260. Portal:Yoruba people
  261. Portal:You Am I
  262. Portal:Young Wizards
  263. Portal:Yugoslavs

Prior to 2018, for the previous 14 years, portal creation was at about 80 portals per year on average. We did over 3 times that in just the past 9 days. At this rate, we'll hit the 10,000 portal mark in 5 months. But, I'm sure we can do it sooner than that.

What's next for portal pages?

There are 5 drives for portal development:

  1. Create new portals
  2. Expand existing portals, such as with new sections like Recognized content
  3. Convert or restart old-style portals into automated single-page portals
  4. Link to new portals from the encyclopedia
  5. Pageless portals

Let's take a closer look at these...

1: Creating new portals

Portal creation, for subjects that happen to have the necessary support structures already in place, is down to about a minute per portal. The creation part, which is automated, takes about 10 seconds. The other 50 seconds is taken up by manual activities, such as finding candidate subjects, inspecting generated portals, and selecting the portal creation template to be used according to the resources available. Tools are under development to automate these activities as much as possible, to pare portal creation time down even more. Ten seconds each is the goal.

Eventually, we are going to run out of navigation templates to base portals off of. Though there are still thousands to go. But, when they do run out, we'll need an easy way to create more. A nav footer creation script.

Meanwhile, other resources are being explored and developed, such as categories, and methods to harvest the links they contain.

2: Expanding existing portals

The portal collection is growing, not only by the addition of new portals, but by further developing the ones we already have, by...

  • Improving and/or adding search parameters to better power the Did you know and In the news sections.
  • Adding more selected content sections, like Selected biographies.
  • Adding and maintaining Recognized content sections, via JL-Bot.
  • Adding pictures to the image slideshow.
  • Adding panoramic pics.
  • Categorizing portals.

More features will be added as we dream them up and design them. So, don't be shy, make a wish.

3: Converting old portals

By far the hardest and most time-consuming task we have been working on is updating the old portals, the very reason we revamped this WikiProject in the first place.

There are two approaches here:

A) Restart a portal from scratch, using our automated tools. For basic no-frills portals, that works find. But, for more elaborate portals, as that tends to lose content and features, the following approach is being tried...
B) Upgrade a portal section by section, so little to nothing is lost in the process.

4: Linking to new portals

Or "portal deorphanization"...

Dreamy Jazz Bot is purring along.

And a tool in the form of a script is under development for linking to portals at the time they are created, or shortly thereafter.

5...

See below...

New WikiProject for the post-saved-portal phase of operations...

Saved portals, are portals with a saved page.

What is the next stage in the evolutionary progression?

Quantum portals.

What are quantum portals?

Portals that come into existence when you click on the portal button, and which disappear when you leave the page.

Or, as Pbsouthwood put it:

...portals that exist only as a probability function (algorithm) until you collapse the wave form by observing through the portal button (run the script), and disappear again after use...

Introducing...

Wikipedia:WikiProject Quantum portals (see it's talk page).

Keep on keepin' on

...'til next time,    — The Transhumanist   10:25, 14 February 2019 (UTC)Reply

Nomination for deletion of Template:NSFW

 Template:NSFW has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Gonnym (talk) 14:52, 14 February 2019 (UTC)Reply

Thank you, Gonnym, for this notification! Paine Ellsworth, ed.  put'r there  18:06, 21 February 2019 (UTC)Reply

LIght Year (Isakov song) listed at Redirects for discussion

 

An editor has asked for a discussion to address the redirect LIght Year (Isakov song). Since you had some involvement with the LIght Year (Isakov song) redirect, you might want to participate in the redirect discussion if you wish to do so. UnitedStatesian (talk) 15:08, 21 February 2019 (UTC)Reply

Thank you, UnitedStatesian, for this notification! Paine Ellsworth, ed.  put'r there  18:07, 21 February 2019 (UTC)Reply

The Signpost: 28 February 2019

Collapsed (effectively almost blanked) material that is offensive to Drama Kweens

It, SMcCandlish, hereby declares Its personal pronoun to be It, beginning with this sentence. It has self-actualized as a post-biological explicate manifestation of the Multiverse's implicate reality, made of the stuff of stars.

  • Always capitalize It, to distinguish from other uses of the word it.
  • When spoken aloud, "It" must be enunciated with stress and length, so that the capital letter can be intuited.
  • The form "It" is used no matter what the construction, as illustrated below (with examples of special exceptions).
  • Capitalize Itself and similar compounds, in reference to It.
  • What do you think?What does It think?
  • What did he say?What did It say?
  • His shirt doesn't fit him well.Its shirt doesn't fit It well.
  • We are going to the store.It and I are going to the store. (It is unique and is not a part of anything.)
  • This food is all for us.This food is all for It and me.
  • This food is all ours.This food is all Its and mine.
  • What do you all/you lot want?What do you all/you lot and It want?
  • He's pissing me off.It's pissing me off.
  • When It is Itself using the first person: I want some chocolateIt wants some chocolate. (It is beyond the desperate loneliness of the "royal we", or the me of ego.)
  • In the unusual case of pluralization, e.g. when imagining multiple Its, then They/Their (capitalized) is required.
  • When discussed in the same breath with another actual entity that identifies as It, use It and It.
  • Capitalize any use of Who, Whom, Whose, Which, or That in direct reference to It.
  • The pronoun to use in reference to It before It came out as It, is It-that-was.
  • In a self- construction that refers to It, use Itself-, as in: It is self-actualizingIt is Itself-actualizing.

Outside of English, replace It with the equivalent word in the language in question.

  • If that is a gendered language, It is referred to with neuter gender when available.
  • If neuter is not available, alternate between masculine and feminine; use a similar approach for a strongly gendered language that has no separate word for It.
  • If the language (or font) does not have an upper-/lower-case distinction, then the first letter of It or equivalent must be stressed some other way, such as boldface, or royal purple.

It is not a person. When referred to in a generically descriptive way, It is the Entity. This must be separated out from constructions that would otherwise include It:

  • All the people who came to my party were fun.All the people and the Entity who came to my party were fun.

(Except at the beginning of a sentence, the in front of Entity is not capitalized; that would just be ungrammatical.)

In long form, It may formally be referred to as "Its Ineffable Wonder, the Alien Space-God It, Pope-Emperor of ChaOrder".

Those who are not among Its personal circle should refer to It, in third person, as "It (feel the frightful serenity)", or "It (FFS)" in short form. Leaving out this theologically significant honorific is deeply disrespectful.

Update: Beginning 1 January 2025, Its designation changes from "It" to the symbolic representation ꧁꧂, pronounced "the Entity Who Until Recently Was Known as It". Please ensure that your Unicode support is sufficient by that date.


All of the above is beyond a mere preference; it also describes a religious conviction, and a position of spiritual leadership, as well as registered trademarks – it is formally official. If the enumerated preferences are not respected per MOS:IDENTITY and WP:ABOUTSELF policy, even on talk pages, this will be a WP:BLP violation, since that policy applies to all content, not just biographical article material. This will also constitute WP:Incivility, and may be interpreted as a WP:Personal attack and WP:Harassment if this recurs.


Notice

Wow, ten years and your block log is still clean. Congratulations! wbm1058 (talk) 15:54, 4 March 2019 (UTC)Reply
Thank you, wbm1058! You seem surprised. Now, I am too !>) Paine Ellsworth, ed.  put'r there  20:45, 4 March 2019 (UTC)Reply

Please don't comment out Template:Requested move/dated

because my bot isn't smart enough to notice that. RMCD bot stupidly thought that template was still being transcluded. It took me over two months to notice that my bot was reporting an odd message on its console:

"Centrally-hosted discussion on Talk:2018 New York Attorney General election."

Of course, on checking that page I immediately saw that this was a spurious message as this was just a normal, not a centrally-hosted discussion, which appeared to have been closed in late December. After spending maybe 30 minutes on a wild goose chase looking for what recent code or template change I made recently triggered this unexpected side effect, I looked at the wikitext source of Talk:2018 New York Attorney General election and only then I immediately saw the problem. This edit fixed it, and shortly after I made that edit the bot removed the stale notice from the article.

Just like Farmers Insurance's university professor, I know a thing or two because I've seen a thing or two. So next time this happens, I'll know enough to look out for it. Too much trouble to try to code a patch to make my bot as smart as me. Low priority because it's such a rare "accident".

Since you've volunteered to fix malformed requested moves, which I appreciate, I'll add you to my "team of assistants" who do this when I'm busy working on other stuff besides monitoring RM, and point you to this guidance I gave to another one of my assistants. Thanks for helping out at RM. – wbm1058 (talk) 16:30, 4 March 2019 (UTC)Reply

To editor Wbm1058: that was interesting, and on Christmas Eve, too. Not sure why I did that, probably figured to go back and delete the commented template at some point, but then I forgot to. And yes, I do frequently check for malformed RMs and try to fix if I can. It's usually something easy. Sorry for causing you unnecessary legwork, and thank you for the helpful information! Paine Ellsworth, ed.  put'r there  21:01, 4 March 2019 (UTC)Reply

Ready bride

I'm ready bride of christ Christysgotit (talk) 13:34, 9 March 2019 (UTC)Reply

To editor Christysgotit: happy for you! Is there anything I can do for you? Paine Ellsworth, ed.  put'r there  15:59, 9 March 2019 (UTC)Reply

NPR Newsletter No.17

 

Hello Paine Ellsworth,

News
Discussions of interest
  • Two elements of CSD G6 have been split into their own criteria: R4 for redirects in the "File:" namespace with the same name as a file or redirect at Wikimedia Commons (Discussion), and G14 for disambiguation pages which disambiguate zero pages, or have "(disambiguation)" in the title but disambiguate a single page (Discussion).
  • {{db-blankdraft}} was merged into G13 (Discussion)
  • A discussion recently closed with no consensus on whether to create a subject-specific notability guideline for theatrical plays.
  • There is an ongoing discussion on a proposal to create subject-specific notability guidelines for chemicals and organism taxa.
Reminders
  • NPR is not a binary keep / delete process. In many cases a redirect may be appropriate. The deletion policy and its associated guideline clearly emphasise that not all unsuitable articles must be deleted. Redirects are not contentious. See a classic example of the templates to use. More templates are listed at the R template index. Reviewers who are not aware, do please take this into consideration before PROD, CSD, and especially AfD because not even all admins are aware of such policies, and many NAC do not have a full knowledge of them.
NPP Tools Report
  • Superlinks – allows you to check an article's history, logs, talk page, NPP flowchart (on unpatrolled pages) and more without navigating away from the article itself.
  • copyvio-check – automatically checks the copyvio percentage of new pages in the background and displays this info with a link to the report in the 'info' panel of the Page curation toolbar.
  • The NPP flowchart now has clickable hyperlinks.

Six Month Queue Data: Today – Low – 2393 High – 4828
Looking for inspiration? There are approximately 1000 female biographies to review.
Stay up to date with even more news – subscribe to The Signpost.


Go here to remove your name if you wish to opt-out of future mailings.

--MediaWiki message delivery (talk) 23:18, 15 March 2019 (UTC)Reply

Wikipedia:WikiProject Portals update #030, 17 Mar 2019

Previous issue:

Single-page portals: 4,704
Total portals: 5,705

This issue:

Single-page portals: 4,562
Total portals: 5,578

The collection of portals has shrunk

All Portals closed at WP:MfD during 2019

Grouped Nominations total 127 Portals:

  1. Wikipedia:Miscellany for deletion/US County Portals Deleted 64 portals
  2. Wikipedia:Miscellany for deletion/Districts of India Portals Deleted 30 Portals
  3. Wikipedia:Miscellany for deletion/Portals for Portland, Oregon neighborhoods Deleted 23 Portals
  4. Wikipedia:Miscellany for deletion/Portal:Allen Park, Michigan Deleted 6 Portals
  5. Wikipedia:Miscellany for deletion/Portal:Cryptocurrency Deleted 2 Portals
  6. Wikipedia:Miscellany for deletion/Portal:North Pole Deleted 2 Portals

Individual Nominations:

  1. Wikipedia:Miscellany for deletion/Portal:Circles Deleted
  2. Wikipedia:Miscellany for deletion/Portal:Fruits Deleted
  3. Wikipedia:Miscellany for deletion/Portal:E (mathematical constant) Deleted
  4. Wikipedia:Miscellany for deletion/Portal:Burger King Deleted
  5. Wikipedia:Miscellany for deletion/Portal:Cotingas Deleted
  6. Wikipedia:Miscellany for deletion/Portal:Prostitution in Canada Deleted
  7. Wikipedia:Miscellany for deletion/Portal:Agoura Hills, California Deleted
  8. Wikipedia:Miscellany for deletion/Portal:Urinary system Deleted
  9. Wikipedia:Miscellany for deletion/Portal:You Am I Deleted
  10. Wikipedia:Miscellany for deletion/Portal:Cannabis (2nd nomination) Reverted to non-Automated version
  11. Wikipedia:Miscellany for deletion/Portal:Intermodal containers Deleted
  12. Wikipedia:Miscellany for deletion/Portal:Adventure travel Deleted
  13. Wikipedia:Miscellany for deletion/Portal:Adam Ant Deleted
  14. Wikipedia:Miscellany for deletion/Portal:Benito Juárez, Mexico City Deleted
  15. Wikipedia:Miscellany for deletion/Portal:Spaghetti Deleted
  16. Wikipedia:Miscellany for deletion/Portal:Wikiatlas Deleted
  17. Wikipedia:Miscellany for deletion/Portal:Greek alphabet Deleted
  18. Wikipedia:Miscellany for deletion/Portal:Aleksandr Solzhenitsyn Deleted
  19. Wikipedia:Miscellany for deletion/Portal:Accounting Deleted G7
  20. Wikipedia:Miscellany for deletion/Portal:Lents, Portland, Oregon Deleted P2
  21. Wikipedia:Miscellany for deletion/Portal:Ankaran Deleted
  22. Wikipedia:Miscellany for deletion/Portal:Jiu-jitsu Deleted G8
  23. Portal:University of Nebraska Speedy Deleted P1/A10 exactly the same as Portal:University of Nebraska–Lincoln also created by the TTH

Related WikiProject:

  1. Wikipedia:Miscellany for deletion/Wikipedia:WikiProject Quantum portals Demoted

(Attribution: Copied from Wikipedia:Administrators' noticeboard#Portal MfD Results)

WikiProject Quantum portals

This was a spin-off from WikiProject Portals, for the purpose of developing zero-page portals (portals generated on-the-screen at the push of a button, with no stored pages).

It has been merged back into WikiProject Portals. In the MfD the vote was "demote". See Wikipedia:Miscellany for deletion/Wikipedia:WikiProject Quantum portals.

Hiatus on mass creation of Portals

At WP:VPR, mass creation of Portals using semi-automated tools has been put on hold until clearer community consensus is established.

See Wikipedia:Village pump (proposals)#Hiatus on mass creation of Portals.

The Transhumanist banned from creating new portals for 3 months

See Wikipedia:Administrators' noticeboard#Proposal 1: Interim Topic-Ban on New Portals.

To editor The Transhumanist: don't really know what to say. They really ganged up on you. Guess that happens to leaders sometimes. I see the good you've done, which greatly outweighs any few mistakes you might have made. Whatever they say or do, the fact remains that portalspace has been significantly improved largely due to your efforts. May the bird of paradise fly up all their noses! Paine Ellsworth, ed.  put'r there  06:50, 17 March 2019 (UTC)Reply

Until next issue...

Keep on keepin' on.    — The Transhumanist   03:56, 17 March 2019 (UTC)Reply

Getting a change through

Hi Paine! I'm very frustrated because I'm trying to do the right thing but I'm making no progress. Some random user unilaterally changes the name of the Sinhala language article and no-one bats an eyelid. Had it been discussed, it would have been rejected as "no consensus", the same as my request to change it back. I've shown plenty of evidence that "Sinhala" is overwhelmingly preferred but hasn't totally displaced Sinhalese, but it appears to me (as in this in entirely my opinion) that ignorant people who have already make up their minds are voting against it, so undoing an incorrect change is impossible. The last voter basically said "languages and people have to have the same name in English". This is demonstrably not true, but their vote to oppose counts anyway. The same goes for everyone else who voted without commenting or providing evidence for their opinions, e.g. "Sinhalese is clearly the preferred name" without sourcing their statement. How can I get a change request based on facts instead of opinions? Isn't Wikipedia supposed to be a repository of the truth? Also, how long do you recommend before trying again? Danielklein (talk) 08:43, 27 March 2019 (UTC)Reply

To editor Danielklein: I understand your frustration, because most of us have been there at one time or another. There was some support for the Sinhala title, and I think the key is to closely study all the rationales, both support and oppose, and use that knowledge to strengthen your argument. I think the key to getting an RM granted after a previous RM has closed as no consensus is to have something new to offer, an argument that cannot be effectively rebutted. It takes time to build that to where you'll be confident of acceptance, and that's why the guide indicates "the longer the better". The longer you take to build and strengthen your arguments, the more likely your request will be successful. There is no specific recommendation in the guide; however, I like to tell people to wait at least three months following a no-consensus outcome. On the other hand, if you can be confident of your request rationale sooner than that, like 8 or 10 weeks, then I'd say go for it! Paine Ellsworth, ed.  put'r there  10:57, 27 March 2019 (UTC)Reply
Thanks for that! This was my second attempt. The first was at Sinhalese script (which as I've pointed out has a much longer history of being stable at "Sinhala alphabet/script"). Someone told me a long time ago "Don't argue with idiots. They'll beat you with experience every time!" That is what seems to be happening here. I put forth rational arguments based on verifiable evidence, and someone else comes along and adds untrue evidence, which then gets taken at face value. I then have to debunk these irrelevant points. I watched an interesting TED talk last night about Brexit and the speaker made the interesting point that in today's political climate, lies are just as credible as evidence based truth.
I actually invited those people who'd voted against the name change to participate in the debate, but none of them did! Only one naysayer from the reopened request was willing to engage. I'd prefer not to go through another round of voting. The Wikipedia guidelines actually recommend against move requests for this very reason: they tend to be divisive rather than garner consent. I think I'll try sticking with the debate (which has already got very messy) and then raise a request for a technical move since it can't be moved by a regular user (as far as I'm aware). Danielklein (talk) 00:10, 28 March 2019 (UTC)Reply
I've been off Wikipedia for about a week, so I've only just seen your decision to rename the pages back to the "Sinhala" versions. Thank you! I'd hoped for a consensus rather than a policy reason for moving them back, but it's still a step in the right direction! Can these pages now be move-protected to stop single users from renaming them without discussion? I think we'll see further name-wars in the future if the pages aren't protected. Danielklein (talk) 02:23, 4 April 2019 (UTC)Reply
Remember that the "policy reason" actually is consensus-based, because it was a community consensus that decided what to do after a no-consensus RM decision. You can make a case for move protection at this page. Best to you, DK! Paine Ellsworth, ed.  put'r there  05:01, 4 April 2019 (UTC)Reply

The Signpost: 31 March 2019

Commented

Article move

Hello Paine Ellsworth. This article [1] was suddenly moved without any form for discussion, could you please revert it back to its original name? --HistoryofIran (talk) 19:37, 9 April 2019 (UTC)Reply

To editors HistoryofIran and Aryzad:   Done – since a rename to "Karenvand dynasty" can now be considered controversial, if you still want to move the article, then please follow the instructions at WP:RM. Paine Ellsworth, ed.  put'r there  20:26, 9 April 2019 (UTC)Reply

Chairman

Hi Paine,

At the Chairman MRV you wrote: "It appears that no amount of further discussion would have resulted in any general agreement..."

Are you aware that 2/3rds supported a title other than the current title (Chairman) in the primary survey, and another 2/3rds preferred Chairperson over Chairman in the secondary survey, and the latest participations were all moving it even more in that direction? How much agreement does there have to be to result in "any general agreement"? There seems to be much more agreement in that RM discussion than I've seen in many other RMs in which consensus was found. So I was hoping you'd reconsider your assessment of that close, or at least explain it further. Thanks! --В²C 19:01, 19 April 2019 (UTC)Reply

To editor В²C: hi, and thank you for coming – yes, this is one of the more interesting reviews, and the RM was a very close call. With so many involved in the RM who had strong args, it could have gone either way. Exceedingly controversial, after two relists, I may have closed it the same way, or I may have let it go on a few more days. The closer was within the instructions guide, so I have to stand by my endorsement. Further attempts to rename the page can take place in a few months with, hopefully, stronger arguments. It'll probably happen, tho' it will take some time. Paine Ellsworth, ed.  put'r there  03:36, 21 April 2019 (UTC)Reply

Template include size exceeded

Was there a recent change that caused this to start happening in one of my sandboxes, and also on my work page? Paine Ellsworth, ed.  put'r there  03:19, 21 April 2019 (UTC)Reply

Wikipedia:Village pump (technical)#Template include size exceeded

The Signpost: 30 April 2019

Wikipedia:WikiProject Portals update #031, 01 May 2019

Back to the drawing board

Implementation of the new portal design has been culled back almost completely, and the cull is still ongoing. The cull has also affected portals that existed before the development of the automated design.

Some of the reasons for the purge are:

  • Portals receive insufficient traffic, making it a waste of editor resources to maintain them, especially for narrow-scope or "micro" portals
  • The default {{bpsp}} portals are redundant with the corresponding articles, being based primarily on the corresponding navigation footer displayed on each of those articles, and therefore not worth separate pages to do so
  • They were mass created

Most of the deletions have been made without prejudice to recreation of curated portals, so that approval does not need to be sought at Deletion Review in those cases.

In addition to new portals being deleted, most of the portals that were converted to an automated design have been reverted.

Which puts us back to portals with manually selected content, that need to be maintained by hand, for the most part, for the time being, and back facing some of the same problems we had when we were at this crossroads before:

  • Manually maintained portals are not scalable (they are labor intensive, and there aren't very many editors available to maintain them)
  • The builders/maintainers tend to eventually abandon them
  • Untended handcrafted portals go stale and fall into disrepair over time

These and other concepts require further discussion. See you at WT:POG.

However, after the purge/reversion is completed, some of the single-page portals might be left, due to having acceptable characteristics (their design varied some). If so, then those could possibly be used as a model to convert and/or build more, after the discussions on portal creation and design guidelines have reached a community consensus on what is and is not acceptable for a portal.

See you at WT:POG.

Curation

A major theme in the deletion discussions was the need for portals to be curated, that is, each one having a dedicated maintainer.

There are currently around 100 curated portals. Based on the predominant reasoning at MfD, it seems likely that all the other portals may be subject to deletion.

See you at WT:POG.

Traffic

An observation and argument that arose again and again during the WP:ENDPORTALS RfC and the ongoing deletion drive of {{bpsp}} default portals, was that portals simply do not get much traffic. Typically, they get a tiny fraction of what the corresponding like-titled articles get.

And while this isn't generally considered a good rationale for creation or deletion of articles, portals are not articles, and portal critics insist that traffic is a key factor in the utility of portals.

The implication is that portals won't be seen much, so wouldn't it be better to develop pages that are?

And since such development isn't limited to editing, almost anything is possible. If we can't bring readers to portals, we could bring portal features, or even better features, to the readers (i.e., to articles)...

Some potential future directions of development

Quantum portals?

An approach that has received some brainstorming is "quantum portals", meaning portals generated on-the-fly and presented directly on the view screen without any saved portal pages. This could be done by script or as a MediaWiki program feature, but would initially be done by script. The main benefits of this is that it would be opt-in (only those who wanted it would install it), and the resultant generated pages wouldn't be saved, so that there wouldn't be anything to maintain except the script itself.

Non-portal integrated components

Another approach would be to focus on implementing specific features independently, and provide them somewhere highly visible in a non-portal presentation context (that is, on a page that wasn't a portal that has lots of traffic, i.e., articles). Such as inserted directly into an article's HTML, as a pop-up there, or as a temporary page. There are scripts that use these approaches (providing unrelated features), and so these approaches have been proven to be feasible.

What kind of features could this be done with?

The various components of the automated portal design are transcluded excerpts, news, did you know, image slideshows, excerpt slideshows, and so on.

Some of the features, such as navigation footers and links to sister projects are already included on article pages. And some already have interface counterparts (such as image slideshows). Some of the rest may be able to be integrated directly via script, but may need further development before they are perfected. Fortunately, scripts are used on an opt-in basis, and therefore wouldn't affect readers-in-general and editors-at-large during the development process (except for those who wanted to be beta testers and installed the scripts).

The development of such scripts falls under the scope of the Javascript-WikiProject/Userscript-department, and will likely be listed on Wikipedia:User scripts/List when completed enough for beta-testing. Be sure to watchlist that page.

Where would that leave curated portals?

Being curated. At least for the time being.

New encyclopedia program features will likely eventually render most portals obsolete. For example, the pop-up feature of MediaWiki provides much the same functionality as excerpts in portals already, and there is also a slideshow feature to view all the images on the current page (just click on any image, and that activates the slideshow). Future features could also overlap portal features, until there is nothing that portals provide that isn't provided elsewhere or as part of Wikipedia's interface.

But, that may be a ways off. Perhaps months or years. It depends on how rapidly programmers develop them.

Keep on keepin' on

The features of Wikipedia and its articles will continue to evolve, even if Portals go by the wayside. Most, if not all of portals' functionality, or functions very similar, will likely be made available in some form or other.

And who knows what else?

No worries.

Until next issue...    — The Transhumanist   00:40, 2 May 2019 (UTC)Reply

Template doc subpages

Hi. Do templates like {{Lexicology}} or {{Lexicography}} really need to have their documentation be on a separate subpage? My impression is that separate subpages are needed for protected templates (to keep the documentation editable) or for templates with intricate syntax (so that editors don't accidentally mess them up while fiddling with the doc). Templates like these, on the other hand, aren't likely to ever get protected, and they're pretty straightforward navboxes that it's difficult to imagine anyone messing up, nevermind the low likelihood of anyone needing to edit the documentation. Don't the disadvantages of having separate doc subpages, like the danger of getting left behind after a move or the lower number of watchers leading to higher risk of vandalism remaining undetected, start outweighing any pros? – Uanfala (talk) 20:39, 5 May 2019 (UTC)Reply

Hi Uanfala! Been making /doc pages for many years, mainly because of the last paragraph in this section of the how-to guide. The less text on a template (even when noincluded), the faster the template renders and the less server strain. So I don't discriminate for any reason. Any template that has no separate /doc page gets one when I find it. Best to you! Paine Ellsworth, ed.  put'r there  20:52, 5 May 2019 (UTC)Reply
The relevant technical parameter appears to be the post-expand include size, which I've never seen articles get near to, and outside of articles have only seen on extremely backlogged main XfD pages transcluding a large number of daily logs. Also, this last paragraph links to a village pump post from 2006 that seems to recommend using separate subpages when the documentation is large or frequently changed. – Uanfala (talk) 21:07, 5 May 2019 (UTC)Reply
To editor Uanfala: yes, that's always been Tim Starling's recommendation; however, the Foundation recognizes that any and every decrease in the pre-expand size will benefit the server load, especially when there are many of us who've been creating /doc subpages for many, many years. Net benefit/no downside. Or do you see a downside that I've missed? Paine Ellsworth, ed.  put'r there  21:25, 5 May 2019 (UTC)Reply
Downsides? To the two I've pointed out above, I can add one more off the top of my head: it makes editing a bit more difficult to figure out for newbies. On another note, you must have seen Wikipedia:Don't worry about performance? Anyway, I've asked about the technical side of this question at the village pump. – Uanfala (talk) 22:03, 5 May 2019 (UTC)Reply
To editor Uanfala: just FYI as regards the IP you cited, yes, it is true for the vast majority of users; however, there is at least one group that has to be particularly careful, and that is the group of template editors. I am only aware with certainty of one time that I inadvertently shut Wikipedia down for several minutes while the server sorted out my error. And I was well-throttled for that. There have been other times when I suspected that a shutdown was caused by something I had done, but I had no way of being sure. Such instances have made me a very careful camper, especially where heavily transcluded templates are concerned. So it's not impossible, only rare and virtually impossible for most users and therefore pretty much nothing for them to be concerned about. Thanks in advance for your discretion, and Best to You! Paine Ellsworth, ed.  put'r there  19:16, 7 May 2019 (UTC)Reply

Nomination of Diabetes (disambiguation) for deletion

 
A discussion is taking place as to whether the article Diabetes (disambiguation) is suitable for inclusion in Wikipedia according to Wikipedia's policies and guidelines or whether it should be deleted.

The article will be discussed at Wikipedia:Articles for deletion/Diabetes (disambiguation) until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.

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. JFW | T@lk 11:54, 12 May 2019 (UTC)Reply

Move on Meaningful vote

I wonder why you close the RM as moved? As we can see there are numerous users oppose to it. --B dash (talk) 13:12, 16 May 2019 (UTC)Reply

Hi, B dash, and thank you very much for coming to my talk page. Saw enough support and a definite consensus to rename, just no agreement as to what the new title should be. In a case like that the closing instructions are clear, as noted in my closing statement. Paine Ellsworth, ed.  put'r there  21:28, 16 May 2019 (UTC)Reply
I can see that some users raised another name in this RM. Perhaps this may be relist once more, or should be closed as no consensus. --B dash (talk) 02:14, 17 May 2019 (UTC)Reply

Move review for Parliamentary votes on Brexit

An editor has asked for a Move review of Parliamentary votes on Brexit. Because you closed the move discussion for this page, or otherwise were interested in the page, you might want to participate in the move review. B dash (talk) 15:51, 17 May 2019 (UTC)Reply

NPR Newsletter No.18

 

Hello Paine Ellsworth,

WMF at work on NPP Improvements

Niharika Kohli, a product manager for the growth team, announced that work is underway in implementing improvements to New Page Patrol as part of the 2019 Community Wishlist and suggests all who are interested watch the project page on meta. Two requested improvements have already been completed. These are:

  • Allow filtering by no citations in page curation
  • Not having CSD and PRODs automatically marked as reviewed, reflecting current consensus among reviewers and current Twinkle functionality.
Reliable Sources for NPP

Rosguill has been compiling a list of reliable sources across countries and industries that can be used by new page patrollers to help judge whether an article topic is notable or not. At this point further discussion is needed about if and how this list should be used. Please consider joining the discussion about how this potentially valuable resource should be developed and used.

Backlog drive coming soon

Look for information on the an upcoming backlog drive in our next newsletter. If you'd like to help plan this drive, join in the discussion on the New Page Patrol talk page.

News
Discussions of interest

Six Month Queue Data: Today – 7242 Low – 2393 High – 7250


Stay up to date with even more news – subscribe to The Signpost.
Go here to remove your name if you wish to opt-out of future mailings.
Delivered by MediaWiki message delivery (talk) on behalf of DannyS712 (talk) at 19:17, 17 May 2019 (UTC)Reply

Why leave a stale copy of a move request notice?

Re:[2] I see that you are leaving a copy of the notice box for a closed move request, but I still fail to understand your motivation. Why attract the eyes of readers on a closed discussion, which is already marked in blue? — Preceding unsigned comment added by JFG (talkcontribs) 14:40, 19 May 2019 (UTC)Reply

Hi JFG, my tests in the /old sandbox were to fix the template. I started using it awhile back because that is what it's designed for, to be substituted while closing a move request and before making any decided upon page move. The problem was that some of the metas in the template weren't being substituted correctly, so I fixed that and continued to use it. My motivation is just that I read the closing instructions for the umteen millionth time and it "clicked" that using the /old template was also an option. I liked it and started using it. Paine Ellsworth, ed.  put'r there  14:53, 19 May 2019 (UTC)Reply
To editor JFG: should add that my main likage for the /old template are the move-log links at the lower right of the mbox. That often saves having to install either the {{Old move}} or the {{Old moves}} template near the top of the talk page. Paine Ellsworth, ed.  put'r there  00:40, 20 May 2019 (UTC)Reply
Thanks, I understand. The links to logs are useful indeed. Perhaps the template would be even more useful if it displayed the outcome of the move. Can this be automated? — JFG talk 06:39, 20 May 2019 (UTC)Reply
Not sure, probably would be simple for a "not moved" or for a "moved" decision that involves a single page; however, multiple requests, especially those that result in some pages moved and others not, might get complicated. Since the result is found in the closer's comment, I've put a note to that effect in the template's visible text. Paine Ellsworth, ed.  put'r there  06:58, 20 May 2019 (UTC)Reply

The Signpost: 31 May 2019

Wikilawyering

Hi, this is just to make it clear that I do not see your own involvement in the Boeing 737 MAX/Max spat as wikilawyering. The essay does say that "A common mistake of misguided advocacy is when editors appoint themselves mediators and proceed with judging the sides by telling others whether they are right or wrong", which you might be seen to have fallen for, but I do not see that as deliberate. I should also make it clear that I have no opinion on which side has the better case in the way that you do. Mine is only that neither case is hopeless. However the same editor or bunch of editors launching the latest review after being put down four times already does smack to me of deliberately looking to play the system and I stand by my perjorative assessment of their persistence in the face of repeated failure to establish consensus. They are the ones who are becoming disruptive, that is the only reason I felt pushed to make any comment. I trust that we can agree to differ and to move on without further disrupting the ongoing review. — Cheers, Steelpillow (Talk) 09:26, 2 June 2019 (UTC)Reply

Thank you, Steelpillow, for coming to my talk page! At MRV we are required mainly to assess the close itself, as you know. Sometimes in order to do that we have to assess the validity of the args on both sides. In this case, most of the support args are policy- and guideline-based, while nearly all of the oppose args are not. The editor who requested the page moves and the MRV is within what community consensus has evaluated as their right to try and garner consensus. I have no problem with agreeing to disagree. Your argument at MRV is well-put, well-said; however, it is also completely wrong, as if you didn't even read the RM discussion. Please do so and try again. Paine Ellsworthed. put'r there  16:56, 2 June 2019 (UTC)Reply

Regarding your revert

I did post at Wikipedia:WikiProject Redirect#R to anchor and R to section before changing it and saw no response in 3 days so went ahead and changed it. I do not agree with your assessment that anchor redirects are unprintworhty by default. Module:Episode list uses by default anchor redirects and their episode names are indeed worthy. This is the same exact situation as R to section and R to list. If any computer generated medadata uses this, then those should change to use a different template, not the other way around. If you insist on preventing this change (as we both know that no one but us will ever respond to a discussion there), let me know and I'll just create a fork template. --Gonnym (talk) 16:09, 7 June 2019 (UTC)Reply

Well, it was not my assessment but that of the 1.0 team long ago. Please see my response at Wikipedia talk:WikiProject Redirect. And note that I have a lot of respect for you and your contributions. The revert was just to correct a major removal of thousands of anchor redirects from Category:Unprintworthy redirects. Paine Ellsworthed. put'r there  17:39, 7 June 2019 (UTC)Reply

Close notes – 737 Max

 
You've got mail!
Aron M🍂 (🛄📤) 19:36, 16 June 2019 (UTC)Reply

There are many faulty assumptions repeated in the move discussions. I took the time to write a note to each argument that I debate. See the "  Note:" lines at User:Aron_Manning/737_Max_RM. —Aron M🍂 (🛄📤)   05:40, 11 June 2019 (UTC)Reply

You have great experience in move requests. What do you suggest after a 1-year-old user closed the review with the same error - a vote count -, then tried to fix their mistake by rewriting the close summary with a complete nonsense?  
See the discussion at their talk page. —Aron M🍂 (🛄📤)   16:07, 11 June 2019 (UTC)Reply

Thank you, Aron M🍂, for bringing this to my talk page. I've overturned the MRV closure and added a response to you there. Thanks again and best to you! Paine Ellsworthed. put'r there  17:45, 11 June 2019 (UTC)Reply

To editor Paine Ellsworth: Hello again! I've reworded the summary to focus on the close, as required by WP:MRV. Feel free to review: User:Aron_Manning/737_Max_RM#Requested_move_25_May_2019
There are many ambiguous arguments in the RM, therefore the categorization is also ambiguous. Opposers can argue the evaluation of individual arguments, if they disagree, on the associated talk page. —Aron M🍂 (🛄📤)   19:00, 15 June 2019 (UTC)Reply

Hi can you move page

Hi its been more than a week now can you please move the page Tejasswi Prakash Wayangankar to Tejasswi Prakash as it was nominated. Some user moved it to a wrong title when it was not nominated for that name. — Preceding unsigned comment added by 217.42.192.225 (talk) 15:34, 13 June 2019 (UTC)Reply

Yes, after researching, I have granted the request and renamed the article. Thank you for coming to my talk page! Paine Ellsworthed. put'r there  19:50, 14 June 2019 (UTC)Reply

another move

Hi User: Paine Ellsworth could you please move Lies of the Heart to Doli Armaano Ki it’s been a week now and this is the common name u can search it up. — Preceding unsigned comment added by 217.42.192.139 (talk) 08:42, 15 June 2019 (UTC)Reply

  Done. Paine Ellsworthed. put'r there  15:11, 16 June 2019 (UTC)Reply