Misplaced Pages

Revision as of 23:30, 10 December 2024

Hello. I'm I dream of horses. My pronouns are she/her/herself. I live in the Pacific Time Zone. Please be sure that you mean to contact me and not someone else. I have a FAQ here, which you should pursue before asking me anything. Other ways to contact me are listed here. I don't review drafts on request. If you want to ask a question anyone can answer, you'll most likely receive a reply more quickly if you ask it somewhere else or click Help! If you do ask a question here, a talk page watcher might (rarely!) reply, so don't be confused about that. I'm willing to talk to members of the press, per this notice.

This user is aware of the designation of the following topics as contentious topics: post-1992 politics of the United States and closely related people articles about living or recently deceased people, and edits relating to the subject (living or recently deceased) of such biographical articles climate change the Balkans or Eastern Europe gender-related disputes or controversies or people associated with them COVID-19, broadly construed the Arab–Israeli conflict She should not be given alerts for those areas.

I dream of horses uses the Wikibreak Switch template, and plans to update this notice if a wikibreak is taken.

This user has opted out of talkbacks

Recent draftification

Hello, I hope you're well. I wanted to bring up your draftification of Incognito (2025 TV series), which occured 40 minutes after the article was created. It was, and still is unsourced, but per WP:NPPHOUR we shouldn't be draftifying articles that are under an hour old. I understand and sympathize with wanting unsourced articles out of main space, but at the end of the day, we need to be considerate of how it may come across as WP:BITEY to draftify an article too quickly. Especially considering that an article doesn't need to be complete to be in main space and editors are allowed to build them there if they'd prefer to.

Thank you for your work at NPP and the effort that you put in, it's very much appreciated! Hey man im josh (talk) 21:32, 29 November 2024 (UTC)

@Hey man im josh This has been bought up to me recently. I have concerns that NPPHOUR is being applied too rigidly, which might be a policy violation onto itself. I think the "spirit" of NPPHOUR is more about allowing time for an article and evaluating things on a case-by-case basis. Honestly, I'd feel better about this if this was more about when the article creator less edited, and not when the article itself was created. I dream of horses (Hoofprints) (Neigh at me) 23:19, 29 November 2024 (UTC)

To my understanding, NPPHOUR does apply to when the article was last edited meaningfully, rather than the time it was created. In this case, that means you draftified the article 29 minutes following the creator's most recent edit. Additionally, they edited the article again 22 minutes after you draftified it, as well as later that day. Significa liberdade (she/her) (talk) 23:40, 1 December 2024 (UTC)

@Significa liberdade Why are we waiting an hour, though? 29 minutes is plenty of time to read up on policy, find online sources in the event a new editor is writing their article backwards, etc. I dream of horses (Hoofprints) (Neigh at me) 06:50, 2 December 2024 (UTC)

29 minutes may be enough time for some editors to read up on policy and find sources but certainly not for all, especially for editors (such as newbies) who don't know where to look for relevant policy and/or may find themselves confused by the policies. Overall, the question is whether it's potentially more harmful for an article to be in main space (unreviewed and thus unindexed) for an extra 30 minutes or is it more harmful to bite a newbie. Significa liberdade (she/her) (talk) 15:46, 2 December 2024 (UTC)

Yes, my understanding is "an hour from last edit" as well, though I'd probably only come after someone for getting in under an hour of the initial page creation, since those are highlighted on the page curation list so they're easy to avoid. Though I'm of the opinion that we should be waiting more than an hour, especially for draftifications, unless there's some obvious fuckery going on (like someone moving a page to mainspace after it was draftified via AfD).

I remember NPP driving me completely crazy as a new editor, so I went back and looked at my early articles. I had MB swing through literally minutes after my last edits in a few cases, which I do remember finding annoying, since it caused me edit conflicts. Much worse, though, was the NPPers who, sometimes following NPPHOUR and sometimes not (I'm not sure when it first became "best practices" anyway), tagged the articles as needing more footnotes when they clearly met WP:MINREF/WP:WHEN, which I had very carefully followed. I don't think it bothered me any less when I had my articles mistagged hours later or minutes later. Which is all to say, I don't think it's any more or less bitey to draftify something in 30 minutes or 3 hours. But a lot of new editors don't break their edits up into smaller chunks like experienced editors tend to, often doing a whole dump of several new paragraphs at a time. My initial edits took me ages - I remember looking at the 500-edit bar for XC and thinking "evidently I've got this wrong, since no one would ever expect someone to be able to make 500 edits like this in a month".

All of that is to say, I think draftification isn't going to be a positive experience for an editor no matter when it's done, but I do think we should be waiting for longer than an hour, just in case. Most of the time it won't make a difference, but every so often you'll save an editor (newbie or otherwise) from pressing "publish" only to find the article's been moved out from under them. -- asilvering (talk) 17:42, 3 December 2024 (UTC)

@Asilvering I actually agree that edit conflicts can be pretty BITE-y. I mean, we don't agree on how much time it should take vefore an edit conflict because no longer a reasonable expectation, but we agree on that. And yeah, it's odd, isn't it, how clean up tags are apparently exempt from NPPHOUR, given how upset I've seen a few people get over them, just inferring from how often they're removed without fixing the issues. Also, I swear, I remember a few newcomers from #wikipedia-en-help getting confused/upset over them; that might've been paid editors having an upset boss, though. It does make you reflect on how the subject of the article view the tags. I dream of horses (Hoofprints) (Neigh at me) 17:53, 3 December 2024 (UTC)

@I dream of horses: The spirit of NPPHOUR is to be less bitey and more welcoming to new comers. Do you believe it's damaging to Misplaced Pages to give an editor a full hour to contribute to a work in progress article in main space? I believe it's far more likely to piss someone off and, based on old NPP habits where we waited 15 minutes instead of an hour, it leads to more community pushback against NPP and draftification as a whole if we are too quick on the trigger. Hey man im josh (talk) 13:34, 2 December 2024 (UTC)

@Hey man im josh, @Significa liberdade: First of all, let's acknowledge that the article that started this discussion was written by someone who has had 586 edits since 2017. They've created 13 articles in total. We were assuming they were a newcomer all along, but they aren't.

Let's also acknowledge that there's a risk of a low-quality article being abandoned the longer we wait, and such articles vary in the amount of risk they pose. It could range from anyting from a non-blatant hoax (embarrassing, but mostly to entirely harmless) to potentially defaming a living person.

I think the pushback from the community is from a fear of confusing newcomers more than anything. Does waiting reduce that confusion? I'm not sure about that. Perhaps there should be some sort of welcome template that states "Hey, can you source the article you just created? Because otherwise, we're going to have to draftify it. Here's a list of resources you can turn to for help." Talking to them would probably help out a newcomer more than avoiding them. I dream of horses (Hoofprints) (Neigh at me) 09:06, 3 December 2024 (UTC)

First of all, let's acknowledge that the article that started this discussion was written by someone who has had 586 edits since 2017. They've created 13 articles in total. We were assuming they were a newcomer all along, but they aren't. – I do actually still think of that user as a relative newcomer, but I also believe the NPPHOUR courtesy should be extended to all users. As mentioned, you're explicitly allowed to draft your articles in main space if you so wish.

Let's also acknowledge that there's a risk of a low-quality article being abandoned the longer we wait, and such articles vary in the amount of risk they pose. It could range from anyting from a non-blatant hoax (embarrassing, but mostly to entirely harmless) to potentially defaming a living person. – Yes, and it was a work in progress, and not a hoax in this case.

I think the pushback from the community is from a fear of confusing newcomers more than anything. – It's that, and being unnecessarily disruptive by moving to draft space while people are working on things.

Does waiting reduce that confusion? I'm not sure about that. – Does waiting a full hour negatively impact Misplaced Pages in any way?

Perhaps there should be some sort of welcome template that states "Hey, can you source the article you just created? Because otherwise, we're going to have to draftify it. Here's a list of resources you can turn to for help." Talking to them would probably help out a newcomer more than avoiding them. – Nobody is advocating for avoiding users. We're advocating for ACTUALLY giving people a chance to work on what they're working on.

Seriously, what harm is there to leaving an article for a full hour when it's not a hoax? It's not indexed until marked as reviewed. NPPers just come off as assholes when we immediately jump the gun and move to draft space and it's the type of behaviour that pushes people away. We want to foster a more positive environment to help with editor retention, not immediately move something to draft space, and thus, take away our option to do so after they're done working at it and it's still not fit for main space. Then, instead of re-draftifying it, which we shouldn't do because we shouldn't draftify more than once, we're forced to send the article(s) to AfD or let them stand in main space in a poor state. Neither of those options is ideal. Hey man im josh (talk) 13:34, 3 December 2024 (UTC)

@Hey man im josh, I'm with you about how we shouldn't be jumping the gun and it pushes people away, but from my experience at least, I'm not sure waiting an hour is the thing that makes the difference. I say that as someone who thinks we really, really ought to observe NPPHOUR, and actually would prefer that we extended it. I know we all see draftspace as a chance to work on what they're working on, but that's because we know that often the alternative is a CSD tag (which will be honoured, unless one of the kinder CSD patrollers has mercy and declines it in favour of draftification). I think @I dream of horses's idea of a template that says "hey can you do this thing? if you don't do this thing within an hour, fyi, it might be draftified or maybe even deleted at any time" is a good idea. The maintenance templates don't really get the urgency across, or feel like an opportunity for dialogue between patroller and author. It would be really convenient if we could have some kind of "draftification warning" in the page curation toolbar. We could even have it set an alert (like the "this might be copyvio" etc ones) to show later patrollers that such a message has already been received. I wonder if this could cut down some of the community angst about draftification. -- asilvering (talk) 17:50, 3 December 2024 (UTC)

Oh I'm totally fine with a template @Asilvering. My issue is that we should, at least, honour NPPHOUR. Hey man im josh (talk) 17:51, 3 December 2024 (UTC)

@Hey man im josh, Asilvering is correct; newcomers don't have the perspective that we do, but we do realize that often, draftification is an alternative to deletion. Hence my idea of some sort of template. I'm trying to come up with a solution that makes NPPHOUR make some sort of sensee while giving newcomers a kick in the pants. Heck, some of them will likely even ask for draftification if it's explained to them. I dream of horses (Hoofprints) (Neigh at me) 17:56, 3 December 2024 (UTC)

I don't care if it's someone with six figures of edits or someone making their first article, it still doesn't make sense to disruptively move a work in progress that's being worked on to draft space. Again, I support a template if someone wants to make one, but it does not benefit Misplaced Pages to draftify too quickly, it actively hurts it. That's the main/entire point of this discussion. If you think something else can be improved upon, fantastic. Hey man im josh (talk) 03:12, 4 December 2024 (UTC)

@Hey man im josh I don't care if it's someone with six figures of edits or someone making their first article, it still doesn't make sense to disruptively move a work in progress that's being worked on to draft space. I'm a new page patroller who has six figures of edits. I have a decent idea of how to write an article, having evaluated quite a few. I'd probably write a decent article...but, alas, I'm among a niche few who has gotten to my level of edit count without having written an article. I'd be a gray-area 'newcomer' to article writing, if I decided to write one. /NotMad, just introducing myself.

I think the crux of the disagreement is determining if an article is being actively worked on, not whether or not it's disruptive to move an article that is being actively worked to draftspace. I dream of horses (Hoofprints) (Neigh at me) 04:06, 4 December 2024 (UTC)

Sigh. Honestly, at this point, I'm banging my head against a brick wall, so I'm going to drop it after this message. It is disruptive to do so before the article is an hour old, plain and simple. Just remember that I tried to stop you from getting dragged to ANI, which is inevitable if you continue to draftify articles less than an hour old, as you seem to routinely do. Hey man im josh (talk) 13:16, 4 December 2024 (UTC)

@Hey man im josh And, again, my concern is that NPPHOUR is being rigidly applied. There eems to be little guidance as to where gray areas or nuance applies besides "blatant content issues." I dream of horses (Hoofprints) (Neigh at me) 06:05, 5 December 2024 (UTC)

(Also, maybe we can actually concentrate on that welcome template now.) I dream of horses (Hoofprints) (Neigh at me) 06:07, 5 December 2024 (UTC)

Guild of Copy Editors December 2024 Newsletter

Guild of Copy Editors December 2024 Newsletter Hello, and welcome to the December newsletter, a quarterly digest of Guild activities since September. If you no longer want this newsletter, you can unsubscribe at any time; see below. If you'd like to be notified of upcoming drives and blitzes, and other GOCE activities, the best method is to add our announcements box to your watchlist. Election news: The Guild's coordinators play an important role in the WikiProject, making sure nearly everything runs smoothly and on time. Editors in good standing (unblocked and without sanctions) are invited to nominate themselves or another editor to be a Guild coordinator (with their permission, of course) until 23:59 on 15 December (UTC). The voting phase begins at 00:01 on 16 December and runs until 23:59 on 31 December. Questions may be asked of candidates at any stage in the process. Elected coordinators will serve a six-month term from 1 January through 30 June. Drive: In our September Backlog Elimination Drive, 67 editors signed up, 39 completed at least one copy edit, and between them they edited 682,696 words comprising 507 articles. Barnstars awarded are here. Blitz: The October Copy Editing Blitz saw 16 editors sign-up, 15 of whom completed at least one copy edit. They edited 76,776 words comprising 35 articles. Barnstars awarded are here. Drive: In our November Backlog Elimination Drive, 432,320 words in 151 articles were copy edited. Of the 54 users who signed up, 33 copy edited at least one article. Barnstars awarded are posted here. Blitz: The December Blitz will begin at 00:00 on 15 December (UTC) and will end on 21 December at 23:59. Sign up here. Barnstars awarded will be posted here. Progress report: As of 22:12, 7 December 2024 (UTC), GOCE copy editors have completed 333 requests since 1 January, and the backlog of tagged articles stands at 2,401 articles. Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators, Dhtwiki, Miniapolis, Mox Eden and Wracking. To stop receiving GOCE newsletters, please remove your name from our mailing list.

Message sent by Baffle_gab1978 using MediaWiki message delivery (talk) 22:49, 7 December 2024 (UTC).

This week's article for improvement (week 50, 2024)

Meow!

You are now a cat, no longer a horse, now say meow! (way too bored rn) ミラへぜ (talk) 00:22, 9 December 2024 (UTC)

Tech News: 2024-50

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

Weekly highlight

• Technical documentation contributors can find updated resources, and new ways to connect with each other and the Wikimedia Technical Documentation Team, at the Documentation hub on MediaWiki.org. This page links to: resources for writing and improving documentation, a new #wikimedia-techdocs IRC channel on libera.chat, a listing of past and upcoming documentation events, and ways to request a documentation consultation or review. If you have any feedback or ideas for improvements to the documentation ecosystem, please contact the Technical Documentation Team.

Updates for editors

• Later this week, Edit Check will be relocated to a sidebar on desktop. Edit check is the feature for new editors to help them follow policies and guidelines. This layout change creates space to present people with new Checks that appear while they are typing. The initial results show newcomers encountering Edit Check are 2.2 times more likely to publish a new content edit that includes a reference and is not reverted.
• The Chart extension, which enables editors to create data visualizations, was successfully made available on MediaWiki.org and three pilot wikis (Italian, Swedish, and Hebrew Wikipedias). You can see a working examples on Testwiki and read the November project update for more details.
• Translators in wikis where the mobile experience of Content Translation is available, can now discover articles in Wikiproject campaigns of their interest from the "All collection" category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the <page-collection> </page-collection> tag to their campaign article list page on Meta-wiki. This will make those articles discoverable in the Content Translation tool. For more detailed information on how to use the tool and tag, please refer to the step-by-step guide.
• The Nuke feature, which enables administrators to mass delete pages, now has a multiselect filter for namespace selection. This enables users to select multiple specific namespaces, instead of only one or all, when fetching pages for deletion.
• The Nuke feature also now provides links to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions. Thanks to Chlod and the Moderator Tools team for both of these improvements.
• The Editing Team is working on making it easier to populate citations from archive.org using the Citoid tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, archiveUrl and archiveDate, within the TemplateData for each citation template using Citoid. You can see an example of a change in a template, and a list of all relevant templates.
• One new wiki has been created: a Wikivoyage in Indonesian (voy:id:)
• Last week, all wikis had problems serving pages to logged-in users and some logged-out users for 30–45 minutes. This was caused by a database problem, and investigation is ongoing.
• View all 19 community-submitted tasks that were resolved last week. For example, a bug in the Add Link feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases.

Updates for technical contributors

• Codex, the design system for Wikimedia, now has an early-stage implementation in PHP. It is available for general use in MediaWiki extensions and Toolforge apps through Composer, with use in MediaWiki core coming soon. More information is available in the documentation. Thanks to Doğu for the inspiration and many contributions to the library.
• Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. On December 4, the MediaWiki Interfaces team began rerouting page/revision metadata and rendered HTML content endpoints on testwiki from RESTbase to comparable MediaWiki REST API endpoints. The team encourages active users of these endpoints to verify their tool's behavior on testwiki and raise any concerns on the related Phabricator ticket before the end of the year, as they intend to roll out the same change across all Wikimedia projects in early January. These changes are part of the work to replace the outdated RESTBase system.
• The 2024 Developer Satisfaction Survey is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 3 January 2025, and has an associated privacy statement.
• There is no new MediaWiki version this week.

Meetings and events

• The next meeting in the series of Wikimedia Foundation discussions with the Wikimedia Commons community will take place on December 12 at 8:00 UTC and at 16:00 UTC. The topic of this call is new media and new contributors. Contributors from all wikis are welcome to attend.

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

MediaWiki message delivery 22:13, 9 December 2024 (UTC)

This Month in Education: November 2024

This Month in Education

Volume 13 • Issue 9 • November 2024

• Auckland Museum Misplaced Pages Student Programme
• Citizenship and free knowledge on Misplaced Pages in Albanian language
• Engaging students with Misplaced Pages and Wikidata at Hasanuddin University’s Wikimedia Week
• Minigrant initiative by empowering the Rrëshen community in Albania
• Wikidata birthday in Albania, 2024
• Wikidata birthday in School
• Wikimedia Education Workshop at Lumbini Technological University
• Wikimedia MKD's new collaborations and new content
• Improving Historical Knowledge on Persian Misplaced Pages through a continuous Wikimedia Education Program: Shahid Beheshti University Misplaced Pages Education Program

Question from Poletbar (15:48, 10 December 2024)

Hello, I want to edit and add a new entry with a topic. To make this new entry, do you have to wait a long time to review the information or is this process fast? --Poletbar (talk) 15:48, 10 December 2024 (UTC)

Question from Amache Spencer (19:10, 10 December 2024)

Hello my name is Amache I am trying to figure out how I can send Denzel Washington a message or if that's even possible --Amache Spencer (talk) 19:10, 10 December 2024 (UTC)

Feedback request: All RFCs request for comment

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

Message delivered to you with love by Yapperbot :) | Is this wrong? Contact my bot operator. | Sent at 23:30, 10 December 2024 (UTC)