en.m.wikipedia.org
Wikipedia:Village pump (policy)
"WP:VPP" redirects here. For proposals, see Wikipedia:Village pump (proposals).
 
Policy
 
Technical
 
Proposals
 
Idea lab
 
WMF
 
Miscellaneous
 
First discussion New post
Shortcuts
The policy section of the village pump is used to discuss proposed policies and guidelines and changes to existing policies and guidelines.
Please see this FAQ page for a list of frequently rejected or ignored proposals. Discussions are automatically archived after remaining inactive for two weeks.
« Archives, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166

Centralized discussion
Village pumps policy tech proposals idea lab WMFmisc
For a listing of ongoing discussions, see the dashboard.
view edit history watch archivetalk purge
Undisclosed alternate accounts
For purposes of this discussion, "undisclosed" can be taken to mean "not publicly declared" regardless of whether the account has been disclosed to ArbCom or to a CU, or was discovered without voluntary disclosure. This discussion is aimed at "privacy alts", secondary accounts created for editing certain topic areas the user would prefer not to edit from their primary account.
Background
Since the early days of the English Wikipedia, there has been a tradition or custom of some users having either known or undisclosed alternate accounts. This has held over to some extent into the modern era of the project and is enshrined in policy at WP:VALIDALT. Publicly disclosed alternate accounts are fully free to edit in any way with few restrictions; however, WP:PROJSOCK states that undisclosed accounts may not edit the Wikipedia namespace. English Wikipedia is something of an outlier in this regard: many other WMF projects regard undisclosed alternate accounts as illegitimate sock puppets. Therefore, behavior that is technically acceptable at EN.WP can have serious consequences if practiced on many other WMF wikis. Existing policy makes it clear that private disclosure to ArbCom or individual functionaries does not allow for policy violations, but this is often misunderstood by users and can lead to frustration both on the side of users and of CheckUsers.
Issues
Proposed remedies
Discussion of proposed remedies
I would like to know this too. I don't have an issue with undisclosed alt accounts that would out someone who isn't paid but if you don't want to potentially connect yourself to your employer, a simple solution is to not edit about them. No one is forcing you to and conversely, no one is forcing you to edit Wikipedia at all. TAXIDICAE💰 22:27, 15 April 2021 (UTC)
See the comment directly below for one example. Often it's a matter of not wishing to "out"some specfic aspect of their life, either something mundane as mentioned below, or perhaps editing controversial topics on religion or sexual practices. Beeblebrox (talk) 22:32, 15 April 2021 (UTC)
@Schazjmd: that's a good question. The common old-school example for why someone would have a "secret" alt is to edit embarrassing subjects, e.g. certain sexuality topics. Another possibility is to edit a topic, which editing with the main account may compromise the user's privacy. Another possibility could be an existing Wikipedia editor having assigned coursework that involves editing Wikipedia, and would not want that associated with the main account, either from either side so to say (on-wiki in terms of an association with a given university, or having university colleagues know the existence of the main account). In some cases there are real-world implications in that Wikipedia editors may experience trouble with local authorities as a result of certain edits. At the end of the day we are a project that permits pseudonymous editors. Short of running certain mass checkusers—something that is a non-starter as far as the privacy policy goes—we ought to accept that there is not much one can do about someone using two accounts to edit separate topics. Of course, there are obvious deceptive uses of multiple accounts; think of vote-stacking an AfD or cases where a banned user uses multiple accounts to evade the ban to continue the same disruption that led to the ban. That said, it ought to be considered whether the simple fact of using an alternate account is somehow a problem. Maxim(talk) 23:34, 15 April 2021 (UTC)
Praxidicae, I've edited with an undisclosed alt in the past. Not everyone is okay with being connected to articles about illness, politics, religion and sexuality. There's also a photo around here somewhere of the pierced penis of a Wikipedian which I helped anonymize. They made a request to vanish when they found potential clients who googled their name found a pierced penis as the top result. It actually took years, but I just checked it again and it seems Google has *finally* forgotten about it. — Alexis Jazz (talk or ping me) 15:04, 30 April 2021 (UTC)
Yes, I do recall you using an undisclosed alt in the past. AntiCompositeNumber (talk) 23:48, 30 April 2021 (UTC)
  1. People commenting on AE or ANI cases related to individuals they have a known negative relationship with. This prevents the closer from weighting arguments (grudges are fair to consider), and has the effect of potentially preventing sanctions on a main account (i.e. IBAN.) Even if only one account comments, this is an issue.
  2. Potential harassment concerns following users around in project space that they don't like from disputes elsewhere. Even if there is not any double voting, this is still an illegitimate use of multiple accounts. It is significantly harder to deal with, however, if there is not a clear prohibition.
  3. Concealing behaviour on internal discussions that might not be sanctionable but would have a negative impact on someone's position within the community -- if you're an archinclusionist or archdeletionist with positions way outside of the community norm and use a "privacy alt" to comment on AfDs this is an abuse of multiple accounts. If you request permissions at NPR and it is clear that you do not have an understanding of the notability policy that is in line with the community's it will be denied. If you run for RfA and you have positions on any number of topics that show a clear disconnect with community consensus, you will not pass RfA. All of these are forms of evasion of scrutiny that erode community trust, and are abuses of multiple accounts, but without PROJSOCK would be much more difficult to deal with.
We are an online community and part of that is about trust. If you don't know that the person who you are talking to is not commenting in a completely absurd and abusive manner 10 minutes later, or at least have reasonable assurances that they aren't, trust will go down hill. Many other Wikimedia projects do not allow secondary accounts at all. Updating our policy to allow people to essentially have as many personalities as they want in project space, and have ways to Wikilawyer out of it as the policy would be unclear is a clear negative, and would set us up with Commons to be one of the projects most open to abuse. TonyBallioni (talk) 01:32, 17 April 2021 (UTC)
Hmm... On #2, surely hounding is hounding anywhere (why is it any better to be following an editor around on article talk or template talk pages?). On #3, surely we shouldn't make policy that affects many editors for the sake of the dozen per year that want to run RfA (who can be asked to disclose individually?). Also, general note, aren't 1/3 not mutually exclusive with 2? Seems like Beeble has pointed out multiple issues, and even if PROJSOCK is adjusted (in whatever direction) the 'issues' about CUs not knowing declared alt accounts, or the infeasibility of policing edits (whether in WP: or any other namespace) remains. ProcrastinatingReader (talk) 10:15, 17 April 2021 (UTC)
TonyBallioni, The problem is, this is conflating "internal discussions that affect project policy" with "Wikipedia namespace". Given that we do allow privacy socks, surely you're not arguing that WP:Teahouse should be off-limits? Is asking for help on Help talk:Footnotes OK, but not on Wikipedia talk:Citing sources?
If a privacy sock is dragged to WP:AN, can they defend themselves there? Or if one of their articles is nominated at WP:AfD, can they participate in that discussion? Would it be OK to protest a WP:PROD, because that happens in article Talk space, but once you've done that and somebody takes the next step and brings it to AfD, you're stuck?
And what about WP:DYK, WP:GA, WP:FA? Are those fair game for privacy socks? DYK reviews take place mostly in Template space, GA in article Talk space, and FA in Wikipedia space. Does that mean that DYK and GA are OK, but FA is not?
What about participating in wikiprojects? They're in Wikipedia space. Would our hapless NASA employee from my earlier example be barred from participating in WP:Wikiproject Flat Earth? Maybe that's off-limits but Portal:Flat Earth is fine?
What about drafts? Can they review submissions in Draft space, but not add their name to Wikipedia:WikiProject Articles for creation/Participants?
Your goal is to ensure that privacy socks don't get to speak with multiple voices at discussions that drive project policy. That's a laudable goal, but outlawing the subset of pages that happen to fall into the Wikipedia namespace does not advance that goal. By the time you're done carving out all these exemptions, the bright line you seek will have gotten rather blurry. -- RoySmith (talk) 12:47, 17 April 2021 (UTC)
Your goal is to ensure that privacy socks don't get to speak with multiple voices at discussions that drive project policy. No. That is not my goal, and my entire response above was saying it doesn't matter if people only contribute once to each discussion if they are doing so in a way that is designed to avoid scrutiny and deceive the community. My goal is to prevent evasion of scrutiny by people using multiple accounts, because evasion of scrutiny destroys trust on a collaborative project, which is one of the driving principles of our policy on the abuse of multiple accounts.The reason why Wikipedia space in particular matters is because the only reason to use a second account in the Wikipedia namespace outside of limited discussions about content (RSN, AfD, and FA mainly) is to avoid scrutiny. It's to separate personalities, and not cause you to associate actions from one with the other. Unless your dealing with sexually deviant materials or other similar controversial topics, there really isn't a valid reason to want to have privacy on your project space discussions other than evasion of scrutinyWhich leads us to the final point: clear lines addressed with common sense are easier to enforce than ambiguous policy. No one is currently being blocked for commenting on the Tea House or in DYK or the like with a second account. CUs and SPI clerks have brains and are able to determine intent. If you remove a clear prohibition, that becomes much harder to figure out, and appeals become more difficult. Ambiguity on what constitutes "Avoidance of scrutiny" isn't helpful, and by keeping one line that clearly defines it for everyone, you help people know what is and isn't allowed and you help with enforcement. We're dealing with hypotheticals about the negatives, there are some heavy handed blocks, but they're pretty rare for this violation. The positives of this line when it comes to enforcement, however, are pretty huge. TonyBallioni (talk) 17:18, 17 April 2021 (UTC)
"by keeping one line that clearly defines it for everyone" Except the current single line doesn't clearly define it for everyone (otherwise we wouldn't be having this discussion). In addition to RSN, FA, AfD there are the village pumps (this one arguably excluded), the help desk, WikiProject pages, XfDs (especially related to pages they've contributed to with the alt account), RFU, RFHM, ITNC, TALKPP and similar projects, AN(I) when their behaviour is being discussed or they are the victim of others' bad behaviour, CCI, EFR, EFFP, EAR, Arbitration space for cases relevant to the pages they edit with the alt, RFA/RFB for someone they've interacted with in topics they edit using their alt, and likely many more I've not heard of. Yet the current wording does not do anything to stop someone developing multiple account personalities in discussions that happen to occur in places other than the Wikipedia and Wikipedia talk namespaces. By saying "CUs and SPI clerks have brains and are able to determine intent." you seem to be agreeing with me that what matters is the intent of the person, so surely the rules should be written to state that what matters is the intent not the venue? "The positives of this line when it comes to enforcement, however, are pretty huge." I've not seen a single good enforcement of this rule that was not also covered by other existing provisions so I completely disagree with you that "The positives of this line when it comes to enforcement, however, are pretty huge."Thryduulf (talk) 18:19, 17 April 2021 (UTC)
clear lines addressed with common sense are easier to enforce than ambiguous policy — Easier for CUs. But for the people actually using these accounts, it's much harder. Whether you will be blocked and outed is based on the goodwill of a CU or their whim on whether to go by "common sense" or the rule. We should not be setting a rule stricter than how we want to apply it—rather, the opposite, because "disruptive editing" does not have and does not need a rigorous definition, as the community can always decide to rule something as disruptive on a case-by-case basis. — Bilorv (talk) 18:01, 27 April 2021 (UTC)
I always thought PROJSOCK was an arbitrary rule, but I don't know the history behind it, so I'm on the fence about that. – Joe (talk) 19:05, 17 April 2021 (UTC)
WP:SOCK is confusing for a simple newish Wikipedian to get simple answers. There is some very complicated stuff in it that is interspersed with simple stuff, and I think the simple stuff should be stated clearly and upfront, and with the complicated stuff below, under warnings.
The simple stuff is:
WP:SOCKING is NOT:
The use of multiple accounts that are publicly declared (declared on the main userpage, and all such accounts connected). Examples for this include secure and non secure computers. Segregation of edits of different types. Maintenance of multiple watchlists. Templates for this include {{User alternative account name}}, and I think they belong at the top of the main userpage.
Non-editing accounts. eg. Reader accounts; long-abandoned accounts; doppelganger-prevention accounts.
Editing logged out to fix errors in mainspace.
Stuff gets complicated when talking about multiple editing accounts that are not publicly declared. Mainly, the reason for these seems to be "privacy". There are good reasons to not publicly disclose two editing accounts. You may have a good reason to edit publicly, in front of family, work, or for educational course purposes, and not want to reveal your main anonymous account. However, the section allowing for this should clearly and strongly state that doing this is NOT RECOMMENDED, and if done, done only briefly and for very narrowly defined purposes. One little mistake, and the connection may be spotted, and may then be forever public. Relative newcomers to Wikipedia should be actively discouraged from running undeclared editing accounts in parallel. This complicated stuff needs to be written, and is written, but it should be separated from the simple for the sake of simple comprehension of a simple reading of policy for simple questions.
The rules for non-publicly-declared parallel-editing accounts need to be clear and hard. There is currently a rule that you have these, only the main account may edit project space. This is very important for accountability. I think some words are needed to clarify what is a "main account".
Should an undeclared account every be allowed to participate in AfD discussions on their own content? We had discussions on this at WT:SOCK in March 2010, and in the end I found User:SlimVirgin, 10:03, 19 March 2010 specifically, convincing that legitsocks should not be allowed at AfD or dispute resolution. I also think that it is a simple and necessary extension to this that IPs must not be allowed to contribute to AfD, or to project space discussions in general.
--SmokeyJoe (talk) 08:36, 18 April 2021 (UTC)
Answering User:RoySmith's questions of 12:47, 17 April 2021 (UTC). For LEGITSOCKS, that are the not the main account, These should be specific-purpose, preferably short-term accounts. WP:Teahouse should be off-limits. Asking for help on Help talk:Footnotes maybe, but not on Wikipedia talk:Citing sources? No, simple hard rules are needed for this dangerous practice. The main account can ask questions about citing sources. I don't see why the non-main LEGITSOCK should be asking at Help talk:Footnotes.
If a privacy sock is dragged to WP:AN, they cannot defend themselves. If a privacy sock is dragged to WP:AN, and the thread is entertained, something is wrong, and the person is not qualified to run a privacy sock. An account trying to be quiet and do a specific thing should be quiet and well mannered.
If one of their articles is nominated at WP:AfD, can they participate in that discussion? No. The community has to be trusted to be running a fair AfD.
Would it be OK to protest a WP:PROD, because that happens in article Talk space, OK. But once you've done that and somebody takes the next step and brings it to AfD, you're stuck? That's right. Trust the community at AfD.
And what about WP:DYK, WP:GA, WP:FA? These are high end editing, competitive and somewhat drama associated. Reputation and accountability are important here. It is no place for a sockpuppet.
No to WikiProjects. No to AfC reviewing. No to Portals.
Pretty much, LEGITSOCKS should stick to mainspace, and to answer questions directed to them in talk space and user_talk. --SmokeyJoe (talk) 11:21, 18 April 2021 (UTC)
I believe the policy clause being questioned here is a misinterpretation of ArbCom. The statement is sourced to Wikipedia:Requests for arbitration/Privatemusings#Sockpuppetry​, which says: Sockpuppet accounts are not to be used in discussions internal to the project, such as policy debates. Firstly, this quote doesn't refer to discussions about behavior or to deletion discussions. Secondly, and more importantly, the question is if "sockpuppetry" means using multiple accounts in a single discussion, or using a non-main account in any of the discussions this statement refers to. I believe we should take the first meaning here, while the policy statement takes the second; if you take the second, it should apply only to the discussions refered to by the first issue here. 147.161.8.37 (talk) 12:57, 19 May 2021 (UTC)
The best way to know is to ask the arbs who handled this case, hope some of them are still around and remember this case 14 years later. The arbs are: User:Kirill Lokshin, User:UninvitedCompany​, User:FloNight, User:Jpgordon, User:Jdforrester, User:Mackensen, User:Morven, and User:Charles Matthews. 147.161.8.37 (talk) 13:19, 19 May 2021 (UTC)
Anonymous editing, and efforts to maintain anonymity, were more widely thought to be good things in the early days of the project than today. Specific scenarios that I recall being discussed during that era (possibly but not necessarily as part of the Privatemusings decision) were individuals who were risking governmental or institutional reprisal for their edits, most notably editors from China. Another example would be editors disclosing details of cryptographic or DRM systems, which posed real risks of prosecution in some jurisdictions back in the day. Yet another would be contributions to topic areas that would reveal lifestyle choices (sexual orientation, recreational drug use) that could result in real-world discrimination. These concerns remain valid today for editors contributing from particularly conservative jurisdictions.
As Wikipedia has evolved, the very onerous restrictions on anonymous editing (especially in difficult topic areas) make it necessary to have a named account to make meaningful contributions. It is my view that requiring users to link all their contributions by using the same account at all times will silence important voices that have a genuine interest and ability to contribute. I also believe that the present approach to dealing with socking is heavyhanded and unsustainable, and that we are better off evaluating edits based on their merit rather than their source. UninvitedCompany 20:27, 21 May 2021 (UTC)
My mood at the time was pretty specific -- I was really pissed off at Privatemusing's socking to "carry on and exacerbate drama", as I said in refusing an unblock request from him, and I was likely only considering it through my really intense hatred of socking in general. I think now I'd recommend deleting it; we don't need this blanket policy to deal with disruptive and/or dishonest socking when it's disruptive and/or dishonest. --jpgordon𝄢𝄆 𝄐𝄇 23:29, 4 June 2021 (UTC)
Consolidating help venues
Moved to Wikipedia:Village pump (proposals) § Consolidating help venues
Impartial Expert Editor
Maybe this is the wrong place in which to be asking this question. However, at the Dispute Resolution Noticeboard, there is a dispute where one of the editors says that they need an impartial expert editor to supervise the rewriting of a group of articles. Wikipedia does not have any designations of expert editors or master editors. (Some new editors may think that the various service ribbons on user pages have more meaning than they do. The editors who display the service ribbons know that the awards are either humorous or humourous, depending on continent.) There isn't a pool of impartial expert editors who can be called on when requested. My thinking is that improving any group of articles is sort of what WikiProjects are for. Is there any additional advice that I should give to an editor who says that a whole group of articles need to be substantially rewritten? Robert McClenon (talk) 04:23, 18 May 2021 (UTC)
Isn't this where setting out the issues on the article talk page and then requesting comments using the feedback request service can provide the benefit of impartial input from experienced editors who have signed up to that service? They may not bring topic expertise as such but can advise on whether there is indeed a problem and what might be next steps. AllyD (talk) 06:26, 18 May 2021 (UTC)
User:AllyD - Yes, but.... I don't think that is exactly what the editor in question wants. The editor in question wants to recruit an impartial expert editor to oversee a long project of rewriting a group of articles. As I understand the Feedback Request Service, it is invoked via the Request for Comments mechanism, and so can be used in either of two ways. The first is to ask a specific question and obtain a binding consensus, for which other editors will have been invited via FRS. The second is to ask an open-ended question, which will obtain comments (just as RFC stands for). I think that what is being asked for is something more. Thank you for your comments. Robert McClenon (talk) 17:01, 18 May 2021 (UTC)
@Robert McClenon: I'd go with your initial hunch: WikiProjects. If the most relevant WikiProject is dormant, try its parent project or something closely related. WikiProjects get a lot of criticism but this sounds like a perfect task for them. – Finnusertop (talkcontribs) 00:33, 19 May 2021 (UTC)
Thank you. I think that the editor who requested an impartial expert editor has the idea that there are ranks or grades of expertise among Wikipedia editors which may be indicated by their service ribbons on their user pages. We know that some editors display various sorts of service ribbons on their user pages. It has always been my understanding that those service ribbons are humorous and should not be taken seriously. I think that I have seen at least one case of an editor who thinks that there is a semi-official pool of such editors to be called on. Robert McClenon (talk) 23:03, 30 May 2021 (UTC)
Need clarity around the role of AfD closers
It's not uncommon for admins closing discussions at WP:AfD to offer their own opinion on the notability of a subject, i.e. whether WP:GNG and/or some WP:SNG is met. These will often get brought to WP:DRV for review. There's one such case at DRV now, and while that case was indeed what led me to start this thread, I want to focus on the more general issue, not just that one case or that one admin.
For as long as I've been involved in AfD (which is a long time), the rule has been that closers are supposed to distill the discussion, not inject their own opinions about notability. Unfortunately, I can't find any policy statement which comes right out and says that. WP:CLOSE#Policy comes close, calling out specific exceptions for WP:V, WP:OR, WP:CP, and WP:NPOV, but doesn't explicitly say those are the only exceptions. In any case, it's a WP:INFOPAGE, so doesn't rank as policy. Likewise, WP:Supervote, while widely cited in DRV discussions, is just an essay.
So, what I'm looking for is a more official statement that AfD closers must rely on the input of the discussants regarding notability. If there's not an actual policy page where it makes sense to add that, then at least a consensus close to this thread and updating WP:CLOSE#Policy to explicitly disallow closers to apply their own notability judgements would be good enough. -- RoySmith (talk) 16:04, 24 May 2021 (UTC)
Thanks for raising this issue. WP:DGFA might be a place to put it also. But I think the issue you're raising is broader than deletion discussions. We have almost no policies or guidelines about closing statements, and what is and is not appropriate to include in them. It's not really spelled out in WP:CONSENSUS, WP:CLOSE, WP:RFCEND, DGFA, WP:XFD, WP:DELPOL... how to write a closing statement doesn't appear to be anywhere in our alphabet soup. I would imagine the rules or at least principles for closing statements should be the same for XfDs as for RFCs and other discussions. We should write something, as it will help all sorts of closure reviews. Levivich harass/hound 16:22, 24 May 2021 (UTC)
There is too much supervoting on RfCs and with WP:NACs too, but maybe for another time. Xxanthippe (talk) 04:05, 31 May 2021 (UTC).
Original research heraldry for fictional universes
Is there some more specific policy for this? I removed some: Special:Diff/1026260344 and Special:Diff/1026072768​. These images are artist impressions based on text descriptions. I'm afraid there may be a lot more out there. According to OTRS the image on the right is a creation of User:TTThom. It's used on Heraldry of Middle-earth, I'd remove it but removing all the OR will leave the article gutted and I'm not in the mood for an edit war. Is there some misunderstanding about WP:OR that causes these to be added without getting reverted in a decade? — Alexis Jazz (talk or ping me) 12:02, 1 June 2021 (UTC)
It's one thing to make up heraldry for real-world royalty/houses based on language but I would tend to agree that doing this for the same for fictional ones are far less appropriate. Unlike real heraldry which follows a specific language format that allows for license-less recreations without engaging in OR, fictional ones rarely are given in the same verbiage and thus fan-made art, while maybe not being strictly a copyright violation or failing fair use, is likely original research. --Masem (t) 13:25, 1 June 2021 (UTC)
If the depiction actually matches the description in the primary sources (which should always be the author themself or someone explicitly authorized by the author), and the depiction is both sourced to said description and presented as an artistic depiction with clear labelling of such (not just in the caption, but with, for example, a section hat), and is not used in the primary infobox of a page, then I would find such images appropriate and useful. Anything short of that warrants either removal, or improvement to the standards I described.
Note that I would not apply this standard to images on commons, where I think that the only standards which needs be met is a clear description of what it is and a clear statement that it's an artistic depiction. ᛗᛁᛟᛚᚾᛁᚱPantsTell me all about it. 13:32, 1 June 2021 (UTC)
BLPPROD and Authority Control
Hello!
I ran into a couple unsourced BLP articles (i.e. Kev Hopper) and proposed them for deletion via Wikipedia:Proposed deletion of biographies of living people. I noticed that they had authority control templates, but that was it. The BLPPROD templates were later removed on the grounds that authority control counts as sources in the same way that external links would. While this reasoning makes sense, authority control is pulling links from Wikidata. The Wikipedia page source code only shows {authority control} and nothing else, so in my mind, the Wikipedia page itself contains no sources in any form. That's the disconnect for me.
Whether authority control makes BLPPROD ineligible or not, I think it should be explicitly specified in the policy to avoid this confusion again, such as "adding article contains no sources in any form (as references, external links, authority control identifiers, etc.)". Mbdfar (talk) 19:02, 2 June 2021 (UTC)
This is ridiculous, authority control is not a substitute for sources. In the case of the particular article you mentioned the "source" in the authority control is unreliable anyway (see WP:UGC). The BLPPROD template clearly states Once the article has at least one reliable source, you may remove this tag., yet it was removed even though there are no reliable sources anywhere in the article including the authority control template.--Rusf10 (talk) 19:07, 2 June 2021 (UTC)
To be fair, GB fan would have been in his right to remove the tag if authority control does count for sourcing. Per the policy, "to place a BLPPROD tag, the process requires that the article contains no sources in any form (as references, external links, etc.) which support any statements made about the person in the biography. Please note that this is a different criterion than the one used for sources added after the correct placement of the tag." So if the authority control does count for sourcing (no matter the reliability), I would have placed BLPPROD incorrectly as the page would have been ineligible. Mbdfar (talk) 19:14, 2 June 2021 (UTC)
100% agreement with Rusf10 here. The authority control listed at Kev Hopper links back to a database of user generated content, and even if the content were editorially controlled, that would not in any way establish notability, as there's no bar for inclusion that roughly translates to GNG. ᛗᛁᛟᛚᚾᛁᚱPantsTell me all about it. 22:22, 2 June 2021 (UTC)
MPants at work, Rusf10; Right, but you guys are missing the point of this discussion. My apologies for being unclear. This is not an argument about subject notability, nor about the reliability of sources. This is about WP:BLPPROD. BLPPROD states that "to place a BLPPROD tag, the process requires that the article contains no sources in any form (as references, external links, etc., reliable or otherwise) " For example, BLPPROD is invalid on an article that has so much as a link to a tweet. My question is whether pre-existing authority control identifiers qualify as a source contained in the article. In other words, is an article BLPPROD eligible if it has a valid authority control identifier? The policy should be made clear. Mbdfar (talk) 22:32, 2 June 2021 (UTC)
No it isn't, because "To be eligible for a BLPPROD tag, the entry must be a biography of a living person and contain no sources in any form (as references, external links, etc., reliable or otherwise) supporting any statements made about the person in the biography". In the case of Kev Hopper, the AC link (which is to MusicBrainz) does not support any statement mde in the prose of the article. And even if it did, it's not a reliable source, which makes me wonder why we bother with it. Black Kite (talk) 22:38, 2 June 2021 (UTC)
Black Kite, if I may ask a follow-up question; If an AC link DOES support a statement made in the prose of the article, would you consider it a valid "source" (thus rendering the article BLPPROD ineligible)? Take the page Jorge Niosi for example. He has many identifiers that support his birthdate, nationality, and publications. Would you consider this page BLPPROD immune? Mbdfar (talk) 22:52, 2 June 2021 (UTC)
The AC link definitely does support material in the biography -- it verifies an item on his discography, and by having a discography, it verifies that he's a musician. Is it a reliable source? Probably not, but that is not (and should not be) a requirement for preventing BLPROD, which is meant to wipe the most blatant cases. If this concern about AC and BLPROD is something that arises frequently, then yes, it should be added explicitly to the BLPROD descriptor. If this is a rare case, then probably not worth the hassle. --Nat Gertler (talk) 23:03, 2 June 2021 (UTC)
The AC link verifies nothing because its NOT reliable. (WP:V is about using reliable sources) A source that is not reliable does not count. Otherwise, someone could just create an article and link to their own blog to circumvent BLPPROD.--Rusf10 (talk) 01:08, 3 June 2021 (UTC)
But BLPPROD does say reliable or otherwise, so someone could circumvent it that way. JoelleJay (talk) 02:39, 3 June 2021 (UTC)
A source that is not reliably absolutely counts for making the BLPROD illegitimate. Per WP:BLPROD, "The requirements can be summed up as: only add a BLPPROD if there are no sources in any form that support any statement made about the person in the article, but once (properly) placed, it can only be removed if a reliable source is added." If you want to change the core of BLPROD, that's a much larger discussion to have. --Nat Gertler (talk) 03:08, 3 June 2021 (UTC)
There are alternatives to get rid of pages with only unreliable sources such as speedy delete, prod, or AFD, so no need to be concerned about gaming the system. Unreliable sources need more examination to see if they are, so not great for fast deletion of articles based on that. Graeme Bartlett (talk) 03:56, 3 June 2021 (UTC)
Authority Control should be considered valid for external links, provided that (as far as we can tell, after the fact) the link in question was actually there when the tag was added. 147.161.12.57 (talk) 06:21, 3 June 2021 (UTC)
Mbdfar, I wholeheartedly concur with Black Kite's response to this comment. The AC template is not, and should not be considered a source. It is an index which allows one to find data on the subject, but it doesn't guarantee the existence or relevance of said data. ᛗᛁᛟᛚᚾᛁᚱPantsTell me all about it. 12:23, 3 June 2021 (UTC)
I would agree that the AC template, on its own, is not enough to prevent a PROD... however... it does link us to an index of potential sources that should be reviewed prior to a PROD (per WP:BEFORE). If it is likely that one of those potential sources could support information in the article, then don’t prod... go directly to AFD if you wish to question/challenge notability. Blueboar (talk) 12:41, 3 June 2021 (UTC)
The question is not is the AC template enough to prevent a PROD. The question concerns WP:BLPPROD. The BLPPROD policy says that any source, reliable or not, on the article that supports any information in the article makes it ineligible for BLPROD. If we have this scenario:
  1. We have a BLP.
  2. The BLP hasin its source code.
  3. In the authority control template that renders on the article there are link(s).
  4. In at least one of the links there is some piece of information that is also in the article.
Is this enough to make this BLP ineligible for BLPPROD? ~ GB fan 13:56, 3 June 2021 (UTC)
GB fan, I would say that depends entirely on whether or not the information in that link exists and meets our standards for reliability. In the example listed above, it clearly does not do the latter. If there's a case where it does... Well, I think that such cases should be discussed, which probably puts me on your side of things for those cases. In general though, the presence or absence of an authority control template on a page should not be a factor in dealing with BLPROD. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 15:37, 3 June 2021 (UTC)
Exactly... Do due diligence BEFORE prodding. First check the potential sources linked through the AC template. If any of them could be cited in the article, then PROD is probably not appropriate. But if none are usable, then go ahead and prod (and mention that you checked AC and found no viable sources). Remember that PROD is for clear cut cases. If there is any doubt, don’t PROD. Blueboar (talk) 15:35, 3 June 2021 (UTC)
MPants at work: Why should an AC link be treated any differently than any other external link when it comes to BLPROD -- i.e., if it contains any of the information in the article, even if it's not reliable, then BLPROD is not allowed? If there's some reason, that would seem an exception that would have to be built into BLPROD, which it currently is not. --Nat Gertler (talk) 15:43, 3 June 2021 (UTC)
NatGertler, because there's no guarantee that it will contain any information at all, let alone any information that's in the article.Just because something's indexed in a database doesn't mean there's any data attached to that index. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 15:49, 3 June 2021 (UTC)
MPants at work, so it sounds like we should treat it like any other external link. Merely having an external link doesn't void a BLPROD. "To be eligible for a BLPPROD tag, the entry must be a biography of a living person and contain no sources in any form (as references, external links, etc., reliable or otherwise) supporting any statements made about the person in the biography." An AC link that supports statements in the bio would seem to fit quite nicely into the "etc." in that, if not simply as an "external link". I'm still not seeing the "but not Authority Control" exception in this. --Nat Gertler (talk) 16:09, 3 June 2021 (UTC)
snicker* good luck with that. The wikidata crowd dont want it treated as an external link because then it would be subject to WP:EL and its content being removed in many cases. The solution to this is to alter BLPPROD to allow BLPRODing of articles that do not contain references/sources. External links or templates are not a consideration if something can be prodded based on the sourcing, because they are not sources or references. Just remove the wording that is causing this. Only in death does duty end (talk) 16:17, 3 June 2021 (UTC)
the "but not Authority Control" exception for me (which lead me to starting this discussion) is that the AC links are hosted on Wikidata, not Wikipedia. The links on Wikidata can be changed or removed without leaving a changelog on Wikipedia. I think this is important in a BLP context. The Wikipedia page itself hosts no external links or sources, which lead me to interpreting BLPPROD this way. Mbdfar (talk) 16:24, 3 June 2021 (UTC)
I don't think the distinction of whether data/link content is stored on Wikidata or on Wikipedia is particularly useful to make. We use images from Commons in our articles all the time although that means we don't have local control over changes. In the case at hand, had someone turned the AC template into a MusicBrainz link would not have made the situation any better, or any worse. —Kusma (talk) 18:52, 3 June 2021 (UTC)
NatGertler, Merely having an external link doesn't void a BLPROD. I agree, and believe that merely having an AC template should not void a BLPROD.
An AC link that supports statements in the bio would seem to fit quite nicely into the "etc." in that, if not simply as an "external link". Yes, hence why I said above that it's worth discussing in those cases. I agree with Blueboar that checking the AC links should be normal due diligence for BLPRODing an article. I also assert that double-checking the AC links should be part of the normal due diligence for removing a BLPROD. Finally, I also agree with Only in death below that external links should not be included in the criteria at WP:BLPROD. There should be actual sources to void it, not simply external links. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 16:26, 3 June 2021 (UTC)
As I understand it, BLPPROD uses bright line rules. The Musicbrainz link was present in the article (doesn't matter whether through AC or directly), so the article wasn't a BLPPROD candidate. However, the link doesn't verify anything useful, and I can't find sources that support much other than #REDIRECT [[Stump (band)]]. I would support strengthening BLPPROD to require presence of a reliable source/a reliable xlink before use, that would make adding and removing the BLPPROD follow the same rules. —Kusma (talk) 15:53, 3 June 2021 (UTC)
Are there any serious objections to redirecting? We still have this unsourced BLP to take care of... —Kusma (talk) 18:54, 3 June 2021 (UTC)
If only we had a clear cut policy to take care of unsourced BLPs ;)
Jk, I think a redirect is rational. Mbdfar (talk) 04:06, 4 June 2021 (UTC)
The current version of WP:BLPPROD is, if there is any source in the article, whether it is reliable or not, and that source supports any statement in the article, the article can not be BLPPROD'd. So an external link to the BLP's personal self published website that supports some statement in the article makes the article ineligible for BLPPROD. Going back to the article that was mentioned in the first post in this section, Kev Hopper. It has an authority control template with one link. That link goes to musicbrainz.org. The musicbrainz page says that Kev Hopper released an album called Stolen Jewels in 1990. The first entry in the list of Solo albums in the Kev Hopper article says that he released Stolen Jewels in 1990. So we have an external link that supports information in the article. Under the current version of BLPPROD, is this eligible for a BLPPROD? ~ GB fan 17:51, 3 June 2021 (UTC)
Not eligible. —Kusma (talk) 18:04, 3 June 2021 (UTC)
Ignoring for the moment, the unreliability of that database, I don't think the name & release year of an album really rises to the level of being considered a source here, else one could just as validly point to the article's name as being sourced to the AC link. I'd want to see some substantial facts in the AC link, not just a single datum that does nothing to really tell us anything about the subject. ᛗᛁᛟᛚᚾᛁᚱPantsTell me all about it. 18:22, 3 June 2021 (UTC)
If you determine that a subject is not notable then just use a different procedure to propose/nominate it for deletion. The BLPPROD procedure is simply something that was introduced in the midst of a moral panic when some disruptive editors, egged on by Jimmy Wales, thought that it was more urgent to delete unsourced articles that said "Joe Bloggs is a footballer who plays for Anytown United" than to delete genuine BLP violations, which often cite loads of sources. Please let's think about things, rather than blindly follow procedures. I'm still convinced that the difference between what is valid for placing a BLPPROD tag and what is valid for removing it was a simple accident of wording caused by the rush to put something in place, rather than the philosphical talking point beloved of Wikilawyers that it seems to have become. Phil Bridger (talk) 18:56, 3 June 2021 (UTC)
Proposal to adjust the policy wording to include "authority control"
I propose that we update the policy to read To be eligible for a BLPPROD tag, the entry must be a biography of a living person and contain no sources in any form (as references, external links, authority control links, etc., reliable or otherwise)Novem Linguae (talk) 03:45, 4 June 2021 (UTC)
We can not even assume that the AC template was added by a human editor. It might have been added by bot, with no one checking to see if any of the potential sources are actually viable. Blueboar (talk) 10:28, 5 June 2021 (UTC)
Damn good point, this. ᛗᛁᛟᛚᚾᛁᚱPantsTell me all about it. 19:03, 9 June 2021 (UTC)
POV with admitted lack of knowledge on the matter ?
Hello, I witnessed a WP:TAGTEAMed administrator both warning an user of possible block and acknowledging he/she did not reviewed the relevant conflict/edits/discussion. Is there a WP:RULES that administrator or user cannot take consequential actions if they have no knowledge of the said matter ? I would like to know such rule to cite it. Yug (talk) 11:24, 3 June 2021 (UTC)
Better to ask this at WP:AN, but you should maybe link the relevant discussion so people can understand the context and advise accordingly, and also judge whether your summary is a fair representation of the events. ProcrastinatingReader (talk) 11:28, 3 June 2021 (UTC)
My idea was to cite that WP:Rule if it exist when I will message WP:AN. I already bumped into the concept of "flyover" editors/administrators for users who jump in, drop an opinion without understanding of the situation, then leave, but I can't find the page if any. Yug (talk) 12:24, 3 June 2021 (UTC)
I don’t think there is any “rule” (for or against). A lot depends on WHY the admins in question “jumped in”. Blueboar (talk) 12:50, 3 June 2021 (UTC)
The closest that I can think of is WP: ADMINACCT, where admins are supposed to be able to explain and justify their actions as admins. --Kyohyi (talk) 13:07, 3 June 2021 (UTC)
Notice of RfC on how usernames should be displayed in custom signatures
See Wikipedia talk:Signatures#RfC: usernames in signatures
Rhododendrites talk
\\ 01:11, 4 June 2021 (UTC)
Welcome over warning
Hello, How about having a new policy for experienced Wikipedians in relation to WP:Don't Bite Newcomers that promotes sending "Welcome" over "warning"? A number of unconstructive edits by anonymous users don't happen to be pure Vandalism. They are either mistakes or test edits. Sometimes due to the lack of the knowledge of Wikipedia, they err the formatting. We have rollbacking tools like Redwarn that just warn those users. Whereas, the Welcome template has more helpful links for them to better understand Wikipedia and make constructive edits to Wikipedia. This way, we can retain more happy newcomers. P.S.- This need not be exercised for those who truly vandalize Wikipedia. They better be warned than getting a Welcome. Lightbluerain (Talk | contribs) 02:56, 5 June 2021 (UTC)
That is a good idea. I always use {{Subst:Welcome to Wikipedia}} due to its pleasant and yet comprehensive content. VV 06:21, 5 June 2021 (UTC)
It depends on WHY you are warning the new user. Some behaviors are so unacceptable and egregious that they should be slapped down (hard)… no matter who the editor is. Blueboar (talk) 15:30, 5 June 2021 (UTC)
Certainly that is the case in some situations. But lets not have that get in the way of the broader discussion on being more welcoming to new editors in general. I agree that a little too often we are more likely to slap on a warning template rather than something a little more helpful and welcoming. PackMecEng (talk) 15:37, 5 June 2021 (UTC)
I agree we have such users but not all are as I wrote in my post as well. Lightbluerain (Talk | contribs) 06:00, 6 June 2021 (UTC)
Although I am sure that mistakes happen and I know from experience that some new editors are too quick to issue a vandalism warnings, and that tools like Redwarn perhaps make it too easy to issue such warnings, I would want to see data about how frequent such errors are overall. In my experience, it is pretty easy in most cases to distinguish between good faith newbie bungling and malicious intent. I strongly favor welcoming and assisting the honest newbies, and I also favor ousting malicious people promptly. Convincing evidence of a widespread problem that cannot be controlled by existing mechanisms should be required to implement a policy change. Cullen328Let's discuss it 05:10, 8 June 2021 (UTC)
Cullen328, How to collect the data? I have no idea for this. Lightbluerain (Talk | contribs) 03:34, 9 June 2021 (UTC)
Lightbluerain, my personal skills are not in data collection on Wikipedia, but I will evaluate the data that editors with such skills collect. Cullen328 Let's discuss it 05:07, 9 June 2021 (UTC)
Alright. Lightbluerain (Talk | contribs) 10:06, 9 June 2021 (UTC)
Oppose. The level one warnings have a pretty nice and welcoming tone if you read their texts from the perspective of a newcomer, and that is intentional. They also have the advantage of being brief and readable, with concise and specific instructions that newcomers can immediately implement. In my view, this is actually more helpful to newcomers than a generic welcome message which doesn't address the problem with their contributions. JBchrch talk 11:16, 11 June 2021 (UTC)
JBchrch, we have welcome templates on twinkle that addresses some of the problematic edits. I agree the level one warning templates have welcoming tones. The welcome templates addressing problematic edits have more helpful links than the warning one along with an encouraging edit summary. I use both of them considering the conditions I specified in my post. Lightbluerain (Talk | contribs) 06:25, 12 June 2021 (UTC)
Wikiquote
Hello, my question is about the link to Wikiquote found at the bottom of some WP articles. In my opinion, the quotations inserted in WQ are often an important complement to the WP page, for example when WP talks about the thought of an author and WQ illustrates it with the author's own words. However, the link to WQ is located at the bottom of the WP page with other external links and I am sure that it goes unnoticed by the vast majority of readers who might be interested in such quotes. To remedy this lack of visibility, is one allowed to insert the link to WQ in one of the sections dealing with the author's thoughts? In the French WP it is tolerated. Regards,--Hamza Alaoui (talk) 14:53, 5 June 2021 (UTC)
In general, I think bottom of article is reasonable, since WQ is WP:USERG and shouldn't be given more "attention" than external links. I may be pessimistic, but I find it probable that a WQ entry could have serious cherry-picking problems from some sort of POV. I've never edited WQ, so I don't know how "good" it is. Gråbergs Gråa Sång (talk) 08:13, 6 June 2021 (UTC)
I agree with Hamza Alaoui, it is almost impossible to find the link to Wikiquote in the articles. Can't something be done to improve this? --Mhorg (talk) 11:29, 11 June 2021 (UTC)
Reverting a revert
The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.
Rejected per snowball clause . The proposal has been withdrawn by HAL333. (non-admin closure) Sdrqaz (talk) 10:26, 8 June 2021 (UTC)
The following scenario is frustratingly common: An editor changes the longstanding status quo with an edit. You revert the edit and encourage them to discuss on the talk page. They then revert that revert. There should be repercussions for this disregard of civil discussion through the BOLD, revert, discuss cycle. I propose that the following becomes policy:
If a user's edit that changes the status quo is reverted, a revert of that revert will result in a talk page warning. A second revert of such a revert begets a 24 hour block.
This would not apply to an edit originally removing some gross violation of Wikipedia policy, such as a BLP vio. And, 3RR would still stand, as the 3 reverts do not necessarily have to be over the exact same issue. ~ HAL333 18:36, 6 June 2021 (UTC)
  • Support as nom It would encourage discussion and help stifle edit warring before it heats up. ~ HAL333 18:46, 6 June 2021 (UTC)
  • Comment – let's clarify this because the wording is a bit confusing. User1 makes a WP:BOLD edit, User2 reverts to WP:STATUSQUO and encourages talk page discussion. User1 reinstates the edit, gets a talk page warning. User2 reverts it again to the STATUSQUO. User1 again reinstates the edit, gets blocked. Is that what you're proposing, HAL333? —El Millo (talk) 18:50, 6 June 2021 (UTC)
    Facu-el Millo, Yes. Sorry for any confusion. ~ HAL333 19:04, 6 June 2021 (UTC)
  • Support, no contested edit should be allowed to remain before the issue is settled just because of the editor's persistence. —El Millo (talk) 23:50, 6 June 2021 (UTC)
    Strike my support based on other comments below. I second Number57's opinion: The issue for me is more with 3RR giving an advantage to the editor going against the status quo. IMO this should be amended to allow an editor one free revert to restore the status quo. —El Millo (talk) 17:22, 7 June 2021 (UTC)
  • Oppose. People aren't born with knowledge of how Wikipedia works. A warning for making the same edit twice? And a block on the second offense. Maybe they thought their edit didn't save. Or maybe they're really right and the "status quo" is wrong, but they don't yet know about WP:CITE, WP:V, WP:BRD, WP:OMGWTFBBQ, etc. Or they didn't see the warning. Or the first person to revert them was carelessly pushing buttons. Or they're an busy or elderly expert in their field, and just don't have the time or patience to learn our petty little rules. Or they're a kid, trying their best. A block on the second offense would be spectacularly heavy-handed. Give people time to learn how this place works. And, I'd like to see "status quo" defined in a way where all the tricky edge cases don't just work out to "version preferred by the editor with the higher edit count" in practice. Suffusion of Yellow (talk) 00:53, 7 June 2021 (UTC)
    Suffusion of Yellow Valid point - we shouldn't bite the newcomers. How about three such warning templates for IP, new, and autoconfirmed editors and only one for those who are extended confirmed? ~ HAL333 04:10, 7 June 2021 (UTC)
    I really don't think it's possible to write a message that is both non-bitey and makes it clear the editor will be blocked on the very next edit. Suffusion of Yellow (talk) 20:21, 7 June 2021 (UTC)
  • Comment I think we would have to clearly define at what point something becomes WP:STATUSQUO. Is it WP:STATUSQUO after being in the article a day, a week, a month, a year, etc? Regards  Spy-cicle💥 Talk? 01:02, 7 June 2021 (UTC)
How about 15 days or anything present in an article after going through a GAN or FAC? It wouldn't be fair to give February and July equal treatment. ~ HAL333 04:13, 7 June 2021 (UTC)
15 days seems okay though I feel we may have to adjust on context (i.e. low traffic article has a higher wait time for status quo). Probably on FAC maybe on GAN, but I suppose we would also have to adjust WP:ONUS. It can be tricky to formulate the best way to propose it but I do certainly understand the frustration. I remember rewriting an article, I submitted to GAN, it got completely rewritten by another editor, I reverted it back to the status quo, back and forth and then another editor reverted it back to the new version forcing it off the status quo, then a different editor failed my GAN due to edit warring. Easier just to work on lower traffic articles...  Spy-cicle💥 Talk? 07:02, 8 June 2021 (UTC)
  • [ec] Comment, There is nothing special about status quo per se. Do not mistake it for consensus as a result of reasoned discussion and evidence. A lot of status quo is the consequence of no-one getting round to making an improvement yet. · · · Peter Southwood (talk): 04:16, 7 June 2021 (UTC)
  • Oppose as currently expressed. Too vague, with loopholes for misuse. · · · Peter Southwood (talk): 04:25, 7 June 2021 (UTC)
  • Oppose. This needs to be added to WP:PERENNIAL. Making WP:BRD a guideline or policy instead of an essay has been proposed many times, and failed every time. If someone insists on engaging in editwarring, use WP:ANEW if it breaches WP:3RR. If it's more a long-term pattern of evading 3RR but editwarring a lot anyway, try WP:ANI as more likely to produce a restraint.  — SMcCandlish ¢ 😼  10:14, 7 June 2021 (UTC)
  • Oppose BRD is worth trying to follow but it isn't always possible or even desirable. There are enough ways to deal with this situation already.Selfstudier (talk) 10:29, 7 June 2021 (UTC)
  • Oppose. There are many situations where such a bright-line rule would lead to perverse outcomes, such as when a spelling mistake is corrected that nobody has noticed for years. Are we really saying that someone who reinstates a reverted correction should be warned and then blocked, even if the correction is obviously correct? As so often, this is an area where human judgement is needed rather than adherence to strict rules. Phil Bridger (talk) 10:33, 7 June 2021 (UTC)
  • I completely agree with the issue presented, but I can't agree with this implementation given concerns raised by Phil Bridger, among others. I agree we should use common sense more when it comes to edit warring. Elli (talk | contribs) 14:42, 7 June 2021 (UTC)
  • Support in principle but oppose as currently written. "Do not repeat an edit without consensus" is what our rule should be (it would be an effective sitewide 1RR, which I would support, and is basically what is being proposed, but I quibble on the propose wording). Levivich 14:48, 7 June 2021 (UTC)
    As I understand it, WP:1RR allows the original editor to make one revert, whereas this proposal is explicitly prohibiting this. It's really making the bold, revert, discuss cycle mandatory. isaacl (talk) 20:13, 7 June 2021 (UTC)
  • Oppose There are several situations where a revert of a revert is perfectly acceptable – for instance, the outcome of a discussion being implemented and the original reverter being unaware of this outcome, or reverting a knee-jerk blind revert that was not done in good faith. The issue for me is more with 3RR giving an advantage to the editor going against the status quo. IMO this should be amended to allow an editor one free revert to restore the status quo. Number 57 15:10, 7 June 2021 (UTC)
    I totally agree with you on 3RR. ~ HAL333 16:33, 7 June 2021 (UTC)
  • Oppose and personally I like how 3RR advantages an editor going against the status quo. It forces people making a revert to find at least once other person to agree with them which proves consensus. Chess (talk) (please use
    {{reply to|Chess}}
    on reply) 19:47, 7 June 2021 (UTC)
    The problem is that conflicts with WP:CONSENSUS. Per NOCON (part of consensus) the change shouldn't be made unless there is a consensus to change it. Often edit wars occur because editors trying to make a change haven't shown consensus but they have enough reverts on their side to be the last revert standing. So long as CONSENSUS is policy our behavioral rules should push in that direction. Springee (talk) 21:28, 7 June 2021 (UTC)
  • As much as I think the bold, revert, discuss cycle is a good approach whose level of community support makes it close to a policy, I feel making it mandatory might be too inflexible for all situations. I think it could also exacerbate article ownership issues, by making it easy to turn every update into a protracted discussion. isaacl (talk) 20:24, 7 June 2021 (UTC)
  • Oppose as stated but... I strongly support the concern here. Far to often I've see a poor quality edit added to a page, it gets reverted (back to status quo) then the person who added it or even another editor restores the disputed content. A flaw of 1RR or 3RR is any time both editors use up their "edit limit" the result is the change stays vs is reverted. I would rather see something included in the 1RR rules that say, 1RR, mandatory BRD if a new edit is challenged. This would allow an editor to make several new edits to a page, even if one of those edits is reverted, without hitting the 1RR limit. However, if any edit is challenged they cannot restore it without talk page consensus first. Number 57's "one free revert" might work as well but reducing the number of reverts is probably better than increasing the number. Either way, it is a problem that the current system inadvertently favors a change vs status quo. Springee (talk) 21:24, 7 June 2021 (UTC)
    An alternative might be to turn 3RR into a three edit rule – i.e. an editor cannot make the same edit more than three times within a 24 hour period. This would take away the advantage the editor going against the status quo has. Number 57
  • Comment from nominator Well this looks like a WP:SNOWCLOSE. But as suggested by multiple editors above, I'll propose a (more thought-out) change to 3RR in a few days. Cheers. ~ HAL333 21:29, 7 June 2021 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Am I canvassing?
Hi, a user just made this comment.[1] Am I doing something wrong? I don't think I'm canvassing... I am exposing in this discussion[2] with a user encountered in an AE request, all the events that I consider unfair about another user. If so, I'll stop now. Thank you.--Mhorg (talk) 18:57, 6 June 2021 (UTC)
 Comment: This seems like it should be brought up at WP:ANI, instead of here. 2601:1C0:4401:24A0:6463:127E:E490:C360 (talk) 16:30, 11 June 2021 (UTC)
Airport destination lists
I don't need to cite specific examples, just look up any article about a reasonably sized airport and you'll find an #Airlines_and_destinations section. I don't know if there's an explicit consensus for this (or, if there is, if it's a WP:LOCALCONSENSUS​), but they seem to be blatant and obvious examples of WP:NOT (both because we're not a travel guide and because we're not an indiscriminate collection of information), in addition to being high-maintenance stuff. Would there be any objection to me starting an RfC (here) to get explicit consensus for their removal? RandomCanadian (talk / contribs) 01:52, 11 June 2021 (UTC)
It appears to be part of the standard Wikipedia:WikiProject Airports/page content layout. Make sure you are clear in your RfC whether you are only talking about the destinations vs the whole airlines list also. DMacks (talk) 02:01, 11 June 2021 (UTC)
So LOCALCONSENSUS, as I was saying? RandomCanadian (talk / contribs) 02:24, 11 June 2021 (UTC)
Not everything you didn't get a chance to vote on is a violation of "local consensus" and not every bit of text that appears at Wikipedia requires pre-approval by the entire community. Where the community has decided some principle, local consensus should not override it, but the community has not decided this issue in any meaningful way, and no one is doing anything wrong here. --Jayron32 14:40, 11 June 2021 (UTC)
It definitely feels like something to see if the project's standards are inconsistent with the overall en.wiki expectations. An RFC would be appropriate but you definitely need to make sure the Airports wikiproject is informed about it. --Masem (t) 02:31, 11 June 2021 (UTC)
On the other hand, we list all the stations train stations directly service, why not airports? --Golbez (talk) 04:01, 11 June 2021 (UTC)
Trains really cannot reroute as freely as airplanes, in which there that's all up to what airlines decide to do for the most part. There are reasons to consider, particularly for smaller regional/municipal airports, to say that they generally serve to provide connecting flights to a major airport hub, but this reasoning doesn't make sense for the large scale airports. --Masem (t) 04:14, 11 June 2021 (UTC)
New routes opening and closing does get mentioned in the media. People seem to maintain them. Kind of the only reason I can see to remove them is that Wikipedia is the best place on the internet for this information. Which isn't such a great reason to destroy this useful resource. —Kusma (talk) 05:51, 11 June 2021 (UTC)
For a slightly more encyclopaedic reasoning, something like the destination list is necessary to understand what kind of airport a given airport is. From a European perspective, for example it is a characterising feature whether an airport has domestic flights or not. Nuremberg Airport is reasonably usefully connected to hubs and business destinations (plus holidays), while Dortmund Airport serves holidays and flights home for Eastern Europeans working in Germany. You can read this off from the destination list without having to make a judgement in the article whether you consider flights to Barcelona and Paris to be business or leisure flights. If you explain the character of the destination list in prose, you still have to give some examples, and then going for the full list isn't very far away. —Kusma (talk) 06:34, 11 June 2021 (UTC)
There's no reason what type of airport cannot be described in text using terms-of-art words for describing the airports. Eg: as I mentioned, a small regional airport likely only has flights to two or three major hubs so that can be briefly mentioned. But I would not list all the possible destinations for a major hub like JFK or LAX. Instead, something like "Atlanta International Airport is one of Delta's main hubs in the United States, serving its domestic routes and international travel to Europe, Central and South America." That future proofs the article from any changes that may happen to Delta's flightplans. --Masem (t) 15:02, 11 June 2021 (UTC)
That would be an issue if the destination tables weren't regularly updated. Look at any airport, I just spot-checked Heathrow: we have lots of airport editors who gnome specifically to keep the information up-to-date. Some don't make any other edits. SportingFlyer T·C 22:45, 11 June 2021 (UTC)
A typical small regional airport in Germany, on the other hand, has zero connections to major national hubs. From Erfurt–Weimar Airport, you can't fly to Frankfurt or Munich. Airports are very different in countries with functioning rail networks and countries without. Future-proofing could work well using "as of" and by hiding the lists should they become out of date. In practice, airport destination lists have been well maintained, unlike, say, electoral constituencies, which are commonly ten years old and outdated by two elections. —Kusma (talk) 16:10, 12 June 2021 (UTC)
RfC: Ariport destination tables
WITHDRAWN
A shame, but clearly no enthusiasm for this particular proposal. RandomCanadian (talk / contribs) 16:05, 12 June 2021 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Should tabular listings of destinations in airport articles be removed and replaced with prose descriptions? 02:23, 12 June 2021 (UTC)
Survey
  • Yes per comments in above discussion about NOTDIR and the high maintenance burden of this non-encyclopedic information. RandomCanadian (talk / contribs) 02:23, 12 June 2021 (UTC)
  • Strong oppose this type of instruction creep. Destination lists are encyclopedic information (just look into the 1911 Britannica), you just want them in prose instead of lists? The proposal basically says "we should avoid having complete and up to date information about these things". These lists change about as often as sports team squads do, and are being well maintained by dedicated people. The problem you wish to solve does not exist. —Kusma (talk) 06:18, 12 June 2021 (UTC)
  • Oppose They are useful information to have in articles, and having them as lists/tables makes it easier to quickly parse compared to prose. Thanks. Mike Peel (talk) 07:56, 12 June 2021 (UTC)
  • Strong oppose Just because we include information in a tabular format does not mean WP:NOTDIR applies. WP:NOTTRAVEL, mentioned above, also doesn't apply, since no travel guide would want this information - just because the information bases itself in travel does not mean that it's written like a travel guide. The "high maintenance" is wrong and completely ignores the fact we have many wiki-gnomes who update this on a frequent basis. "Non-encyclopaedic" is an opinion, and one I strongly disagree with. As someone with lots of aviation related books, destination information was one of my primary uses of the site before I started contributing on a regular basis. Finally, no example of what this would look like in prose has been contributed. This is a half-baked proposal that doesn't fix any problem. SportingFlyerT·C 08:01, 12 June 2021 (UTC)
  • Oppose Prose for this sort of information would be difficult to compile in an accessible manner. Tables are suitable and well established. NOTDIR does not apply, surely, as an airport article would be expected to contain an easy to read summary of destinations available from that airport. doktorb wordsdeeds 08:40, 12 June 2021 (UTC)
  • No. WP:NOTDIR doesn't apply here, as this is not a list of loosely associated topics, a directory for conducting business, nor a simple listing without context. The proposal to change it with prose description is merely table-phobia - if the content violated NOTDIR or NOTTRAVEL, it would do it in prose form as well. We are discussing merely about presentation format, and I'm not aware of no policy saying that tables are a format to avoid when showing a list of items. Also, the problem of having to maintain the content would also exist if this was changed to prose, so how does it solve the problem as stated? Diego (talk) 09:07, 12 June 2021 (UTC)
  • Oppose. The proposal is to reformat the content, with no comment about changing the scope or level of detail of the content (that is, it does not address the original goal of the preceding discussion). Therefore it it just a Wikipedia:Manual of Style/Lists question. Table seems the best way to organize this info, though no prejudice from also including other prose highlighting general themes or historical aspects. DMacks (talk) 15:21, 12 June 2021 (UTC)
    If you read the clarification comment below, you'll see the proposal is to trim the info by putting it into prose and sticking to what can be found in reliable secondary sources and not simply to be a listing of destinations based on WP:PRIMARY sources. RandomCanadian (talk / contribs) 15:30, 12 June 2021 (UTC)
    My position stands. No evidence that this can't be found in secondary (User:Kusma suggests above that it can). And no evidence that only using secondary for bare facts, which might lead to omissions, is better than a factually complete statement (the idea being the specific details, not the general patterns). And finally, WP:PRIMARY explicitly condones this sort of bare-facts use. DMacks (talk) 15:36, 12 June 2021 (UTC)
Discussion
Question clarification "prose descriptions" might be a bit vague, but this is intentional so as not to explicitly exclude specific but not thought of forms of reliably sourced information and also not to get people hung up on wording. It ideally includes any significant information which can be reliably sourced, such as main airlines serving the airport, most important destinations, so on so forth. RandomCanadian (talk / contribs) 02:30, 12 June 2021 (UTC)
You should inform the relevant stakeholders. Holding an RfC on a policy for a small subclass of articles here without telling people about it is like proposing to knock down a house and put the plans on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.” You know, talk to the people whose house you are proposing to knock down before finalising the plans. In this case, this seems to involve masses of IPs that have kept this content up to date and accurate for many years. I think your RfC should be closed as premature. —Kusma (talk) 06:25, 12 June 2021 (UTC)
@Diego: "it would also violate NOTDIR in prose format" - wrong. Prose format would make it far more inconvenient to give a full, excessive listing of all of them. We're an encyclopedia, not an airport departures board. Readers who absolutely need the information should not be using Wikipedia for this - they should instead go directly to the airport's website. To those who don't, the only relevant and encyclopedic information is providing a summary (Encyclopedia: "reference work or compendium providing summaries of knowledge") of it, for example in the case of the previously linked Dortmund Airport: "As of 2021, Dortmund is a hub for Wizz Air, and is also used by other low-cost carriers such as Ryanair ... Destinations served including most major European cities, and..." In the current form, the tables are a clear, context-less indiscriminate collection, without providing any useful information. We don't list every single stop of a bus route ('cause we're not a bus schedule website). Likewise, on the exact same grounds, we shouldn't list every single airport served from another one. RandomCanadian (talk / contribs) 12:42, 12 June 2021 (UTC)
It's not an indiscriminate list per WP:DISCRIMINATE, though - it's a very clearly defined list of airlines which serve the airport, and the places they fly to from that airport. They're also not schedules as you seem to imply, that would clearly violate WP:NOT. As someone who looks at this sort of information, I really don't understand why you think readers "shouldn't be using wikipedia for this." SportingFlyer T·C 12:47, 12 June 2021 (UTC)
Listing every element of a set, even if the set is clearly defined, can still be indiscriminate if it serves no useful encyclopedic purpose. Prose is preferred, especially if it can be used to give more context. Describing which type of airlines serve an airport, what the main focus of destinations is, ... is far more relevant context information than leaving an unannotated list which is subject to frequent and non-encyclopedic short-term changes. As I said, it's a WP:BADIDEA. RandomCanadian (talk / contribs) 13:30, 12 June 2021 (UTC)
Again, "no useful encyclopaedic purpose" is your own opinion. We'll see how the discussion plays out. SportingFlyer T·C 13:35, 12 June 2021 (UTC)
The tables provide additional information with clearly given context that you mainly seem to object to because they are complete and up-to-date. WP:NOTPAPER tells us that we are not bound by the limitations of paper-based encyclopaedias, but can "include more information, provide more external links, and update more quickly." Your opinion "without providing any useful information" has already been disproved by other people telling you that they do regard this as useful information. —Kusma (talk) 14:13, 12 June 2021 (UTC)
Thank you. Put exactly what I wanted to say, above. "NOTDIR" can be thrown about with enthusiasm but NOTPAPER should be our guiding principle here. doktorb wordsdeeds 15:04, 12 June 2021 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Last edited on 13 June 2021, at 02:14
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
Desktop
HomeRandomNearbyLog inSettingsDonateAbout WikipediaDisclaimers
LanguageWatchEdit