User talk:MB

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 94.121.173.168 (talk) at 14:34, 28 January 2023 (→‎https://en.wikipedia.org/wiki/Draft:Per_Christian_Münstermann: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Maa Tara Chandi Temple

What does your edit summary mean? Please do not revert my edits giving such reasons. Instead of reinserting bare references you may try to fix them. Egeymi (talk) 16:25, 29 December 2022 (UTC)[reply]

There is a mop reserved in your name

You are a remarkable editor in many ways. You would be a good administrator, in my opinion, and appear to be well qualified. You personify an administrator without tools and have gained my support already!

TheresNoTime (talk • they/them) 06:28, 30 December 2022 (UTC)[reply]

Remarkable work in patrolling mainspace, and could clearly use the tools. I'd support if you decided to request adminship. Wug·a·po·des 20:15, 30 December 2022 (UTC)[reply]
I think patrolling and XfD look good, but would like to see more content creation, probably a GA. If you have one, which I think shouldn't take more than three months once you pick a topic, I'd be more than happy to support. – John M Wolfson (talk • contribs) 00:50, 31 December 2022 (UTC)[reply]
I already have two (and 85 DYKs). MB 01:34, 31 December 2022 (UTC)[reply]

My mistake, the edit count gave me the contrary impression. – John M Wolfson (talk • contribs) 02:43, 31 December 2022 (UTC)[reply]

Remember that steam engine-related article you edited and added that “bare URLs” banner? Well I’ve tried two improve the URLs since then and now the page is longer than it was when you probably saw it. Is it alright if the bare URLs banner gets removed? 23.169.64.51 (talk) 01:02, 31 December 2022 (UTC)[reply]

Yes it seems that there are no longer any bare urls so you can certainly remove it. But there is a different referencing error now - Ref #13 says there are to refs with the same name but different content. Probably just needs a minor correction. Can you fix that too? MB 01:52, 31 December 2022 (UTC)[reply]

Billard

How much more of this[1] kind of trolling cleanup, typo(s) fixed: Billard → Billiard should I expect? This has continued for a few months now. Invasive Spices (talk) 31 December 2022 (UTC)

(talk page stalker) Invasive Spices, it's interesting that you didn't revert it then - but you knew of course that the edit hadn't actually been made and was an AWB false positive leaving a non revertible edit summary. What the AWB run did do was to remove a lot of unnecessary overlinking and effect some other MoS corrections. Its a long article and I see you added 86.9% of the text. Probably took a long time to write and I found it very interesting, but clean ups and copy-editing are necessary evils and any editor is welcome to do it. It even happens on the many articles I write, but with the arthritis in my fingers I've become a rather clumsy typist and I'm grateful for it. MB was doing the right thing. Perhaps being so quick to accuse experienced editors of trolling isn't quite the best reaction. Kudpung กุดผึ้ง (talk) 00:11, 1 January 2023 (UTC)[reply]
"Several months" and "so quick" don't go together. The dichotomy of an immediate impression and several months experience is the important thing here.
it's interesting that you didn't revert it then no it isn't. I read the edit. Why would I revert any of it? but you knew of course of course I did. Invasive Spices (talk) 1 January 2023 (UTC)
As a retired professional linguist, I am unable to resolve how that can be a dichotomy unless you are confusing the word with its botanical sense. Your 'several months' and your quick and incorrect impression don't conjoin in theory and method in any sense. The accusation of trolling was just plain wrong. Perhaps you might wish to thank MB for his clean up work. Kudpung กุดผึ้ง (talk) 01:50, 2 January 2023 (UTC)[reply]
The place to voice your disagreement with WP:Talk#User talk pages is WP talk:Talk#User talk pages Kudpung. Discussion of disagreements on Talk:s occurs perhaps hundreds of times every day and your desire to prohibit such discussion would seriously disrupt Wikipedia business. As an admin you are well aware of that so I don't see why I should have to remind you. My phrasing[2] was as oblique as was possible. Invasive Spices (talk) 12 January 2023 (UTC)

A barnstar for you!

The Original Barnstar
Happy New Year, MB! In 2022, other editors thanked you 1010 times using the thanks tool. This places you in the top 9 most thanked Wikipedians of 2022. Congratulations and, well, thank you for all that you do for Wikipedia. Here's to 2023! Mz7 (talk) 23:42, 31 December 2022 (UTC)[reply]

Happy New Year, MB!

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

Abishe (talk) 03:18, 1 January 2023 (UTC)[reply]

Happy New Year, MB!

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

Moops T 20:24, 1 January 2023 (UTC)[reply]

NPP Awards for 2022

Redirect Ninja Award
For over 6,000 redirect reviews during 2022. -MPGuy2824 (talk) 02:44, 2 January 2023 (UTC)[reply]

The New Page Reviewer's Bronze Award

For over 1,000 article reviews during 2022. Well done! Keep up the good work! -MPGuy2824 (talk) 02:44, 2 January 2023 (UTC)[reply]
I wish you good luck on your adminship bid! -MPGuy2824 (talk) 02:50, 2 January 2023 (UTC)[reply]
I hope you will be successful but right now the odds are falling... Thingofme (talk) 10:16, 3 January 2023 (UTC)[reply]

New Pages Patrol newsletter January 2023

Hello MB,

New Page Review queue December 2022
Backlog

The October drive reduced the backlog from 9,700 to an amazing 0! Congratulations to WaddlesJP13 who led with 2084 points. See this page for further details. The queue is steadily rising again and is approaching 2,000. It would be great if <2,000 were the “new normal”. Please continue to help out even if it's only for a few or even one patrol a day.

2022 Awards

Onel5969 won the 2022 cup for 28,302 article reviews last year - that's an average of nearly 80/day. There was one Gold Award (5000+ reviews), 11 Silver (2000+), 28 Iron (360+) and 39 more for the 100+ barnstar. Rosguill led again for the 4th year by clearing 49,294 redirects. For the full details see the Awards page and the Hall of Fame. Congratulations everyone!

Minimum deletion time: The previous WP:NPP guideline was to wait 15 minutes before tagging for deletion (including draftification and WP:BLAR). Due to complaints, a consensus decided to raise the time to 1 hour. To illustrate this, very new pages in the feed are now highlighted in red. (As always, this is not applicable to attack pages, copyvios, vandalism, etc.)

New draftify script: In response to feedback from AFC, the The Move to Draft script now provides a choice of set messages that also link the creator to a new, friendly explanation page. The script also warns reviewers if the creator is probably still developing the article. The former script is no longer maintained. Please edit your edit your common.js or vector.js file from User:Evad37/MoveToDraft.js to User:MPGuy2824/MoveToDraft.js

Redirects: Some of our redirect reviewers have reduced their activity and the backlog is up to 9,000+ (two months deep). If you are interested in this distinctly different task and need any help, see this guide, this checklist, and spend some time at WP:RFD.

Discussions with the WMF The PageTriage open letter signed by 444 users is bearing fruit. The Growth Team has assigned some software engineers to work on PageTriage, the software that powers the NewPagesFeed and the Page Curation toolbar. WMF has submitted dozens of patches in the last few weeks to modernize PageTriage's code, which will make it easier to write patches in the future. This work is helpful but is not very visible to the end user. For patches visible to the end user, volunteers such as Novem Linguae and MPGuy2824 have been writing patches for bug reports and feature requests. The Growth Team also had a video conference with the NPP coordinators to discuss revamping the landing pages that new users see.

Reminders
  • Newsletter feedback - please take this short poll about the newsletter.
  • There is live chat with patrollers on the New Page Patrol Discord.
  • Please add the project discussion page to your watchlist.
  • If you no longer wish to be a reviewer, please ask any admin to remove you from the group. If you want the tools back again, just ask at PERM.
  • To opt out of future mailings, please remove yourself here.

New pages patrol newsletter

Regarding the latest newsletter: it's missing a closing div tag, and thus its formatting is leaking out to subsequent sections. isaacl (talk) 21:09, 3 January 2023 (UTC)[reply]

(talk page watcher) Ah shoot, we will probably need someone to use WP:AWB or similar tool to go through all of the pages at Wikipedia:New pages patrol/Reviewers/Newsletter list and add </div> to the end of the newsletters. Mz7 (talk) 00:58, 4 January 2023 (UTC)[reply]
I would be willing to help with the cleanup effort for this. At the moment, I only have access to a Mac, so it's a bit cumbersome to get AWB set up, but I'm looking into WP:JWB as a potential alternative to AWB. Mz7 (talk) 01:07, 4 January 2023 (UTC)[reply]
@Certes, @GoingBatty, could either of you fix my screw-up. I could do this myself, but am a little tied up at my RFA right now. MB 01:08, 4 January 2023 (UTC)[reply]
Ah, I will leave it to one of them as well, then! Looks like they have more recent experience with AWB. It's probably an easy fix: just look for the text <!-- Drafted by User:MB, Reviewed by Novem Linguae, Kudpung --> and preprend the div tag to that. Mz7 (talk) 01:19, 4 January 2023 (UTC)[reply]
The tricky part would be detecting if it has already been fixed, as I did at User talk:Valereee, since there are numerous ways of making an edit to fix the problem. Of course, an extra closing div tag isn't the end of the world for most pages. There are some who do want their entire talk page enclosed within a box, and so deliberately leave an unclosed tag at the top of their page. Adding an extra closing div tag in that case would close the box prematurely. isaacl (talk) 02:17, 4 January 2023 (UTC)[reply]
@MB: Fix it like this? There are 869 pages to review, so it would take quite a while. GoingBatty (talk) 04:07, 4 January 2023 (UTC)[reply]
That looks correct. Can you manually watch for ones that have already been fixed, in case any of those would have the problem described above if there was another wrapper box? MB 04:13, 4 January 2023 (UTC)[reply]
Thanks for confirming. If DannyS712 has a bot that could fix this, I'll defer to him. Ping me if that doesn't work out. GoingBatty (talk) 15:39, 4 January 2023 (UTC)[reply]
Ping @DannyS712 for help running his Mms fix bot. Best, Barkeep49 (talk) 14:10, 4 January 2023 (UTC)[reply]

Also, (and I realize you're busy at the mop festival) there are three incorrect usages of semicolons in the newsletter that I always have to correct, because it renders invalid HTML5 and creates issues with screen readers per H:DL, so please fix that when you get a chance. The incorrect semicolons are just before the "Backlog", "2022 Awards" and "Reminders". Thank you for fixing this, and I have added the closing div tag to your newsletter above this section. P.I. Ellsworth , ed. put'r there 02:39, 4 January 2023 (UTC)[reply]

Thanks for letting me know about that. I've updated the draft, should not happen next time. MB 02:52, 4 January 2023 (UTC)[reply]
my pleasure and thank you very much! P.I. Ellsworth , ed. put'r there 02:56, 4 January 2023 (UTC)[reply]
Although I agree using semicolons to create pseudo-headings results in invalid HTML, I can't get too excited about that aspect in content intended for talk pages, which typically contain many colon-based list items, and those too create invalid HTML without a preceding semicolon list item. It is nonetheless semantically incorrect, with one possible consequence being screen readers misinterpreting how to read it, and thus inadvisable. (No easy alternatives exist for lists with only colon-based list items, so for better or worse we just live with that problem.) isaacl (talk) 03:34, 4 January 2023 (UTC)[reply]
WP:AWBREQ may be able to help if you guys add a request there. –Novem Linguae (talk) 04:06, 4 January 2023 (UTC)[reply]
Hey MB. I have just gone through around 300+ user talk pages to manually add </div>. Hopefully this should help out with the cleanup! echidnaLives - talk - edits 12:45, 4 January 2023 (UTC)[reply]
Hmm, since we're in a situation right now where some people already have it fixed and some people don't, I don't think a fully automated solution (what I presume DannyS712's bot is) is worth the time to investigate (especially given the risk of bugs creating even more work). 869 pages is a lot, but it's still within the realm of what's accomplishable in a semi-automated fashion using AWB or JWB. I am now in the process of using JWB and going through the user talk pages—checking first if it has been fixed already by seeing if any </div> tag exists after the newsletter. Mz7 (talk) 06:57, 5 January 2023 (UTC)[reply]
OK, I was able to go in alphabetical order through all of the user talk pages from the letters A through F. Edited 228 pages and manually skipped 33 either because the issue was already fixed or because the newsletter got removed. I think I'll call it here for the night, but somebody else can feel free to pick up where I left off (the next user talk page to process is User talk:GRuban). Mz7 (talk) 07:58, 5 January 2023 (UTC)[reply]
@GoingBatty, see above. @EchidnaLives and @Mz7 have gone through a lot of these, but there may be a couple hundred left. If you can do any more it would be much appreciated. MB 14:21, 5 January 2023 (UTC)[reply]
  • Just noticed this on my talk page, came here to give a friendly tip, and saw this section. I was going to offer to to an AWB run and fix it, actually, so I can try and tackle the rest of them. jp×g 02:43, 7 January 2023 (UTC)[reply]
    @JPxG: Thanks. (I see you started on the M's about half an hour ago) Mako001 (C)  (T)  🇺🇦 03:29, 7 January 2023 (UTC)[reply]
I am through them all now -- I wrote the regex to detect if there was already a closing div (and skip the page if there was), but a couple people have said they still got two closing divs. I think that if we went from a thousand messed-up pages to a dozen, it is probably still an improvement (although I can give it another shot). jp×g 03:40, 7 January 2023 (UTC)[reply]
Nice work, JPxG! I sampled several pages and looks like we can call this issue  Fixed at this point. Mz7 (talk) 06:53, 7 January 2023 (UTC)[reply]

For future, I have approval from MalnadachBot Task 12 to fix Lint errors like this. You can drop them at User:MalnadachBot/Signature submissions and I will process them. I have fixed many newsletters like this. It is good practice to run Wikipedia:LINTHINT on a page once before sending a mass message. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 04:30, 8 January 2023 (UTC)[reply]

Saw this change on my page and it looks like the edit to the URL in the comment has duplicated an existing part of the URL. Not a big deal but a little bit odd. – numbermaniac 07:53, 10 January 2023 (UTC)[reply]

In recognition

Seven score and four years ag–
wait, shit, let me try that again
From one MassMessage sender to another: I feel your pain. It happens to the best of us! jp×g 22:37, 17 January 2023 (UTC)[reply]


Hang in there!

It feels difficult right now...
Regardless of the outcome, you've managed an unexpectedly difficult RfA with patience and reasonableness. It's clear the community writ large approves of your previous behaviors and actions. I admire the apparent calm and gentleness with which you've interacted with others during the week. BusterD (talk) 15:31, 7 January 2023 (UTC)[reply]

World oil market chronology from 2003 ‎

I was given advice to have detailed articles on a few years at a time, with a brief summary in the parent article.

There would have been no content to speak of in the 2023–2025 world oil market chronology article but it made it easier for me to start today to have one.

You wouldn't be the only one to consider deleting it, but can I feel safe in creating that now even though it currently has one paragraph?

Because it will get really, really long as information is added.— Vchimpanzee • talk • contributions • 17:02, 7 January 2023 (UTC)[reply]

Your RfA

I always hate to be the bearer of bad news, but as of a few minutes ago the bureaucrat chat for your RfA was closed as unsuccessful. Primefac (talk) 18:39, 9 January 2023 (UTC)[reply]

Hey MB, I know it's not the result you were hoping for, but I wanted to swing by and leave some positive words. I don't want this to discourage you from continuing your great work at NPP and hope you'll continue to grow as an editor here. Once the inherent stress of RfA fades I'd encourage you to take another look at the feedback provided, keep it in mind moving forward, and know it's not a 'no' forever.
Looking forward to seeing you around, and hope you'll make another run for it in 6-12 months time. All my best, Lord Roem ~ (talk) 19:36, 9 January 2023 (UTC)[reply]
Don't take it personally. It's not a reflection on you personally or your work here. HJ Mitchell | Penny for your thoughts? 19:45, 9 January 2023 (UTC)[reply]
Commiserations. I just wanted to say how much I appreciate your volunteer work here, and that I hope you continue to do it. I'm sure that the comments in all sections of that RfA give you a lot of food for thought and self-reflection. We live and learn - just know that a great many people have the utmost respect for your contributions. Girth Summit (blether) 20:54, 9 January 2023 (UTC)[reply]
+1 to everybody's comment, especially Lord Roem. I hope you make another run in around an year. —usernamekiran (talk) 22:08, 9 January 2023 (UTC)[reply]
And when you decide to go again, I'll happily nominate you. Keep up the good work, the pettiness on display notwithstanding you're a huge asset to the project. The Blade of the Northern Lights (話して下さい) 01:56, 10 January 2023 (UTC)[reply]
Hey, MB. I'm sorry it didn't happen. Take the feedback as a gift. This can be turned around in six months to a year, the community wants it to happen for you. Valereee (talk) 02:56, 10 January 2023 (UTC)[reply]
As someone who supported this RfA, I will be looking for your second attempt in the future. My first attempt didn't go so well either, but I came back a few months later. Good luck and stay with it! --rogerd (talk) 03:12, 10 January 2023 (UTC)[reply]
MB, I also want to jump in here and tell you that I am very grateful for the valuable work you do here, especially at NPP. There are many people that believe you would be a great administrator, and I am one of them. Valereee's comment above that feedback can be a gift is spot on. I hope you decide to run again in the future. Thank you for all that you do for the encyclopedia! Netherzone (talk) 03:23, 10 January 2023 (UTC)[reply]
You do great and necessary work. Others recognize that. I hope it brings you satisfaction and you will stick with it. Several administrators have succeeded on their second or third try after a period of time. If you wish to do it again, wait a while and give it another try. Best wishes. Donner60 (talk) 04:27, 10 January 2023 (UTC)[reply]
My first RfA didn't go well. I think it's quite a large and respectable group. SilkTork (talk) 16:39, 10 January 2023 (UTC)[reply]
Bummer. :( As I said in my support !vote, much of what you said about NPP etc. resonated with me, and I'm sorry it got turned into a club to beat you with. Don't let it get to you, though, there was a lot of support also. Cheers, -- DoubleGrazing (talk) 16:44, 10 January 2023 (UTC)[reply]
Thank you for all you do on Wikipedia. I think you would make a great admin. — Archer1234 (t·c) 16:46, 10 January 2023 (UTC)[reply]
Thanks for running under the bus that is RfA, M8! Sorry you didn't pass this time. VQuakr (talk) 16:54, 10 January 2023 (UTC)[reply]
Sorry to hear this, it is simply absurd. How is there going to be a WP if there are no admins? How are there going to be admins if the scrutiny levels are ten times higher than what is required to join the US Congress? Geez. I guess NPP is going to wither now, too.  Mr.choppers | ✎  04:18, 11 January 2023 (UTC)[reply]
It was truly a shame to watch a hardworking, efficient, and level-headed editor have their candidness used in such a way against them. I'm positive you would have been an asset to the admin team. PhotogenicScientist (talk) 00:21, 13 January 2023 (UTC)[reply]
I may be late to the party, but I would add that it is a shame that you failed. Like it or not, NPP may be impacted by what is going on. Thanks for running, I am sure the future will be brighter! Have a great day! ✠ SunDawn ✠ (contact) 06:47, 14 January 2023 (UTC)[reply]
+1 SunDawn - knowing MB's abilities, I have no doubt that his future will not only be bright, it will be successful. A big portion of the community is behind him. Atsme 💬 📧 15:00, 14 January 2023 (UTC)[reply]

A barnstar for you!

The Original Barnstar
For stepping up at RfA. Ad Orientem (talk) 22:29, 9 January 2023 (UTC)[reply]

DYK nomination of Beezer Brothers

Hello! Your submission of Beezer Brothers at the Did You Know nominations page has been reviewed, and some issues with it may need to be clarified. Please review the comment(s) at your nomination's entry and respond there at your earliest convenience. Thank you for contributing to Did You Know! BlueMoonset (talk) 18:02, 14 January 2023 (UTC)[reply]

NPP newsletter, Jan 2023

Hi. I hope you are doing well. I am not sure, but I think there was an extra/unnecessary /div tag at the bottom of the "New Pages Patrol newsletter January 2023". Courtesy ping to Novem Linguae. —usernamekiran (talk) 11:28, 18 January 2023 (UTC)[reply]

Hey usernamekiran. Yes, you're correct. A couple people went through and removed the extra div tags. We thought we got them all, but if we missed any, please let us know. Thank you. –Novem Linguae (talk) 13:56, 18 January 2023 (UTC)[reply]
done. There were ~255 pages. —usernamekiran (talk) 18:44, 19 January 2023 (UTC)[reply]

Please publish https://en.wikipedia.org/wiki/Draft:Per_Christian_Münstermann Thanks in advance! 94.121.173.168 (talk) 14:34, 28 January 2023 (UTC)[reply]