Misplaced Pages

talk:Template index/User talk namespace - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages talk:Template index

This is an old revision of this page, as edited by Zinnober9 (talk | contribs) at 20:46, 24 September 2024 (Can't place this template on an indented line due to Multiline table in list error. Dropped to new line.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 20:46, 24 September 2024 by Zinnober9 (talk | contribs) (Can't place this template on an indented line due to Multiline table in list error. Dropped to new line.)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Skip to table of contents
This is the talk page for discussing Template index/User talk namespace and anything related to its purposes and tasks.
Shortcuts
This page is part of the Misplaced Pages:WikiProject User warnings. This means that the WikiProject has identified it as part of the user warning system. The WikiProject itself is an attempt to standardise and improve user warnings, and conform them to technical guidelines. Your help is welcome, so feel free to join in.
To help centralize discussions and keep related topics together, all uw-* template talk pages and WikiProject User warnings project talk pages redirect here. If you are here to discuss one of the uw-* templates, be sure to identify which one.

Archives
  1. WP:UW Archives 1
  2. WP:UW Archives 2
  3. WP:UW Archives 3
  4. WP:UW Archives 4
  5. WP:UW Archives 5
WP:UTM archives
  1. April 2005–April 2006
  2. April 2006–October 2006
  3. October 2006–January 2007
  4. January 2007–February 2007
  5. February 2007
  6. February 2007–March 2007
  7. March 2007–September 2007
  8. September 2007–May 2008
  9. April 2008–June 2009
  10. June 2009–May 2010
  11. May 2010–February 2011
  12. February 2011–September 2013
  13. October 2013–July 2015
  14. July 2015–December 2016
  15. December 2016–August 2018
  16. August 2018–February 2020
  17. February 2020–November 2020
  18. December 2020–November 2021
  19. November 2021–March 2023
  20. March 2023–present


This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 5 sections are present.

Using AFC

Various policies and guidelines tell conflicted or paid editors to use WP:AFC.

On {{uw-coi}}, shouldn't:

avoid editing or creating articles about yourself, your family, friends, colleagues, company, organization, clients, or competitors;

say something like:

other than in the Draft namespace (where you should declare your CoI), avoid avoid editing or creating articles about yourself, your family, friends, colleagues, company, organization, clients, or competitors;

(which could be split over two bullet points)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:53, 27 August 2024 (UTC)

No, I prefer it as it is. -- Deepfriedokra (talk) 12:25, 27 August 2024 (UTC)
It's not a matter of personal preference; it's a matter of giving (new) users correct and relevant information. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:36, 27 August 2024 (UTC)

Uw-block edit request for dark mode compatibility

This edit request to Template:Uw-block has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Please merge changes at Template:Uw-block/sandbox so future substitutions are dark mode compatible. You can also check testcases (Template:Uw-block/testcases). —Matrix(!) {user - talk? - uselesscontributions} 07:38, 28 August 2024 (UTC)

 Done Sohom (talk) 12:40, 29 August 2024 (UTC)

Template-protected edit request on 1 September 2024

This edit request to Template:Uw-editsummary2 has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Currently, {{uw-editsummary2}} uses File:Information.svg with the empty argument |link=, preventing it from linking to its information page. According to Help:Pictures § Links, since the file's CC BY-SA license requires attribution, the image should link to its information page. Therefore, I think it should be changed from:

]

to:

]

jlwoodwa (talk) 17:55, 1 September 2024 (UTC)

I noticed {{uw-editsummary}} also had this issue, I have fixed it as described above. {{uw-editsummary2}} still needs this fix. Tollens (talk) 18:39, 1 September 2024 (UTC)
 Completed. P.I. Ellsworth , ed.  20:29, 3 September 2024 (UTC)
Thanks for the license fix. It's unfortunate that it's necessary, though — from a usability standpoint, it's not very helpful to have a link to an icon file page in a notice. Sdkb21:31, 3 September 2024 (UTC)
I agree that these links are annoying as a user, I've clicked them by accident before and it is very confusing to get suddenly sent to the media viewer. It would be great if a CC0 icon set could be found or created to replace the ones often used for these templates, since it wouldn't require any attribution whatsoever. I'm sure such icons probably exist but am also nearly certain that changing these very commonly-used icons would make a non-zero amount of people unreasonably upset. Tollens (talk) 04:33, 4 September 2024 (UTC)
Looks like the information icon currently displayed on the side of the closed edit request template in this section, for instance, is public domain (File:Information icon4.svg). Tollens (talk) 04:36, 4 September 2024 (UTC)

Reminder template for undue detail per WP:BALANCE?

It's possible that a majority of edits I have to routinely revert are that aren't covered by a template are substantial additions of sourced, verifiable, but deleterious material that is some combination of tangential, excessively detailed, redundant, or otherwise irreparably undue as to unbalance the coverage or coherence of the article. {{uw-fringe1}} is the closest, but is obviously not appropriate in most cases described above. Perhaps the template can standardize the common suggestions to move the content to a more specific article, more briefly summarize it in context, or compare with how analogous content is treated across several related articles Remsense ‥  22:17, 14 September 2024 (UTC)

Templates Lang1 through Lang4

{{lang1}}, {{lang2}}, {{lang3}} and {{lang4}}, which are redirects to different user warning templates, have been nominated for discussion or deletion at Misplaced Pages:Redirects for discussion/Log/2024 September 19#Template:Lang1. Please leave any comments you have there to keep discussion in one place. Thryduulf (talk) 18:00, 19 September 2024 (UTC)

New template?

Is there any way we can create a template regarding people who comment on closed discussions? Because I ran into that problem a couple weeks ago and had to use a generic level 2 disruptive editing template and append a message onto it; when I think a level 2 template specifically for commenting on closed/archived discussions would have been a lot more appropriate. Hurricane Clyde 🌀 21:31, 19 September 2024 (UTC)

Is this happening often enough that there's really a need for a template? It seems to me you could just leave a message saying something to the effect of, "Please don't comment on discussions once they have been closed/archived. Thanks!" DonIago (talk) 02:11, 20 September 2024 (UTC)
I’ll get back to you on it. That particular editor had done so twice. Hurricane Clyde 🌀 03:09, 20 September 2024 (UTC)

Proposal: new uncited-content template

It used to be popularly understood, even by non-editors, that a {{cn}} tag meant the tagger thought the statement was unverifiable, not just uncited.

I'd like to propose this draft new template. I've noticed an increasing number of editors are deleting content they think is accurate and verifiable. They wrongly think all uncited content must be removed, not just WP:BLP content. This is not what policy says.

New editors often add uncited content. When uncited content mostly got cited or tagged, editor numbers were growing exponentially. When it mostly gets deleted, editors numbers decline or just about stay steady. More fixing and tagging of uncited content could significantly increase editor retention.

My goal is to give recipients information about what policy is, and why, and what the alternatives to deletion are.

Crit and suggestions very welcome! HLHJ (talk) 22:58, 22 September 2024 (UTC)

Are you suggesting templating the regulars, or is this only intended to be used when it's newer editors who are removing unsourced content? DonIago (talk) 00:42, 23 September 2024 (UTC)
It's mostly new editors and even IPs I've seen removing unsourced content (I once saw an IP which reverted very solid unsourced content on Japanese furniture by an admin living in Japan; I confidently restored it). If a regular wrote or behaved in a way that convinced me they believed they needed to remove content they thought was unsourced but otherwise fine, then I suppose an informational template would be actually informative, and hope it would therefore not be resented. I'd be slower to assume ignorance in the case of an experienced editor, but I'm still finding corners of the wiki where I am ignorant, so I'm not offended when people tell me stuff I might not know. The rvv stuff is a bit obvious, but I think it's needed as a counterbalance. I can't promise no-one will ever misuse this template, but I can hope... HLHJ (talk) 23:41, 23 September 2024 (UTC)
I'm not really a fan. Speaking from experience, I think editors who are willing to remove unsourced content already face a great deal of pressure if/when they do so on a regular basis, and I think templating newer editors who are presumably operating in good faith in this manner is just going to lead to more editors who are afraid to touch unsourced content lest they get sanctioned for doing so. If we could guarantee this template would only be used in cases of egregious overreach I might feel differently, but there's no such guarantee of that. As such, I think while it might be understandable to advise editors in cases where one feels they're unnecessarily removing unsourced content, I don't think we should routinize and depersonalize the process.
I guess my other question is in regards to when this template is intended to be used. I feel there's a difference between newly added unsourced content where the adding editor can be identified, and unsourced "stable" content. If an editor is removing uncontroversial "stable" content for lacking sources, then I would agree that there were probably better options available, such as tagging it. If an editor is focusing on newly added content though (as I do), then I have much less of an issue with it being removed if the editor who added it is being asked to provide a source in the process; indeed, I think this is one of the primary ways that many editors become familiar with the general need to source content when adding it.
TL;DR I'm not comfortable with the template presently, but might support a version clearly intended to be used only in cases of egregious removals of unsourced content in cases where the unsourced content had also been in the article for a significant amount of time. DonIago (talk) 14:06, 24 September 2024 (UTC)
Ah. In that case I agree with you; the template is clearly not saying what I meant it to say. I want to encourage editors to ask other editors to provide sources. I agree that this is an essential part of teaching new editors. Clearly the template needs a drastic re-write. Thank you very much for the feedback.
The research evidence cited here seems to say that it's significantly more effective to teach sourcing by promptly tagging unsourced new content than by removing it and then trying to engage with the editor. Evidence is that most new editors struggle, and indeed fail, to use talk pages. They also mostly don't understand that reverted edits are still accessible in the page history. But they often check back repeatedly to look at the content they added. If the content is newly-added, and another editor tags or improves it right away, the new editor is likely to see that and respond, usually by fixing up the content or adding more content (following the model they have been shown) and they are much more likely to keep editing. I want to encourage prompt criticism and correction, and I want to encourage it in its most effective forms.
Of course sometimes prompt deletion is unavoidable, and I want to encourage that, too.
I agree that the template should not threaten sanctions; it's intended to be informational. Sanctions are not a suitable remedy for ignorance.
Perhaps a flowchart-like form would work better? Something vaguely like:
Draft:
  1. Was the content obviously added in bad faith? That is, the editor isn't trying, not even really incompetently, to improve the encyclopedia? Delete. Use curt edit summaries, like rvv. Avoid engaging the bad-faith editor.
  2. Is it BLP content? Remove immediately, linking to WP:BLP in the edit summary.
  3. Are you pretty sure it's unverifiable (that is, no sources exist, or it misrepresents the balance of sources)? If appropriate, replace with a sourced contradiction. Otherwise, remove, giving the reason and linking to WP:V in the edit summary.
  4. Is is probably verifiable, but you haven't checked?
    1. Ignore it; always an option on a volunteer project. This is more suitable for uncontroversial topics, and topics where misinformation is fairly inconsequential, and topics where misinformation is more likely to be fixed. It is also more suitable if you lack expertise or interest in the topic. There are other editors.
    2. Ask other editors to check. This is more suitable for controversial topics, expert topics, and topics where misinformation is dangerous andor unlikely to be fixed.
    3. Check
      1. Did you find sources? Add them.
      2. Are you having trouble finding sources? Ask the editor who added the content to add sources (this is most effective if done with inline tags; also sending a talk message is optional)
      3. Is finding sources impossible (that is, you've decided that it's unverifiable after all)? Modify the statement and cite it, if possible. Otherwise, delete with explanation, and engage with the editor as appropriate.
Engage editors if they are new and well-intentioned but not yet competent. If you have to delete their edits, try to make sure they understand why; new editors often don't see edit summaries and talk pages notices. If possible, help them make a productive edit. It's a lot of work, but it significantly increases their chances of becoming long-term editors. If your actions retain a new editor, you've doubled your contribution to the project.
Does the imperative makes this sound patronising? The very basic level of some of the content? It's hard to write something that is clear to the newest editors without splaining anyone.
I'm mostly worried about editors (often with semi-automated tools) regularly deleting stuff with comments like "good content but needs sources, sorry", "probably true but removed cuz uncited", or just "removing unsourced content" (people making similar statements in discussions can just be replied to, templates not needed). In some cases a closer look shows that it's unverifiable, or BLP, or some such, but sometimes an editor will delete a lot of well-written, really easy-to-cite content, without any attempt at engaging a new editor, and will even indicate that they don't like doing this but think it's their duty, because unsourced content cannot be allowed in Misplaced Pages, even temporarily. I want to tell them there are alternatives. Perhaps we can narrow the template scope accordingly. HLHJ (talk) 20:22, 24 September 2024 (UTC)
I think there's a few templates I would like to have but know shouldn't exist, and this is one of them. We only have standardized uw templates for fairly straightforward consequences of P&G, and it should likely stay that way. Having a direct extemporaneous conversation explaining "yes WP:BURDEN says what it says, but think about what we're trying to accomplish here" etc. will help users understand more than boilerplate could in this specific instance. Editors who don't learn how not to disrupt the encyclopedia are going to run into trouble in any case. Remsense ‥  20:32, 24 September 2024 (UTC)
Category: