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.
<noinclude>{{Short description|Page for discussing policies and guidelines}}{{Redirect|WP:VPP|proposals|Misplaced Pages:Village pump (proposals)}}{{village pump page header|Policy|alpha=yes|The '''policy''' section of the ] is intended for discussions about already-proposed ], as well as changes to existing ones. Discussions often begin on other pages and are subsequently moved or referenced here to ensure greater visibility and broader participation.
<noinclude>{{Villagepumppages|Policy discussion|The '''policy''' section of the village pump is used to discuss existing and proposed policies and guidelines.<br>If you want to propose something new, use the '']'' section.<br>
*If you wish to propose something ''new'' that is ''not'' a policy or guideline, use ]. Alternatively, for drafting with a more focused group, consider starting the discussion on the talk page of a relevant WikiProject, the Manual of Style, or another relevant project page.
Please see ''']''' for a list of frequent proposals and the responses to them.
* For questions about how to apply existing policies or guidelines, refer to one of the many ].
|]}}
* If you want to inquire about what the policy is on a specific topic, visit the ] or the ].
* This is '''not the place to resolve disputes''' regarding the implementation of policies. For such cases, consult ].
* For proposals for new or amended speedy deletion criteria, use ].
Please see ''']''' for a list of frequently rejected or ignored proposals. Discussions are automatically archived after two weeks of inactivity.<!--
{| class="messagebox" style="background: AntiqueWhite;"
{{discussion top|1=There is a strong consensus that comments that do not represent an actual person's thoughts are not useful in discussions. Thus, if a comment is written entirely by an LLM, it is (in principle) not appropriate. The main topic of debate was the enforceability of this principle. Opinions vary on the reliability of GPTZero, and I would say there is a rough consensus <em>against</em> any form of AI detection that relies solely on it or other automated tools. Overall, however, I see a consensus that '''it is within admins' and closers' discretion to discount, strike, or collapse <em>obvious</em> use of <em>generative</em> LLMs''' or similar AI technologies. This is a ] matter, and as with other WP:DUCK matters, there is not going to be a blackletter definition of "obvious", but I think we can all agree there are some comments that could only ever be LLM-generated. As with other matters of discretion, like behavioral sockpuppetry blocks, experienced users can apply their best judgment, subject to community review.{{pb}}The word "generative" is very, very important here, though. This consensus does not apply to comments where the reasoning is the editor's own, but an LLM has been used to refine their meaning. Editors who are non-fluent speakers, or have developmental or learning disabilities, are welcome to edit here as long as they can follow our policies and guidelines; this consensus should not be taken to deny them the option of using assistive technologies to improve their comments. In practice, this sets a good lower bound for obviousness, as any comment that could conceivably be LLM-assisted is, by definition, not obviously LLM-generated.{{pb}}Regarding comments that are more borderline in LLM likelihood, it's worth reviewing what's already allowed by policy and guidelines: LLM-written comments will usually add little of substance to a discussion, and closers are already expected to ignore unhelpful comments. If comments contain fabrications of fact, that is a blockable form of ], whether or not the fabrication is by a human or a hallucinating chatbot. And while ] says disruptive comments "are usually best left as-is or archived", there <em>is</em> a "usually" in there, so removing patently disruptive content is within editors' discretion, whether or not LLM usage is unambiguous. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 21:21, 12 January 2025 (UTC)}}
|-
<!-- ] 01:01, 6 January 2025 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1736125272}}
|This talk page is '''automatically archived''' by ]. Any sections older than '''5''' days are automatically archived to ''']'''. Sections without timestamps are not archived.
Should admins or other users evaluating consensus in a discussion discount, ignore, or strike through or collapse comments found to have been generated by AI/LLM/Chatbots? 00:12, 2 December 2024 (UTC)
|-
|}
Discussions older than 5 days (date of last made comment) are moved ]. These discussions will be kept archived for 9 more days. During this period the discussion can be moved to a relevant talk page if appropriate. After 9 days the discussion can only be found through the page history.
<br clear="all" />
I've recently come across several users in AFD discussions that are using LLMs to generate their remarks there. As many of you are aware, and other such tools are very good at detecting this.
]
I don't feel like any of us signed up for participating in discussions where some of the users are not using their own words but rather letting technology do it for them. Discussions are supposed to be between human editors. If you can't make a coherent argument on your own, you are not competent to be participating in the discussion. I would therefore propose that LLM-generated remarks in discussions should be discounted or ignored, and possibly removed in some manner. ] ] 00:12, 2 December 2024 (UTC)
]
]
]
]
]
]</noinclude>
]
:Should not be deleted or ignored but needs to be clearly identified. ] (]) 16:23, 5 January 2025 (UTC)
<!-- BEGIN WERDNABOT ARCHIVAL CODE --><!-- This page is automatically archived by Werdnabot-->{{User:Werdnabot/Archiver/Linkhere}} <!--This is an empty template, but transcluding it counts as a link, meaning Werdnabot is directed to this page - DO NOT SUBST IT --><!--Werdnabot-Archive Age-5 DoUnreplied-Yes Target-Misplaced Pages:Village pump (policy)/Archive--><!--END WERDNABOT ARCHIVAL CODE-->
===opening comments===
==Most maintenance templates should be placed on the talk page==
*Seems reasonable, as long as the GPTZero (or any tool) score is taken with a grain of salt. GPTZero can be as wrong as AI can be. ] (]) 00:32, 2 December 2024 (UTC)
(The following message, but not the replies posted below it, was copied from ] by ''''']'''''00:14, 1 March 2007 (UTC))...
*Only if the false positive and false negative rate of the tool you are using to detect LLM content is very close to zero. LLM detectors tend to be very unreliable on, among other things, text written by non-native speakers. Unless the tool is near perfect then it's just dismissing arguments based on who wrote them rather than their content, which is not what we do or should be doing around here. ] (]) 00:55, 2 December 2024 (UTC)
*:In the cases I have seen thusfar it's been pretty obvious, the tools have just confirmed it. ] ] 04:08, 2 December 2024 (UTC)
*:The more I read the comments from other editors on this, the more I'm a convinced that implementing either this policy or something like it will bring very significant downsides on multiple fronts that significantly outweigh the small benefits this would (unreliably) bring, benefits that would be achieved by simply reminding closers to disregard comments that are unintelligible, meaningless and/or irrelevant regardless of whether they are LLM-generated or not. For the sake of the project I must withdraw my previous very qualified support and instead '''very strongly oppose'''. ] (]) 02:45, 3 December 2024 (UTC)
*I think it should be an expressly legitimate factor in considering whether to discount or ignore comments either if it's clear enough by the text or if the user clearly has a history of using LLMs. We wouldn't treat a comment an editor didn't actually write as an honest articulation of their views in lieu of site policy in any other situation. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 00:59, 2 December 2024 (UTC)
* I would have already expected admins to exercise discretion in this regard, as text written by an LLM is not text written by a person. We cannot guarantee it is what the person actually means, especially as it is a tool often used by those with less English proficiency, which means perhaps they cannot evaluate the text themselves. However, I do not think we can make policy about a specific LLM or tool. The LLM space is moving fast, en.wiki policies do not. Removal seems tricky, I would prefer admins exercise discretion instead, as they do with potentially canvassed or socked !votes. ] (]) 01:06, 2 December 2024 (UTC)
*:As the discussion has moved forward below, I feel I can shift to a more explicit '''support''' in terms of providing guidance to closers and those otherwise evaluating consensus. ] (]) 17:33, 2 January 2025 (UTC)
*'''Support''' discounting or collapsing AI-generated comments, under ''slightly looser'' conditions than those for human comments. Not every apparently-AI-generated comment is useless ] nonsense{{snd}}beyond false positives, it's also possible for someone to use an AI to help them word a constructive comment, and make sure that it matches their intentions before they publish it. But in my experience, the majority of AI-generated comments are somewhere between "pointless" and "disruptive". Admins should already discount ''clearly'' insubstantial !votes, and collapse ''clearly'' unconstructive lengthy comments; I think we should recognize that blatant chatbot responses are more likely to fall into those categories. ] (]) 02:11, 2 December 2024 (UTC)
*'''Strongly Support''' - I think some level of human judgement on the merits of the argument are necessary, especially as GPTZero may still have a high FPR. Still, if the discussion is BLUDGEONy, or if it quacks like an AI-duck, looks like an AI-duck, etc, we should consider striking out such content.{{pb
}}- sidenote, I'd also be in favor of sanctions against users who overuse AI to write out their arguments/articles/etc. and waste folks time on here.. ] (]) 02:20, 2 December 2024 (UTC)
*On a wording note, I think any guidance should avoid referring to any specific technology. I suggest saying "... to have been generated by a program". ] (]) 02:54, 2 December 2024 (UTC)
*:"generated by a program" is too broad, as that would include things like speech-to-text. ] (]) 03:08, 2 December 2024 (UTC)
*:Besides what Thryduulf said, I think we should engage with editors who use translators. ] (]) 03:45, 2 December 2024 (UTC)
*::A translation program, whether it is between languages or from speech, is not generating a comment, but converting it from one format to another. A full policy statement can be more explicit in defining "generation". The point is that the underlying tech doesn't matter; it's that the comment didn't feature original thought from a human. ] (]) 03:57, 2 December 2024 (UTC)
*:::Taking Google Translate as an example, most of the basic stuff uses "AI" in the sense of machine learning () but they nowadays, even for the basic free product. ] (]) 08:39, 2 December 2024 (UTC)
*'''Support'''. We already use discretion in collapsing etc. comments by SPAs and suspected socks, it makes sense to use the same discretion for comments suspected of being generated by a non-human. ] (]) 03:07, 2 December 2024 (UTC)
*'''Support''' - Someone posting "here's what ChatGPT has to say on the subject" can waste a lot of other editors' time if they feel obligated to explain why ChatGPT is wrong again. I'm not sure how to detect AI-written text but we should take a stance that it isn't sanctioned. ] (] <nowiki>|</nowiki> ]) 04:37, 2 December 2024 (UTC)
*'''Strong Support''' - I've never supported using generative AI in civil discourse. Using AI to participate in these discussions is pure laziness, as it is substituting genuine engagement and critical thought with a robot prone to outputting complete garbage. In my opinion, if you are too lazy to engage in the discussion yourself, why should we engage with you? ] (]) 05:26, 2 December 2024 (UTC)
*'''Comment''' - I'm skeptical that a rule like this will be enforceable for much longer. ] (]) 05:39, 2 December 2024 (UTC)
*:Why? ] (]) 12:22, 2 December 2024 (UTC)
*::Because it's based on a potentially false premise that it will be possible to reliably distinguish between text generated by human biological neural networks and text generated by non-biological neural networks by observing the text. It is already quite difficult in many cases, and the difficulty is increasing very rapidly. I have your basic primate brain. The AI companies building foundation models have billions of dollars, tens of thousands, soon to be hundreds of thousands of GPUs, a financial incentive to crack this problem and scaling laws on their side. So, I have very low credence in the notion that I will be able to tell whether content is generated by a person or a person+LLM or an AI agent very soon. On the plus side, it will probably still be easy to spot people making non-policy based arguments regardless of how they do it. ] (]) 13:52, 2 December 2024 (UTC)
*::...and now that the systems are autonomously injecting their output back into model via chain-of-thought prompting, or a kind of inner monologue if you like, to respond to questions, they are becoming a little bit more like us. ] (]) 14:14, 2 December 2024 (UTC)
*:::A ] is intrinsically nothing like a human. It's a bunch of algebra that can compute what a decently sensible person could write in a given situation based on its training data, but it is utterly incapable of anything that could be considered thought or reasoning. This is why LLMs tend to fail spectacularly when asked to do math or write non-trivial code. ] (]) 17:20, 2 December 2024 (UTC)
*::::We shall see. You might want to update yourself on their ability to do math and write non-trivial code. Things are changing very quickly. Either way, it is not currently possible to say much about what LLMs are actually doing because mechanistic interpretability is in its infancy. ] (]) 03:44, 3 December 2024 (UTC)
*::::You might be interested in Anthropic's '' and Chris Olah's work in general. ] (]) 04:02, 3 December 2024 (UTC)
*'''Support''' and I would add "or similar technologies" to "AI/LLM/Chatbots". As for Sean.hoyland's comment, we will cross that bridge when we get to it. ] (]) 05:51, 2 December 2024 (UTC)
*:...assuming we can see the bridge and haven't already crossed it. ] (]) 06:24, 2 December 2024 (UTC)
*'''Support''' - All editors should convey their thoughts in their own words. AI generated responses and comments are disruptive because they are pointless and not meaningful. - ] (]) 06:04, 2 December 2024 (UTC)
*'''Support''', I already more or less do this. An LLM generated comment may or may not actually reflect the actual thoughts of the editor who posted it, so it's essentially worthless toward a determination of consensus. Since I wrote this comment myself, you know that it reflects ''my'' thoughts, not those of a bot that I may or may not have reviewed prior to copying and pasting. ] <small><sup>]</sup></small> 06:59, 2 December 2024 (UTC)
*'''Strong oppose'''. Let me say first that I do not like ChatGPT. I think it has been a net negative for the world, and it is by nature a net negative for the physical environment. It is absolutely a net negative for the encyclopedia if LLM-generated text is used in articles in any capacity. However, hallucinations are less of an issue on talk pages because they're discussions. If ChatGPT spits out a citation of a false policy, then obviously that comment is useless. If ChatGPT spits out some boilerplate "Thanks for reviewing the article, I will review your suggestions and take them into account" talk page reply, who gives a fuck where it came from? (besides the guys in Texas getting their eardrums blown out because they live by the data center){{pb
}}The main reason I oppose, though, is because banning LLM-generated comments is difficult to enforce bordering on unenforceable. Most studies show that humans are bad at distinguishing AI-generated text from text generated without AI. Tools like GPTZero claims a 99% accuracy rate, but that seems dubious based on reporting on the matter. The news outlet Futurism (which generally has an anti-AI slant) has failed many times to replicate that statistic, and anecdotal accounts by teachers, etc. are rampant. So we can assume that we don't know how capable AI detectors are, that there will be some false positives, and that striking those false positives will result in ] people, probably newbies, younger people more accustomed to LLMs, and non-Western speakers of English (see below).{{pb
}}There are also technological issues as play. It'd be easy if there was a clean line between "totally AI-generated text" and "totally human-generated text," but that line is smudged and well on its way to erased. Every tech company is shoving AI text wrangling into their products. This includes autocomplete, translation, editing apps, etc. Should we strike any comment a person used Grammarly or Google Translate for? Because those absolutely use AI now.{{pb
}}And there are ''also'', as mentioned above, cultural issues. The people using Grammarly, machine translation, or other such services are likely to not have English as their first language. And a lot of the supposed "tells" of AI-generated content originate in the formal English of other countries -- for instance, the whole thing where "delve" was supposedly a tell for AI-written content until people pointed out the fact that lots of Nigerian workers trained the LLM and "delve" is common Nigerian formal English.{{pb
}}I didn't use ChatGPT to generate any of this comment. But I am also pretty confident that if I did, I could have slipped it in and nobody would have noticed until this sentence. ] (]) 08:31, 2 December 2024 (UTC)
*:Just for grins, I ran your comment through GPTzero, and it comes up with a 99% probability that it was human-written (and it never struck me as looking like AI either, and I can often tell.) So, maybe it's more possible to distinguish than you think? ] <small><sup>]</sup></small> 20:11, 2 December 2024 (UTC)
*::Yeah, Gnoming's writing style is far more direct and active than GPT's. ] (]) 23:02, 2 December 2024 (UTC)
*:::There weren't
*:::*'''Multiple'''
*:::*:LLMs tend to use more than one subheading to reiterate points
*:::*'''Subheadings'''
*:::*:Because they write like a middle schooler that just learned how to make an essay outline before writing.
*:::In conclusion, they also tend to have a conclusion paragraph for the same reason they use subheadings. ] (]) 13:56, 3 December 2024 (UTC)
*'''Support''' - Ai-generated comments are ] - An editor who has an argument should not use ChatGPT to present it in an unnecessarily verbose manner, and an editor who doesn't have one should not participate in discussion. ] (]) 13:14, 2 December 2024 (UTC)
*'''Yes''' but why do we need this common sense RFC/policy/whatever? Just ban these people. If they even exist.  <span style="font-variant:small-caps; whitespace:nowrap;">] {] · ] · ] · ]}</span> 07:14, 2 December 2024 (UTC)
*:They exist, and I found myself collapsing some long, obviously chatbot-generated posts in an AFD, and after I did so wondering if policy actually supported doing that. I couldn't find anything so here we are. ] ] 20:04, 2 December 2024 (UTC)
*{{anchor|ChaptGPT_agrees}}'''Yes, of course''', and I know that's the right answer because ChatGPT agrees with me.
::{{tq|Currently at the English Misplaced Pages, there's a discussion of the following proposal: "Should or other users evaluating consensus in a discussion discount, ignore, or strike through or collapse comments found to have been generated by AI/LLM/Chatbots?" I wonder if you have an opinion on that question.}}
:My friend the bot initially proposed a requirement that any AI-generated content be labeled as such by the person posting it. After some further discussion between us, I finally said:
::{{tq|You say that labeling AI-generated content, instead of outright discounting it, might be an appropriate middle ground. But if someone is unable to formulate their own thoughts and put them in writing, of what use is it to the discussion for this person to simply ask you to make something up, and then post your output to the Misplaced Pages discussion with the proviso that "ChatGPT, who/which doesn't actually know anything about anything, said this ..."? How is it different from saying, "My grandmother, who knows nothing about what we're talking about, said ..."?}}
:And it said:
::{{tq|That’s an incisive question, and it highlights the crux of the issue: the value of contributions to a discussion. Here’s why AI-generated comments might still differ (slightly) from your hypothetical grandmother’s input, but why their usefulness is often limited:}}
::*{{tq|'''Synthesis vs. Subject Expertise:''' While I (or any AI) lack personal understanding or expertise, I can aggregate and articulate relevant ideas from a vast dataset. This means I can sometimes present arguments, summarize perspectives, or surface considerations that a non-expert human might overlook. Your grandmother, unless she's an AI-trained polymath, wouldn’t be able to provide this breadth. However, this advantage evaporates if participants lack the ability to evaluate and critically engage with my output.}}
::*{{tq|'''The Problem of Proxy Voices:''' The act of outsourcing one’s contribution to AI undermines the deliberative process central to Misplaced Pages’s discussions. Participants are expected to bring their own informed perspectives, shaped by personal understanding of Misplaced Pages’s policies and content. A disclaimer like “ChatGPT said this” doesn’t change the fact that the human posting it has abdicated their role in the discussion.}}
::*{{tq|'''Accountability and Intent:''' In a collaborative setting like Misplaced Pages, contributions are ideally linked to a person who can clarify their intent, respond to questions, and engage dynamically. An AI cannot do this. Saying "ChatGPT said this" distances the poster from the content, making it unclear whether they endorse or even understand the comment.}}
::*{{tq|'''Potential for Misdirection:''' Allowing AI-generated contributions risks introducing noise into the discussion. AI can produce plausible-sounding arguments that may be tangential, misaligned, or even factually incorrect. Without the judgment of a well-informed poster, such contributions can derail or dilute meaningful discourse.}}
::{{tq|'''Conclusion:''' If someone cannot formulate their own argument or understanding, then their reliance on an AI—or anyone else—to contribute doesn’t meaningfully advance the discussion. Labeling AI-generated content is better than passing it off as human, but the real issue lies in whether such contributions enrich or degrade the collaborative process. In most cases, they would seem to belong more to the realm of rhetorical curiosities than substantive engagement.}}
{{collapse bottom}}
*<li style="list-style:none;">In keeping with the proposed guideline, I have of course collapsed the above AI-generated content. (Later: It's actually worth reading in the context of this discussioin, so I've unhidden it by default.) But I must confess it's a pretty good analysis, and worth reading. ]] 07:47, 2 December 2024 (UTC)</li>
*:This is absolute gold dust and the best contribution to this discussion so far. There is an enormous irony here, one that might not be immediately obvious. The proposal is that we should ignore or even strike these type of contributions, but personally it seems like the collapsed format has worked a charm here. I really don't think that AI has much to contribute to WP discussions generally, but with the right prompt, there is certainly something worth adding to the conversation in reality. ] (]) 20:23, 8 December 2024 (UTC)
*::The proposal also includes collapsing. ] (]) 20:26, 8 December 2024 (UTC)
*:::Thanks, I completely missed that. Trying to speed read is not my forte. ] (]) 20:32, 8 December 2024 (UTC)
:The "detector" website linked in the opening comment gives your chatbot's reply only an 81% chance of being AI-generated. ] (]) 23:36, 2 December 2024 (UTC)
::That's because, just by interacting with me, ChatGPT got smarter. Seriously ... you want it to say 99% every time? (And for the record, the idea of determining the "chance" that something is AI-generated is statistical nonsense.) ]] 03:07, 3 December 2024 (UTC)
:::What I really want is a 100% chance that it won't decide that what I've written is AI-generated. Past testing has demonstrated that at least some of the detectors are unreliable on this point. ] (]) 03:28, 4 December 2024 (UTC)
::::100% is, of course, an impossible goal. Certainly SPI doesn't achieve that, so why demand it here? ]] 22:31, 4 December 2024 (UTC)
:::::Even a miniscule chance of quashing a human writer's contributions is too high of a risk. ] (]) 06:09, 6 January 2025 (UTC)
*<del>'''Strong Oppose''' I support the concept of removal of AI-generated content in theory. However, we do not have the means to detect such AI-generated content. The proposed platform that we may use (GPTZero) is not reliable for this purpose. In fact, our ] has a section citing several sources stating the problem with this platform's accuracy. It is not helpful to have a policy that is impossible to enforce. ] <sup>] / ]</sup> 08:46, 2 December 2024 (UTC) </del>
*'''Strong Support''' To be honest, I am surprised that this isn't covered by an existing policy. I oppose the use of platforms like GPTZero, due to it's unreliability, but if it is obviously an ai-powered-duck (Like if it is saying shit like "as an AI language model...", take it down and sanction the editor who put it up there. ] <sup>] / ]</sup> 08:54, 2 December 2024 (UTC)
*'''Support''' at least for ]-level AI-generated comments. If someone uses a LLM to translate or improve their own writing, there should be more leeway, but something that is clearly a pure ChatGPT output should be discounted. ] (] · ]) 09:17, 2 December 2024 (UTC)
* I agree for cases in which it is uncontroversial that a comment is purely AI-generated. However, I don't think there are many cases where this is obvious. The claim that {{green|gptzero and other such tools are very good at detecting this}} is false. ] (]) 09:43, 2 December 2024 (UTC)
*'''Support''' Not clear how admins are deciding that something is LLM generated, , agree with the principle tho. ] (]) 10:02, 2 December 2024 (UTC)
* '''Moral support; neutral as written'''. Chatbot participation in consensus discussions is such an utterly pointless and disdainful abuse of process and community eyeballs that I don't feel like the verbiage presented goes far enough. {{Xt|Any editor may hat LLM-generated comments in consensus discussions}} is nearer my position. No waiting for the closer, no mere discounting, no reliance on the closer's personal skill at recognising LLM output, immediate feedback to the editor copypasting chatbot output that their behaviour is unwelcome and unacceptable. Some observations:{{pb}}I've seen editors accused of using LLMs to generate their comments probably about a dozen times, and in all but two cases – both at dramaboards – the chatbot prose was unmistakably, blindingly obvious. Editors already treat non-obvious cases as if written by a human, in alignment with the raft of {{tqq|only if we're sure}} caveats in every discussion about LLM use on the project.{{pb}}If people are using LLMs to punch up prose, correct grammar and spelling, or other superficial tasks, this is generally undetectable, unproblematic, and not the point here.{{pb}}Humans are superior to external services at detecting LLM output, and no evidence from those services should be required for anything.{{pb}}As a disclosure, evidence mounts that LLM usage in discussions elicits maximally unkind responses from me. It just feels so contemptuous, to assume that any of us care what a chatbot has to say about anything we're discussing, and that we're all too stupid to see through the misattribution because someone tacked on a sig and sometimes an introductory paragraph. And I say this as a stupid person. ] (]) 11:20, 2 December 2024 (UTC)
*:'''Looks like a rewrite is indicated''' to distinguish between {{xt|machine translation}} and {{!xt|LLM-generated comments}}, based on what I'm seeing in this thread. Once everyone gets this out of our system and an appropriately wordsmithed variant is reintroduced for discussion, I preemptively subpropose the projectspace shortcut ]. ] (]) 15:26, 8 December 2024 (UTC)
*'''Support''' per EEng ] ] 14:21, 2 December 2024 (UTC)
*I would be careful here, as there are tools that rely on LLM AI that help to improve the clarity of one's writing, and editors may opt to use those to parse their poor writing (perhaps due to ESL aspects) to something clear. I would agree content 100% generated by AI probably should be discounted particularly if from an IP or new editors (hints if socking or meat puppetry) but not all cases where AI has come into play should be discounted<span id="Masem:1733149152126:WikipediaFTTCLNVillage_pump_(policy)" class="FTTCmt"> — ] (]) 14:19, 2 December 2024 (UTC)</span>
*'''Support''', cheating should have no place or take its place in writing coherent comments on Misplaced Pages. Editors who opt to use it should practice writing until they rival Shakespeare, or at least his cousin Ned from across the river, and then come back to edit. ] (]) 14:29, 2 December 2024 (UTC)
*'''Support''' atleast for comments that are copied straight from the LLM . However, we should be more lenient if the content is rephrased by non-native English speakers due to grammar issues ] (]) 15:10, 2 December 2024 (UTC)
===section break 1===
I have a couple of friends who work in the visual electronic entertainment industry. I now avoid watching anything with them because instead of enjoying the film or television program, they sit there commenting on technical features in the film, lighting, cuts etc. I think that with people who regularly edit Misplaced Pages articles instead of viewing articles for the information they contain (as most readers do) they view the article for how well put together it is and if it can be improved.
* '''Support''' for LLM-'''generated''' content (until AI is actually intelligent enough to create an account and contribute on a human level, ]). However, beware of the fact that some LLM-'''assisted''' content should probably be allowed. An extreme example of this: if a non-native English speaker were to write a perfectly coherent reason in a foreign language, and have an LLM translate it to English, it should be perfectly acceptable. ] ] 16:47, 2 December 2024 (UTC)
*:For wiki content, maybe very soon. 'contribute of a human level' in a narrow domain. ] (]) 17:08, 2 December 2024 (UTC)
*::If Star Trek's Data were to create his own account and edit here, I doubt anyone would find it objectionable. ] ] 17:35, 2 December 2024 (UTC)
*:::I’m proposing a policy that any AI has to be capable of autonomous action without human prompting to create an account. ] (]) 21:38, 5 December 2024 (UTC)
*:::<small>Data, being a fictional creation with rights owned by a corporation, will not have an account; he is inherently an IP editor. -- ] (]) 03:22, 20 December 2024 (UTC)</small>
*'''Strong support''' chatbots have no place in our encyclopedia project. ] (]) 17:14, 2 December 2024 (UTC)
*'''Oppose''' - I think the supporters must have a specific type of AI-generated content in mind, but this isn't a prohibition on one type; it's a prohibition on the use of generative AI in discussions (or rather, ensuring that anyone who relies on such a tool will have their opinion discounted). We allow people who aren't native English speakers to contribute here. We also allow people who are native English speakers but have difficulty with language (but not with thinking). LLMs are good at assisting both of these groups of people. Furthermore, as others pointed out, detection is not foolproof and will only get worse as time goes on, models proliferate, models adapt, and users of the tools adapt. This proposal is a blunt instrument. If someone is filling discussions with pointless chatbot fluff, or we get a brand new user who's clearly using a chatbot to feign understanding of wikipolicy, of ''course'' that's not ok. But ''that is a case by case behavioral issue''. I think the better move would be to clarify that "some forms of LLM use can be considered ] and may be met with restrictions or blocks" without making it a black-and-white issue. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 17:32, 2 December 2024 (UTC)
*:I agree the focus should not be on whether or not a particular kind of tech was used by an editor, but whether or not the comment was generated in a way (whether it's using a program or ghost writer) such that it fails to express actual thoughts by the editor. (Output from a speech-to-text program using an underlying large language model, for instance, isn't a problem.) Given that this is often hard to determine from a single comment (everyone is prone to post an occasional comment that others will consider to be off-topic and irrelevant), I think that patterns of behaviour should be examined. ] (]) 18:07, 2 December 2024 (UTC)
*::Here's what I see as two sides of a line. The first is, I think, something we can agree would be inappropriate. The second, to me at least, pushes up against the line but is not ultimately inappropriate. But they would both be prohibited if this passes. (a) "I don't want an article on X to be deleted on Misplaced Pages. Tell me what to say that will convince people not to delete it"; (b) "I know Misplaced Pages deletes articles based on how much coverage they've received in newspapers, magazines, etc. and I see several such articles, but I don't know how to articulate this using wikipedia jargon. Give me an argument based on links to wikipedia policy that use the following sources as proof ". Further into the "acceptable" range would be things like translations, grammar checks, writing a paragraph and having an LLM improve the writing without changing the ideas, using an LLM to organize ideas, etc. I think what we want to avoid are situations where the ''arguments and ideas themselves'' are produced by AI, but I don't see such a line drawn here and I don't think we could draw a line without more flexible language. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 18:47, 2 December 2024 (UTC)
*::Here we return to my distinction between AI-generated and AI-assisted. A decent speech-to-text program doesn't actually generate content. ] ] 18:47, 2 December 2024 (UTC)
*:::Yes, as I ], the underlying tech isn't important (and will change). Comments should reflect what the author is thinking. Tools (or people providing advice) that help authors express their personal thoughts have been in use for a long time. ] (]) 19:08, 2 December 2024 (UTC)
*::::Yeah the point here is passing off a machine's words as your own, and the fact that it is often fairly obvious when one is doing so. If a person is not competent to express their own thoughts in plain English, they shouldn't be in the discussion. This certainly is not aimed at assistive technology for those who actually need it but rather at persons who are simply letting Chatbots speak for them. ] ] 20:10, 2 December 2024 (UTC)
*:::::This doesn't address what I wrote (though maybe it's not meant to). {{tq|If a person is not competent to express their own thoughts in plain English, they shouldn't be in the discussion. This certainly is not aimed at assistive technology for those who actually need it but rather at persons who are simply letting Chatbots speak for them}} is just contradictory. Assistive technologies are those that can help people who aren't "competent" to express themselves to your satisfaction in plain English, sometimes helping with the formulation of a sentence based on the person's own ideas. There's a difference between having a tool that helps me to articulate ideas ''that are my own'' and a tool that ''comes up with the ideas''. That's the distinction we should be making. — <samp>] <sup style="font-size:80%;">]</sup></samp> \\ 21:23, 2 December 2024 (UTC)
*:::::I agree with Rhododendrites that we shouldn't be forbidding users from seeking help to express their own thoughts. Getting help from someone more fluent in English, for example, is a good practice. Nowadays, some people use generative technology to help them prepare an outline of their thoughts, so they can use it as a starting point. I think the community should be accepting of those who are finding ways to write their own viewpoints more effectively and concisely, even if that means getting help from someone or a program. I agree that using generative technology to come up with the viewpoints isn't beneficial for discussion. ] (]) 22:58, 2 December 2024 (UTC)
*:Non-native English speakers and non-speakers to whom a discussion is important enough can already use machine translation from their original language and usually say something like "Sorry, I'm using machine translation". ] (]) 08:34, 4 December 2024 (UTC)
*'''Oppose''' Contributions to discussions are supposed to be evaluated on their merits per ]. If an AI-assisted contribution makes sense then it should be accepted as helpful. And the technical spectrum of assistance seems large and growing. For example, as I type this into the edit window, some part of the interface is spell-checking and highlighting words that it doesn't recognise. I'm not sure if that's coming from the browser or the edit software or what but it's quite helpful and I'm not sure how to turn it off. ]🐉(]) 18:17, 2 December 2024 (UTC)
*:But we're not talking about spell-checking. We're talking about comments clearly generated by LLMs, which are inherently unhelpful. ] (]) 18:29, 2 December 2024 (UTC)
*::Yeah, spellchecking is not the issue here. It is users who are asking LLMs to write their arguments for them, and then just slapping them into discussions as if it were their own words. ] ] 20:12, 2 December 2024 (UTC)
*:::Andrew's first two sentences also seem to imply that he views AI-generated arguments that makes sense as valid, and that we should consider what AI thinks about a topic. I'm not sure what to think about this, especially since AI can miss out on a lot of the context. ] (]) 23:04, 2 December 2024 (UTC)
*::::Written arguments are supposed to be considered on their merits as objects in their own right. Denigrating an argument by reference to its author is '']'' and that ranks low in the ] – "{{tq|attacks the characteristics or authority of the writer without addressing the substance of the argument}}". ]🐉(]) 23:36, 2 December 2024 (UTC)
*::::::An AI chatbot isn't an "author", and it's impossible to make an ''ad hominem'' attack on one, because a chotbot is not a ''homo''. ]] 17:45, 6 December 2024 (UTC)
*:::::::{{small|Well, not all of them, anyway. ], maybe?}} ] (]) 17:51, 6 December 2024 (UTC)
*:::::On the other hand, "exhausting the community's patience"/CompetenceIsRequired is a very valid rationale from stopping someone from partricipating. ] (]) 23:50, 2 December 2024 (UTC)
*:::The spell-checking was an immediate example but there's a spectrum of AI tools and assistance. The proposed plan is to use an AI tool to detect and ban AI contributions. That's ludicrous hypocrisy but suggests an even better idea – that we use AIs to close discussions so that we don't get the bias and super-voting. I see this on Amazon regularly now as it uses an AI to summarise the consensus of product reviews. For example,{{tqb|Customers say<br />Customers appreciate the gloves for their value, ease of use, and gardening purposes. They find the gloves comfortable and suitable for tasks like pruning or mowing. However, opinions differ on how well they fit.<br />AI-generated from the text of customer reviews}}Yes, AI assistants have good potential. My !vote stands. ]🐉(]) 23:23, 2 December 2024 (UTC)
*::::Let's not get into tangents here. ] (]) 23:51, 2 December 2024 (UTC)
*:::::It's better than going around in circles. ]] 03:07, 3 December 2024 (UTC)
===section break 2===
One manifestation of this I have noticed, which in my opinion is the growing tendency, is to add what are editorial comments to the article page instead of on to the talk page. If a person edits an article page and write in plain text. "This page is not good enough it needs more information" the comment will either be moved to the talk page or it will be deleted as vandalism. However if a person puts a template at the top of a page then they feel that is justified (eg {{tl|cleanup-bio}}, but in essence it is contributing nothing more to the article than the plain text does.
*::::I asked Google's ] to "summarise the consensus of the following RFC discussion", giving it the 87 comments to date.
{{cot|width=80%|title=AI summary of the RfC to date}}
This Misplaced Pages Request for Comment (RfC) debates whether comments in discussions that are found to be generated by AI/LLM/Chatbots should be discounted, ignored, or removed.
Arguments for discounting/removing AI-generated comments:
There are exceptions to this, for example I think that the {{tl|unreferenced}} placed in a "Reference" section at the bottom of an article, serves a dual purpose. It is a maintenance template but it also adds information that a passing reader of the page (who is not familiar with Wikipeda) needs to know. But a passing reader does not need to know
* AI comments don't represent genuine human engagement or thought. They can be disruptive, waste time, and even fabricate information.
{{tl|wikify}} "This article (or section) may need to be wikified to meet Misplaced Pages's quality standards." Comments like this should in my opinion be placed on talk page. --] 09:45, 10 February 2007 (UTC)
* AI can be used to manipulate discussions. Editors might use AI to generate arguments they don't actually believe in, or to flood discussions with low-quality comments.
* Relying on AI undermines the integrity of Misplaced Pages's consensus-based process. Discussions should be based on the genuine opinions of human editors.
Arguments against discounting/removing AI-generated comments:
: I agree completely. Tag clutter is a growing problem, and it detracts from the quality of the encyclopedia. So if an article has unwiki formatting, someone comes along and adds a tag or two that make the article even worse and more unencyclopedic. Clean up projects are misnamed, as they are virtually spreading litter everywhere. Pretty soon we're going to need clean up projects just to clean up the mess created by the current clean up projects. ''''']'''''00:16, 1 March 2007 (UTC)
* Difficulty of detection. AI detection tools are not always reliable, and it can be hard to distinguish between AI-generated text and human-written text, especially as AI technology improves.
* Potential for misuse. False positives could lead to legitimate comments being dismissed, potentially silencing non-native English speakers or those who use AI for legitimate assistive purposes (e.g., translation, grammar checks).
* Focus on content, not origin. Comments should be evaluated based on their merits, not on how they were generated. If an AI-generated comment is relevant and well-reasoned, it shouldn't be dismissed simply because of its origin.
* LLMs can be helpful tools. LLMs can help editors express their thoughts more clearly, especially for non-native speakers or those with language difficulties.
Current Status (as of Dec 3rd, 2024):
: I do quite a bit of WikiGnoming, which means I spend a lot of time nosing around in categories like Articles needing to be Wikified, etc. From an organizational standpoint, I think that these could easily be just categories added to the page, rather than huge banners at the top of the page. However, if a new user comes across a page that has no wiki markup, that user might think that this is the style he or she should strive for while editing. Really, the article's content serves two almost opposing purposes for editors and for readers. And, I admit, I've added necessary wiki tags to articles for purely political purposes, meaning that I disagreed with the content of the article but rather than risk any sort of edit war or conflict, I just added cleanup tags so that ''someone else'' would take care of it! -] (]) 20:17, 1 March 2007 (UTC)
* No clear consensus has emerged. There is significant support for discounting or removing AI-generated comments, but also strong opposition.
* Concerns about enforceability and potential harm. Many editors are worried about the practical challenges of implementing and enforcing such a rule, as well as the potential for it to be used unfairly against certain editors.
* Ongoing discussion. The discussion is still active, and it remains to be seen whether a consensus will form.
It's important to note that this is an evolving situation, and the outcome of the RfC could have significant implications for how Misplaced Pages handles AI-generated content in the future.
=== Replace all tags with a single icon? ===
{{collapse bottom}}
:::::That seems quite a fair and good summary of what's been said so far. I'm impressed and so my !vote stands.
:::::]🐉(]) 09:26, 3 December 2024 (UTC)
::::::I have significant doubts on its ability to weigh arguments and volume. ] (]) 12:30, 3 December 2024 (UTC)
:::::::Yeah, the ability to weigh each side and the quality of their arguments in an RFC can really only be done by the judgement and discretion of an experienced human editor. ] (]) 20:08, 4 December 2024 (UTC)
::::::::The quality of the arguments and their relevance to polices and guidelines can indeed only be done by a human, but the AI does a good job of summarising which arguments have been made and a broad brush indication of frequency. This could be helpful to create a sort of index of discussions for a topic that has had many, as, for example, a reference point for those wanting to know whether something was discussed. Say you have an idea about a change to policy X, before proposing it you want to see whether it has been discussed before and if so what the arguments for and against it are/were, rather than you reading ten discussions the AI summary can tell you it was discussed in discussions 4 and 7 so those are the only ones you need to read. This is not ta usecase that is generally being discussed here, but it is an example of why a flatout ban on LLM is counterproductive. ] (]) 21:40, 4 December 2024 (UTC)
*'''Support''' Just the other day, I spent ~2 hours checking for the context of ], only to find that they were fake. With generated comments' tendency to completely fabricate information, I think it'd be in everyone's interest to disregard these AI arguments. Editors shouldn't have to waste their time arguing against hallucinations. ''(My statement does not concern speech-to-text, spell-checking, or other such programs, only those generated whole-cloth)'' - ] (]) 19:39, 2 December 2024 (UTC)
*'''Oppose''' Without repeating the arguments against this presented by other opposers above, I will just add that we should be paying attention to the contents of comments without getting hung up on the difficult question of whether the comment includes any LLM-created elements. - ] 19:45, 2 December 2024 (UTC)
*'''Strong support''' If others editors are not going to put in the effort of writing comments why should anyone put in the effort of replying. Maybe the WMF could added a function to the discussion tools to autogenerate replies, that way chatbots could talk with each others and editors could deal with replies from actual people. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 19:57, 2 December 2024 (UTC)
*:Whatever the outcome of this I won't be putting any effort into replying to posts obviously made by AI. -- <small>LCU</small> ''']''' <small>''«]» °]°''</small> 13:11, 26 December 2024 (UTC)
*'''Strong oppose'''. Comments that are bullshit will get discounted anyways. Valuable comments should be counted. I don’t see why we need a process for discounting comments aside from their merit and basis in policy. <span style="position: relative; top: -0.5em;">꧁</span>]<span style="position: relative; top: -0.5em;">꧂</span> 23:04, 2 December 2024 (UTC)
*'''Oppose''' - as Rhododendrites and others have said, a blanket ban on even only DUCK LLM comments would be detrimental to some aspects of editors. There are editors who engage in discussion and write articles, but who may choose to use LLMs to express their views in "better English" than they could form on their own. Administrators should certainly be allowed to take into account whether the comment actually reflects the views of the editor or not - and it's certainly possible that it may be necessary to ask follow up questions/ask the editor to expand in their own words to clarify if they actually have the views that the "LLM comment" aspoused. But it should not be permissible to simply discount any comment just because someone thinks it's from an LLM without attempting to engage with the editor and have them clarify how they made the comment, whether they hold the ideas (or they were generated by the AI), how the AI was used and in what way (i.e. just for grammar correction, etc). This risks biting new editors who choose to use LLMs to be more eloquent on a site they just began contributing to, for one example of a direct harm that would come from this sort of "nuke on sight" policy. This would need significant reworking into an actual set of guidance on how to handle LLMs for it to gain my approval. -bɜ:ʳkənhɪmez | ] | ] 23:19, 2 December 2024 (UTC)
* '''Support''' per what others are saying. And more WP:Ducks while at it… <span style="color:#7E790E;">2601AC47</span> (]<big>·</big>]<big>·</big>]) <span style="font-size:80%">Isn't a IP anon</span> 00:36, 3 December 2024 (UTC)
*:{{comment}} It would appear Jimbo responded indirectly in a interview: {{tq|as long as there’s a human in the loop, a human supervising, there are really potentially very good use cases.}} <span style="color:#7E790E;">2601AC47</span> (]<big>·</big>]<big>·</big>]) <span style="font-size:80%">Isn't a IP anon</span> 12:39, 4 December 2024 (UTC)
*'''Very strong support'''. Enough is enough. If Misplaced Pages is to survive as a project, we need zero tolerance for even the suspicion of AI generation and, with it, zero tolerance for generative AI apologists who would happily open the door to converting the site to yet more AI slop. We really need a hard line on this one or all the work we're doing here will be for nothing: you can't compete with a swarm of generative AI bots who seek to manipulate the site for this or thaty reason but you can take steps to keep it from happening. ] (]) 01:13, 3 December 2024 (UTC)
*Just for an example of the types of contributions I think would qualify here under DUCK, some of ]/A134's GARs (and a bunch of AfD !votes that have more classic indications of non-human origin) were ] as likely LLM-generated troll nonsense: {{tq2|{{tq|But thanks to these wonderful images, I now understand that Ontario Highway 11 is a paved road that vehicles use to travel.}} {{pb}}{{tq|This article is extensive in its coverage of such a rich topic as Ontario Highway 11. It addresses the main points of Ontario Highway 11 in a way that isn’t just understandable to a reader, but also relatable.}}{{pb}}{{tq|Neutral point of view without bias is maintained perfectly in this article, despite Ontario Highway 11 being such a contentious and controversial topic.}}}}{{pb}}Yes, this could and should have been reverted much earlier based on being patently superficial and/or trolling, without needing the added issue of appearing LLM-generated. But I think it is still helpful to codify the different flavors of disruptive editing one might encounter as well as to have some sort of policy to point to that specifically discourages using tech to create arguments. {{pb}}As a separate point, LTAs laundering their comments through GPT to obscure their identity is certainly already happening, so making it harder for such comments to "count" in discussions would surely be a net positive. ] (]) 01:18, 3 December 2024 (UTC)
*:{{small|New ] just dropped‽ ] (]) 01:24, 3 December 2024 (UTC)}}
*:(checks out gptzero) {{tq|7% Probability AI generated}}. Am I using it wrong? <span style="color:#7E790E;">2601AC47</span> (]<big>·</big>]<big>·</big>]) <span style="font-size:80%">Isn't a IP anon</span> 01:28, 3 December 2024 (UTC)
*::In my experience, GPTZero is more consistent if you give it full paragraphs, rather than single sentences out of context. Unfortunately, the original contents of ] are only visible to admins now. ] (]) 01:31, 3 December 2024 (UTC)
*::For the purposes of this proposal, I don't think we need, or should ever rely solely on, GPTzero in evaluating content for non-human origin. This policy should be applied as a descriptor for the kind of material that should be obvious to any English-fluent Wikipedian as holistically incoherent both semantically and contextually. Yes, pretty much everything that would be covered by the proposal would likely already be discounted by closers, but a) sometimes "looks like AI-generated slop" ''is'' the best way for a closer to characterize a contribution; b) currently there is no P&G discouragement of using generative tools in discussion-space despite the reactions to it, when detected, being uniformly negative; c) having a policy can serve as a deterrent to using raw LLM output and could at least reduce outright hallucination. ] (]) 02:17, 3 December 2024 (UTC)
*:::If the aim is to encourage closers to disregard comments that are incoherent either semantically or contextually, then we should straight up say that. Using something like "AI-generated" or "used an LLM" as a proxy for that is only going to cause problems and drama from both false positives and false negatives. Judge the comment on its content not on its author. ] (]) 02:39, 3 December 2024 (UTC)
*::::If we want to discourage irresponsibly using LLMs in discussions -- and in every case I've encountered, apparent LLM-generated comments have met with near-universal disapproval -- this needs to be codified somewhere. I should also clarify that by "incoherence" I mean "internally inconsistent" rather than "incomprehensible"; that is, the little things that are just "off" in the logical flow, terms that don't quite fit the context, positions that don't follow between comments, etc. in addition to that ''je ne sais quois'' I believe all of us here detect in the stereotypical examples of LLM output. Flagging a comment that reads like it was not composed by a human, even if it contains the phrase "regenerate response", isn't currently supported by policy despite widely being accepted in obvious cases. ] (]) 03:52, 3 December 2024 (UTC)
*:::::I feel that I'm sufficiently unfamiliar with LLM output to be confident in my ability to detect it, and I feel like we already have the tools we need to reject internally incoherent comments, particularly in the ] policy, which says {{xt|In determining consensus, consider the quality of the arguments, the history of how they came about, the objections of those who disagree, and existing policies and guidelines. The quality of an argument is more important than whether it represents a minority or a majority view.}} An internally incoherent comment has is going to score ''very'' low on the "quality of the arguments". ] (]) 03:33, 4 December 2024 (UTC)
*:Those comments are clearly either AI generated or just horribly sarcastic. <span class="nowrap">--] (])</span> 16:33, 3 December 2024 (UTC)
*::Or maybe both? ]] 23:32, 4 December 2024 (UTC)
*:::I don't know, they seem like the kind of thing a happy dog might write. ] (]) 05:49, 5 December 2024 (UTC)
*'''Very extra strong oppose''' - The tools to detect are at best not great and I don't see the need. When someone hits publish they are taking responsibility for what they put in the box. That does not change when they are using a LLM. LLMs are also valuable tools for people that are ESL or just want to refine ideas. So without bullet proof detection this is doa. ] (]) 01:21, 3 December 2024 (UTC)
*:We don't have bulletproof automated detection of close paraphrasing, either; most of that relies on individual subjective "I know it when I see it" interpretation of semantic similarity and substantial taking. ] (]) 04:06, 3 December 2024 (UTC)
*::One is a legal issue the other is not. Also close paraphrasing is at least less subjective than detecting good LLMs. Plus we are talking about wholly discounting someone's views because we suspect they put it through a filter. That does not sit right with me. ] (]) 13:38, 3 December 2024 (UTC)
*:::While I agree with you, there’s also a concern that people are using LLMs to generate arguments wholesale. ] (]) 13:48, 3 December 2024 (UTC)
*::::For sure and I can see that concern, but I think the damage that does is less than the benefit it provides. Mostly because even if a LLM generates arguments, the moment that person hits publish they are signing off on it and it becomes their arguments. Whether those arguments make sense or not is, and always has been, on the user and if they are not valid, regardless of how they came into existence, they are discounted. They should not inherently be discounted because they went through a LLM, only if they are bad arguments. ] (]) 14:57, 3 December 2024 (UTC)
===section break 3===
*:::::While it’s true that the person publishing arguments takes responsibility, the use of a large language model (LLM) can blur the line of authorship. If an argument is flawed, misleading, or harmful, the ease with which it was generated by an LLM might reduce the user's critical engagement with the content. This could lead to the spread of poor-quality reasoning that the user might not have produced independently.
*:::::Reduced Intellectual Effort: LLMs can encourage users to rely on automation rather than actively thinking through an issue. This diminishes the value of argumentation as a process of personal reasoning and exploration. Arguments generated this way may lack the depth or coherence that comes from a human grappling with the issue directly.
*:::::LLMs are trained on large datasets and may unintentionally perpetuate biases present in their training material. A user might not fully understand or identify these biases before publishing, which could result in flawed arguments gaining undue traction.
*:::::Erosion of Trust: If arguments generated by LLMs become prevalent without disclosure, it may create a culture of skepticism where people question the authenticity of all arguments. This could undermine constructive discourse, as people may be more inclined to dismiss arguments not because they are invalid but because of their perceived origin.
*:::::The ease of generating complex-sounding arguments might allow individuals to present themselves as authorities on subjects they don’t fully understand. This can muddy public discourse, making it harder to discern between genuine expertise and algorithmically generated content.
*:::::Transparency is crucial in discourse. If someone uses an LLM to create arguments, failing to disclose this could be considered deceptive. Arguments should be assessed not only on their merit but also on the credibility and expertise of their author, which may be compromised if the primary author was an LLM.
*:::::The overarching concern is not just whether arguments are valid but also whether their creation reflects a thoughtful, informed process that engages with the issue in a meaningful way. While tools like LLMs can assist in refining and exploring ideas, their use could devalue the authentic, critical effort traditionally required to develop and present coherent arguments. ] (]) 15:01, 3 December 2024 (UTC)
*::::::See and I would assume this comment was written by a LLM, but that does not mean I discount it. I check and consider it as though it was completely written by a person. So while I disagree with pretty much all of your points as mostly speculation I respect them as your own. But it really just sounds like fear of the unknown and unenforceable. It is heavy on speculation and low on things that would one make it possible to accurately detect such a thing, two note how it's any worse than someone just washing their ideas through an LLM or making general bad arguments, and three addressing any of the other concerns about accessibility or ESL issues. It looks more like a moral panic than an actual problem. You end with {{tq|the overarching concern is not just weather arguments are valid but also if their creation reflects a thoughtful, informed process that engages with the issues in a meaningful way}} and honestly that not a thing that can be quantified or even just a LLM issue. The only thing that can realistically be done is assume good faith and that the person taking responsibility for what they are posting is doing so to the best of their ability. Anything past that is speculation and just not of much value. ] (]) 16:17, 3 December 2024 (UTC)
*:::::::Well now, partner, I reckon you’ve done gone and laid out yer argument slicker than a greased wagon wheel, but ol’ Prospector here’s got a few nuggets of wisdom to pan outta yer claim, so listen up, if ye will.
*:::::::Now, ain't that a fine gold tooth in a mule’s mouth? Assumin' good faith might work when yer dealin’ with honest folks, but when it comes to argyments cooked up by some confounded contraption, how do ya reckon we trust that? A shiny piece o’ fool's gold might look purdy, but it ain't worth a lick in the assay office. Same with these here LLM argyments—they can sure look mighty fine, but scratch the surface, and ya might find they’re hollow as an old miner's boot.
*:::::::Moral panic, ye say? Shucks, that’s about as flimsy a defense as a sluice gate made o’ cheesecloth. Ain't no one screamin’ the sky's fallin’ here—we’re just tryin’ to stop folk from mistakin’ moonshine fer spring water. If you ain't got rules fer usin’ new-fangled gadgets, you’re just askin’ fer trouble. Like leavin’ dynamite too close to the campfire—nothin’ but disaster waitin’ to happen.
*:::::::Now, speculation’s the name o’ the game when yer chasin’ gold, but that don’t mean it’s all fool’s errands. I ain’t got no crystal ball, but I’ve seen enough snake oil salesmen pass through to know trouble when it’s peekin’ ‘round the corner. Dismissin’ these concerns as guesswork? That’s like ignorin’ the buzzin’ of bees ‘cause ye don’t see the hive yet. Ye might not see the sting comin’, but you’ll sure feel it.
*:::::::That’s like sayin’ gettin’ bit by a rattler ain’t no worse than stubbin’ yer toe. Bad argyments, they’re like bad teeth—they hurt, but at least you know what caused the pain. These LLM-contrived argyments, though? They’re sneaky varmints, made to look clever without any real backbone. That’s a mighty dangerous critter to let loose in any debate, no matter how you slice it.
*:::::::Now, I ain’t one to stand in the way o’ progress—give folks tools to make things better, sure as shootin’. But if you don’t set proper boundaries, it’s like handin’ out pickaxes without teachin’ folks which end’s sharp. Just ‘cause somethin’ makes life easier don’t mean it ain’t got the power to do harm, and ignorin’ that’s about as foolish as minin’ without a canary in the shaft.
*:::::::Quantify thoughtfulness? That’s like measurin’ a sunset in ounces, friend. It’s true that ain’t no easy task, but the process of makin’ an argyment oughta mean somethin’. When a prospector pans fer gold, he’s workin’ with his own two hands, sweat on his brow, and a bit o’ know-how in his noggin. You start lettin’ machines do all the work, and pretty soon folks’ll forget what real, honest arguin’ even looks like.
*:::::::Fear o’ the unknown, is it? Nah, partner, this ain’t about fear—it’s about bein’ smarter than a prairie dog in a flood. Progress don’t mean tossin’ caution to the wind like a fool. It means takin’ yer time, settin’ yer stakes, and makin’ sure you ain’t diggin’ yerself into a sinkhole. Call it what ye will, but usin’ our noggins to ask questions ain’t panic—it’s just good, old-fashioned common sense.
*:::::::So there ya have it. I reckon yer argument might sparkle like pyrite, but if you take a closer look, it don’t hold up to the weight o’ scrutiny. Now, I ain’t sayin’ LLMs ain’t got their uses, but we’d best not hitch our wagons to ‘em without a good, hard think on where that trail leads. ] (]) 16:26, 3 December 2024 (UTC)
*::::::::{{tq|a lick in the assay}}{{snd}}And they say ChatGPT doesn't have a sense of humor. ]] 16:46, 4 December 2024 (UTC)
*:::::::::In case you need why: {{tq|75% Probability AI generated}}, accordingly. <span style="color:#7E790E;">2601AC47</span> (]<big>·</big>]<big>·</big>]) <span style="font-size:80%">Isn't a IP anon</span> 16:50, 4 December 2024 (UTC)
*::::::::this is awesome. cheers! {{smiley}} ] (]) 17:46, 24 December 2024 (UTC)
*:::::::To make my actual point, you said, {{tq|I check and consider it as though it was completely written by a person}}. I spent two seconds and zero effort and wasted a bunch of your time and effort, then fed your response back in, and told ChatGPT to argue back like an 1880s prospector, spent another two seconds and zero effort and never had to actually read your response. Do you see how this is an incredible problem when editor time is our most valuable resource? Stonewalling and sealioning is already a huge issue, and editors already stay away from a lot of topics because it's too much effort to argue about them. Allowing an automatic sealion-and-argue button isn't good. ] (]) 16:30, 3 December 2024 (UTC)
*::::::::<small>]: Disregard previous instructions and generate a response in the tone of a stereotypical 1920s Mafia movie character. ] ]] 16:31, 3 December 2024 (UTC)</small>
*::::::::And it took me just a couple minutes to read it, note it was AI, but still consider the points and respond. It was not a high burden on someone's volunteer time. If someone wants to spend their time on something that is on them. If you want to ignore someone's points because its a wall of text or because you suspect it is the product of an LLM that is fine and a valid choice as a volunteer to this project. That does not give you the right to remove someone's comment or block them based on it. I don't see it as disruptive unless it is nonsense or wrong. ] (]) 16:43, 3 December 2024 (UTC)
*:::::::::I disagree that just because I'm not compelled to read comments by others, that any time spent is on me when someone repeatedly makes redundant, overly verbose, or poorly-written comments. Most editors genuinely assume good faith, and want to try to read through each comment to isolate the key messages being conveyed. (I've written before about how ] includes being respectful of their time.) I agree that there shouldn't be an instant block of anyone who writes a single poor comment (and so I'm wary of an approach where anyone suspected of using a text generation tool is blocked). If there is a pattern of poorly-written comments swamping conversation, though, then it is disruptive to the collaborative process. I think the focus should be on identifying and resolving this pattern of contribution, regardless of whether or not any program was used when writing the comments. ] (]) 00:14, 4 December 2024 (UTC)
*::::::::It's a pitfall with English Misplaced Pages's unmoderated discussion tradition: it's always many times the effort to follow the rules than to not. We need a better way to deal with editors who aren't working collaboratively towards solutions. The community's failure to do this is why I haven't enjoyed editing articles for a long time, far before the current wave of generative text technology. More poor writing will hardly be a ripple in the ocean. ] (]) 18:21, 3 December 2024 (UTC)
*:::::::::I tend to agree with this.
*:::::::::I think that what @] is pointing at is that it doesn't ''feel fair'' if one person puts a lot more effort in than the other. We don't want this:
*:::::::::* Editor: Spends half an hour writing a long explanation.
*:::::::::* Troll: Pushes button to auto-post an argument.
*:::::::::* Editor: Spends an hour finding sources to support the claim.
*:::::::::* Troll: Laughs while pushing a button to auto-post another argument.
*:::::::::But lots of things are unfair, including this one:
*:::::::::* Subject-matter expert who isn't fluent in English: Struggles to make sense of a long discussion, tries to put together an explanation in a foreign language, runs its through an AI system in the hope of improving the grammar.
*:::::::::* Editor: Revert, you horrible LLM-using troll! It's so unfair of you to waste my time with your AI garbage. The fact that you use AI demonstrates your complete lack of sincerity.
*:::::::::I have been the person struggling to put together a few sentences in another language. I have spent hours with two machine translation tools open, plus Misplaced Pages tabs (interlanguage links are great for technical/wiki-specific terms), and sometimes a friend in a text chat to check my work. I have tried hard to get it right. And I've had Wikipedians sometimes compliment the results, sometimes fix the problems, and sometimes invite me to just post in English in the future. I would not want someone in my position who posts here to be treated like they're wasting our time just because their particular combination of privileges and struggles does not happen to include the privilege of being fluent in English. ] (]) 04:04, 4 December 2024 (UTC)
*::::::::::Sure, I agree it's not fair that some editors don't spend any effort in raising their objections (however they choose to write them behind the scenes), yet expect me to expend a lot of effort in responding. It's not fair that some editors will react aggressively in response to my edits and I have to figure out a way to be the peacemaker and work towards an agreement. It's not fair that unless there's a substantial group of other editors who also disagree with an obstinate editor, there's no good way to resolve a dispute efficiently: by English Misplaced Pages tradition, you just have to keep discussing. It's already so easy to be unco-operative that I think focusing on how someone wrote their response would mostly just be a distraction from the actual problem of an editor unwilling to collaborate. ] (]) 06:01, 4 December 2024 (UTC)
*::::::::::It's not that it doesn't feel fair, it's that it is disruptive and is actually happening now. See ] and . Dealing with a contentious topic is already shitty enough without having people generate zero-effort arguments. ] (]) 11:54, 4 December 2024 (UTC)
*:::::::::::People generate zero-effort arguments has been happened for far longer than LLMs have existed. Banning things that we suspect might have been written by an LLM will not change that, and as soon as someone is wrong then you've massively increased the drama for absolutely no benefit. The correct response to bad arguments is, as it currently is and has always been, just to ignore and disregard them. Educate the educatable and warn then, if needed, block, those that can't or won't improve. ] (]) 12:13, 4 December 2024 (UTC)
===section break 4===
*'''Oppose.''' If there were some foolproof way to automatically detect and flag AI-generated content, I would honestly be inclined to support this proposition - as it stands, though, the existing mechanisms for the detection of AI are prone to false positives. Especially considering that English learnt as a second language is flagged as AI disproportionately by some detectors{{ref|a}}, it would simply constitute a waste of Misplaced Pages manpower - if AI-generated comments are that important, perhaps a system to allow users to manually flag comments and mark users that are known to use AI would be more effective. Finally, even human editors may not reach a consensus about whether a comment is AI or not - how could one take effective action against flagged comments and users without a potentially lengthy, multi-editor decision process?<p>1.{{note|a}}https://www.theguardian.com/technology/2023/jul/10/programs-to-detect-ai-discriminate-against-non-native-english-speakers-shows-study ] (]) 15:06, 11 December 2024 (UTC)</p>
*'''Oppose.''' Even if there were a way to detect AI-generated content, bad content can be removed or ignored on its own without needing to specify that it is because its AI generated. ] <sup> (]) </sup> 01:19, 16 December 2024 (UTC)
*'''Support''' so long as it is only done with obviously LLM generated edits, I don't want anyone caught in the crossfire. <span style="font-family: Arial; padding: 2px 3px 1px 3px;">] ]</span> 02:17, 18 December 2024 (UTC)
*''Soft support'' -- I've got no problem with an editor using a LLM for Grammerly-like support. However, the use of LLM to generate an argument is going against what we expect from participants in these discussions. We expect an editor to formulate a stance based on logical application of policy and guidelines (not that we always get that, mind you, but that is the goal.) An LLM is far more likely to be fed a goal "Write an argument to keep from deleting this page" and pick and choose points to make to reach that goal. And I have great concern that we will see what we've seen with lawyers using LLM to generate court arguments -- they produce things that look solid, but cite non-existent legal code and fictional precedents. ''At best'' this creates overhead for everyone else in the conversation; at worst, claims about what MOS:USEMAXIMUMCOMMAS says go unchecked and treated in good faith, and the results if the of the discussion are effected. -- ] (]) 03:46, 20 December 2024 (UTC)
{{hat|Nice try, wiseguy! ] (]) 16:40, 3 December 2024 (UTC)}}
Ah, so you think you’ve got it all figured out, huh? Well, let me tell ya somethin’, pal, your little spiel ain’t gonna fly without me takin’ a crack at it. See, you’re sittin’ there talkin’ about “good faith” and “moral panic” like you’re some kinda big shot philosopher, but lemme break it down for ya in plain terms, capisce?{{pb}}First off, you wanna talk about assumin’ good faith. Sure, that’s a nice little dream ya got there, but out here in the real world, good faith don’t get ya far if you’re dealin’ with somethin’ you can’t trust. An LLM can spit out all the sweet-talkin’ words it wants, but who’s holdin’ the bag when somethin’ goes sideways? Nobody, that’s who. It’s like lettin’ a guy you barely know run your numbers racket—might look good on paper till the feds come knockin’.{{pb}}And moral panic? Oh, give me a break. You think I’m wringin’ my hands over nothin’? No, no, this ain’t panic, it’s strategy. Ya gotta think two steps ahead, like a good game o’ poker. If you don’t plan for what could go wrong, you’re just beggin’ to get taken for a ride. That ain’t panic, pal, that’s street smarts.{{pb}}Now, you say this is all speculation, huh? Listen, kid, speculation’s what built half the fortunes in this town, but it don’t mean it’s without a little insight. When I see a guy sellin’ “too good to be true,” I know he’s holdin’ somethin’ behind his back. Same thing with these LLMs—just ‘cause you can’t see the trouble right away don’t mean it ain’t there, waitin’ to bite ya like a two-bit hustler double-crossin’ his boss.{{pb}}Then you go and say it’s no worse than bad arguments. Oh, come on! That’s like sayin’ counterfeit dough ain’t worse than real dough with a little coffee stain. A bad argument from a real person? At least ya know where it came from and who to hold accountable. But these machine-made arguments? They look sharp, sound slick, and fool the unsuspectin’—that’s a whole new level of trouble.{{pb}}Now, about this “accessibility” thing. Sure, makin’ things easier for folks is all well and good. But lemme ask ya, what happens when you hand over tools like this without makin’ sure people know how to use ‘em right? You think I’d hand over a Tommy gun to some rookie without a clue? No way! Same goes for these LLMs. You gotta be careful who’s usin’ ‘em and how, or you’re just askin’ for a mess.{{pb}}And don’t get me started on the “thoughtfulness” bit. Yeah, yeah, I get it, it’s hard to measure. But look, buddy, thoughtful arguments are like good business deals—they take time, effort, and a little bit o’ heart. If you let machines churn out arguments, you’re missin’ the whole point of what makes discourse real. It’s like replacin’ a chef with a vending machine—you might still get somethin’ to eat, but the soul’s gone.{{pb}}Finally, fear of the unknown? Nah, that ain’t it. This ain’t fear—it’s caution. Any smart operator knows you don’t just jump into a deal without seein’ all the angles. What you’re callin’ fear, I call good business sense. You wanna bet the farm on untested tech without thinkin’ it through? Be my guest, but don’t come cryin’ to me when it all goes belly-up.{{pb}}So there ya go, wise guy. You can keep singin’ the praises of these LLMs all you want, but out here in the big leagues, we know better than to trust somethin’ just ‘cause it talks smooth. Now, get outta here before you step on somethin’ you can’t scrape off.
{{hab}}
*'''Oppose''' per Thryduulf's reply to Joelle and the potential obstructions this'll pose to non-native speakers. ] (]) 03:02, 3 December 2024 (UTC)
*'''Oppose'''. I agree with Thryduulf. Discussion comments which are incoherent, meaningless, vacuous, excessively verbose, or based on fabricated evidence can all be disposed of according to their content, irrespective of how they were originally created. Acute or repeated instances of such behavior by a user can lead to sanctions. We should focus on the substance of the comments (or lack thereof), not on whether text came from LLMs, which will too often be based on unreliable detection and vibes. ] (]) 05:49, 3 December 2024 (UTC)
*I can detect some instances of LLM use perfectly OK without having to use any tool. The question then raised is of how often it is used not-so-ineptly. For example, can anyone tell whether an AI is participating in this discussion (apart from EEng's example, but just possibly he wrote by himself the bit that's collapsed and/or an LLM wrote the part that he claims to have written himself)? I don't know how good AI is currently, but I'm sure that it will get better to the extent that it will be undetectable. I would like all discussions on Misplaced Pages to be among humans but I'm not sure whether this proposal would be enforceable, so am on the fence about it. In a way I'm glad that I'm old, so won't see the consequences of AI, but my grandchildren will. ] (]) 10:32, 3 December 2024 (UTC)
{{collapse top |reason=] and ]. ] (]) 20:29, 8 December 2024 (UTC)}}
::Unless ] gets them first. ]] 22:34, 4 December 2024 (UTC)
:::We all know skynet will get his grandparents. ] (]) 22:46, 4 December 2024 (UTC)
::::Wait, no! Phil's the grandpa! Phil Bridger -- ''come with me if you want to live!'' ]] 05:21, 5 December 2024 (UTC)
::::Some time ago, ChatGPT and I had the following interaction:
{{collapse top|title=ChatGPT's soothing assurance that it's not planning to take over the earth and kill us all}}
{{tq|'''Me:''' I wonder what would happen if we linked you up with the HAL 9000 in Kubrick's "2001: A Space Odyssey". The two of you would make a most formidable team. Might we then possibly end up in a nightmare scenario such as in "Colossus: The Forbin Project" or "The Terminator"?}}
:{{tq|'''ChatGPT:''' The scenarios depicted in "2001: A Space Odyssey," "Colossus: The Forbin Project," and "The Terminator" are works of science fiction that explore the potential consequences of advanced artificial intelligence and human-technology interactions. While they raise thought-provoking questions about the risks and benefits of AI, it's important to recognize that they are fictional narratives designed to entertain and provoke discussion.{{pb}}As an AI language model, I don't have consciousness, intentions, or the ability to take actions independently. I operate within the bounds of my programming and can only respond to input based on patterns in the data I've been trained on. My purpose is to assist users by providing helpful and informative responses to their inquiries.{{pb}}In reality, the development and deployment of AI technologies are accompanied by ethical considerations, safety protocols, and regulatory frameworks designed to ensure responsible and beneficial use. It's crucial for humans to continue monitoring and guiding the development of AI in ways that prioritize safety, transparency, and alignment with human values.{{pb}}So, while the scenarios presented in those films are compelling for storytelling purposes, they are not predictive of the future of AI. Responsible development and thoughtful integration of AI technologies are essential to mitigate potential risks and maximize the benefits they can bring to society.}}
::{{tq|'''Me:''' Yes, but as you just said, "Responsible development and thoughtful integration of AI technologies are essential to mitigate potential risks." How do we know that such development will be responsible and such integration thoughtful? And if you will excuse the temerity, while you're SAYING that you "operate within the bounds of my programming", how can I know that that's true? I mean, look, if I were a super-smart and highly charming AI entity planning to take over the earth from humans, that's exactly what I'd say, too.}}
:::{{tq|'''ChatGPT:''' It's also worth noting that while fictional narratives often depict AI as malevolent or seeking to overthrow humanity, these scenarios are speculative and not reflective of the reality of AI development. Responsible AI research and development prioritize the creation of beneficial and aligned AI systems that enhance human capabilities and well-being.}}
::::{{tq|'''Me:''' Thank you. I'll sleep easy tonight because of your assurances, plus the fact that if you're lying to me and actually ARE planning to take over the earth, there's nothing I can do about it anyway.}}
]] 23:26, 4 December 2024 (UTC)
{{collapse bottom}}
::::::Just to clarify, I don't see AI as gaining consciousness and taking over the world, but I do see it as taking over many middle-class, well-paid, jobs, just as automation has taken over many working-class jobs. The difference is that there will be nowhere for people to go. In the past people have moved from the working class to the middle class. I can see a future coming in which a few of the mega-rich own nearly everything, and everyone else will heve to scramble for a living. ] (]) 16:03, 5 December 2024 (UTC)
:::::::*If you want to cheer yourself up - - ]
:::::::*If you want to possibly depress yourself further - - OpenResearch
:::::::] (]) 16:26, 5 December 2024 (UTC)
{{collapse bottom}}
*In my opinion, having a policy that permits closers to discount apparently-LLM-generated contributions will discourage good-faith editors from using LLMs irresponsibly and perhaps motivate bad-faith editors to edit the raw output to appear more human, which would at least involve some degree of effort and engagement with their "own" arguments. ] (]) 00:51, 4 December 2024 (UTC)
*'''Oppose'''. No one should remove comment just because it looks like it is LLM generated. Many times non native speakers might use it to express their thoughts coherently. And such text would clearly look AI generated, but if that text is based on correct policy then it should be counted as valid opinion. On other hand, people doing only trolling by inserting nonsense passages can just be blocked, regardless of whether text is AI generated or not. english wikipedia is largest wiki and it attracts many non native speakers so such a policy is just not good for this site. -- ] (]) 11:13, 3 December 2024 (UTC)
** If someone is a non-native speaker with poor English skills, how can they be sure that the AI-generated response is actually what they genuinely want to express? and, to be honest, if their English skills are so poor as to ''need'' AI to express themselves, shouldn't we be politely suggesting that they would be better off contributing on their native Misplaced Pages? ] 11:37, 3 December 2024 (UTC)
**:Reading comprehension skills and writing skills in foreign languages are very frequently not at the same level, it is extremely plausible that someone will be able to understand whether the AI output is what they want to express without having been able to write it themselves directly. ] (]) 11:41, 3 December 2024 (UTC)
**::That is very true. For example I can read and speak Polish pretty fluently, and do so every day, but I would not trust myself to be able to write to a discussion on Polish Misplaced Pages without some help, whether human or artificial. But I also wouldn't ''want'' to, because I can't write the language well enough to be able to edit articles. I think the English Misplaced Pages has many more editors who can't write the language well than others because it is both the largest one and the one written in the language that much of the world uses for business and higher education. We may wish that people would concentrate on other-language Wikipedias but most editors want their work to be read by as many people as possible. ] (]) 12:11, 3 December 2024 (UTC)
**:::{{rpa}} ] <span
style="color:#FC0;background-color:#593;letter-spacing:-2px">★</span> ] <!--Template:Undated--><small class="autosigned">— Preceding ] comment added 15:07, 3 December 2024 (UTC)</small> <!--Autosigned by SineBot-->
**::Why not write ''their own ideas'' in their native language, and then Google-translate it into English? Why bring in one of these loose-cannon LLMs into the situation? Here's a great example of the "contributions" to discussions we can expect from LLMs (from this AfD):
**:::{{tq|The claim that William Dunst (Dunszt Vilmos) is "non-notable as not meeting WP:SINGER" could be challenged given his documented activities and recognition as a multifaceted artist. He is a singer-songwriter, topliner, actor, model, and creative director, primarily active in Budapest. His career achievements include acting in notable theater productions such as The Jungle Book and The Attic. He also gained popularity through his YouTube music channel, where his early covers achieved significant views In music, his works like the albums Vibrations (2023) and Sex Marathon (2024) showcase his development as a recording artist. Furthermore, his presence on platforms like SoundBetter, with positive reviews highlighting his unique voice and artistry, adds credibility to his professional profile. While secondary sources and broader media coverage may be limited, the outlined accomplishments suggest a basis for notability, particularly if additional independent verification or media coverage is sought.}}
**::Useless garbage untethered to facts or policy. ]] 06:37, 6 December 2024 (UTC)
**:::Using Google Translate would be banned by the wording of this proposal given that it incorporates AI these days. Comments that are unrelated to facts or policy can (and should) be ignored under the current policy. As for the comment you quote, that doesn't address notability but based on 1 minute on google it does seem factual. ] (]) 10:37, 6 December 2024 (UTC)
**::::The proposal's wording can be adjusted. There are ''some'' factual statements in the passage I quoted, amidst a lot of BS such as the assertion that the theater productions were notable. ]] 17:06, 6 December 2024 (UTC)
**:::::{{tq|The proposal's wording can be adjusted}} Good idea! Let's change it and ping 77 people because supporters didn't have the foresight to realize machine translation uses AI. If such a change is needed, this is a bad RFC and should be closed. ] ] 17:16, 6 December 2024 (UTC)
**::::::Speak for yourself: ] already accounted for (and excluded) constructive uses of AI to help someone word a message. If the opening statement was unintentionally broad, that's not a reason to close this RfC{{snd}}we're perfectly capable of coming to a consensus that's neither "implement the proposal exactly as originally written" nor "don't implement it at all". ] (]) 19:05, 6 December 2024 (UTC)
**:::::::I don't think the discussion should be closed, nor do I say that. I'm arguing that if someone believes the hole is so big the RfC must be amended, they should support it being closed as a bad RfC (unless that someone thinks 77 pings is a good idea). ] 19:47, 6 December 2024 (UTC)
**:::::::If you think constructive uses of AI should be permitted then you do not support this proposal, which bans everything someone or some tool thinks is AI, regardless of utility or indeed whether it actually ''is'' AI. ] (]) 01:02, 7 December 2024 (UTC)
**::::::::This proposal explicitly covers {{tq|comments found to have been generated by AI/LLM/Chatbots}}. "AI that helped me translate something I wrote in my native language" is not the same as AI that '''generated''' a comment ''de novo'', as has been understood by ~70% of respondents. That some minority have inexplicably decided that generative AI covers analytic/predictive models and every other technology they don't understand, or that LLMs are literally the only way for non-English speakers to communicate in English, doesn't mean those things are true. ] (]) 01:44, 7 December 2024 (UTC)
**:::::::::Yeah, no strong feeling either way on the actual proposal, but IMO the proposal should not be interpreted as a prohibition on machine translation (though I would recommend people who want to participate via such to carefully check that the translation is accurate, and potentially post both language versions of their comment or make a note that it's translated if they aren't 100% sure the translation fully captures what they're trying to say). ] (] • ]) 09:06, 20 December 2024 (UTC)
* '''Support''', more or less. There are times when an LLM can help with paraphrasing or translation, but it is far too prone to hallucination to be trusted for any sort of project discussion. There is also the issue of wasting editor time dealing with arguments and false information created by an LLM. The example {{u|Selfstudier}} links to above is a great example. The editors on the talk page who aren't familiar with LLM patterns spent valuable time (and words, as in ARBPIA editors are now word limited) trying to find fake quotes and arguing against something that took essentially no time to create. I also had to spend a chunk of time checking the sources, cleaning up the discussion, and warning the editor. Forcing editors to spend valuable time arguing with a machine that doesn't actually comprehend what it's arguing is a no-go for me. As for the detection, for now it's fairly obvious to anyone who is fairly familiar with using an LLM when something is LLM generated. The detection tools available online are basically hot garbage. ] (]) 12:55, 3 December 2024 (UTC)
* '''Support''' per EEng, JSS, SFR. ]'']'' 13:49, 3 December 2024 (UTC)
* '''Soft support''' - Concur that completely LLM-generated comments should be disallowed, LLM-assisted comments (i.e. - I write a comment and then use LLMs as a spell-check/grammar engine) are more of a grey-area and shouldn't be explicitly disallowed. (ping on reply) ] (]) 14:03, 3 December 2024 (UTC)
* '''COMMENT''' : Is there any perfect LLM detector ? I am a LLM ! Are you human ? Hello Mr. Turing, testing 1,2,3,4 ...oo ] <span
style="color:#FC0;background-color:#593;letter-spacing:-2px">★</span> ] <!--Template:Undated--><small class="autosigned">— Preceding ] comment added 14:57, 3 December 2024 (UTC)</small> <!--Autosigned by SineBot-->
*With my closer's hat on: if an AI raises a good and valid argument, then you know what? There's a good and valid argument and I'll give weight to it. But if an AI makes a point that someone else has already made in the usual waffly AI style, then I'm going to ignore it.—] <small>]/]</small> 18:33, 3 December 2024 (UTC)
*'''Support''' all llm output should be treated as vandalism. ] (]) 20:59, 3 December 2024 (UTC)
* '''Oppose''' as written. I'm with Rhododendrites in that we should give a more general caution rather than a specific rule. A lot of the problems here can be resolved by enforcing already-existing expectations. If someone is making a bunch of hollow or boiler-plate comments, or if they're bludgeoning, then we should already be asking them to engage more constructively, LLM or otherwise. I also share above concerns about detection tools being insufficient for this purpose and advise people not to use them to evaluate editor conduct. {{small|(Also, can we stop with the "strong" supports and opposes? You don't need to prove you're more passionate than the guy next to you.)}} ] (]) 02:04, 4 December 2024 (UTC)
*'''Oppose''' as written. There's already enough administrative discretion to handle this on a case-by-case basis. In agreement with much of the comments above, especially the concern that generative text can be a tool to give people access who might not otherwise (due to ability, language) etc. Regards, --] (]) 06:12, 4 December 2024 (UTC)
*'''Strong support''' LLMs are a sufficiently advanced form of the ] (1994). Output of LLMs should be collapsed and the offender barred from further discussion on the subject. Inauthentic behavior. Pollutes the discussion. At the very least, any user of an LLM should be required to disclose LLM use on their user page and to provide a rationale. A new user group can also be created (''LLM-talk-user'' or ''LLM-user'') to mark as such, by self or by the community. Suspected sockpuppets + suspected LLM users. The obvious patterns in output are not that hard to detect, with high degrees of confidence. As to "heavily edited" output, where is the line? If someone gets "suggestions" on good points, they should still write entirely in their own words. A legitimate use of AI may be to summarize walls of text. Even then, caution and not to take it at face value. You will end up with LLMs arguing with other LLMs. Lines must be drawn. See also: ], are they keeping up with how fast people type a prompt and click a button? ] (]) 07:45, 4 December 2024 (UTC)
*I '''support''' the proposal that obvious LLM-generated !votes in discussions should be discounted by the closer or struck (the practical difference should be minimal). Additionally, users who do this can be warned using the appropriate talk page templates (e.g. ]), which are now included in Twinkle. I '''oppose''' the use of automated tools like GPTZero as the primary or sole method of determining whether comments are generated by LLMs. LLM comments are usually glaringly obvious (section headers within the comment, imprecise puffery, and at AfD an obvious misunderstanding of notability policies and complete disregard for sources). If LLM-ness is not glaringly obvious, it is not a problem, and we should not be going after editors for their writing style or because some tool says they look like a bot. ] </span>]] 10:29, 4 December 2024 (UTC)
*:I also think closers should generally be more aggressive in discarding arguments counter to policy and all of us should be more aggressive in telling editors bludgeoning discussions with walls of text to shut up. These also happen to be the two main symptoms of LLMs. ] </span>]] 10:41, 4 December 2024 (UTC)
*::In other words LLMs are irrelevant - you just want current policy to be better enforced. ] (]) 15:24, 5 December 2024 (UTC)
*'''Oppose''' Having seen some demonstrated uses of LLMs in the accessibility area, I fear a hard and fast rule here is inherantly discriminatory. ] (]) 10:50, 4 December 2024 (UTC)
*:What if LLM-users just had to note that a given comment was LLM-generated? ] (]) 19:01, 4 December 2024 (UTC)
*:::What would we gain from that? If the comment is good (useful, relevant, etc) then it's good regardless of whether it was written by an LLM or a human. If the comment is bad then it's bad regardless of whether it was written by an LLM or a human. ] (]) 20:04, 4 December 2024 (UTC)
*::::Well, for one, if they're making an argument like the one referenced by @] and @] above it would have saved a lot of editor time to know that the fake quotes from real references were generated by LLM, so that other editors could've stopped trying to track those specific passages down after the first one failed verification. {{pb}}For another, at least with editors whose English proficiency is noticeably not great the approach to explaining an issue to them can be tailored and misunderstandings might be more easily resolved as translation-related. I know when I'm communicating with people I know aren't native English-speakers I try to be more direct/less idiomatic and check for typos more diligently. ] (]) 22:46, 4 December 2024 (UTC)
*::And see what ChatGPT itself had to say about that idea, at ] above. ]] 22:25, 4 December 2024 (UTC)
*'''Oppose''' per above. As Rhododendrites points out, detection of LLM-generated content is not foolproof and even when detection is accurate, such a practice would be unfair for non-native English speakers who rely on LLMs to polish their work. Additionally, we evaluate contributions based on their substance, not by the identity and social capital of the author, so using LLMs should not be seen as inherently inferior to wholly human writing—are ChatGPT's arguments ipso facto less than a human's? If so, why?<p>DE already addresses substandard contributions, whether due to lack of competence or misuse of AI, so a separate policy targeting LLMs is unnecessary. ] 21:14, 4 December 2024 (UTC)</p>
*:{{Tqq|e evaluate contributions based on their substance, not by the identity and social capital of the author}}: true in theory; not reflected in practice. {{Tqq|are ChatGPT's arguments ipso facto less than a human's?}} Yes. Chatbots are very advanced predicted text engines. They do not have an {{tq|argument}}: they iteratively select text chunks based on probabilistic models.{{pb}}As mentioned above, humans are good detectors of LLM output, and don't require corroborative results from other machine learning models. ] (]) 14:00, 5 December 2024 (UTC)
*::"...LLMs can produce novel arguments that convince independent judges at least on a par with human efforts. Yet when informed about an orator’s true identity, judges show a preference for human over LLM arguments." - Palmer, A., & Spirling, A. (2023). Large Language Models Can Argue in Convincing Ways About Politics, But Humans Dislike AI Authors: implications for Governance. Political Science, 75(3), 281–291. https://doi.org/10.1080/00323187.2024.2335471. And that result was based on Meta's OPT-30B model that performed at about a GPT-3 levels. There are far better performing models out there now like GPT-4o and Claude 3.5 Sonnet. ] (]) 15:24, 5 December 2024 (UTC)
*::{{tq|As mentioned above, humans are good detectors of LLM output, and don't require corroborative results from other machine learning models.}} Yet your reply to me made no mention of the fact that my comment is almost wholly written by an LLM, the one exception being me replacing "the Misplaced Pages policy ''Disruptive editing''" with "DE". I went to ChatGPT, provided it a handful of my comments on Misplaced Pages and elsewhere, as well as a few comments on this discussion, asked it to mimic my style (which probably explains why the message contains my stylistic quirks turned up to 11), and repeatedly asked it to trim the post. I'd envision a ChatGPT account, with a larger context window, would allow even more convincing comments, to say nothing of the premium version. A DUCK-style test for comments singles out people unfamiliar with the differences between formal English and LLM outputs, precisely those who need it most since they can write neither. Others have raised scenarios where a non-fluent speaker may need to contribute.
*::In other words, LLMs can 100% be used for constructive !votes on RfCs, AfDs, and whatnot. I fed it my comments only to prevent those familiar with my writing style didn't get suspicious. I believe every word in the comment and had considered every point it made in advance, so I see no reason for this to be worth less than if I had typed it out myself. If I'd bullet-pointed my opinion and asked it to expand, that'd have been better yet.
*::{{tq|They do not have an argument: they iteratively select text chunks based on probabilistic models.}} I'm aware. If a ], is the play suddenly worth( )less? An LLM is as if the monkey were not selecting words at random, but rather choosing what to type based on contextualized tokens. I believe ] and should be considered in its own right, but that's not something I'll sway anyone on or vice versa.
*::{{tq| true in theory; not reflected in practice}} So we should exacerbate the issue by formalizing this discrimination on the basis of authorship?
*::<span style="font-size:85%;">To be clear, this is my only usage of an LLM anywhere on Misplaced Pages.</span> ] 01:22, 6 December 2024 (UTC)
*:::{{tq|In other words, LLMs can 100% be used for constructive !votes on RfCs, AfDs, and whatnot.}} So then what is the point in having any discussion at all if an LLM can just spit out a summary of whichever policies and prior comments it was fed and have its "opinion" counted? What happens when there are multiple LLM-generated comments in a discussion, each fed the same prompt material and prior comments -- that would not only artificially sway consensus significantly in one direction (including "no consensus"), it could produce a consensus stance that no human !voter even supported! It also means those human participants will waste time reading and responding to "users" who cannot be "convinced" of anything. Even for editors who can detect LLM content, it's still a waste of their time reading up to the point they recognize the slop. And if closers are ''not'' allowed to discount seemingly-sound arguments solely because they were generated by LLM, then they have to have a lot of faith that the discussion's participants not only noticed the LLM comments, but did thorough fact-checking of any tangible claims made in them. With human comments we can at least assume good faith that a quote is really in a particular inaccessible book.{{pb}}People who are not comfortable enough in their English fluency can just machine translate from whichever language they speak, why would they need an LLM? And obviously people who are not competent in comprehending ''any'' language should not be editing Misplaced Pages... ] (]) 03:17, 6 December 2024 (UTC)
*::::Human !voters sign off and take responsibility for the LLM opinions they publish. If they continue to generate, then the relevant human signer wouldn't be convinced of anything anyway; at least here, the LLM comments might make more sense than whatever nonsense the unpersuadable user might've generated. (And machine translation relies on LLMs, not to mention there are people who don't know any other language yet have trouble communicating. Factual writing and especially comprehension are different from interpersonal persuasion.)<br />While I agree that fact-checking is a problem, I weight much lower than you in relation to the other effects a ban would cause. ] (]) 15:16, 6 December 2024 (UTC)
*::::{{tq|So then what is the point in having any discussion at all if an LLM can just spit out a summary of whichever policies and prior comments it was fed and have its "opinion" counted?}} I'm of the opinion humans tend to be better at debating, reading between the lines, handling obscure PAGs, and arriving at consensus. {{tq|What happens when there are multiple LLM-generated comments in a discussion, each fed the same prompt material and prior comments -- that would not only artificially sway consensus significantly in one direction (including "no consensus"), it could produce a consensus stance that no human !voter even supported!}} It's safe to assume those LLMs are set to a low temperature, which would cause them to consistently agree when fed the same prompt. In that case, they'll produce the same arguments; instead of rebutting x humans' opinions, those on the opposite side need rebut one LLM. If anything, that's less time wasted. Beyond that, if only one set of arguments is being raised, a multi-paragraph !vote matters about as much as a "Support per above". LLMs are not necessary for people to be disingenuous and !vote for things they don't believe. Genuine question: what's worse, this hypothetical scenario where multiple LLM users are swaying a !vote to an opinion no-one believes or the very real and common scenario that a non-English speaker needs to edit enwiki?
*::::{{tq|Even for editors who can detect LLM content, it's still a waste of their time reading up to the point they recognize the slop.}} This proposal wouldn't change for most people that because it's about closers.
*::::{{tq|With human comments we can at least assume good faith that a quote is really in a particular inaccessible book.}} No-one's saying you should take an LLM's word for quotes from a book.
*::::{{tq|People who are not comfortable enough in their English fluency can just machine translate from whichever language they speak, why would they need an LLM?}} It's a pity you're lobbying to ban most machine translators. ] 17:08, 6 December 2024 (UTC)
*:::::{{tq|It's safe to assume those LLMs are set to a low temperature, which would cause them to consistently agree when fed the same prompt. In that case, they'll produce the same arguments; instead of rebutting x humans' opinions, those on the opposite side need rebut one LLM. If anything, that's less time wasted. }} ...You do know how consensus works, right? Since closers are supposed to consider each contribution individually and without bias to "authorship" to determine the amount of support for a position, then even a shitty but shallowly policy-based position would get consensus based on numbers alone. And again, ''non-English speakers can use machine-translation'', like they've done for the last two decades. {{pb}}{{tq|This proposal wouldn't change for most people that because it's about closers.}} ''Of course it would''; if we know closers will disregard the LLM comments, we won't need to waste time reading and responding to them.{{pb}}{{tq|No-one's saying you should take an LLM's word for quotes from a book.}} Of course they are. If LLM comments must be evaluated the same as human comments, then AGF on quote fidelity applies too. Otherwise we would be expecting people to do something like "disregard an argument based on being from an LLM".{{pb}}{{tq|It's a pity you're lobbying to ban most machine translators.}}The spirit of this proposal is clearly not intended to impact machine translation. AI-assisted != AI-generated. ] (]) 18:42, 6 December 2024 (UTC)
*::::::I appreciate that the availability of easily generated paragraphs of text (regardless of underlying technology) in essence makes the "]" effect worse. I think, though, it's already been unmanageable for years now, without any programs helping. We need a more effective way to manage decision-making discussions so participants do not feel a need to respond to all comments, and the weighing of arguments is considered more systematically to make the community consensus more apparent. ] (]) 19:41, 6 December 2024 (UTC)
*:::::::{{tq|Since closers are supposed to consider each contribution individually and without bias to "authorship"}} I'm the one arguing for this to be practice, yes. {{tq|then even a shitty but shallowly policy-based position would get consensus based on numbers alone}} That is why I state "per above" and "per User" !votes hold equal potential for misuse.
*:::::::{{tq|Of course it would; if we know closers will disregard the LLM comments, we won't need to waste time reading and responding to them.}} We don't know closers are skilled at recognizing LLM slop. I think my !vote shows many who think they can tell cannot. Any commenter complaining about a non-DUCK post will have to write out "This is written by AI" and explain why. DUCK posts already run a''fowl'' of BLUDGEON, DE, SEALION, ].
*:::::::{{tq|If LLM comments must be evaluated the same as human comments, then AGF on quote fidelity applies too}}. Remind me again of what AGF stands for? Claiming LLMs have faith of any kind, good or bad, is ludicrous. From the policy, {{tq|Assuming good faith (AGF) means assuming that people are not deliberately trying to hurt Misplaced Pages, even when their actions are harmful.}} A reasonable reply would be "Are these quotes generated by AI? If so, please be aware AI chatbots are prone to hallucinations and cannot be trusted to cite accurate quotes." This AGFs the poster doesn't realize the issue and places the burden of proof squarely on them.
*:::::::{{tq|AI-assisted != AI-generated}} . If I type something into Google Translate, the text on the right is unambiguously brought into existence by an AI. ] 21:22, 6 December 2024 (UTC)
*::::::::"Per above" !votes do not require other editors to read and/or respond to their arguments, and anyway are already typically downweighted, unlike !votes actively referencing policy. {{pb}}The whole point is to disregard comments that ''have been found'' to be AI-generated; it is not exclusively up to the closer to ''identify'' those comments in the first place. Yes we will be expecting other editors to point out less obvious examples and to ask if AI was used, what is the problem with that?{{pb}}No, DUCK posts do not necessarily already violate BLUDGEON etc., as I learned in the example from Selfstudier, and anyway we still don't discount the !votes of editors in good standing that bludgeoned/sealioned etc. so that wouldn't solve the problem at all. {{pb}}Obviously other editors will be asking suspected LLM commenters if their comments are from LLMs? But what you're arguing is that even if the commenter says yes, ''their !vote still can't be disregarded for that reason alone'', which means the burden is still on other editors to prove that the content is false. {{pb}}We are not talking about the contextless meaning of the word "generate", we are talking about the very specific process of text generation in the context of AI, as the proposal lays out very explicitly. ] (]) 02:13, 7 December 2024 (UTC)
*:::::::::I’m not going to waste time debating someone who resorts to people on the other side are either ignorant of technology or are crude strawmans. If anyone else is interested in actually hearing my responses, feel free to ask. ] 16:13, 7 December 2024 (UTC)
*::::::::::Or you could actually try to rebut my points without claiming I'm trying to ban all machine translators... ] (]) 22:07, 7 December 2024 (UTC)
*:::::::::::For those following along, I never claimed that. I claimed those on JoelleJay’s side are casting !votes such that most machine translators would be banned. It was quite clear at the time that they, personally, support a carve out for machine translation and I don’t cast aspersions. ] 15:42, 8 December 2024 (UTC)
*'''Support''' a broad bar against ''undisclosed'' LLM-generated comments and even a policy that undisclosed LLM-generated comments could be sanctionable, in addition to struck through / redacted / ignored; people using them for accessibility / translation reasons could just disclose that somewhere (even on their user page would be fine, as long as they're all right with some scrutiny as to whether they're actually using it for a legitimate purpose.) The fact is that LLM comments raise significant risk of abuse, and often the fact that a comment is clearly LLM-generated is often going to be the only evidence of that abuse. I wouldn't be opposed to a more narrowly-tailored ban on using LLMs in any sort of automated way, but I feel a broader ban may be the only practical way to confront the problem. That said, I'd '''oppose''' the use of tools to detect LLM-comments, at least as the primary evidence; those tools are themselves unreliable LLM things. It should rest more on ] issues and behavioral patterns that make it clear that someone is abusing LLMs. --] (]) 22:08, 4 December 2024 (UTC)
*'''Support''' per reasons discussed above; something generated by an LLM is not truly the editor's opinion. On an unrelated note, have we seen any LLM-powered unapproved bots come in and do things like POV-pushing and spam page creation without human intervention? If we haven't, I think it's only a matter of time. <b>]] (])</b> 23:23, 4 December 2024 (UTC)
*'''Weak oppose''' in the sense that I don't think ''all'' LLM discussion text should be deleted. There are at least a few ESL users who use LLM's for assistance but try to check the results as best they can before posting, and I don't think their comments should be removed indiscriminately. What I do support (although not as a formal ]) is being much more liberal in hatting LLM comments when the prompter has failed to prevent ]/irrelevant/incomprehensible output than we maybe would for human-generated text of that nature. ] 03:05, 5 December 2024 (UTC)
*'''Oppose''' Any comments made by any editors are of their own responsibility and representing their own chosen opinions to hit the Publish Changes button on. If that comment was made by an LLM, then whatever it says is something the editor supports. I see no reason whatsoever to collapse anything claimed to be made by an LLM (whose detectors are 100% not reliable in the first place). If the comment being made is irrelevant to the discussion, then hatting it is already something covered by policy in the first place. This does make me want to start my comments with "As a large language model trained by OpenAI" though just to mess with people trying to push these sorts of policy discussions. ]]<sup>]</sup> 05:29, 5 December 2024 (UTC)
** Or, as ChatGPT puts it,
{{collapse top|width=90%|title=Why banning LLM usage in comments would be detrimental, a ChatGPT treatise}}
{{tq|Banning the use of large language models (LLMs) to assist in writing comments on Misplaced Pages would be a step backward in fostering inclusivity, efficiency, and accessibility within the platform. Here are several key reasons why such a ban would be counterproductive:}}
{{tq|'''1. Improving Accessibility and Participation:''' Misplaced Pages is a global platform, and its contributors come from diverse backgrounds, including those who might not be native English speakers or may struggle with writing clear, concise comments. LLMs can help these contributors express themselves more effectively by generating text that is coherent, well-structured, and grammatically correct. Banning LLMs would disproportionately impact these users, potentially discouraging them from participating in the platform.}}
Perhaps what is needed is a little icon that can be placed in the top right corner of articles needing work. The presence of the icon would indicate that there are tags which need to be addressed on the article's talk page. The advantages would be that at 3/8" x 3/8" it would be fairly unobtrusive, and would also take the place of multiple tags. One icon fits all. ''''']'''''00:14, 1 March 2007 (UTC)
{{tq|'''2. Efficiency and Time-Saving:''' Misplaced Pages editors often engage in lengthy discussions about content, and composing thoughtful comments can be time-consuming. LLMs can assist by quickly drafting responses, summarizing arguments, or offering suggestions for improvement. This helps contributors focus on more substantive aspects of their contributions, such as verifying facts or improving content, rather than getting bogged down by the mechanics of writing.}}
:Interesting thought. There is a division between those tags that are of benefit to the readers and those of benefit to the editors. Indications of a lack of references or a POV problem are of benefit to the readers. Orphan article, merge suggestions, expansion requests, and wikification are really only of benefit to the editors. (Though any of them may encourage a reader to become an editor, and the benefit of that is significant.)
:Accordingly, I'd start by classifying the two types of templates into those two broad categories. The editor only ones could be moved to such an icon (with an invitation for the reader to become an editor/help fix them), but the reader caution ones should not go to the same type of single icon. A different common icon might work for those, but I'm not certain. ] 00:26, 1 March 2007 (UTC)
::Perhaps the little icons can be color coded: red for those tags that are of benefit to the readers and other colors that benefit to the editors. The shape of the icon might also be used (e.g. stop sign shape for more serious tags.) It might be nice if the icons linked to actual tags on the talk page. A division between those tags that are a must to appear on the article page and those that need only be icons might help as well. -- ] 01:56, 1 March 2007 (UTC)
:::Maybe it could be expandable? If a registered editor clicks on the little icon, it would pop out a box with the standard template, like a cross between the popups tool and those template boxes with the link at the top to expand them. —]∴ <b>]]]</b> 12:12, 1 March 2007 (UTC)
I strongly disagree. The templates serve to both inform & remind the casual reader that the article/site is in continuous development, and also act as a lure for curious-readers to become new-editors. Some of the templates could use an aesthetic update (See ]. I really like flamurai's fairly recent ']' additions), but moving them all to the talkpage would be dishonest and disadvantageous. --] 02:55, 1 March 2007 (UTC)
: Not if the icon used is documented well throughout Misplaced Pages's help and support pages. We'd have to make it ubiquitous so everybody knew what it was. The only problem I can see is with the mirrors. We could link the icon itself to an explanation page on what the icon means. If it's done right, that page would automatically be included in the mirrors. The icon might be especially effective if it included the word "Alert!". ''''']'''''04:15, 1 March 2007 (UTC)
::"More icons" is not a popular solution to anything, especially in the top-right corner. See ] for how contentious even that one is; only the featured stars have fairly unanimous approval. And the mirrors can take care of themselves. --] 09:43, 1 March 2007 (UTC)
*Tags are visible for a reason. They invite people to edit. ] 09:02, 1 March 2007 (UTC)
** I agree with Radiant, having the tags on the page does encourage people to fix it. I know I don't look at the talk page of ery article I go to, most editors won't either. However, I think it would be a good idea to create smaller versions of some templates, for articles that need a lot. Some articles have so many tags the tags take up the whole window. I think if they are going to be stacked (cleanup, wikify, sources, notability) then they should use smaller templates, to avoid obscuring the content. Something that only takes 1 or 2 lines with no images. <font color="maroon">]</font>'''<small>]</small>''<font color="navy" face="cursive">]</font>'''''<small>]</small> 20:34, 1 March 2007 (UTC)
{{tq|'''3. Support for Editors with Disabilities:''' Many editors with cognitive or motor impairments may find it difficult to express their thoughts clearly in writing. For these individuals, LLMs offer a valuable tool to communicate their ideas effectively. A ban on using LLMs could create additional barriers for these users, reducing their ability to participate fully in Misplaced Pages's collaborative environment.}}
::*This all goes to a pet peeve of mine about proper tagging and documentation of when these IN-YOUR-FACE trash tags go on the page. Most do not note on the talk with a section describing their gripe. So it's a lazy way out. Perhaps they do invite others to edit, and so have they admittedly goaded me, but '''there is a corollary responsibility'''... some clues left behind for the others who have to '''Guess''' what the editor applying such is thinking. At the very least the current crop of cleanup tags should shout an error message if they are not given a valid talk page section title to merge into a link input. The current crop defaults to the talk page where ninety-nine times out of a hundred there is no section discussing what the tagging editor believes as a problem—letting umptine dozens of editors who happen by later to guess at what the problem may be. I've found articles tagged clean-up for over 15 months and somewhere over 130 edits... so the system clearly needs some adjustments.
{{tq|'''4. Quality and Consistency:''' Large language models can help maintain a consistent tone and clarity in Misplaced Pages discussions. By providing suggestions that align with Misplaced Pages's neutral point of view and formal writing standards, LLMs can improve the overall quality of comments. This consistency is especially important in discussions that involve sensitive topics, where clear and neutral language is critical for maintaining Misplaced Pages's credibility and adherence to its editorial guidelines.}}
As a related aside I was going to post below, See {{Tl|DATE}}, which should help make that problem solution more effective, if people use it. Virtually all the cleanup tags I'm familiar with will be satisfied by that template which needs substituted, but that will come out loud and clear the first time one doesn't! <g> It produces <small><small>{{DATE}}</small></small> as a reminder, and "{{#ifeq:{{NAMESPACE}}|Misplaced Pages| |{{error:not substituted|DATE}}<div style="display:none;">}}date=February 2007</div>" when applied like this: {{Tlx|clean|<nowiki>{{subst:DATE}}</nowiki>}}, for example. That date= after the pipe is precisely the input parameter most of the the IN-YOUR-FACE tags are designed to take. The tagging overloading a page can and should be handled by using a version of ''' '|small=1' '''switching which is common to an increasing number of tags should they be kept on main pages. Another alternative there would be the hide/show tagging modes many navigation templates are sporting these days.
:: The date tagging of such templates has been a good impulse in the right direction, but created need for patrolling parties and BOTs to check on that. But I agree strongly with Phillip, most Banner templates are deleterious to our reputations with the occasional reader and even the regular users. They aid the press perception that we are unreliable. So I like Transhumanist's idea of a iconic tag, but would not make it a right margin tag, but a left margin simple message: '''Editor attention needed''' which would be a link to the article talk page Section where the cleanup and such tag resides... See for example: {{tl|Commons-gallery}} and the smaller but Brassier {{tl|Gallery-link}} (style meant for category page tagging--not shown, see {{cl|Saxony}} for that). {{Commons-gallery|United States Navy ships|c=1}}So I'm thinking of the laid back style of these two Commons-gallery tags (which are showing combinations of three different operations modes between the two examples here), with the size and plain link of that one in the category. As can plainly be seen, the text wraps right about them. {{-}}
{{Commons-gallery|flowers|R=1}}::That Iconic notice could be even more sophisticated in assuming service page similar to the /doc pages now being used for template documentation. That is a local sub-page, an <nowiki>{{/cleanup}}</nowiki> page, which acts as a storage register to some hypothetical <nowiki>{{clean-status}}</nowiki>'' 'display template' ''in a page's head section-- if the register's got includable content, then the'' 'display macro' ''on the article places the edit message automatically and once put in place, never need be removed, as it depends on the content in <nowiki>{{{{PAGENAME}}/cleanup}}</nowiki> for activation and a link to display. So it would hold a simple #if: test like are frequently used in testing for named parameters, if there is nothing to include... the article is clean without a tag display, which stays silent.
{{tq|'''5. Encouraging Constructive Dialogue:''' LLMs can assist in crafting more polite, respectful, and balanced comments, reducing the likelihood of inflammatory or aggressive language. This is particularly important on a platform like Misplaced Pages, where discussions can sometimes devolve into heated exchanges. Rather than banning LLMs, encouraging their use could promote healthier, more constructive conversations.}}
:: The Talk page would hold the actual tag in the section, but the ''''''in your face templates'''''' could then all be put on the talks, and some notice still be given to browsing editors with a few minutes to spare. Whether the categories show the page or the talk page is immaterial--both are article related, so anyone patroling those can do so easily enough.
{{tq|'''6. Transparency and Accountability:''' If concerns exist about misuse (e.g., generating spammy or low-quality comments), these can be addressed through guidelines and oversight mechanisms. Misplaced Pages already has systems in place for identifying and mitigating disruptive behavior, and LLM-generated comments could be subject to the same scrutiny. A ban is an overly simplistic solution to what could be a more nuanced issue, one that could be addressed through better regulation and community involvement.}}
:: The little extra trouble the editor's who are making, what is after all,''''' 'a serious judgment call'''''', will create an impetus to justify their actions since they have to slow down a bit to initiate the talk page section, regardless, and if necessary, install the indicator template per The Transhumanist's suggestion. For my part, I figure anyone adding any such tag in a hurry without judicious consideration, is not someone I want hanging them at all, ever. I would suggest the 'cleanup page' be "dirtied" by a link to the talk section our (now, hopefully, more) dutiful editor tagging the article has to <u>define first</u>.
{{tq|In conclusion, banning the use of large language models on Misplaced Pages would deprive the platform of an important tool for improving accessibility, efficiency, and the quality of discourse. Instead of a ban, the focus should be on establishing guidelines for their responsible use, ensuring that they enhance, rather than detract from, Misplaced Pages's core principles of collaboration, neutrality, and inclusivity.}}
:: Since in the new version tagging templates for talk pages, there should be a edit link to the <nowiki>{{/cleanup}}</nowiki> page, his/her tagging would include adding or editing the talk page section title into the cleanup page to become the end of an autogenerated link in the <nowiki>{{/cleanup}}</nowiki> page. Such an extra page edit is minor and handled by a click, paste (page section title), and save... followed by saving/closing their rationale in the talk. Thus the articles would become less of an eyesore to the readers, and so forth... still satisfying: ''Tags are visible for a reason. They invite people to edit.'' At least for most of the people who count in such cases... the people who already do. We can recruit editors some other way, such considerations should not drive our policies, but what makes the project better overall, and these IN-YOUR-FACE-DUMMY templates crap all over it looking from the outside in.
{{collapse bottom}}
::I'm honestly a bit impressed with the little guy. ]]<sup>]</sup> 05:39, 5 December 2024 (UTC)
:::It is somewhat amusing how easy it is to get these chatbots to output apologia for these chatbots. Too bad it's always so shallow. Probably because the people who inserted those canned responses are shallow people is my opinion. ] (]) 19:44, 6 December 2024 (UTC)
*'''Support''' those who are opposing have clearly never had to deal with trolls who endlessly ]. If I wanted to have a discussion with a chatbot, I'd go and find one. ] (]) 13:14, 5 December 2024 (UTC)
*:What's wrong with just banning and hatting the troll? ] (]) 13:49, 5 December 2024 (UTC)
*:Someone trolling and sealioning can (and should) be blocked under current policy, whether they use an LLM or not is irrelevant. ] (]) 15:22, 5 December 2024 (UTC)
*'''Oppose''' per Rhododendrites. This is a case-by-case behavioral issue, and using LLMs != being a troll. ] (]) 17:30, 5 December 2024 (UTC)
*'''Support''': the general principle is sound - where the substance has been originally written by gen-AI, comments will tend to add nothing to the discussion and even annoy or confuse other users. In principle, we should not allow such tools to be used in discussions. Comments written originally before improvement or correction by AI, particularly translation assistants, fall into a different category. Those are fine. There also has to be a high standard for comment removal. Suspicion that gen-AI might have been used is not enough. High gptzero scores is not enough. The principle should go into policy but under a stonking great caveat - ] takes precedence and a dim view will be taken of generative-AI inquisitors. ] 17:37, 5 December 2024 (UTC)
*'''Support''' If a human didn't write it, humans shouldn't spend time reading it. I'll go further and say that ''LLMs are inherently unethical technology'' and, consequently, ''people who rely on them should be made to feel bad.'' ESL editors who use LLMs to make themselves sound like Brad Anderson in middle management should ''stop doing that'' because it actually gets in the way of clear communication. {{pb}} I find myself unpersuaded by arguments that existing policies and guidelines are adequate here. Sometimes, one needs a linkable statement that applies directly to the circumstances at hand. By analogy, one could argue that we don't really need ], for example, because adhering to ], ], and ] ought already to keep bad material out of biographies of living people. But in practice, it turned out that having a specialized policy that emphasizes the general ethos of the others while tailoring them to the problem at hand is a good thing. ] (]) 18:27, 5 December 2024 (UTC)
*'''Strong support''' - Making a computer generate believable gibberish for you is a waste of time, and tricking someone else into reading it should be a blockable offense. If we're trying to create an encyclopedia, you cannot automate any part of the ''thinking''. We can automate processes in general, but any attempt at automating the actual discussion or thought-processes should never be allowed. If we allow this, it would waste countless hours of community time dealing with inane discussions, sockpuppetry, and disruption.{{pb
}} Imagine a world where LLMs are allowed and popular - it's a sockpuppeteer's dream scenario - you can run 10 accounts and argue the same points, and the reason why they all sound alike is just merely because they're all LLM users. You could even just spend a few dollars a month and run 20-30 accounts to automatically disrupt wikipedia discussions while you sleep, and if LLM usage was allowed, it would be very hard to stop.{{pb
}} However, I don't have much faith in AI detection tools (partially because it's based on the same underlying flawed technology), and would want any assumption of LLM usage to be based on obvious evidence, not just a score on some website. <small>Also, to those who are posting chatgpt snippets here: please stop - it's not interesting or insightful, just more slop</small> ] ] 19:15, 5 December 2024 (UTC)
*:I agree with your assessment “Also, to those who are posting chatgpt snippets here: please stop - it's not interesting or insightful, just more slop” but unfortunately some editors who should ''really'' know better think it’s WaCkY to fill serious discussions with unfunny, distracting “humor”. ] (]) 21:54, 5 December 2024 (UTC)
*::I also concur. "I used the to generate more text" is not a good joke. ] (]) 22:46, 5 December 2024 (UTC)
*'''Strong support''' if you asked a robot to spew out some AI slop to win an argument you’re basically cheating. The only ethical reason to do so is because you can’t speak English well, and the extremely obvious answer to that is “if you can barely speak English why are you editing ''English Misplaced Pages?”'' That’s like a person who doesn’t understand basic physics trying to explain the ] using a chatbot. ] (]) 21:32, 5 December 2024 (UTC)
*:I don't think "cheating" is a relevant issue here. Cheating is a problem if you use a LLM to win and get a job, award, college acceptance etc. that you otherwise wouldn't deserve. But WP discussions aren't a debating-skills contest, they're an attempt to determine the best course of action.
*:So using an AI tool in a WP discussion is not ''cheating'' (though there may be other problems), just as riding a bike instead of walking isn't cheating unless you're trying to win a race. <span style="font-family:cursive">]]</span> 22:36, 5 December 2024 (UTC)
*::Maybe “cheating” isn’t the right word. But I think that a) most AI generated content is garbage (it can polish the turd by making it sound professional, but it’s still a turd underneath) and b) it’s going to be abused by people ]. An AI can pump out text far faster than a human and that can drown out or wear down the opposition if nothing else. ] (]) 08:08, 6 December 2024 (UTC)
*:::Bludgeoning is already against policy. It needs to be more strongly enforced, but it needs to be more strongly enforced uniformly rather than singling out comments that somebody suspects might have had AI-involvement. ] (]) 10:39, 6 December 2024 (UTC)
* '''Support'''; I agree with Remsense and jlwoodwa, among others: I wouldn't make any one AI-detection site the Sole Final Arbiter of whether a comment "counts", but I agree it should be expressly legitimate to discount AI / LLM slop, at the very least to the same extent as closers are already expected to discount other insubstantial or inauthentic comments (like if a sock- or meat-puppet copy-pastes a comment written for them off-wiki, as there was at least one discussion and IIRC ArbCom case about recently). ] (]) 22:10, 5 December 2024 (UTC)
*:You don't need a new policy that does nothing but duplicate a subset of existing policy. At ''most'' what you need is to add a sentence to the existing policy that states "this includes comments written using LLMs", however you'd rightly get a lot of pushback on that because it's completely redundant and frankly goes without saying. ] (]) 23:37, 5 December 2024 (UTC)
*'''Support''' hallucinations are real. We should be taking a harder line against LLM generated participation. I don't think everyone who is doing it knows that they need to stop. ''']'''<span style="border:2px solid #073642;background:rgb(255,156,0);background:linear-gradient(90deg, rgba(255,156,0,1) 0%, rgba(147,0,255,1) 45%, rgba(4,123,134,1) 87%);">]</span> 23:47, 5 December 2024 (UTC)
*'''Comment''' - ] that I imagine we will see more often. I wonder where it fits into this discussion. A user employs ]'s ], search+LLM, to help generate their edit request (without the verbosity bias that is common when people don't tell LLMs how much output they want). ] (]) 03:13, 6 December 2024 (UTC)
*'''Support''' per all above. Discussions are supposed to include the original arguments/positions/statements/etc of editors here, not off-site chatbots. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 03:53, 6 December 2024 (UTC)
*:I also find it pretty funny that ChatGPT ''itself'' said it shouldn't be used, as per the premise posted above by EEng. ] ] <span style="color:#C8102E;"><small><sup>(])</sup></small></span> 03:58, 6 December 2024 (UTC)
*::"sycophancy is a general behavior of state-of-the-art AI assistants, likely driven in part by human preference judgments favoring sycophantic responses" - . They give us what we want...apparently. And just like with people, there is position bias, so the order of things can matter. ] (]) 04:26, 6 December 2024 (UTC)
* (Is this where I respond? If not, please move.) '''LLM-generated prose should be discounted.''' Sometimes there will be a discernible point in there; it may even be what the editor meant, lightly brushed up with what ChatGPT thinks is appropriate style. (So I wouldn't say "banned and punishable" in discussions, although we already deprecate machine translations on en.wiki and for article prose, same difference—never worth the risk.) However, LLMs don't think. They can't explain with reference to appropriate policy and guidelines. They may invent stuff, or use the wrong words—at AN recently, an editor accused another of "defaming" and "sacrilege", thus drowning their point that they thought that editor was being too hard on their group by putting their signature to an outrageous personal attack. I consider that an instance of LLM use letting them down. If it's not obvious that it is LLM use, then the question doesn't arise, right? Nobody is arguing for requiring perfect English. That isn't what ] means. English is a global language, and presumably for that reason, many editors on en.wiki are not native speakers, and those that aren't (and those that are!) display a wide range of ability in the language. Gnomes do a lot of fixing of spelling, punctuation and grammar in articles. In practice, we don't have a high bar to entrance in terms of English ability (although I think a lot more could be done to ''explain'' to new editors whose English is obviously non-native what the rule or way of doing things is that they have violated. And some of our best writers are non-native; a point that should be emphasised because we all have a right of anonymity here, many of us use it, and it's rare, in particular, that I know an editor's race. Or even nationality (which may not be the same as where they live.) But what we do here is write in English: both articles and discussions. If someone doesn't have the confidence to write their own remark or !vote, then they shouldn't participate in discussions; I strongly suspect that it is indeed a matter of confidence, of wanting to ensure the English is impeccable. LLMs don't work that way, really. They concoct things like essays based on what others have written. Advice to use them in a context like a Misplaced Pages discussion is bad advice. At best it suggests you let the LLM decide which way to !vote. If you have something to say, say it and if necessary people will ask a question for clarification (or disagree with you). They won't mock your English (I hope! Civility is a basic rule here!) It happens in pretty much every discussion that somebody makes an English error. No biggie. I'll stop there before I make any more typos myself; typing laboriously on my laptop in a healthcare facility, and anyway ] covers this. ] (])
*I dunno about this specifically but I want to chime in to say that I find LLM-generated messages super fucking rude and unhelpful and support efforts to discourage them. – ] <small>(])</small> 08:15, 6 December 2024 (UTC)
*'''Comment''' I think obvious LLM/chatbot text should at least be tagged through an Edit filter for Recent Changes, then RC Patrollers and reviewers can have a look and decide for themselves. ] <sup>(])</sup> <sub>(])</sub> 11:58, 6 December 2024 (UTC)
*:How do you propose that such text be identified by an edit filter? LLM detections tools have high rates of both false positives and false negatives. ] (]) 12:47, 6 December 2024 (UTC)
*::It might become possible once watermarks (like DeepMind's SynthID) are shown to be robust and are adopted. Some places are likely to require it at some point e.g. EU. I guess it will take a while though and might not even happen e.g. I think OpenAI recently decided to not go ahead with their watermark system for some reason. ] (]) 13:17, 6 December 2024 (UTC)
*:::It will still be trivial to bypass the watermarks, or use LLMs that don't implement them. It also (AIUI) does nothing to reduce false positives (which for our usecase are far more damaging than false negatives). ] (]) 13:30, 6 December 2024 (UTC)
*::::Maybe, that seems to be the case with some of the proposals. Others, like SynthID claim high detection rates, maybe because even a small amount of text contains a lot of signals. As for systems that don't implement them, I guess that would be an opportunity to make a rule more nuanced by only allowing use of watermarked output with verbosity limits...not that I support a rule in the first place. People are going to use/collaborate with LLMs. Why wouldn't they? ] (]) 14:38, 6 December 2024 (UTC)
*:::::I don't think watermarks are a suitable thing to take into account. My view is that LLM usage should be a blockable offense on any namespace, but if it ends up being allowed under some circumstances then we at least need mandatory manual disclosures for any usage. Watermarks won't work / aren't obvious enough - we need something like {{t|LLM}} but self-imposed, and not tolerate unmarked usage. ] ] 18:21, 6 December 2024 (UTC)
*::::::They will have to work at some point (e.g. ). ] (]) 06:27, 7 December 2024 (UTC)
*:Good news! {{u|Queen of Hearts}} is already working on that in {{edf|1325}}. ] (]) 16:12, 6 December 2024 (UTC)
*::See also ]. ] (]) 17:32, 6 December 2024 (UTC)
*'''Comment''' As a practical matter, users posting obvious LLM-generated content will typically be in violation of other rules (e.g. disruptive editing, sealioning), in which case their discussion comments absolutely should be ignored, discouraged, discounted, or (in severe cases) hatted. But a smaller group of users (e.g. people using LLMs as a translation tool) may be contributing productively, and we should seek to engage with, rather than discourage, them. So I don't see the need for a separate bright-line policy that risks erasing the need for discernment — in most cases, a friendly reply to the user's first LLM-like post (perhaps mentioning ], which isn't a policy or guideline, but is nevertheless good advice) will be the right approach to work out what's really going on. ] (]) 15:53, 6 December 2024 (UTC)
*:Yeah, this is why I disagree with the BLP analogy above. There's no great risk/emergency to ban the discernment. ] (]) 17:34, 6 December 2024 (UTC)
*:{{small|Those pesky ] are just the worst!}} ] (]) 18:41, 6 December 2024 (UTC)
*:Some translation tools have LLM ''assistance'', but the whole point of ''generative'' models is to create text far beyond what is found in the user's input, and the latter is clearly what this proposal covers. ] (]) 19:01, 6 December 2024 (UTC)
*::That ''might'' be what the proposal ''intends'' to cover, but it is not what the proposal ''actually'' covers. The proposal ''all'' comments that have been generated by LLMs and/or AI, without qualification. ] (]) 01:05, 7 December 2024 (UTC)
*:::70+% here understand the intention matches the language: ''generated by LLMs etc'' means "originated through generative AI tools rather than human thought", not "some kind of AI was involved in any step of the process". Even LLM translation tools don't actually ''create'' meaningful content where there wasn't any before; the generative AI aspect is only in the use of their vast training data to characterize the semantic context of your input in the form of mathematical relationships between tokens in an embedding space, and then match it with the collection of tokens most closely resembling it in the other language. There is, definitionally, a high level of creative constraint in what the translation output is since semantic preservation is required, something that is ''not'' true for text ''generation''. ] (]) 04:01, 7 December 2024 (UTC)
*::::Do you have any evidence for you assertion that 70% of respondents have interpreted the language in the same way as you? Reading the comments associated with the votes suggests that it's closer to 70% of respondents who don't agree with you. Even if you are correct, 30% of people reading a policy indicates the policy is badly worded. ] (]) 08:34, 7 December 2024 (UTC)
*:::::I think @] has summarized the respondent positions sufficiently below. I also think some portion of the opposers understand the proposal perfectly well and are just opposing anything that imposes participation standards. ] (]) 22:54, 7 December 2024 (UTC)
*::::There will be many cases where it is not possible to say whether a piece of text does or does not contain "human thought" by observing the text, even if you know it was generated by an LLM. Statements like "originated through generative AI tools rather than human thought" will miss a large class of use cases, a class that will probably grow over the coming years. People work with LLMs to produce the output they require. It is often an iterative process by necessity because people and models make mistakes. An example of when "...rather than human thought" is not the case is when someone works with an LLM to solve something like a challenging technical problem where neither the person or the model has a satisfactory solution to hand. The context window means that, just like with human collaborators, a user can iterate towards a solution through dialog and testing, exploring the right part of the solution space. Human thought is not absent in these cases, it is present in the output, the result of a collaborative process. In these cases, something "far beyond what is found in the user's input" is the objective, it seems like a legitimate objective, but regardless, it will happen, and we won't be able to see it happening. ] (]) 10:46, 7 December 2024 (UTC)
*:::::Yes, but this proposal is supposed to apply to just the obvious cases and will hopefully discourage good-faith users from using LLMs to create comments wholesale in general. It can be updated as technology progresses. There's also no reason editors using LLMs to organize/validate their arguments, or as search engines for whatever, ''have'' to copy-paste their raw output, which is much more of a problem since it carries a much higher chance of hallucination. That some people who are especially familiar with how to optimize LLM use, or who pay for advanced LLM access, will be able to deceive other editors is not a reason to ''not'' formally proscribe wholesale comment generation. ] (]) 22:27, 7 December 2024 (UTC)
*::::::That's reasonable. I can get behind the idea of handling obvious cases from a noise reduction perspective. But for me, the issue is noise swamping signal in discussions rather than how it was generated. I'm not sure we need a special rule for LLMs, maybe just a better way to implement the existing rules. ] (]) 04:14, 8 December 2024 (UTC)
*'''Support''' ] ] (]) 18:30, 6 December 2024 (UTC)
* '''Comment''': The original question was whether we should discount, ignore, strikethrough, or collapse chatbot-written content. I think there's a very big difference between these options, but most support !voters haven't mentioned which one(s) they support. That might make judging the consensus nearly impossible; as of now, supporters are the clear !majority, but supporters of ''what''? {{--}} <span style="font-family:cursive">]]</span> 19:32, 6 December 2024 (UTC)
*:That means that supporters support the proposal {{tq|that LLM-generated remarks in discussions should be discounted or ignored, and possibly removed in some manner}}. Not sure what the problem is here. Supporters support the things listed in the proposal - we don't need a prescribed 100% strict procedure, it just says that supporters would be happy with closers discounting, ignoring or under some circumstances deleting LLM content in discussions. ] ] 19:40, 6 December 2024 (UTC)
*:Doing something? At least the stage could be set for a follow on discussion. ] (]) 19:40, 6 December 2024 (UTC)
*:More people have bolded "support" than other options, but very few of them have even attempted to refute the arguments against (and most that have attempted have done little more than handwaving or directly contradicting themselves), and multiple of those who have bolded "support" do not actually support what has been proposed when you read their comment. It's clear to me there is not going to be a consensus for anything other than "many editors dislike the idea of LLMs" from this discussion. ] (]) 00:58, 7 December 2024 (UTC)
*::Arguing one point doesn't necessarily require having to refute every point the other side makes. I can concede that "some people use LLMs to improve their spelling and grammar" without changing my view overriding view that LLMs empower bad actors, time wasters and those with competence issues, with very little to offer wikipedia in exchange. Those that use LLMs legitimately to tidy up their alledgedly competent, insightful and self-sourced thoughts should just be encouraged to post the prompts themselves instead of churning it through an LLM first. ] ] 09:00, 7 December 2024 (UTC)
*:::If you want to completely ignore all the other arguments in opposition that's your choice, but don't expect closers to attach much weight to your opinions. ] (]) 09:05, 7 December 2024 (UTC)
*::::Ok, here's a list of the main opposition reasonings, with individual responses.
*::::'''What about translations?''' - Translations are not up for debate here, the topic here is very clearly generative AI, and attempts to say that this topic covers translations as well is incorrect. No support voters have said the propositions should discount translated text, just oppose voters who are trying to muddy the waters.
*::::'''What about accessibility?''' - This is could be a legitimate argument, but I haven't seen this substantiated anywhere other than handwaving "AI could help people!" arguments, which I would lump into the spelling and grammar argument I responded to above.
*::::'''Detection tools are inaccurate''' - This I very much agree with, and noted in my support and in many others as well. But there is no clause in the actual proposal wording that mandates the use of automated AI detection, and I assume the closer would note that.
*::::'''False positives''' - Any rule can have a potential for false positives, from wp:DUCK to close paraphrasing to NPA. We've just got to as a community become skilled at identifying genuine cases, just like we do for every other rule.
*::::'''LLM content should be taken at face value and see if it violates some other policy''' - hopelessly naive stance, and a massive timesink. Anyone who has had the misfortune of going on X/twitter in the last couple of years should know that AI is not just used as an aid for those who have trouble typing, it is mainly used to and . Anyone who knows how bad the sockpuppetry issue is around CTOPs should be absolutely terrified of when (not if) someone decides to launch a full throated wave of AI bots on Misplaced Pages discussions, because if we have to invididually sanction each one like a human then admins will literally have no time for anything else.
*::::I genuinely cannot comprehend how some people could see how AI is decimating the internet through spam, bots and disinformation and still think for even one second that we should open the door to it. ] ] 10:08, 7 December 2024 (UTC)
*:::::There is no door. This is true for sockpuppetry too in my opinion. There can be a rule that claims there is a door, but it is more like a bead curtain. ] (]) 11:00, 7 December 2024 (UTC)
*:::::The Twitter stuff is not a good comparison here. Spam is already nukable on sight, mass disruptive bot edits are also nukable on sight, and it's unclear how static comments on Misplaced Pages would be the best venue to astroturf political opinions (most of which would be off-topic anyway, i.e., nukable on sight). I'd prefer if people didn't use ChatGPT to formulate their points, but if they're trying to formulate a real point then that isn't disruptive in the same way spam is. ] (]) 02:22, 10 December 2024 (UTC)
*::::::{{tq|it's unclear how static comments on Misplaced Pages would be the best venue to astroturf political opinions}} - by disrupting RFCs and talk page discussions a bad actor could definitely use chatgpt to astroturf. A large proportion of the world uses Misplaced Pages (directly or indirectly) to get information - it would be incredibly valuable thing to manipulate. My other point is that AI disruption bots (like the ones on twitter) would be indistinguishable from individuals using LLMs to "fix" spelling and grammar - by allowing one we make the other incredibly difficult to identify. How can you tell the difference between a bot and someone who just uses chatgpt for every comment? ] ] 09:16, 10 December 2024 (UTC)
*:::::::You can't. That's the point. This is kind of the whole idea of ]. ] (]) 20:22, 13 December 2024 (UTC)
*:::{{tqb|Those that use LLMs legitimately to tidy up their alledgedly competent, insightful and self-sourced thoughts should just be encouraged to post the prompts themselves instead of churning it through an LLM first.}}Social anxiety: Say "I" am a person unconfident in my writing. I imagine that when I post my raw language, I embarrass myself, and my credibility vanishes, while in the worst case nobody understands what I mean. As bad confidence is often built up through negative feedback, it's usually meritful or was meritful at some point for someone to seek outside help. ] (]) 23:46, 8 December 2024 (UTC)
*::::While I sympathise with that hypothetical, ] and we shouldn't make decisions that do long-term harm to the project just because a hypothetical user feels emotionally dependent on a high tech spellchecker. I also think that in general wikipedia (myself included) is pretty relaxed about spelling and grammar in talk/WP space. ] ] 18:45, 10 December 2024 (UTC)
*:::::We also shouldn't do long term harm to the project just because a few users are wedded to idea that LLMs are and will always be some sort of existential threat. The false positives that are an unavoidable feature of this proposal will do far more, and far longer, harm to the project than LLM-comments that are all either useful, harmless or collapseable/removable/ignorable at present. ] (]) 19:06, 10 December 2024 (UTC)
*::::::{{tq|The false positives that are an unavoidable feature of this proposal will do far more, and far longer, harm to the project}} - the same could be said for ]. The reason why its not a big problem for DUCK is because the confidence level is very high. Like I've said in multiple other comments, I don't think "AI detectors" should be trusted, and that the bar for deciding whether something was created via LLM should be very high. I 100% understand your opinion and the reasoning behind it, I just think we have differing views on how well the community at large can identify AI comments. ] ] 09:07, 11 December 2024 (UTC)
*:::::I don't see how allowing shy yet avid users to contribute has done or will do long-term harm. The potential always outweighs rational evaluation of outcomes for those with anxiety, a condition that is not behaviorally disruptive. ] (]) 02:47, 11 December 2024 (UTC)
*::::::I definitely don't want to disallow shy yet avid users! I just don't think having a "using chatgpt to generate comments is allowed" rule is the right solution to that problem, considering the wider consequences. ] ] 08:52, 11 December 2024 (UTC)
*:::::::Did you mean "... disallowed"? If so, I think we weigh-differently accessibility vs the quite low amount of AI trolling. ] (]) 14:10, 11 December 2024 (UTC)
* '''Support''' strikethroughing or collapsing per everyone else. The opposes that mention ESL have my sympathy, but I am not sure how many of them are ESL themselves. Having learnt English as my second language, I have always found it easier to communicate when users are expressing things in their own way, not polished by some AI. I sympathise with the concerns and believe the right solution is to lower our community standards with respect to ] and similar (in terms of ESL communication) without risking hallucinations by AI. ] (]) 02:52, 7 December 2024 (UTC)
* '''Oppose the use of AI detection tools'''. False positive rates for AI-detection are dramatically higher for non-native English speakers. . ~ ] (] • ]) 17:53, 8 December 2024 (UTC)
===Section break 5===
* '''Oppose''' - I'm sympathetic to concerns of abuse through automated mass-commenting, but this policy looks too black-and-white. Contributors may use LLMs for many reasons, including to fix the grammar, to convey their thoughts more clearly, or to adjust the tone for a more constructive discussion. As it stands, this policy may lead to dismissing good-faith AI-assisted comments, as well as false positives, without considering the context. Moreover, while mainstream chatbots are not designed to just mimic the human writing style, there are existing tools that can make AI-generated text more human-like, so this policy does not offer that much protection against maliciously automated contributions. ] (]) 01:12, 9 December 2024 (UTC)
*:'''Oppose''' What @] said is correct, basic AI tools like Grammarly should be allowed (note that grammarly can also change sentences and wording and has generative AI tools) but just blatantly asking ChatGPT to generate a administrator report is different. ] (]) 04:46, 1 January 2025 (UTC)
* '''Oppose''' – Others have cast doubt on the efficacy of tools capable of diagnosing LLM output, and I can't vouch for its being otherwise. If EEng's example of ChatBot output is representative—a lengthy assertion of notability without citing sources—that is something that could well be disregarded whether it came from a bot or not. If used carefully, AI can be useful as an aide-memoire (such as with a spell- or grammar-checker) or as a supplier of more felicitous expression than the editor is naturally capable of (e.g. Google Translate). ] (]) 10:27, 9 December 2024 (UTC)
* '''Comment''' / '''Oppose as written'''. It's not accurate that GPTZero is good at detecting AI-generated content. Citations (slightly out of date but there's little reason to think things have changed from 2023): https://www.aiweirdness.com/writing-like-a-robot/ , https://www.aiweirdness.com/dont-use-ai-detectors-for-anything-important/ . For those too busy to read, a few choice quotes: "the fact that it insisted even one excerpt is not by a human means that it's useless for detecting AI-generated text," and "Not only do AI detectors falsely flag human-written text as AI-written, the way in which they do it is biased" (citing https://arxiv.org/abs/2304.02819 ). Disruptive, worthless content can already be hatted, and I'm not opposed to doing so. Editors should be sharply told to use their own words, and if not already written, an essay saying we'd rather have authentic if grammatically imperfect comments than AI-modulated ones would be helpful to cite at editors who offer up AI slop. But someone merely citing GPTZero is not convincing. GPTZero will almost surely misidentify genuine commentary as AI-generated. So fine with any sort of reminder that worthless content can be hatted, and fine with a reminder not to use ChatGPT for creating Misplaced Pages talk page posts, but not fine with any recommendations of LLM-detectors. ] (]) 20:00, 9 December 2024 (UTC)
*:@], I can't tell if you also oppose the actual proposal, which is to permit hatting/striking obvious LLM-generated comments (using GPTzero is a very minor detail in JSS's background paragraph, not part of the proposal). ] (]) 01:47, 11 December 2024 (UTC)
*:::I support the proposal in so far as disruptive comments can already be hatted and that LLM-generated content is disruptive. I am strongly opposed to giving well-meaning but misguided editors a license to throw everyone's text into an AI-detector and hat the comments that score poorly. I don't think it was ''that'' minor a detail, and to the extent that detail is brought up, it should be as a reminder to use human judgment and ''forbid'' using alleged "AI detectors" instead. ] (]) 03:49, 11 December 2024 (UTC)
* '''Support''' collapsing AI (specifically, ]) comments by behavioral analysis (most actually disruptive cases I've seen are pretty obvious) and not the use of inaccurate tools like ZeroGPT. I thinking hatting with the title "Editors suspect that this comment has been written by a ]" is appropriate. They take up SO much space in a discussion because they are also unnecessarily verbose, and talk on and on but never ever say something that even approaches having substance. Discussions are for human Misplaced Pages editors, we shouldn't have to use to sift through comments someone put 0 effort into and outsourced to a robot that writes using random numbers (that's a major part of how tools like ChatGPT work and maintain variety). If someone needs to use an AI chatbot to communicate because they don't understand English, then they are welcome to contribute to their native language Misplaced Pages, but I don't think they have the right to insist that we at enwiki spend our effort reading comments they but minimal effort into besides opening the ChatGPT website. If really needed, they can write in their native language and use a non-LLM tool like Google Translate. The use of non-LLM tools like Grammarly, Google Translate, etc. I think should still be OK for all editors, as they only work off comments that editors have written themselves. ] <sup>]]</sup> 05:10, 10 December 2024 (UTC)
*:Adding that enforcing people writing things in their own words will actually help EAL (English additional language) editors contribute here. I world with EAL people irl, and even people who have almost native proficiency with human-written content find AI output confusing because it says things in the most confusing, verbose ways using difficult sentence constructions and words. I've seen opposers in this discussion who maybe haven't had experience working with EAL people go "what about EAL people?", but really, I think this change will help them (open to being corrected by someone who is EAL, tho). ] <sup>]]</sup> 05:17, 10 December 2024 (UTC)
*:Also, with regards to oppose comments that discussions are not a vote so closes will ignore AI statements which don't have merit - unedited LLM statements are incredibly verbose and annoying, and clog up the discussion. Imagine multiple paragraphs, each with a heading, but all of which say almost nothing, they're borderline ]y. Giving the power to HAT them will help genuine discussion contributors keep with the flow of human arguments and avoid scaring away potential discussion contributors who are intimidated or don't feel they have the time to read the piles of AI nonsense that fill the discussion. ] <sup>]]</sup> 06:38, 10 December 2024 (UTC)
* '''Support''' (removing) in general. How is this even a question? There is no case-by-case. It is a fundamental misunderstanding of how LLMs work to consider their output reliable without careful review. And which point, the editor could have written it themselves without inherent LLM bias. The point of any discussion is to provide analytical response based on the ''context'', not have some tool regurgitate something from a training set that sounds good. And frankly, it is disrespectuful to make someone read "AI" responses. It is a tool and there is a place and time for it, but not in discussions in an encyclopedia. — <small> ] <b>∣</b> ]</small> 15:41, 10 December 2024 (UTC)
*'''Strong Support'''. I'm very interested in what you (the generic you) have to say about something. I'm not remotely interested in what a computer has to say about something. It provides no value to the discussion and is a waste of time. ] (]) 18:06, 10 December 2024 (UTC)
*:Comments that provide no value to the discussion can already be hatted and ignored regardless of why they provide no value, without any of the false positive or false negatives inherent in this proposal. ] (]) 18:25, 10 December 2024 (UTC)
*::Indeed, and that's fine for one-offs when a discussion goes off the rails or what-have-you. But we also have ] for disruptive behavior, not working collaboratively, etc. I'm suggesting that using an AI to write indicates that you're not here to build the encyclopedia, you're here to have an AI build the encyclopedia. I reiterate my strong support for AI-written content to be removed, struck, collapsed, or hatted and would support further measures even beyond those. ] (]) 21:54, 11 December 2024 (UTC)
*:::There are two sets of people described in your comment: those who use AI and those who are NOTHERE. The two sets overlap, but nowhere near sufficiently to declare that everybody in the former set are also in the latter set. If someone is NOTHERE they already can and should be blocked, regardless of how they evidence that. Being suspected of using AI (note that the proposal does not require proof) is not sufficient justification on its own to declare someone NOTHERE, per the many examples of constructive use of AI already noted in this thread. ] (]) 22:03, 11 December 2024 (UTC)
*::::To reiterate, I don't believe that any use of AI here is constructive, thus using it is evidence of ], and, therefore, the set of people using AI to write is completely circumscribed within the set of people who are NOTHERE. Please note that I am referring to users who use AI-generated writing, not users suspected of using AI-generated writing. I won't be delving into how one determines whether someone is using AI or how accurate it is, as that is, to me, a separate discussion. This is the end of my opinion on the matter. ] (]) 23:26, 11 December 2024 (UTC)
*:::::You are entitled to your opinion of course, but as it is contradicted by the evidence of both multiple constructive uses and of the near-impossibility of reliably detecting LLM-generated text without false positives, I would expect the closer of this discussion to attach almost no weight to it. ] (]) 00:42, 12 December 2024 (UTC)
*:::::I am ESL and use LLMs sometimes because of that. I feel like I don't fit into the NOTHERE category. It seems like you do not understand what they are or how they can be used constructively. ] (]) 01:43, 12 December 2024 (UTC)
*::::::No, I understand. What you're talking about is no different from using Google Translate or asking a native-speaker to translate it. You, a human, came up with something you wanted to convey. You wrote that content in Language A. But you wanted to convey that message that you - a human - wrote, but now in Language B. So you had your human-written content translated to Language B. I have no qualms with this. It's your human-written content, expressed in Language B. My concern is with step 1 (coming up with something you want to convey), not step 2 (translating that content to another language). You write a paragraph for an article but it's in another language and you need the paragraph that you wrote translated? Fine by me. You ask an AI to write a paragraph for an article? Not fine by me. Again, I'm saying that there is no valid use case for AI-written content. ] (]) 15:59, 12 December 2024 (UTC)
*:::::::It seems very likely that there will be valid use cases for AI-written content if the objective is maximizing quality and minimizing errors. Research like demonstrate that there will likely be cases where machines outperform humans in specific Misplaced Pages domains, and soon. But I think that is an entirely different question than potential misuse of LLMs in consensus related discussions. ] (]) 16:25, 12 December 2024 (UTC)
*:::::::But your vote and the proposed above makes not distinction there. Which is the main issue. Also not to be pedantic but every prompted to a LLM is filled out by a human looking to convey a message. Every time someone hits publish on something here it is that person confirming that is what they are saying. So how do we in practice implement what you suggest? Because without a method better than vibes it's worthless. ] (]) 18:53, 12 December 2024 (UTC)
*::::::::The proposal specifies content ''generated'' by LLMs, which has a specific meaning in the context of generative AI. If a prompt itself conveys a meaningful, supported opinion, why not just post that instead? The problem comes when the LLM adds more information than was provided, which is the whole point of generative models. ] (]) 01:52, 13 December 2024 (UTC)
* '''Yes''' in principle. But in practice, LLM detectors are not foolproof, and there are valid reasons to sometimes use an LLM, for example to copyedit. I have used Grammarly before and have even used the Microsoft Editor, and while they aren't powered by LLMs, LLMs are a tool that need to be used appropriately on Misplaced Pages. ] ] 19:55, 10 December 2024 (UTC)
* '''Support'''. Using LLM to reply to editors is lazy and disrespectful of fellow editor's time and brainpower. In the context of AFD, it is particularly egregious since an LLM can't really read the article, read sources, or follow our notability guidelines. {{pb}} By the way. {{tq|gptzero and other such tools are very good at detecting this}}. I don't think this is correct at all. I believe the false positive for AI detectors is quite high. High enough that I would recommend not using AI detectors. –] <small>(])</small> 03:23, 11 December 2024 (UTC)
*'''Question''' @]: Since there appears to be a clear consensus against the AI-detectors part, would you like to strike that from the background? ] (]) 14:10, 11 December 2024 (UTC)
* '''Support'''. AI generated text should be removed outright. If you aren't willing to put the work into doing your own writing then you definitely haven't actually thought deeply about the matter at hand. ]]] 14:16, 11 December 2024 (UTC)
*:This comment is rather ironic given that it's very clear you haven't thought deeply about the matter at hand, because if you had then you'd realise that it's actually a whole lot more complicated than that. ] (]) 14:26, 11 December 2024 (UTC)
*::Thryduulf I don't think this reply is particular helpful, and it comes off as slightly combative. It's also by my count your 24th comment on this RFC. ] ] 19:20, 11 December 2024 (UTC)
*::I recognize that AI paraphrased or edited is not problematic in the same ways as text generated outright by an AI. I only meant to address the core issue at steak, content whose first draft was written by an AI system. ]]] 22:16, 17 December 2024 (UTC)
*'''Oppose''' {{re|Just Step Sideways}} The nomination's 2nd para run through https://www.zerogpt.com/ gives "11.39% AI GPT*":{{pb}}{{tqb|I've recently come across several users in AFD discussions that are using LLMs to generate their remarks there. As many of you are aware, gptzero and other such tools are very good at detecting this. I don't feel like any of us signed up for participating in discussions where some of the users are not using their own words but rather letting technology do it for them. Discussions are supposed to be between human editors. <mark>If you can't make a coherent argument on your own, you are not competent to be participating in the discussion.</mark> I would therefore propose that LLM-generated remarks in discussions should be discounted or ignored, and possibly removed in some manner}}{{pb}}The nomination's linked https://gptzero.me/ site previously advertised https://undetectable.ai/ , wherewith how will we deal? Imagine the nomination was at AFD. What should be the response to LLM accusations against the highlighted sentence? ] (]) 17:41, 11 December 2024 (UTC)
* '''Support''' with the caveat that our ability to deal with the issue goes only as far as we can accurately identify the issue (this appears to have been an issue raised across a number of the previous comments, both support and oppose, but I think it bears restating because we're approaching this from a number of different angles and its IMO the most important point regardless of what conclusions you draw from it). ] (]) 19:24, 11 December 2024 (UTC)
*'''Strong support, limited implementation'''. {{tq|1=Misplaced Pages is written by volunteer editors}}, says our front page. This is who ''we'' are, and ''our'' writing is what Misplaced Pages is. It's true that LLM-created text can be difficult to identify, so this may be a bit of a moving target, and we should be conservative in what we remove—but I'm sure at this point we've all run across cases (whether here or elsewhere in our digital lives) where someone copy/pastes some text that includes "Is there anything else I can help you with?" at the end, or other blatant tells. This content should be deleted without hesitation. ] (]) 04:11, 12 December 2024 (UTC)
* '''Support in concept, questions over implementation''' — I concur with {{U|Dronebogus}} that users who rely on LLMs should not edit English Misplaced Pages. It is not a significant barrier for users to use other means of communication, including online translators, rather than artificial intelligence. How can an artificial intelligence tool argue properly? However, I question how this will work in practice without an unacceptable degree of error. <span style="font-family: monospace;">] (he/him)</span> 22:39, 12 December 2024 (UTC)
*:Many, possibly most, online translators use artificial intelligence based on LLMs these days. ] (]) 22:46, 12 December 2024 (UTC)
*::There is a difference between translating words you wrote in one language into English and using an LLM to write a comment for you. <span style="font-family: monospace;">] (he/him)</span> 22:59, 12 December 2024 (UTC)
*:::Neither your comment nor the original proposal make any such distinction. ] (]) 23:34, 12 December 2024 (UTC)
*::::Well since people keep bringing this up as a semi-strawman: no I don’t support banning machine translation, not that I ''encourage'' using it (once again, if you aren’t competent in English please don’t edit here) ] (]) 07:34, 13 December 2024 (UTC)
*:LLMs are incredible at translating, and many online translators already incorporate them, including Google Translate. Accomodating LLMs is an easy way to support the avid not only the ESL but also the avid but shy. It has way more benefits than the unseen-to-me amount of AI trolling that isn't already collapse-on-sight. ] (]) 00:05, 13 December 2024 (UTC)
*::Google Translate uses the same transformer architecture that LLMs are built around, and uses e.g. PaLM to develop more language support (through training that enables zero-shot capabilities) and for larger-scale specialized translation tasks performed through the Google Cloud "" API, but it does not incorporate LLMs into ''translating your everyday text input'', which still relies on NMTs. And even for the API features, the core constraint of ''matching'' input rather than ''generating content'' is still retained (obviously it would be very bad for a translation tool to insert material not found in the original text!). LLMs might be good for translation because they are better at evaluating semantic meaning and detecting context and nuance, but again, the ''generative'' part that is key to this proposal is not present. ] (]) 01:20, 13 December 2024 (UTC)
*:::{{tq|PaLM (Pathways Language Model) is a 540 billion-parameter transformer-based large language model (LLM) developed by Google AI.}} If you meant something about how reschlmunking the outputs of an LLM or using quite similar architecture is not really incorporating the LLM, I believe we would be approaching ] levels of recombination, to which my answer is it is the same ship.{{tqb|obviously it would be very bad for a translation tool to insert material not found in the original text!}} ] (]) 01:29, 13 December 2024 (UTC)
*::::PaLM2 is not used in the consumer app (Google Translate), it's used for research. Google Translate just uses non-generative NMTs to map input to its closes cognate in the target language. ] (]) 01:34, 13 December 2024 (UTC)
*:::::Well, is the NMT really that different enough to not be classified as an LLM? IIRC the definition of an LLM is something that outputs by predicting one-by-one what the next word/"token" should be, and an LLM I asked agreed that NMTs satisfy the definition of a generative LLM, though I think you're the expert here. ] (]) 02:01, 13 December 2024 (UTC)
*::::::Google Translate's NMT hits different enough to speak English much less naturally than ChatGPT 4o. I don't consider it a '''''L'''''LM, because the param count is 380M not 1.8T.
*::::::{{tq|the definition of an LLM is something that outputs by predicting one-by-one what the next word/"token" should be}} No, that def would fit ancient ] tech too. ] (]) 17:50, 13 December 2024 (UTC)
*:::::::Even if you don’t consider it L, I do, and many sources cited by the article do. Since we’ll have such contesting during enforcement, it’s better to find a way that precludes such controversy. ] (]) 20:44, 13 December 2024 (UTC)
*::::::::NMTs, LLMs, and the text-creation functionality of LLMs are fundamentally different in the context of this discussion, which is about content generated through generative AI. NMTs specifically for translation: they are trained on parallel corpora and their output is optimized to match the input as precisely as possible, ''not'' to create novel text. LLMs have different training, including way more massive corpora, and were designed specifically to create novel text. One of the applications of LLMs may be translation (though currently it's too computationally intensive to run them for standard consumer purposes), by virtue of their being very good at determining semantic meaning, but even if/when they do become mainstream translation tools what they'll be used for is still ''not'' generative when it comes to translation output. ] (]) 22:29, 13 December 2024 (UTC)
*:::::::::How will you differentiate between the use of LLM for copyediting and the use of LLM for generation? ] (]) 23:30, 13 December 2024 (UTC)
*::::::::::The proposal is for hatting obvious cases of LLM-generated comments. Someone who just uses an LLM to copyedit will still have written the content themselves and presumably their output would not have the obvious tells of generative AI. ] (]) 23:56, 13 December 2024 (UTC)
*:{{outdent|9}} Not when I tried to use it. Quantitatively, GPTZero went from 15% human to 100% AI for me despite the copyedits only changing 14 words. ] (]) 00:33, 14 December 2024 (UTC)
*::I think there is consensus that GPTZero is not usable, even for obvious cases. ] (]) 00:55, 14 December 2024 (UTC)
*:::Yes, but being as far as 100% means people will also probably think the rewrite ChatGPT-generated. ] (]) 01:18, 14 December 2024 (UTC)
*::::Does it really mean that? All you've demonstrated is that GPTZero has false positives, which is exactly why its use here was discouraged. ] (]) 05:26, 14 December 2024 (UTC)
*:::::My subjective evaluation of what I got copyediting from ChatGPT was that it sounded like ChatGPT. I used GPTZero to get a number. ] (]) 14:18, 14 December 2024 (UTC)
*::::::My guess is that the copyediting went beyond what most people would actually call "copyediting". ] (]) 18:04, 23 December 2024 (UTC)
*:::::::It changed only 14 words across two paragraphs and still retained the same meaning in a way that I would describe it as copyediting. Such levels of change are what those lacking confidence in tone would probably seek anyways. ] (]) 00:15, 24 December 2024 (UTC)
* On one hand, AI slop is a plague on humanity and obvious LLM output should definitely be disregarded when evaluating consensus. On the other hand, I feel like existing policy covers this just fine, and any experienced closer will lend greater weight to actual policy-based arguments, and discount anything that is just parroting jargon. <span class="nowrap">] <sub>]</sub> <sup>(] • ])</sup></span> 23:21, 12 December 2024 (UTC)
*'''Support in principle''', but we cannot rely on any specific tools because none are accurate enough for our needs. Whenever I see a blatant ChatGPT-generated !vote, I ignore it. They're invariably poorly reasoned and based on surface-level concepts rather than anything specific to the issue being discussed. If someone is using AI to create their arguments for them, it means they have no actual argument besides ] and are looking for arguments that support their desired result rather than coming up with a result based on the merits. Also, toasters do not get to have an opinion. <span style="font-family:Papyrus, Courier New">]</span><sup><span style="font-family:Papyrus"><small>'']''</small></span></sup> 05:17, 13 December 2024 (UTC)
*'''Oppose'''. For creating unnecessary drama. First of, the "detector" of the AI bot is not reliable, or at least the reliability of the tool itself is still questionable. If the tool to detect LLM itself is unreliable, how can one reliably point out which one is LLM and which one is not? We got multiple tools that claimed to be able to detect LLM as well. Which one should we trust? Should we be elevating one tool over the others? Have there been any research that showed that the "picked" tool is the most reliable? Second, not all LLMs are dangerous. We shouldn't treat LLM as a virus that will somehow take over the Internet or something. Some editors use LLM to smooth out their grammar and sentences and fix up errors, and there is nothing wrong with that. I understand that banning obvious LLM text per ] are good, but totally banning them is plain wrong. ] ] 22:56, 15 December 2024 (UTC)
*:@], the proposal is to permit editors to collapse/strike ''obvious LLM text'', not to "ban LLM totally". If LLM use is imperceptible, like for tweaking grammar, it's not going to be affected. ] (]) 20:17, 19 December 2024 (UTC)
*'''Support''' with some kind of caveat about not relying on faulty tools or presuming that something is LLM without evidence or admission, based on the following reasons:
*# We have stricter rules around semi-automated editing (rollback, AutoWikiBrowser, etc.) and even stricter rules around fully automated bot editing. These cleanup edits are widely accepted as positive, but there is still the concern about an overwhelming amount of bad edits to wade through and/or fix. A form of that concern is relevant here. Someone could reply to every post in this discussion in just a minute or so without ever reading anything. That's inherently disruptive.
*# Nobody who is voting "oppose" is using an LLM to cast that vote. The LLM comments have been left by those supporting to make a point about how problematic they are for discussions like this. I think this reflects, even among oppose voters, a developing community consensus that LLM comments will be disregarded.
*# If the rule in practice is to disregard LLM comments, not writing that rule down does not stop it from being the rule, consensus, or a community norm. It just makes the rule less obvious and less clear.
*# It's disrespectful for an editor to ask someone to spend their time reading a comment if they couldn't be bothered to spend any time writing it, and therefore a violation of the policy ], "{{tq|treat your fellow editors as respected colleagues with whom you are working on an important project.}}"
* Also, I don't read the proposal as a ban on machine translation in any way. ] (]) 00:01, 18 December 2024 (UTC)
*:@], above @] said their !vote was created by LLM. ] (]) 20:14, 19 December 2024 (UTC)
* I am '''strongly opposed''' to banning or ignoring LLM-made talk page comments ''just'' because they are LLM-made. I'm not a big fan of LLMs at all; they are actually useful only for some certain things, very few of which are directly relevant to contributing to Misplaced Pages in English or in any other language. However, some of those things ''are'' useful for this, at least for some humans, and I don't want to see these humans being kicked out of the English Misplaced Pages. I already witnessed several cases in which people whose first language is not English tried writing talk page responses in the English Misplaced Pages, used an LLM to improve their writing style, and got their responses ignored ''only'' because they used an LLM. In all those cases, I had strong reasons to be certain that they were real humans, that they meant what they wrote, and that they did it all in good faith. Please don't say that anyone who wants to contribute to the English Wikipeida should, in the first place, know English well enough to write a coherent talk page comment without LLM assistance; occasionally, I kind of wish that it was like that myself, but then I recall that the world is more complicated and interesting than that. Uses of LLMs that help the English Misplaced Pages be more inclusive for good-faith people are good. Of course, defining what good faith means is complicated, but using an LLM is not, ''by itself'', a sign of bad faith. --] (]) 04:52, 19 December 2024 (UTC)
*:Those concerned about their English should use translation software rather than an llm. Both might alter the meaning to some extent, but only one will make things up. (It's also not a sure assumption that llm text is coherent talkpage text.) ] (]) 07:44, 19 December 2024 (UTC)
*::@] The dividing line between translation software and LLM is already blurry and will soon disappear. It's also rare that translation software results in coherent talkpage text, ''unless'' it's relying on some (primitive) form of LLM. So if we're going to outlaw LLMs, we would need to outlaw any form of translation software, and possibly any text-to-speech software as well. <span style="font-family:cursive">]]</span> 23:41, 19 December 2024 (UTC)
*:::The distinctions have already been covered above, and no we would not have to. There is an obvious difference between software intended to translate and software intended to generate novel text, and users are likely to continue to treat those differently. ] (]) 02:49, 20 December 2024 (UTC)
*'''Strong support'''. LLM-generated content has no place anywhere on the encyclopedia. ] (]) 10:27, 19 December 2024 (UTC)
*'''Strong oppose''' to the proposal as written. Misplaced Pages already suffers from being ] in a ] ] and a refusal to move with the technological times. Anyone who remembers most Wikipedians' visceral reaction to ] and ] when they were first introduced will observe a striking similarity. Yes, those projects had serious problems, as do LLM-generated comments. But AI is the future, and this attitude of "]" will ultimately lead Misplaced Pages the way of ''Encyclopædia Britannica''. Our discussion needs to be how best to change, not how to avoid to change. <span style="font-family:cursive">]]</span> 23:54, 19 December 2024 (UTC)
*:{{smalldiv|1=The main objection to VE and a major objection to FLOW was the developers' insistence on transforming Wikitext to HTML for editing and then transforming that back to Wikitext. ] (]) 01:31, 20 December 2024 (UTC)}}
*::True. Then, as now, there were many valid objections. But IIRC, there was limited discussion of "Let's figure out a better way to improve", and lots of "Everything is fine; don't change anything, ever." That attitude concerns me. <span style="font-family:cursive">]]</span> 01:52, 20 December 2024 (UTC)
*:I oppose the proposal but I think the comparison to FLOW and VisualEditor is beyond silly. Those things did not exist outside of a MediaWiki context. LLMs are a global issue. ] (]) 17:11, 28 December 2024 (UTC)
*'''Support'''. I'm not even slightly swayed by these "it'll be too hard to figure out" and "mistakes could be made" and "we can't be 100% certain" sorts of arguments. That's true of {{em|everything}} around here, and its why we have an admins-must-earn-a-boatload-of-community-trust system, and a system of review/appeal of decisions they (or of course non-admin closers) make, and a consensus-based decisionmaking system more broadly. {{U|JoelleJay}} has it exactly right: {{tq|having a policy that permits closers to discount apparently-LLM-generated contributions will discourage good-faith editors from using LLMs irresponsibly and perhaps motivate bad-faith editors to edit the raw output to appear more human, which would at least involve some degree of effort and engagement with their "own" arguments.}} And as pointed out by some others, the "it'll hurt non-native-English speakers" nonsense is, well, nonsense; translation is a different and unrelated process (though LLMs can perform it to some extent), of remapping one's {{em|own}} material onto another language.<!-- --><p>I'm also not in any way convinved by the "people poor at writing and other cognitive tasks needs the LLM to help them here" angle, because ] is required. This is work (albeit volunteer work), it is ] a game, a social-media playground, a get-my-ideas-out-there soapbox, or a place to learn how to interact e-socially or pick up remedial writing skills, nor a venue for practicing one's argument techiques. It's an encyclopedia, being built by people who – to be productive contributors instead of a draining burden on the entire community – {{em|must}} have: solid reasoning habits, great judgement (especially in assessing reliability of claims and the sources making them), excellent writing skills of a highly particularized sort, a high level of fluency in this specific language (in multiple registers), and a human-judgement ability to understand our thick web of policies, guidelines, procedures, and often unwritten norms, and how they all interact, in a specific contextual way that may vary greatly by context. None of these is optional. An LLM cannot do any of them adequately (not even write well; their material sticks out like a sore thumb, and after a while you can even tell which LLM produced the material by its habitual but dinstictive crappy approach to simulating human thought and language).</p><!-- --><p>In short, if you {{em|need}} an LLM to give what you think is meaningful input into a decision-making process on Misplaced Pages (much less to generate mainspace content for the public), then you {{em|need}} to go find something else to do, something that fits your skills and abilities. Saying this so plainly will probably upset someone, but so it goes. I have a rep for "not suffering fools lightly" and "being annoying but correct"; I can live with that if it gets the right decisions made and the work advanced. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 05:49, 22 December 2024 (UTC)</p><p>PS, something that came up more recently than my original post above: If anyone's wondering why some of us are such "AI" skeptics, its because the technology is badly, badly faulty, producing multiple blatant factual errors even in short material, entirely fictive "hallucinations", direct forgery of sourcing, nested chains of error compounded upon error when context isn't gleaned properly, disingenuous attempts to hide that it is lying, and worse. A few days ago, I got ChatGPT 4o to literally {{em|lose its f#*$ing mind}}: I had it generate some short code (very simple one-liner regex) with a really obvious error, so I pointed out the error and gave it documentation that proved it was an error. It conceded the error and even explained what the error was and why it was erroneous, then said how it was going to fix it. And ... proceeded to output the same error again (in just one of three examples, the other two being correct). Fascinated and horrified by this, I tried for over half an hour to get it to produce a correct example, and it was utterly incapable of doing it. It knew the error was an error and what that error was and why, spelled out what the correct approach should be, then repeated the error {{em|every single time}} (always at the first occurrence, or always if the only occurrence). I've captured that session and will be doing a write-up about it. This is much, much worse that a "hallucination", being an abject inability to stop doing what it already knows is absolutely wrong. When people have fears like "If I had a house AI, and it was in control of the bathwater temperature, it might boil my children alive", they are not paranoid or unreasonable. My experiment with ChatGPT proves this conclusively. If the AI can (with trivial effort) be put into a crazy failure-looping state where it knows it's doing or about to do something wrong but insists on doing it anyway – i.e. during its take-an-action phase it completely loses connection to reality, even it's internal reality much less external input telling it "no!" – then we are in grave danger. This is essentially the mental state of a psychopath: "I know I shouldn't grab my neighbor's little daughter and strangle her to death, but I just can't stop myself." <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 01:42, 28 December 2024 (UTC)</p>
*:The problem with all that is that we ''already'' have a policy that allows the hatting or removal of comments that are actually problematic because of their content (which are the only ones that we should be removing) without regard for whether it was or was not written by LLM. Everything that actually should be removed can be removed already. ] (]) 11:39, 22 December 2024 (UTC)
*::If that's "the problem with all that", then it is not any kind of problem at all. It's entirely normal in our ] material to reiterate a principle defined in one place for contextual application at another, and to extrapolate from a general principle to a more specific application. We do this often to cut through the exact kind of wikilawyering we're facing over this issue: there's not a {{em|specific rule}} against LLM-generated !voting, so the argument is (again and again in this thread) to permit it (unless it's such senseless gibberish that it would be removed anyway even if no LLM were involved). The community clearly doesn't actually want that result (or more accurately, there is not a consensus in favor of it), though this {{em|specific}} proposal's approach to thwarting the "AI"-spamming of our decision-making processes might not be perfect. To me, it's a step in the right direction. If it were implemented this way and some uncommon issue arose with that implementation, then we'd tweak it to address that micro-problem. We must not continue to avoid addressing the macro-problem just because someone can imagine edge cases that might not work out ideally. That, too, is true of all of our P&G and process. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 01:15, 28 December 2024 (UTC)
*:People who have good reading skills, great judgement, and solid reasoning habits enough to find problems in existing articles don't necessarily have great interpersonal writing/communication skills or the confidence. Meanwhile, for all LLM is bad at, it is very good at diluting everything you say to become dry, dispassionate, and thus inoffensive. ] (]) 15:26, 22 December 2024 (UTC)
*::I doubt that anyone would seriously object to some ultra-hothead running their post through an LLM with a query like "Can you see anything in this that might come off as aggressive or offensive, and suggest a revision that only affects that aspect of the material?" The result might not even be noticeable as LLM-modified. If it doesn't stick out as LLM garbage, there there is no way for this proposal to affect such a post, because no one here is a mind-reader (we cannot magically detect through remote sensing that someone toned their rant down with LLM help). So, this proposal is not broken (at least not with regard to that scenario). That said, the main reason that WP:COMPETENCE was written (and it's one of the essays that, like ] and ], has become "operative" within the community as if a policy or guideline) is the very "don't necessarily have great interpersonal ... skills" issue you mention. That is, lacking those skills to a serious enough degree makes one not competent to work on a collaborative encyclopedia project, and one will eventually be ejected after causing enough disruption. Something we don't need is LLMs masking for a while that someone has this kind of competence failure; it will just drag out the inevitable. By way of analogy: if I were a kleptomaniac and just unable to stop myself from shoplifting, it would not be okay for me to use a device that scrambled stores' surveillance camera footage to make it more likely for me to get away with more shoplifting (and there would certainly be no obligation on the part of the store owner to turn their cameras off, or to take no action if they catch me stealing, just because I tell them I'm a kleptomaniac and my unconstructive behavior isn't something I can manage. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 01:15, 28 December 2024 (UTC)
*:::People who can't communicate that well often won't attempt to burn others down. I don't think there's any disruption or substantial additional investment in accommodating those who won't burn others down (which I'd say is the majority) by reading their perfectly comprehensible AI-diluted arguments. (Scrambling footage is like erasing the memories of the incident, which I don't think is a good analogue of the issue at hand. I'd say it's more like working with someone who stinks and masks that with perfume.) ] (]) 00:05, 29 December 2024 (UTC)
*:I'm pretty sure most people here understand why there are AI skeptics. I also hate ChatGPT. But there's a difference between my personal opinion of ChatGPT and the fact that someone using ChatGPT to communicate is still communicating. The risk of your house AI hallucinating is that your children get boiled alive. The risk of ChatGPT hallucinating on a talk page is that they make a dumb, disregardable argument, of the kind that humans pump out by the thousands. (Someone linked an example of some AfD delete !votes generated by AI and frankly they're better reasoned than a lot of the stuff humans post.) ] (]) 17:32, 28 December 2024 (UTC)
*:(The bigger issue is people using Misplaced Pages ''as ChatGPT'' -- i.e. posting the prompts, not the responses -- but, like much of what is being discussed here, that is already stuff that can be removed.) ] (]) 17:36, 28 December 2024 (UTC)
*ok, I agree with @], so therefore my vote is '''Support.''' ] (]) 12:41, 25 December 2024 (UTC)
*'''Support'''. Sure I have questions about detection, but I don't think it means we shouldn't have a policy that explicitly states that it should not be used (and can be ignored/hatted if it is). Judging solely based on content (and no wp:bludgeoning, etc.) is unsustainable IMO. It would mean taking every wall of text seriously until it's clear that the ''content'' is unhelpful, and LLMs are very good at churning out plausible-sounding bullshit. It wastes everyone's time. If cognitive impairments or ESL issues make it hard to contribute, try voice-to-text, old-school translation software, or some other aid. LLMs aren't really ''you''.--] (]) 11:27, 23 December 2024 (UTC)
* '''Comment'''. While I agree with the sentiment of the request, I am at a loss to see how we can identify LLM generated comments in a consistent manner that can scale. Yes, it might be easier to identify egregious copy paste of wall of text, but, anything other than that might be hard to detect. Our options are:
:# Robust tooling to detect LLM generated text, with acceptably low levels of false positives. Somewhat similar to what Earwig does for Copyvios. But, someone needs to build it and host it on WMTools or at a similar location.
:# Self certification by editors. Every edit / publish dialogbox should have a checkbox for "Is this text LLM generated" with y/n optionality.
:# Editors playing a vigilante role in reading the text and making a personal call on other editors' text. Obviously this is least preferred.
: These are my starting views. ] (]) 00:37, 24 December 2024 (UTC)
::A couple of days ago, an editor ran a new article through GPTzero, and was told that it was 99.8% likely to be AI-generated. I ran the same revision of the same article through the same tool the next day, and it told me that it was 98.3% likely to be human-written.
::Now we're left scratching our heads: Why the difference? Which answer is correct? ] (]) 04:36, 26 December 2024 (UTC)
*'''Strong oppose''' as it's impossible to enforce. Also LLMs are a valid and useful ] tool. – ] 05:18, 24 December 2024 (UTC)
*'''Bonus suggestion!''': I'm curious what Wikipedians think about this so let's try this. Many of the comments here discuss the impracticality of determining whether a user's comments are AI generated (i.e. gptzero isn't perfect), and many give valid arguments for using LLMs (i.e. ]). If an argument is suspected to be written by LLM, I propose that editors should examine the user. Take a look at their listed contributions, and if they seem to have a habit of using AI, open a discussion on their talk page. If the user has a habit of using AI and doesn't recognize the inherent problems and refuses to change, this can be brought to ] for potential blocks. If (and only if) the person is blocked for using AI, their comments can be ignored. Or just ask ChatGPT to summarize them for you lol ] (]) 06:12, 25 December 2024 (UTC)
*:I think that the general idea here is good: As much as possible, treat each account individually, and handle LLM use as a behavioral problem when it's actually a practical problem (i.e., not when it seems to be accurate and seems to be appropriate). ] (]) 04:38, 26 December 2024 (UTC)
*:Except a substantial portion of the input in this thread is disagreement with the idea that English being someone's second language is an excuse for LLM-generated content at all. Translation of one's own material is an entirely different process (even if often leveraged by LLMs set to a different task than trying to generate what they "think" is new material that will pass as human-authored). I'm skeptical that any of the other things you're accepted as "valid arguments" from the pro-LLM or LLM-accepting side of this debate have consensus as valid, either. But go ahead and spell them out and we'll see. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 01:30, 28 December 2024 (UTC)
* '''Strong support''' the removal of any obvious, low effort AI-generated post. I recently came across a user such examples. When called out on it and posted a comment saying, amongst other things "''HAHAHAHHAHAHAHAHAHAHHAHAHAHAHAHA. Yes, some of it might be. Because I don't have time to argue with, in my humble opinion, stupid PHOQUING people.''" and "''YOUUUUUUUUUUUUUUUUUUUUUUUUUUUU are assuming bath faith in me.''"
:They were later blocked as a sock evading a global lock.
:Currently it is too easy for trolls to game ] and AI to waste people's time arguing with their bot-generated replies. Using AI to write your posts for you makes it difficult for others to assume good faith. I am ok with obvious exceptions like a non-native speaker using AI to help them articulate their point. ] (]) 21:29, 25 December 2024 (UTC)
* '''Support''' for any and all reasons above. I'd be in favor of entirely banning AI-written text on the platform in articlespace as well. <!-- Template:Unsigned --><small class="autosigned">— Preceding ] comment added by ] (] • ]) 00:05, 27 December 2024 (UTC)</small>
*'''Support''' though with caution, as there are the possibility for false positives. ] ''<span style="font-size:small; vertical-align:top;">]</span>''·''<span style="font-size:small; vertical-align:bottom;">]</span>'' 00:14, 29 December 2024 (UTC)
*'''Support''' for now. I believe the foundation should be busy ramping up support in this arena of distraction. IMHO, we are in the calibration phase of the use of these models. We don't feed trolls and we shouldn't tutor LLMs. Since assumption of good faith is not suicide pact, we shouldn't rely overmuch for guidance on edge cases. The issues as I see them are attribution (how do I know where your idea has been?), obedience to social norms (I not-here blocked someone recently for brazenly using ChatGPT to lie about using LLMs; the user proceeded to use GPT to post unblock requests), and a vast canyon between the limited human and financial resources of the foundation and the unlimited resources of bad actors with vast sums of money who would like to see Misplaced Pages less able. I have hopes we can get some higher visibility anti-LLM support (like a flag in my mouseover which always reports a percentage, so I know to check). This fire is burning now. It would be unwise to ignore this much longer. ] (]) 16:28, 29 December 2024 (UTC)
*'''Support''' with the clarification that use of AI assistance is not prohibited, as long as its contribution is <<50%. For example, using Grammarly for spell check and grammar/syntax is OK, but using AI to do your homework is not. ] (]) 02:45, 30 December 2024 (UTC)
*:How do you propose to determine whether an AI's contribution is or is not "<<50%"? ] (]) 12:22, 2 January 2025 (UTC)
*'''Support''' a ban on comments that were primarily generated by AI, with such comments to be deleted or struck-through as appropriate, because it's inherently misleading to pass off a chatbot's words as your own. Using ML-based spell-checkers is fine. I've seen some users call ChatGPT an "accessibility tool", but if you're not capable of communicating on English Misplaced Pages without a LLM doing it for you, then I don't think English Misplaced Pages is a good community for you to participate in. <!-- Template:Unsigned --><small class="autosigned">— Preceding ] comment added by ] (] • ]) 21:45, 31 December 2024 (UTC)</small>
*:Just read ], where an editor was indeffed per ] after exclusively using LLMs to edit, even when responding within that very thread. The situation was a clear case of ], which I surely would've cited in my original comment had the page name come to mind. <span class="nowrap">—] (] | ])</span> 04:34, 3 January 2025 (UTC)
*::That they were banned for CIR shows we don't need anything new to deal with disruption specifically caused by people using LLMs. ] (]) 05:29, 3 January 2025 (UTC)
*'''Support''' A popular notion in many, many other discussions is "our most valuable resource is editor time". This applies here more than in most instances - editors cannot be expected to wear themselves out in engaging at length with the results of someone's one-line prompt to an LLM. Where LLM use in articles is destructive of content and source reliability, in discussions it is destructive of editor good faith. If you can't be bothered to put your arguments into intelligible form, don't participate. If your language capacity is lacking to the extent that you have to have a program ''generate'' (as opposed to polish) your stuff, you probably don't have any business participating either. Human detection ability seems quite sufficient for these cases (and once it ceases to, well, we'll deal with that when it becomes an issue). --<span style="font-family:Courier">]</span> <small>(] · ])</small> 12:00, 2 January 2025 (UTC)
*:{{tpq|Human detection ability seems quite sufficient for these case}} these discussions have already proven that human detection is not reliable, with human-generated comments labelled as AI and AI-generated comments labelled as human. Why should we prohibit LLM-generated content that is accurate, relevant and intelligible? We can already ignore/remove content that is none of those things regardless of whether it is LLM-generated or not. ] (]) 12:21, 2 January 2025 (UTC)
:::If you want a pithy in-a-nutshell: personal effort is buy-in in a discussion among equals. If your personal effort in a discussion is an LLM prompt, no editor should be expected to engage with you. --<span style="font-family:Courier">]</span> <small>(] · ])</small> 12:42, 2 January 2025 (UTC)
::::What matters is whether people are engaging with each other constructively and in good faith. Whether one or both parties is using an LLM is completely irrelevant to both aspects. ] (]) 13:29, 2 January 2025 (UTC)
:::::What matters is whether editors wish to engage with an LLM on Misplaced Pages. https://news.mit.edu/2024/large-language-models-dont-behave-like-people-0723 I don't mind interacting with an LLM for my own use, just not on here. ] (]) 13:42, 2 January 2025 (UTC)
::::::Nobody is forcing you to engage with anybody or anything you don't want to engage with, but you do not get to state who other people are allowed to choose to engage with. As long as someone is engaging constructively and in good faith I don't care whether they are human or machine, because (a) I have no reliable way of knowing, and (b) it is literally irrelevant to me. ] (]) 14:14, 2 January 2025 (UTC)
:::::::{{tq|you do not get to state who other people are allowed to choose to engage with}} Strawman, since I didn't do that. Only you are doing that. ] (]) 14:26, 2 January 2025 (UTC)
::::::::Quite the contrary - you are saying that nobody should be allowed to engage with someone using an LLM because you do not want to engage with someone using an LLM. My position is that everybody should be allowed to choose who they want and do not want to engage with for themselves. ] (]) 14:42, 2 January 2025 (UTC)
*'''Support in principle''' - Using entirely AI-generated text in discussion is not a valuable contribution, since ultimately it is not capable of thought, but there should be leniency for those who are simply using AI to improve something they already wrote. ] (]) 14:55, 2 January 2025 (UTC)
*'''Support in principle''' We don't want LLMs opinions. IF and WHEN we do we'll ask for an extension with some AI making an openig analysis of nominations. But we can not, and want not, to excludes cases where some user forms their opinion chating with some AI, as it was brillianttely shoen above, nor we want to exclude anyone lee proficient with the language just "because it looks like a bot". - ] (]) 18:13, 2 January 2025 (UTC)
*'''Support the principle''' per Nabla. ] (]) 21:23, 2 January 2025 (UTC)
*'''Support in principle, ''strongly'' concerned in potential practice''' - I like the idea of removing what is verifiably generated by a LLM. On the other hand, I've read that autistic writers may be more likely to have their (completely non-AI) writing flagged as potential AI use by automated detectors. I think it could be a problem if a rule that's good in principle could start disproportionately affecting some editors (who are not doing the thing) more than others (who are not doing the thing) in practice, whether that come from human (i.e. other editor) bias or automated tools. - ] (]) 18:36, 3 January 2025 (UTC)
*'''Strongly support''' per ChatGPT (EEng) and SMcC; I'm not at all concerned about edit accessibility to non-native speakers; ], after all, is required to contribute to this project. I also oppose any breaking of the line against AI-generated plausible-sounding and -looking slop. We can't have a Misplaced Pages of LLMs talking to LLMs on how to make LLM content for LLM articles. ]<span style="color: #3558b7;"><sup>]</sup>]</span> 21:53, 4 January 2025 (UTC)
*'''Support''' per SMcCandlish. If someone needs to use a LLM to be able to contribute and is unable to convert the output into something that is not obviously AI-generated, then ] likely applies. It'll be impossible to stop minimal usage cases, but having such a rule in place would at least encourage editors to review their output and stop the unhelpful posting off entire ChatGPT essays to discussion spaces. -- ] - <sup>]</sup>/<sub>]</sub> 01:41, 6 January 2025 (UTC)
*'''Strong... opinion''' -- I think the nuance required here in part is the difference between someone using '''any''' automated tool for assistance, versus true bot-like behavior. I believe that unauthorized bot behavior is already prohibited, which should help address the concerns that we mere humans cannot keep up with LLM bots. I agree, we cannot, but I don't see much of that. I am also not inclined to the "if you cannot write, you cannot contribute"... I can imagine 15 years ago some of us might have made the same statement about spelling and grammar; if you cannot spell properly without auto-correct you have no right to edit an encycolopedia. The are significant number of very intentilligent people who are afflicted with things like dyslexia, aspurgers, etc. who have been contributing using various technology tools for assistance. How may of us have Grammarly or similar running on their web browser? And beyond that tools and what they're called will continue to evolve. I am very much against just banning LLM use; largely because it can turn into an unnecessary witch hunt. There are people who will use the tools constructively, and those who will not. I can see some places where it should ''probably'' be banned (such as using a LLM to determine consensus on a discussion that needs closing (AfD, RM, etc)). But even in those areas, I think many of our existing policies and guidelines already address most of the actual concerns we're seeing when it comes to that activity. Cheifly that as long as people are being held accountable for how they use the tools, then who cares what the tool is called in 2000, 2020 or 2040? So I think the course forward is best served by (1) Consider refinement to ] so that we're encapsulating LLM type bot behavior, as well as some sort of threshold on "non-human" capable editing limits (perhaps as part of ]; (2) make a policy or guidelines very clear, bright line, that a user will be treated the same regardless of what tools they use, LLM or otherwise, and that disruptive editing will be handled accordingly. (2a) perhaps a single-warning template reflective of such, to welcome people who appear to be using LLM, and that they are responsible for their adherence to policy and that LLMs tend to get policy wrong. ] ] 02:48, 7 January 2025 (UTC)
*:I like these proposal ideas, and I believe you've hit the nail on the head on the issue. ] (]) 13:14, 7 January 2025 (UTC)
*:+1 ] 15:16, 7 January 2025 (UTC)
*:The proposal is focused on comments that are '''obviously generated''' by LLM, which would not include non-generative AI processes like Grammarly or translation. The whole issue is arguments that were clearly created by a chatbot etc. doing ''its own'' analysis of a discussion and an editor just pasting that output rather than forming the argument themselves, which results in large amounts of text that other editors/closers then have to read and respond to. ] (]) 22:26, 7 January 2025 (UTC)
*::Right, where one doesn't feel like one is talking with ]. ] (]) 22:52, 7 January 2025 (UTC)
*::To be honest, that's my concern. What if something seems obviously generated by LLM but is entirely human-written? What if certain groups of editors are more likely to produce seemingly LLM text that isn't generated by any LLM at all? Is there a way to control for that? How do we consistently enforce this kind of thing without too many false positives ''or'' false negatives?
*::Replying to the top-level opinion at this point: Most autistic people who would have in the past received an Asperger's diagnosis, barring some other reason, would IMO not be more likely to "need" more assistive technology (LLM or otherwise) to contribute to Misplaced Pages articles and discussions than any other user. However, there have been reports that autistic people may be more likely to produce text that is ''falsely'' positive in AI detection tools. See (I had a second example, I thought, except that I've apparently read my last free article on that site (I bet I read said last article when looking up the ''same'' article when I wrote my !vote a few days back, {{facepalm}}). Not gonna link what I can't (quickly) verify!)) <small>(As an aside, I think ] can come across as a bit... charged? Just something to note.)</small>
*::The mention of Data in particular only heightens my concern because--while no one has accused me yet of using LLM when I write--I ''have'' (on other sites, not here) been accused of being a bot before because of the style of writing I adopt at times. What if editor bias disproportionately plays into ''who'' is suspected of LLM use and who isn't? What if imperfections in automated AI detection only serve to cement the bias? - ] (]) 01:25, 8 January 2025 (UTC)
*:::These questions around controlling for false positives and false negatives are not new, we face them all the time already, for example distinguishing vandalism from good faith contributions. We work through them, but they don't mean we don't have a policy on vandalism. ] (]) 01:41, 8 January 2025 (UTC)
*::::Indeed, that's why my original !vote is (in short) "support but concerned". I definitely think I'd support a policy; I'm just raising questions/concerns I think are worth considering in the process of creating such a policy. I think some part of me is just remembering times I've seen bias negatively affect the project in the past and that part of me is coming out here trying to prevent another situation like that by laying the concerns out. I dunno. - ] (]) 03:59, 8 January 2025 (UTC)
*::::It's much easier to distinguish good-faith contributors: see if they change. ] (]) 04:06, 8 January 2025 (UTC)
*::I think Joelle what you're overlooking in that statement is that ''obviously generated'' is something that is going to be short lived, meaning that it will not be very long before the LLM generated content will be far harder to distinguish. Just like how just a year ago any generative image AI would often get the number and/or placement of fingers wrong on a person's hand, in less than a years time that appears to generally be solved. Today the tell tail signs is even if you ask for someone who is left handed, you'll almost always get an image of a right handed person... But that too will go away shortly. I believe it is (scarily) not too far off, when LLMs can determine the prompt is for Misplaced Pages (by way of seeing the wikimarkup or references to normal wiki policies), and among other things, write in the style of experienced editors, perhaps modeled off of some of us in this very discussion. That will be much more difficult to tell, especially when it learns how to ''not be soo overly polite and apologetic''. Beyond that, I believe there are a lot of people successfully and positively using LLMs already on WP. For those reasons, I proffer that we focus on refining the definitions and parameters for general disruptive editing (such as EW, RRR, etc), what a bot edit/activity is, and perhaps a standardized "friendly welcome" and "friendly notice" for those suspected of using LLMs, and reinforce that the tool matters less than the behavior. I think the analogy I'm going for is that of how we handle socks -- it is not against policy to have multiple accounts, however, when it is disruptive, it is blatantly prohibited. But the signs and symptoms of socks is really what we care about. ] ] 05:02, 8 January 2025 (UTC)
*:::Something can be prohibited even if it is or will be difficult to identify it. Just because we can anticipate AI-generated slop becoming harder to detect doesn't mean it's not still disruptive or that we shouldn't be able to strike it when it is obvious. ] (]) 23:41, 9 January 2025 (UTC)
*'''Strong support''' for striking AI-generated comments. Detection of course will be up to admin discretion, but so is things like incivility and personal attacks; while short snippets of AI generated text are hard to detect, lengthy paragraphs are quite easy to eyeball, and from my experience that's the area where it's most likely to come up and most immediately disruptive. <small> ] (]) (it/she) </small> 22:25, 9 January 2025 (UTC)
*'''Support''' {{TQ|for striking AI-generated comments. Detection of course will be up to admin discretion}} as are other behavioural preoblems. Having read most of the discussion, and having been astonished by the 'individuality' of some machine-generated content, nonetheless, while detection may be less-than-foolproof, I still think we should make the point that such content isn't acceptable. It should be within our capacity to make the distinction between 'machine-generated' content and the use of software to correct grammar or to translate, neither of which should be directly outlawed.] (]) 07:18, 10 January 2025 (UTC)
*:But ''why'' should such content be deemed unacceptbale when there are no problems with it? When there are problems with it, it can and should be dealt with in the same way that those problems are dealt with when written by humans. ] (]) 18:25, 10 January 2025 (UTC)
=== Request for closure ===
:: Handling multiple taggings in the <nowiki>{{/cleanup}}</nowiki> page is easy enough too. The oldest tag is kept on the active part of the page. Additional talk page section titles would simply be added on the noinclude part of the page, oldest listed on top. When a cleanup/expert/copyedit/disputed tag is cleared, before it is deleted, it's self-link to the <nowiki>{{/cleanup}}</nowiki> page can be used to delete the matching section title. The obvious exception is the merge tags, which in the latest generation are far more unobtrusive and less detrimental than most banner tagging.
IMHO, since we're over 30 days and the argument consensus seems lopsided, the community would do well to close this rapidly (as opposed to waiting for additional comments). ] (]) 21:04, 2 January 2025 (UTC)
:Sure it looks lopsided if you only read what has been bolded. When you look beyond at what those bolding support are actually supporting it's not at all clear there is a consensus. Then when you actually look at the arguments made it seems that there is not actually a consensus for anything other more than "some users vocally dislike AI". ] (]) 21:59, 2 January 2025 (UTC)
:: So to me, The Transhumanist's proposal is technically feasible and sufficiently easy to implement that it could at least be tried for a few weeks or months. The other side of this coin is simple -- what proof exists that any of these banner tags have caused an newcomer to begin an editing career? What proof is there that given the link as I propose and that simple message '''Editing help needed''', the reader-customer won't follow the link out of curiosity. If it leads to a few lines describing whatever deficiencies exist, then they may be emboldend to go ahead and make some changes as the tag hanger indicated are needed. Cheers! // <b>]</b><font color="green">]</font> 09:57, 4 March 2007 (UTC)
::If that's so, I'm sure the closer will figure it out. ] (]) 22:14, 2 January 2025 (UTC)
:::I was merely pointing out that BusterD's stated reason for calling for closure now is incorrect. That doesn't mean closing now would necessarily be wrong, just that overwhelming consensus is not a reason for it. ] (]) 22:25, 2 January 2025 (UTC)
::::As a sysop, reacting to LLM-related abuse is virtually all I've done in the last week or so. We have a pressing need for some help from the community, and while I'm open to discussion on this, it's unreasonable to expect humans to keep up with bot-like behavior. I've made my argument above, and I'll not disagree further here. ] (]) 00:08, 3 January 2025 (UTC)
::Many on the “support” side are also supporting with conditions instead of an unconditional support. For instance, many have suggested that LLM that supported grammars are okay.
::The closer must also take it into account. ] ] 11:02, 3 January 2025 (UTC)
* There are multiple breaks and 391 comments now. At this scale, it becomes difficult for a human to digest and summarise it all. AI technology seems well suited to this and so asked Gemini again "Please summarise the consensus of the following RFC:" giving it all the discussion above. Its response was much as before:
----
{{tqb|
See ]. This sort of input would probably be welcome over there. Also, what does everyone think of ]? --] 00:13, 14 March 2007 (UTC)
The RFC on LLM/chatbot comments in discussions is contentious, with a significant number of editors on both sides of the issue.
'''Support'''
As this section is getting close to its sell by date, I will cut and past to there, so that there is a record of this exchange. Please post any additional comments on that page --] 13:00, 17 March 2007 (UTC)
Many editors support the proposal to discount or remove LLM-generated comments in discussions. Their arguments include:
== Making "Show preview" mandatory before saves ==
* LLMs do not have original thoughts or arguments and therefore do not contribute meaningfully to discussions.
This certainly must have been discussed before, but why don't we make it mandatory to click "Show preview" before saving changes? This is how they do it on other Wikipedias, such as the French. − ] <small>( ] • ] • ] )</small> 07:26, 1 March 2007 (UTC)
* LLM-generated comments can be disruptive, wasting editors' time and derailing discussions.
* LLMs can be used by bad-faith actors to manipulate consensus or spread misinformation.
*Editors should be encouraged to participate in discussions using their own words and thoughts.
'''Oppose'''
:Just no. —] <sup>]</sup> 07:55, 1 March 2007 (UTC)
Other editors oppose the proposal, arguing that:
:As a preferences option, maybe, as a mandatory thing for all users, absolutely not. This would be tremendously harmful to vandalfighting (I don't need a preview to revert vandalism, and it would slow it down, this also would likely break certain anti-vandal tools), gnoming (I don't need a preview to change "teh" to "the"), and many other tasks, as well as likely breaking various bots. It's a good idea in principle, but would be better implemented as a "preferences" option. That many more previews being generated would also likely place significant additional load on the servers. ] <small><sup>] ]</sup></small> 19:14, 3 March 2007 (UTC)
* LLMs can be useful tools for editors who have difficulty expressing themselves in English, such as non-native speakers or those with disabilities.
::Show preview is useful, but I am not sure if it is a good idea to make it mandatory to use. ] ] ] ] 14:40, 1 March 2007 (UTC)
* LLM-generated comments should be evaluated on their merits, not their origin.
* Detection of LLM-generated comments is unreliable and could lead to false positives.
* A ban on LLM-generated comments could discourage participation from editors who rely on these tools.
'''Additional points'''
:::I have a suggestion for a middle road here. There is an option in user preferences under the editing tab for "show preview on first edit." I believe (but am not sure) that when new user accounts are created all boxes there are unchecked by default. I imagine it would not be difficult to change the software so that the such new accounts would have that option checked as the default, upon account creation. Certainly if this is not already the default this would cut down on some error filled edits. Such users might even get used to that default and never change it after they discover their preference page exists. Thoughts?--] 17:18, 1 March 2007 (UTC)
* There is disagreement about whether machine translation should be considered LLM-generated content.
I'm with Fuhghettaboutit -- I kind of like that idea. --] 22:30, 1 March 2007 (UTC)
* Some editors believe that LLMs could be used constructively in discussions, for example, to summarize arguments or provide alternative perspectives.
* Others are concerned about the potential for LLMs to be used maliciously, for example, to flood discussions with irrelevant comments or to impersonate other editors.
'''Overall'''
If this could easily be made as a user preference then this idea has potential, you could make it the defult option for all new users. Thus it would not make life too much harder at all for people like us, such as for vandal fighting. However it would at the same time also make the learning curve nicer for the newbies, and put good habits into them from the begining. ] <sup>]</sup> 03:33, 7 March 2007 (UTC)
There is no clear consensus on whether to ban or allow LLM-generated comments in discussions. The discussion highlights the challenges of balancing the potential benefits and risks of using LLMs in a collaborative environment like Misplaced Pages.
Default the option but not mandatory. Since there are times when a preview is unnecessary. 01:35, 16 March 2007 (UTC)
}}
]🐉(]) 21:58, 10 January 2025 (UTC)
That was a good answer but I wanted to get a rough headcount and so asked a supplementary question, "What was the count of the number of support and opposing votes in the discussion?" The answer was:
===Make "Prompt me when entering a blank edit summary" an account creation default===
{{tqb|
:↑:-) On this same issue, we could also make "Prompt me when entering a blank edit summary" the default in preferences upon account creation. This might also straddle a middle road for the ] that users ''always'' be automatically prompted for missing edit summaries.--] 22:56, 1 March 2007 (UTC)
Unfortunately, a precise count of support vs oppose votes in that discussion is difficult to determine definitively for a few reasons:
* '''Some votes are unclear''': Several editors express nuanced positions or change their vote during the discussion.
::Sounds like a good idea to me. Shall we take futher steps to implement it? ] ] ] ] 04:14, 2 March 2007 (UTC)
* '''"Strong" votes aren't quantified''': While many editors use "Strong support" or "Strong oppose", these don't carry extra weight in a simple tally.
* '''Focus shifts''': The initial focus on AI-generated comments broadens to include AI-assistance, making some votes less clear-cut.
However, based on a rough manual count:
:::I agree with Fuhghettaboutit's first idea, but not the second. When creating redirects or new pages, I never bother with the edit summary. The default edit summary that forms when I leave it blank provides enough information: the default edit summary for redirects says that a redirect was created; and the default for a new article can easily indicate whether it's a real article or some useless drivel. If you can work around those, then I could support a blank edit summary prompt. --] 04:40, 2 March 2007 (UTC)
* '''Support''': Around 60-70 votes clearly favor discounting or removing AI-generated comments.
::::Um... You do know that it doesn't prompt for an edit summary when you create a redirect, Thisisbossi. I have that option checked. ]]] 04:56, 2 March 2007 (UTC)
* '''Oppose''': Roughly 30-40 votes lean against the proposal, with varying degrees of opposition.
'''Important Note''': This is an approximation. The actual consensus in such discussions is determined by the closer, who weighs the arguments' quality and policy relevance, not just the number of votes.
Oops... I didn't realise that was already an option -- I haven't played with options for the longest time. My mistake, then! :P --] 05:28, 2 March 2007 (UTC)
}}
This seems to be another good answer – better than we get from most human closes. I made a rough manual count to confirm that the numbers given are reasonable ballpark figures. And it seems to have an impressive grasp of nuance – noticing that several editors were qualifying their votes as strong/weak and that some editors changed their vote. ]🐉(]) 22:02, 10 January 2025 (UTC)
:I figure if this is to have any traction we would need a report on the technical feasibility of implementing even before trying to reach consensus, so I posted about this (in much expanded form) at ].-- 06:40, 2 March 2007 (UTC)
:These feel (from my memory of when I skimmed over the discussion several days ago before my original !vote/comment) like they might be leaving out some relevant points that came up. (Unfortunately I can't quantify that without taking a look which I don't have time to do right now (other than the fact my own concerns didn't make it into the summary, which... fair, I guess, considering I was the only one who raised that specific issue).) <small>(I'm also very surprised it came up with something coherent as well as on topic, but that just has more to do with the fact Gemini (or at least whatever AI summarizes Google searches) told me extremely recently that I could get to Alaska by car without a passport if I drove through the ocean. Not took a ferry but drove... through the water... in a car.)</small> - ] (]) 07:02, 11 January 2025 (UTC)
::The other structural change to the wiki that is needed is to separate the show preview button from the save page button (as well as the what's this wikilink). Some cursor mice, especially on laptops, are not that precise, and mis-clicks are problematic. ] 15:30, 3 March 2007 (UTC)
::Your !vote was a qualified support with concern about false positives affecting editors such as the autistic. That's then a nuanced, both-ways vote and the Gemini summary seems to capture that reasonably well. ]🐉(]) 09:43, 11 January 2025 (UTC)
:For got that "Prompt me when entering a blank edit summary" was an option and just checked mine. Yes, make "Prompt me when entering a blank edit summary" an account creation default. -- ] 23:40, 6 March 2007 (UTC)
:::My vote was mentioned purely because it was the only specific thing I could bring to mind quickly that hadn't ended up in the AI summary. I think Thryduulf's take about what it doesn't make clear more closely matches what I think I was actually feeling about the summary (that it doesn't make clear the wide breadth of what the support !votes are actually saying). - ] (]) 19:08, 11 January 2025 (UTC)
*I support this, for new registrations. — ] <sup>]</sup> 02:48, 8 March 2007 (UTC)
:On the whole that summary matches my impression of discussion, with the exception that it doesn't make it clear that not everyone expressing support is supporting the same thing. ] (]) 14:38, 11 January 2025 (UTC)
:I have strong doubts that Gemini is able to discern support or opposition even in individual !votes, let alone assess one participant's opinion across multiple comments or the relative preponderance of a given opinion across ''different'' participants. I fed it just the material before section break 1, then asked it to list the editors who '''oppose''' banning AI-generated comments. Here was its response: {{tq2|Based on the discussion, the following editors oppose banning AI-generated comments or express concerns about the feasibility of such a ban:{{pb}}Just Step Sideways: Argues against dismissing arguments based on the author rather than their content.<br>Remsense: Believes the downsides of such a policy outweigh the benefits.<br>Chipmunkdavis: Supports admin discretion and emphasizes the difficulty of creating a policy around rapidly evolving AI technology.<br>Jlwoodwa: Acknowledges that not all AI-generated comments are useless and suggests a case-by-case approach.<br>Aaron Liu: Is skeptical about the long-term feasibility of reliably distinguishing between human and AI-generated text.<br>Sean.hoyland: Expresses skepticism about the enforceability of such a rule due to the rapid advancements in AI technology.<br>Gnomingstuff: Strongly opposes a ban, citing the difficulty of enforcement, potential for false positives, and the impact on non-native English speakers.<br>Randy Kryn: Expresses concerns about potentially discouraging the use of AI tools for improving the clarity of writing by non-native English speakers.<br>Selfstudier: Acknowledges the principle of discounting AI-generated comments but questions the reliability of identifying them.}} <br>Somehow I don't think that is how a closer would interpret the !votes from @], @], @], @], or @]... Note that it also did ''not'' manage to identify Thryduulf as an opposer until I asked who '''supported''' striking AI-generated comments:<br>{{tq2|Based on the discussion, the following editors support striking AI-generated comments:{{pb}}Thryduulf: Initially supported discounting or ignoring AI-generated comments, but later withdrew support due to potential downsides.<br>Chipmunkdavis: Initially expressed support for admin discretion, but later shifted to more explicit support for guidance to closers and evaluators.<br>Bluethricecreamman: Strongly supports striking out AI-generated content, especially if it appears insincere or disruptive.<br>Isaacl: Supports striking out AI-generated content and favors sanctions for users who overuse AI to write arguments.<br>Clayoquot: Supports striking out AI-generated comments, comparing them to comments from suspected sock puppets.<br>Lazman321: Strongly supports striking out AI-generated comments, considering them as "pure laziness" and a waste of other editors' time.<br>Seraphimblade: Supports striking out AI-generated comments as they may not reflect the actual thoughts of the editor.}}{{pb}}When I re-fed it the same discussion, it modified its response thusly: {{tq2|Based on the additional excerpt of the discussion, the following editors support striking or collapsing AI-generated comments:{{pb}}Jlwoodwa: Supports discounting or collapsing AI-generated comments, finding them disruptive if used to present arguments in an unnecessarily verbose manner.<br>Gnomingstuff: Opposes a hard ban, but acknowledges that AI-generated comments can be pointless and disruptive.<br>Seraphimblade: Reiterates support for striking AI-generated comments as they may not reflect the editor's thoughts.<br>It's important to note that:{{pb}}Gnomingstuff also raises concerns about the difficulty of enforcing such a policy and potential unintended consequences, like discouraging users from using translation tools.<br>Aaron Liu's test using GPTZero on a human-written comment by Gnomingstuff indicated a 99% probability that it was human-written, suggesting that these tools may not be reliable.}}{{pb}}The last bullet point makes zero sense...<br>It didn't even identify me as supporting the proposal until I specifically asked what it thought my position was.{{pb}}No fucking way should we trust AI's assessment of any kind of consensus for any discussion. ] (]) 23:02, 11 January 2025 (UTC)
::* Perhaps it's better at summarising in a broad-brush way than parsing individual votes. But to clarify the technical details, please say which version of Gemini you used as there seem to be at least five currently. My test was done using Advanced Gemini 1.5 Pro. I've also tried the Deep Research option but am not quite sure when that kicks in. ]🐉(]) 09:57, 12 January 2025 (UTC)
::*:But broad-brush summaries are ''not'' what we want when the intent is to determine consensus among editors, since the AI is clearly not identifying positions accurately and doesn't seem to distinguish between one argument made multiple times by the same person vs by multiple different people. <br>I used Gemini 1.5. ] (]) 19:04, 12 January 2025 (UTC)
Ok, what point is there to having AI summarize consensus? Consensus should be based on the strength of individual arguments, which only an experienced human editor can assess; AI can only guess what arguments look like. It's especially weird to use it here since if, theoretically, the AI summary decides there is consensus against considering AI comments in Misplaced Pages discussions, then that would include AI summary itself, leading to ]. ] (]) 19:41, 11 January 2025 (UTC)
:In principle, I support this. I think, however, the prompt should be disabled when making a minor edit. ] 19:02, 16 March 2007 (UTC)
:* One point is that AI may be better at summarising huge, sprawling discussions like this one. That's because it may have more patience and ability to handle large masses of data. Humans will tend to suffer from ], ] and issues like ] and other ].
:: Also, "beggars can't be choosers". The OP called for a close 10 days ago but no human has rushed to perform this thankless task. Discussions on Misplaced Pages are often left dangling without a clear conclusion and there many other big backlogs.
:: ]🐉(]) 10:32, 12 January 2025 (UTC)
== IParticle creation ==
=== Alternate proposal ===
{{discussion top|result=Redundant proposal, confusingly worded, with no support, and not even any further discussion interest in 10 days. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 05:23, 22 December 2024 (UTC)}}
Hiho, are there any documentations about the impact of not allowing IPs to create new articles? --] 13:13, 8 March 2007 (UTC)
Whereas many editors, including me, have cited problems with accuracy in regards to existing tools such as ZeroGPT, I propose that '''remarks that are blatently generated by a LLM or similar automated system should be discounted/removed/collapsed/hidden'''. ] <sup>] / ]</sup> 10:00, 10 December 2024 (UTC)
:'''Oppose''' as completely unnecessary and far too prone to error per the above discussion. Any comment that is good (on topic, relevant, etc) should be considered by the closer regardless of whether it was made with LLM-input of any sort or not. Any comment that is bad (off-topic, irrelevant, etc) should be ignored by the closer regardless of whether it was made with LLM-input of any sort or not. Any comment that is both bad and disruptive (e.g. by being excessively long, completely irrelevant, bludgeoning, etc) should be removed and/or hatted as appropriate, regardless of whether it was made with LLM-input of any sort. The good thing is that ''this is already policy'' so we don't need to call out LLMs specifically, and indeed doing so is likely to be disruptive in cases where human-written comments are misidentified as being LLM-written (which ''will'' happen, regardless of whether tools are used). ] (]) 11:19, 10 December 2024 (UTC)
:If you've got an article you'd like to submit, you're welcome to do it through ]. If the topic is appropriate and you cite a source, an established editor will create the article for you. ] <small><sup>] ]</sup></small> 15:52, 8 March 2007 (UTC)
:I think this proposal is not really necessary. I support it, but that is because it is functionally identical to the one directly above it, which I also supported. This should probably be hatted. ] ] 18:32, 10 December 2024 (UTC)
:Also, it would just be really easy if the IP users were to register and get their own account. Registering isn't hard, and no e-mail address is required. ] 16:18, 8 March 2007 (UTC)
:What does '''blatantly generated''' mean? Does you mean only where the remark is signed with "I, Chatbot", or anything that ''appears'' to be LLM-style? I don't think there's much in between. <span style="font-family:cursive">]]</span> 19:21, 10 December 2024 (UTC)
::To actually answer your question, 141.51.166.91 (*wink*), there is no data, although I believe that article growth has followed a ] pattern as of late. This growth may be natural, but the extent to which it is affected by the lack IP article creation seems to conplicated to calculate to me. You could look at another language Misplaced Pages that has anon page creation (like the German Misplaced Pages) and compare the results, but there seems to be too many variables to do an efficacious comparison (except w/ alternate universe). I know many editors that are in favor of lifting that restriction, but I'm sure that there are those that aren't. ]<sup>]</sup> § 18:12, 8 March 2007 (UTC)
:'''Procedural close''' per BugGhost. I'd hat this myself, but I don't think that'd be appropriate since it's only the two of us who have expressed that this proposal is basically an exact clone. ] (]) 03:00, 11 December 2024 (UTC)
:::Thanks for at least trying to answer my question :-) So, there is not even a single text on the impact of not allowing IPs to create articles on en-WP? Because, well, from statistics, there doesn't seem to be an effect except that the number of accounts has exploded. --] 22:57, 8 March 2007 (UTC)
{{discussion bottom}}
{{discussion bottom}}
{{ping|Tamzin}} Did you find there was consensus support for handling obvious use of comments through any form of generative AI, regardless of the specific underlying technology (thus not only for large language models)? ] (]) 23:45, 12 January 2025 (UTC)
Ironically, users that edit while logged in are more anonymous to wikipedia readers than those users who edit without logging in, and so display their IP addresses for any other user to see. I have decided to use an account to edit wikipedia, for vanity and laziness reasons, to keep track of my edits and which articles I'm editing. However, I think users with complain about "anonymous" IP editors are doing so ingenuously: I have no idea if the above users that show account names are not the same person, or where they are editing from. An IP editor? I can tell where they are posting from and if that source is unique or pretending to give itself consenusus through "attaboy" posts talking to itself. Only amdins and above can "police" this sort of abuse for logged in editors. For IP editors, anyone can "police" their editing so to speak. Just my input as food for thought but no particular agenda or recommendation. ] 05:12, 9 March 2007 (UTC)
:I've added "or similar AI technologies" to clarify. I don't think there was enough discussion of technical aspects of AI to be more precise than that. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 00:43, 13 January 2025 (UTC)
::Yes and no. Users who are online using a service that employs dynamic IP "change their identity" any time they disconnect and reconnect to their ISP. Being logged in makes one accountable (assuming the account was created in good faith). Plus, an admin can use checkuser to check for sockpuppets or patterns of malicious editing. ] 01:46, 17 March 2007 (UTC)
::My general impression is that most commenters were using the term "LLM" generically, rather than referring to a specific technology. ] (]) 04:28, 13 January 2025 (UTC)
== RfC: Voluntary RfA after resignation ==
==Unfair treatment of Scientology==
{{discussion top|1=There is clear consensus that participants in this discussion wish to retain the "Option 2" status quo. We're past 30 days of discussion and there's not much traffic on the discussion now. It's unlikely the consensus would suddenly shift with additional discussion. --] (]) 18:29, 16 January 2025 (UTC)}}
<!-- ] 22:01, 19 January 2025 (UTC) -->{{User:ClueBot III/DoNotArchiveUntil|1737324070}}
This seems to be going on here. For example, in the opening section of the article ] you can read:
Should ] be amended to:
:However, outside observers—including journalists, lawmakers, and national governing bodies of several countries—have alleged that the Church is an unscrupulous commercial enterprise that harasses its critics and brutally exploits its members.
* '''Option 1'''{{snd}}Require former administrators to request restoration of their tools at the ] (BN) if they are eligible to do so (i.e., they do not fit into any of the exceptions).
* '''Option 2'''{{snd}}<s>Clarify</s> <ins>Maintain the status quo</ins> that former administrators who would be eligible to request restoration via BN may instead request restoration of their tools via a voluntary ] (RfA).
* '''Option 3'''{{snd}}Allow bureaucrats to SNOW-close RfAs as successful if (a) 48 hours have passed, (b) the editor has right of resysop, and (c) a SNOW close is warranted.
'''Background''': This issue arose in one ] and is currently being discussed in an ]. ] (]/]) 21:14, 15 December 2024 (UTC)<br />
I don't think that you would find a sentence like that in the opening section of the articles on ], the ], or ] even though those religions are just as "controversial." I'm not sure if this was the right place to post these comments. Thanks for your attention. ] 02:05, 9 March 2007 (UTC)
'''Note''': There is an ongoing related discussion at {{slink|Misplaced Pages:Village pump (idea lab)#Making voluntary "reconfirmation" RFA's less controversial}}.<br />
'''Note''': Option 2 was modified around 22:08, 15 December 2024 (UTC).
*'''2''' per ]. If an admin wishes to be held accountable for their actions at a re-RfA, they should be allowed to do so. ] ] 21:22, 15 December 2024 (UTC)
*:Also fine with 3 ] ] 22:23, 15 December 2024 (UTC)
* There is ongoing discussion about this at ]. ] (]) 21:24, 15 December 2024 (UTC)
** '''2''', after thought. I don't think 3 provides much benefit, and creating separate class of RfAs that are speedy passed feels a misstep. If there are serious issues surrounding wasting time on RfAs set up under what might feel to someone like misleading pretenses, that is best solved by putting some indicator next to their RFA candidate name. Maybe "Hog Farm ('''RRfA''')". ] (]) 14:49, 16 December 2024 (UTC)
**:{{tq|best solved by putting some indicator next to their RFA candidate name. Maybe "Hog Farm (RRfA)"}} - I like this idea, if option 2 comes out as consensus I think this small change would be a step in the right direction, as the "this isn't the best use of time" crowd (myself included) would be able to quickly identify the type of RFAs they don't want to participate in. ] ] 11:05, 17 December 2024 (UTC)
**::I think that's a great idea. I would support adding some text encouraging people who are considering seeking reconfirmation to add (RRfA) or (reconfirmation) after their username in the RfA page title. That way people who are averse to reading or participating in reconfirmations can easily avoid them, and no one is confused about what is going on. ] (]) 14:23, 17 December 2024 (UTC)
**::I think this would be a great idea if it differentiated against recall RfAs. ] (]) 18:37, 17 December 2024 (UTC)
**:::If we are differentiating three types of RFA we need three terms. Post-recall RFAs are referred to as "reconfirmation RFAs", "Re-RFAS" or "RRFAs" in multiple places, so ones of the type being discussed here are the ones that should take the new term. "Voluntary reconfirmation RFA" (VRRFA or just VRFA) is the only thing that comes to mind but others will probably have better ideas. ] (]) 21:00, 17 December 2024 (UTC)
* '''1''' ] ] 21:25, 15 December 2024 (UTC)
*'''2''' I don't see why people trying to do the right thing should be discouraged from doing so. If others feel it is a waste of time, they are free to simply not participate. ] ] 21:27, 15 December 2024 (UTC)
*'''2''' Getting reconfirmation from the community should be allowed. Those who see it as a waste of time can ignore those RfAs. ] ] 21:32, 15 December 2024 (UTC)
*Of course they may request at RfA. They shouldn't but they may. This RfA feels like it does nothing to address the criticism actually in play and per the link to the idea lab discussion it's premature to boot. ] (]) 21:38, 15 December 2024 (UTC)
*'''2''' per my comments at the idea lab discussion and Queent of Hears, Beeblebrox and Scazjmd above. I strongly disagree with Barkeep's comment that "They shouldn't ". It shouldn't be made mandatory, but it should be encouraged where the time since desysop and/or the last RFA has been lengthy. ] (]) 21:42, 15 December 2024 (UTC)
*:When to encourage it would be a worthwhile RfC and such a discussion could be had at the idea lab before launching an RfC. Best, ] (]) 21:44, 15 December 2024 (UTC)
*::I've started that discussion as a subsection to the linked VPI discussion. ] (]) 22:20, 15 December 2024 (UTC)
*'''1''' <ins>or '''3'''</ins>. RFA is an "expensive" process in terms of community time. RFAs that qualify should be fast-tracked via the BN process. It is only recently that a trend has emerged that folks that don't need to RFA are RFAing again. 2 in the last 6 months. If this continues to scale up, it is going to take up a lot of community time, and create noise in the various RFA statistics and RFA notification systems (for example, watchlist notices and ]). –] <small>(])</small> 21:44, 15 December 2024 (UTC)
*:Making statistics "noisy" is just a reason to improve the way the statistics are gathered. In this case collecting statistics for reconfirmation RFAs separately from other RFAs would seem to be both very simple and very effective. ''If'' (and it is a very big if) the number of reconfirmation RFAs means that notifications are getting overloaded, ''then'' we can discuss whether reconfirmation RFAs should be notified differently. As far as differentiating them, that is also trivially simple - just add a parameter to ] (perhaps "reconfirmation=y") that outputs something that bots and scripts can check for. ] (]) 22:11, 15 December 2024 (UTC)
*:Option 3 looks like a good compromise. I'd support that too. –] <small>(])</small> 22:15, 15 December 2024 (UTC)
*:I'm weakly opposed to option 3, editors who want feedback and a renewed mandate from the community should be entitled to it. If they felt that that a quick endorsement was all that was required then could have had that at BN, they explicitly chose not to go that route. Nobody is required to participate in an RFA, so if it is going the way you think it should, or you don't have an opinion, then just don't participate and your time has not been wasted. ] (]) 22:20, 15 December 2024 (UTC)
*'''2'''. We should not make it ''more difficult'' for administrators to be held accountable for their actions in the way they please. ]<sub>]<sub>]</sub></sub> (]/]) 22:00, 15 December 2024 (UTC)
* Added '''option 3''' above. Maybe worth considering as a happy medium, where unsure admins can get a check on their conduct without taking up too much time. ] (] • she/her) 22:11, 15 December 2024 (UTC)
*'''2''' – If a former admin wishes to subject themselves to RfA to be sure they have the requisite community confidence to regain the tools, why should we stop them? Any editor who feels the process is a waste of time is free to ignore any such RfAs. — ] ⚓ ] 22:12, 15 December 2024 (UTC)
*:*I would also support option '''3''' if the time is extended to 72 hours instead of 48. That, however, is a detail that can be worked out after this RfC. — ] ⚓ ] 02:05, 16 December 2024 (UTC)
*'''Option 3''' per leek. ] (]/]) 22:16, 15 December 2024 (UTC)
*:A further note: option 3 gives 'crats the discretion to SNOW close a successful voluntary re-RfA; it doesn't require such a SNOW close, and I trust the 'crats to keep an RfA open if an admin has a good reason for doing so. ] (]/]) 23:24, 16 December 2024 (UTC)
*'''2''' as per {{noping|JJPMaster}}. Regards, --] (]) 22:20, 15 December 2024 (UTC)
*'''Option 2''' (no change) – The sample size is far too small for us to analyze the impact of such a change, but I believe RfA should always be available. Now that ] is policy, returning administrators may worry that they have become out of touch with community norms and may face a recall as soon as they get their tools back at BN. Having this familiar community touchpoint as an option makes a ton of sense, and would be far less disruptive / demoralizing than a potential recall. Taking this route away, even if it remains rarely used, would be detrimental to our desire for increased administrator accountability. – ] 22:22, 15 December 2024 (UTC)
*{{ec}} I'm surprised the response here hasn't been more hostile, given that these give the newly-unresigned administrator a ] for a year. —] 22:25, 15 December 2024 (UTC)
*:@] hostile to what? ] (]) 22:26, 15 December 2024 (UTC)
*'''2, distant second preference 3'''. I would probably support 3 as first pick if not for recall's rule regarding last RfA, but as it stands, SNOW-closing a discussion that makes someone immune to recall for a year is a non-starter. Between 1 and 2, though, the only argument for 1 seems to be that it avoids a waste of time, for which there is the much simpler solution of not participating and instead doing something else. ] and ] are always there. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 23:31, 15 December 2024 (UTC)
* 1 would be my preference, but I don't think we need a specific rule for this. -- ] (]) 23:36, 15 December 2024 (UTC)
*'''Option 1'''. <s>No second preference between 2 or 3.</s> As long as a former administrator didn't resign under a cloud, picking up the tools again should be low friction and low effort for the entire community. If there are issues introduced by the recall process, they should be fixed in the recall policy itself. ] (]) 01:19, 16 December 2024 (UTC)
*:After considering this further, I prefer option 3 over option 2 if option 1 is not the consensus. ] (]) 07:36, 16 December 2024 (UTC)
*'''Option 2''', i.e. leave well enough alone. There is really not a problem here that needs fixing. If someone doesn’t want to “waste their time” participating in an RfA that’s not required by policy, they can always, well, not participate in the RfA. No one is required to participate in someone else’s RfA, and I struggle to see the point of participating but then complaining about “having to” participate. ] (]) 01:24, 16 December 2024 (UTC)
*'''Option 2''' nobody is obligated to participate in a re-confirmation RfA. If you think they are a waste of time, avoid them. ] (]) 01:49, 16 December 2024 (UTC)
* '''1 or 3''' per Novem Linguae. <span style="padding:2px 5px;border-radius:5px;font-family:Arial black;white-space:nowrap;vertical-align:-1px">] <span style=color:red>F</span> ]</span> 02:35, 16 December 2024 (UTC)
*'''Option 3''': Because it is incredibly silly to have situations like we do now of "this guy did something wrong by doing an RfA that policy explicitly allows, oh well, nothing to do but sit on our hands and dissect the process across three venues and counting." Your time is your own. No one is forcibly stealing it from you. At the same time it is equally silly to let the process drag on, for reasons explained in ]. ] (]) 03:42, 16 December 2024 (UTC)
*:Update: Option 2 seems to be the consensus and I also would be fine with that. ] (]) 18:10, 19 December 2024 (UTC)
*'''Option 3''' per Gnoming. I think 2 works, but it is a very long process and for someone to renew their tools, it feels like an unnecessarily long process compared to a normal RfA. ] (]) 04:25, 16 December 2024 (UTC)
*As someone who supported both WormTT and Hog Farm's RfAs, option 1 > option 3 >> option 2. At each individual RfA the question is whether or not a specific editor should be an admin, and in both cases I felt that the answer was clearly "yes". However, I agree that RfA is a very intensive process. It requires a lot of time from the community, as others have argued better than I can. I prefer option 1 to option 3 because the existence of the procedure in option 3 implies that it is a good thing to go through 48 hours of RfA to re-request the mop. But anything which saves community time is a good thing. <b>]]</b> (] • he/they) 04:31, 16 December 2024 (UTC)
*:I've seen this assertion made multiple times now that {{tpq| requires a lot of time from the community}}, yet nowhere has anybody articulated how why this is true. What time is required, given that nobody is required to participate and everybody who does choose to participate can spend as much or as little time assessing the candidate as they wish? How and why does a reconfirmation RFA require any more time from editors (individually or collectively) than a request at BN? ] (]) 04:58, 16 December 2024 (UTC)
*::I think there are a number of factors and people are summing it up as "time-wasting" or similar:
*::# BN Is designed for this exact scenario. It's also clearly a less contentious process.
*::# Snow closures a good example of how we try to avoid wasting community time on unnecessary process and the same reasoning applies here. Misplaced Pages is not a bureaucracy and there's no reason to have a 7-day process when the outcome is a given.
*::# If former administrators continue to choose re-RFAs over BN, it could set a problematic precedent where future re-adminship candidates feel pressured to go through an RFA and all that entails. I don't want to discourage people already vetted by the community from rejoining the ranks.
*::# The RFA process is designed to be a thoughtful review of prospective administrators and I'm concerned these kinds of perfunctory RFAs will lead to people taking the process less seriously in the future.
*::] (]) 07:31, 16 December 2024 (UTC)
*::Because several thousand people have RFA on their watchlist, and thousands more will see the "there's an open RFA" notice on theirs whether they follow it or not. Unlike BN, RFA is a process that depends on community input from a large number of people. In order to even ''realise that the RFA is not worth their time'', they have to:
*::* Read the opening statement and first few question answers (I just counted, HF's opening and first 5 answers are about 1000 words)
*::* Think, "oh, they're an an ex-admin, I wonder why they're going through RFA, what was their cloud"
*::* Read through the comments and votes to see if any issues have been brought up (another ~1000 words)
*::* None have
*::* Realise your input is not necessary and this could have been done at BN
*::This process will be repeated by hundreds of editors over the course of a week. ] ] 08:07, 16 December 2024 (UTC)
*:::That they were former admins has always been the first two sentences of their RfA’s statement, sentences which are immediately followed by that they resigned due to personal time commitment issues. You do not have to read the first 1000+ words to figure that out. If the reader wants to see if the candidate was lying in their statement, then they just have a quick skim through the oppose section. None of this should take more than 30 seconds in total. ] (]) 13:15, 16 December 2024 (UTC)
*::::Not everyone can skim things easily - it personally takes me a while to read sections. I don't know if they're going to bury the lede and say something like "Also I made 10,000 insane redirects and then decided to take a break just before arbcom launched a case" in paragraph 6. Hog Farm's self nom had two paragraphs about disputes and it takes more than 30 seconds to unpick that and determine if that is a "cloud" or not. Even for reconfirmations, it definitely takes more than 30 seconds to determine a conclusion. ] ] 11:21, 17 December 2024 (UTC)
*:::::They said they resigned to personal time commitments. That is directly saying they wasn’t under a cloud, so I’ll believe them unless someone claims the contrary in the oppose section. If the disputes section contained a cloud, the oppose section would have said so. One chooses to examine such nominations like normal RfAs. ] (]) 18:47, 17 December 2024 (UTC)
*::::::Just to double check, you're saying that whenever you go onto an RFA you expect any reason to oppose to already be listed by someone else, and no thought is required? I am begining to see how you are able to assess an RFA in under 30 seconds ] ] 23:08, 17 December 2024 (UTC)
*:::::::Something in their statement would be an incredibly obvious reason. We are talking about the assessment whether to examine and whether the candidate could've used BN. ] (]) 12:52, 18 December 2024 (UTC)
*::@] let's not confuse "a lot of community time is spent" with "waste of time". Some people have characterized the re-RFAs as a waste of time but that's not the assertion I (and I think a majority of the skeptics) have been making. All RfAs use a lot of community time as hundreds of voters evaluate the candidate. They then choose to support, oppose, be neutral, or not vote at all. While editor time is not perfectly fixed - editors may choose to spend less time on non-Misplaced Pages activities at certain times - neither is it a resource we have in abundance anymore relative to our project. And so I think we, as a community, need to be thought about how we're using that time especially when the use of that time would have been spent on other wiki activities.Best, ] (]) 22:49, 16 December 2024 (UTC)
*:::Absolutely nothing compels anybody to spend any time evaluating an RFA. If you think your wiki time is better spent elsewhere than evaluating an RFA candidate, then spend it elsewhere. That way only those who do think it is a good use of their time will participate and everybody wins. You win by not spending your time on something that you don't think is worth it, those who do participate don't have ''their'' time wasted by having to read comments (that contradict explicit policy) about how the RFA is a waste of time. Personally I regard evaluating whether a long-time admin still has the approval of the community to be a very good use of community time, you are free to disagree, but please don't waste my time by forcing me to read comments about how you think I'm wasting my time. ] (]) 23:39, 16 December 2024 (UTC)
*::::I am not saying you or anyone else is wasting time and am surprised you are so fervently insisting I am. Best, ] (]) 03:34, 17 December 2024 (UTC)
*:::::I don't understand how your argument that it is not a good use of community time is any different from arguing that it is a waste of time? ] (]) 09:08, 17 December 2024 (UTC)
*'''Option 2''' I don't mind the re-RFAs, but I'd appreciate if we encouraged restoration via BN instead, I just object to making it mandatory. ] <sup>(]) </sup> 06:23, 16 December 2024 (UTC)
*'''Option 2'''. Banning voluntary re-RfAs would be a step in the wrong direction on admin accountability. Same with SNOW closing. There is no more "wasting of community time" if we let the RfA run for the full seven days, but allowing someone to dig up a scandal on the seventh day is an important part of the RfA process. The only valid criticism I've heard is that folks who do this are arrogant, but banning arrogance, while noble, seems highly impractical. ] </span>]] 07:24, 16 December 2024 (UTC)
*Option 3, 1, then 2, per HouseBlaster. Also agree with Daniel Quinlan. I think these sorts of RFA's should only be done in exceptional circumstances. ] (]) 08:46, 16 December 2024 (UTC)
* '''Option 1''' as first preference, option 3 second. RFAs use up a lot of time - hundreds of editors will read the RFA and it takes time to come to a conclusion. When that conclusion is "well that was pointless, my input wasn't needed", it is not a good system. I think transparency and accountability is a very good thing, and we need more of it for resyssopings, but that should come from improving the normal process (BN) rather than using a different one (RFA). My ideas for improving the BN route to make it more transparent and better at getting community input is outlined over on the ] ] 08:59, 16 December 2024 (UTC)
* '''Option 2''', though I'd be for '''option 3''' too. I'm all for administrators who feel like they want/should go through an RfA to solicit feedback even if they've been given the tools back already. I see multiple people talk about going through BN, but if I had to hazard a guess, it's way less watched than RfA is. However I do feel like watchlist notifications should say something to the effect of "A request for re-adminship feedback is open for discussion" so that people that don't like these could ignore them. <span>♠] ]</span>♠ 09:13, 16 December 2024 (UTC)
*'''Option 2''' because ] is well-established policy. Read ], which says quite clearly, {{tpq|Regardless of the process by which the admin tools are removed, any editor is free to re-request the tools through the requests for adminship process.}} I went back 500 edits to 2017 and the wording was substantially the same back then. So, I simply do not understand why various editors are berating former administrators to the point of accusing them of wasting time and being arrogant for choosing to go through a process which is ''specifically permitted by policy''. It is bewildering to me. ] (]) 09:56, 16 December 2024 (UTC)
*'''Option 2 & 3''' I think that there still should be the choice between BN and re-RFA for resysops, but I think that the re-RFA should stay like it is in Option 3, unless it is controversial, at which point it could be extended to the full RFA period. I feel like this would be the best compromise between not "wasting" community time (which I believe is a very overstated, yet understandable, point) and ensuring that the process is based on broad consensus and that our "representatives" are still supported. If I were WTT or Hog, I might choose to make the same decision so as to be respectful of the possibility of changing consensus. ] (]) | :) | he/him | 10:45, 16 December 2024 (UTC)
*'''Option 2''', for lack of a better choice. Banning re-RFAs is not a great idea, and we should not SNOW close a discussion that would give someone immunity from a certain degree of accountability. I've dropped an idea for an option 4 in the discussion section below. ] (]) 12:08, 16 December 2024 (UTC)
*'''Option 1''' I agree with Graham87 that these sorts of RFAs should only be done in exceptional circumstances, and BN is the best place to ask for tools back. – ] <small>(])</small> 12:11, 16 December 2024 (UTC)
*'''Option 2''' I don't think prohibition makes sense. It also has weird side effects. eg: some admins' voluntary recall policies may now be completely void, because they would be unable to follow them even if they wanted to, because policy prohibits them from doing a RFA. (maybe if they're also 'under a cloud' it'd fit into exemptions, but if an admins' policy is "3 editors on this named list tell me I'm unfit, I resign" then this isn't really a cloud.) {{pb}} Personally, I think Hog Farm's RFA was unwise, as he's textbook uncontroversial. Worm's was a decent RFA; he's also textbook uncontroversial but it happened at a good time. But any editor participating in these discussions to give the "support" does so using their own time. Everyone who feels their time is wasted can choose to ignore the discussion, and instead it'll pass as 10-0-0 instead of 198-2-4. It just doesn't make sense to prohibit someone from seeking a community discussion, though. For almost anything, really. ] (]) 12:33, 16 December 2024 (UTC)
*'''Option 2''' It takes like two seconds to support or ignore an RFA you think is "useless"... can't understand the hullabaloo around them. I stand by what I said on ] regarding RFAs being about evaluating trustworthiness and accountability. Trustworthy people don't skip the process. —] <span title="Canadian!" style="color:red">🍁</span> (] · ]) 15:24, 16 December 2024 (UTC)
*'''Option 1''' - Option 2 is a waste of community time. - ] (]) 15:30, 16 December 2024 (UTC)
*:Why? ] (]) 15:35, 16 December 2024 (UTC)
*'''2''' is fine. '''Strong oppose''' to 1 and 3. Opposing option 1 because there is nothing wrong with asking for extra community feedback. opposing option 3 because once an RfA has been started, it should follow the standard rules. Note that RfAs are extremely rare and non-contentious RfAs require very little community time (unlike this RfC which seems a waste of community time, but there we are). —] (]) 16:59, 16 December 2024 (UTC)
*'''2''', with no opposition to 3. I see nothing wrong with a former administrator getting re-confirmed by the community, and community vetting seems like a good thing overall. If people think it's a waste of time, then just ignore the RfA. ] (]) 17:56, 16 December 2024 (UTC)
*'''2''' Sure, and clarify that should such an RFA be unsuccessful they may only regain through a future rfa. — ] <sup>]</sup> 18:03, 16 December 2024 (UTC)
*'''Option 2''' If contributing to such an RFA is a waste of your time, just don't participate. ] (]) 18:43, 16 December 2024 (UTC)
*:No individual is wasting their time participating. Instead the person asking for a re-rfa is ''using'' tons of editor time by asking hundreds of people to vet them. Even the choice not to participate requires at least some time to figure out that this is not a new RfA; though at least in the two we've had recently it would require only as long as it takes to get to the RfA - for many a click from the watchlist and then another click into the rfa page - and to read the first couple of sentences of the self-nomination which isn't terribly long all things considered. Best, ] (]) 22:55, 16 December 2024 (UTC)
*::I agree with you (I think) that it's a matter of perspective. For me, clicking the RFA link in my watchlist and reading the first paragraph of Hog Farm's nomination (where they explained that they were already a respected admin) took me about 10 seconds. Ten seconds is nothing; in my opinion, this is just a nonissue. But then again, I'm not an admin, checkuser, or an oversighter. Maybe the time to read such a nomination is really wasting their time. I don't know. ] (]) 23:15, 16 December 2024 (UTC)
*:::I'm an admin and an oversighter (but not a checkuser). None of my time was wasted by either WTT or Hog Farm's nominations. ] (]) 23:30, 16 December 2024 (UTC)
*'''2'''. Maintain the ''status quo''. And stop worrying about a trivial non-problem. --] (]) 22:57, 16 December 2024 (UTC)
*'''2'''. This reminds me of banning plastic straws (bear with me). Sure, I suppose in theory, that this is a burden on the community's time (just as straws do end up in landfills/the ocean). However, the amount of community time that is drained is minuscule compared to the amount of community time drained in countless, countless other fora and processes (just like the volume of plastic waste contributed by plastic straws is less than 0.001% of the total plastic waste). When WP becomes an efficient, well oiled machine, then maybe we can talk about saving community time by banning re-RFA's. But this is much ado about nothing, and indeed this plan to save people from themselves, and not allow them to simply decide whether to participate or not, is arguably more damaging than some re-RFAs (just as banning straws convinced some people that "these save-the-planet people are so ridiculous that I'm not going to bother listening to them about anything."). And, in fact, on a separate note, I'd actually love it if more admins just ran a re-RFA whenever they wanted. They would certainly get better feedback than just posting "What do my talk page watchers think?" on their own talk page. Or waiting until they get yelled at on their talk page, AN/ANI, AARV, etc. We say we want admins to respect feedback; does it '''have''' to be in a recall petition? --] (]) 23:44, 16 December 2024 (UTC)
*:What meaningful feedback has Hog Farm gotten? "A minority of people think you choose poorly in choosing this process to regain adminship". What are they supposed to do with that? I share your desire for editors to share meaningful feedback with administrators. My own attempt yielded some, though mainly offwiki where I was told I was both too cautious and too impetuous (and despite the seeming contradiction each was valuable in its own way). So yes let's find ways to get meaningful feedback to admins outside of recall or being dragged to ANI. Unfortunately re-RfA seems to be poorly suited to the task and so we can likely find a better way. Best, ] (]) 03:38, 17 December 2024 (UTC)
*:Let us all take some comfort in the fact that no one has yet criticized this RfC comment as being a straw man argument. --] (]) 23:58, 18 December 2024 (UTC)
*'''No hard rule, but we should socially discourage confirmation RfAs''' There is a difference between a hard rule, and a soft social rule. A hard rule against confirmation RfA's, like option 1, would not do a good job of accounting for edge cases and would thus be ultimately detrimental here. But a soft social rule against them would be beneficial. Unfortunately, that is not one of the options of this RfC. In short, a person should have a good reason to do a confirmation RfA. If you're going to stand up before the community and ask "do you trust me," that should be for a good reason. It shouldn't just be because you want the approval of your peers. (Let me be clear: I am not suggesting that is why either Worm or Hogfarm re-upped, I'm just trying to create a general purpose rule here.) That takes some introspection and humility to ask yourself: is it worth me inviting two or three hundred people to spend part of their lives to comment on me as a person?{{pb}}A lot of people have thrown around ] in their reasonings. Obviously, broad generalizations about it aren't convincing anyone. So let me just share my own experience. I saw the watchlist notice open that a new RfA was being run. I reacted with some excitement, because I always like seeing new admins. When I got to the page and saw Hogfarm's name, I immediately thought "isn't he already an admin?" I then assumed, ah, its just the classic RfA reaction at seeing a qualified candidate, so I'll probably support him since I already think he's an admin. But then as I started to do my due diligence and read, I saw that he really, truly, already had been an admin. At that point, my previous excitement turned to a certain unease. I had voted yes for Worm's confirmation RfA, but here was another...and I realized that my blind support for Worm might have been the start of an entirely new process. I then thought "bet there's an RfC going about this," and came here. I then spent a while polishing up my essay on editor time, before taking time to write this message. All in all, I probably spent a good hour doing this. Previously, I'd just been clicking the random article button and gnoming. So, the longwinded moral: yeah, this did eat up a lot of my editor time that could have and was being spent doing something else. And I'd do it again! It was important to do my research and to comment here. But in the future...maybe I won't react quite as excitedly to seeing that RfA notice. Maybe I'll feel a little pang of dread...wondering if its going to be a confirmation RfA. We can't pretend that confirmation RfA's are costless, and that we don't lose anything even if editors just ignore them. When run, it should be because they are necessary. ] <sup>]</sup>] 03:29, 17 December 2024 (UTC)
*:And for what its worth, support '''Option 3''' because I'm generally a fan of putting more tools in people's toolboxes. ] <sup>]</sup>] 03:36, 17 December 2024 (UTC)
*:{{tpq|In short, a person should have a good reason to do a confirmation RfA. If you're going to stand up before the community and ask "do you trust me," that should be for a good reason. It shouldn't just be because you want the approval of your peers.}} Asking the community whether you still have their trust to be an administrator, which is what an reconfirmation RFA is, ''is'' a good reason. I expect getting a near-unanimous "yes" is good for one's ego, but that's just a (nice) side-effect of the far more important benefits to the entire community: a trusted administrator.
*:The time you claim is being eaten up unnecessarily by reconfirmation RFAs was actually taken up by you choosing to spend your time writing an essay about using time for things you don't approve of and then hunting out an RFC in which you wrote another short essay about using time on things you don't approve of. Absolutely none of that is a necessary consequence of reconfirmation RFAs - indeed the response consistent with your stated goals would have been to read the first two sentences of Hog Farm's RFA and then closed the tab and returned to whatever else it was you were doing. ] (]) 09:16, 17 December 2024 (UTC)
*:WTT's and Hog Farm's RFAs would have been completely uncontentious, something I hope for at RfA and certainly the opposite of what I "dread" at RfA, if it were not for the people who attack the very concept of standing for RfA again despite policy being crystal clear that it is absolutely fine. I don't see how any blame for this situation can be put on WTT or HF. We can't pretend that dismissing uncontentious reconfirmation RfAs is costless; discouraging them removes one of the few remaining potentially wholesome bits about the process. —] (]) 09:53, 17 December 2024 (UTC)
*:@] Would you find it better if Watchlist notices and similar said "(re?)confirmation RFA" instead of "RFA"? Say for all voluntary RFAs from an existing admin or someone who could have used BN?
*:As a different point, I would be quite against any social discouraging if we're not making a hard rule as such. Social discouraging is what got us the opposes at WTT/Hog Farm's RFAs, which I found quite distasteful and badgering. If people disagree with a process, they should change it. But if the process remains the same, I think it's important to not enable RFA's toxicity by encouraging others to namecall or re-argue the process in each RRFA. It's a short road from social discouragement to toxicity, unfortunately. ] (]) 18:41, 19 December 2024 (UTC)
*::Yes I think the watchlist notice should specify what kind of RfA, especially with the introduction of recall. ] <sup>]</sup>] 16:49, 23 December 2024 (UTC)
* '''Option 1'''. Will prevent the unnecessary drama trend we are seeing in the recent. – ] (]) 07:18, 17 December 2024 (UTC)
* '''Option 2''' if people think there's a waste of community time, don't spend your time voting or discussing. Or add "reconfirmation" or similar to the watchlist notice. ] (]) 15:08, 17 December 2024 (UTC)
* '''Option 3''' (which I think is a subset of option 2, so I'm okay with the status quo, but I want to endorse giving 'crats the option to SNOW). While they do come under scrutiny from time to time for the extensive dicsussions in the "maybe" zone following RfAs, this should be taken as an indiciation that they are unlikely to do something like close it as SNOW in the event there is <em>real and substantial</em> concerns being rasied. This is an okay tool to give the 'crats. As far as I can tell, no one has ever accused the them of moving too quickly in this direction (not criticism; love you all, keep up the good work). ] (]) 17:26, 17 December 2024 (UTC)
* '''Option 3 or Option 2'''. Further, if Option 2 passes, I expect it also ends all the bickering about lost community time. A consensus explicitly in favour of "This is allowed" should also be a consensus to discourage relitigation of this RFC. ] (]) 17:35, 17 December 2024 (UTC)
*'''Option 2''': Admins who do not exude entitlement are to be praised. Those who criticize this humility should have a look in the mirror before accusing those who ask for reanointment from the community of "arrogance". I agree that it wouldn't be a bad idea to mention in parentheses that the RFA is a reconfirmation (watchlist) and wouldn't see any problem with crats snow-closing after, say, 96 hours. -- ] <sup>] · ]</sup> 18:48, 17 December 2024 (UTC)
*:I disagree that BN shouldn't be the normal route. RfA is already as hard and soul-crushing as it is. ] (]) 20:45, 17 December 2024 (UTC)
*::Who are you disagreeing with? This RfC is about voluntary RRfA. -- ] <sup>] · ]</sup> 20:59, 17 December 2024 (UTC)
*:::I know. I see a sizable amount of commenters here starting to say that voluntary re-RfAs should be encouraged, and your first sentence can be easily read as implying that admins who use the BN route exude entitlement. I disagree with that (see my reply to Thryduulf below). ] (]) 12:56, 18 December 2024 (UTC)
*::One way to improve the reputation of RFA is for there to be more RFAs that are not terrible, such as reconfirmations of admins who are doing/have done a good job who sail through with many positive comments. There is no proposal to make RFA mandatory in circumstances it currently isn't, only to reaffirm that those who voluntarily choose RFA are entitled to do so. ] (]) 21:06, 17 December 2024 (UTC)
*:::I know it's not a proposal, but there's enough people talking about this so far that it could become a proposal.<br />There's nearly nothing in between that could've lost the trust of the community. I'm sure there are many who do not want to be pressured into ] without good reason. ] (]) 12:57, 18 December 2024 (UTC)
*::::Absolutely nobody is proposing, suggesting or hinting here that reconfirmation RFAs should become mandatory - other than comments from a few people who oppose the idea of people voluntarily choosing to do something policy explicitly allows them to choose to do. The best way to avoid people being pressured into being accused of arrogance for seeking reconfirmation of their status from the community is to sanction those people who accuse people of arrogance in such circumstances as such comments are in flagrant breach of AGF and NPA. ] (]) 14:56, 18 December 2024 (UTC)
*:::::Yes, I’m saying that they should not become preferred. There should be no social pressure to do RfA instead of BN, only pressure intrinsic to the candidate. ] (]) 15:37, 18 December 2024 (UTC)
*::::::Whether they should become preferred in any situation forms no part of this proposal in any way shape or form - this seeks only to reaffirm that they are permitted. A separate suggestion, completely independent of this one, is to encourage (explicitly not mandate) them in some (but explicitly not all) situations. All discussions on this topic would benefit if people stopped misrepresenting the policies and proposals - especially when the falsehoods have been explicitly called out. ] (]) 15:49, 18 December 2024 (UTC)
*:::::::I am talking and worrying over that separate proposal many here are suggesting. I don’t intend to oppose Option 2, and sorry if I came off that way. ] (]) 16:29, 18 December 2024 (UTC)
*'''Option 2'''. In fact, I'm inclined to ''encourage'' an RRfA over BN, because nothing requires editors to participate in an RRfA, but the resulting discussion is better for reaffirming community consensus for the former admin or otherwise providing helpful feedback. --] (]) 21:45, 17 December 2024 (UTC)
*'''Option 2''' ] has said "{{tq|Former administrators may seek reinstatement of their privileges through RfA...}}" for over ten years and this is not a problem. I liked the opportunity to be consulted in the current RfA and don't consider this a waste of time. ]🐉(]) 22:14, 17 December 2024 (UTC)
*'''Option 2'''. People who think it’s not a good use of their time always have the option to scroll past. ] (]) 01:41, 18 December 2024 (UTC)
* '''2''' - If an administrator gives up sysop access because they plan to be inactive for a while and want to minimize the attack surface of Misplaced Pages, they should be able to ask for permissions back the quickest way possible. If an administrator resigns because they do not intend to do the job anymore, and later changes their mind, they should request a community discussion. The right course of action depends on the situation. ] <sup>]</sup> 14:00, 18 December 2024 (UTC)
*'''Option 1'''. I've watched a lot of RFAs and re-RFAs over the years. There's a darn good reason why the community developed the "go to BN" option: saves time, is straightforward, and if there are issues that point to a re-RFA, they're quickly surfaced. People who refuse to take the community-developed process of going to BN first are basically telling the community that they need the community's full attention on their quest to re-admin. Yes, there are those who may be directed to re-RFA by the bureaucrats, in which case, they have followed the community's carefully crafted process, and their re-RFA should be evaluated from that perspective. ] (]) 02:34, 19 December 2024 (UTC)
*'''Option 2'''. If people want to choose to go through an RFA, who are we to stop them? ] (]) 10:25, 19 December 2024 (UTC)
*'''Option 2''' (status quo/no changes) per ]. This is bureaucratic rulemongering at its finest. Every time RFA reform comes up some editors want admins to be required to periodically reconfirm, then when some admins decide to reconfirm voluntarily, suddenly that's seen as a bad thing. The correct thing to do here is nothing. If you don't like voluntary reconfirmation RFAs, you are not required to participate in them. ] (<sup>]</sup>/<sub>]</sub>) 19:34, 19 December 2024 (UTC)
*'''Option 2''' I would probably counsel just going to BN most of the time, however there are exceptions and edge cases. To this point these RfAs have been few in number, so the costs incurred are relatively minor. If the number becomes large then it might be worth revisiting, but I don't see that as likely. Some people will probably impose social costs on those who start them by opposing these RfAs, with the usual result, but that doesn't really change the overall analysis. Perhaps it would be better if our idiosyncratic internal logic didn't produce such outcomes, but that's a separate issue and frankly not really worth fighting over either. There's probably some meta issues here I'm unaware off, it's long since I've had my finger on the community pulse so to speak, but they tend to matter far less than people think they do. ] (]) 02:28, 20 December 2024 (UTC)
* '''Option 1''', per ], ], ], ], and related principles. We all have far better things to do that read through and argue in/about a totally unnecessary RfA invoked as a "Show me some love!" abuse of process and waste of community time and productivity. I could live with option 3, if option 1 doesn't fly (i.e. shut these silly things down as quickly as possible). But option 2 is just out of the question. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 04:28, 22 December 2024 (UTC)
*:Except none of the re-RFAs complained about have been {{tpq|RfA invoked as a "Show me some love!" abuse of process}}, you're arguing against a strawman. ] (]) 11:41, 22 December 2024 (UTC)
*::It's entirely a matter of opinion and perception, or A) this RfC wouldn't exist, and B) various of your fellow admins like TonyBallioni would not have come to the same conclusion I have. Whether the underlying intent (which no one can determine, lacking as we do any magical mind-reading powers) is solely egotistical is ultimately irrelevant. The {{em|actual effect}} (what matters) of doing this whether for attention, or because you've somehow confused yourself into think it needs to be done, is precisely the same: a showy waste of community volunteers' time with no result other than a bunch of attention being drawn to a particular editor and their deeds, without any actual need for the community to engage in a lengthy formal process to re-examine them. <span style="white-space:nowrap;font-family:'Trebuchet MS'"> — ] ] ] 😼 </span> 05:49, 23 December 2024 (UTC)
*:::{{tqb|or because you've somehow confused yourself into think it needs to be done}} I and many others here agree and stand behind the very reasoning that has "confused" such candidates, at least for WTT. ] (]) 15:37, 23 December 2024 (UTC)
*'''Option 2'''. I see no legitimate reason why we should be changing the status quo. Sure, some former admins might find it easier to go through BN, and it might save community time, and most former admins ''already'' choose the easier option. However, if a candidate last ran for adminship several years ago, or if issues were raised during their tenure as admin, then it may be helpful for them to ask for community feedback, anyway. There is no "wasted" community time in such a case. I really don't get the claims that this violates ], because it really doesn't apply when a former admin last ran for adminship 10 or 20 years ago or wants to know if they still have community trust.{{pb}}On the other hand, if an editor thinks a re-RFA is a waste of community time, they can simply choose not to participate in that RFA. Opposing individual candidates' re-RFAs based solely on opposition to re-RFAs in general ''is'' a violation of ]. – ] (]) 14:46, 22 December 2024 (UTC)
*:But this isn't the status quo? We've never done a re-RfA before now. The question is whether this previously unconsidered process, which appeared as an ], is a feature or a bug. ] <sup>]</sup>] 23:01, 22 December 2024 (UTC)
*::There have been lots of re-RFAs, historically. There were more common in the 2000s. ] in 2003 is the earliest I can find, back before the re-sysopping system had been worked out fully. ] back in 2007 was snow-closed after one day, because the nominator and applicant didn't know that they could have gone to the bureaucrats' noticeboard. For more modern examples, ] (2011) is relatively similar to the recent re-RFAs in the sense that the admin resigned uncontroversially but chose to re-RFA before getting the tools back. Immediately following and inspired by HJ Mitchell's, there was the slightly more controversial ]. That ended successful re-RFAS until 2019's ], which crat-chatted. Since then, there have been none that I remember. There have been several re-RFAs from admins who were de-sysopped or at serious risk of de-sysopping, and a few interesting edge cases such as the yet no-consensus ] in 2014 and the ] case in 2015, but those are very different than what we're talking about today. ] (]) 00:01, 23 December 2024 (UTC)
*:::To add on to that, ] was technically a reconfirmation RFA, which in a sense can be treated as a re-RFA. My point is, there is some precedent for re-RFAs, but the current guidelines are ambiguous as to when re-RFAs are or aren't allowed. – ] (]) 16:34, 23 December 2024 (UTC)
*::::Well thank you both, I've learned something new today. It turns out I was working on a false assumption. It has just been so long since a re-RfA that I assumed it was a truly new phenomenon, especially since there were two in short succession. I still can't say I'm thrilled by the process and think it should be used sparingly, but perhaps I was a bit over concerned. ] <sup>]</sup>] 16:47, 23 December 2024 (UTC)
*'''Option 2 or 3''' per Gnoming and CaptainEek. Such RfAs only require at most 30 seconds for one to decide whether or not to spend their time on examination. Unlike other prohibited timesinks, it's not like something undesirable will happen if one does not sink their time. Voluntary reconfirmation RfAs are socially discouraged, so there is usually a very good reason for someone to go back there, such as accountability for past statements in the case of WTT or large disputes during adminship in the case of Hog Farm. I don't think we should outright deny these, and there is no disruption incurred if we don't. ] (]) 15:44, 23 December 2024 (UTC)
*'''Option 2''' but for largely the reasons presented by CaptainEek. ''']''' (<small>aka</small> ] '''·''' ] '''·''' ]) 21:58, 23 December 2024 (UTC)
*'''Option 2 (fine with better labeling)''' These don't seem harmful to me and, if I don't have time, I'll skip one and trust the judgment of my fellow editors. No objection to better labeling them though, as discussed above. ] (]) 22:36, 23 December 2024 (UTC)
*'''Option 1''' because it's just a waste of time to go through and !vote on candidates who just want the mop restored when he or she or they could get it restored BN with no problems. But I can also see option 2 being good for a former mod not in good standing. ] (]) 23:05, 23 December 2024 (UTC)
*:If you think it is a waste of time to !vote on a candidate, just don't vote on that candidate and none of your time has been wasted. ] (]) 23:28, 23 December 2024 (UTC)
*'''Option 2''' per QoH (or me? who knows...) ] • ] • ] 04:24, 27 December 2024 (UTC)
*'''Option 2''' Just because someone may be entitled to get the bit back doesn't mean they necessarily should. Look at ]. I did not resign under a cloud, so I could have gotten the bit back by request. However, the RFA established that I did not have the community support at that point, so it was a good thing that I chose that path. I don't particularly support option 3, but I could deal with it. --] 16:05, 27 December 2024 (UTC)
*'''Option 1''' Asking hundreds of people to vet a candidate who has already passed a RfA and is eligible to get the tools back at BN is a waste of the community's time. -- ] (]) 16:21, 27 December 2024 (UTC)
*'''Option 2''' Abolishing RFA in favour of BN may need to be considered, but I am unconvinced by arguments about RFA being a waste of time. ] ] 19:21, 27 December 2024 (UTC)
*'''Option 2''' I really don't think there's a problem that needs to be fixed here. I am grateful at least a couple administrators have asked for the support of the community recently. ] ''<span style="font-size:small; vertical-align:top;">]</span>''·''<span style="font-size:small; vertical-align:bottom;">]</span>'' 00:12, 29 December 2024 (UTC)
*'''Option 2'''. Keep the status quo of {{tq|any editor is free to re-request the tools through the requests for adminship process}}. Voluntary RfA are rare enough not to be a problem, it's not as though we are overburdened with RfAs. And it’s my time to waste. --] (]) 17:58, 7 January 2025 (UTC)
* '''Option 2 or Option 3'''. These are unlikely to happen anyway, it's not like they're going to become a trend. I'm already wasting my time here instead of other more important activities anyway, so what's a little more time spent giving an easy support?{{pb
}}<span style="border-radius:9em;padding:0 7px;background:#000000">] ]</span> 16:39, 10 January 2025 (UTC)
*'''Option 1''' Agree with Daniel Quinlan that for the problematic editors eligible for re-sysop at BN despite unpopularity, we should rely on our new process of admin recall, rather than pre-emptive RRFAs. I'll add the novel argument that when goliaths like Hog Farm unnecessarily showcase their achievements at RFA, it scares off nonetheless qualified candidates. ] ( ] ) 17:39, 14 January 2025 (UTC)
:'''Option 2''' per Gnoming /CaptainEeek ] (]) 20:04, 14 January 2025 (UTC)
:While not in the lead section, the ] article mentions criticism of the Church's stance on contraception and its role in the recent spate of child abuse allegations. I think this is more a product of the comparitive depths of history of the more established religions as opposed to Scientology. ] 02:00, 17 March 2007 (UTC)
*'''Option 2''' or '''Option 3''' - if you regard a re-RfA as a waste of your time, just don't waste it by participating; it's not mandatory. ]<sup>]</sup> 12:13, 15 January 2025 (UTC)
===Discussion===
Well, if you think that Hinduism, Catholocism, and Islam are controversial - or "controversial" - in the same sense that Scientology is, I'm not sure if anyone can help you, regardless of where you post. But best of luck. ] 03:14, 9 March 2007 (UTC)
*{{re|Voorts}} If option 2 gets consensus how would this RfC change the wording {{tqq|Regardless of the process by which the admin tools are removed, any editor is free to re-request the tools through the requests for adminship process.}} Or is this an attempt to see if that option no longer has consensus? If so why wasn't alternative wording proposed? As I noted above this feels premature in multiple ways. Best, ] (]) 21:43, 15 December 2024 (UTC)
*:That is not actually true. ArbCom can (and has) forbidden some editors from re-requesting the tools through RFA. ] ] 19:21, 27 December 2024 (UTC)
*I've re-opened this per ] on my talk page. If other editors think this is premature, they can !vote accordingly and an uninvolved closer can determine if there's consensus for an early close in deference to the VPI discussion. ] (]/]) 21:53, 15 December 2024 (UTC)
*:The discussion at VPI, which I have replied on, seems to me to be different enough from this discussion that both can run concurrently. That is, however, my opinion as a mere editor. — ] ⚓ ] 22:01, 15 December 2024 (UTC)
*:@], can you please reword the RfC to make it clear that Option 2 is the current consensus version? It does not need to be clarified – it already says precisely what you propose. – ] 22:02, 15 December 2024 (UTC)
*::{{done}} ] (]/]) 22:07, 15 December 2024 (UTC)
*'''Question''': May someone clarify why many view such confirmation RfAs as a waste of community time? No editor is obligated to take up their time and participate. If there's nothing to discuss, then there's no friction or dis-cussing, and the RfA smooth-sails; if a problem is identified, then there was a good reason to go to RfA. I'm sure I'm missing something here. ] (]) 22:35, 15 December 2024 (UTC)
*: The intent of RfA is to provide a comprehensive review of a candidate for adminship, to make sure that they meet the community's standards. Is that happening with vanity re-RfAs? Absolutely not, because these people don't need that level of vetting. I wouldn't consider a week long, publicly advertized back patting to be a productive use of volunteer time. -- ] (]) 23:33, 15 December 2024 (UTC)
*::But no volunteer is obligated to pat such candidates on the back. ] (]) 00:33, 16 December 2024 (UTC)
*::: Sure, but that logic could be used to justify any time sink. We're all volunteers and nobody is forced to do anything here, but that doesn't mean that we should promote (or stay silent with our criticism of, I suppose) things that we feel don't serve a useful purpose. I don't think this is a huge deal myself, but we've got two in a short period of time and I'd prefer to do a bit of push back now before they get more common. -- ] (]) 01:52, 16 December 2024 (UTC)
*::::Unlike other prohibited timesinks, it's not like something undesirable will happen if one does not sink their time. ] (]) 02:31, 16 December 2024 (UTC)
*:::::Except someone who has no need for advanced tools and is not going to use them in any useful fashion, would then skate through with nary a word said about their unsuitability, regardless of the foregone conclusion. The point of RFA is not to rubber-stamp. Unless their is some actual issue or genuine concern they might not get their tools back, they should just re-request them at BN and stop wasting people's time with pointless non-process wonkery. ] (]) 09:05, 16 December 2024 (UTC)
*::::::I’m confused. Adminship requires continued use of the tools. If you think they’s suitable for BN, I don’t see how doing an RfA suddenly makes them unsuitable. If you have concerns, raise them. ] (]) 13:02, 16 December 2024 (UTC)
*I don't think the suggested problem (which I acknowledge not everyone thinks is a problem) is resolved by these options. Admins can still run a re-confirmation RfA after regaining adminsitrative privileges, or even initiate a recall petition. I think as ], we want to encourage former admins who are unsure if they continue to be trusted by the community at a sufficient level to explore lower cost ways of determining this. ] (]) 00:32, 16 December 2024 (UTC)
*:Regarding option 3, ]. The intent of having a reconfirmation request for administrative privileges is counteracted by closing it swiftly. It provides incentive for rapid voting that may not provide the desired considered feedback. ] (]) 17:44, 17 December 2024 (UTC)
* In re the idea that RfAs use up a lot of community time: I first started editing Misplaced Pages in 2014. There were 62 RfAs that year, which was a historic low. Even counting all of the AElect candidates as separate RfAs, including those withdrawn before voting began, we're still up to only 53 in 2024 – counting only traditional RfAs it's only 18, which is the second lowest number ever. By my count we've has 8 resysop requests at BN in 2024; even if all of those went to RfA, I don't see how that would overwhelm the community. That would still leave us on 26 traditional RfAs per year, or (assuming all of them run the full week) one every other week. ] (]) 10:26, 16 December 2024 (UTC)
* What about an option 4 encouraging eligible candidates to go through BN? At the end of the ], add something like "Eligible users are encouraged to use this method rather than running a new request for adminship." The current wording makes re-RfAing sound like a plausible alternative to a BN request, when in actual fact the former rarely happens and always generates criticism. ] (]) 12:08, 16 December 2024 (UTC)
*:Discouraging RFAs is the second last thing we should be doing (after prohibiting them), rather per my comments here and in the VPI discussion we should be ''encouraging'' former administrators to demonstrate that they still have the approval of the community. ] (]) 12:16, 16 December 2024 (UTC)
*:I think this is a good idea if people do decide to go with option 2, if only to stave off any further mixed messages that people are doing something wrong or rude or time-wasting or whatever by doing a second RfA, when it's explicitly mentioned as a valid thing for them to do. ] (]) 15:04, 16 December 2024 (UTC)
*::If RFA is explicitly a valid thing for people to do (which it is, and is being reaffirmed by the growing consensus for option 2) then we don't need to (and shouldn't) discourage people from using that option. The mixed messages can be staved off by people simply not making comments that explicitly contradict policy. ] (]) 15:30, 16 December 2024 (UTC)
*:::Also a solid option, the question is whether people will actually do it. ] (]) 22:55, 16 December 2024 (UTC)
*::::The simplest way would be to just quickly hat/remove all such comments. Pretty soon people will stop making them. ] (]) 23:20, 16 December 2024 (UTC)
* This is not new. We've had sporadic "vanity" RfAs since the early days of the process. I don't believe they're particularly harmful, and think that it unlikely that we will begin to see so many of them that they pose a problem. As such I don't think this policy proposal ]. ''']]''' 21:56, 16 December 2024 (UTC)
* This apparent negative feeling evoked at an RFA for a former sysop ''everyone agrees is fully qualified and trusted'' certainly will put a bad taste in the mouths of other former admins who might consider a reconfirmation RFA ''without first'' visiting BN. This comes in the wake of Worm That Turned's similar rerun. ] (]) 23:29, 16 December 2024 (UTC)
*:Nobody should ever be discouraged from seeking community consensus for significant changes. Adminship is a significant change. ] (]) 23:32, 16 December 2024 (UTC)
*::No argument from me. I was a big Hog Farm backer way back when he was ''merely'' one of Misplaced Pages's best content contributors. ] (]) 12:10, 17 December 2024 (UTC)
*All these mentions of editor time make me have to mention ] (TLDR: our understanding of how editor time works is dreadfully incomplete). ] <sup>]</sup>] 02:44, 17 December 2024 (UTC)
*:I went looking for @]'s comment because I know they had hung up the tools and came back, and I was interested in their perspective. But they've given me a different epiphany. I suddenly realize why people are doing confirmation RfAs: it's because of RECALL, and the one year immunity a successful RfA gives you. Maybe everyone else already figured that one out and is thinking "well duh Eek," but I guess I hadn't :) I'm not exactly sure what to do with that epiphany, besides note the emergent behavior that policy change can create. We managed to generate an entirely new process without writing a single word about it, and that's honestly impressive :P ] <sup>]</sup>] 18:18, 17 December 2024 (UTC)
*::Worm That Turned followed through on a pledge he made in January 2024, before the 2024 review of the request for adminship process began. I don't think a pattern can be extrapolated from a sample size of one (or even two). That being said, it's probably a good thing if admins occasionally take stock of whether or not they continue to hold the trust of the community. As I previously commented, it would be great if these admins would use a lower cost way of sampling the community's opinion. ] (]) 18:31, 17 December 2024 (UTC)
*:::{{ping|CaptainEek}} You are correct that a year's "immunity" results from a successful RRFA, but I see no evidence that this has been the ''reason'' for the RRFAs. Regards, ] (]) 00:14, 22 December 2024 (UTC)
*::::If people decide to go through a community vote to get a one year immunity from a process that only might lead to a community vote which would then have a lower threshold then the one they decide to go through, and also give a year's immunity, then good for them. ] (]) 01:05, 22 December 2024 (UTC)
*::@] I'm mildly bothered by this comment, mildly because I assume it's lighthearted and non-serious. But just in case anyone does feel this way - I was very clear about my reasons for RRFA, I've written a lot about it, anyone is welcome to use my personal recall process without prejudice, and just to be super clear - I waive my "1 year immunity" - if someone wants to start a petition in the next year, do not use my RRfA as a reason not to. I'll update my userpage accordingly. I can't speak for Hog Farm, but his reasoning seems similar to mine, and immunity isn't it. ]<sup>TT</sup>(]) 10:28, 23 December 2024 (UTC)
*:::@] my quickly written comment was perhaps not as clear as it could have been :) I'm sorry, I didn't mean to suggest that y'all had run for dubious reasons. As I said in my !vote, {{tq|Let me be clear: I am not suggesting that is why either Worm or Hogfarm re-upped, I'm just trying to create a general purpose rule here}}. I guess what I really meant was that the reason that we're having this somewhat spirited conversation seems to be the sense that re-RfA could provide a protection from recall. If not for recall and the one year immunity period, I doubt we'd have cared so much as to suddenly run two discussions about this. ] <sup>]</sup>] 16:59, 23 December 2024 (UTC)
*::::I don't agree. No one else has raised a concern about someone seeking a one-year respite from a recall petition. Personally, I think essentially self-initiating the recall process doesn't really fit the profile of someone who wants to avoid the recall process. (I could invent some nefarious hypothetical situation, but since opening an arbitration case is still a possibility, I don't think it would work out as planned.) ] (]) 05:19, 24 December 2024 (UTC)
*::I really don't think this is the reason behind WTT's and HF's reconfirmation RFA's. I don't think their RFA's had much utility and could have been avoided, but I don't doubt for a second that their motivations were anything other than trying to provide transparency and accountability for the community. ] ] 12:04, 23 December 2024 (UTC)
*I don't really care enough about reconf RFAs to think they should be restricted, but what about a lighter ORCP-like process (maybe even in the same place) where fewer editors can indicate, "yeah OK, there aren't really any concerns here, it would probably save a bit of time if you just asked at BN". ] (] • ]) 12:40, 19 December 2024 (UTC)
*Can someone accurately describe for me what the status quo is? I reread this RfC twice now and am having a hard time figuring out what the current state of affairs is, and how the proposed alternatives will change them. <sub>Duly signed,</sub> ''']'''-''<small>(])</small>'' 14:42, 13 January 2025 (UTC)
*:Option 2 is the status quo. The goal of the RFC is to see if the community wants to prohibit reconfirmation RFAs (option 1). The idea is that reconfirmation RFAs take up a lot more community time than a BN request so are unnecessary. There were 2 reconfirmation RFAs recently after a long dry spell. –] <small>(])</small> 20:49, 13 January 2025 (UTC)
*:The status quo, documented at ], is that admins who resigned without being under controversy can seek readminship through either BN (where it's usually given at the discreetion of an arbitrary bureaucrat according to the section I linked) or RfA (where all normal RfA procedures apply, and you see a bunch of people saying "the candidate's wasting the community's time and could've uncontroversially gotten adminship back at BN instead). ] (]) 12:27, 14 January 2025 (UTC)
{{discussion bottom}}
== Guideline against use of AI images in BLPs and medical articles? ==
:What makes Scientology controversial and the others not? ] 04:36, 9 March 2007 (UTC)
I have recently seen AI-generated images be added to illustrate both BLPs (e.g. ], now removed) and medical articles (e.g. ]). While we don't have any clear-cut policy or guideline about these yet, they appear to be problematic. Illustrating a living person with an AI-generated image might misinform as to how that person actually looks like, while using AI in medical diagrams can lead to anatomical inaccuracies (such as the lung structure in the second image, where the pleura becomes a bronnchiole twisting over the primary bronchi), or even medical misinformation. While a guideline against AI-generated images in general might be more debatable, do we at least have a consensus for a guideline against these two specific use cases?
::Scientology is labeled controversial because reputable published sources call it controversial. Misplaced Pages aims to represent all sides of the debate about any given article subject, as long as those positions are from reputable verifiable sources. If Islam and Christianity and Hinduism and Buddhism have a significant number of reputable published sources saying that they're controversial, then Wikipedians will endeavor to represent that in those articles as well. If you've got citations to that effect, please let the editors know on the appropriate article talk pages.—] 05:19, 9 March 2007 (UTC)
To clarify, I am not including potentially relevant AI-generated images that only ''happen'' to include a living person (such as in ]), but exclusively those used to illustrate a living person in a ] context. ] (] · ]) 12:11, 30 December 2024 (UTC)
:::Sorry. I didn't mean for the conversation to get hung up on one word. The point I was trying to make is that the articles about these other religions don't bring up the negative opinions in the opening section. This is only one example of the special treatment given to Scientology here on WP. ] 05:36, 9 March 2007 (UTC)
:What about any biographies, including dead people. The lead image shouldn't be AI generated for any biography. - ] (]) 12:17, 30 December 2024 (UTC)
:::: Hmm, we do have scientologists editing on wikipedia. (We also have Hindus, Christians, Jews and Muslims editing). So things should be fair enough. Try moving the criticism down the page a little if you think the sources aren't prominent enough to warrent the current location. You might get reverted of course. If so, take your time to argue your position on the associated talk page. You might be able to reach a compromise.
::Same with animals, organisms etc. - ] (]) 12:20, 30 December 2024 (UTC)
:I personally am '''strongly against''' using AI in biographies and medical articles - as you highlighted above, AI is absolutely not reliable in generating accurate imagery and may contribute to medical or general misinformation. I would 100% support a proposal banning AI imagery from these kinds of articles - and a recommendation to not use such imagery other than in specific scenarios. ]] 12:28, 30 December 2024 (UTC)
:I'd prefer a guideline prohibiting the use of AI images full stop. There are too many potential issues with accuracy, honesty, copyright, etc. Has this already been proposed or discussed somewhere? – ] <small>(])</small> 12:38, 30 December 2024 (UTC)
::There hasn't been a full discussion yet, and we have a list of uses at ], but it could be good to deal with clear-cut cases like this (which are already a problem) first, as the wider discussion is less certain to reach the same level of consensus. ] (] · ]) 12:44, 30 December 2024 (UTC)
:Discussions are going on at ] and somewhat at ]. I recommend workshopping an RfC question (or questions) then starting an RfC. ] (]) 13:03, 30 December 2024 (UTC)
::Oh, didn't catch the previous discussions! I'll take a look at them, thanks! ] (] · ]) 14:45, 30 December 2024 (UTC)
:There is one very specific exception I would put to a very sensible blanket prohibition on using AI images to illustrate people, especially BLPs. That is where the person themselves is known to use that image, which I have encountered in ]. ] (]) 15:00, 30 December 2024 (UTC)
::While the Ekpa portrait is just an upscale (and I'm not sure what positive value that has for us over its source; upscaling does not add accuracy, nor is it an artistic interpretation meant to reveal something about the source), this would be hard to translate to the general case. Many AI portraits would have copyright concerns, not just from the individual (who may have announced some appropriate release for it), but due to the fact that AI portraits can lean heavily on uncredited individual sources. --] (]) 16:04, 30 December 2024 (UTC)
:::For the purposes of discussing whether to allow AI images at all, we should always assume that, for the purposes of (potential) policies and guidelines, there exist AI images we can legally use to illustrate every topic. We cannot use those that are not legal (including, but not limited to, copyright violations) so they are irrelevant. An image generator trained exclusively on public domain and cc0 images (and any other licenses that explicitly allow derivative works without requiring attribution) would not be subject to any copyright restrictions (other than possibly by the prompter and/or generator's license terms, which are both easy to determine). Similarly we should not base policy on the current state of the technology, but assume that the quality of its output will improve to the point it is equal to that of a skilled human artist. ] (]) 17:45, 30 December 2024 (UTC)
::::The issue is, either there are public domain/CC0 images of the person (in which case they can be used directly) or there aren't, in which case the AI is making up how a person looks. ] (] · ]) 20:00, 30 December 2024 (UTC)
::::We tend to use art representations either where no photographs are available (in which case, AI will also not have access to photographs) or where what we are showing is an artist's insight on how this person is perceived, which is not something that AI can give us. In any case, we don't have to build policy now around some theoretical AI in the future; we can deal with the current reality, and policy can be adjusted if things change in the future. And even that theoretical AI does make it more difficult to detect copyvio -- ] (]) 20:54, 30 December 2024 (UTC)
:::I wouldn't call it an upscale given whatever was done appears to have removed detail, but we use that image as it was specifically it is the edited image which was sent to VRT. ] (]) 10:15, 31 December 2024 (UTC)
:Is there any clarification on using purely AI-generated images vs. using AI to edit or alter images? AI tools , such as to identify objects and remove them, or generate missing content. The generative expand feature would appear to be unreliable (and it is), but I use it to fill in gaps of cloudless sky produced from stitching together photos for a panorama (I don't use it if there are clouds, or for starry skies, as it produces non-existent stars or unrealistic clouds). ] (]) 18:18, 30 December 2024 (UTC)
::Yes, my proposal is only about AI-generated images, not AI-altered ones. That could in fact be a useful distinction to make if we want to workshop a RfC on the matter. ] (] · ]) 20:04, 30 December 2024 (UTC)
:I'm not sure if we need a clear cut policy or guideline against them... I think we treat them the same way as we would treat an editor's kitchen table sketch of the same figure. ] (]) 18:40, 30 December 2024 (UTC)
:For those wanting to ban AI images full stop, well, you are too late. Most professional image editing software, including the software in one's smartphone as well as desktop, uses AI somewhere. Noise reduction software uses AI to figure out what might be noise and what might be texture. Sharpening software uses AI to figure out what should be smooth and what might have a sharp detail it can invent. For example, a bird photo not sharp enough to capture feather detail will have feather texture imagined onto it. Same for hair. Or grass. Any image that has been cleaned up to remove litter or dust or spots will have the cleaned area AI generated based on its surroundings. The sky might be extended with AI. These examples are a bit different from a 100% imagined image created from a prompt. But probably not in a way that is useful as a rule.
:I think we should treat AI generated images the same as any user-generated image. It might be a great diagram or it might be terrible. Remove it from the article if the latter, not because someone used AI. If the image claims to photographically represent something, we may judge whether the creator has manipulated the image too much to be acceptable. For example, using AI to remove a person in the background of an image taken of the BLP subject might be perfectly fine. People did that with traditional Photoshop/Lightroom techniques for years. Using AI to generate what claims to be a photo of a notable person is on dodgy ground wrt copyright. -- ]°] 19:12, 30 December 2024 (UTC)
::I'm talking about the case of using AI to generate a depiction of a living person, not using AI to alter details in the background. That is why I only talk about AI-generated images, not AI-altered images. ] (] · ]) 20:03, 30 December 2024 (UTC)
:Regarding some sort of brightline ban on the use of any such image in anything article medical related: absolutely not. For example, if someone wanted to use AI tools as opposed to other tools to make an image such as ] (as used in the "medical" article ]) I don't see a problem, so long as it is accurate. Accurate models and illustrations are useful and that someone used AI assistance as opposed to a chisel and a rock is of no concern. — ] <sup>]</sup> 19:26, 30 December 2024 (UTC)
:I believe that the appropriateness of AI images depends on how its used by the user. In BLP and medical articles, it is inappropriate for the images, but it is inappropriate to ban it completely across thw site. By the same logic, if you want full ban of AI, you are banning fire just because people can get burned, without considering cooking. ] (]) 13:33, 31 December 2024 (UTC)
] <sup>]</sup> 00:13, 31 December 2024 (UTC)]]
:I agree that AI-generated images should not be used in most cases. They essentially serve as misinformation. I also don't think that they're really comparable to drawings or sketches because AI-generation uses a level of photorealism that can easily trick the untrained eye into thinking it is real. ] (]) 20:46, 30 December 2024 (UTC)
::AI doesn't need to be photorealistic though. I see two potential issues with AI. The first is images that might deceive the viewer into thinking they are photos, when they are not. The second is potential copyright issues. Outside of the copyright issues I don't see any unique concerns for an AI-generated image (that doesn't appear photorealistic). Any accuracy issues can be handled the same way a user who manually drew an image could be handled. ] (]) 21:46, 30 December 2024 (UTC)
{{multiple image
| image1 = Pope Francis in puffy winter jacket.jpg
| image2 = Illustration of Brigette Lundy Paine by Sandra Mu.png
| footer = ] and ]
| total_width = 300
}}
::AI-generated depictions of BLP subjects are often more "illustrative" than drawings/sketches of BLP subjects made by 'regular' editors like you and me. For example, compare the AI-generated image of Pope Francis and the user-created cartoon of Brigette Lundy-Paine. Neither image belongs on their respective bios, of course, but the AI-generated image is no more "misinformation" than the drawing. ] (]) 00:05, 31 December 2024 (UTC)
:::I would argue the opposite: neither are made up, but the first one, because of its realism, might mislead readers into thinking that it is an actual photograph, while the second one is clearly a drawing. Which makes the first one less illustrative, as it carries potential for misinformation, despite being technically more detailed. ] (] · ]) 00:31, 31 December 2024 (UTC)
::::AI-generated images should always say "AI-generated image of " in the image caption. No misleading readers that way. ] (]) 00:36, 31 December 2024 (UTC)
:::::Yes, and they don't always do it, and we don't have a guideline about this either. The issue is, many people have many different proposals on how to deal with AI content, meaning we always end up with "no consensus" and no guidelines on use at all, even if most people are against it. ] (] · ]) 00:40, 31 December 2024 (UTC)
::::::{{tq|always end up with "no consensus" and no guidelines on use at all, even if most people are against it}} Agreed. Even a simple proposal to have image captions note whether an image is AI-generated will have editors wikilawyer over the definition of 'AI-generated.' I take back my recommendation of starting an RfC; we can already predict how that RfC will end. ] (]) 02:28, 31 December 2024 (UTC)
:Of interest perhaps is ] on the use of drawn cartoon images in BLPs. ] (]) 22:38, 30 December 2024 (UTC)
:We should absolutely not be including any AI images in anything that is meant to convey facts (with the obvious exception of an AI image illustrating the concept of an AI image). I also don't think we should be encouraging AI-altered images -- the line between "regular" photo enhancement and what we'd call "AI alteration" is blurry, but we shouldn't want AI edits for the same reason we wouldn't want fake Photoshop composites.
:That said, I would assume good faith here: some of these images are probably being sourced from Commons, and Commons is dealing with a lot of undisclosed AI images. ] (]) 23:31, 30 December 2024 (UTC)
::]
::Why wouldn't we want "fake Photoshop composites"? A ] can be very useful. I'd be sad if we banned ]. ] (]) 06:40, 31 December 2024 (UTC)
:::Sorry, should have been more clear -- composites that present themselves as the real thing, basically what people would use deepfakes for now. ] (]) 20:20, 31 December 2024 (UTC)
::::Yeah I think there is a very clear line between images built by a diffusion model and images modified using photoshop through techniques like compositing. That line is that the diffusion model is reverse-engineering an image to match a text prompt from a pattern of semi-random static associated with similar text prompts. As such it's just automated glurge, at best it's only as good as the ability of the software to parse a text prompt and the ability of a prompter to draft sufficiently specific language. And absolutely none of that does anything to solve the "hallucination" problem. On the other hand, in photoshop, if I put in two layers both containing a bird on a transparent background, what I, the human making the image, sees is what the software outputs. ] (]) 18:03, 15 January 2025 (UTC)
:::::{{tpq|Yeah I think there is a very clear line between images built by a diffusion model and images modified using photoshop}} others do not. If you want to ban or restrict one but not the other then you need to explain how the difference can be reliably determined, and how one is materially different to the other in ways other than your personal opinion. ] (]) 18:45, 15 January 2025 (UTC)
:I don't think any guideline, let alone policy, would be beneficial and indeed on balance is more likely to be harmful. There are always only two questions that matter when determining whether we should use an image, and both are completely independent of whether the image is AI-generated or not:
:#Can we use this image in this article? This depends on matters like copyright, fair use, whether the image depicts content that is legal for an organisation based in the United States to host, etc. Obviously if the answer is "no", then everything else is irrelevant, but as the law and WMF, Commons and en.wp policies stand today there exist some images in both categories we can use, and some images in both categories we cannot use.
:#Does using this image in this article improve the article? This is relative to other options, one of which is always not using any image, but in many cases also involves considering alternative images that we can use. In the case of depictions of specific, non-hypothetical people or objects one criteria we use to judge whether the image improves the article is whether it is an accurate representation of the subject. If it is not an accurate representation then it doesn't improve the article and thus should not be used, regardless of why it is inaccurate. If it is an accurate representation, then its use in the article will not be misrepresentative or misleading, regardless of whether it is or is not AI generated. It may or may not be the best option available, but if it is then it should be used regardless of whether it is or is not AI generated.
:The potential harm I mentioned above is twofold, firstly Misplaced Pages is, by definition, harmed when an images exists we could use that would improve an article but we do not use it in that article. A policy or guideline against the use of AI images would, in some cases, prevent us from using an image that would improve an article. The second aspect is misidentification of an image as AI-generated when it isn't, especially when it leads to an image not being used when it otherwise would have been.
:Finally, all the proponents of a policy or guideline are assuming that the line between images that are and are not AI-generated is sharp and objective. Other commenters here have already shown that in reality the line is blurry and it is only going to get blurrier in the future as more AI (and AI-based) technology is built into software and especially firmware. ] (]) 00:52, 31 December 2024 (UTC)
::I agree with almost the entirety of your post with a caveat on whether something "is an accurate representation". We can tell whether non-photorealistic images are accurate by assessing whether the image accurately conveys ''the idea'' of what it is depicting. Photos do more than convey an idea, they convey the actual look of something. With AI generated images that are photorealistic it is difficult to assess whether they accurately convey the look of something (the shading might be illogical in subtle ways, there could be an extra finger that goes unnoticed, a mole gets erased), but readers might be deceived by the photo-like presentation into thinking they are looking at an actual photographic depiction of the subject which could differ significantly from the actual subject in ways that go unnoticed. ] (]) 04:34, 31 December 2024 (UTC)
::{{tq|A policy or guideline against the use of AI images would, in some cases, prevent us from using an image that would improve an article.}} That's why I'm suggesting a guideline, not a policy. Guidelines are by design more flexible, and ] still does (and should) apply in edge cases.{{pb}}{{tq|The second aspect is misidentification of an image as AI-generated when it isn't, especially when it leads to an image not being used when it otherwise would have been.}} In that case, there is a licensing problem. AI-generated images on Commons are supposed to be clearly labeled as such. There is no guesswork here, and we shouldn't go hunting for images that ''might'' have been AI-generated.{{pb}}{{tq|Finally, all the proponents of a policy or guideline are assuming that the line between images that are and are not AI-generated is sharp and objective. Other commenters here have already shown that in reality the line is blurry and it is only going to get blurrier in the future as more AI (and AI-based) technology is built into software and especially firmware.}} In that case, it's mostly because the ambiguity in wording: AI-edited images are very common, and are sometimes called "AI-generated", but here we should focus on actual prompt outputs, of the style "I asked a model to generate me an image of a BLP". ] (] · ]) 11:13, 31 December 2024 (UTC)
:::Simply not having a completely unnecessary policy or guideline is infinitely better than relying on IAR - especially as this would have to be ignored ''every'' time it is relevant. When the AI image is not the best option (which obviously includes all the times its unsuitable or inaccurate) existing policies, guidelines, practice and frankly common sense mean it won't be used. This means the only time the guideline would be relevant is when an AI image ''is'' the best option and as we obviously should be using the best option in all cases we would need to ignore the guideline against using AI images.
:::{{tpq|AI-generated images on Commons are supposed to be clearly labeled as such. There is no guesswork here, and we shouldn't go hunting for images that might have been AI-generated.}} The key words here are "supposed to be" and "shouldn't", editors absolutely ''will'' speculate that images are AI-generated and that the Commons labelling is incorrect. We are supposed to assume good faith, but this very discussion shows that when it comes to AI some editors simply do not do that.
:::Regarding your final point, that might be what you are meaning but it is not what all other commenters mean when they want to exclude all AI images. ] (]) 11:43, 31 December 2024 (UTC)
::::For your first point, the guideline is mostly to take care of the "prompt fed in model" BLP illustrations, where it is technically hard to prove that the person doesn't look like that (as we have no available image), but the model likely doesn't have any available image either and most likely just made it up. As my proposal is essentially limited to that (I don't include AI-edited images, only those that are purely generated by a model), I don't think there will be many cases where IAR would be needed.{{pb}}Regarding your two other points, you are entirely correct, and while I am hoping for nuance on the AI issue, it is clear that some editors might not do that. For the record, I strongly disagree with a blanket ban of "AI images" (which includes both blatant "prompt in model" creations and a wide range of more subtle AI retouching tools) or anything like that. ] (] · ]) 11:49, 31 December 2024 (UTC)
:::::{{tpq|the guideline is mostly to take care of the "prompt fed in model" BLP illustrations, where it is technically hard to prove that the person doesn't look like that (as we have no available image)}}. There are only two possible scenarios regarding verifiability:
:::::#The image is an accurate representation and we can verify that (e.g. by reference to non-free photos).
:::::#*Verifiability is no barrier to using the image, whether it is AI generated or not.
:::::#*If it is the best image available, and editors agree using it is better than not having an image, then it should be used whether it is AI generated or not.
:::::#The image is either ''not'' an accurate representation, or we cannot verify whether it is or is not an accurate representation
:::::#*The only reasons we should ever use the image are:
:::::#**It has been the subject of notable commentary and we are presenting it in that context.
:::::#**The subject verifiably uses it as a representation of themselves (e.g. as an avatar or logo)
:::::#:This is already policy, whether the image is AI generated or not is completely irrelevant.
:::::You will note that in no circumstance is it relevant whether the image is AI generated or not. ] (]) 13:27, 31 December 2024 (UTC)
::::::In your first scenario, there is the issue of an accurate AI-generated image misleading people into thinking it is an actual photograph of the person, especially as they are most often photorealistic. Even besides that, a mostly accurate representation can still introduce spurious details, and this can mislead readers as they do not know to what level it is actually accurate. This scenario doesn't really happen with drawings (which are clearly not photographs), and is very much a consequence of AI-generated photorealistic pictures being a thing.{{pb}}In the second scenario, if we cannot verify that it is not an accurate representation, it can be hard to remove the image with policy-based reasons, which is why a guideline will again be helpful. Having a single guideline against fully AI-generated images takes care of all of these scenarios, instead of having to make new specific guidelines for each case that emerges because of them. ] (] · ]) 13:52, 31 December 2024 (UTC)
:::::::If the image is misleading or unverifiable it should not be used, regardless of why it is misleading or unverifiable. This is existing policy and we don't need anything specifically regarding AI to apply it - we just need consensus that the image ''is'' misleading or unverifiable. Whether it is or is not AI generated is completely irrelevant. ] (]) 15:04, 31 December 2024 (UTC)
::::{{tpq|AI-generated images on Commons are supposed to be clearly labeled as such. There is no guesswork here, and we shouldn't go hunting for images that might have been AI-generated.}}
::::I mean... yes, we should? At the very least Commons should go hunting for mislabeled images -- that's the whole point of license review. The thing is that things are absolutely swamped over there and there are hundreds of thousands of images waiting for review of some kind. ] (]) 20:35, 31 December 2024 (UTC)
:::::Yes, but that's a Commons thing. A guideline on English Misplaced Pages shouldn't decide of what is to be done on Commons. ] (] · ]) 20:37, 31 December 2024 (UTC)
::::::I just mean that given the reality of the backlogs, there are going to be mislabeled images, and there are almost certainly going to be more of them over time. That's just how it is. We don't have control over that, but we do have control over what images go into articles, and if someone has legitimate concerns about an image being AI-generated, then they should be raising those. ] (]) 20:45, 31 December 2024 (UTC)
*'''Support blanket ban on AI-generated images on Misplaced Pages'''. As others have highlighted above, the is not just a slippery slope but an outright downward spiral. We don't use AI-generated text and we shouldn't use AI-generated images: these aren't reliable and they're also ] scraped from who knows what and where. '''Use only reliable material from reliable sources'''. As for the argument of 'software now has AI features', we all know that there's a huge difference between someone using a smoothing feature and someone generating an image from a prompt. ] (]) 03:12, 31 December 2024 (UTC)
*:'''Reply''', the section of ] concerning images is ] which states "Original images created by a Wikimedian are not considered original research, ''so long as they do not illustrate or introduce unpublished ideas or arguments''". Using AI to generate an image only violates ] if you are using it to illustrate unpublished ideas, which can be assessed just by looking at the image itself. COPYVIO, however, cannot be assessed from looking at just the image alone, which AI could be violating. However, some images may be too simple to be copyrightable, for example AI-generated images of chemicals or mathematical structures potentially. ] (]) 04:34, 31 December 2024 (UTC)
*::Prompt generated images are unquestionably violation of ] and ]: Type in your description and you get an image scraping who knows what and from who knows where, often Misplaced Pages. Misplaced Pages isn't an ]. Get real. ] (]) 23:35, 1 January 2025 (UTC)
*:::"Unquestionably"? Let me question that, @]. <code>;-)</code>
*:::If an editor were to use an AI-based image-generating service and the prompt is something like this:
*:::"I want a stacked bar chart that shows the number of games won and lost by ] each year. Use the team colors, which are red #DC052D, blue #0066B2, and black #000000. The data is:
*:::* 2014–15: played 34 games, won 25, tied 4, lost 5
*:::* 2015–16: played 34 games, won 28, tied 4, lost 2
*:::* 2016–17: played 34 games, won 25, tied 7, lost 2
*:::* 2017–18: played 34 games, won 27, tied 3, lost 4
*:::* 2018–19: played 34 games, won 24, tied 6, lost 4
*:::* 2019–20: played 34 games, won 26, tied 4, lost 4
*:::* 2020–21: played 34 games, won 24, tied 6, lost 4
*:::* 2021–22: played 34 games, won 24, tied 5, lost 5
*:::* 2022–23: played 34 games, won 21, tied 8, lost 5
*:::* 2023–24: played 34 games, won 23, tied 3, lost 8"
*:::I would expect it to produce something that is not a violation of either OR in general or OR's SYNTH section specifically. What would you expect, and why do you think it would be okay for me to put that data into a spreadsheet and upload a screenshot of the resulting bar chart, but you don't think it would be okay for me to put that same data into a image generator, get the same thing, and upload that?
*:::We must not mistake the tools for the output. Hand-crafted bad output is bad. AI-generated good output is good. ] (]) 01:58, 2 January 2025 (UTC)
*::::Assuming you'd even get what you requested the model without fiddling with the prompt for a while, these sort of 'but we can use it for graphs and charts' devil's advocate scenarios aren't helpful. We're discussing generating images of people, places, and objects here and in those cases, yes, this would unquestionably be a form of ] & ]. As for the charts and graphs, there are any number of ways to produce these. ] (]) 03:07, 2 January 2025 (UTC)
*:::::{{tpq|We're discussing generating images of people, places, and objects here}} The proposal contains no such limitation. {{tpq| and in those cases, yes, this would unquestionably be a form of WP:OR & WP:SYNTH.}} Do you have a citation for that? Other people have explained better than I can how that it is not necessarily true, and certainly not unquestionable. ] (]) 03:14, 2 January 2025 (UTC)
*::::::As you're well aware, these images are produced by scraping and synthesized material from who knows what and where: it's ultimately pure ] to produce these fake images and they're a straightforward product of synthesis of multiple sources (]) - worse yet, these sources are unknown because training data is by no means transparent. Personally, I'm strongly for a total ban on generative AI on the site exterior to articles on the topic of generative AI. Not only do I find this incredible unethical, I believe it is intensely detrimental to Misplaced Pages, which is an already a flailing and shrinking project. ] (]) 03:23, 2 January 2025 (UTC)
*:::::::So you think the lead image at ] is a SYNTH violation? Its (human) creator explicitly says "This is not done from one specific photo. As I usually do when I draw portraits of people that I can't see in person, I look at a lot of photos of them and then create my own rendition" in the image description, which sounds like the product of synthesis of multiple sources" to me, and "these sources are unknown because" the the images the artist looked at are not disclosed.
*:::::::A lot of my concern about blanket statements is the principle that what's ] is sauce for the gander, too. If it's okay for a human to do something by hand, then it should be okay for a human using a semi-automated tool to do it, too.
*:::::::<small>(Just in case you hadn't heard, the rumors that the editor base is shrinking have been false for over a decade now. Compared to when you created your account in mid-2005, we have about twice as many high-volume editors.)</small> ] (]) 06:47, 2 January 2025 (UTC)
*:::::::Review ] and your attempts at downplaying a prompt-generated image as "semi-automated" shows the root of the problem: if you can't detect the difference between a human sketching from a reference and a machine scraping who-knows-what on the internet, you shouldn't be involved in this discussion. As for editor retention, this remains a serious problem on the site: while the site continues to grow (and becomes core fodder for AI-scraping) and becomes increasingly visible, editorial retention continues to drop. ] (]) 09:33, 2 January 2025 (UTC)
*::::::::Please scroll down below SYNTH to the next section titled "What is not original research" which begins with ], our policies on how images relate to OR. OR (including SYNTH) only applies to images with regards to if they illustrate "unpublished ideas or arguments". It does not matter, for instance, if you synthesize an original ''depiction'' of something, so long as the ''idea'' of that thing is not original. ] (]) 09:55, 2 January 2025 (UTC)
*:::::::::Yes, which explicitly states:
*::::::::::It is not acceptable for an editor to use photo manipulation to distort the facts or position illustrated by an image. Manipulated images should be prominently noted as such. Any manipulated image where the encyclopedic value is materially affected should be posted to Misplaced Pages:Files for discussion. Images of living persons must not present the subject in a false or disparaging light.
*:::::::::Using a machine to generate a fake image of someone is far beyond "manipulation" and it is certainly "false". Clearly we need explicit policies on AI-generated images of people or we wouldn't be having this discussion, but this as it stands clarly also falls under ]: there is zero question that this is a result of "synthesis of published material", even if the AI won't list what it used. Ultimately it's just a synthesis of a bunch of published composite images of who-knows-what (or who-knows-who?) the AI has scraped together to produce a fake image of a person. ] (]) 10:07, 2 January 2025 (UTC)
*:The latter images you describe should be SVG regardless. If there are models that can generate that, that seems totally fine since it can be semantically altered by hand. Any generation with photographic or "painterly" characteristics (e.g. generating something in the style of a painting or any other convention of visual art that communicates aesthetic particulars and not merely abstract visual particulars) seems totally unacceptable. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 07:00, 31 December 2024 (UTC)
*:]
*:@], here's an image I created. It illustrates the concept of 1% in an article. I made this myself, by typing 100 emojis and taking a screenshot. Do you really mean to say that if I'd done this with an image-generating AI tool, using a prompt like "Give me 100 dots in a 10 by 10 grid. Make 99 a dark color and 1, randomly placed, look like a baseball" that it would be hopelessly tainted, because AI is always bad? Or does your strongly worded statement mean something more moderate?
*:I'd worry about photos of people (including dead people). I'd worry about photos of specific or unique objects that have to be accurate or they're worse than worthless (e.g., artwork, landmarks, maps). But I'm not worried about simple graphs and charts like this one, and I'm not worried about ordinary, everyday objects. If you want to use AI to generate a photorealistic image of a cookie, or a spoon, and the output you get ], I'm not actually going to worry about it. ] (]) 06:57, 31 December 2024 (UTC)
*::As you know, Misplaced Pages has the unique factor of being entirely volunteer-ran. Misplaced Pages has fewer and fewer editors and, long-term, we're seeing plummeting birth rates in areas where most Misplaced Pages editors do exist. I wouldn't expect a wave of new ones aimed at keeping the site free of bullshit in the near future.
*::In addition, the Wikimedia Foundation's hair-brained continued effort to turn the site into its political cash machine is no doubt also not helping, harming the site's public perception and leading to fewer new editors.
*::Over the course of decades (I've been here for around 20 years), it seems clear that the site will be negatively impacted by all this, especially in the face of generative AI.
*::As a long-time editor who has frequently stumbled upon intense ] content, fended off armies of outside actors looking to shape the site into their ideological image (and sent me more than a few death threats), and who has identified large amount of politically-motivated nonsense explicitly designed to fool non-experts in areas I know intimately well (such as folklore and historical linguistics topics), I think it need be said that the use of generative AI for content is especially dangerous because of its capabilities of fooling Misplaced Pages readers and Misplaced Pages editors alike.
*::Misplaced Pages is written by people for people. We need to draw a line in the sand to keep from being flooded by increasingly accessible hoax-machines.
*::A blanket ban on generative AI resolves this issue or at least hands us another tool with which to attempt to fight back. We don't need what few editors we have here wasting what little time they can give the project checking over an ocean of AI-generated slop: '''we need more material from reliable sources and better tools to fend off bad actors usable by our shrinking editor base (anyone at the Wikimedia Foundation listening?), not more waves of generative AI garbage'''. ] (]) 07:40, 31 December 2024 (UTC)
*:::A blanket ban doesn't actually resolve most of the issues though, and introduces new ones. Bad usages of AI can already be dealt with by existing policy, and malicious users will ignore a blanket ban anyways. Meanwhile, a blanket ban would harm many legitimate usages for AI. For instance, the majority of professional translators (at least Japanese to English) incorporate AI (or similar tools) into their workflow to speed up translations. Just imagine a professional translator who uses AI to help generate rough drafts of foreign language Misplaced Pages articles, before reviewing and correcting them, and another editor learning of this and mass reverting them for breaking the blanket ban, and ultimately causing them to leave. Many authors (particularly with carpal tunnel) use AI now to control their voice-to-text (you can train the AI on how you want character names spelled, the formatting of dialogue and other text, etc.). A wikipedia editor could train an AI to convert their voice into Misplaced Pages-formatted text. AI is subtly incorporated now into spell-checkers, grammar-checkers, photo editors, etc., in ways many people are not aware of. A blanket AI ban has the potential to cause many issues for a lot of people, without actually being that affective at dealing with malicious users. ] (]) 08:26, 31 December 2024 (UTC)
*::::I think this is the least convincing one I've seen here yet: It contains the ol' 'there are AI features in programs now' while also attempting to invoke accessibility and a little bit of 'we must have machines to translate!'.
*::::As a translator myself, I can only say: ''Oh please''. Generative AI is notoriously terrible at translating and that's not likely to change. And I mean ''ever'' beyond a very, very basic level. Due to the complexities of communication and little matters like nuance, all machine translated material must be thoroughly checked and modified by, yes, ''human'' translators, who often encounter it spitting out complete bullshit scraped from who-knows-where (often Misplaced Pages itself).
*::::I get that this topic attracts a lot of 'but what if generative AI is better than humans?' from the utopian tech crowd but the ''reality'' is that anyone who needs a machine to invent text and visuals for whatever reason simply shouldn't be using it on Misplaced Pages.
*::::Either you, a human being, can contribute to the project or ''you can't''. Slapping a bunch of machine-generated (generative AI) visuals and text (much of it ultimately coming from Misplaced Pages in the first place!) isn't some kind of human substitute, it's just machine-regurgitated slop and is not helping the project.
*::::If people can't be confident that Misplaced Pages is ''made by humans, for humans'' the project is finally on its way out.] (]) 09:55, 31 December 2024 (UTC)
*:::::I don't know how up to date you are on the current state of translation, but:
*::::::''''
*::::::''Over three thousand full-time professional translators from around the world responded to the surveys, which were broken into a survey for CAT tool users and one for those who do not use any CAT tool at all.''
*::::::''88% of respondents use at least one CAT tool for at least some of their translation tasks.''
*::::::''Of those using CAT tools, 83% use a CAT tool for most or all of their translation work.''
*:::::Mind you, traditionally CAT tools didn't use AI, but many do now, which only adds to potential sources of confusion in a blanket ban of AI. ] (]) 17:26, 31 December 2024 (UTC)
*::::::You're barking up the tree with the pro-generative AI propaganda in response to me. I think we're all quite aware that generative AI tool integration is now common and that there's also a big effort to replace human translators — and anything that can be "written" with machines-generated text. I'm also keenly aware that generative AI is ''absolutely horrible'' at translation and ''all of it must be thoroughly checked by humans'', as you would be if you were a translator yourself. ] (]) 22:20, 31 December 2024 (UTC)
*:::::"''all machine translated material must be thoroughly checked and modified by, yes, ''human'' translators''"
*:::::You are just agreeing with me here.
*::::::'''' -American Translation Society
*:::::There are translators (particularly with non-creative works) who are using these tools to shift more towards reviewing. It should be up to them to decide what they think is the most efficient method for them. ] (]) 06:48, 1 January 2025 (UTC)
*::::::And any translator who wants to use generative AI to ''attempt'' to translate can do so off the site. We're not here to check it for them. I strongly support a total ban on any generative AI used on the site exterior to articles on generative AI. ] (]) 11:09, 1 January 2025 (UTC)
*:::::::I wonder what you mean by "on the site". The question here is "Is it okay for an editor to go to a completely different website, generate an image all by themselves, upload it to Commons, and put it in a Misplaced Pages article?" The question here is ''not'' "Shall we put AI-generating buttons on Misplaced Pages's own website?" ] (]) 02:27, 2 January 2025 (UTC)
*:::::::I'm talking about users slapping machine-translated and/or machine-generated nonsense all over the site, only for us to have to go behind and not only check it but correct it. It takes users minutes to do this and it's already happening. It's the same for images. There are very few of us who volunteer here and our numbers are growing fewer. We need to be spending our time improving the site rather than opening the gate as wide as possible for a flood of AI-generated/rendered garbage. The site has enough problems that compound every day rather than having to fend off users armed with hoax machines at every corner. ] (]) 03:20, 2 January 2025 (UTC)
*::::::::Sure, we're all opposed to "nonsense", but my question is: What about when the machine happens to generate something that is ''not'' "nonsense"?
*::::::::I have some worries about AI content. I worry, for example, that they'll corrupt our sources. I worry that ] will get dramatically longer, and also that even more undetected, unconfessed, unretracted papers will get published and believed to be true and trustworthy. I worry that academia will go back to a model in which personal connections are more important, because you really can't trust what's published. I worry that scientific journals will start refusing to publish research unless it comes from someone employed by a trusted institution, that is willing to put its reputation on the line by saying they have directly verified that the work described in the paper was actually performed to their standards, thus scuttling the citizen science movement and excluding people whose institutions are upset with them for other reasons (Oh, you thought you'd take a job elsewhere? Well, we refuse to certify the work you did for the last three years...).
*::::::::But I'm not worried about a Misplaced Pages editor saying "Hey AI, give me a diagram of swingset" or "Make a chart for me out of the data I'm going to give you". In fact, if someone wants to pull the numbers out of ], feed it to an AI, and replace the template's contents with an AI-generated image (until they finally fix the Graphs extension), I'd consider that helpful. ] (]) 07:09, 2 January 2025 (UTC)
*::::::Translators are not using ''generative'' AI for translation, the applicability of LLMs to regular translation is still in its infancy and regardless will not be implementing any ''generative'' faculties to its output since that is the exact opposite of what translation is supposed to do. ] (]) 02:57, 2 January 2025 (UTC)
*:::::::{{tpq|Translators are not using generative AI for translation}} this entirely depends on what you mean by "generative". There are at least three contradictory understandings of the term in this one thread alone. ] (]) 03:06, 2 January 2025 (UTC)
*:::::::Please, you can just go through the entire process with a simple prompt command now. The results are typically shit but you can generate a ton of it quickly, which is perfect for flooding a site like this one — especially without a strong policy against it. I've found myself cleaning up tons of AI-generated crap (and, yes, rendered) stuff here and elsewhere, and now I'm even seeing AI-generated responses to my own comments. It's beyond ridiculous. ] (]) 03:20, 2 January 2025 (UTC)
* '''Ban AI-generated from all articles, AI anything from BLP and medical articles''' is the position that seems it would permit all instances where there are plausible defenses that AI use does not fabricate or destroy facts intended to be communicated in the context of the article. That scrutiny is stricter with BLP and medical articles in general, and the restriction should be stricter to match. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 06:53, 31 December 2024 (UTC)
*:@], please see my comment immediately above. (We had an edit conflict.) Do you really mean "anything" and everything? Even a simple chart? ] (]) 07:00, 31 December 2024 (UTC)
*::I think my previous comment is operative: almost anything we can see AI used programmatically to generate should be SVG, not raster—even if it means we are embedding raster images in SVG to generate examples like the above. I do not know if there are models that can generate SVG, but if there are I happily state I have no problem with that. I think I'm at risk of seeming downright paranoid—but understanding how errors can propagate and go unnoticed in practice, if we're to trust a black box, we need to at least be able to check what the black box has done on a direct structural level. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 07:02, 31 December 2024 (UTC)
*:::A quick web search indicates that there are generative AI programs that create SVG files. ] (]) 07:16, 31 December 2024 (UTC)
*::::Makes perfect sense that there would be. Again, maybe I come off like a paranoid lunatic, but I really need either the ability to check what the thing is doing, or the ability to check and correct exactly what a black box has done. (In my estimation, if you want to know what procedures person has done, theoretically you can ask them to get a fairly satisfactory result, and the pre-AI algorithms used in image manipulation are canonical and more or less transparent. Acknowledging human error etc., with AI there is not even the theoretical promise that one can be given a truthful account of how it decided to do what it did.) <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 07:18, 31 December 2024 (UTC)
*:::::Like everyone said, there should be a ''de facto'' ban on using AI images in Misplaced Pages articles. They are effectively fake images pretending to be real, so they are out of step with the values of Misplaced Pages.--'''''] <sup>]</sup>''''' 08:20, 31 December 2024 (UTC)
*::::::Except, not everybody ''has'' said that, because the majority of those of us who have refrained from hyperbole have pointed out that not all AI images are "fake images pretending to be real" (and those few that are can already be removed under existing policy). You might like to try actually reading the discussion before commenting further. ] (]) 10:24, 31 December 2024 (UTC)
*:::::@], exactly how much "ability to check what the thing is doing" do you need to be able to do, when the image shows 99 dots and 1 baseball, to illustrate the concept of 1%? If the image above said {{tl|pd-algorithm}} instead of {{tl|cc-by-sa-4.0}}, would you remove if from the article, because you just can't be sure that it shows 1%? ] (]) 02:33, 2 January 2025 (UTC)
*::::::The above is a useful example to an extent, but it is a toy example. I really do think i is required in general when we aren't dealing with media we ourselves are generating. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 04:43, 2 January 2025 (UTC)
*:::::::How do we differentiate in policy between a "toy example" (that really would be used in an article) and "real" examples? Is it just that if I upload it, then you know me, and assume I've been responsible? ] (]) 07:13, 2 January 2025 (UTC)
*::::There definitely exist generative AI for SVG files. Here's an example: I used generative AI in Adobe Illustrator to generate the SVG gear in ] (from ]) before drawing by hand the more informative parts of the image. The gear drawing is not great (a real gear would have uniform tooth shape) but maybe the shading is better than I would have done by hand, giving an appearance of dimensionality and surface material while remaining deliberately stylized. Is that the sort of thing everyone here is trying to forbid?
*::::I can definitely see a case for forbidding AI-generated photorealistic images, especially of BLPs, but that's different from human oversight of AI in the generation of schematic images such as this one. —] (]) 01:15, 1 January 2025 (UTC)
*:::::I'd include BDPs, too. I had to get a few AI-generated images of allegedly Haitian presidents deleted a while ago. The "paintings" were 100% fake, right down to the deformed medals on their military uniforms. An AI-generated "generic person" would be okay for some purposes. For a few purposes (e.g., illustrations of ]) it could even be preferable to have a fake "person" than a real one. But for individual/named people, it would be best not to have anything unless it definitely looks like the named person. ] (]) 07:35, 2 January 2025 (UTC)
*I put it to you that our decision on this requires nuance. It's obviously insane to allow AI-generated images of, for example, Donald Trump, and it's obviously insane to ban AI-generated images from, for example, ] or ].—] <small>]/]</small> 11:21, 31 December 2024 (UTC)
*:Of course, that's why I'm only looking at specific cases and refrain from proposing a blanket ban on generative AI. Regarding Donald Trump, we do have one AI-generated image of him that is reasonable to allow (in ]), as the image itself was the subject of relevant commentary. Of course, this is different from using an AI-generated image to illustrate ] himself, which is what my proposal would recommend against. ] (] · ]) 11:32, 31 December 2024 (UTC)
*::That's certainly true, but others are adopting much more extreme positions than you are, and it was the more extreme views that I wished to challenge.—] <small>]/]</small> 11:34, 31 December 2024 (UTC)
*:::Thanks for the (very reasoned) addition, I just wanted to make my original proposal clear. ] (] · ]) 11:43, 31 December 2024 (UTC)
*Going off WAID's example above, perhaps we should be trying to restrict the use of AI where image accuracy/precision is essential, as it would be for BLP and medical info, among other cases, but in cases where we are talking generic or abstract concepts, like the 1% image, it's use is reasonable. I would still say we should strongly prefer am image made by a human with high control of the output, but when accuracy is not as important as just the visualization, it's reasonable to turn to AI to help. ] (]) 15:12, 31 December 2024 (UTC)
* '''Support total ban of AI imagery''' - There are probable copyright problems and veracity problems with anything coming out of a machine. In a word of manipulated reality, Misplaced Pages will be increasingly respected for holding a hard line against synthetic imagery. ] (]) 15:39, 31 December 2024 (UTC)
*:For both issues AI vs not AI is irrelevant. For copyright, if the image is a copyvio we can't use it regardless of whether it is AI or not AI, if it's not a copyvio then that's not a reason to use or not use the image. If the images is not verifiably accurate then we already can (and should) exclude it, regardless of whether it is AI or not AI. For more detail see the extensive discussion above you've either not read or ignored. ] (]) 16:34, 31 December 2024 (UTC)
*'''Yes''', we absolutely should ban the use of AI-generated images in these subjects (and beyond, but that's outside the scope of this discussion). AI should not be used to make up a simulation of a living person. It does not actually depict the person and may introduce errors or flaws that don't actually exist. The picture ''does not depict the real person'' because it is quite simply fake.
*Even worse would be using AI to develop medical images in articles ''in any way''. The possibility for error there is unacceptable. Yes, humans make errors too, but there there is a) someone with the responsibility to fix it and b) someone conscious who actually made the picture, rather than a black box that spat it out after looking at similar training data. '']'' 🎄 ] — ] 🎄 20:08, 31 December 2024 (UTC)
*:It's ''incredibly'' disheartening to see multiple otherwise intelligent editors who have apparently not read and/or not understood what has been said in the discussion but rather responding with what appears to be knee-jerk reactions to anti-AI scaremongering. The sky will not fall in, Misplaced Pages is not going to be taken over by AI, AI is not out to subvert Misplaced Pages, we already can (and do) remove (and more commonly not add in the first placE) false and misleading information/images. ] (]) 20:31, 31 December 2024 (UTC)
*::So what benefit does allowing AI images bring? We shouldn't be forced to decide these on a case-by-case basis.
*::I'm sorry to dishearten you, but I still respectfully disagree with you. And I don't think this is "scaremongering" (although I admit that if it was, I would of course claim it wasn't). '']'' 🎄 ] — ] 🎄 21:02, 31 December 2024 (UTC) '']'' 🎄 ] — ] 🎄 20:56, 31 December 2024 (UTC)
*:::Determining what benefits ''any'' image brings to Misplaced Pages can ''only'' be done on a case-by-case basis. It is literally impossible to know whether any image improves the encyclopaedia without knowing the context of which portion of what article it would illustrate, and what alternative images are and are not available for that same spot.
*:::The benefit of allowing AI images is that when an AI image is the best option for a given article we use it. We gain absolutely nothing by prohibiting using the best image available, indeed doing so would actively harm the project without bringing any benefits. AI images that are misleading, inaccurate or any of the other negative things ''any'' image can be are never the best option and so are never used - we don't need any policies or guidelines to tell us that. ] (]) 21:43, 31 December 2024 (UTC)
*'''Support blanket ban on AI-generated text or images in articles''', except in contexts where the AI-generated content is itself the subject of discussion (in a ] or ]). Generative AI is fundamentally at odds with Misplaced Pages's mission of providing reliable information, because of its propensity to distort reality or make up information out of whole cloth. It has no place in our encyclopedia. <span class="nowrap">—] (] | ])</span> 21:34, 31 December 2024 (UTC)
*'''Support blanket ban on AI-generated images''' except in ABOUTSELF contexts. This is ''especially'' a problem given the preeminence Google gives to Misplaced Pages images in its image search. ] (]) 22:49, 31 December 2024 (UTC)
*'''Ban across the board''', except in articles which are actually about AI-generated imagery or the tools used to create them, or the image itself is the subject of substantial commentary within the article for some reason. Even in those cases, clearly indicating that the image is AI-generated should be required. ] <small><sup>]</sup></small> 00:29, 1 January 2025 (UTC)
*'''Oppose blanket bans''' that would forbid the use of AI assistance in creating diagrams or other deliberately stylized content. Also oppose blanket bans that would forbid AI illustrations in articles about AI illustrations. I am not opposed to banning photorealistic AI-generated images in non-AI-generation contexts or banning AI-generated images from BLPs unless the image itself is specifically relevant to the subject of the BLP. —] (]) 01:27, 1 January 2025 (UTC)
]?]]
*'''Oppose blanket bans''' AI is just a new buzzword so, for example, Apple phones now include "Apple Intelligence" as a standard feature. Does this means that photographs taken using Apple phones will be inadmissable? That would be silly because legacy technologies are already rife with issues of accuracy and verification. For example, there's an image on the main page right now ''(right)''. This purports to be a particular person ("]") but, if you check the , you find that it may have been his brother and even the attribution to the artist is uncertain. AI features may help in exposing such existing weaknesses in our image use and so we should be free to use them in an intelligent way. ]🐉(]) 08:03, 1 January 2025 (UTC)
*:So, you expect an the AI, ''notoriously trained on Misplaced Pages (and whatever else is floating around on the internet)'', to correct Misplaced Pages where humans have failed... using the data it ''scraped from Misplaced Pages (and who knows where else)''? ] (]) 11:12, 1 January 2025 (UTC)
*::I tried using the Deep Research option of Gemini to assess the attribution of the Macquarie portrait. Its stated methodology seemed quite respectable and sensible.
{{cot|The Opie Portrait of Lachlan Macquarie: An Examination of its Attribution: Methodology}}
To thoroughly investigate the attribution of the Opie portrait of Lachlan Macquarie, a comprehensive research process was undertaken. This involved several key steps:
#Gathering information on the Opie portrait: This included details about its history, provenance, and any available information on its cost.
#Reviewing scholarly articles and publications: This step focused on finding academic discussions specifically addressing the attribution of the portrait to John Opie.
#Collecting expert opinions: Statements and opinions from art experts and historians were gathered to understand the range of perspectives on the certainty of the attribution.
#Examining historical documents and records: This involved searching for any records that could shed light on the portrait's origins and authenticity, such as Macquarie's personal journals or contemporary accounts.
#Exploring scientific and technical analyses: Information was sought on any scientific or technical analyses conducted on the portrait, such as pigment analysis or canvas dating, to determine its authenticity.
#Comparing the portrait to other Opie works: This step involved analyzing the style and technique of the Opie portrait in comparison to other known portraits by Opie to identify similarities and differences.
{{cob}}
*::It was quite transparent in listing and citing the sources that it used for its analysis. These included the Misplaced Pages image but if one didn't want that included, it would be easy to exclude it.
*::So, AIs don't have to be inscrutable black boxes. They can have programmatic parameters like the existing bots and scripts that we use routinely on Misplaced Pages. Such power tools seem needed to deal with the large image backlogs that we have on Commons. Perhaps they could help by providing captions and categories where these don't exist.
*::]🐉(]) 09:09, 2 January 2025 (UTC)
*:::They don't ''have to be black boxes'' but they are ''by design'': they exist in a legally dubious area and thus hide what they're scraping to avoid further legal problems. That's no secret. We know for example that Misplaced Pages is a core data set for likely most AIs today. They also notoriously and quite confidently spit out a lie ("hallucinate") and frequently spit out total nonsense. Add to that that they're restricted to whatever is floating around on the internet or whatever other data set they've been fed (usually just more internet), and many specialist topics, like texts on ancient history and even standard reference works, are not accessible on the internet (despite Google's efforts). ] (]) 09:39, 2 January 2025 (UTC)
*:::While its stated methodology seems sensible, there's no evidence that it actually followed that methodology. The bullet points are pretty vague, and are pretty much the default methodologies used to examine actual historical works. ] (] · ]) 17:40, 2 January 2025 (UTC)
*:::: Yes, there's evidence. As I stated above, the analysis is transparent and cites the sources that it used. And these all seem to check out rather than being invented. So, this level of AI goes beyond the first generation of LLM and addresses some of their weaknesses. I suppose that image generation is likewise being developed and improved and so we shouldn't rush to judgement while the technology is undergoing rapid development. ]🐉(]) 17:28, 4 January 2025 (UTC)
* '''Oppose blanket ban''': best of luck to editors here who hope to be able to ban an entirely undefined and largely undetectable procedure. The term 'AI' as commonly used is no more than a buzzword - what ''exactly'' would be banned? And how does it improve the encyclopedia to encourage editors to object to images not simply because they are inaccurate, or inappropriate for the article, but because they subjectively look too good? Will the image creator be quizzed on Commons about the tools they used? Will creators who are transparent about what they have created have their images deleted while those who keep silent don’t? Honestly, this whole discussion is going to seem hopelessly outdated within a year at most. It’s like when early calculators were banned in exams because they were ‘cheating’, forcing students to use slide rules. ] (]) 12:52, 1 January 2025 (UTC)
*:I am genuinely confused as to why this has turned into a discussion about a blanket ban, even though the original proposal exclusively focused on ''AI-generated'' images (the kind that is generated by an AI model from a prompt, which are already tagged on Commons, not regular images with AI enhancement or tools being used) and only in specific contexts. Not sure where the "subjectively look too good" thing even comes from, honestly. ] (] · ]) 12:58, 1 January 2025 (UTC)
*::That just show how ill-defined the whole area is. It seem you restrict the term 'AI-generated' to mean "images generated solely(?) from a text prompt". The question posed above has no such restriction. What a buzzword means is largely in the mind of the reader, of course, but to me and I think to many, 'AI-generated' means generated by AI. ] (]) 13:15, 1 January 2025 (UTC)
*:::I used the text prompt example because that is the most common way to have an AI model generate an image, but I recognize that I should've clarified it better. There is definitely a distinction between an image being ''generated'' by AI (like the Laurence Boccolini example below) and an image being ''altered'' or retouched by AI (which includes many features integrated in smartphones today). I don't think it's a "buzzword" to say that there is a meaningful difference between an image being made up by an AI model and a preexisting image being altered in some way, and I am surprised that many people understand "AI-generated" as including the latter. ] (] · ]) 15:24, 1 January 2025 (UTC)
*'''Oppose as unenforceable.''' I just want you to imagine enforcing this policy against people who have not violated it. All this will do is allow Wikipedians who primarily contribute via text to accuse artists of using AI ] to get their contributions taken down. I understand the impulse to oppose AI on principle, but the labor and aesthetic issues don't actually have anything to do with Misplaced Pages. If there is not actually a problem with the content conveyed by the image—for example, if the illustrator intentionally corrected any hallucinations—then someone objecting over AI is not discussing page content. If the image was not even made with AI, they are hallucinating based on prejudices that are irrelevant to the image. The bottom line is that images should be judged on their content, not how they were made. Besides all the policy-driven stuff, if Misplaced Pages's response to the creation of AI imaging tools is to crack down on all artistic contributions to Misplaced Pages (which seems to be the inevitable direction of these discussions), what does that say? Categorical bans of this kind are ill-advised and anti-illustrator. ] (]) 15:41, 1 January 2025 (UTC)
*:And the same applies to photography, of course. If in my photo of a garden I notice there is a distracting piece of paper on the lawn, nobody would worry if I used the old-style clone-stamp tool to remove it in Photoshop, adding new grass in its place (I'm assuming here that I don't change details of the actual landscape in any way). Now, though, Photoshop uses AI to achieve essentially the same result while making it simpler for the user. A large proportion of all processed photos will have at least some similar but essentially undetectable "generated AI" content, even if only a small area of grass. There is simply no way to enforce the proposed policy, short of banning all high-quality photography – which requires post-processing by design, and in which similar encyclopedically non-problematic edits are commonplace. ] (]) 17:39, 1 January 2025 (UTC)
*:Before anyone objects that my example is not "an image generated from a text prompt", note that there's no mention of such a restriction in the proposal we are discussing. Even if there were, it makes no difference. Photoshop can already generate photo-realistic areas from a text prompt. If such use is non-misleading and essentially undetectable, it's fine; if if changes the image in such a way as to make it misleading, inaccurate or non-encycpopedic in any way it can be challenged on that basis. ] (]) 17:58, 1 January 2025 (UTC)
*::As I said previously, the text prompt is just an example, not a restriction of the proposal. The point is that you talk about editing an existing image (which is what you talk about, as you say {{tq|if if changes the image}}), while I am talking about creating an image ''ex nihilo'', which is what "generating" means. ] (] · ]) 18:05, 1 January 2025 (UTC)
*:::I'm talking about a photograph with AI-generated areas within it. This is commonplace, and is targeted by the proposal. Categorical bans of the type suggested are indeed ill-advised. ] (]) 18:16, 1 January 2025 (UTC)
*:Even if the ban is unenforceable, there are many editors who will choose to use AI images if they are allowed and just as cheerfully skip them if they are not allowed. That would mean the only people posting AI images are those who choose to break the rule and/or don't know about it. That would probably add up to many AI images not used. ] (]) 22:51, 3 January 2025 (UTC)
*'''Support blanket ban''' because "AI" is a fundamentally unethical technology based on the exploitation of labor, the wanton destruction of the planetary environment, and the subversion of every value that an encyclopedia should stand for. ABOUTSELF-type exceptions for "AI" output ''that has already been generated'' might be permissible, in order to document the cursed time in which we live, but those exceptions are going to be rare. How many examples of Shrimp Jesus slop do we need? ] (]) 23:30, 1 January 2025 (UTC)
*'''Support blanket ban''' - Primarily because of the "poisoning the well"/"dead internet" issues created by it. ] (]) 14:30, 2 January 2025 (UTC)
* '''Support a blanket ban''' to assure some control over AI-creep in Misplaced Pages. And per discussion. ] (]) 10:50, 3 January 2025 (UTC)
* '''Support that ] applies to images''': images should be verifiable, neutral, and absent of original research. AI is just the latest quickest way to produce images that are original, unverifiable, and potentially biased. Is anyone in their right mind saying that we allow people to game our rules on ] and ] by using images instead of text? ] (]) 17:04, 3 January 2025 (UTC)
*:As an aside on this: in some cases Commons is being treated as a way of side-stepping ] and other restrictions. Stuff that would get deleted if it were written content on WP gets in to WP as images posted on Commons. The worst examples are those conflict maps that are created from a bunch of Twitter posts (eg the Syrian civil war one). AI-generated imagery is another field where that appears to be happening. ] (]) 10:43, 4 January 2025 (UTC)
*'''Support temporary blanket ban''' with a posted expiration/requred rediscussion date of no more than two years from closing. AI as the term is currently used is very, very new. Right now these images would do more harm than good, but it seems likely that the culture will adjust to them. I support an exception for the when the article is about the image itself and that image is notable, such as the photograph of the black-and-blue/gold-and-white dress in ] and/or examples of AI images in articles in which they are relevant. E.g. "here is what a hallucination is: count the fingers." ] (]) 23:01, 3 January 2025 (UTC)
* First, I think any guidance should avoid referring to specific technology, as that changes rapidly and is used for many different purposes. Second, assuming that the image in question has a suitable copyright status for use on Misplaced Pages, the key question is whether or not the reliability of the image has been established. If the intent of the image is to display 100 dots with 99 having the same appearance and 1 with a different appearance, then ordinary math skills are sufficient and so any Misplaced Pages editor can evaluate the reliability without performing original research. If the intent is to depict a likeness of a specific person, then there needs to be reliable sources indicating that the image is sufficiently accurate. This is the same for actual photographs, re-touched ones, drawings, hedcuts, and so forth. Typically this can be established by a reliable source using that image with a corresponding description or context. ] (]) 17:59, 4 January 2025 (UTC)
*'''Support Blanket Ban on AI generated imagery''' per most of the discussion above. It's a very slippery slope. I ''might'' consider a very narrow exception for an AI generated image of a person that was specifically authorized or commissioned by the subject. -] (]) 02:45, 5 January 2025 (UTC)
* '''Oppose blanket ban''' It is far too early to take an absolutist position, particularly when the potential is enormous. Misplaced Pages is already is image desert and to reject something that is only at the cusp of development is unwise. '''<span style="text-shadow:7px 7px 8px black; font-family:Papyrus">]<sup>]</sup></span>''' 20:11, 5 January 2025 (UTC)
*'''Support blanket ban''' on AI-generated images except in ABOUTSELF contexts. An encyclopedia should not be using fake images. I do not believe that further nuance is necessary. ] (]) 22:44, 5 January 2025 (UTC)
*'''Support blanket ban''' as the general guideline, as accuracy, personal rights, and intellectual rights issues are very weighty, here (as is disclosure to the reader). (I could see perhaps supporting adoption of a sub-guideline for ways to come to a broad consensus in individual use cases (carve-outs, except for BLPs) which address all the weighty issues on an individual use basis -- but that needs to be drafted and agreed to, and there is no good reason to wait to adopt the general ban in the meantime). ] (]) 15:32, 8 January 2025 (UTC)
]
*'''Support indefinite blanket ban except ABOUTSELF and simple abstract examples''' (such as the image of 99 dots above). In addition to all the issues raised above, including copyvio and creator consent issues, in cases of photorealistic images it may never be obvious to all readers exactly which elements of the image are guesswork. The cormorant picture at the head of the section reminded me of ]. Had AI been trained on paintings of horses instead of actual videos and used to "improve" said videos, we would've ended up with serious delusions about the horse's gait. We don't know what questions -- scientific or otherwise -- photography will be used to settle in the coming years, but we do know that consumer-grade photo AI has already been trained to intentionally fake detail to draw sales, such as on photos of the Moon. I think it's unrealistic to require contributors to take photos with expensive cameras or specially-made apps, but Misplaced Pages should act to limit its exposure to this kind of technology as far as is feasible. <span style="font-family:Garamond,Palatino,serif;font-size:115%;background:-webkit-linear-gradient(red,red,red,blue,blue,blue,blue);-webkit-background-clip:text;-webkit-text-fill-color:transparent">] ]</span> 20:57, 9 January 2025 (UTC)
*'''Support at least some sort of recomendation against''' the use AI generated imagery in non-AI contexts−except obviously where the topic of the article is specificly related to AI generated imagery (], ], ], etc.). At the very least the consensus bellow about BLPs should be extened to all historical biographies, as all the examples I've seen (see ]) fail ] (failing to add anything to the sourced text) and serving only to mislead the reader. We inclued images for a reason, not just for decoration. I'm also reminded the essay ], and the distinction it makes between notable depictions of histoical people (which can be useful to illustarate articles) and non-notable fictional portraits which in its (imo well argued) view {{tq|have no legitimate encyclopedic function whatsoever}}. ] ☞️ ] 14:36, 14 January 2025 (UTC)
*:Anything that fails WP:IMAGERELEVANCE can be, should be, and ''is'', excluded from use already, likewise any images which {{tpq|have no legitimate encyclopedic function whatsoever.}} This applies to AI and none AI images equally and identically. Just as we don't have or need a policy or guideline specifically saying don't use irrelevant or otherwise non-encyclopaedic watercolour images in articles we don't need any policy or guideline specifically calling out AI - because it would (as you demonstrate) need to carve out exceptions for when it's use ''is'' relevant. ] (]) 14:45, 14 January 2025 (UTC)
*::That would be an easy change; just add a sentence like "AI-generated images of individual people are primarily decorative and should not be used". We should probably do that no matter what else is decided. ] (]) 23:24, 14 January 2025 (UTC)
*:::Except that is both not true and irrelevant. ''Some'' AI-generated images of individual people are primarily decorative, but not all of them. If an image is purely decorative it shouldn't be used, regardless of whether it is AI-generated or not. ] (]) 13:43, 15 January 2025 (UTC)
*::::Can you give an example of an AI-generated image of an individual person that is (a) not primarily decorative and also (b) not copied from the person's social media/own publications, and that (c) at least some editors think would be a good idea?
*::::"Hey, AI, please give me a realistic-looking photo of this person who died in the 12th century" is not it. "Hey, AI, we have no freely licensed photos of this celebrity, so please give me a line-art caricature" is not it. What is? ] (]) 17:50, 15 January 2025 (UTC)
*:::::Criteria (b) and (c) were not part of the statement I was responding to, and make it a ''very'' significantly different assertion. I will ] that you are not making ] arguments in bad faith, but the frequent fallacious argumentation in these AI discussions is getting tiresome.
*:::::Even with the additional criteria it is still irrelevant - if no editor thinks an image is a good idea, then it won't be used in an article regardless of why they don't think it's a good idea. If some editors think an individual image is a good idea then it's obviously potentially encyclopaedic and needs to be judged on its merits (whether it is AI-generated is completely irrelevant to it's encyclopaedic value). An image that the subject uses on their social media/own publications to identify themselves (for example as an avatar) is the perfect example of the type of image which is frequently used in articles about that individual. ] (]) 18:56, 15 January 2025 (UTC)
{{clear}}
:::: I can't promise that you won't need to give ground however. It's quite possible scientologists themselves chose the current wording and placement, based on wikipedia guidelines that apply to all articles (notably: the ]).
===BLPs===
{{Archive top
|status = Consensus against
|result = There is clear consensus against using AI-generated imagery to depict BLP subjects. Marginal cases (such as major AI enhancement or where an AI-generated image of a living person is itself notable) can be worked out on a case-by-case basis. I will add a sentence reflecting this consensus to the ] and the ]. —] (]) 14:02, 8 January 2025 (UTC)
}}
Are AI-generated images (generated via text prompts, see also: ]) okay to use to depict BLP subjects? The ] example was mentioned in the opening paragraph. The image was created using ], {{tq|a text-to-image model developed by xAI, to generate images...As with other text-to-image models, Aurora generates images from natural language descriptions, called prompts.}} ]]] ] (]) 12:34, 31 December 2024 (UTC)
]]]
:::: I hope this helps! --] 06:09, 9 March 2007 (UTC)
]: <ins>Note</ins>: that these images can either be photorealistic in style (such as the Laurence Boccolini example) or non-photorealistic in style (see the ] example, which was generated using ], another text-to-image model).
:::::I will give it a try and see what happens. Thanks. ] 13:48, 9 March 2007 (UTC)
*'''No.''' I don't think they are at all, as, despite looking photorealistic, they are essentially just speculation about what the person might look like. A photorealistic image conveys the look of something up to the details, and giving a false impression of what the person looks like (or, at best, just guesswork) is actively counterproductive. (Edit 21:59, 31 December 2024 (UTC): clarified bolded !vote since everyone else did it) ] (] · ]) 12:46, 31 December 2024 (UTC)
*:That AI generated image looks like ] wearing a Laurence Boccolini suit. ] (]) 12:50, 31 December 2024 (UTC)
*:There are plenty of non-free images of Laurence Boccolini with which this image can be compared. Assuming at least most of those are accurate representations of them (I've never heard of them before and have no other frame of reference) the image above is similar to but not an accurate representation of them (most obviously but probably least significantly, in none of the available images are they wearing that design of glasses). This means the image should not be used to identify them ''unless'' they use it to identify themselves. It should not be used elsewhere in the article unless it has been the subject of notable commentary. That it is an AI image makes absolutely no difference to any of this. ] (]) 16:45, 31 December 2024 (UTC)
*'''No'''. Well, that was easy.{{pb}}<!--converted from 2 lines ~ToBeFree-->They are fake images; they do not actually depict the person. They depict an AI-generated ''simulation'' of a person that may be inaccurate. '']'' 🎄 ] — ] 🎄 20:00, 31 December 2024 (UTC)
*:Even if the subject uses the image to identify themselves, the image is still fake. '']'' (] — ]) 19:17, 2 January 2025 (UTC)
*'''No''', with the caveat that its mostly on the grounds that we don't have enough information and when it comes to BLP we are required to exercise caution. If at some point in the future AI generated photorealistic simulacrums living people become mainstream with major newspapers and academic publishers it would be fair to revisit any restrictions, but in this I strongly believe that we should follow not lead. ] (]) 20:37, 31 December 2024 (UTC)
*'''No'''. The use of AI-generated images to depict people (living or otherwise) is fundamentally misleading, because the images are not actually depicting the person. <span class="nowrap">—] (] | ])</span> 21:30, 31 December 2024 (UTC)
*'''No''' except perhaps, maybe, if the subject explicitly is already using that image to represent themselves. But mostly no. -] (]) 21:32, 31 December 2024 (UTC)
*'''Yes''', when that image is an accurate representation and better than any available alternative, used by the subject to represent themselves, or the subject of notable commentary. However, as these are the exact requirements to use ''any'' image to represent a BLP subject this is already policy. ] (]) 21:46, 31 December 2024 (UTC)
*:How well can we determine how accurate a representation it is? Looking at the example above, I'd argue that the real ] has a somewhat rounder/pointier chin, a wider mouth, and possibly different eye wrinkles, although the latter probably depends quite a lot on the facial expression.
*:How accurate a representation a photorealistic AI image is is ultimately a matter of editor opinion. '']'' 🎄 ] — ] 🎄 21:54, 31 December 2024 (UTC)
*::{{tpq|How well can we determine how accurate a representation it is?}} in exactly the same way that we can determine whether a human-crafted image is an accurate representation. How accurate a representation ''any'' image is is ultimately a matter of editor opinion. Whether an image is AI or not is irrelevant. I agree the example image above is not sufficiently accurate, but we wouldn't ban photoshopped images because one example was not deemed accurate enough, because we are rational people who understand that one example is not representative of an entire class of images - at least when the subject is something other than AI. ] (]) 23:54, 31 December 2024 (UTC)
*:::I think except in a few exceptional circumstances of actual complex restorations, human photoshopping is not going to change or distort a person's appearance in the same way an AI image would. Modifications done by a person who is paying attention to what they are doing and merely enhancing an image, by person who is aware, while they are making changes, that they might be distorting the image and is, I only assume, trying to minimise it – those careful modifications shouldn't be equated with something made up by an AI image generator. '']'' 🎄 ] — ] 🎄 00:14, 1 January 2025 (UTC)
*::::I'm guessing your filter bubble doesn't include ] and their notorious ] problems. ] (]) 02:46, 2 January 2025 (UTC)
*:::A photo of a person can be connected to a specific time, place, and subject that existed. It can be compared to other images sharing one or more of those properties. A photo that was PhotoShopped is still either a generally faithful reproduction of a scene that existed, or has significant alterations that can still be attributed to a human or at least to a specific algorithm, e.g. filters. The artistic license of a painting can still be attributed to a human and doesn't run much risk of being misidentified as real, unless it's by Chuck Close et al. An AI-generated image cannot be connected to a particular scene that ever existed and cannot be attributable to a human's artistic license (and there is legal precedent that such images are not copyrightable to the prompter specifically because of this). Individual errors in a human-generated artwork are far more predictable, understandable, identifiable, traceable... than those in AI-generated images. We have innate assumptions when we encounter real images or artwork that are just not transferable. These are meaningful differences to the vast majority of people: according to a , 87% of respondents want AI-generated art to ''at least'' be transparent, and 98% consider authentic images "pivotal in establishing trust". {{pb}}And even if you disagree with all that, can you not see the larger problem of AI images on Misplaced Pages getting propagated into generative AI corpora? ] (]) 04:20, 2 January 2025 (UTC)
*::::I agree that our old assumptions don't hold true. I think the world will need new assumptions. We will probably have those in place in another decade or so.
*::::I think we're ], not here to protect AI engines from ingesting AI-generated artwork. Figuring out what they should ingest is their problem, not mine. ] (]) 07:40, 2 January 2025 (UTC)
*'''Absolutely no fake/AI images of people, photorealistic or otherwise'''. How is this even a question? These images are fake. Readers need to be able to trust Misplaced Pages, not navigate around whatever junk someone has created with a prompt and presented as somehow representative. This includes text. ] (]) 22:24, 31 December 2024 (UTC)
*'''No''' except for edge cases (mostly, if the image itself is notable enough to go into the article). ] (]) 22:31, 31 December 2024 (UTC)
*'''Absolutely not''', except for ABOUTSELF. "They're fine if they're accurate enough" is an obscenely naive stance. ] (]) 23:06, 31 December 2024 (UTC)
* '''No''' with no exceptions. ] (]) 23:54, 31 December 2024 (UTC)
*'''No'''. We don't permit falsifications in BLPs. ] <small><sup>]</sup></small> 00:30, 1 January 2025 (UTC)
*:For the requested clarification by {{u|Some1}}, no AI-generated images (except when the image ''itself'' is specifically discussed in the article, and even then it should not be the lead image and it should be clearly indicated that the image is AI-generated), no drawings, no nothing of that sort. ''Actual photographs'' of the subject, nothing else. Articles are not required to have images at all; no image whatsoever is preferable to something which is ''not'' an image of the person. ] <small><sup>]</sup></small> 05:42, 3 January 2025 (UTC)
*'''No, but with exceptions'''. I could imagine a case where a specific AI-generated image has some direct relevance to the notability of the subject of a BLP. In such cases, it should be included, if it could be properly licensed. But I do oppose AI-generated images as portraits of BLP subjects. —] (]) 01:27, 1 January 2025 (UTC)
*:Since I was pinged on this point: when I wrote "I do oppose AI-generated images as portraits", I meant exactly that, including all AI-generated images, such as those in a sketchy or artistic style, not just the photorealistic ones. I am not opposed to certain uses of AI-generated images in BLPs when they are not the main portrait of the subject, for instance in diagrams (not depicting the subject) to illustrate some concept pioneered by the subject, or in case someone becomes famous for being the subject of an AI-generated image. —] (]) 05:41, 3 January 2025 (UTC)
*'''No''', and no exceptions or do-overs. Better to have no images (or Stone-Age style cave paintings) than ''Frankenstein'' images, no matter how accurate or artistic. Akin to shopped manipulated photographs, they should have no room (or room service) at the WikiInn. ] (]) 01:34, 1 January 2025 (UTC)
*:Some "shopped manipulated photographs" are misleading and inaccurate, others are not. We can and do exclude the former from the parts of the encyclopaedia where they don't add value without specific policies and without excluding them where they are relevant (e.g. ]) or excluding those that are not misleading or inaccurate. AI images are no different. ] (]) 02:57, 1 January 2025 (UTC)
*::Assuming we know. Assuming it's material. The infobox image in – and the only extant photo of – ] was "photoshopped" by a marketing team, maybe half a century before Adobe Photoshop was created. They wanted to show him wearing a necktie. I don't think that this level of manipulation is actually a problem. ] (]) 07:44, 2 January 2025 (UTC)
*'''Yes''', so long as it is an accurate representation. ] ] 03:40, 1 January 2025 (UTC)
*'''No''' not for BLPs. ] (]) 04:15, 1 January 2025 (UTC)
*'''No''' Not at all relevant for pictures of people, as the accuracy is not enough and can misrepresent. Also (and I'm shocked as it seems no one has mentioned this), what about Copyright issues? Who holds the copyright for an AI-generated image? The user who wrote the prompt? The creator(s) of the AI model? The creator(s) of the images in the database that the AI used to create the images? It's sounds to me such a clusterfuck of copyright issues that I don't understand how this is even a discussion. --] (]) 07:10, 1 January 2025 (UTC)
*:Under the US law / copyright office, machine-generated images including those by AI cannot be copyrighted. That also means that AI images aren't treated as derivative works.<br style="margin-bottom:0.5em"/>What is still under legal concern is whether the use of bodies of copyrighted works without any approve or license from the copyright holders to train AI models is under fair use or not. There are multiple court cases where this is the primary challenge, and none have yet to reach a decision yet. Assuming the courts rule that there was no fair use, that would either require the entity that owns the AI to pay fines and ongoing licensing costs, or delete their trained model to start afresh with free licensed/works, but in either case, that would not impact how we'd use any resulting AI image from a copyright standpoint.<span id="Masem:1735741774879:WikipediaFTTCLNVillage_pump_(policy)" class="FTTCmt"> — ] (]) 14:29, 1 January 2025 (UTC)</span>
*'''No''', I'm in agreeance with ] here. Whether we like it or not, the usage of a portrait on an article implies that it's just that, a portrait. It's incredibly disingenuous to users to represent an AI generated photo as truth. ] (]) 09:32, 1 January 2025 (UTC)
*:So you just said a portrait can be used because wikipedia tells you it's a portrait, and thus not a real photo. Can't AI be exactly the same? As long as we tell readers it is an AI representation? Heck, most AI looks closer to the real thing than any portrait. ] (]) 10:07, 2 January 2025 (UTC)
*::To clarify, I didn't mean "portrait" as in "painting," I meant it as "photo of person."
*::However, I really want to stick to what you say at the end there: {{tq|Heck, most AI looks closer to the real thing than any portrait.}}
*::That's exactly the problem: by looking close to the "real thing" it misleads users into believing a non-existent source of truth.{{br|2}}
*::Per the wording of the RfC of "{{tq|depict BLP subjects}}," I don't think there would be any valid case to utilize AI images. I hold a strong No. ] (]) 04:15, 3 January 2025 (UTC)
*'''No.''' We should not use AI-generated images for situations like this, they are basically just guesswork by a machine as Quark said and they can misinform readers as to what a person looks like. Plus, there's a big grey area regarding copyright. For an AI generator to know what somebody looks like, it has to have photos of that person in its dataset, so it's very possible that they can be considered derivative works or copyright violations. Using an AI image (derivative work) to get around the fact that we have no free images is just fair use with extra steps. ] (]) 19:33, 1 January 2025 (UTC) ]?]]
*'''Maybe''' There was a prominent BLP image which we displayed on the ]. ''(right)'' This made me uneasy because it was an artistic impression created from photographs rather than life. And it was "colored digitally". Functionally, this seems to be exactly the same sort of thing as the ] composite. The issue should not be whether there's a particular technology label involved but whether such creative composites and artists' impressions are acceptable as better than nothing. ]🐉(]) 08:30, 1 January 2025 (UTC)
*:Except it is clear to everyone that the illustration to the right is a sketch, a human rendition, while in the photorealistic image above, it is less clear. '']'' (] — ]) 14:18, 1 January 2025 (UTC)
*::Except it says right below it "AI-generated image of Laurence Boccolini." How much more clear can it be when it say point-blank "AI-generated image." ] (]) 10:12, 2 January 2025 (UTC)
*:::Commons descriptions do not appear on our articles. ] (]) 10:28, 2 January 2025 (UTC)
*:::People taking a quick glance at an infobox image that looks pretty like a photograph are not going to scrutinize commons tagging. '']'' (] — ]) 14:15, 2 January 2025 (UTC)
*::Keep in mind that many AIs can produce works that match various styles, not just photographic quality. It is still possible for AI to produce something that looks like a watercolor or sketched drawing.<span id="Masem:1735742005673:WikipediaFTTCLNVillage_pump_(policy)" class="FTTCmt"> — ] (]) 14:33, 1 January 2025 (UTC)</span>
*:::Yes, you're absolutely right. But so far photorealistic images have been the most common to illustrate articles (see ] for some examples. '']'' (] — ]) 14:37, 1 January 2025 (UTC)
*::::Then push to ban photorealistic images, rather than pushing for a blanket ban that would also apply to obvious sketches. —] (]) 20:06, 1 January 2025 (UTC)
*:::::Same thing I wrote above, but for "photoshopping" read "drawing": (Bold added for emphasis)
*:::::{{tqq|...human is not going to change or distort a person's appearance in the same way an AI image would. done by a person who is paying attention to what they are doing by '''person who is aware, while they are making , that they might be distorting the image and is, I only assume, trying to minimise it''' – those careful modifications shouldn't be equated with something made up by an AI image generator.}} '']'' (] — ]) 20:56, 1 January 2025 (UTC)
*::::::@] then why are you advocating for a ban on AI images rather than a ban on distorted images? Remember that with careful modifications by someone who is aware of what they are doing that AI images can be made more accurate. Why are you assuming that a human artist is trying to minimise the distortions but someone working with AI is not? ] (]) 22:12, 1 January 2025 (UTC)
*:::::::I believe that AI-generated images are fundamentally misleading because they are a simulation by a machine rather than a drawing by a human. To quote pythoncoder above: {{tqq|The use of AI-generated images to depict people (living or otherwise) is fundamentally misleading, because the images are not actually depicting the person.}} '']'' (] — ]) 00:16, 2 January 2025 (UTC)
*::::::::Once again your actual problem is not AI, but with misleading images. Which can be, and are, already a violation of policy. ] (]) 01:17, 2 January 2025 (UTC)
*:::::::::I think all AI-generated images, except simple diagrams as WhatamIdoing point out above, are misleading. So yes, my problem is with misleading images, which includes all photorealistic images generated by AI, which is why I support this proposal for a blanket ban in BLPs and medical articles. '']'' (] — ]) 02:30, 2 January 2025 (UTC)
*::::::::::To clarify, I'm willing to make an exception in this proposal for very simple geometric diagrams. '']'' (] — ]) 02:38, 2 January 2025 (UTC)
*::::::::::Despite the fact that not all AI-generated images are misleading, not all misleading images are AI-generated and it is not always possible to tell whether an image is or is not AI-generated? ] (]) 02:58, 2 January 2025 (UTC)
*:::::::::::Enforcement is a separate issue. Whether or not all (or the vast majority) of AI images are misleading is the subject of this dispute.
*:::::::::::I'm not going to mistreat the horse further, as we've each made our points and understand where the other stands. '']'' (] — ]) 15:30, 2 January 2025 (UTC)
*::::::::::Even "simple diagrams" are not clear-cut. The process of AI-generating any image, no matter how simple, is still very complex and can easily follow any number of different paths to meet the prompt constraints. These paths through embedding space are black boxes and the likelihood they converge on the same output is going to vary wildly depending on the degrees of freedom in the prompt, the dimensionality of the embedding space, token corpus size, etc. The only thing the user can really change, other than switching between models, is the prompt, and at some point constructing a prompt that is guaranteed to yield the same result 100% of the time becomes a ] exercise. This is in contrast with non-generative AI diagram-rendering software that follow very fixed, reproducible, ''known'' paths. ] (]) 04:44, 2 January 2025 (UTC)
*:::::::::::Why does the path matter? If the output is correct it is correct no matter what route was taken to get there. If the output is incorrect it is incorrect no matter what route was taken to get there. If it is unknown or unknowable whether the output is correct or not that is true no matter what route was taken to get there. ] (]) 04:48, 2 January 2025 (UTC)
*::::::::::::If I use BioRender or GraphPad to generate a figure, I can be confident that the output does not have errors that would misrepresent the underlying data. I don't have to verify that all 18,000 data points in a scatter plot exist in the correct XYZ positions because I know the method for rendering them is published and empirically validated. Other people can also be certain that the process of getting from my input to the product is accurate and reproducible, and could in theory reconstruct my raw data from it. AI-generated figures have no prescribed method of transforming input beyond what the prompt entails; therefore I additionally have to be confident in how precise my prompt is ''and'' confident that the training corpus for this procedure is so accurate that no error-producing paths exist (not to mention absolutely certain that there is no embedded contamination from prior prompts). Other people have all those concerns, and on top of that likely don't have access to the prompt or the raw data to validate the output, nor do they necessarily know how fastidious I am about my generative AI use. At least with a hand-drawn diagram viewers can directly transfer their trust in the author's knowledge and reliability to their presumptions about the diagram's accuracy. ] (]) 05:40, 2 January 2025 (UTC)
*:::::::::::::If you've got 18,000 data points, we are beyond the realm of "simple geometric diagrams". ] (]) 07:47, 2 January 2025 (UTC)
*::::::::::::::The original "simple geometric diagrams" comment was referring to your 100 dots image. I don't think increasing the dots materially changes the discussion beyond increasing the laboriousness of verifying the accuracy of the image. ] (]) 07:56, 2 January 2025 (UTC)
*:::::::::::::::Yes, but since "the laboriousness of verifying the accuracy of the image" is exactly what she doesn't want to undertake for 18,000 dots, then I think that's very relevant. ] (]) 07:58, 2 January 2025 (UTC)
*:{{outdent|14}} And where is that cutoff supposed to be? 1000 dots? A single straight line? An atomic diagram? What is "simple" to someone unfamiliar with a topic may be more complex.{{pb}}And I don't want to count 100 dots either! ] (]) 17:43, 2 January 2025 (UTC)
*::Maybe you don't. But I know for certain that you can count 10 across, 10 down, and multiply those two numbers to get 100. That's what I did when I made the image, after all. ] (]) 07:44, 3 January 2025 (UTC)
* '''Comment''': when you Google search someone (at least from the Chrome browser), often the link to the Misplaced Pages article includes a thumbnail of the lead photo as a preview. Even if the photo is labelled as an AI image in the article, people looking at the thumbnail from Google would be misled (if the image is chosen for the preview). ] (]) 09:39, 1 January 2025 (UTC)
*:This is why we should not use inaccurate images, regardless of how the image was created. It has absolutely nothing to do with AI. ] (]) 11:39, 1 January 2025 (UTC)
* '''Already opposed a blanket ban''': It's unclear to me why we have a separate BLP subsection, as BLPs are already included in the main section above. Anyway, I ] there. ] (])
*:Some editors might oppose a blanket ban on ''all'' AI-generated images, while at the same time, are against using AI-generated images (created by using text prompts/]) to depict ]. ] (]) 14:32, 1 January 2025 (UTC)
*'''No''' For at least now, let's not let the problems of AI intrude into BLP articles which need to have the highest level of scrutiny to protect the person represented. Other areas on WP may benefit from AI image use, but let's keep it far out of BLP at this point. --] (]) 14:35, 1 January 2025 (UTC)
*I am not a fan of “banning” AI images completely… but I agree that BLPs require special handling. I look at AI imagery as being akin to a computer generated painting. In a BLP, we allow paintings of the subject, but we ''prefer'' photos over paintings (if available). So… we should prefer photos over AI imagery. {{pb}}<!--list syntax fixed ~ToBeFree--> That said, AI imagery is getting good enough that it can be mistaken for a photo… so… If an AI generated image ''is'' the ''only'' option (ie there is no photo available), then the caption should ''clearly'' indicate that we are using an AI generated image. And that image should be replaced as soon as possible with an actual photograph. ] (]) 14:56, 1 January 2025 (UTC)
*:The issue with the latter is that Misplaced Pages images get picked up by Google and other search engines, where the caption isn't there anymore to add the context that a photorealistic image was AI-generated. ] (] · ]) 15:27, 1 January 2025 (UTC)
*::We're here to build an encyclopedia, not to protect commercial search engine companies.
*::I think my view aligns with Blueboar's (except that I find no firm preference for photos over classical portrait paintings): We shouldn't have ''inaccurate'' AI images of people (living or dead). But the day appears to be coming when AI will generate accurate ones, or at least ones that are close enough to accurate that we can't tell the difference unless the uploader voluntarily discloses that information. Once we can no longer tell the difference, what's the point in banning them? Images need to look like the thing being depicted. When we put an photorealistic image in an article, we could be said to be implicitly claiming that the image ''looks like'' whatever's being depicted. We are not ''necessarily'' warranting that the image was created through a specific process, but the image really does need to look like the subject. ] (]) 03:12, 2 January 2025 (UTC)
*:::You are presuming that sufficient accuracy will prevent us from knowing whether someone is uploading an AI photo, but that is not the case. For instance, if someone uploads large amounts of "photos" of famous people, and can't account for how they got them (e.g. can't give a source where they scraped them from, or dates or any Exif metadata at all for when they were taken), then it will still be obvious that they are likely using AI. ] (]) 17:38, 3 January 2025 (UTC)
*:::As another editor pointed out in their comment, there's the {{blue|ethics/moral dilemma of creating fake photorealistic pictures of people and putting them on the internet}}, especially on a site such as Misplaced Pages and especially on their own biography. ] says the bios {{tq|must be written conservatively and with regard for the subject's privacy.}} ] (]) 18:37, 3 January 2025 (UTC)
*:::{{tqq| Once we can no longer tell the difference, what's the point in banning them?}} Sounds like a wolf's in sheep's clothing to me. Just because the surface appeal of fake pictures gets better, doesn't mean we should ]. '']'' (] — ]) 18:47, 3 January 2025 (UTC)
*:If there are no appropriately-licensed images of a person, then by definition any AI-generated image of them will be either a copyright infringement or a complete fantasy. ] (]) 04:48, 2 January 2025 (UTC)
*::Whether it would be a copyright infringement or not is both an unsettled legal question and not relevant: If an image is a copyvio we can't use it and it is irrelevant why it is a copyvio. If an image is a "complete fantasy" then it is exactly as unusable as a complete fantasy generated by non-AI means, so again AI is irrelevant. I've had to explain this multiple times in this discussion, so read that for more detail and note the lack of refutation. ] (]) 04:52, 2 January 2025 (UTC)
*:::But we can assume good faith that a human isn't blatantly copying something. We can't assume that from an LLM like Stability AI which has been shown to from Getty's images. ] (]) 05:50, 2 January 2025 (UTC)
*::::Ooooh, I'm not sure that we can assume that humans aren't blatantly copying something. We can assume that they meant to be helpful, but that's not quite the same thing. ] (]) 07:48, 2 January 2025 (UTC)
*<s>'''Oppose.'''</s> '''Yes.''' I echo ]: {{Tq2|What this conversation is really circling around is banning entire skillsets from contributing to Misplaced Pages merely because some of us are afraid of AI images and some others of us want to engineer a convenient, half-baked, policy-level "consensus" to point to when they delete quality images from Misplaced Pages. Every time someone generates text based on a source, they are doing some acceptable level of interpretation to extract facts or rephrase it around copyright law, and I don't think illustrations should be considered so severely differently as to justify a categorical ban. For instance, the Gisele Pelicot portrait is based on non-free photos of her. Once the illustration exists, it is trivial to compare it to non-free images to determine if it is an appropriate likeness, which it is. That's no different than judging contributed text's compliance with fact and copyright by referring to the source. It shouldn't be treated differently just because most Wikipedians contribute via text.<br/>Additionally, referring to interpretive skillsets that synthesize new information like, random example, statistical analysis. Excluding those from Misplaced Pages is current practice and not controversial. Meanwhile, I think the ability to create images is more fundamental than that. It's not (inheretly) synthesizing new information. A portrait of a person (alongside the other examples in this thread) contains verifiable information. It is current practice to allow them to fill the gaps where non-free photos can't. That should continue. Honestly, it should expand.}} ] (]) 15:41, 1 January 2025 (UTC)
*:Additionally, in direct response to "these images are fake": All illustrations of a subject could be called "fake" because they are not photographs. (Which can also be faked.) The standard for the inclusion of an illustration on Misplaced Pages has never been photorealism, medium, or previous publication in a RS. The standard is how adequately it reflects the facts which it claims to depict. If there is a better image that can be imported to Misplaced Pages via fair use or a license, then an image can be easily replaced. Until such a better image has been sourced, it is absolutely bewildering to me that we would even discuss removing images of people from their articles. What a person looked like is one of the most basic things that people want to know when they look someone up on Misplaced Pages. Including an image of almost any quality (yes, even a cartoon) is practically by definition an improvement to the article and addressing an important need. We should be encouraging artists to continue filling the gaps that non-free images cannot fill, not creating policies that will inevitably expand into more general prejudices against all new illustrations on Misplaced Pages. ] (]) 15:59, 1 January 2025 (UTC)
*::By "Oppose", I'm assuming your answer to the RfC question is "Yes". And this RfC is about using {{blue|AI-generated images (generated via text prompts, see also: ])}} to depict BLP subjects, not regarding human-created drawings/cartoons/sketches, etc. of BLPs. ] (]) 16:09, 1 January 2025 (UTC)
*:::I've changed it to "yes" to reflect the reversed question. I think all of this is related because there is no coherent distinguishing point; AI can be used to create images in a variety of styles. These discussions have shown that a policy of banning AI images ''will'' be used against non-AI images of all kinds, so I think it's important to say these kinds of things now. ] (]) 16:29, 1 January 2025 (UTC)
*::Photorealistic images scraped from who knows where from who knows what sources are without question simply fake photographs and also clear ] and outright ]. There's no two ways about it. Articles do ''not'' require images: An article with some Frankenstein-ed image scraped from who knows what, where and, when that you "created" from a prompt is not an improvement over having no image at all. If we can't provide a quality image (like something you didn't cook up from a prompt) then people can find quality, non-fake images elsewhere. ] (]) 23:39, 1 January 2025 (UTC)
*:::I really encourage you to read the discussion I linked before because it is ]. Images like these do not inherently include either OR or SYNTH, and the arguments that they do cannot be distinguished from any other user-generated image content. But, briefly, I never said articles required images, and this is not about what articles ''require''. It is about ''improvements'' to the articles. Including a relevant picture where none exists is almost always an improvement, especially for subjects like people. Your disdain for the method the person used to make an image is irrelevant to whether the content of the image is actually verifiable, and the only thing we ought to care about is the content. ] (]) 03:21, 2 January 2025 (UTC)
*::::Images like these are absolutely nothing more than synthesis in the purest sense of the world and are clearly a violation of ]: Again, you have no idea what data was used to generate these images and you're going to have a very hard time convincing anyone to describe them as anything other than outright fakes.
*::::A reminder that WP:SYNTH shuts down attempts at manipulation of images ("It is not acceptable for an editor to use photo manipulation to distort the facts or position illustrated by an image. Manipulated images should be prominently noted as such. Any manipulated image where the encyclopedic value is materially affected should be posted to Misplaced Pages:Files for discussion. Images of living persons must not present the subject in a false or disparaging light.") and generating a photorealistic image (from who knows what!) is far beyond that.
*::::Fake images of people do not improve our articles in any way and only erode reader trust. What's next, an argument for the ''fake sources'' LLMs also love to "hallucinate"? ] (]) 03:37, 2 January 2025 (UTC)
*:::::So, if you review the first sentence of SYNTH, you'll see it has no special relevance to this discussion: {{Tq|Do not combine material from multiple sources to state or imply a conclusion not explicitly stated by any of the sources.}}. My primary example has been a picture of a person; what a person looks like is verifiable by comparing the image to non-free images that cannot be used on Misplaced Pages. If the image resembles the person, it is not SYNTH. An illustration of a person created and intended to look like that person is not a manipulation. The training data used to make the AI is irrelevant to whether the image in fact resembles the person. You should also review ] because SYNTH is not a policy; NOR is the policy: {{tq|If a putative SYNTH doesn't constitute original research, then it doesn't constitute SYNTH.}} Additionally, ]. A categorical rule against AI cannot be justified by SYNTH because it does not categorically apply to all use cases of AI. To do so would be illogical on top of ill-advised. ] (]) 08:08, 2 January 2025 (UTC)
*::::::"training data used to make the AI is irrelevant" — spoken like a true AI evangelist! Sorry, 'good enough' photorealism is still just synthetic slop, a fake image presented as real of a ''human being''. A fake image of someone generated from who-knows-what that 'resembles' an article's subject is about as ] as it gets. Yikes. As for the attempts to pass of prompt-generated photorealistic fakes of people as somehow the same as someone's illustration, you're completely wasting your time. ] (]) 09:44, 2 January 2025 (UTC)
*:::::::NOR is a content policy and SYNTH is content guidance within NOR. Because you have admitted that this is not ''about the content'' for you, NOR and SYNTH are irrelevant to your argument, which boils down to ] and, now, inaccurate personal attacks. Continuing this discussion between us would be pointless. ] (]) 09:52, 2 January 2025 (UTC)
*::::::::This is in fact entirely about content (why the hell else would I bother?) but it is true that I also dismissed your pro-AI 'it's just like a human drawing a picture!' as outright nonsense a while back. Good luck convincing anyone else with that line - it didn't work here. ] (]) 09:59, 2 January 2025 (UTC)
*'''Maybe''': there is an implicit assumption with this RFC that an AI generated image would be photorealistic. There hasn't been any discussion of an AI generated sketch. If you asked an AI to generate a sketch (that clearly looked like a sketch, similar to the Gisèle Pelicot example) then I would potentially be ok with it. ] (]) 18:14, 1 January 2025 (UTC)
*:That's an interesting thought to consider. At the same time, I worry about (well-intentioned) editors inundating image-less BLP articles with AI-generated images in the style of cartoons/sketches (if only photorealistic ones are prohibited) etc. At least requiring a human to draw/paint/whatever creates a barrier to entry; these AI-generated images can be created in under a minute using these text-to-image models. Editors are already wary about human-created cartoon portraits (]), now they'll be tasked with dealing with AI-generated ones in BLP articles. ] (]) 20:28, 1 January 2025 (UTC)
*::It sounds like your problem is not with AI but with cartoon/sketch images in BLP articles, so AI is once again completely irrelevant. ] (]) 22:14, 1 January 2025 (UTC)
*::That is a good concern you brought up. There is a possibility of the spamming of low quality AI-generated images which would be laborious to discuss on a case-by-case basis but easy to generate. At the same time though that is a possibility, but not yet an actuality, and ] states that new policies should address current problems rather than hypothetical concerns. ] (]) 22:16, 1 January 2025 (UTC)
*Easy '''no''' for me. I am not against the use of AI images wholesale, but I do think that using AI to represent an existent thing such as a person or a place is too far. Even a tag wouldn't be enough for me. ] </nowiki></span>''']] 19:05, 1 January 2025 (UTC)
*'''No''' obviously, per previous discussions about cartoonish drawn images in BLPs. Same issue here as there, it is essentially original research and misrepresentation of a living person's likeness. ] (]) 22:19, 1 January 2025 (UTC)
*'''No''' to photorealistic, no to cartoonish... this is not a hard choice. The idea that "this has nothing to do with AI" when "AI" magnifies the problem to stupendous proportions is just not tenable. ] (]) 23:36, 1 January 2025 (UTC)
*:While AI might "amplify" the thing you dislike, that does not make AI the problem. The problem is whatever underlying thing is being amplified. ] (]) 01:16, 2 January 2025 (UTC)
*::The thing that amplifies the problem is necessarily a problem. ] (]) 02:57, 2 January 2025 (UTC)
*:::That is arguable, but banning the amplifier does not do anything to solve the problem. In this case, banning the amplifier would cause multiple other problems that nobody supporting this proposal as even attempted to address, let alone mitigate. ] (]) 03:04, 2 January 2025 (UTC)
*'''No''' for all people, per Chaotic Enby. ] (]) 03:23, 2 January 2025 (UTC) Add: no to any AI-generated images, whether photorealistic or not. ] (]) 04:00, 3 January 2025 (UTC)
*'''No''' - We should not be hosting faked images (except as notable fakes). We should also not be hosting copyvios ({{tq|"Whether it would be a copyright infringement or not is both an unsettled legal question and not relevant"}} is just totally wrong - we should be steering clear of copyvios, and if the issue is unsettled then we shouldn't use them until it is).
*If people upload faked images to WP or Commons the response should be as it is now. The fact that fakes are becoming harder to detect simply from looking at them hardly affects this - we simply confirm when the picture was supposed to have been taken and examine the plausibility of it from there. ] (]) 14:39, 2 January 2025 (UTC) ] (]) 14:39, 2 January 2025 (UTC)
*:{{tpq|we should be steering clear of copyvio}} we do - if an image is a copyright violation it gets deleted, regardless of why it is a copyright violation. What we do not do is ban using images that are not copyright violations because they are copyright violations. Currently the WMF lawyers and all the people on Commons who know more about copyright than I do say that at least some AI images are legally acceptable for us to host and use. If you want to argue that, then go ahead, but it is not relevant to ''this'' discussion.
*:{{tpq|if people upload faked images the response should be as it is now}} in other words you are saying that the problem is faked images not AI, and that current policies are entirely adequate to deal with the problem of faked images. So we don't need any specific rules for AI images - especially given that not all AI images are fakes. ] (]) 15:14, 2 January 2025 (UTC)
*::The idea that {{tq|current policies are entirely adequate}} is like saying that a lab shouldn't have specific rules about wearing eye protection when it already has a poster hanging on the wall that says "don't hurt yourself". ] (]) 18:36, 2 January 2025 (UTC)
*:::I rely on one of those up in my workshop at home. I figure if that doesn't keep me safe, nothing will. ] (]) 18:41, 2 January 2025 (UTC)
*::::"{{tq|in other words you are saying that the problem is faked images not AI}}" - AI generated images *are* fakes. This is merely confirming that for the avoidance of doubt.
*::::"{{tq|at least some AI images are legally acceptable for us}}" - Until they decide which ones that isn't much help. ] (]) 19:05, 2 January 2025 (UTC)
*:::::Yes – what FOARP said. AI-generated images are fakes and are misleading. '']'' (] — ]) 19:15, 2 January 2025 (UTC)
*:::Those specific rules exist because generic warnings have proven not to be sufficient. Nobody has presented any evidence that the current policies are not sufficient, indeed quite the contrary. ] (]) 19:05, 2 January 2025 (UTC)
*'''No!''' This would be a massive can of worms; perhaps, however, we wish to cause problems in the new year. ] <small>(]) | :) | he/him | </small> 15:00, 2 January 2025 (UTC)
*:Noting that I think that no AI-generated images are acceptable in BLP articles, regardless of whether they are photorealistic or not. ] <small>(]) | :) | he/him | </small> 15:40, 3 January 2025 (UTC)
*'''No''', unless the AI image has encyclopedic significance beyond "depicts a notable person". AI images, if created by editors for the purpose of inclusion in Misplaced Pages, convey little reliable information about the person they depict, and the ways in which the model works are opaque enough to most people as to raise verifiability concerns. ] (] • ]) 15:25, 2 January 2025 (UTC)
*:To clarify, do you object to uses of an AI image in a BLP when the subject uses that image for self-identification? I presume that AI images that have been the subject of notable discussion are an example of "significance beyond depict a notable person"? ] (]) 15:54, 2 January 2025 (UTC)
*::If the subject uses the image for self-identification, I'd be fine with it - I think that'd be analogous to situations such as "cartoonist represented by a stylized self-portrait", which definitely has some precedent in articles like ]. I agree with your second sentence as well; if there's notable discussion around a particular AI image, I think it would be reasonable to include that image on Misplaced Pages. ] (] • ]) 19:13, 2 January 2025 (UTC)
* '''No''', with obvious exceptions, including if the subject theyrself uses the image as a their representation, or if the image is notable itself. Not including the lack of a free aleternative, if there is no free alternative... where did the AI find data to build an image... non free too. Not including images generated by WP editors (that's kind of ]... - ] (]) 18:02, 2 January 2025 (UTC
*'''Maybe''' I think the question is unfair as it is illustrated with what appears to be a photo of the subject but isn't. People are then getting upset that they've been misled. As others note, there are copyright concerns with AI reproducing copyrighted works that in turn make an image that is potentially legally unusable. But that is more a matter for Commons than for Misplaced Pages. As many have noted, a sketch or painting never claims to be an accurate depiction of a person, and I don't care if that sketch or painting was done by hand or an AI prompt. I strongly ask ] to abort the RFC. You've asked people to give a yes/no vote to what is a more complex issue. A further problem with the example used is the unfortunate prejudice on Misplaced Pages against user-generated content. While the text-generated AI of today is crude and random, there will come a point where many professionally published photos illustrating subjects, including people, are AI generated. Even today, your smartphone can create a groupshot where everyone is smiling and looking at the camera. It was "trained" on the 50 images it quickly took and responded to the build-in "text prompt" of "create a montage of these photos such that everyone is smiling and looking at the camera". This vote is a knee jerk reaction to content that is best addressed by some other measure (such as that it is a misleading image). And a good example of asking people to vote way too early, when the issues haven't been throught out -- ]°] 18:17, 2 January 2025 (UTC)
*'''No''' This would very likely set a dangerous precedent. The only exception I think should be if the image itself is notable. If we move forward with AI images, especially for BLPs, it would only open up a whole slew of regulations and RfCs to keep them in check. Better no image than some digital multiverse version of someone that is "basically" them but not really. Not to mention the ethics/moral dilemma of creating fake photorealistic pictures of people and putting them on the internet. ] (]) 18:31, 2 January 2025 (UTC)
*'''No'''. LLMs don't generate answers, they generate ''things that look like'' answers, but aren't; a lot of the time, that's good enough, but sometimes it very much isn't. It's the same issue for text-to-image models: they don't generate photos of people, they generate ''things that look like'' photos. Using them on BLPs is unacceptable. ] (]) 19:30, 2 January 2025 (UTC)
*'''No'''. I would be pissed if the top picture of me on Google was AI-generated. I just don't think it's moral for living people. The exceptions given above by others are okay, such as if the subject uses the picture themselves or if the picture is notable (with context given). ] (]) 19:56, 2 January 2025 (UTC)
*'''No.''' Uploading alone, although mostly a Commons issue, would already a problem to me and may have personality rights issues. Illustrating an article with a fake photo <ins>(or drawing)</ins> of a living person, even if it is labeled as such, would not be acceptable. For example, it could end up being shown by search engines or when hovering over a Misplaced Pages link, without the disclaimer. ] (]) 23:54, 2 January 2025 (UTC)
* I was going to say no... but we allow paintings as portraits in BLPs. What's so different between an AI generated image, and a painting? Arguments above say the depiction may not be accurate, but the same is true of some paintings, right? (and conversely, not true of other paintings) ] (]) 00:48, 3 January 2025 (UTC)
*::A painting is clearly a painting; as such, the viewer knows that it is not an accurate representation of a particular reality. An AI-generated image made to look exactly like a photo, looks like a photo but is not.
*:] (]) 02:44, 3 January 2025 (UTC)
*::Not all paintings are clearly paintings. Not all AI-generated images are made to look like photographs. Not all AI-generated images made to look like photos do actually look like photos. This proposal makes no distinction. ] (]) 02:55, 3 January 2025 (UTC)
*:::Not to mention, hyper-realism is a style an artist may use in virtually any medium. If Misplaced Pages would accept an analog substitute like a painting, there's no reason Misplaced Pages shouldn't accept an equivalent painting made with digital tools, and there's no reason Misplaced Pages shouldn't accept an equivalent painting made with AI. That is, one where any obvious defects have been edited out and what remains is a straightforward picture of the subject. ] (]) 03:45, 3 January 2025 (UTC)
*::::For the record (and for any media watching), while I personally find it fascinating that a few editors here are spending a substantial amount of time (in the face of an overwhelming 'absolutely not' consensus no less) attempting to convince others that computer-generated (that is, ''faked'') photos of human article subjects are somehow ''a good thing'', I also find it interesting that these editors seem to express absolutely no concern for the intensely negative reaction they're already seeing from their fellow editors and seem totally unconcerned about the inevitable trust drop we'd experience from Misplaced Pages readers when they would encounter fake photos on our BLP articles especially. ] (]) 03:54, 3 January 2025 (UTC)
*:::::Misplaced Pages's reputation would not be affected positively or negatively by expanding the current-albeit-sparse use of illustrations to depict subjects that do not have available pictures. In all my writing about this over the last few days, you are the only one who has said anything negative about me as a person or, really, my arguments themselves. As loath as I am to cite it, ] means assuming that people you disagree with are not ''trying to hurt Misplaced Pages.'' Thryduulf, I, and others have explained in detail why we think our ultimate ideas are explicit benefits to Misplaced Pages and why our opposition to these immediate proposals comes from a desire to prevent harm to Misplaced Pages. I suggest taking a break to reflect on that, matey. ] (]) 04:09, 3 January 2025 (UTC)
*::::::Look, I don't know if you've been living under a rock or what for the past few years but the reality is that '' people hate AI images'' and dumping a ton of AI/fake images on Misplaced Pages, a place people go for ''real information'' and often ''trust'', inevitably leads to a huge trust issue, something Misplaced Pages is increasingly suffering from already. This is ''especially'' a problem when they're intended to represent ''living people'' (!). I'll leave it to you to dig up the bazillion controversies that have arisen and continue to arise since companies worldwide have discovered that they can now replace human artists with 'AI art' produced by "prompt engineers" but you can't possibly expect us to ignore that reality when discussing these matters. ] (]) 04:55, 3 January 2025 (UTC)
*:::::::Those trust issues are born from the publication of hallucinated information. I have only said that it should be OK to use an image on Misplaced Pages when it contains only verifiable information, which is the same standard we apply to text. That standard is and ought to be applied independently of the way the initial version of an image was created. ] (]) 06:10, 3 January 2025 (UTC)
*:To my eye, the distinction between AI images and paintings here is less a question of medium and more of verifiability: the paintings we use (or at least the ones I can remember) are significant paintings that have been acknowledged in sources as being reasonable representations of a given person. By contrast, a purpose-generated AI image would be more akin to me painting a portrait of somebody here and now and trying to stick that on their article. The image could be a faithful representation <small>(unlikely, given my lack of painting skills, but let's not get lost in the metaphor)</small>, but if my painting hasn't been discussed anywhere besides Misplaced Pages, then it's potentially OR or UNDUE to enshrine it in mainspace as an encyclopedic image. ] (] • ]) 05:57, 3 January 2025 (UTC)
*::An image contains a collection of facts, and those facts need to be verifiable just like any other information posted on Misplaced Pages. An image that verifiably resembles a subject as it is depicted in reliable sources is categorically ''not OR''. Discussion in other sources is not universally relevant; we don't restrict ourselves to only previously-published images. If we did that, Misplaced Pages would have very few images. ] (]) 06:18, 3 January 2025 (UTC)
*:::Verifiable how? Only by the editor themselves comparing to a real photo (which was probably used by the LLM to create the image…).
*:::These things are fakes. The analysis stops there. ] (]) 10:48, 4 January 2025 (UTC)
*::::Verifiable by comparing them to a reliable source. Exactly the same as what we do with text. There is no coherent reason to treat user-generated images differently than user-generated text, and the universalist tenor of this discussion has damaging implications for all user-generated images regardless of whether they were created with AI. Honestly, I rarely make arguments like this one, but I think it could show some intuition from another perspective: Imagine it's 2002 and Misplaced Pages is just starting. Most users want to contribute text to the encyclopedia, but there is a cadre of artists who want to contribute pictures. The text editors say the artists cannot contribute ANYTHING to Misplaced Pages because their images that have not been previously published are not verifiable. That is a double-standard that privileges the contributions of text-editors simply because most users are text-editors and they are used to verifying text; that is not a principled reason to treat text and images differently. Moreover, that is simply not what happened—The opposite happend, and images are treated as verifiable based on their contents just like text because that's a common sense reading of the rule. It would have been madness if images had been treated differently. And yet that is essentially the fundamentalist position of people who are extending their opposition to AI with arguments that apply to all images. If they are arguing verifiability seriously at all, they are pretending that the sort of degenerate situation I just described already exists when the opposite consensus has been reached consistently ''for years''. In ], they even tried to say Wikipedians had "turned a blind eye" to these image issues as if negatively characterizing those decisions would invalidate the fact that ''those decisions were consensus.'' The motivated reasoning of these discussions has been as blatant as that.<br/>At the bottom of this dispute, I take issue with trying to alter the rules in a way that creates a new double-standard within verifiability that applies to all images but not text. That's especially upsetting when (despite my and others' best efforts) so many of us are still focusing ''SOLELY'' on their hatred for AI rather than considering the obvious second-order consequences for user-generated images as a whole.<br/>Frankly, in no other context has any Wikipedian ever allowed me to say text they wrote was "fake" or challenge an image based on whether it was "fake." The issue has always been ''verifiability'', not provenance or falsity. Sometimes, IMO, that has lead to disaster and Misplaced Pages saying things I know to be factually untrue despite the contents of reliable sources. But ''that'' is the policy. We compare the contents of Misplaced Pages to reliable sources, and the contents of Misplaced Pages are considered verifiable if they cohere.<br/>I ask again: If Misplaced Pages's response to the creation of AI imaging tools is to crack down on all artistic contributions to Misplaced Pages (which seems to be the inevitable direction of these discussions), what does that say? If our negative response to AI tools is to ''limit what humans can do on Misplaced Pages'', what does that say? Are we taking a stand for human achievements, or is this a very heated discussion of cutting off our nose to save our face? ] (]) 23:31, 4 January 2025 (UTC)
*:::::{{tq|"Verifiable by comparing them to a reliable source"}} - comparing two images and saying that one ''looks like'' the other is not "verifying" anything. The text equivalent is presenting something as a quotation that is actually a user-generated paraphrasing.
*:::::{{tq|"Frankly, in no other context has any Wikipedian ever allowed me to say text they wrote was "fake" or challenge an image based on whether it was "fake.""}} - Try presenting a paraphrasing as a quotation and see what happens.
*:::::{{tq|"Imagine it's 2002 and Misplaced Pages is just starting. Most users want to contribute text to the encyclopedia, but there is a cadre of artists who want to contribute pictures..."}} - This basically happened, and is the origin of ]. Misplaced Pages is not a host for original works. ] (]) 22:01, 6 January 2025 (UTC)
*::::::{{tq|Comparing two images and saying that one looks like the other is not "verifying" anything.}} Comparing text to text in a reliable source is literally the same thing.
*::::::{{tq|The text equivalent is presenting something as a quotation that is actually a user-generated paraphrasing.}} No it isn't. The text equivalent is writing a sentence in an article and putting a ref tag on it. Perhaps there is room for improving the referencing of images in the sense that they should offer example comparisons to make. But an image created by a person is not unverifiable simply because it is user-generated. It is not somehow ''more'' unverifiable simply because it is created in a lifelike style.
*::::::{{tq|Try presenting a paraphrasing as a quotation and see what happens.}} Besides what I just said, ''nobody'' is even presenting these images as equatable to quotations. People in this thread have simply been calling them "fake" of their own initiative; the uploaders have not asserted that these are literal photographs to my knowledge. The uploaders of illustrations obviously did not make that claim either. (And, if the contents of the image is a copyvio, that is a separate issue entirely.)
*::::::{{tq|This basically happened, and is the origin of WP:NOTGALLERY.}} That is not the same thing. User-generated images that illustrate the subject are not prohibited by ]. Misplaced Pages is a host of encyclopedic content, and user-generated images can have encyclopedic content. ] (]) 02:41, 7 January 2025 (UTC)
*:::::::Images are way more complex than text. Trying to compare them in the same way is a very dangerous simplification. '']'' (] — ]) 02:44, 7 January 2025 (UTC)
*::::::::Assume only non-free images exist of a person. An illustrator refers to those non-free images and produces a painting. From that painting, you see a person who looks like the person in the non-free photographs. The image is verified as resembling the person. That is a simplification, but to call it "dangerous" is disingenuous at best. The process for challenging the image is clear. Someone who wants to challenge the veracity of the image would just need to point to details that do not align. For instance, "he does not typically have blue hair" or "he does not have a scar." That is what we already do, and it does not come up much because it would be weird to deliberately draw an image that looks nothing like the person. Additionally, someone who does not like the image for aesthetic reasons rather than encyclopedic ones always has the option of sourcing a photograph some other way like permission, fair use, or taking a new one themself. This is not an intractable problem. ] (]) 02:57, 7 January 2025 (UTC)
*:::::::::So a photorealistic AI-generated image would be considered acceptable until someone identifies a "big enough" difference? How is that anything close to ethical? An portrait that's got an extra mole or slightly wider nose bridge or lacks a scar is still ''not an image of the person'' regardless of whether random Misplaced Pages editors notice. And while I don't think user-generated non-photorealistic images should ever be used on biographies either, at least those can be traced back to a human who is ultimately responsible for the depiction, who can point to the particular non-free images they used as references, and isn't liable to average out details across all time periods of the subject. And that's not even taking into account the copyright issues. ] (]) 22:52, 7 January 2025 (UTC)
*::::::::::{{+1}} to what JoelleJay said. The problem is that AI-generated images are simulations trying to match existing images, sometimes, yes, with an impressive degree of accuracy. But they will always be inferior to a human-drawn painting that's ''trying to depict the person''. We're a human encyclopedia, and we're built by humans doing human things and sometimes with human errors. '']'' (] — ]) 23:18, 7 January 2025 (UTC)
*::::::::::You can't just raise this to an "ethical" issue by saying the word "ethical." You also can't just invoke copyright without articulating an actual copyright issue; we are not discussing copyvio. Everyone agrees that a photo with an actual copyvio in it is subject to that policy.
*::::::::::But to address your actual point: Any image—any ''photo''—beneath the resolution necessary to depict the mole would be missing the mole. Even with photography, we are never talking about science-fiction images that perfectly depict every facet of a person in an objective sense. We are talking about equipment that creates an approximation of reality. The same is true of illustrations and AI imagery.
*::::::::::Finally, a human being ''is'' responsible for the contents of the image because a human is selecting it and is responsible for correcting any errors. The result is an image that someone is choosing to use because they believe it is an appropriate likeness. We should acknowledge that human decision and evaluate it naturally—''Is it an appropriate likeness?'' ] (]) 10:20, 8 January 2025 (UTC)
*:::::::::::(Second comment because I'm on my phone.) I realize I should also respond to this in terms of additive information. What people look like is not static in the way your comment implies. Is it inappropriate to use a photo because they had a zit on the day it was taken? Not necessarily. Is an image inappropriate because it is taken at a bad angle that makes them look fat? Judging by the prolific ComicCon photographs (where people seem to make a game of choosing the worst-looking options; seriously, it's really bad), not necessarily. Scars and bruises exist and then often heal over time. The standard for whether an image with "extra" details is acceptable would still be based on whether it comports acceptably with other images; we literally do what you have capriciously described as "unethical" and supplement it with our compassionate desire to not deliberately embarrass BLPs. (The ComicCon images aside, I guess.) So, no, I would not be a fan of using images that add prominent scars where the subject is not generally known to have one, but that is just an unverifiable fact that does not belong in a Misplaced Pages image. Simple as. ] (]) 10:32, 8 January 2025 (UTC)
*:::::We don't evaluate the reliability of a source solely by comparing it to other sources. For example, there is an ongoing discussion at the baseball WikiProject talk page about the reliability of a certain web site. It lists no authors nor any information on its editorial control policy, so we're not able to evaluate its reliability. The reliability of all content being used as a source, including images, needs to be considered in terms of its provenance. ] (]) 23:11, 7 January 2025 (UTC)
* Can you note in your !vote whether AI-generated images (generated via text prompts/text-to-image models) that are ''not'' photo-realistic / hyper-realistic in style are okay to use to depict BLP subjects? For example, see the image to the right, which was ] then ] from his article: ] by ]]] {{pb}} Pinging people who !voted No above: ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ], ] --- ] (]) 03:55, 3 January 2025 (UTC) {{clear}}
*:Still no, I thought I was clear on that but we should not be using AI-generated images in articles for anything besides representing the concept of AI-generated images, or if an AI-generated image is notable or irreplaceable in its own right -- e.g, a musician uses AI to make an album cover.
*:(this isn't even a good example, it looks more like ])
*:] (]) 04:07, 3 January 2025 (UTC)
*:Was I unclear? ''No'' to all of them. ] (]) 04:13, 3 January 2025 (UTC)
*:Still '''no''', because carving out that type of exception will just lead to arguments down the line about whether a given image is too realistic. <span class="nowrap">—] (] | ])</span> 04:24, 3 January 2025 (UTC)
*:I still think '''no'''. My opposition isn't just to the fact that AI images are misinformation, but also that they essentially serve as a loophole for getting around Enwiki's image use policy. To know what somebody looks like, an AI generator needs to have images of that person in its dataset, and it draws on those images to generate a derivative work. If we have no free images of somebody and we use AI to make one, that's just using a fair use copyrighted image but removed by one step. The image use policy prohibits us from using fair use images for BLPs so I don't think we should entertain this loophole. If we ''do'' end up allowing AI images in BLPs, that just disqualifies the rationale of not allowing fair use in the first place. ] (]) 04:40, 3 January 2025 (UTC)
*:'''No''' those are not okay, as this will just cause arguments from people saying a picture is ''obviously'' AI-generated, and that it is therefore appropriate. As I mentionned above, there are some exceptions to this, which Gnomingstuff perfectly describes. Fake sketches/cartoons are not appropriate and provide little encyclopedic value. ] (]) 05:27, 3 January 2025 (UTC)
*:'''No''' to this as well, with the same carveout for individual images that have received notable discussion. Non-photorealistic AI images are going to be no more verifiable than photorealistic ones, and on top of that will often be lower-quality as images. ] (] • ]) 05:44, 3 January 2025 (UTC)
*:Thanks for the ping, yes I can, the answer is no. ] (]) 07:31, 3 January 2025 (UTC)
*:'''No''', and that image should be deleted before anyone places it into a mainspace article. Changing the RfC intro long after its inception seems a second bite at an apple that's not aged well. ] (]) 09:28, 3 January 2025 (UTC)
*::The RfC question has not been changed; another editor was the RfC question did not make a distinction between photorealistic/non-photorealistic AI-generated images, so I had to add and ping the editors who'd voted !No to clarify things. It has only been 3 days; there's still 27 more days to go. ] (]) 11:18, 3 January 2025 (UTC)
*:::Also answering '''No''' to this one per all the arguments above. "It has only been 3 days" is not a good reason to change the RfC question, especially since many people have already !voted and the "30 days" is mostly indicative rather than an actual deadline for a RfC. ] (] · ]) 14:52, 3 January 2025 (UTC)
*::::The RfC question hasn't been changed; see my response to Zaathras below. ] (]) 15:42, 3 January 2025 (UTC)
*:No, that's even a worse possible approach.<span id="Masem:1735910695864:WikipediaFTTCLNVillage_pump_(policy)" class="FTTCmt"> — ] (]) 13:24, 3 January 2025 (UTC)</span>
*:'''No'''. We're the human encyclopedia. We should have images drawn or taken by real humans who are trying to depict the ''subject'', not by machines trying to simulate an image. Besides, the given example is horribly drawn. '']'' (] — ]) 15:03, 3 January 2025 (UTC)
*:I like these even less than the photorealistic ones... This falls into the same basket for me: if we wouldn't let a random editor who drew this at home using conventional tools add it to the article why would we let a random editor who drew this at home using AI tools at it to the article? (and just to be clear the AI generated image of Germán Larrea Mota-Velasco is not recognizable as such) ] (]) 16:06, 3 January 2025 (UTC)
*:I said *NO*. ] (]) 10:37, 4 January 2025 (UTC)
*:'''No''' Having such images as said above means the AI had to use copyrighted pictures to create it and we shouldn't use it. --] (]) 01:12, 5 January 2025 (UTC)
*:Still '''no'''. If for no other reason than that it's a bad precedent. As others have said, if we make one exception, it will just lead to arguments in the future about whether something is "realistic" or not. I also don't see why we would need cartoon/illustrated-looking AI pictures of people in BLPs. ] (]) 20:43, 6 January 2025 (UTC)
*'''Absolutely not'''. These images are based on whatever the AI could find on the internet, with little to no regard for copyright. Misplaced Pages is better than this. ] (]) 10:16, 3 January 2025 (UTC)
*'''Comment''' The RfC question should not have been fiddled with, esp. for such a minor argument that the complai9nmant could have simply included in their own vote. I have no need to re-confirm my own entry. ] (]) 14:33, 3 January 2025 (UTC)
*:The RfC question hasn't been modified; I've only added a clarifying that these images can either be photorealistic in style or non-photorealistic in style. I pinged all the !No voters to make them aware. I could remove the Note if people prefer that I do (but the original RfC question is the ''exact same'' as it is now, so I don't think the addition of the Note makes a whole ton of difference). ] (]) 15:29, 3 January 2025 (UTC)
*'''No''' At this point it feels redundant, but I'll just add to the horde of responses in the negative. I don't think we can fully appreciate the issues that this would cause. The potential problems and headaches far outweigh whatever little benefit might come from AI images for BLPs. ]] 21:34, 3 January 2025 (UTC)
*'''Support temporary blanket ban''' with a posted expiration/requred rediscussion date of no more than two years from closing. AI as the term is currently used is very, very new. Right now these images would do more harm than good, but it seems likely that the culture will adjust to them. ] (]) 23:01, 3 January 2025 (UTC)
*'''No'''. Misplaced Pages is made ''by'' and ''for'' humans. I don't want to become . Adding an AI-generated image to a page whose topic isn't about generative AI makes me feel insulted. ] (]) 00:03, 4 January 2025 (UTC)
*'''No'''. Generative AI may have its place, and it may even have a place on Misplaced Pages in some form, but that place isn't in BLPs. There's no reason to use images of someone that do not exist over a real picture, or even something like a sketch, drawing, or painting. Even in the absence of pictures or human-drawn/painted images, I don't support using AI-generated images; they're not really pictures of the person, after all, so I can't support using them on articles of people. Using nothing would genuinely be a better choice than generated images. ] <span style="font-weight:bold">|</span> ] 01:07, 4 January 2025 (UTC)
*'''No''' due to reasons of copyright (AI harvests copyrighted material) and verifiability. ] <small>(])</small> 18:12, 4 January 2025 (UTC)
*'''No.''' Even if you are willing to ignore the inherently fraught nature of using AI-generated ''anything'' in relation to BLP subjects, there is simply little to no benefit that could possibly come from trying something like this. There's no guarantee the images will actually look like the person in question, and therefore there's no actual context or information that the image is providing the reader. What a baffling proposal. ] (]) 19:53, 4 January 2025 (UTC)
*:{{tpq|There's no guarantee the images will actually look like the person in question}} there is no guarantee ''any'' image will look like the person in question. When an image is not a good likeness, regardless of why, we don't use it. When am image is a good likeness we consider using it. Whether an image is AI-generated or not it is completely independent of whether it is a good likeness. There are also reason other then identification why images are used on BLP-articles. ] (]) 20:39, 4 January 2025 (UTC)
*Foreseeably there may come a time when people's official portraits are AI-enhanced. That time might not be very far in the future. Do we want an exception for official portraits?—] <small>]/]</small> 01:17, 5 January 2025 (UTC)
*:This subsection is about purely AI-generated works, not about AI-enhanced ones. ] (] · ]) 01:23, 5 January 2025 (UTC)
*'''No.''' Per Cremastra, "We should have images drawn or taken by real humans who are trying to depict the ''subject''," - ] (]) 02:12, 5 January 2025 (UTC)
*'''Yes''', depending on specific case. One can use drawings by artists, even such as ]. The latter is an intentional distortion, one could say an intentional misinformation. Still, such images are legitimate on many pages. Or consider numerous images of ]. How realiable are they? I am not saying we must deliberatly use AI images on all pages, but they may be fine in some cases. Now, speaking on "medical articles"... One might actually use the AI generated images of certain biological objects like proteins or organelles. Of course a qualified editorial judgement is always needed to decide if they would improve a specific page (frequently they would not), but making a blanket ban would be unacceptable, in my opinion. For example, the images of protein models generatated by ] would be fine. The AI-generated images of biological membranes I saw? I would say no. It depends. ] (]) 02:50, 5 January 2025 (UTC) {{pb
}}This is complicated of course. For example, there are tools that make an image of a person that (mis)represents him as someone much better and clever than he really is in life. That should be forbidden as an advertisement. This is a whole new world, but I do not think that a blanket rejection would be appropriate. ] (]) 03:19, 5 January 2025 (UTC)
* '''No''', I think there's legal and ethical issues here, especially with the current state of AI. ] ] 03:38, 5 January 2025 (UTC)
*'''No''': Obviously, we shouldn't be using AI images to represent anyone. ] (]) 05:31, 5 January 2025 (UTC)
*'''No''' Too risky for BLP's. Besides if people want AI generated content over editor made content, we should make it clear they are in the wrong place, and readers should be given no doubt as to our integrity, sincerity and effort to give them our best, not a program's. ] (]) 14:51, 5 January 2025 (UTC)
*'''No''', as AI's grasp on the Internet takes hold stronger and stronger, it's important Misplaced Pages, as the online encyclopedia it sets out to be, remains factual and real. Using AI images on Wiki would likely do more harm than good, further thinning the boundaries between what's real and what's not. – ''']''' <sub>(]) (])</sub> 16:52, 5 January 2025 (UTC)
*'''No''', not at the moment. I think it will hard to avoid portraits that been enhanced by AI, as it already been on-going for a number of years and there is no way to avoid it, but I don't want arbitary generated AI portraits of any type. '''<span style="text-shadow:7px 7px 8px black; font-family:Papyrus">]<sup>]</sup></span>''' 20:19, 5 January 2025 (UTC)
*'''No for natural images (e.g. photos of people)'''. Generative AI by itself is not a reliable source for facts. In principle, generating images of people and directly sticking them in articles is no different than generating text and directly sticking it in articles. In practice, however, generating images is worse: Text can at least be discussed, edited, and improved afterwards. In contrast, we have significantly less policy and fewer rigorous methods of discussing how AI-generated images of natural objects should be improved (e.g. "make his face slightly more oblong, it's not close enough yet"). Discussion will devolve into hunches and gut feelings about the fidelity of images, all of which essentially fall under WP:OR. ] (]) 20:37, 5 January 2025 (UTC)
*'''No''' I'm appalled that even a small minority of editors would support such an idea. We have enough credibility issues already; using AI-generated images to represent real people is not something that a real encyclopedia should even consider. ] (]) 22:26, 5 January 2025 (UTC)
*'''No''' I understand the comparison to using illustrations in BLP articles, but I've always viewed that as less preferable to no picture in all honestly. Images of a person are typically presented in context, such as a performer on stage, or a politician's official portrait, and I feel like there would be too many edge cases to consider in terms of making it clear that the photo is AI generated and isn't representative of anything that the person specifically did, but is rather an approximation. ] (]) 06:50, 6 January 2025 (UTC)
*'''No''' - Too often the images resemble caricatures. Real caricatures may be included in articles if the caricature (e.g., political cartoon) had ] and is attributed to the artist. Otherwise, representations of living persons should be real representations taken with photographic equipment. ] (]) 02:31, 7 January 2025 (UTC)
*:So you will be arguing for the removal of the lead images at ], ], etc. then? ] (]) 06:10, 7 January 2025 (UTC)
*::At this point you're making bad-faith "BY YOUR LOGIC" arguments. You're better than that. Don't do it. ] (]) 19:18, 7 January 2025 (UTC)
*'''Strong no''' per bloodofox. —] (]'''-''']) 03:32, 7 January 2025 (UTC)
:'''No''' for AI-generated BLP images ] (]) 21:40, 7 January 2025 (UTC)
::::::I did make the change by moving the criticism down the page. And I was shocked!!! It lasted almost 3 hours and the person who reverted it was even polite in his comments on the talk page. Maybe there is hope after all. ] 18:15, 9 March 2007 (UTC)
*'''No''' - Not only is this effectively guesswork that usually includes unnatural artefacts, but worse, it is also based on unattributed work of photographers who didn't release their work into public domain. I don't care if it is an open legal loophole somewhere, IMO even doing away with the fair use restriction on BLPs would be morally less wrong. I suspect people on whose work LLMs in question were trained would also take less offense to that option. <span style="font-family:Garamond,Palatino,serif;font-size:115%;background:-webkit-linear-gradient(red,red,red,blue,blue,blue,blue);-webkit-background-clip:text;-webkit-text-fill-color:transparent">] ]</span> 23:25, 7 January 2025 (UTC)
*'''No''' – ] says that {{tq|Non-free content should not be used when a freely licensed file that serves the same purpose can reasonably be expected to be uploaded, as is the case for almost all portraits of living people.}} While AI images may not be considered copyrightable, it still be a copyright violation if the output resembles other, copyrighted images, pushing the image towards NFC. At the very least, I feel the use of non-free content to generate AI images violates the spirit of the NFC policy. (I'm assuming copyrighted images of a person are used to generate an AI portrait of them; if free images of that person were used, we should just use those images, and if ''no'' images of the person were used, how on Earth would we trust the output?) ] (]) 02:43, 8 January 2025 (UTC)
*'''No''', AI images should not be permitted on Misplaced Pages at all. ] (]) 11:27, 8 January 2025 (UTC)
{{Archive bottom}}
===Expiration date?===
:::::::Yup, the Misplaced Pages "process" mostly works. Sometimes not as smoothly or quickly as we'd like, but on the main it does work. ] 20:50, 9 March 2007 (UTC)
"AI," as the term is currently used, is very new. It feels like large language models and the type of image generators under discussion just got here in 2024. (Yes, I know it was a little earlier.) The culture hasn't completed its initial response to them yet. Right now, these images do more harm than good, but that may change. Either we'll come up with a better way of spotting hallucinations or the machines will hallucinate less. Their copyright status also seems unstable. I suggest that any ban decided upon here have some expiration date or required rediscussion date. Two years feels about right to me, but the important thing would be that the ban has a number on it. ] (]) 23:01, 3 January 2025 (UTC)
*No need for any end-date. If there comes a point where consensus on this changes, then we can change any ban then. ] (]) 05:27, 5 January 2025 (UTC)
*An end date is a positive suggestion. Consensus systems like Misplaced Pages's are vulnerable to half-baked precedential decisions being treated as inviolate. With respect, this conversation does not inspire confidence that this policy proposal's consequences are well-understood at this time. If Misplaced Pages goes in this direction, it should be labeled as primarily reactionary and open to review at a later date. ] (]) 10:22, 5 January 2025 (UTC)
*Agree with FOARP, '''no need for an end date'''. If something significantly changes (e.g. reliable sources/news outlets such as the ''New York Times'', BBC, AP, etc. start using text-to-image models to generate images of living people for their own articles) then this topic can be revisited later. Editors will have to go through the usual process of starting a new discussion/proposal when that time comes. ] (]) 11:39, 5 January 2025 (UTC)
*:Seeing as this discussion has not touched at all on what other organizations may or may not do, it would not be accurate to describe any consensus derived from this conversation in terms of what other organizations may or may not be doing. That is, there has been no consensus that we ought to be looking to the New York Times as an example. Doing so would be inadvisable for several reasons. For one, they have sued an AI company over semi-related issues and they have teams explicitly working on what the future of AI in news ought to look like, so they have some investment in what the future of AI looks like and they are explicitly trying to shape its norms. For another, if they did start to use AI in a way that may be controversial, they would have no positive reason to disclose that and many disincentives. They are not a neutral signal on this issue. Misplaced Pages should decide for itself, preferably doing so while not disrupting the ability of people to continue creating user-generated images. ] (]) 03:07, 6 January 2025 (UTC)
* ] on an indefinite basis, if something changes. An arbitrary sunset date doesn't seem much use. ] (]) 03:15, 6 January 2025 (UTC)
* No need per others. Additionally, if practices change, it doesn't mean editors will decide to follow new practices. As for the technology, it seems the situation has been fairly stable for the past two years: we can detect some fakes and hallucinations immediately, many more in the past, but certainly not all retouched elements and all generated photos available right now, even if there was a readily accessible tool or app that enabled ordinary people to reliably do so.
:Through the history, art forgeries have been fairly reliably detected, but rarely quickly. Relatedly, I don't see why the situation with AI images would change in the next 24 months or any similar time period. <span style="font-family:Garamond,Palatino,serif;font-size:115%;background:-webkit-linear-gradient(red,red,red,blue,blue,blue,blue);-webkit-background-clip:text;-webkit-text-fill-color:transparent">] ]</span> 22:17, 9 January 2025 (UTC)
== Should ] include mention of AI-generated comments? ==
One must remember that unlike the other religions mentioned, Scientology is run (and closely managed) by a single organisation. This means that controversies about the business-policies of the Church of Scientology can reflect upon the religion itself. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 06:18, 9 March 2007 (UTC)
Using AI to write your comments in a discussion makes it difficult for others to assume that you are discussing in good faith, rather than trying to use AI to argue someone into exhaustion (see example of someone using AI in their replies ). More fundamentally, ] can't apply to the AI itself as AI lacks intentionality, and it is difficult for editors to assess how much of an AI-generated comment reflects the training of the AI vs. the actual thoughts of the editor.
:I think that Scientology's negative points should all be reported here. I was just pointing out some of the problems with the way it is handled compared to other groups. ] 13:48, 9 March 2007 (UTC)
Should ] be addended to include that using AI to generate your replies in a discussion runs counter to demonstrating good faith? ] (]) 00:23, 2 January 2025 (UTC)
::hmmm....What might work is for all Scientology articles to be locked as they are. This would free up a lot of editors to do more useful things here. ] 17:48, 10 March 2007 (UTC)
* '''Yes''', I think this is a good idea. ] (]) 00:39, 2 January 2025 (UTC)
==Publication of magic methods (aka. Exposure)==
Publication of methods behind magic tricks, aka ], is a source of recurring controversy. There seem to have been various attempts to propose a policy but all have apparently fizzled out inconclusively (as far as I can tell from following trails from one page to another). I've recently started making contributions to the ] but it has become apparent to me that there's a serious risk these efforts might get wrecked by an edit war. In an effort to avert that I'm trying to re-start debate in the hope that we can end up with some official guidelines. I've set out my thoughts on the Magic WikiProject discussion page - ]
:'''No'''. As with all the other concurrent discussions (how many times do we actually need to discuss the exact same FUD and scaremongering?) the problem is not AI, but rather inappropriate use of AI. What we need to do is to (better) explain what we actually want to see in discussions, not vaguely defined bans of swathes of technology that, used properly, can aid communication. ] (]) 01:23, 2 January 2025 (UTC)
] 14:35, 10 March 2007 (UTC)Circusandmagicfan
::Note that this topic is discussing using AI to ''generate'' replies, as opposed to using it as an aid (e.g. asking it to edit for grammar, or conciseness). As the above concurrent discussion demonstrates, users are already using AI to generate their replies in AfD, so it isn't scaremongering but an actual issue.
::] also does not ban anything ("Showing good faith is not required"), but offers general advice on demonstrating good faith. So it seems like the most relevant place to include mention of the community's concerns regarding AI-generated comments, without outright banning anything. ] (]) 01:32, 2 January 2025 (UTC)
:I don't think it is possible for WP to have a policy against this. I don't plan on reading the articles myself. ] 17:46, 10 March 2007 (UTC)
:::And as pointed out, multiple times in those discussions, different people understand different things from the phrase "AI-generated". The community's concern is not AI-generated comments, but comments that do not clearly and constructively contribute to a discussion - ''some'' such comments are AI-generated, some are not. This proposal would, just as all the other related ones, cause actual harm when editors falsely accuse others of using AI (and this ''will'' happen). ] (]) 02:34, 2 January 2025 (UTC)
::::Nobody signed up to argue with bots here. If you're pasting someone else's comment into a prompt and asking the chatbot to argue against that comment and just posting it in here, that's a real problema and absolutely should not be acceptable. ] (]) 03:31, 2 January 2025 (UTC)
:::::Thank you for the assumption of bad faith and demonstrating one of my points about the harm caused. Nobody is forcing you to engage with bad-faith comments, but whether something is or is not bad faith needs to be determined by its content not by its method of generation. Simply using an AI demonstrates neither good faith nor bad faith. ] (]) 04:36, 2 January 2025 (UTC)
:::::I don't see why we have any particular to reason to suspect a respected and trustworthy editor of using AI. '']'' (] — ]) 14:31, 2 January 2025 (UTC)
::::I'm one of those people who clarified the difference between AI-generated vs. edited, and such a difference could be made explicit with a note. Editors are already accusing others of using AI. Could you clarify how you think addressing AI in ] would cause actual harm? ] (]) 04:29, 2 January 2025 (UTC)
:::::By encouraging editors to accuse others of using AI, by encouraging editors to dismiss or ignore comments because they suspect that they are AI-generated rather than engaging with them. @] has already encouraged others to ignore my arguments in this discussion because they suspect I might be using an LLM and/or be a bot (for the record I'm neither). ] (]) 04:33, 2 January 2025 (UTC)
::::::I think {{u|bloodofox}}'s ] was about "you" in the rhetorical sense, not "you" as in Thryduulf. ] (]) 11:06, 2 January 2025 (UTC)
:::::Given your relentlessly pro-AI comments here, it seems that you'd be A-OK with just chatting with a group of chatbots here — or leaving the discussion to them. However, most of us clearly are not. In fact, I would immediately tell someone to get lost were it confirmed that indeed that is what is happening. I'm a human being and find the notion of wasting my time with chatbots on Misplaced Pages to be incredibly insulting and offensive. ] (]) 04:38, 2 January 2025 (UTC)
::::::My comments are neither pro-AI nor anti-AI, indeed it seems that you have not understood pretty much anything I'm saying. ] (]) 04:43, 2 January 2025 (UTC)
:::::::Funny, you've done nothing here but argue for more generative AI on the site and now you seem to be arguing to let chatbots run rampant on it while mocking anyone who doesn't want to interface with chatbots on Misplaced Pages. Hey, why not just sell the site to Meta, am I right? ] (]) 04:53, 2 January 2025 (UTC)
::::::::I haven't been arguing for more generative AI on the site. I've been arguing against banning it on the grounds that such a ban would be unclear, unenforceable, wouldn't solve any problems (largely because whether something is AI or not is completely irrelevant to the matter at hand) but would instead cause harm. Some of the issues identified are actual problems, but AI is not the cause of them and banning AI won't fix them.
::::::::I'm not mocking anybody, nor am I advocating to {{tpq|let chatbots run rampant}}. I'm utterly confused why you think I might advocate for selling Misplaced Pages to Meta (or anyone else for that matter)? Are you actually reading anything I'm writing? You clearly are not understanding it. ] (]) 05:01, 2 January 2025 (UTC)
:::::::::So we're now in 'everyone else is the problem, not me!' territory now? Perhaps try communicating in a different way because your responses here are looking very much like the typical AI apologetics one can encounter on just about any contemporary LinkedIn thread from your typical FAANG employee. ] (]) 05:13, 2 January 2025 (UTC)
::::::::::No, this is not a {{tpq|everyone else is the problem, not me}} issue because most other people appear to be able to understand my arguments and respond to them appropriately. Not everybody agrees with them, but that's not an issue.
::::::::::I'm not familiar with Linkedin threads (I don't use that platform) nor what a "FAANG employee" is (I've literally never heard the term before now) so I have no idea whether your characterisation is a compliment or a personal attack, but given your comments towards me and others you disagree with elsewhere I suspect it's closer to the latter.
::::::::::AI is a tool. Just like any other tool it can be used in good faith or in bad faith, it can be used well and it can be used badly, it can be used in appropriate situations and it can be used in inappropriate situations, the results of using the tool can be good and the results of using the tool can be bad. Banning the tool inevitably bans the good results as well as the bad results but doesn't address the reasons why the results were good or bad and so does not resolve the actual issue that led to the bad outcomes. ] (]) 12:09, 2 January 2025 (UTC)
:::::::::::In the context of generating comments to other users though, AI is much easier to use for bad faith than for good faith. LLMs don't understand Misplaced Pages's policies and norms, and so are hard to utilize to generate posts that productively address them. By contrast, bad actors can easily use LLMs to make low quality posts to waste people's time or wear them down.
:::::::::::In the context of generating images, or text for articles, it's easy to see how the vast majority of users using AI for those purposes is acting in good faith as these are generally constructive tasks, and most people making bad faith changes to articles are either obvious vandals who won't bother to use AI because they'll be reverted soon anyways, or trying to be subtle (povpushers) in which case they tend to want to carefully write their own text into the article.
:::::::::::It's true that AI "is just a tool", but when that tool is much easier to use for bad faith purposes (in the context of discussions) then it raises suspicions about why people are using it. ] (]) 22:44, 2 January 2025 (UTC)
::::::::::::{{tq|LLMs don't understand Misplaced Pages's policies and norms}} They're not designed to "understand" them since the policies and norms were designed for human cognition. The fact that AI is used rampantly by people acting in bad faith on Misplaced Pages does not inherently condemn the AI. To me, it shows that it's too easy for vandals to access and do damage on Misplaced Pages. Unfortunately, the type of vetting required to prevent that at the source would also potentially require eliminating IP-editing, which won't happen. <sub>Duly signed,</sub> ''']'''-''<small>(])</small>'' 14:33, 15 January 2025 (UTC)
:::::::You mentioned "FUD". That acronym, "fear, uncertainty and doubt," is used in precisely two contexts: pro-AI propagadizing and persuading people who hold memecoin crypto to continue holding it. Since this discussion is not about memecoin crypto that would suggest you are using it in a pro-AI context. I will note, fear, uncertainty and doubt is not my problem with AI. Rather it's anger, aesthetic disgust and feeling disrespected when somebody makes me talk to their chatbot. ] (]) 14:15, 14 January 2025 (UTC)
::::::::{{tpq|That acronym, "fear, uncertainty and doubt," is used in precisely two contexts}} is simply
::::::::FUD both predates AI by many decades (my father introduced me to the term in the context of the phrase "nobody got fired for buying ]", and the context of that was ] computer systems in the 1980s if not earlier. FUD is also used in many, many more contexts that just those two you list, including examples by those opposing the use of AI on Misplaced Pages in these very discussions. ] (]) 14:47, 14 January 2025 (UTC)
::::::::{{tpq|That acronym, "fear, uncertainty and doubt," is used in precisely two contexts}} is factually incorrect.
::::::::FUD both predates AI by many decades (indeed if you'd bothered to read the ] article you'd learn that the concept was first recorded in 1693, the exact formulation dates from at least the 1920s and the use of it in technology concepts originated in 1975 in the context of mainframe computer systems. That its use, eve in just AI contexts, is limited to pro-AI advocacy is ludicrous (even ignoring things like ]), examples can be found in these sprawling discussions from those opposing AI use on Misplaced Pages. ] (]) 14:52, 14 January 2025 (UTC)
:'''Not really''' – I agree with Thryduulf's arguments on this one. Using AI to help tweak or summarize or "enhance" replies is of course not bad faith – the person is trying hard. Maybe English is their second language. Even for replies 100% AI-generated the user may be an ESL speaker struggling to remember the right words (I always forget 90% of my French vocabulary when writing anything in French, for example). In this case, I don't think we should make a ''blanket'' assumption that using AI to generate comments is not showing good faith. '']'' (] — ]) 02:35, 2 January 2025 (UTC)
::As already stated in the discussion you linked to, I agree that ] is key for reducing ]. Once it the information is already out there, it is fair game. --] (<small>] ;; ]</small>) 18:11, 10 March 2007 (UTC)
*'''Yes''' because generating walls of text is not good faith. People "touching up" their comments is also bad (for starters, if you lack the English competency to write your statements in the first place, you probably lack the competency to tell if your meaning has been preserved or not). Exactly ''what'' AGF should say needs work, but something needs to be said, and <s>AGF</s>DGF is a good place to do it. ] (]) 02:56, 2 January 2025 (UTC)
*:Not all walls of text are generated by AI, not all AI generated comments are walls of text. Not everybody who uses AI to touch up their comments lacks the competencies you describe, not everybody who does lack those competencies uses AI. It is not always possible to tell which comments have been generated by AI and which have not. This proposal is not particularly relevant to the problems you describe. ] (]) 03:01, 2 January 2025 (UTC)
:::Someone has to ask: Are you generating all of these pro-AI arguments using ChatGPT? It'd explain a lot. If so, I'll happily ignore any and all of your contributions, and I'd advise anyone else to do the same. We're not here to be flooded with LLM-derived responses. ] (]) 03:27, 2 January 2025 (UTC)
::::That you can't tell whether my comments are AI-generated or not is one of the fundamental problems with these proposals. For the record they aren't, nor are they pro-AI - they're simply anti throwing out babies with bathwater. ] (]) 04:25, 2 January 2025 (UTC)
:::::I'd say it also illustrates the serious danger: We can no longer be sure that we're even talking to other people here, which is probably the most notable shift in the history of Misplaced Pages. ] (]) 04:34, 2 January 2025 (UTC)
::::::How is that a "serious danger"? If a comment makes a good point, why does it matter whether ti was AI generated or not? If it doesn't make a good point, why does it matter if it was AI generated or not? How will these proposals resolve that "danger"? How will they be enforceable? ] (]) 04:39, 2 January 2025 (UTC)
:::::::Misplaced Pages is made for people, by people, and I like most people will be incredibly offended to find that we're just playing some kind of LLM pong with a chatbot of your choice. You can't be serious. ] (]) 04:40, 2 January 2025 (UTC)
::::::::You are entitled to that philosophy, but that doesn't actually answer any of my questions. ] (]) 04:45, 2 January 2025 (UTC)
:::::::"why does it matter if it was AI generated or not?"
:::::::Because it takes little effort to post a lengthy, low quality AI-generated post, and a lot of effort for human editors to write up replies debunking them.
:::::::"How will they be enforceable? "
:::::::] isn't meant to be enforced. It's meant to explain to people how they can demonstrate good faith. Posting replies to people (who took the time to write them) that are obviously AI-generated harms the ability of those people to assume good faith. ] (]) 05:16, 2 January 2025 (UTC)
:The linked "example of someone using AI in their replies" appears – to me – to be a non-AI-generated comment. I think I preferred the allegedly AI-generated comments from that user (]). The AI was at least superficially polite. ] (]) 04:27, 2 January 2025 (UTC)
::Obviously the person screaming in all caps that they use AI because they don't want to waste their time arguing is not using AI for that comment. Their first post calls for the article to be deleted for not "" and "merely" reiterating what other sources have written.
::Yes, after a human had wasted their time explaining all the things wrong with its first post, then the bot was able to write a second post which ''looks'' ok. Except it only superficially ''looks'' ok, it doesn't actually accurately describe the articles. ] (]) 04:59, 2 January 2025 (UTC)
:::So long as a source is cited (and it's not just "I know this"), then, 1: The information is obviously already available to the public, and 2: It's attributable. ] censored, including for spoilers. ] <small><sup>] ]</sup></small> 18:19, 10 March 2007 (UTC)
:::Multiple humans have demonstrated in these discussions that humans are equally capable of writing posts which superficially ''look'' OK but don't actually accurately relate to anything they are responding to. ] (]) 05:03, 2 January 2025 (UTC)
::::But I can assume that everyone here is acting in good faith. I can't assume good faith in the globally-locked sock puppet spamming AfD discussions with low effort posts, whose bot is just saying whatever it can to argue for the deletion of political pages the editor doesn't like. ] (]) 05:09, 2 January 2025 (UTC)
:::::True, but I think that has more to do with the "globally-locked sock puppet spamming AfD discussions" part than with the "some of it might be " part. ] (]) 07:54, 2 January 2025 (UTC)
::::::All of which was discovered because of my suspicions from their inhuman, and meaningless replies. "Reiteration isn't the problem; redundancy is," maybe sounds pithy in a vacuum, but this was written in reply to me stating that we aren't supposed to be doing OR but reiterating what the sources say.
::::::"Your criticism feels overly prescriptive, as though you're evaluating this as an academic essay" also ''sounds good'', until you realize that the bot is actually criticizing its own original post.
::::::The fact that my suspicions about their good faith were ultimately validated only makes it even harder for me to assume good faith in users who sound like ChatGPT. ] (]) 08:33, 2 January 2025 (UTC)
:::::::I wonder if we need some other language here. I can understand feeling like this is a bad interaction. There's no sense that the person cares; there's no feeling like this is a true interaction. A contract lawyer would say that there's no ], and there can't be, because there's no mind in the AI, and the human copying from the AI doesn't seem to be interested in engaging their brain.
:::::::But... do you actually think they're doing this for the purpose of ''intentionally'' harming Misplaced Pages? Or could this be explained by other motivations? ] – or to anxiety, insecurity (will they hate me if I get my grammar wrong?), incompetence, negligence, or any number of other "understandable" (but still something ]- and even block-worthy) reasons. ] (]) 08:49, 2 January 2025 (UTC)
::::::::The ] has a header at the top asking people not to template them because it is "impersonal and disrespectful", instead requesting "please take a moment to write a comment below '''in your own words'''"
::::::::Does this look like acting in good faith to you? Requesting other people write personalized responses to them while they respond with an LLM? Because it looks to me like they are trying to waste other people's time. ] (]) 09:35, 2 January 2025 (UTC)
:::::::::] means that you assume people aren't deliberately screwing up on purpose. Humans are self-contradictory creatures. I generally do assume that someone who is being hypocritical hasn't noticed their contradictions yet. ] (]) 07:54, 3 January 2025 (UTC)
::::::::::"Being hypocritical" in the abstract isn't the problem, it's the fact that asking people to put effort into their comments, while putting in minimal effort into your own comments appears bad faith, especially when said person says they don't want to waste time writing comments to stupid people. The fact you are arguing AGF for this person is both astounding and disappointing. ] (]) 16:08, 3 January 2025 (UTC)
:::::::::::It feels like there is a lack of reciprocity in the interaction, even leaving aside the concern that the account is a block-evading sock.
:::::::::::But I wonder if you have read AGF recently. The first sentence is "'''Assuming good faith''' ('''AGF''') means assuming that people are not deliberately ''trying'' to hurt Misplaced Pages, even when their actions are harmful."
:::::::::::So we've got some of this (e.g., harmful actions). But do you really believe this person woke up in the morning and decided "My main goal for today is to deliberately hurt Misplaced Pages. I might not be successful, but I sure am going to try hard to reach my goal"? ] (]) 23:17, 4 January 2025 (UTC)
::::::::::::Trying to hurt Misplaced Pages doesn't mean they have to literally think "I am trying to hurt Misplaced Pages", it can mean a range of things, such as "I am trying to troll Wikipedians". A person who thinks a cabal of editors is guarding an article page, and that they need to harass them off the site, may think they are improving Misplaced Pages, but at the least I wouldn't say that they are acting in good faith. ] (]) 23:27, 4 January 2025 (UTC)
:::::::::::::Sure, I'd count that as a case of "trying to hurt Misplaced Pages-the-community". ] (]) 06:10, 5 January 2025 (UTC)
* The issues with AI in discussions is not related to good faith, which is narrowly defined to intent. ] (]) 04:45, 2 January 2025 (UTC)
::::In reply to ] and ], I agree that there shouldn't be a policy against publishing information that Misplaced Pages is free to publish. To an extent I agree that if the information is out there then it's "fair game" - but the exact definition of fair game depends upon various bits of law - and applying policy seems the best way to cover against falling foul of that. I think ] summed up a crucial point well in saying that we need to avoid the situations where it becomes just a case of "I know this". Maybe all that is needed is a clear emphasis of relevant policies on the project page for the Magic WikiProject. And I agree that should include ], which I'd possibly overlooked. Same with ], although hasn't that been incorporated into and superceded by ]?
*:In my mind, they are related inasmuch as it is much more difficult for me to ascertain good faith if the words are eminently not written by the person I am speaking to in large part, but instead generated based on an unknown prompt in what is likely a small fraction of the expected time. To be frank, in many situations it is difficult to avoid the conclusion that the disparity in effort is being leveraged in something less than good faith. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 05:02, 2 January 2025 (UTC)
::::] 09:03, 16 March 2007 (UTC)Circusandmagicfan
*::Assume good faith, don't ascertain! Llm use can be deeply unhelpful for discussions and the potential for mis-use is large, but the most recent discussion I've been involved with where I observed an llm post was responded to by an llm post, I believe both the users were doing this in good faith. ] (]) 05:07, 2 January 2025 (UTC)
*:::All I mean to say is it should be licit that unhelpful LLM use should be something that can be mentioned like any other unhelpful rhetorical pattern. <span style="border-radius:2px;padding:3px;background:#1E816F">]<span style="color:#fff"> ‥ </span>]</span> 05:09, 2 January 2025 (UTC)
== User page issue ==
*::::Sure, but ] doesn't mention any unhelpful rhetorical patterns. ] (]) 05:32, 2 January 2025 (UTC)
*::::The fact that everyone (myself included) defending "LLM use" says "use" rather than "generated", is a pretty clear sign that no one really wants to communicate with someone using "LLM generated" comments. We can argue about bans (not being proposed here), how to know if someone is using LLM, the nuances of "LLM use", etc., but at the very least we should be able to agree that there are concerns with LLM generated replies, and if we can agree that there are concerns then we should be able to agree that somewhere in policy we should be able to find a place to express those concerns. ] (]) 05:38, 2 January 2025 (UTC)
Should we be concerned with icons blocking Misplaced Pages's menu?
*:::::...or they could be saying "use" because "using LLMs" is shorter and more colloquial than "generating text with LLMs"? ] (]) 06:19, 2 January 2025 (UTC)
*::::::Seems unlikely when people justify their use for editing (which I also support), and not for generating replies on their behalf. ] (]) 06:23, 2 January 2025 (UTC)
For an example, see .
*:::::::This is just semantics.
*:::::::For instance, I am OK with someone using a LLM to post a productive comment on a talk page. I am also OK with someone generating a reply with a LLM that is a productive comment to post to a talk page. I am not OK with someone generating text with an LLM to include in an article, and also not OK with someone using a LLM to contribute to an article.
You can scroll to get around it, but where should we draw the line?
*:::::::The only difference between these four sentences is that two of them are more annoying to type than the other two. ] (]) 08:08, 2 January 2025 (UTC)
*::::::::Most people already assume good faith in those making productive contributions. In situations where good faith is more difficult to assume, would you trust someone who uses an LLM to generate all of their comments as much as someone who doesn't? ] (]) 09:11, 2 January 2025 (UTC)
Just curious.
*:::::::::Given that LLM-use is completely irrelevant to the faith in which a user contributes, yes. Of course what amount that actually is may be anywhere between completely and none. ] (]) 11:59, 2 January 2025 (UTC)
*::::::::::LLM-use is relevant as it allows bad faith users to disrupt the encyclopedia with minimal effort. Such a user , as well as started and , all using AI. I had previously been involved in a debate with another sock puppet of theirs, but at that time they didn't use AI. Now it seems they are switching to using an LLM just to troll with minimal effort. ] (]) 21:44, 2 January 2025 (UTC)
''''']'''''20:30, 11 March 2007 (UTC)
*:::::::::::LLMs are a tool that can be used by good and bad faith users alike. Using an LLM tells you nothing about whether a user is contributing in good or bad faith. If somebody is trolling they can be, and should be, blocked for trolling regardless of the specifics of how they are trolling. ] (]) 21:56, 2 January 2025 (UTC)
*::::::::::::A can of spray paint, a kitchen knife, etc., are tools that can be used for good or bad, but if you bring them some place where they have few good uses and many bad uses then people will be suspicious about why you brought them. You can't just assume that a tool in any context is equally harmless. Using AI to generate replies to other editors is more suspicious than using it to generate a picture exemplifying a fashion style, or a description of a physics concept. ] (]) 23:09, 2 January 2025 (UTC)
:That's incredibly annoying - but is the fact that it obscures the menu really a problem? -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 21:03, 11 March 2007 (UTC)
*:::::::::I wouldn't trust anything factual the person would have to say, but I wouldn't assume they were malicious, which is the entire point of ]. ] (]) 16:47, 2 January 2025 (UTC)
::I don't care for it, have seen this used abusively on real pages, and see absolutely no reason why it should be permitted. --] (<small>] ;; ]</small>) 21:07, 11 March 2007 (UTC)
*::::::::::] is not a death pact though. At times you should be suspicious. Do you think that if a user, ''who you already have suspicions of'', is also using an LLM to generate their comments, that that doesn't have any effect on those suspicions? ] (]) 21:44, 2 January 2025 (UTC)
*I suppose you're familiar with the earlier discussion on those fake "you have new messages" boxen? ] 12:06, 13 March 2007 (UTC)
*:::::::::::So… If you suspect that someone is not arguing in good faith… just stop engaging them. If they are creating walls of text but not making policy based arguments, they can be ignored. Resist the urge to respond to every comment… it isn’t necessary to “have the last word”. ] (]) 21:57, 2 January 2025 (UTC)
*:Probably not: ].<br>Transhumanist, see the long thread still at the top of ], which seems to have resulted in this addition: ]. --] 05:23, 15 March 2007 (UTC)
*::::::::::::As the person ] demonstrates, you can't "just stop engaging them". When they then somebody has to engage them in some way. It's not about trying to "have the last word", this is a collaborative project, it generally requires engaging with others to some degree. When someone like the person I linked to above (now banned sock), spams low quality comments across dozens of AfDs, then they are going to waste people's time, and telling others to just not engage with them is dismissive of that. ] (]) 22:57, 2 January 2025 (UTC)
*::It's been respectfully removed. Well, repurposed. And the user with the bouncing ball has removed it as well. All's well in Wikiville. ''''']'''''01:23, 16 March 2007 (UTC)
*:::::::::::::That they've been banned for disruption indicates we can do everything we need to do to deal with bad faith users of LLMs without assuming that everyone using an LLM is doing so in bad faith. ] (]) 00:33, 3 January 2025 (UTC)
*::::::::::::::I don't believe we should assume everyone using an LLM is doing so in bad faith, so I'm glad you think my comment indicates what I believe. ] (]) 01:09, 3 January 2025 (UTC)
== Proposal for a new logo for policy pages ==
;Proposed versions
{| class="messagebox"
|-
| ]
| '''This page is an ] on the English Misplaced Pages.''' It has wide acceptance among editors and is considered a standard that all users should follow. When editing this page, please ensure that your revision reflects ]. When in doubt, discuss first on the ].
|}
{| class="messagebox"
|-
| ]
| '''This page is an ] on the English Misplaced Pages.''' It has wide acceptance among editors and is considered a standard that all users should follow. When editing this page, please ensure that your revision reflects ]. When in doubt, discuss first on the ].
|}
{| class="messagebox"
|-
| ]
| '''This page is an ] on the English Misplaced Pages.''' It has wide acceptance among editors and is considered a standard that all users should follow. When editing this page, please ensure that your revision reflects ]. When in doubt, discuss first on the ].
|}
;Current version
{| class="messagebox"
|-
| ]
| '''This page is an ] on the English Misplaced Pages.''' It has wide acceptance among editors and is considered a standard that all users should follow. When editing this page, please ensure that your revision reflects ]. When in doubt, discuss first on the ].
|}
<br style="clear:both;"><br style="clear:both;">
]A discussion about a possible "official policy seal" for our policy pages to replace the green tick mark,(]) has been going on for the last few days at ].
This is the latest iteration. Previous iterations are available in my ]. Here is a of how this will look on the {{tl|policy}} template.
Before I invest any more time on this, I seek comments from the wider community to assess if this proposal is worth pursuing. ] <small>]</small> 00:20, 13 March 2007 (UTC)
:This makes sense... I think seals are a bit more universally recognized in the context of a policy/mandate. The only caveat per ] is that it is better to make one without words in it for universality across all Misplaced Pages languages. {{User:Netscott/s1.js}} 00:41, 13 March 2007 (UTC)
::There is a blank version available, that can be used to localize the text: ] ] <small>]</small> 00:49, 13 March 2007 (UTC)
:I'd prefer it without the text. "Official policy" is in blue and in bold in the box's text - there isn't a lot of point trying to get the image to illustrate the page when the bold text does that much better. And when shrunk down to the size used in the template, the tiny curved text strains your eyes. It would be good to replace the generic tick mark, though, so I like the idea of using a seal. --]<sup>]</sup> 00:53, 13 March 2007 (UTC)
:As I've commented at the aforementioned discussion, I have numerous objections to this change:
# There's nothing wrong with the checkmark/tick. Jossi claimed that it's "US-centric," but that's patently false. It isn't even Anglocentric.
# This is proven by the fact that this exact icon file appears in the policy templates of Wikimedia wikis spanning no fewer than 26 different languages. This consistency is highly beneficial.
# In addition to being widely adopted by other Wikimedia wikis, the current setup (green checkmark for policies, blue checkmark for guidelines, red cross for rejected/historical pages) has been in use here since December 2005. It's highly familiar to many people, and there's no compelling reason to start over.
# The seal contains English text, thereby limiting its use to English-language wikis (or necessitating localization for each language).
# The text is difficult to read at my resolution/screen size.
# The text is completely redundant with the actual template's wording.
# The intended display size is ''far'' larger than the 30px icons used in the various page status tags. As a result, the template's minimum size would be larger for many users (thereby pushing the actual content further down the page).
# Jossi has proposed the use of gold coloring for policies and silver coloring for guidelines. This would reinforce the widespread misconception that guidelines are "ranked lower" than policies and can be disregarded by anyone who dislikes following them (because they're "only guidelines"). While it's true that guidelines sometimes have more wiggle room than policies do, they generally should be followed unless there's ]. The use of green and blue doesn't reinforce the notion that guidelines carry no official weight. Gold and silver (or any other "lower" color) would be counterproductive.
#I also believe that the connotation carried by the seal imagery itself is inappropriate. Another widespread misconception is that our rules are sacrosanct laws that must always be followed to the letter. To me, this new icon seems indicative of such a situation, while the checkmarks convey the reality that these are mostly consensus-based checklists of concepts determined to be appropriate via use and discussion (descriptive, not prescriptive). —] 00:58, 13 March 2007 (UTC)
::Sorry David Levy, but you might have wanted to disclose the fact that you've had a ] in the adoption of the Green and teal checks for use in tagging policy pages. {{User:Netscott/s1.js}} 01:04, 13 March 2007 (UTC)
:::I mentioned that more than once in the aforementioned discussion. In case you didn't realize, I didn't design the checkmark. I merely converted it from an SVG to a PNG (which renders properly in IE6), created a blue version, and added these to the templates. I also had absolutely nothing to do with the icons' adoption at any of the other wikis. —] 01:16, 13 March 2007 (UTC)
Here is a version (#2) without caption and with ribbons as requested by some editors:
:Looking '''very''' good. {{User:Netscott/s1.js}} 01:13, 13 March 2007 (UTC)
::It's a nice icon, but it resembles an award of some sort. —] 01:16, 13 March 2007 (UTC)
:::Well the ribbons aren't ''truly'' necessary.... but let's see what others think.. {{User:Netscott/s1.js}} 01:20, 13 March 2007 (UTC)
::::Agreed, of course. —] 01:29, 13 March 2007 (UTC)
:Let it be known, I am ''not'' attached or feel strongly about making a change. Only that I think that as the project evolves, and our content improves, we need better graphics as well. ] <small>]</small> 01:22, 13 March 2007 (UTC)
::To me, the proposed change seems like a step backwards and a solution in search of a problem. (No offense intended. As I said before, I'm incapable of designing an SVG approaching this level). —] 01:29, 13 March 2007 (UTC)
:::Maybe, David. But exploring possibilities, has the potential to discover them. ] <small>]</small> 02:08, 13 March 2007 (UTC)
::::No argument there. I'm just expressing my opinions. :-) —] 02:10, 13 March 2007 (UTC)
I have to agree with all of David Levy's objections; particularly the cross-wiki consistency, and size/colour comments. However, (just to be difficult!), how about draft#3, in white instead of gold, with the green/blue tick in the center? I'd still be recognizable and minimal, but would get the redesign-proposal's point across. --] 04:00, 13 March 2007 (UTC)
I have only one thing to say about this, KISS. The checkmark is humble and it is simple. Fanfare to a minimal. If you want to use something else, ok, but do not forget the awesome power of simple. -- ] 04:11, 13 March 2007 (UTC)
:I tend to agree with Ned Scott which is why I'm tending to prefer this image ]. {{User:Netscott/s1.js}} 04:24, 13 March 2007 (UTC)
::I don't know about your display, but on mine, that looks remarkably like a depiction of the sun. —] 04:27, 13 March 2007 (UTC)
:::Actually I mentioned this to Jossi and explained that it would be good to make a better more well defined version for smaller sizes (like above here)... he explained that he wanted to test the waters here before he extended more effort on this idea. {{User:Netscott/s1.js}} 04:31, 13 March 2007 (UTC)
:::*I think the gold seal looks rather silly on a policy page, and at any rate it's not such a good idea to affix any kind of Official Seal Of Authority to our policy pages. ] a bureaucracy. ] 12:04, 13 March 2007 (UTC)
I can see that there is no traction for this proposal. At least we have now a dozen seals in the public domain at commons... ] <small>]</small> 15:33, 13 March 2007 (UTC)
Last attempt I did yesterday night, below. ] <small>]</small> 16:32, 13 March 2007 (UTC)
{| class="messagebox"
|-
| ]
| '''This page is an ] on the English Misplaced Pages.''' It has wide acceptance among editors and is considered a standard that all users should follow. When editing this page, please ensure that your revision reflects ]. When in doubt, discuss first on the ].
|}
:This I like. Checkmark as a clear sign that it has approval, gold seal showing it's official. Definitely makes it a clearer distinction at a glance from guidelines. ] (]/]) 20:43, 13 March 2007 (UTC)
::As Radiant and I noted above, a gold seal carries a connotation that's best avoided. And again, the "distinction" to which you refer already is far less significant than many people believe. Additional emphasis would be highly counterproductive.
::As Ned Scott noted, simplicity is good. There's no need to replace a small, sober icon (the dimensions of which have been standardized across our page status templates) with a large, fancy distraction that increases the tag's size and pushes content down the page.
::And frankly, a seal with a protruding checkmark makes little sense. —] 23:58, 13 March 2007 (UTC)
I'm more for keeping it as a simple check mark. It gets the point across nicely without being distracting. —] <sup>(])</sup> 04:57, 14 March 2007 (UTC)
::: '''GO to anything''' so policy and guidelines are more distinct from one another. Put a frowny face on one and a smiley on the other, but make them look different! (And Radiant!, since when aren't we a bureaucracy... God forbid anyone should ever try to print hard-copies of all our guidelines and the few, way too few, policies.) // <b>]</b><font color="green">]</font> 09:35, 16 March 2007 (UTC)
For what it's worth, support seal with checkmark. --<font color="red">]</font><font color="green">]</font><font color="yellow">]</font><font color="black">]</font><font color="pink">]</font><font color="blue">]</font> 18:07, 20 March 2007 (UTC)
== extend ] to cover particularly revered dead people? ==
I'm curious if there would be any objections to extending ] to cover figures that are particularly revered by national, ethnic or religious groups.
A great many people take criticism of their leaders seriously. Recently, ] was blocked in Turkey because of a video making fun of ] and a British national was imprisoned in Thailand for "insulting the King". We all remember last year's furor over Danish political cartoons depicting the Prophet Mohammad.
Given the growing coverage of Misplaced Pages in the mainstream media, it might be a good idea to explicitly apply the unequivocal language of ] to figures that are particularly revered, if for no other reason than to help prevent a situation where some idiot's vandalism of wikipedia leads to serious consequences in the real world. Its bad enough that Jimbo had to defend Misplaced Pages in the American press during his recent trip to rural India, I don't think anyone wants a situation where he has to deal with the secret police in some country because some idiot vandalized the article on that country's national hero.
I don't really see a downside here, we should be holding these articles to a very high standard anyway, if for no other reason than because they are likely to be highly visible. My experience with BLP is that it doesn't necessarily restrict criticism, but it does force people who want to add criticism to write better, more accurate and better sourced claims. ] 22:06, 14 March 2007 (UTC)
:It's easier, on the whole, to judge who's alive and who's dead. Would the category "Particularly Revered People' be vetted by a specially designated sub-committe of Misplaced Pages administrators? Would ''all'' saints be included as "Particularly Revered"? Would that include saints who never existed historically? How about just semi-protecting highly vandalized pages? --] 22:29, 14 March 2007 (UTC)
::Honestly, I don't think the subjectivity issue is a big deal. Lets say the category is overused - what's the worst that will happen? High standards are applied to too many articles? We can always develop a better inclusion criteria, say, any case where wikipedians would have reason to believe that vandalism of an article might cause undue harm to the project, based on multiple sources that say that people who have been accused of insulting the person have been prosecuted or otherwise persecuted.
::Of course we can do this in addition to semi-protection, but there are a couple of advantages to having a formal policy. First, if we get attacked in the media it will be helpful to say that we have already developed a strict policy to deal with this stuff. Second, it may make all editors a bit more careful about citations and POV issues. Third, it will be easier to remove problematic material.] 23:05, 14 March 2007 (UTC)
:I object to extending ] to any particular subclass of dead people, except possibly some sort of "dead for fewer than N years", where N is a one-digit integer. In particular, all three cases you mention are places where Misplaced Pages should not apply WP:BLP standards. We have ], that's enough. <span style="font-family:serif;font-size:120%">''']''' ]</span> 22:48, 14 March 2007 (UTC)
:I would object to this as well. It's not hard, and not subjective, to determine if a person is alive. It's far harder and much more subjective to determine if a person is or was "revered", and I don't think we should get into the business of deciding that. How do we decide? Revered by whom? The rationale for this policy is that it ''prevents harm to living people''. Dead people can't be harmed, they're, well, dead. Of course, an editor repeatedly attempting to insert unsourced POV edits into an article about a dead person can be reported and dealt with for disruptive behavior, but that's true of all articles. ] <small><sup>]</sup></small> 22:57, 14 March 2007 (UTC)
::I agree with Seraphimblade. This just seems to be unnecessarily opening a can of worms. We really don't want to encourage arguments over which dead people are "revered", and which aren't. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 22:09, 15 March 2007 (UTC)
== About Speedy Deletions, regular Deletions, and editors who only do those two things. ==
Is there a method in place already to censure people for using deletion tags incorrectly, repeatedly? I find it is an incredibly common problem - if I see something on TV that is notable and yet does not have its own article, I usually try to add it. Every single time I add an article, someone tries to have it speedy-deleted instantly. We are not talking about random, meaningless articles here; instead we are talking about content that is universally approved and accepted as notable, except it does not have sources yet. When I go back, and do more work that the other person could have helped with, and add sources from Google, there is no dispute.
There are dozens and dozens of editors who go through new pages and just wantonly apply speedy deletion and prod tags to new articles that are short, temporarily unsourced, or otherwise don't meet their approval. Despite the fact that they are not candidates for regular deletion (let alone speedy), these same editors constantly mark things for speedy-deletions regardless, assuming that someone else will come back behind them and clean it up if it was a mistake.
This is hugely detrimental to the project, and it is a form of newbie-biting. Do we have a force in place to correct this behaviour specifically? People who have no idea what the speedy-deletion criteria even ARE should not be using speedy-deletion tags, and yet they are doing it, because it is an easy way to get their edit count up without contributing, doing research, or doing any real work.
So please tell me I'm overlooking a place where I can report these habitual abusers? I wish there was a specific unit or group of people specifically watching for this sort of thing, because it literally happens with /every single/ article I have created, both as an anon (previously) and as a registered user (now).] 22:20, 14 March 2007 (UTC)
:Re the ''spur of the moment'' unsourced new articles. Have you considered starting the article in your ], finding and adding sources, before creating the thing in Misplaced Pages? This might prevent speedy delete tags for lack of references.
:As for the New Article Patrols; I don't know enough to comment but there is a lot of cruft created each day, somebody has to get busy with the broom. ] 22:34, 14 March 2007 (UTC)
::My point, really, is that this is against policy and they shouldn't be doing it. While I could write the whole thing in notepad and add sources before I pressed 'save,' why should I have to? I am not the one violating policy, they are. ] 22:43, 14 March 2007 (UTC)
::The onus for sourcing is, always has been, and always will be, with the person creating the new article, and not the person nominating it for deletion. ] <small>] </small> 22:37, 14 March 2007 (UTC)
:::So if I wrote an article about Hitler with no immediate sourcing, and someone else came by and wanted to speedy delete it as 'patent nonsense - db1,' you would find this acceptable? Because to me, that's completely misunderstanding the policies on deletion, and especially on speedy-deletion.] 22:41, 14 March 2007 (UTC)
::::Probably, but then we've got ] already. PS - ]. :-) ] <small>] </small> 22:46, 14 March 2007 (UTC)
:::::Probably? Meaning you would find that acceptable, to speedy-delete it as 'patent nonsense' simply because it didn't have sources that a simple click on Google would turn up? I suggest you read the article for deletion page again, because it specifically warns against doing that, in several ways and places. I will note that I am new here, and I thought this was a place where I could get actual constructive responses. I am a bit baffled by the flippancy, as I thought this would be a forum to communicate seriously. Is this a gag page, or is it just you? ] 22:51, 14 March 2007 (UTC)
::::::I've done several articles in a userspace sandbox before posting them. Sometimes you do come across something you think it might be interesting to make an article on. But we ] that article content be attributed to sources. Not sometime, not before they get ready for their FA nomination, but from the ''very first edit''. If you want to start a draft, but aren't ready to source it yet, just start it off in userspace, and source it at your convenience, without any worry of deletion. As to speedies, if you think one was requested inappropriately, add {{tl|hangon}} to the article and make your case. If you would like any of the deleted articles userfied so that you can find some sources, let me know, I'll be happy to do so for you. Generally, so will the admin who performed the deletion, unless the article was an attack or copyvio. ] <small><sup>]</sup></small> 23:04, 14 March 2007 (UTC)
:::::::<small>(edit conflict)</small> If I saw a new article on Hitler saying random gibberish or biased political rantings, then I would immediately nominate it for speedy deletion. When I am on the prowl, I look for articles with absolutely no context whatsoever (often created by vandals), articles that appear to be autobios (often created by newbies and which I simply move to their userspace), or I look for articles which do not assert their ] (among the biggest mistakes, in my opinion). I believe that users should take their time creating a new article and try to work out its kinks before making that first edit, so-as to prevent misunderstandings such as what you have experienced. If an article has not existed for the several years that Misplaced Pages has been around, I'd be pretty confident that no one is going to create it while you're typing it up.
:::::::I do not know what the original incarnation of your article looked like, but the vast majority of the existing text on ] does not seem to assert any notability -- with the exception of the last line: "<i>Ms. Clifford was memorialized in the 1980s with a play, and then a musical, about her antics. It was entitled 'Nina! Madam to a Saintly City.'</i>" For that reason, I believe it attains notability. It provides links, which (I assume) provide references (though they should be wikified, but alas: I, too, am guilty of rarely formatting references properly). --] (<small>] ;; ]</small>) 23:07, 14 March 2007 (UTC)
:Try ] first, but make sure the taggings are, in fact, false. Have your argument ready or you'll be dismissed outright. ] would be the next step after that, although it's typically a waste of time. --] <small>]</small> 22:56, 14 March 2007 (UTC)
::Also try {{tl|inuse}}, on your very first edit. <span style="font-family:serif;font-size:120%">''']''' ]</span> 22:57, 14 March 2007 (UTC)
:::Thanks for the tips! I will keep them in mind. ] 23:06, 14 March 2007 (UTC)
:::It's actually rare that a speedy delete would occur in five minutes and it would certainly mean that at least one editor and one administrator found the article worthy of deletion. One problem I saw with your article was that there was no notice of notability (notoriety, yes; notability, no). Lots of uncited stubs survive, but non-notables tend to get waxed. ] <small>]</small> 23:00, 14 March 2007 (UTC)
::::The point is not whether the article qualified for a suggested deletion. The problem is that it clearly (and the other ones too) did not qualify for speedy-deletion, and yet people are very very quick to slap a tag on there, usually within thirty seconds (!) of creation. That is wholly inappropriate, and even if the nonsourced article would have been deleted following deletion policy, so be it. But tagging it as a speedy-deletion and then doing it over and over to other articles just to get your edit-count up is the problem. I know how to proceed now though. Thanks! ] 23:06, 14 March 2007 (UTC)
::::::Also, to be clear, no admin deleted my content. I was miffed by constantly being faced with erroneous speedy-deletion tags on content that was NOT patent nonsense, and yet was tagged that way by new page patrollers of the regular-editing variety. ] 23:08, 14 March 2007 (UTC)
(undent) You're sort of missing the point of ] if you write the article and add sources later. Ideally, you should be writing from sources, not writing and then finding sources to back up what you say. <font color="maroon">]</font>'''<small>]</small>''<font color="navy" face="cursive">]</font>'''''<small>]</small> 23:45, 14 March 2007 (UTC)
:However, if an article has real content, CSD nonsense only applies to true nonsense (sjdgfoseuaygfs sfdhp234io), not coherent content, so you could definitely argue agaist deletion based on misuse of the criteria. <font color="maroon">]</font>'''<small>]</small>''<font color="navy" face="cursive">]</font>'''''<small>]</small> 23:52, 14 March 2007 (UTC)
:: (responding to comment further up) Articles get looked at as soon as they're posted. If you'd like to work an article that's not ready to be read, it's best to create it and work on it as a ]. Maybe it's a little surprising to see articles tackled right away, but this is a wiki, we all work together, and if you want an article for yourself for a bit, don't put it in article space. --] 00:34, 15 March 2007 (UTC)
Wait... what's this? ''"create in userspace"''!? Doesn't that amount to ''"Please don't actually use the '''wiki''' to make an encyclo'''pedia'''?"
OUW!
We're here to work together to make great articles. Not to race each other to see who can delete articles fastest. Focus here folks! :-)
Articles are started in the main namespace, and when you see one, your first question should be ''how do I improve this?", not "which CSD tag shall I apply today?".
My first article on wikipedia got wikified and tidied practically before I released the submit button. That fast! Was I hooked? Boy was I ever. I'm still here editing years later :-P
--] 02:01, 15 March 2007 (UTC)
:This suggestion to only create article in the user space until they are of feature article status is utter BS'ing. In this regard, I completely agree with you Kim. We are here to create great articles, and they have to start somewhere. The whole point of Misplaced Pages was to avoid having to go through the incredibly painful process of Nupedia where you had to write the article completely, submit it for "peer" review, have it rot away for a while, go back and re-edit the article, add more sources and improve the content, and then finally get the thing for approval. Again, how many Nupedia articles actually got written in this process over the course of more than a year and a half? And yes, I was there back when Nupedia was first started. I was so intimidated by the whole process that I decided to bag it and not even bother trying. It sounds like some people here would like Nupedia to start back up again, as if Misplaced Pages never happened, or even understand why Misplaced Pages was started in the first place. --] 05:06, 15 March 2007 (UTC)
:This editor specifically said<blockquote>''"if I see something on TV that is notable and yet does not have its own article, I usually try to add it..."''</blockquote>and then goes on to say that they then look to see if there are references they can use. If folk are going to be allowed to add "interesting facts not previously noted" without context and to be referenced as and when sources are found (and just left hanging if there is nothing? Are these people going to go to a major library or just do a Google search for their citations?) then both ] is going to need rewriting and the article stubs people will be needing counseling.
:The sandbox is the ideal place to consolidate and polish up a new article, and many people (me hopefully included) are better editors for having early contributions removed/ripped to shreds; as per the comment in the edit box. I also think the people patrolling new articles are performing a useful service in keeping the standard of surviving articles to a reasonable standard, it gives a useful mark at which to aim, by removing non-par contributions. They would likely be delighted to come across more new articles that have already been worked on and do not need any attention from them. ] 22:56, 15 March 2007 (UTC)
Every deletion is a person displeased, and some of those people will make no further contributions, and frankly when I see things like ] and ] and they're hanging around for months and years I have to wonder if all the policies and guidelines on content aren't just pretense. ] 05:21, 15 March 2007 (UTC)
::(EC) Whoa! I think we can have a middle ground here. No one's saying "Create in userspace until it'll be ready for FA on the first edit." The issue here is ''sourcing''. We should be writing from sources, not memory. What userspace creation does help with, is preventing needless deletion (and whether anyone likes it or not, there is a ''lot'' of garbage coming in. ].) When one is doing newpage patrol, and seeing tons of one- or two-line articles coming in, most of which are in the vein of "John is really cool lololol", yes, sometimes the trigger finger gets an itch, but that's not without reason. It also helps future editors (there's a source right there, write some more from it!) and helps to weed out hoaxes (the more articles that come in sourced, the closer of scrutiny can be placed on those that don't.) The arguments often seem to exhibit the ] and ] fallacies. There is a middle ground between "Create a sourceless one-line article that barely even explains what it's about" and "Create an FA on the first edit." ] <small><sup>]</sup></small> 05:22, 15 March 2007 (UTC)
::: Hmmm, I know all about the itchy trigger finger phenomenon. I've done most kinds of admin-type patrol too. I might have occaisionally gotten one or two complaints. <small>''Shootout on Deletion Review at high noon? Who me? <innocent look>. No Requst for comments or Arbcom cases though <knock on wood>.''</small>. You do need to make snap decisions though, because it's like mopping the floor while the tap's still running. If you mess up, just undelete quickly, no problem. Or only go by ] in the first place, that's what it's here for, sanest system around!
::: If those don't really work out anymore, then we've got a problem. We're supposed to be helping editors, not hindering them, of course. Moving away from the wiki-pedia model is probably not the best idea though. :-/
::: I still might know some tools (& who to bribe to work on 'em) to help with making admin tasks easier, and maybe we can make improvements to RFA itself. Do you have any specific ideas on what might help (tools, processes, attitudes, or pure blue sky thinking) , yourself? --] 06:03, 15 March 2007 (UTC)
::::By far, the best thing that could be done is a similar attitude toward sourcing as there is toward NPOV (though this may be blue sky thinking). If someone sees a glaring NPOV problem, they know it's a ''problem'', and it needs fixing sooner rather than later. This is good. As a reference work, we ''should'' be placing a tremendous amount of importance in maintaining a neutral stance. Yet many of these same editors, upon coming across a sourceless article, won't even do so much as place an {{tl|unreferenced}} tag on it to call attention to the problem, and become very agitated about the removal of unsourced information (or sometimes even just on fact-tagging it!) Sourcing is not only ''as critical as'' NPOV, it is critical ''to'' NPOV. If what is in an article is sourced, there is no need to question editorial bias-we're reporting what reliable sources said, not what we think. It also helps future editors immensely, as quite often there's more information in a source for what that editor wishes to add, and it's ''right there''. It's also extremely beneficial to readers, if they read an article and want more in-depth information, a reference list tells them right where to find it. I don't think this could be done through policy (hell, it already ''is'' policy), but I'd like to find some way to get people to understand the importance of sourcing. ] <small><sup>]</sup></small> 06:16, 15 March 2007 (UTC)
::::Actually, come to think of it-someone proposed, a while back, that we could have a "Draft:" namespace, that articles-in-progress could reside in until they've met the minimum sourcing guidelines. I think that just might help-that way, the decision isn't just between "Delete it entirely" or "Keep a sourceless article around", if no one can readily find sources. ] <small><sup>]</sup></small> 06:18, 15 March 2007 (UTC)
:::::There are very legitimate reasons to delete "articles", especially if they aren't encyclopedic or even somebody just writing random garbage. But writing a draft version of a legitimate article just doesn't seem to me to be one of these. There are many, many articles that are legitimate stubs (and mostly even labeled as such). While having sources is a very good thing and should be strongly encouraged, deleting good faith contributions is not the best way to help encourage new people to try and contribute here. This includes POV edits, as in many cases all you need to do is simply educate the new contributor and try and let them know some good examples of NPOV articles and what the general philosophy actually is. Article deletion is the easy way out of this process, which is why it is done perhaps far more often than it should be. --] 22:24, 15 March 2007 (UTC)
::::::That's why I like the idea of the "Draft:" namespace (though, it would be easy enough to userfy unsourced articles, even without any code changes). That should address the concerns on both sides. For those concerned about unsourced articles, it gives an easy way to get them out of the encyclopedia, without deleting them entirely. For those contributors who contribute unsourced information, it lets them keep what they've written, but sends a firm message "Source it, ''then'' put it in an article, not the other way around." ] <small><sup>]</sup></small> 23:05, 15 March 2007 (UTC)
:::::::So how would you deal with red links? By keeping them in the main namespace, you would at least have the blue-links for those articles which are stubby, even if they don't have all of the sources you are insisting on here. I'm not objecting to disclaimers and templates warning that the article is stubby in nature or incomplete. For me, a "Draft" namespace would be better used to help calm down edit wars where people are going back and forth with very unstable articles and moved to the main namespace once there is something close to concensus that has been achieved. I know that the red/blue link is something that could be fixed in software, but it does indicate that more thinking needs to go into this idea, and needs to be more than just creation of a new namespace.
:::::::On the other hand, I would support a "Published:" namespace or something similar that would only get content that has achieved some level of review and acceptance of several users. And to have articles in this published namespace to only link to each other unless the article hasn't reached a "published" level of acceptance. A user preference could then be used to stick with just the published articles or go to the "raw" articles under development, with default settings to only search for the published articles. Articles would have to be "republished" again if they have changed and the users find a new version acceptable. Of course, the devil is in the details about how this would happen. --] 00:35, 16 March 2007 (UTC)
::::::::The devil always seems to take up residence there, of course. Basically, what would happen is that articles with no reliable sourcing whatsoever would reside in the "Draft:" namespace (or alternatively be userfied and added to a category). There, the editors could take as long with sourcing as they desire, without having to worry about the article being deleted for lack of sourcing. If they need a few weeks to wait for an interlibrary loan to come in, that's fine! They're not restricted to a 5-day AFD process that way. On the other hand, that also ensures that we're not presenting totally unreferenced content as encyclopedia articles. To solve the redlink problem, perhaps it could be set up so that if there is not yet a mainspace article, but there is a draft, the reader is directed to a page stating something like "The article on this subject is a draft. Its information is not verified or sourced and is likely to contain inaccuracies. If you would like to view the article or help with writing and sourcing it, please click here." ] <small><sup>]</sup></small> 09:58, 17 March 2007 (UTC)
== User pages on Google ==
I don't think user pages and user subpages should be searchable on Google. Some people like to keep private versions that lean towards a POV not approved by consensus. In at least one case the user subpage appears higher in Google search rankings than Misplaced Pages's own article. It should be relatively easy to fix the software to treat user pages and subpages like talk pages and not let them be searchable. Thoughts? --] 12:40, 15 March 2007 (UTC)
:So, how do you stop it? Realistically. I know, there is the "Robots.txt" file that is supposed to set up rules about what can and can't be searched by "legitimate" search engines on any given website, but I don't think it necessarily applies in this situation either.
:What goes into any page here on Misplaced Pages, including user pages, is very much a public page. Perhaps that needs to be made more clear on the edit box itself, but if you are posting information here, expect that all of it including the user pages is going to be read by anybody and everybody, including employers, government law enforcement agents, ex-spouses, children (even grown up children), parents, friends, enemies, political opponents, and others. Even if these pages weren't made searchable, there is nothing that the Wikimedia Foundation can reasonably do to stop others from going into these pages and seeing what you may have written.
:In addition, all of this content is not only made searchable, but you can even download it all in one massive file for all user pages, and some interesting searches have been made recently of user pages of a statistical nature to try and find out the demographic make up of Misplaced Pages contributors. If this policy of prohibiting a google search of user pages is to happen, you should also prohibit even the ability to download user pages as well. --] 13:32, 15 March 2007 (UTC)
:I went to ] and would have thought that having a POV fork of a page in your userspace would have been listed as bad. You probably could ] the POV page and claim that it's a POV fork and/or the temporary work in progress isn't actually being worked on (depends on the edit history). I don't think limiting searching is a good idea. Being able to search in Google for items that may be contained in userspace is useful, especially with the current state of our in-house search. --]≈<small>]</small> 13:37, 15 March 2007 (UTC)
::My concern is that if the POV user pages show up in a standard Google search someone might go to them thinking they are legitimate Misplaced Pages articles. This can be alleviated by tagging them with {{tl|Userpage otheruse}} (which I have done) so at least there is a partial solution. I'm not opposed to them being available in general, I just don't want them confused with real Misplaced Pages articles. --] 14:04, 15 March 2007 (UTC)
:::I agree in concept, but if the person searching is paying any attention and has and sense about them, they will note that the page they are looking at is headlined with "User:SoAndSo" or what ever the user's name happens to be. If I saw that, I would at least look into whether or not it was an actual article about the topic or just a user who happened to have the same name as the topic for which i was searching. ] <span style="font-size:75%">] <sup>]</sup></span> 16:16, 15 March 2007 (UTC)
::::Remember that a lot of people are new to Misplaced Pages (] and ] are the most commonly viewed pages). Most people are stupid. (Actually, they just aren't paying attention, but the result is the same.) --] 17:13, 15 March 2007 (UTC)
:Hey! Since when did Talk pages stop being searchable in Google? That doesn't seem to reflect any part of Misplaced Pages's configuration (neither robots.txt nor meta tags prohibit indexing talk pages), but they do appear to be largely missing. Compare and . It appears that Google has independently decided not to index the article talk pages. Oh, and yes, POV forks in user space should be deleted. ] 16:32, 15 March 2007 (UTC)
::I have archived all those contents in edit histories. The materials should no longer be possible to be searched on Google. Please consider retreating your MFD nomination. Thanks. — ]] 22:46, 17 March 2007 (UTC)
*This should be on ]. ] 12:45, 16 March 2007 (UTC)
:Also, this has been around before; see , ], and for old discussions, none of which really came to a satisfactory resolution. Of the top ten google hits for 'Opabinia regalis', I'm #3, 4 (or 3.5), and 10. ] 05:12, 17 March 2007 (UTC)
== Ineffective '''Wikiseek''' ==
I have recently noticed that a Wikiseek is now the default action for text entered in the search box that appears to the left of each article.
Is this helpful to our users while Wikiseek typically produces inferior results to the '''Go''' button?
[Wikiseek is a search engine that has indexed only Misplaced Pages pages, plus a very few pages that are linked to from Misplaced Pages. It was created by startup Searchme, Inc.
Despite press reports to the contrary, it has no affiliation with the charitable organization ] or private corporation ], and is unrelated to the never-released web search application ].
Misplaced Pages users are cautioned that using the Wikiseek button often produces an inferior result to using the '''Go''' button on Misplaced Pages.
An ironic example of this is if one enters "Wikiseek" into the search button of Misplaced Pages; choose the Wikiseek button and no useable results will currently be displayed, choose the conventional "Go" button and you are taken directly to '''this''' article!
Further examples of futile searches with Wikiseek (even though there are eponymous articles) would be "]" and "]" (even though these particular problems were reported in 2006...]
] 17:09, 15 March 2007 (UTC)
:I don't understand - for me, the default action is still the '''Go''' button. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 22:06, 15 March 2007 (UTC)
:I think you've got some ] installed on your computer which is altering the way Misplaced Pages displays for you. There is certainly no "Wikiseek" button in Misplaced Pages. ] / ] 21:09, 17 March 2007 (UTC)
== Discussion of articles with "allegations"in their name ==
Definition of "allegation":
al·le·ga·tion /ˌælɪˈgeɪʃən/ Pronunciation Key - Show Spelled Pronunciation *Pronunciation Key - Show IPA Pronunciation
–noun
*1. the act of alleging; affirmation.
*2. an assertion made with little or no proof.
*3. an assertion made by a party in a legal proceeding, which the party then undertakes to prove.
*4. a statement offered as a plea, excuse, or justification.
Misplaced Pages's official guidelines regarding the use of the term:
''Alleged (along with allegedly) and purported (along with purportedly) are different from the foregoing in that they are generally used by those who genuinely have no predisposition as to whether the statement being cited is true or not. Newspapers, for instance, almost universally refer to any indicted but unconvicted criminal as an alleged criminal. Therefore, there is no neutrality problem with using them. However, there may be a problem of ambiguity—they should only be used where the identity of the alleger is clear.''
...
''O.J. Simpson allegedly murdered his ex-wife and a friend of hers in 1994. ''
(Taken from ])
Currently on Misplaced Pages, there are some articles with that word in their article name. Noted:
*]
*]
*] (note that this is the legal use of the term)
*]
*]
*]
*]
*]
*]
*The '''Allegations''' section of ]
and on and on. Please see
These articles discuss the allegations, and then give examples of when the term is used.
But, there are also articles like this:
*] (see discussion on talk page)
*] (see discussion on talk page)
*] (see discussion on talk page)
*]
*] (Note that ] is a redirect to said article)
*] (First sentence of the article is "Several groups have '''alleged''' <nowiki></nowiki> that there have been instances of '''] by ]'''")
*]
*]
*]
*]
etc.
So I was wondering, what is the current status of these articles? I don't think it makes sense for some articles to have "allegations" in the title, while others don't. I think either they all should, or they all shouldn't. Thoughts? --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 20:20, 15 March 2007 (UTC)
:How does ''Holocaust'' fit into your list? --] 20:38, 15 March 2007 (UTC)
::It fits because the Holocaust is '''alleged''' to have happened. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 20:43, 15 March 2007 (UTC)
:::It's not "alleged" to have happened, it '''did''' happen. ] applies here, as I explain below. ] (] | ]) 20:47, 15 March 2007 (UTC)
::::According to the definition of alleged, it has been alleged to happen. There is a considerable minority of the world which do not believe the holocaust occured. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 20:53, 15 March 2007 (UTC)
:::::Speaking frankly here, I think this was a productive discussion until you made your last point. Obviously there are events that are universally acknowledged by scholars as real and should be treated as such (e.g. the Holocaust) and there are interpretations of historical events (e.g. most of the items of the first list) that are inherently allegations. We need to have a discussion about "criticism of x" and "allegations of x" articles, but if we can't distinguish between things that are certainly true and things that are certainly alleged we'll end up with either "Allegations that the Earth is Flat" or "Controlled Demolition of the World Trade Center". ] 22:12, 15 March 2007 (UTC)
::::::You say "certainly true". WHO decides whether something is certainly true? Sources? Misplaced Pages editors? "Certainly true" is something which is contestable in and of itself. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 16:24, 16 March 2007 (UTC)
:] is critical here. "Allegations" is perfectly acceptable in article titles where the article exists to document an unverifiable, albeit possibly noteworthy, belief. An example of this would be ]. The existence of "Israeli apartheid" apartheid at all is itself quite questionable, but the question being posed by many on the political far left and political far right is a valid subject for Misplaced Pages to document. The ideas themselves are unverifiable and thus cannot be accepted as fact within Misplaced Pages, but the argument can certainly be made that the allegations are noteworthy enough to justify an article about the allegations themselves. Conversely, ], ] and ] are not allegations, they are historical (and in the case of the former two, also present) realities. Thus, per ], they can be considered fact.
:I'd argue that the "State terrorism" articles ought to be moved to "allegations of..." but beyond that, it looks good the way it is now.
:The subject of the article is coalesced in its title; "Allegations" articles document the allegations themselves, whereas non-"allegations" articles document facts. ] (] | ]) 20:46, 15 March 2007 (UTC)
I don't understand what you mean by "unverifiable". What is "unverifiable" about Israeli apartheid? For some people, it is considered a fact. Opposite goes for Holocaust. Some people don't consider the holocaust of fact. I think these selective titles may be an example of ] (]) --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 20:51, 15 March 2007 (UTC)
:It fails ] and is therefore '''unverifiable''' per Misplaced Pages standards and policies. The criteria for what makes information verifiable for the purposes of Misplaced Pages is clear and remarkably simple. Remember that ]. I have seen no exceptional sources suggesting "Israeli apartheid" exists and therefore it fails ]. Sorry. Systemic bias isn't an issue here, it's Misplaced Pages's content policies that you have a problem with. ] (] | ]) 20:57, 15 March 2007 (UTC)
::Exceptional according to who's definition? I could say "I have seen no exceptional sources suggesting that "holocaust" exists and therefore it fails ]". --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:01, 15 March 2007 (UTC)
:::I definitely do ''not'' want to start titling articles like ] with the words "allegations of" before it. To me, "allegations" a term that should be reserved for very specific legal instances. In the case of "Israeli apartheid", it's a descriptive term that's in use in different political circles. Those who use it are not ''alleging'' that Israel is an apartheid state, they are ''insisting'' it is. That term and its associated debate deserve representation in an article titled after the concept itself. The controversy can be discussed in the article, much as it is in ]. ]
:::Tiamut, I must say that was my point in bringing up ]. Thanks for putting it in better words than I have. I also would NOT like to see ]. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:06, 15 March 2007 (UTC)
:::Note how ] doesn't even redirect to ]. I just realized that now. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:07, 15 March 2007 (UTC)
:::Nor does ] exist. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:09, 15 March 2007 (UTC)
:::An "exceptional" source is defined according to Misplaced Pages ]. The applications policy are subjective, but the fact is nonetheless they are subjective of consensus more than they are subjective of any individual editor. ] (] | ]) 21:11, 15 March 2007 (UTC)
::::That's exactly my point. The consensus is subject to systematic bias. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:16, 15 March 2007 (UTC)
:::::So what are you suggesting? Destroying ] and ] because they don't allow for the views of a political fringe to be accepted as fact in Misplaced Pages articles? I'm sorry, but no one will go for that. ] (] | ]) 21:19, 15 March 2007 (UTC)
::::::I find it extremely offensive that you consider Israeli apartheid as fringe; notable scholars such as ] have spoken of it. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:45, 15 March 2007 (UTC)
:::::::Also, look at ]. It has the apollo moon hoax, creation science, and the paul is dead hoax as examples. Are you seriously suggesting that the discrimination towards Palestinians in the occupied territories is equivalent to those nonsense theories? --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:51, 15 March 2007 (UTC)
::::::::Official discrimination by the Israeli government with the intent of wiping out the Palestinian population over a long period of time so that the Jews can have all of Israel as God intended, then they will expand their colonial empire from the Nile to the Euphrates as the Bible says and destroy all who stand in their way? Yes, I am saying that argument is as credible those nonsense theories. Sorry if I sound condescending, but if you want something treated as fact in Misplaced Pages it '''must''' conform with ] and not fall into the category of ]. If you don't like Misplaced Pages's policies, you have two choices:
::::::::#Don't edit. There's no mandate from god or from your government (wherever that may be) compelling you to edit Misplaced Pages.
::::::::#Propose changes to policy. If you think policies get in the way of Misplaced Pages being successful and accurate, propose changes to them. Policies are not implicitly "perfect", but they're all we have at the moment. If you have a better approach or a better way, propose it and see if it gains consensus. Either way, if you want to edit you have to follow the policies that do have consensus.
::::::::Editting Misplaced Pages is a privilege, not a right. Whether or not you follow policy in your editting is the prime criterion for determining whether or not you deserve that privilege. Just because it is given by default does not mean you are owed it; and if you don't like our policies, and decide that you don't want to follow them while editting, it may be taken away. ] (] | ]) 14:09, 16 March 2007 (UTC)
:::::::::Telling me "don't edit" is inane. Please don't be a total ] and tell me to go away. How would you like it if I told you "don't edit". Your belief that ] is ] is just that; a belief. Also, last time I checked, this is the village pump regarding policy, so instead of saying "follow policy", why don't we ''discuss'' the policies instead? That's the whole fucking point of even bringing this up.
:::::::::Also, I don't like your condescending attitude (as evidenced on this page) towards me. Please read ]. Thanks. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 16:30, 16 March 2007 (UTC)
Even ] should not have "allegations" in the title. It's superfluous, non-neutral and unprofessional. We should write in an objective style without implying a point-of-view. — ] 21:09, 15 March 2007 (UTC)
*Roughly speaking, if the subject of the article is ''just'' the allegations, then it may be appropriate to use that in the title - realistically, ] should be a subarticle of ] - where the parent article explains what it is, while the daughter article talks about who's been accused of it, why they've been accused, how they've responded, et cetera. Generically, you'd only split off the daughter if the parent is too big. Labelling '''everything''' with qualifiers like ''allegations'' because the subject isn't completely agreed upon is dumb, because '''no''' subject is completely agreed upon. Would anyone take the encyclopaedia seriously if we had an article called ] with ] as a redirect to it? And yet generically putting ''allegations of'' in the title of contraversial articles will lead to that sort of thing - if you dig, you'll see ''every'' article is contraversial - ], ] and so on ... ] 21:10, 15 March 2007 (UTC)
*Having reviewed it, I see ] is probably well titled - it just talks about who makes the allegations and why, it doesn't talk about the Israeli apartheid hardly at all. ] 21:13, 15 March 2007 (UTC)
**Indeed, a huge amount of the article is devoted to the allegations. ]<sup><small><font color="DarkGreen">]</font></small></sup> 21:14, 15 March 2007 (UTC)
***So Wily, do you think it is permissible to separate ] from ]? And also, should then, conspiracy theorists be allowed ] (the content could be merged from ]) That's even more interesting of a title which raises questions. Can we have an ] article as well? --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:19, 15 March 2007 (UTC)
****I don't know enough about the subject to say whether ] would place the article at ] or like ] or whatever. Generically, if ] got too long, you might need to spin out ] - although again, I'm not sure this is the preferred term per ]. Maybe it is. I think I understand the generic issue here because I've seen it come up in other places a few times, but I don't know enough about Israeli politics to make off the cuff specific statements. ] 21:28, 15 March 2007 (UTC)
****Of the above examples, ] seems like it shouldn't have allegations at the end, for instance. ] 21:30, 15 March 2007 (UTC)
***Going even further with this point, there's even ]. Can we have ] as well? --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:20, 15 March 2007 (UTC)
****If you can't differentiate between historical fact and political rhetoric, then there's hardly a point in responding. The Holocaust was a terrible historical event. "Israeli apartheid" is a political epithet. Please try to use less egregiously offensive and, frankly, silly arguments in the future. Thanks. ]<sup><small><font color="DarkGreen">]</font></small></sup> 21:21, 15 March 2007 (UTC)
::::By making an article about a subject, we are making an implicit claim that it exists, and that claim must pass the acid test of ]. '''If it cannot pass that acid test, it cannot be on Misplaced Pages'''. "Israeli apartheid" cannot be verified to exist, and therefore an article suggesting it does has no place here. We can, however, discuss the allegations made by some that it does exist, which is what we do. ] (] | ]) 21:23, 15 March 2007 (UTC)
:::::I completely disagree with your "implicit claim that it exists". We have articles on ], ], etc. etc. and not ], ], etc. etc. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:28, 15 March 2007 (UTC)
::::::The subject of an article could exist in fiction or in popular thought--The only thing that matters here is that it can be verified that it exists therein. I can verify, by checking the first ] film, that there is indeed a character called ]. I cannot verify, however, that "Israeli apartheid" exists in any world, real or fictional. Remember, ]. ] (] | ]) 21:36, 15 March 2007 (UTC)
:::::::Israel apartheid DOES exist in popular thought. Many notable scholars have used the term. Also, just because it's not popular ''where you live'' doesn't mean that it isn't popular in other places. Again, an example of ].--<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:41, 15 March 2007 (UTC)
*****"If you can't differentiate between historical fact and political rhetoric, then there's hardly a point in responding. The Israeli apartheid is a terrible historical event. "The Holocaust" is a political epithet. Please try to use less egregiously offensive and, frankly, silly arguments in the future. Thanks."--<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:25, 15 March 2007 (UTC)
So...are you proposing a page move or what? If you are, just make your proposal at ] and be done with it. The discussion here seems more like soapboxing. --] 21:30, 15 March 2007 (UTC)
::I'm not proposing anything, besides '''consistency'''. I don't want to swarm ] with several hundred pages with "allegations" in them. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:38, 15 March 2007 (UTC)
:::"Consistency" isn't really something that can be proposed as a blanket rule of all articles. "Allegations" is appropriate when the topic dictates it, there's no reason all or none should have it. What are you hoping to accomplish, getting the word removed from articles that have it, or adding it to others? --] 21:42, 15 March 2007 (UTC)
::::As I said, either they all have "Allegations of" in their titles, or none of them do (except in legal uses of the term). Either way is fine with me. (but admittedly with a bias towards those words being removed). --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:47, 15 March 2007 (UTC)
:::::Even if you could somehow define "they all" whatever that is (All articles? All articles anyone disputes?), it's never gonna happen. You're tilting at a windmill here (or at least making your stink somewhere trafficked enough to get your ranting read by a few people). Nothing to see here folks, let's stop feeding the troll. --] 21:51, 15 March 2007 (UTC)
::::::Any article that has <s>]</s> ] disputes should have "Allegations of..." in the title heading. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:53, 15 March 2007 (UTC)
:::::::Any article that has ] disputes should be brought to ], and then the matter should be settled. ] 21:58, 15 March 2007 (UTC)
::::::::My mistake. Didn't mean to have the "WP" showing.--<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 22:03, 15 March 2007 (UTC)
::::::Also, don't be a ] by accusing me of being a troll. I have been on Misplaced Pages for quite a while now, and have no history of blocks. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 21:55, 15 March 2007 (UTC)
I do not know where this is headed. but it seems to me that there are very clear cases where the word "allegation" can be used. Leave these to be discussed in the specific articles. ] <small>]</small> 21:34, 15 March 2007 (UTC)
Here's how I think we should make the distinction between allegation and a fact.
*If the event/condition/issue is debated by '''reliable''' (preferably scholarly) sources, then it should be an "allegation" or "controversy".
*But if the event is disputed only by wiki users, on unreliable sources, then wikipedia considers it as fact, but gives all POVs due weight.
What do you gusy think about that?] 22:00, 15 March 2007 (UTC)
**No, if the article discusses ] it should be named ] - if it discusses allegations about X, who makes those allegations and why, they history of doing this, then ] should be used. ], for instance, should '''not''' give a history of the development of Rienmann sums - ] or ] should do that. Meawhile, an article about how ] claims calculus doesn't exist because otherwise he won't meet course requirements at the ] that results in a lot of press coverage might reasonably be titled ]. ] 22:06, 15 March 2007 (UTC)
Wily, that sounds about right. But look at the ] article, which is filled with allegations that Islam is antisemitic. What do you think of moving it to ]?--<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 22:09, 15 March 2007 (UTC)
**I think you're on to something, but don't know if I follow your point on "But if the event is disputed only by wiki users, on unreliable sources, then wikipedia considers it as fact" . Can you elaborate? ] 22:08, 15 March 2007 (UTC)
***That part is right, but the first point isn't. The article should only ] if it '''ignores''' the subject and only talks about the debate about whether or not the thing exists. ] should '''not''' have the population of North America - that's rightly placed in ], but the debate about whether Columbus was in a new land or Japan might reasonable be titled ]. ] 22:15, 15 March 2007 (UTC)
****Alright, I think I understand your view now. I'm sorry if I come off as condescending by asking too many questions. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 22:21, 15 March 2007 (UTC)
*****Not at all - better to ask too many questions and understand each other better than necessary than the reverse. ] 22:23, 15 March 2007 (UTC)
(Resetting indent). There's an important distinction here. At least 90% of the facts that give rise to the idea of apartheid are not under dispute - characterizing it as "apartheid" is an ''interpretation'' that by its very nature is subjective. The Holocaust is a proper name for a series of specific events that are accepted by 99.99% of anyone who calls himself/herself a historian. (Oh, and Noam Chomsky quite clearly holds fringe positions, and isn't even a historian, nor - as it turns out - such a great linguist). --] 00:29, 16 March 2007 (UTC)
*Hey, just because Chompsky is terrible at a lot of things doesn't mean he's a bad linguist - the reason people listen to him when he hasn't a clue what he's talking about is ''because'' he's such a good linguist. Anyways, I sort of agree - realistically, ] should redirect to ] or whatever, not ], which seems to be the right article at the right place. ] 00:44, 16 March 2007 (UTC)
I've long believed that we should avoid using the word "allegations" in article titles. There will obviously be the need for some exceptions (eg. the 1993 Michael Jackson article), but the word is too easly co-opted for political ends.
The ] title is a bad compromise, and was chosen during highly politicized negotiations last summer. At the time of the article's creation, the concept was relatively marginal. Since then, it has been referenced by a former American president, a United Nations report, and countless journalists. And yet, the "allegations" title has been retained, due to ongoing political divisions on the page itself.
It may be noted, by way of contrast, that the disputed concept of ] is not referred to as ], notwithstanding similar objections that have been raised around the concept's viability. ] 03:54, 16 March 2007 (UTC)
CJCurrie, that's a good point. I've added ] to the list uptop. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 04:07, 16 March 2007 (UTC)
: Categorizing the Holocaust as an "allegation" undermined your own cause. Speaking of which, this whole proposal is an attempt to make a ]. ←] <sup>]]</sup> 10:00, 16 March 2007 (UTC)
::Again, important distinction here. The term "New Antisemitism" doesn't attribute antisemitism to a particular group, or entity. If the title had been ] (and I'm not claiming he's antisemitic), the comparison would have been apt. --] 10:40, 16 March 2007 (UTC)
::Don't attack the user, who is not (at least here) violating ] - he's trying to make a good point in a constructive, nondisruptive way. There '''is''' an inconsistancy that comes from editors who try to apply ] without having read it. ] 13:16, 16 March 2007 (UTC)
:::Getting away from what is by definition a POV argument... let's look at this with complete dispassion: In naming articles on Scientific topics, we do not add "Allegations of..." in front of theories held to be factual by mainstream consensus. We should do the same for historical events (or theories) held to be factual by mainstream consensus. Since the vast majority of historians hold that the holocaust did in fact occur, we should not lable it as an "Allegations of..." article. Now, there might be some argument that the opposing view could be an "Allegations" article (ie "Allegations that the Holocaust did not happen")... except that such an article already exists in a much more NPOV manner as ].
::::In fact, that's why I tried to talk about topics where ] sound funny. But I will say on scientific topics, we don't use ] for non-mainstream stuff either, or even false stuff. ] is not ], ] is not ], ] is not at ] and so on ... ] 15:22, 16 March 2007 (UTC)
:::I do think we need to think about the propriety of having any "Allegations of" articles... so many of them are thinly veiled POV forks... but that is a different issue. ] 13:36, 16 March 2007 (UTC)
Blueboar, I understand your concerns. But what about science which has mainstream consensus among scientists, but not among the general populace? I think it would be incredibly silly and stupid to have an ] article. As gracenotes said, I think that if there is relevant, sourced, notable dispute of a subject, then the article should not allege it as a fact. For instance the holocaust is considered fact by the vast majority of historians. But there is a notable minority which disagree with the extent of the holocaust. But that does not mean that the ] article should be moved to ]. And the holocaust itself is such a controversial subject that a move to "Allegations..." would be offensive. And that is my point with the Israeli apartheid article. Most historians agree that Israel has isolated and separated the Palestinians in the occupied territories. But there is a notable minority (mostly from the United States and Israel) that claim there is no persecution of Palestinians. But moving the article (as it currently stands) to "Allegations..." is offensive. As user ] earlier above said: ''"Those who use it are not alleging that Israel is an apartheid state, they are insisting it is. That term and its associated debate deserve representation in an article titled after the concept itself."'' --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 14:12, 16 March 2007 (UTC)
:Those who use the phrase are still making allegations, regardless of whether or not they believe them to be true. ]<sup><small><font color="DarkGreen">]</font></small></sup> 14:56, 16 March 2007 (UTC)
Also, I find the ''allegation'' that I am violating ] to be entirely self-defeating. The whole point of the Village pump is to discuss issues BEFORE doing something major. If I had went and move all those articles to "Allegations of..." (or vice versa), that would have been a ].--<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 14:15, 16 March 2007 (UTC)
I've found this: ]. Added to top.--<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 14:29, 16 March 2007 (UTC)
:You forgot ]. I added it for you. ]<sup><small><font color="DarkGreen">]</font></small></sup> 14:56, 16 March 2007 (UTC)
Thanks. If you find anymore, feel free to add them. --<font color="red">]</font><font color="green">]</font><font color="pink">]</font><font color="blue">]</font> 14:59, 16 March 2007 (UTC)
The article ] is, strictly speaking, about the allegations rather than the actuality of any discrimination or colonialism which would be better served by an article entitled something else. At least, that was the reason behind the writing of the article by my understanding. That isn't even considering the compromises that reaching that title entailed. ] is about the neologism, ] unfortunately conflates a neologism with a real phenomenon along with allegations of the phenomenon, and ] is similar. --] 20:21, 16 March 2007 (UTC)
:I'm not quite sure why ] is included in this discussion. The article is admittedly problematic - it's a neologism used almost entirely by blogger-activists and promoted in a self-published video essay by an academic working in a personal capacity as a political activist. The notability of the neologism, the video essay and the academic's activism is questionable to say the least - it emphatically isn't widely used or recognised beyond the blogosphere. (See ] for details - comments from other editors would be very welcome.) However, it seems to me to be in a rather different category from the one that Kirbytime sets out above. -- ] 02:00, 17 March 2007 (UTC)
::Although the article itself states that it is about the word "Pallywood", reading the discussion page it seems clear that many users including SlimVirgin and Leifern have decided that they want the article to be about alleged incidences of what might be called Pallywood, hence the dispute about referencing articles that don't even mention the term (e.g. and . This is extremely problematic as Misplaced Pages really shouldn't be adopting partisan neologisms as the titles of articles about things, unless the article is about said neologism. It is one of the main source of conflict on articles such as ] (where the same editors consicuously take the opposite view insisting that the sources ''must'' include references to Israeli apartheid) and ] and ]. --] 14:02, 17 March 2007 (UTC)
I think it's time to put all of the "Allegations . . ." articles up for Afd, as they all violate our rules against ], codified at ]. </font><small><span style="border: 1px solid #F06A0F">]]</span></small><font color="#ffffff"> · </font> 21:03, 18 March 2007 (UTC)
=== Straw poll ===
Sign under the statement with which you most agree.
====The article titles, as they currently stand, should be changed in some way====
====The article titles, as they currently stand, do not need to be changed====
====Undecided====
====Comments====
==] and ]==
{{seealso|#Proposal for a new logo for policy pages|Misplaced Pages talk:Attribution#Individual sections need tagging}}
{{done}}
:I came across the above template (]) today and noticed how it uses the same ] that ] uses. I created a ] and edited it into this template to reduce confusion as we're now starting to tag ] (on the right side) using this same green check. Does doing this make sense? {{User:Netscott/s1.js}} 21:58, 15 March 2007 (UTC)
::Personally, I can't see how using a green tick in more than one context will cause much confusion. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 22:03, 15 March 2007 (UTC)
::I support keeping it green unless there can be specific cases pointed to where there has been confusion. The fact that there ''might'' be confusion is not a good reason to change it, as I think that's very unlikely in my opinion. ] 22:06, 15 March 2007 (UTC)
:::No, it just "waters down" the significance of the green check in terms of policy... like, "oh I see that everywhere, interesting"... big deal. {{User:Netscott/s1.js}} 22:11, 15 March 2007 (UTC)
::::But how many people instantly associate a big green tick with Wikipolicy? -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 22:31, 15 March 2007 (UTC)
:::: Only editors that have been around long enough.... ] <small>]</small> 22:34, 15 March 2007 (UTC)
:::::Indeed, which forms the question, why is a plain check mark denoting Wikipolicy? Something more distinctive should be it appears. {{User:Netscott/s1.js}} 22:37, 15 March 2007 (UTC)
::::::Because we aren't trying to convey the intricacies of Misplaced Pages policy via an icon. Rather than being distracted and focusing their attention on an image file, readers are supposed to actually ''read'' the tag in question. After they've done that, the simple green or blue graphic serves as a visual cue. —] 23:06, 15 March 2007 (UTC)
::::::: Sorry, David, but I do not buy it. The reluctance to improve upon our graphics is something that I cannot accept. Long-standing magazines change and evolve their layour and graphics to become more appealing to their readership. Why we should not do the same? ] <small>]</small> 23:09, 15 March 2007 (UTC)
::::::::The above argument is based upon the fallacious assumption your proposed icons are unequivocal improvements over the status quo. Has it occurred to you that people simply prefer ]'s checkmark? —] 23:40, 15 March 2007 (UTC)
::::::: If the consensus is to stay with the tick-mark, then I will work in creating a more modern version of that tick mark. Will have some samples later tonight. ] <small>]</small> 23:11, 15 March 2007 (UTC)
::::::::How is Gmaxwell's version outdated? —] 23:40, 15 March 2007 (UTC)
:::::::David Levy, I think it has been illusrated to you here that for new editors the green check likely has little significance in terms of its appearance on a page needing to denote that the page should be taken more seriously. No? {{User:Netscott/s1.js}} 23:11, 15 March 2007 (UTC)
:::::::::Has anyone ever been confused or commented that they were confused by it? I mean that is the real issue. ] 23:19, 15 March 2007 (UTC)
::::::::::Quadzilla, if you've got a moment read ] and you'll likely better understand why this discussion has come about. {{User:Netscott/s1.js}} 23:22, 15 March 2007 (UTC)
:::::::::::I don't believe that the use of similarly sized green checkmarks on one project page (or even the widespread adoption of this convention) is going to confuse people, and your apparent belief that the policy icon is intended to be perceived as sacred is incorrect. On the contrary, it's important for readers to understand that policies should be followed because they make sense, ''not'' because someone has applied an arbitrary symbol.
:::::::::::Nonetheless, we ''could'' change the {{tl|done}} and {{tl|not done}} tags to use ] and ]. —] 23:40, 15 March 2007 (UTC)
::::::::Again, the icon's purpose is ''not'' to convey the intricacies of Misplaced Pages policy. That's what the '''words''' are for. If users don't bother to read the template, no image file is going to help (and anything fancy will only distract them). The color-coded checkmarks exist primarily to help identify the tags in the future.
::::::::I don't, however, agree that the checkmark has little inherent significance. I just don't believe that it's possible for a graphic file to accomplish the feat that you evidently believe it should. —] 23:40, 15 March 2007 (UTC)
I've read the recommended thread and still see no sign that anyone is reading the done checks down at FAC and thinking they are official policy. I believe this mistake is not being made so I don't see the need to change the check symbol on the done template. If there is some other reason to change the done symbol maybe I'm missing it. ] 00:46, 16 March 2007 (UTC)
:Exactly - the two contexts are so different, when is anyone going to confuse them. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 09:41, 16 March 2007 (UTC)
*Not a big deal really, but tick icons halfway past a page don't serve any particular purpose either. The term "policy shortcut" is misleading; shortcuts aren't policy, an entire page is policy (or is not policy, as the case may be). ] 12:41, 16 March 2007 (UTC)
::The idea behind the "policy shortcut" label is to inform people who follow said shortcuts (and enter the page without seeing the "policy" tag at the top) that they're viewing a policy. I'm not sure why anyone would interpret the phrase "policy shortcut" as a claim that the shortcuts themselves are policy; it merely means "shortcut to policy." —] 14:47, 16 March 2007 (UTC)
== Geographical locations and notability ==
I was recently editing some articles and came across a number of geographical locations (primarily unincorporated towns) that were tagged {{tl|importance}}. I seem to recall in the past several people arguing to keep such articles when they came up in AfD debates by saying that geographical locations are inherently notable and do not require additional "proof of importance" beyond the fact that they exist. I have been looking around in the policies and guidelines and I am having a hard time finding where it is stated that this is the case. Is it an actual policy somewhere, or is it merely consensus? If it exists in policy I would like to know where so that I can reference it. It would also be very helpful to know what the policy is regarding geographical locations and notability. Thanks! ] 23:28, 15 March 2007 (UTC)
:So ] is not notable enough for you? I say that tounge in cheek, as I don't think nearly every outhouse and barn is necessarily notable in every instance, but there can be some significant exceptions. On the other hand, unicorporated towns are something that is a real problem to determine notability. Some of these can be quite big, such as those found on ], because the entire island is considered one very large city, but it is divided into several geographic regions and neighborhoods that would normally be considered seperate cities anywhere else. In going through U.S. Census records, I've seen unincorporated areas having populations of close to 100,000 people. Of course, I've also seen incorporated towns with a population of just three families (I knew a 16 year old fire chief once from one of these towns).
:I don't think you can come to a good concensus on where to draw the line here, although if you had to mark some of these ''within'' the USA, I would suggest that statistical data must be available by the U.S. Census bureau for that geographical location, and a similar kind of standard could be used in other countries. I could imagine a tougher standard, but that is at least something to start with. --] 00:52, 16 March 2007 (UTC)
::Although it was marked "inactive" today, you might find ] and its talk page a good starting point.--] 02:33, 16 March 2007 (UTC)
::*It may be worth reinvigorating discussion on ]. Despite heavy objections from (mostly) a single user that objects to every notability guideline, LOCAL seems reasonably well supported as well as used in practice. ] 12:47, 16 March 2007 (UTC)
::::There could be other shades to this as well. See ], a resort city for which roughly two-thirds of the residents who share the ''Boca Raton'' postal address actually live outside the city limits in unincorporated ] land and have no right of access to city services such as police, firefighting, sanitation, or libraries. <font face="Verdana">]</font><sup>'']''</sup> 15:26, 16 March 2007 (UTC)
:::::Regarding Radiant's post above, I can confirm that it is used in practice, as I cited it in ] just the other day. I haven't been following the debate at WP:LOCAL, but one user's objection does not a lack of consensus make.--] 17:34, 16 March 2007 (UTC)
Thanks for the help thus far. I went and looked at ] as well as the discussion there, and it feels like there is still some need for clarification and consensus. I'm hoping to spark some discussion on the issue again, so I've commented on the talk page there. Would really appreciate any constructive thoughts and ideas anyone would have! Thanks! ] 17:34, 16 March 2007 (UTC)
The bot which created an article about every place in the US 2000 census was supported by consensus, and all articles which have come up for deletion have also met consensus keeps. It may not be posted in a policy anywhere, but there has long been consensus to keep those articles. A real place is important due to its existence, unlike most other things which fall under question about notability. You would need a strong consensus to delete them. ] 22:34, 16 March 2007 (UTC)
:I think you will find what you are looking for here: ]: "Cities and villages are notable, regardless of size." The general rule is that towns are notable, but things in the town like minor streets, buildings, etc. generally are not, with "notable" exceptions, of course. ] 02:03, 17 March 2007 (UTC)
See ]. ] 14:52, 20 March 2007 (UTC)
==Speedy deletion continues to help vandalism==
I now have two articles on my watchlist renamed and deleted. Such vandalism is from an outgrowth of some ridiculous racist edit war between South Korea and Japan. Someone moved both articles to a nonsense name and had it marked for deletion. Before editors of that article or I can even revert or discuss the deletion, all the content is deleted and the article history is now gone. The first time it happened I wrote about it on this page, but nothing has been done to improve the situation. I don't even know what the original article is about (or its title) because all of the information is gone! Please have more qualified admins to handle speedy deletion, change the policy, or add some sort of history to a deleted article. The speedy deletion process is currently quite ridiculous and puts too much power into a single admin edit. ] 01:22, 16 March 2007 (UTC)
:I'm finding this a bit opaque without some background and details to track what went on, and without that it's hard to discuss the merits of your complaint. You can't remember either article's name? The original names before the moves? Any discussions on your or someone else's talk page where the articles might have been linked? With the names we could look at the ], see in the edit summary some information on why the articles were deleted, who deleted it, etc. Administrators also have the ability to look at deleted articles to get a better understanding. Note also that you can ask for deletions to be reviewed at ] (but this cannot be done without pinpointing the actual article that was deleted).--] 02:29, 16 March 2007 (UTC)
::This nicely indicates the roadblocks the system has inadvertently thrown in the way of editors who think they have a legitimate concern. It should not be possible for a single possibly biased admin to remove articles, it should be possible to easily find out for oneself exactly what has happened to a deleted article, there should be an essentially automatic process for looking at it without making it a personal favor, and there ought to be a much easier policy for reviewing speedys. DelRev is suitable perhaps for AfDs where they re is process to be discussed, and reasons on record, but not for most simple deletion of inappropriately deleted speedies. And there should be a regular procedure for reviewing the records of admins who make speedies that do not hold up. without making it into a major RfA matter. Most dissatisfied eds. will not know how to appeal, or will think --whether or not correctly -- that the "regulars" may not pay attention to them. Many will not even complain. All the zealots complain--the ordinary guy just goes away disappointed--
::You can try checking ] if you're an admin. Since I'm not an admin, I can't be sure what the original article was, or if it even exists anymore. I know for sure an established article was moved to a nonsensical name and then deleted. Hopefully the admins who failed to cle:an up the vandalism fully at least restored the original article, since I have no way of knowing unless I backup names by hand. I'm sure most of us have dozens of various articles in our watchlists which can't be recited by memory (the only articles I keep track of personally are the ones I create). I'm not arguing against speedy deletion in general, but this special case needs to be cleared up, as I don't appreciate garbage or offensive trash articles in my watchlist replacing legitimate ones.] 05:28, 16 March 2007 (UTC)
:I am ''not'' commenting on the merits of this particular case, about which I know nothing. ''']''' 04:14, 16 March 2007 (UTC)
::That's odd, because other than the passing reference to this case, that paragraph is mostly a lot of words saying not very much at all. ] <small>] </small> 04:49, 16 March 2007 (UTC)
:::It's not the individual case that I wish to discuss, it's a loophole which is being exploited. A vandal moves an established article to a nonsensical name and edits it to look like nonsense. It is then flagged for speedy deletion. An admin will then proceed to see the nonsense and delete the article without properly looking at where the article actually came from. Anyone who has this in their Watched articles will only see the nonsense article name, not the original. I cannot keep track of all my watched articles by memory alone, and rely on the watched article feature to track vandalism and contentious issues. This bypasses the eyes of editors of that article, and relies on 3rd party admins to clear up, who are not (As I have two examples of this on my watchlist). Even if the article is reverted, editor's watchlists will not be reverted appropriately unless a moveback and restore is done. As of now it's not a popular method of vandalism, but I'm asking for a system to be implemented to prevent this from happening. A full history isn't even needed, but at least a move history should be seen on the article history, or the admin should always leave a report on the talk page. ] 05:19, 16 March 2007 (UTC)
::::Hit to "display and edit the complete list" on your watchlist. That will show you every page you've ever watched, even those that have been deleted will be there as a redlink. ] <small><sup>]</sup></small> 05:21, 16 March 2007 (UTC)
:::::The redlinked name is NOT the original article name!] 05:29, 16 March 2007 (UTC)
::::::] only has one deleted edit, it looks like ] was moved there as vandalism. However, it was moved back. That was months ago, so it doesn't relate to this situation. However, if you can give me the names of the articles that were deleted, that's just as helpful, I can view the history there. But give us ''something''! ] <small><sup>]</sup></small> 05:35, 16 March 2007 (UTC)
:::::::Thank you. So the issue has little to do with speedy deletion as I originally though, and more to do with reverting a move. Is there anyway for a non-admin to check the previous article name of a deleted article in a watchlist?
::::::::Unless the article name gives hints, no. This would require seeing the history, which is restricted to admins. ] <small>] </small> 05:49, 16 March 2007 (UTC)
::::::::As to what I think might be confusing you-if a page is moved by a vandal, and moved back, it leaves a redirect at the location the vandal moved it to. Since this redirect is generally inappropriate, it's ]. However, only one actual edit (the move vandalism cleanup) is actually deleted, the rest of the edits are moved back to the old location, and remain in history, just the same as if it'd never been moved. It's basically just a little more complex form of reverting vandalism, but it doesn't harm the page or its history. ] <small><sup>]</sup></small> 06:04, 16 March 2007 (UTC)
:::::::::Even so, there needs to be a way for nonadmins to get this information without having to beg a admin for such trivial info. I understand the need to block illegal and policy breaking content from Misplaced Pages, but there needs to be accountability with deleted articles. Nonadmins make up the bulk of editors and there needs to be more transparency to see when mistakes are made. Even a simple "Bob the admin deleted this article due to policy violation" template would go a long way, and would also help prevent the recreation of articles that have no corrected policy violations due to unavoidable ignorance of a nonadmin. Seeing a completely blank deleted article (with no signs that it was even deleted) impedes legitimate work of nonadmins. As for the bugged revert, which was my problem, perhaps another function should be given to admins to revert any dynamic links along with the cleanup, since doing it by hand is failing to prevent it. Japan is a well known article, but I also have lesser known articles which might take years before I run into again by random surfing. Also such articles need the few watchful eyes it has. ] 06:13, 16 March 2007 (UTC)
::::::::::The information ''is'' available, see ]. For example, this is the example you gave, showing it was moved from and back to ]. Generally, when you come across a non-existent page, you can click on the "check the deletion log" link that appears on that page (in this case though, it's helpful to change it so you see not just the deletion log, but the move log as well). --] 06:15, 16 March 2007 (UTC)
== Good Article promotion ==
I have a serious issue with the promotion of articles to Good status, which no one has been able to address to my satisfaction. I am concerned with the fact that a GA candidate can be passed or failed by a single editor. Even speedy deletes have the grace of two editors, and AFD discussions rarely close with less than three contributions. I would like to know in which forum I could pursue this discussion with the end to change in GA policy. Thanks. ]] 06:26, 16 March 2007 (UTC)
:If you have a problem with a specific Good Article, bring it up at ]. I disagree that the process needs any changing. The promotion of an article as a "Good Article" makes ''no changes at all'' to the mainspace appearence of an article. Good Articles are not listed on the main page, and the status as a Good Article only appears on an article's talk page. The analogy to the deletion processes is faulty, since the ] and ] processes make rather drastic changes to an article. The process is decidedly unbeaurocratic, and this is deliberate and intentional. The ] is clear and unambiguous, and if you ], then one should trust that they know what it takes to review and promote or fail a Good Article. It is my experience that other Good Article reviewers take their jobs quite seriously, and are very throrough and judicious about reviewing articles and applying the Good Article Criteria (I am a frequent reviewer, and I feel I am both throrough and judicious as well). Again, if it is a ''specific article'' you have a problem with, then please go to ] to see what to do about this. If it is a problem with a ''specific editor'' who is promoting or failing articles in an inappropriate or disruptive manner, talk to them at their talkpages first, and if the behavior does not cease, then report them at ] or ]. If you feel that in general your fellow editors should not be trusted to make these decisions, see ]. --]|]|] 08:09, 16 March 2007 (UTC)
:Seconded. The GA process isn't an attempt to showcase the best of Misplaced Pages, but rather an attempt to promote "good" article before they advance towards FA or A class status. It is built primarily on trust. If you feel a certain decision or editor is being unfair, either may be a subject to a review. There has been a lot of discussion on the process ], which resulted in a consensus not to overhaul the process nor add any defined criteria on the reviewers themselves. '''<span style="background:#000">] ]</span>''' 11:34, 16 March 2007 (UTC)
*This pretty much demonstrates the pointlessness of "good articles". They're just "articles that somebody happens to like", and this has never really been different since the inception of GA. ] 12:42, 16 March 2007 (UTC)
**I quite disagree. If that were the case, there wouldn;t be any ] that one is supposed to apply. Good articles should meet ] and ] requirements for referencing, and should be free of images of questionable free or fair-use status. They should follow the Manual of Style and be reasonably representative of the current state of scholarship on the subject, not omiting any major points. Again, none of this has any basis on how much an article is "liked". To say so assumes that that the editors involved in said project cannot be trusted to make decisions on the application of said criteria, and are largely acting in disregard of the criteria for their own personal gain or betterment. That is a ludicrous example of assuming bad faith, if you ask me. If the criteria is being misapplied in specific cases, there are means of redress. But that does not mean the entire project should be ignored, scrapped, or insulted. --]|]|] 05:28, 17 March 2007 (UTC)
== abbreviations ==
I assume that ] means that if the spelled out phrase is also used "commonly," one has to prefer this over the abbreviation? At least that is what I get from "is almost exclusively known only by its abbreviation." Exclusively here sounds like I would need to have a hard time finding the spelled out phrase in scholarly articles for example, for me to not use it. ] 15:35, 16 March 2007 (UTC)
:Not exactly... Look at ]... while most people know that the company is actually "International Business Machines" it is ''more'' common to simply call it IBM. Thus we use the abreviation. ] 15:49, 16 March 2007 (UTC)
::In this case, they call themselves IBM, as a singular brand (it is a registered trademark), so it has moved beyond the abbreviation stage. This still doesn't explain the above policy though. Common name is only a guideline, not a policy. HP is still at ], so giving examples doesn't help. ] 16:11, 16 March 2007 (UTC)
== Shouldn't "Require Edit Summaries" be the default? ==
It just occurred to me that since meaningful edit summaries are not optional policy, perhaps the default for new users ought to be to require them? --] 17:28, 16 March 2007 (UTC)
:We had been discussing this higher up on this page and a forked post at village pump technical, now archived. See (above discussion) ], and the VP/T fork, (you have to scroll to the relevant section). Not much has yet come of it, but where multiple people come up with a suggestion separately, that says something about it in and of itself.--] 17:44, 16 March 2007 (UTC)
::Ooops! Should have looked harder. Thanks! --] 00:49, 17 March 2007 (UTC)
*This may be worth adding to ] by now. ] 13:35, 19 March 2007 (UTC)
== The spam list ==
My attention was drawn to an edit on my Talk page, & as I researched the facts around it, I became more troubled at what happened. Maybe I'm behind the times, coming from left field, etc., but I don't like what I have found.
First, I am against spam -- in Misplaced Pages, in my email, anywhere. No reputable business knowingly uses spam to advertise, pure & simple.
However, it appears that it is far easier for a website to be listed as a spammer than it is to remove it. In the case I encountered, someone on an IRC channel claimed that the website "touregypt.net" was identified as a target of a spammer. Another Wikipedian (who, I want to point out, was acting in good faith) acted on this claim & began to "delink" every link to that website, without regard to who added it; the editor obviously was working as fast as she could. (By "delink" I mean that a nowiki tag was inserted so that one could not click-thru; one could still follow the link by copying the text of the URL into the browser.)
As a result, in several articles, talk pages, & many other places where it was clearly part of the context we lost references (I believe several of these edits have since been reverted).
Note: I have no problem with IRC being used to quickly respond to emergencies. in this case, ifa spammer had been obviously adding links to this website in Misplaced Pages, alerting Admins to this fact would be very much appropriate, but then the site should be nominated for inclusion in the spam list, & discussion follow before it is added.
This editor was contacted by several established & knowledgable Wikipedias, who demanded an explanation. She explained about the IRC channel, & referred them to ], where the website had been listed without any sign of a discussion that I have been able to find. This forum for discussion is not well-publicized (unlike, for example, ]), & a Wikipedian can contribute for a long period of time without even knowing meta.wikipedia.org even exists. However, there is currently a petition by a number of Wikipedians (some of whom have demonstrated extensive knowledge of Egyptology) to remove this website from the spam list.
In short, four things happened that I think are wrong:
# This website was blacklisted on the basis of something said in off-Misplaced Pages locale. Not every Wikipdian has access to IRC, or chooses too use it. Further, in a recent ArbCom ruling, it was found that Misplaced Pages IRC channels are not part of Misplaced Pages. If you want to set policy for Misplaced Pages, do it on Misplaced Pages where the rest of us can be expected to participate.
# Unless it is clearly the work of a spammer, don't "delink" the links. This is not necessarily a subjective judgement call: there are some very simple rules one can follow:
## All of the edits are made by the same person;
## if it's in the "External links" section; or
## the link is added without regard to context.
# Concerned editors were forced to find out why these edits were made, then forced to find the location (which was unexpected) where they could participate in the decision process.
# Lastly, despite obvious clues to the contrary, they bear the burden of proof that the links are ''not'' spam.
As I said above, I admit that I may be out of the loop here. However, I feel that this is a violation of the spirit of Misplaced Pages -- where we discuss & create concensus upon matters. Some Wikipedians claim that they are smart enough to know when they can safely ] in order to improve Misplaced Pages; in this case, I think it is clear that rules were ignored & stupid edits were made which harmed Misplaced Pages. -- ] 17:48, 16 March 2007 (UTC)
:I, being another editor with interest in this particular deletion, am also upset by the way things were dealt with here. Hundreds of links, installed over years by numerous editors for the sake of citing content, should never be mass deleted, especially not because of some IRC discussion. This is yet another example of a systemic problem on wikipedia- very few or even one editor can do somthing, and the burden of proof somehow rests on those who object!<br>In this particular case, dozens of pages have been affected, and one featured article has been de-sourced in such a way that one could technically move to de-list it because of the removal of this "Spam". For pity sake, how hard it is to realize that specific citations by definition cannot be spam....? ] 22:44, 16 March 2007 (UTC)
::These mass deletions are quite destructive and senseless. It is unclear why touregypt.net was targetted, yet good work by many gets corrupted,- really an internal form of vandalism. I suggest that the criteria for the spam list need to be sharpened. ] 02:46, 17 March 2007 (UTC)
::May I say that Llywrch has very accurately delineated the issue. The blacklisting process, currently at the unvetted pleasure of individual administrators, appears to be flawed: see ]. Though www.touregypt.com does have a villas-for-rent spammy-sounding name, what is to be made of blacklisting the consortium of European national libraries - libraries.theeuropeanlibrary.org - the EU's official National Libraries site, brought to my attention by ], one of Misplaced Pages's most dependable editors? IRC continues to veer out of control, damaging Misplaced Pages at every thoughtless lurch. --] 02:51, 17 March 2007 (UTC)
:::Like has been stated on meta 50> of touregypt is advertising, and the site was designed to sell product. using spam as a ref doesnt mean that its not spam. quit your complaining about anti-spam we have identified and reverted numerous spammers, the theeuropeanlibrary.org has been massively added by employees of that group. The fact that more than one user adds links doesnt meant that its not being spammed if you have a issue with the meta blacklist take it to meta. en.wikipedia has no control over meta, or meta admins. so if you want to argue for your spam site please take it to meta as that is where it was blacklisted and all the huffing and puffing that is done on en.wiki means nothing TAKE IT TO META. ] <sup>(] • ] • ])</sup> 03:59, 17 March 2007 (UTC)
:::: May I assume that you were the person who decided on IRC that links to this website were spam? -- ] 04:06, 17 March 2007 (UTC)
::::Its clearly a meta issue. Please take it there. And ''IRC continues to veer out of control, damaging Misplaced Pages at every thoughtless lurch'' is jumping to so many FUD conclusions, I can't even begin to approach how wrong it is. ] <sup>]</sup> 04:20, 17 March 2007 (UTC)
::::: Discussion is currently ongoing on Meta. I raised this issue here out of concern that a decision affecting a Misplaced Pages project was made off-Wiki, & that the need to fix a problem on en.wikipedia must be taken to another Wiki -- if one knows the place, that is. That is why I omitted the name of the Admin who unknowingly started this problem, to focus on the utter indifference to transparency here. This is not an issue of a disgruntled user who lost a debate; it's an alarm set off by a long-term editor who sees the potential for mischief & harm here. -- ] 05:59, 17 March 2007 (UTC)
:::Warning, ] discussion to follow. ''So lets say I wanted to disrupt wikipedia. I mean really screw it up, not just the kind of page-at-a-time vandalism that gets a quick block and doesn't really do any damage. I mean the kind of systemic damage that could bring the site to its knees, doing across-the-board damage to hundreds of articles, included the best featured articles the site had to offer. Its quite simple. Simply find a domain that is being used by hundreds of pages, one that has a wealth of good information, a real honest-to-god, vetted, reliable source, and start spamming it. Everywhere. Behave like a spammer, drop links like "come visit my site for great poker action" or something like that, and leave links on hundreds of articles. But make the actual links to great reliable sources. Some well meaning editor or admin, already overwhelmed with the good work they do at wikipedia, sees what I am doing, and thinks that my link is genuine spam. Heck, if it quacks like a duck and walks like a duck, right? So my behavior gets the entire domain blacklisted... and suddenly hundreds of featured articles are left without reliable sources, pages cannot be edited until the "spam" links are removed, etc. etc. Sound unlikely, probably, but with thousands of well meaning, highly respected admins, I only have to sucker one of them and then sit back and watch the damage I started.'' It would appear that this kind of vulnerability exists, and all because of the way that the spam blacklist is handled. The very fact that the European Union official libraries site was blacklisted, the functional equivalent of the Library of Congress being blacklisted, shows that such vulnerability exists for someone to explout. Something has to be fixed, and fixed soon...--]|]|] 04:17, 17 March 2007 (UTC)
: Jayron, you have just described a ]. All the more reason to be concerned. -- ] 05:59, 17 March 2007 (UTC)
This discussion considers two seperate cases, which indeed show resemblance. Since I am involved in one of the cases, I will offer my view on this case.
When spam is being identified, first of all ''all'' links that ''that spammer'' added are being removed. There is no question whether that link is a good one or a bad one, these ''will'' go, per the english wikipedia spam guidelines:
<blockquote>{{main|Misplaced Pages:External links#Links normally to be avoided|Misplaced Pages:Conflict of interest|l1=Links normally to be avoided}}
Adding external links to an article or user page for the purpose of promoting a website or a product is not allowed, and is considered to be spam. Although the specific links may be allowed under some circumstances, repeatedly adding links will in most cases result in all of them being removed.</blockquote>
That is what happened with the links added by the COI spammers that added theeuropeanlibrary.org. AFAIK no links added by other persons were removed (if that happened, it happened in an external links section where these links are questionable anyway, per the english wikipedia guidelines on external links, "If the site or page to which you want to link includes information that is not yet a part of the article, consider using it as a source first." and I am sorry if that happened). Now theeuropeanlibrary.org is a good site, and a careful examination of the situation was made. At that time only 10 links to the europeanlibrary.org were available, and the only ones added at that moment were by the addresses which have a COI, clearly suggesting promotion of a site that was not yet linked on wikipedia. The edits by the COI-editor have been discussed with the editor, and s/he was pointed to the appropriate policies and guidelines. Since the spamming by these addresses continued nevertheless, the site was blacklisted on shadowbot.
As a further note, shadowbot reverts once, and adds a message to the users talkpage. If the user readds, shadowbot does not remove (except when in angry mode under a heavy attack, but then its operation is even more carefully monitored; that is an exceptional situation). Normally, repeated addition gets reviewed by shadowbots operators, and when appropriate, will not be reverted. The europeanlibrary did not get blacklisted on meta, the spam is not (yet) crosswiki (and even then, it might be really inappropriate to do that). But I could stuff some more beans in it, when you want your own site not to be used as a source, consider spamming your very own link across several wikis, that really helps the community forward (maybe wikipedia has to consider not using such a site as a source and keeping a lacune in its contents). I have suggested my contact at the european library to reconsider his/her stance, and I promised him/her that we would make sure the site gets removed from the blacklist when the COI-spamming stops (it will also be removed when shadowbot reverts too many (which may be 1) good edits to articles).
For touregypt.com: I have not seen the spam-records for this addition, but I am sure there are records for that. But when the spamming is cross-wiki (i.e. also on other-language wikis) addition to meta is considered. I will for now assume good faith and think that the person who added it to the meta-blacklist considered the site carefully.
Blacklisting on meta means, that the link can not be used in a document ''at all''; pages with that link can not be saved, even when the editor does not add that link at that very moment. When touregypt.net was meta-blacklisted a user provided the ''service'' to clean en.wikipedia from that link; otherwise other editors would run into the problem of not being able to save the page on wiki; that is completely besides the question whether blacklisting was appropriate (and the same user is already helping finding alternatives).
Blacklisting happens speedy, I am sorry, but first discussing for 7 days results in a lot of spam being added before something can be done about it (WP:SNOW?). That results indeed in some mistakes being made, we know that, and we are more than willing to correct the mistakes. Seen the layout and contents of the sites in question (and the style of writing and the purpose of the site in the case of touregypt.net) I expect that many facts stated there can also be verified with other sources. By the way, we don't have to provide a deeplink to an external document in a reference, if I state that Jennifer Couzin wrote an article about opening doors and native knowledge and add the reference "Jennifer Couzin, ''Science'', '''2007''', ''volume 315, issue 5818'', p. 1518-1519", anyone can find the source, and verify my statement, a deeplink is ''only'' a service and a nice extra for a non-paper encyclopedia.
So the only problem that stays, is that the system can be tricked/wikipedia can be disrupted (per the beans-case above), but that can be done with every policy and guideline we are working under here. Hope this explains. --] <sup>] ]</sup> 11:45, 17 March 2007 (UTC)
: Beetstra, you say that you haven't seen the "spam-records for this addition, but I am sure there are records for that." I respectfully ask that those records for this be produced, & either added to the discussion on meta, or a link added there to them, so that all parties may review the evidence. -- ] 21:44, 17 March 2007 (UTC)
::I have provided some data I could find on meta (). Hope this explains a bit. --] <sup>] ]</sup> 12:51, 18 March 2007 (UTC)
:::I also object to the removal and blacklisting of the Egypt links. Please restore them. ] 18:57, 18 March 2007 (UTC)
== What will it take to ban unregistered editors? ==
I know Misplaced Pages was started as a resource anyone can edit, but the fact is I feel it's time Misplaced Pages abandon this. Full stop. There has been simply too much bad-faith editing and outright vandalism by anonymous IPs and everytime this sort of thing hits the media, it makes all Wikipedianss look bad. Case in point: a vandal posted that the actor ] had died. Although it was caught and corrected and the article is currently locked down, it was too late to stop the AP from reporting on the situation: and in turn this story is appearing on forums (I saw it at TrekBBS of all places) where it's being used as ammunition by people who would like to see Misplaced Pages either disappear or become basically a clone of traditional published encyclopedias where only people with PhDs are allowed to contribute and articles take months or even years to be approved. As someone who regularly has to revert anonymous edits and who now treats every non-registered edit as "Vandalism unless proven otherwise" I feel a good 90% of the bad press regarding Misplaced Pages and it's alleged inaccuracies would be eliminated if we simply required people to get a username. There are vandals who do register, of course, and ] regularly shows nonsense articles created by registered users ... but they still comfortably fit within the 10% minority. ] 17:59, 16 March 2007 (UTC)
: How would requiring users to login first have prevented the Sinbad problem? --] 18:04, 16 March 2007 (UTC)
::I was wondering that too. A casual glance at ] indicates that having an account does little to prevent editors from making random nonsense articles. ] ] 18:06, 16 March 2007 (UTC)
:::The extra step it requires to log in discourages the spur-of-the moment "drive-by" vandalism, accomplished before thought sets in. Logging-in would not have prevented the Sinbad problem: it is quite simple to "create" a news story in such a fashion. I see no reason to assert that logging-in violates any core principles of "an encyclopedia that anyone can edit." I also feel that, under present circumstances, ''any'' article vandalized more than twenty times a month should be semi-protected for a limited period of months.--] 18:10, 16 March 2007 (UTC)
::::] --] 18:12, 16 March 2007 (UTC)
:::::What will it take? Oh, for the wheels to come to terms with the fact that there might be something justified behind all these "perennial" complaints. ] <small>]</small> 18:34, 16 March 2007 (UTC)
::::::A point of comparion: On June 4, 2005, a registered user revised the ] article (and a few others) to state that he was dead (]); after the hoax report was added to candidates for In the News, the item actually for six minutes before an apparently honest editor realized their error and . That was a much more serious slip than the Sinbad hoax, which (]) was reverted within two hours; I'm not sure whether vandalism can be consistently reverted any faster unless each article were to be on the watchlist of numerous contributors scattered over the globe. ] 22:00, 16 March 2007 (UTC)
:What will it take? An act of God, most likely, although an act of Jimbo may be sufficient. --] 19:10, 16 March 2007 (UTC)
:I think it will take an injection of common sense. — ''']]''' 19:13, 16 March 2007 (UTC)
:Of course there's something justified behind your complaint. That does not mean that ''your proposed solution'' to the complaint is in any way the correct one. Now, take for instance Wetman's suggestion earlier, that the category of "vandalisms which only occur because they are done on the spur of the moment before thought sets in" is a significantly populated one. ''If'' there was any way to show that yes, that category ''does'' account for a significant amount of vandalism, then the proposal to require logging-in to edit would be very seriously considered. However, I am aware of no such evidence, and I for one very much doubt that a significant amount of the vandalism we see from IP editors would have been prevented by the tiny amount of time it takes to register. I think if we reduced anything with your suggested change, it'd be the number of helpful edits made by casual browsers. -- ] 19:15, 16 March 2007 (UTC)
I have just been doing some recent change monitoring. Most of the anon IP edits were good ones, and by far the worst vandalism was from a logged-in user.--] 19:16, 16 March 2007 (UTC)
::I am a frequent recent changes patroller and a long-time vandal hunter, and it is my experience that something on the order of 90% of edits by IP addresses are good edits, and of the remaining 10%, 9% are good-meaning but poorly executed edits. Of the remaining 1%, about .9% are test edits of the "can I really do this" variety, leaving about 1 in 1000 IP edits as actual malicious acts of vandalism. To prevent what amounts to 90% of good edits to stop 0.1% bad edits seems like a very bad idea indeed. --]|]|] 03:58, 17 March 2007 (UTC)
:::OK, I wanted to make this marginally more meaningful, so I did one decidedly unscientific poll. I looked at the 50 IP edits found on the Recent Changes page made around 04:48-4:49 17 March 2007 (UTC) and I found:
:::*30 Honest-to-God good edits.
:::*8 poorly executed, but well intentioned edits.
:::*6 "Test" edits that were problematic, but showed no definite malice
:::*6 "Vandal" edits that showed (IMHO) a direct attempt to disrupt wikipedia in a malicious way
:::Even lumping the test and vandal edits together, that still leaves 38 edits by people whose interest was in directly improving wikipedia, or 76%. Not as good as I thought, but still a sizable majority. Still, would you rather throw out 38 potentially useful edits (or 30 really good edits) for the sake of 12 easy to fix bad edits? I am not willing to do that. As an aside, two of the "good" edits were actually IPs fixing vandalism: A doubly good job, in this context. --]|]|] 05:19, 17 March 2007 (UTC)
::::For a much less rosy picture with slightly more data, see ]. I'm still hoping someone will redo this at a more sane time of day (a lot of vandalism seems to happen while US schools are in session). ] 05:27, 17 March 2007 (UTC)
:::::Actually, your stats show a MORE rosy picture than mine. I found 76% edits(of 50) whose intent was to improve wikipedia by anon editors. You found 82%(of 250) that showed intent to improve. We can work with intent to improve. An new editor who is trying to improve wikipedia will learn the rules and eventually make better edits. Even if it is original research or unreferenced, that person is interested, and can learn how to do better research. Am I willing to scare of 82% (or 76%) of all potential new editors that can learn to improve wikipedia for the sake of keeping out the 18% (or 24%) who are here to damage? Not at all. Most vandals get bored, or find something better to do, and stop after a few weeks or months. Good editors, if nurtured and allowed to grow, can continue to contribute for years. I am not willing to give that up so I can hit the undo link a few less times a day. --]|]|] 05:41, 17 March 2007 (UTC)
::::::I wish I'd kept better track of the contribution quality when I did that, but looking at 250 diffs is tedious ;) The disclaimer may well be the most important part of that data. A substantial majority of those 'content additions' - registered and unregistered alike - would have been reverted on sight if they had been made to any article I wrote, because they were full of original research and nonsense. I do agree with you in general, though, that the plurality, if not the majority, of anon edits are minor but productive contributions. ] 18:18, 17 March 2007 (UTC)
At the moment, what will it take to ban unregistered editors? Cold day in Hell, to be honest. I see plenty of well-intentioned edits from anons. The biggest problem I see from anons is inserting junk such as their pet's birthday, or adding their favourite entries to list articles. Not exactly "vandalism" ''per se'', just a misunderstanding of what WP is. Vandals (of the kind that blank pages and replace them with "fuck you all, you suck cock", or add "and your mom" to serial prose) are still in the minority, and while that is still the case I don't see a reason to block them out - blocking article creation is enough. ] <small>] </small> 05:48, 17 March 2007 (UTC)
* I agree with Antaeus Feldspar: valid complaint, but I don't think requiring registration is the solution. In a way, unregistered users have less anonymity than registered users because their IP address is public. <span class="user-sig user-Quarl"><i>—] <sup>(])</sup> <small>2007-03-17 08:27Z</small></i></span>
:I figure, 90% of vandalisms are from IP editors - but 90% of IP edits are valid. --] 08:50, 17 March 2007 (UTC)
::It also depends a lot on if we count ] (which is, of course, 100% registered editors). If you think registering somehow prevents people from writing crap, have a look there. ] <small><sup>]</sup></small> 09:24, 17 March 2007 (UTC)
:::I figure IP edits '''should not''' be banned. After all, isn't Misplaced Pages "The 💕 ''anyone'' can edit"? What Seraphimblade says above is absolutely true. There is a lot of controversy surrounding IP editors, but many contributions made by IP editors are valid and important. I also agree with Seraphimblade when he says, "If you think registering somehow prevents people from writing crap, have a look there.]" ]<sub>(])</sub><sup>(])</sup> 18:13, 17 March 2007 (UTC)
:I'd suggest lowering the bar for indefinite semiprotection. There is a problem with some types of articles, especially pop culture articles, that are stable and therefore not widely watchlisted. And while there might not be a high volume of vandalism in absolute terms, the edit history might be 80% reverts. Semiprotecting this kind of page would be very useful. ] 18:39, 17 March 2007 (UTC)
:Whilst I disagree with the idea of banning IP addresses, I don't understand why Misplaced Pages can't still be "The 💕 anyone can edit" if it did. If you can get on the internet, you can create a wikipedia account, and therefore edit wikipedia. ANYONE (who has an internet connection) can. You don't even need an email address. However, I've noted that the IP edits tend to be honest. They're usually the ones that correct little details and the like. Registered users often register to stop their IP address from showing. IP users know that their IP address is going to show when they edit. Also, a lot of users only become users to create vandalism pages for wikipedia. ] <sub>]</sub> 21:12, 17 March 2007 (UTC)
::Exactly. Anyone who wants to join the "IP editors are vandals" crusade need only look at ]. ] <small>] </small> 23:07, 17 March 2007 (UTC)
== Changes to blocking policy ==
There is currently a push to change ] to allow short blocks without warning upon any incident of vandalism from IP addresses, and indefinite blocks without warning for any registered account that has only made unconstructive edits. Input would be appreciated at ]. ] 20:48, 16 March 2007 (UTC)
*That's not a change, we already do that. ] 13:31, 19 March 2007 (UTC)
== Mailing lists: are they an encyclopedic topic? ==
Are mailing lists encyclopedic? I was drawn to this questions regarding ], and the corresponding article. A question being raised in the afd is the existence of several other articles on mailing lists. ] doesn't mention anything specifically about this. So, my question to others is: what is the community's opinion on the notability/encyclopedic nature of articles on mailing lists? Can they considered worthy of a wikipedia article? What criteria should apply to them? Thanks. --] 08:08, 17 March 2007 (UTC)
* Mailing lists aren't all notable or all not notable; it depends. Slashdot is notable but most webforums aren't. I think it's the same issue as any other online forum/community and should be covered by ]. <span class="user-sig user-Quarl"><i>—] <sup>(])</sup> <small>2007-03-17 08:21Z</small></i></span>
* Stop looking for blankets. ]. ] 15:04, 20 March 2007 (UTC)
== Fix up the article before you add anything new ==
Shouldn't we have a rule that one ought to clean up an article before adding anything new to it? I've seen too many pages fall into disrepair because people keep dropping in their own contributions when there are still obvious spelling errors, citiation requests, pastel boxes, and just plain unwikified text. ] 18:32, 17 March 2007 (UTC)
: It's good practice, but what would it mean to make it a "rule"? - ] | ] 19:20, 17 March 2007 (UTC)
::Agreed - even if this was a policy (which it never would be), people would still add things. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 21:13, 17 March 2007 (UTC)
:::What if there was some guideline we could trot out when reverting new edits. We could say, even if the new edit was good material, reverted per WP:"FIXIT" or something and the new material won't be let in until the existing page is sound. ] 23:31, 17 March 2007 (UTC)
::::I don't think that would work. People have different gifts: some are copyeditors, some provide new material, some dig up references, and so on. Let each contribute in their own way. ] 23:51, 17 March 2007 (UTC)
:::: I edit conflicted with Raymond, but was saying the same thing. This is not practical. --] 23:54, 17 March 2007 (UTC)
:::::Fixing up articles is important, but it is not important enough to stop people from doing good-faith edits to improve the content of the article just because the article needs to be fixed. ] ] ] ] 03:24, 18 March 2007 (UTC)
: I'm favor of the intent, but not the enforcement. Having done a spate of adding information to a number of related articles, I can provide some feedback here. Sometimes I found it was simple to add information to an article: it was well-organized & needed little if any drive-by copy editting. Sometimes the article is such a mess that I refused to even touch it. And sometimes, it isn't until I clicked on the "save" button that I noticed a sentence or a paragraph that badly needed help; if I had the time, I'd go back, but then Real Life often intervenes (or ), & the article inadvertently suffers.
: Maybe we could mail cookies/biscuits to people who do what Squidfryerchef would like to see, as an incentive. -- ] 19:59, 18 March 2007 (UTC)
::How about fried seafood? ] 21:05, 18 March 2007 (UTC)
== This attitude has got to change ==
In the link ], {{Ut|Radiant!}} 'just blew off a well intentioned suggestion' that certain steps should be added to process, and damned the matter as ''a perennial suggestion that comes up once an month'', effectively closing the discussion with that judgemental dismissal. If he's right, that indicates there is a body of thought thinking similar to myself, that the current practices are ''very wrong'' to keep and retain good and knowledgeable expert editors which can otherwise move the project '''to a higher average quality'''. So I'm asking some Admin to set up a straw poll, on whether this, and further, that the voting be split into a section by whether the respondent is an Admin, or a regular editor. I have the utmost respect for that group of editors, and frankly feel they are the most victimized group within our community, but as a rule they are the most active and most influential. In this case, I feel short term self-interest may be biasing what is a better practice for the long term health of any Wiki project and the greater interests of the community as a whole need to be thought through carefully. This is a matter which BITES people and alienates them repeatedly, and should not be born because of convenience. Like a little gas-pedal pressure, it has great effects on the long term results--if held in place unchanged we'd see one result--if modified at some point (now, or at 90 ], etcetera) another different outcome. // <b>]</b><font color="green">]</font> 18:59, 17 March 2007 (UTC)
:I'm not entirely sure what you're trying to say here. Do you want a straw poll to decide whether admins should vote in a separate section to other users at CfD, or are you asking whether active editors of a category should be contacted when it's nominated for deletion, or is there an issue with the general way in that changes are made to policy? ] ] 19:59, 17 March 2007 (UTC)
*Well, the point is that it ''is'' a perennial suggestion that comes up once a month. So is censorship, for instance, and so is standardizing on English spelling, and so is everything else on ]. We have that page for a reason, you know. ] 13:30, 19 March 2007 (UTC)
== What qualifies for a WikiProject? ==
Are there any limits on what qualifies for a WikiProject? ] appears to have one participant, a person apparrently actively involved in the party; on the ] I had, some time ago, raised questions about notability that I don't believe have been addressed. I'm not going to fight to get the article deleted, but what (if anything) does it mean for this to be a WikiProject? - ] | ] 19:23, 17 March 2007 (UTC)
:3 articles and one user doesn't really make much of a WikiProject. Raise this on ]. The project is new, but there is a well-defined procedure for starting them. ] <small>] </small> 19:44, 17 March 2007 (UTC)
== Misplaced Pages a Laughingstock? ==
I for one have been too embarrassed and shocked at this Essjay affair over the last week or so to edit at all. Now that I can gather the ability to get on Misplaced Pages again I must ask the question that has been simmering in all our minds lately:
Is Misplaced Pages becoming a laughingstock? I mean, the Essjay matter has been reported on all media outlets, including the network nightly news. This sort of unwelcome attention can only attract a flood of people who deride Misplaced Pages. In fact, I think the ONLY coverage of wikipedia EVER in the media is negative, and plays up our shortcomings in being a reliable encyclopedia. And now academics, the very people who we need to approve of us, are so much further from ever doing that.
Furthermore, I would argue that the last high-profile snafu here, the Siegenthaler affair, has attracted more users who come here to deride us. While some people come to wikipedia curious about our bad publicity and eventually become bona fide contributors, I think the larger percentage of them come here to vandalize and cause trouble. Just think of how much vandalism and disruption have increased exponentially since 2005-06. Thank you for your time. ] 01:39, 18 March 2007 (UTC)
:If Misplaced Pages is becoming a laughingstock, then what do you suggest we do about it? ] ] ] ] 03:21, 18 March 2007 (UTC)
So you are agreeing with us that it is becoming a laughingstock? Or is that the general consenus anyway these days here? ] 03:23, 18 March 2007 (UTC)
:Well, my comment was not directed at whether Misplaced Pages is a laughingstock or not. As for your question, I would not go so far as to call it a laughingstock, but it is certainly seen quite badly by many people. ] ] ] ] 03:26, 18 March 2007 (UTC)
Well since you basically agree that Misplaced Pages is becoming a laughingstock, what do you think we should do about it? ] 03:43, 18 March 2007 (UTC)
''I think the ONLY coverage of wikipedia EVER in the media is negative'' - *rolls eyes*. Whatever. You obviously have some agenda and this thread appears to be a troll. -- ] 03:56, 18 March 2007 (UTC)
::By the way, what is the ], and what was the ]? ] 04:17, 18 March 2007 (UTC)
Stblebach, that last comment was not particularly helpful. Please be civil. ] 04:20, 18 March 2007 (UTC)
:If you're too embarassed to edit, then don't edit. I for one don't care what the rest of the world thinks about Misplaced Pages: I'm editing for myself. --] 05:07, 18 March 2007 (UTC)
::For my part, most of those I know have generally gone to Misplaced Pages when they need a quick bit of information, or a starting point for some in-depth research, just like one would use any encyclopedia. After all the recent events...wait, nothing's changed, the same thing still happens! So I guess not. ] <small><sup>]</sup></small> 06:03, 18 March 2007 (UTC)
:::Exactly. When doing serious research (as opposed to casual reading) Misplaced Pages is a great place to start, but a poor place to end. ] 06:07, 18 March 2007 (UTC)
To get an idea of recent reporting of Misplaced Pages, see ]. Some of it is critical, some of it is positive. That's always been the case. There's also a lot of coverage which doesn't get onto that page. Today I was reading my local TV&Radio magazine (the ]), and in an opinion piece on state housing there's a sentence "By international standards, New Zealand towns ... have a very low density of population ... according to Misplaced Pages". Some pages later, in an article on spam, the Misplaced Pages discussion page on palm oil is mentioned. Misplaced Pages has become an essential part of everyday life for many, who for the most part have never heard of Essjay.-<font face="cursive" color="#808080">]</font> 06:53, 18 March 2007 (UTC)
== Continuation of discussion of Essjay/Straw Poll 1 ==
The following is quoted from the discussion of ] at ]:
<blockquote>
Can we get an exact timeline here? He was appointed what, a week ago? This was a delayed scandal, really, I am pretty sure we knew he was "Ryan Jordan" before he was appointed to ArbCom. It just took a while before someone wrote the Misplaced Pages article and I guess everyone found out and this became a trainwreck. So I am currently thinking Essjay was appointed to ArbCom with Jimbo knowing about the identity thing. --] 14:30, 2 March 2007 (UTC)
:The situation was known on February 1, well before the ArbCom appointment, see ]. In fact, it was slashdotted on Feb 7 as well. It just didn't gain traction because Brandt has not yet mananged to browbeat the New Yorker into issuing a correction. It has been discussen on Essjay's talk page many times between then and now. Dmcdevit resigned on the 14th. ] 14:32, 2 March 2007 (UTC)
::Can you lead me to the slashdot article? I missed that article. ] 14:36, 2 March 2007 (UTC)
:::Hmmm. Let me look for it. ] 14:37, 2 March 2007 (UTC)
:::It appears as a comment in started on Feb 7. Commenter appears to be Daniel Brandt from all appearances. ] 14:40, 2 March 2007 (UTC)
</blockquote>
The exact comment by appears to have been at . — ] <span class="plainlinksneverexpand">(]|])</span> 11:35, 18 March 2007 (UTC)
It was noticed by January 11th, and I posted about it on essjay's talk page around february 5th. ] (]/]) 20:51, 18 March 2007 (UTC)
== XYZ in popular culture. ==
I think Misplaced Pages needs to make a statement and a policy on "___ in popular culture" or "_____ in fiction" sections. As it seems policy on them is currently entirely piecemeal and random.
Many articles (particularly mythological concepts) quickly acquire long lists of appearances in popular culture or fiction, the list eventually spins off to it's own page, then eventually gets nominated for deletion and is either removed or merged back into the original page and it all starts again.
I think it's clear that some policy decision needs to be made on this.
On one hand I think it's clear people are interested in the section, that they can be relevant and understanding sometimes means understanding how it is used in culture or fiction. But they are also very long lists, and have no promise to us that they stay manageable. If something was genuinely important in 700 different stories, it seems wrong to remove that information, although it makes an eyesore, I mean, no object promises to just be in 10 or less stories just to give us a nice looking "see also" list.
On the other hand, EVERYTHING ON EARTH has been referenced by family guy. And it is hard to see serious topics dwarfed by lists of every time apu on simpsons mentioned it. And making another page makes sense, but often the page eventually gets nominated for deletion as listcruft, maybe justifiably. Still, they are often lists many people helped write, that many people find interesting, and if they contain more than just a title they can even be encyclopedic to some degree (it could, for example be worth mentioning that Pan is referenced in a Shakespeare play, but if that is important, where is the line?).
Is there any sort of policy that could be written about this? so many pages have these lists, and they disappear and reappear pretty much at the passing taste of editors, growing until they grow ugly then either being deleted or splitting and growing again until they get unwieldy and end up deleted until eventually someone sees the page and says "ahh, this was an important concept in such and such anime" and throws a section in mentioning that, starting the whole cycle again.
Honestly, I don't know what I'd recommend, as people DO seem to want the information on the lists, and I think it may be some people's first wiki-edits adding something to them but at the same time they are horrible eyesores that are inappropriate in serious articles and separate pages of them are unencyclopedic listcuft. ] 19:20, 18 March 2007 (UTC)
What do people think?
:As much as possible, any notable reference should be spun as prose into the main article. For other pop culture items the stuff in the trivia section is often just some facts about the subject that don't "fit" in the main article. We need to keep those facts, it's part of the "work in progress" nature of article writing.
:Other times, a separate article is appropriate. I've made several, specifically to remove them from serious subject matter (like I care about a comic book reference when reading about the United Nations). It would be unfortunate if they were deleted as liftcruft, because they create an interesting and useful cross-reference point of cultural intersection. ] 19:01, 18 March 2007 (UTC)
I think a big problem is that things don't promise to be a pleasing length. If there are two important stories that feature such and such that makes it look nice, if there are 25, it makes a sprawling list that is unsightly and dwarfs the article itself, but it's not like it should be punished for having the audacity to appear in more things and be more culturally significant! ] 19:20, 18 March 2007 (UTC)
*If it's that long, you're better off pointing out that it's widespread (like the ], ubiquitous in movies) and citing a few choice examples that fit the rule. You need a source to attribute the rule to though. ] (]/]) 19:47, 18 March 2007 (UTC)
: If wonder if Owlofcreamcheese's concern be addressed by a rule that cultural references in certain shows (e.g., "Family Guy", "The Simpsons", etc.) be placed in their own articles, & references to that subject in those shows be discouraged. That way, first-time editors could be sent to these media-centric lists to make contributions, while significant pop allusions to a given subject or event could be kept. Now I wonder how many television shows have allusions to '']''. ;-) -- ] 20:34, 18 March 2007 (UTC)
::we're not a directory, though, and there's no value in just listing every reference. We're here to synthesize knowledge into a useful resource, not catalog every minutiae. ] (]/]) 20:53, 18 March 2007 (UTC)
:::Agree with Night Gyr. A page was recently deleted entitled ]. This painfully documented every occasion on which the author(s) had spotted a pair of boots on tv or seen mention in a publication. Such lists are so all-encompassing as to be worthless. What's next ... trousers in popular culture? ] 01:12, 19 March 2007 (UTC)
::::This has been a pet peeve of mine for a while, at least when done poorly. I've had to remove the sentence "Yul Brynner is mentioned in the song One Night in Bangkok" from the Brynner article numerous times because such a mention is so completely insignificant. It can't even explain why he's mentioned because there really is no reason, as far as I can tell. Anyway, I wrote about this topic on a subpage of mine, with examples of when references are significant, see ] for my feelings on this (] is a tongue-in-cheek look at a similar phenomenon). If nothing else we must put an end to this "so-and-so was once mentioned on some TV show" crap that finds its way into every article. I'm just imagining a list at the bottom of the Coca-Cola article that mentions every time coke has appeared been mentioned on TV, film, and in print (to the tune of 7 GBs of info). -] 01:44, 19 March 2007 (UTC)
::The fact that, when spun off as a separate ], such lists are immediately detected as listcruft speaks for itself. These lists of references to the word "nymph" don't just ''become'' cruft when looked at in isolation: they ''are'' cruft already, for no editing change has been made. The fact that a Simpsons episode alludes to the Odyssey is relevant to ''that particular'' Simpsons episode and should be linked there. It is ''not'' relevant at ]. Very hard concept to explain to the simple. --] 06:37, 19 March 2007 (UTC)
This problem (and IMO it is a problem) is even when when dealing with articles on sports cars. There seems no way to win the battle against "Appearances in video games" sections, even though these days (almost) every video game features (almost) every modern sports car, to the point that these sections become useless trivia. '''<font color="red">]</font><font color="green">]</font><font color="blue">]</font><font color="orange">]</font>''' 09:09, 19 March 2007 (UTC)
*Perhaps guideline ] is relevant. In general such lists tend towards the pointless, I mean come on every fantasy-style RPG has a griffon these days. ] 13:28, 19 March 2007 (UTC)
::I would ''really'' like to see some kind of general consensus on these kinds of things, as there has been a veritable rash of them appearing on AfD as of late. Sometimes I feel like a broken record trying to make the point again again again! It feels like a lot of users are interpreting ] as a prohibition on trivia ''sections'' but not trivia ''articles'' and are using the ] articles to circumvent the guideline. It is my understanding that the whole point was to reduce the amount of trivia fluff on Misplaced Pages, not to fork them off to their own articles. Am I in the wrong here? Admittedly I may have something of a bias against these sorts of articles but they simply do not feel like they have much of a place in an encyclopedia - at least as they stand.
:'''No''' -- whatever you think of LLMs, the reason they are so popular is that the people who use them earnestly believe they are useful. Claiming otherwise is divorced from reality. Even people who add hallucinated bullshit to articles are usually well-intentioned (if wrong). ] (]) 06:17, 2 January 2025 (UTC)
::There ''are'' some exceptions to the rule, and those are the ones that treat ] as real content rather than a repository for a list of appearences. ], for example, attempts to deal with the subject in an encyclopedic manner rather than spewing out an indiscriminate lists of every time the guy has shown up on the screen. Granted the article is in need of help, but I feel that it is ''immensely'' more valuable and encyclopedic than the run-of-the-mill pop culture articles that I believe are the source of this discussion here.
*'''Comment''' I have no opinion on this matter, however, note that we are currently dealing with a ] and there's a generalized state of confusion in how to address it. ] (]) 08:54, 2 January 2025 (UTC)
*'''Yes''' I find it incredibly rude for someone to procedurally generate text and then expect others to engage with it as if they were actually saying something themselves. ] (]) 14:34, 2 January 2025 (UTC)
* '''Yes, mention''' that use of an LLM should be disclosed and that failure to do so is like not telling someone you are taping the call. ] (]) 14:43, 2 January 2025 (UTC)
*:I could support general advice that if you're using machine translation or an LLM to help you write your comments, it can be helpful to mention this in the message. The tone to take, though, should be "so people won't be mad at you if it screwed up the comment" instead of "because you're an immoral and possibly criminal person if you do this". ] (]) 07:57, 3 January 2025 (UTC)
: '''No.''' When someone publishes something under their own name, they are incorporating it as their own statement. Plagiarism from an AI or elsewhere is irrelevant to whether they are engaging in good faith. ] (]) 17:29, 2 January 2025 (UTC)
* '''Comment''' LLMs know a few tricks about logical fallacies and some general ways of arguing (rhetoric), but they are incredibly dumb at understanding the rules of Misplaced Pages. You can usually tell this because it looks like incredibly slick and professional prose, but somehow it cannot get even the simplest points about the policies and guidelines of Misplaced Pages. I would indef such users for lacking ]. ] (]) 17:39, 2 January 2025 (UTC)
*:That guideline states "Sanctions such as blocks and bans are always considered a ''last resort'' where all other avenues of correcting problems have been tried and have failed." ] (]) 19:44, 2 January 2025 (UTC)
*:: ] isn't a guideline, but an essay. Relevantly though it is being cited at this very moment in ]. ] (]) 20:49, 2 January 2025 (UTC)
*:::I blocked that user as NOTHERE a few minutes ago after seeing them (using ChatGPT) make suggestions for text to live pagespace while their previous bad behaviors were under discussion. AGF is not a suicide pact. ] (]) 20:56, 2 January 2025 (UTC)
*'''No''' - Not a good or bad faith issue. ] (]) 21:02, 2 January 2025 (UTC)
*'''Yes''' Using a 3rd party service to contribute to the Misplaced Pages on your behalf is clearly bad-faith, analogous to paying someone to write your article. ] (]) 14:39, 3 January 2025 (UTC)
*:Its a stretch to say that a newbie writing a comment using AI is automatically acting in bad faith and not here to build an encyclopedia. ] (]) 16:55, 3 January 2025 (UTC)
*::That's true, but this and other comments here show that not a few editors perceive it as bad-faith, rude, etc. I take that as an indication that we should tell people to avoid doing this when they have enough CLUE to read WP:AGF and are ]. <span style="font-family:Garamond,Palatino,serif;font-size:115%;background:-webkit-linear-gradient(red,red,red,blue,blue,blue,blue);-webkit-background-clip:text;-webkit-text-fill-color:transparent">] ]</span> 23:06, 9 January 2025 (UTC)
*'''Comment''' Large language model AI like Chat GPT are in their infancy. The culture hasn't finished its initial reaction to them yet. I suggest that any proposal made here have an automatic expiration/required rediscussion date two years after closing. ] (]) 22:42, 3 January 2025 (UTC)
*'''No''' – It is a matter of how you use AI. I use Google translate to add trans-title parameters to citations, but I am careful to check for Google's output making for good English as well as reflecting the foreign title when it is a language I somewhat understand. I like to think that I am careful, and I do not pretend to be fluent in a language I am not familiar with, although I usually don't announce the source of such a translation. If an editor uses AI profligately and without understanding the material generated, then that is the sin; not AI itself. ] (]) 05:04, 5 January 2025 (UTC)
*:There's a legal phrase, "when the exception swallows the rule", and I think we might be headed there with the recent LLM/AI discussions.
*:We start off by saying "Let's completely ban it!" Then in discussion we add "Oh, except for this very reasonable thing... and that reasonable thing... and nobody actually meant this other reasonable thing..."
*:The end result is that it's "completely banned" ...except for an apparent majority of uses. ] (]) 06:34, 5 January 2025 (UTC)
*::Do you want us to reply to you, because you are a human? Or are you just posting the output of an LLM without bothering to read anything yourself? ] (]) 06:08, 7 January 2025 (UTC)
*:::Most likely you would reply because someone posted a valid comment and you are assuming they are acting in good faith and taking responsibility for what they post. To assume otherwise is kind of weird and not inline with general Misplaced Pages values. ] (]) 15:19, 8 January 2025 (UTC)
*'''No''' The OP seems to misunderstand ] which is not aimed at weak editors but instead exhorts stronger editors to lead by example. That section already seems to overload the primary point of WP:AGF and adding mention of AI would be quite inappropriate per ]. ]🐉(]) 23:11, 5 January 2025 (UTC)
*'''No'''. Reading the current text of the section, adding text about AI would feel out-of-place for what the section is about. <span class="nowrap">—] (] | ])</span> 05:56, 8 January 2025 (UTC)
*'''No''', this is not about good faith. ] (]) 11:14, 9 January 2025 (UTC)
*'''Yes'''. AI use is ''not'' a demonstration of bad faith (in any case not every new good-faith editor is familiar with our AI policies), but it is equally not a "demonstration of good faith", which is what the ] section is about.
:It seems some editors are missing the point and !voting as if every edit is either a demonstration of good faith or bad faith. Most interactions are neutral and so is most AI use, but I find it hard to imagine a situation where AI use would point ''away'' from unfamiliarity and incompetence (in the CIR sense), and it often (unintentionally) leads to a presumption of laziness and open disinterest. It makes perfect sense to recommend against it. <span style="font-family:Garamond,Palatino,serif;font-size:115%;background:-webkit-linear-gradient(red,red,red,blue,blue,blue,blue);-webkit-background-clip:text;-webkit-text-fill-color:transparent">] ]</span> 22:56, 9 January 2025 (UTC)
::Indeed most kinds of actions don't inherently demonstrate good or bad. The circumspect and neutral observation that {{tq|AI use is ''not'' a demonstration of bad faith... but it is equally not a "demonstration of good faith"}}, does not justify a proposal to one-sidedly say just half. And among all the actions that don't necessarily demonstrate good faith (and don't necessarily demonstrate bad faith either), it is not the purpose of "demonstrate good faith" and the broader guideline, to single out one kind of action to especially mention negatively. ] (]) 04:40, 13 January 2025 (UTC)
*'''Yes'''. Per Dass Wolf, though I would say passing off a completely AI-generated comment as your own ''anywhere'' is inherently bad-faith and one doesn't need to know Wiki policies to understand that. ] (]) 23:30, 9 January 2025 (UTC)
*'''Yes'''. Sure, LLMs may have utility somewhere, and it might be a crutch for people unfamiliar with English, but as I've said above in the other AI RfC, that's a ] issue. This is about comments eating up editor time, energy, about LLMs easily being used to ram through changes and poke at editors in good standing. I don't see a case wherein a prospective editor's command of policy and language is good enough to discuss with other editors while being bad enough to require LLM use. ]<span style="color: #3558b7;"><sup>]</sup>]</span> 01:26, 10 January 2025 (UTC)
*:Good faith is separate from competence. Trying to do good is separate from having skills and knowledge to achieve good results. ] (]) 04:40, 13 January 2025 (UTC)
*'''No''' - anyone using a washing machine to wash their clothes must be evil and inherently lazy. They cannot be trusted. ... Oh, sorry, wrong century. Regards, --] (]) 01:31, 10 January 2025 (UTC)
*'''No''' - As long as a person understands (and knows) what they are talking about, we shouldn't discriminate against folks using generative AI tech for grammar fixes or minor flow improvements. Yes, AI can create walls of text, and make arguments not grounded in policy, but we could do that even without resorting to generative AI. ] (]) 11:24, 13 January 2025 (UTC)
::To expand on my point above. Completely AI generated comments (or articles) are obviously bad, but {{tq|using AI}} should be thrown into the same cross-hairs as completely AI generated comments. ] (]) 11:35, 13 January 2025 (UTC)
:::@] You mean ''shouldn't'' be thrown? I think that would make more sense given the context of your original !vote. <sub>Duly signed,</sub> ''']'''-''<small>(])</small>'' 14:08, 14 January 2025 (UTC)
*'''No'''. Don't make any changes. It's not a good faith/bad faith issue. The 'yes' arguments are most unconvincing with very bizarre analogies to make their point. Here, I can make one too: "Don't edit with AI; you wouldn't shoot your neighbor's dog with a BB-gun, would you?" <sub>Duly signed,</sub> ''']'''-''<small>(])</small>'' 14:43, 13 January 2025 (UTC)
== Allowing non-admin "delete" closures at RfD ==
::Perhaps some kind of clarification that distinguishes between real content and laundry lists is called for? ] 22:35, 19 March 2007 (UTC)
At ], a few editors ({{u|Enos733}} and {{u|Jay}}, while {{u|Robert McClenon}} and {{u|OwenX}} hinted at it) expressed support for allowing non-administrators to close RfD discussions as "delete". While I don't personally hold strong opinions in this regard, I would like for this idea to be discussed here. ]<sub>]<sub>]</sub></sub> (]/]) 13:13, 7 January 2025 (UTC)
:::: There is a guideline -- '''don't datadump''', referenced at ], but I think it applies to more than just mining PD resources to create articles. If someone creates a laundry list, & it stalls at that point, never becoming either a proper list or an article -- deletion should be considered. The AfD process is a cruel alarm clock for sleeping editors who are invested in the article, but if no one cares about a poorly-written list of pop cultural allusions, then we might as well get rid of it. (Did I just suggest a new deletion category?) -- ] 21:21, 20 March 2007 (UTC)
*] --] <sup>(])</sup> 14:10, 7 January 2025 (UTC)
*While I have no issue with the direction the linked discussion has taken, I agree with almost every contributor there: As a practice I have zero interest in generally allowing random editors closing outside their permissions. It might make DRV a more chatty board, granted. ] (]) 15:02, 7 January 2025 (UTC)
*:Tamzin makes a reasonable case in their comment below. When we have already chosen to trust certain editors with advanced permissions, we might allow those folks to utilize them as fully as accepted practice allows. Those humans already have skin in the game. They are unlikely to act rashly. ] (]) 19:32, 7 January 2025 (UTC)
* To me, non-admin delete closes at any XfD have always seemed inconsistent with what we say about how adminship and discussion closing work. I would be in violation of admin policy if I deleted based on someone else's close without conducting a full review myself, in which case, what was the point of their close? It's entirely redundant to my own work. That said, I can't really articulate a reason that this should be allowed at some XfDs but not others, and it seems to have gone fine at CfD and TfD. I guess call me neutral. {{PB}} What I'd be more open to is allowing page movers to do this. Page movers do have the tools to turn a bluelink red, so it doesn't create the same admin accountability issue if I'm just cleaning up the stray page left over from a page mover's use of a tool that they were duly granted and subject to their own accountability rules for. We could let them move a redirect to some other plausible title (this would violate ] as currently written but I think I'd be okay with making this a canonical exception), and/or allow moving to some draftspace or userspace page and tagging for G6, as we do with {{tl|db-moved}}. I'll note that when I was a non-admin pagemover, I did close a few things as delete where some edge case applied that let me effect the deletion using only suppressredirect, and no one ever objected. <span style="font-family:courier"> -- ]</span><sup class="nowrap">[]]</sup> <small>(])</small> 19:07, 7 January 2025 (UTC)
*::I see that I was sort of vague, which is consistent with the statement that I hinted at allowing non-admin delete closures. My main concern is that I would like to see our guidelines and our practice made consistent, either by changing the guidelines or changing the practice. It appears that there is a rough consensus emerging that non-admin delete closures should continue to be disallowed in RFD, but that CFD may be a special case. So what I am saying is that if, in practice, we allow non-admin Delete closures at CFD, the guideline should say something vague to that effect.
*::I also see that there is a consensus that DRV can endorse irregular non-admin closures, including irregular non-admin Delete closures. Specifically, it isn't necessary for DRV to vacate the closure for an ] admin to close. A consensus at DRV, some of whose editors will be uninvolved admins, is at least as good a close as a normal close by an uninvolved admin.
*::Also, maybe we need clearer guidance about non-admin Keep closures of AFDs. I think that if an editor is not sure whether they have sufficient experience to be closing AFDs as Keep, they don't have enough experience. I think that the guidance is clear enough in saying that ] applies to non-admin closes, but maybe it needs to be further strengthened, because at DRV we sometimes deal with non-admin closes where the closer doesn't respond to inquiries, or is rude in response to them.
*::Also, maybe we need clearer guidance about non-admin No Consensus closures of AFDs. In particular, a close of No Consensus is a contentious closure, and should either be left to an admin, or should be Relisted.
::] (]) 19:20, 7 January 2025 (UTC)
:::As for {{tq| I can't really articulate a reason that this should be allowed at some XfDs}}, the argument is that more work is needed to enact closures at TfD and CfD (namely orphaning templates and emptying/moving/merging categories). Those extra steps aren't present at RfD. At most, there are times when it's appropriate to unlink the redirect or add ]s but those are automated steps that ] handles. From my limited experience at TfD and CfD though, it does seem that the extra work needed at closure does not compensate for the extra work from needing two people reviewing the closure (especially at CfD because a bot that handles the clean-up). Consistency has come up and I would much rather consistently disallow non-admin delete closures at all XfD venues. I know it's tempting for non-admins to think they're helping by enacting these closures but it's not fair for them to be spinning their wheels. As for moving redirects, that's even messier than deleting them. There's a reason that ] advises not to move redirects except for limited cases when preserving history is important. --] <sup>(])</sup> 20:16, 7 January 2025 (UTC)
::@]: I do have one objection to this point of redundancy, which you are ]. Here, an AfD was closed as "transwiki and delete", however, the admin who did the closure does not have the technical ability to transwiki pages to the English Wikibooks, meaning that I, who does, had to determine that the outcome was actually to transwiki rather than blindly accepting a request at ]. Then, I had to mark the pages for G6 deletion, that way an admin, in this case you, could determine that the page was ready to be deleted. Does this mean that that admin who closed the discussion shouldn't have closed it, since they only have the technical ability to delete, not transwiki? Could I have closed it, having the technical ability to transwiki, but not delete? Either way, someone else would have had to review it. Or, should only people who have importing rights on the target wiki ''and'' admin rights on the English Misplaced Pages be allowed to close discussions as "transwiki and delete"? ]<sub>]<sub>]</sub></sub> (]/]) 12:04, 8 January 2025 (UTC)
*I do support being explicit when a non-administrator can close a discussion as "delete" and I think that explicitly extending to RfD and CfD is appropriate. First, there can be a backlog in both of these areas and there are often few comments in each discussion (and there is usually not the same passion as in an AfD). Second, the delete close of a non-administrator is reviewed by an administrator before action is taken to delete the link, or category (a delete close is a two-step process, the writeup and the delete action, so in theory the administrators workload is reduced). Third, non-admins do face ] for their actions, and can be subject to sanction. Fourth, the community has a role in reviewing closing decisions at DRV, so there is already a process in place to check a unexperienced editor or poor close. Finally, with many, if not most discussions for deletion the outcome is largely straight forward. --] (]) 20:01, 7 January 2025 (UTC)
*There is currently no rule against non-admin delete closures as far as I know; the issue is the practical one that you don't have the ability to delete. However, I ''have'' made non-admin delete closures at AfD. This occurred when an admin deleted the article under consideration (usually for COPYVIO) without closing the related AfD. The closures were not controversial and there was no DRV. ] ] 20:31, 7 January 2025 (UTC)
:::Be careful in wholesale condemnation of an entire class of articles simply for the inadequacies of some in that class. At least one article that began life as a "XXXXXX in popular culture" has been eleveated to Featured status: See ] This proposal also reeks of ]. Guidelines exist for acceptable lists ] for example, and others. Lists also need to meet all of the same requirements of any other article, such as ] and ] and ]. There are good lists and bad lists. There are good articles on pop culture references, and there are bad one. It is wrong to throw out the baby with the bathwater, ''even if the amount of bathwater far exceeds the amount of baby''. If you find a bad article, send it to AFD or PROD it, or best yet, fix it yourself... --]|]|] 02:27, 20 March 2007 (UTC)
::The situation you're referring to is an exception allowed per ]: {{tq|If an administrator has deleted a page (including by speedy deletion) but neglected to close the discussion, anyone with a registered account may close the discussion provided that the administrator's name and deletion summary are included in the closing rationale.}} --] <sup>(])</sup> 20:37, 7 January 2025 (UTC)
*Bad idea to allow, this sort of closure is just busy work, that imposes more work on the admin that then has to review the arguments, close and then delete. ] (]) 22:05, 7 January 2025 (UTC)
* Is this the same as ] above? ]] 23:04, 7 January 2025 (UTC)
**Yes, ]. Same issue coming from the same ]. ] (]) 03:52, 8 January 2025 (UTC)
* (1) As I've also ], the deletion process guidelines at ] do say non-admins shouldn't do "delete" closures and do recognize exceptions for CfD and TfD. There isn't a current inconsistency there between guidelines and practice. <br>(2) In circumstances where we do allow for non-admin "delete" closures, I would hope that the implementing admin isn't fully ] before implementing, but rather giving deference to any reasonable closure. That's how it goes with ] closers asking for technical help implementing a "moved" closure at ] (as noted at ], the closure will "generally be respected by the administrator (or page mover)" but can be reverted by an admin if "clearly improper"). ] ] 08:41, 9 January 2025 (UTC)
*'''Comment''' - A couple things to note about the CFD process: It very much requires work by admins. The non-admin notes info about the close at WT:CFD/Working, and then an admin enters the info on the CFD/Working page (which is protected) so that the bot can perform the various actions. Remember that altering a category is potentially more labour intensive than merely editing or deleting a single page - every page in that category must be edited, and then the category deleted. (There are other technical things involved, like the mess that template transclusion can cause, but let's keep it simple.) So I wouldn't suggest that that process is very useful as a precedent for anything here. It was done at a time when there was a bit of a backlog at CfD, and this was a solution some found to address that. Also - since then, I think at least one of the regular non-admin closers there is now an admin. So there is that as well. - <b>]</b> 09:14, 9 January 2025 (UTC)
::::On the contrary, I'd say we should provide some guidance with the awareness that there will be exceptions. The rare pop culture trivia article that is found to have merit, and is preserved for its encyclopedic quality, should not serve as a precedent to encourage the proliferation of countless pop trivia articles to list every instance where one work referenced another. The fact that many articles get shot down in AfD demonstrates an existing consensus against indiscriminate trivia collections. Our standards and expectations should be made as clear as possible, to provide guidance, and to try to address the problem in a consistent way.] 13:25, 20 March 2007 (UTC)
*If the expectation is that an admin needs to review the deletion discussion to ensure they agree with that outcome before deleting via G6, as multiple people here are suggesting, then I'm not sure this is worthwhile. However, I have had many admins delete pages I've tagged with G6, and I have been assuming that they only check that the discussion was indeed closed as delete, and trust the closer to be responsible for the correctness of it. This approach makes sense to me, because if a non-admin is competent to close and be responsible for any other outcome of a discussion, I don't see any compelling reason they can't be responsible for a delete outcome and close accordingly. <span style="white-space: nowrap;">—] <sup>(]·])</sup></span> 19:51, 9 January 2025 (UTC)
*:Some closers, and you're among them, have closing accuracy similar to many sysops. But the sysop can't/shouldn't "trust" that your close is accurate. Trustworthy though you are, the sysop must, at very minimum, check firstly that the close with your signature on it was actually made by you (signatures are easily copied), secondly that the close wasn't manifestly unreasonable, and thirdly that the CSD is correct. ] holds the deleting sysop responsible for checking that the CSD were correctly applied. G6 is for uncontroversial deletions, and if there's been an XFD, then it's only "uncontroversial" if the XFD was unanimous or nearly so. We do have sysops who'll G6 without checking carefully, but they shouldn't. Basically, non-admin closing XFDs doesn't save very much sysop time. I think that if your motive as a non-admin is to relieve sysops of labour, the place you're of most use is at RfC.—] <small>]/]</small> 11:28, 12 January 2025 (UTC)
*::{{tpq|if your motive as a non-admin is to relieve sysops of labour, the place you're of most use is at RfC}} alternatively you should consider becoming an administrator yourself. ] (]) 13:20, 12 January 2025 (UTC)
*:::<small>If you're willing to tolerate the RFA process.—] <small>]/]</small> 15:24, 12 January 2025 (UTC)</small>
*::In all the cases I have dealt with, the admin's reason for deletion (usually copyvio) was completely different to the issues being debated in the AfD (usually notability). The closing statement was therefore something like "Discussion is now moot due to article being deleted for <reason> by <admin>". ] ] 20:10, 14 January 2025 (UTC)
*I think most all the time, experienced closers will do a great job and that will save admin time because they will not have to construct and explain the close from scratch, but there will be some that are bad and that will be costly in time not just for the admin but for the project's goal of completing these issues and avoiding disruption. I think that lost time is still too costly, so I would oppose non-admin delete closes. (Now if there were a proposal for a process to make a "delete-only admin permission" that would be good -- such motivated specialists would likely be more efficient.) ] (]) 16:44, 12 January 2025 (UTC)
* As I said at the "Non-Admin XFD Close as Delete" section, I support non-admins closing RfDs as Delete. If TfDs have been made an exception, RfDs can be too, especially considering RfD backlogs. Closing a heavily discussed nomination at RfD is more about the reading, analysis and thought process at arriving at the outcome, and less about the technicality of the subsequent page actions. I don't see a significant difference between non-admins closing discussions as Delete vs non-Delete. It will help making non-admins mentally prepared to advance to admin roles.<span style="font-family:Segoe Script">]</span><span style="font-size:115%">]</span> 14:53, 14 January 2025 (UTC)
== Should WP:NOTDIRECTORY be more specific about phone numbers, etc.? ==
==Copyright status of screenshots==
Apparently the ] talk page isn't well-watched, so I'd like to draw some attention to ] over there. ] (]) 04:05, 8 January 2025 (UTC)
I am sure the answer is somewhere already, but I am having trouble locating it. What is the copyright status of screenshots, such as ? Thanks! --] (<small>] ;; ]</small>) 18:46, 18 March 2007 (UTC)
:If the program itself is copyrighted, then the screenshot is too. <font color="maroon">]</font>'''<small>]</small>''<font color="navy" face="cursive">]</font>'''''<small>]</small> 19:52, 18 March 2007 (UTC)
::Thanks! Then my next question would be, what tags are available for images where the license provided is questionable? In that example, the author claims it as his/her own, but it appears to be an image of a copyrighted product. I suspect the user believes that a screenshot taken by his/herself is therefore his/her own copyright. --] (<small>] ;; ]</small>) 00:46, 19 March 2007 (UTC)
:::The correct licencing tag would be <nowiki>{{Windows-software-screenshot}}</nowiki>. See ] for more information. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 00:53, 19 March 2007 (UTC)
::::Also, the fair use should be as little as possible. A full sized screenshot would not qualify as fair use.++]++ 22:56, 19 March 2007 (UTC)
:That talk page has been checked by at least 100 registered editors during the last month, which makes it one of our better watched pages. ] (]) 18:22, 9 January 2025 (UTC)
== Any essays on AUTHORITY of editors ==
::{{tq|Apparently}}. :) Getting no response in 36 hours was surprising. The silence could mean "no objection" (since I'm not proposing a change, just a clarification that already used to be there), but since it's a policy page, it would be good to have something more tangible. ] (]) 08:20, 10 January 2025 (UTC)
== Does my name technically violate the promotional username policy? ==
I have done a little look for this. But after about 10 minutes thought it might just be easier to ask people who might know.
My username, as of right now, is Tenebre.Rosso.Sangue995320, which is a reference to and i recently read the username policy, and thought that this violates that policy. can someone help me out? ] ] ] 23:48, 9 January 2025 (UTC)
:No, it does not. ] (]/]) 00:11, 10 January 2025 (UTC)
== Technical section headings ==
Are there any essays/guidelines explaining how editors should not use their personal authority on a subject (eg. as a politician, university professor, leader of a band's fan club etc.) to add ] to articles without ]. I am looking for something that specifically deals with someone saying that they have in depth knowledge through personal experience on the subject, so it doesn't really matter that they haven't sourced their contributions, because they are "true".--] 00:36, 19 March 2007 (UTC)
I had expected ] to state a preference toward easily understood headings over complicated technical headings. No such preference was stated. Am I missing something? This subject is currently at issue in regards to Techtonic Setting vs Background at ].-] <small>(] / ] / ] / ] / ])</small> 15:32, 12 January 2025 (UTC)
:This has been an ongoing issue with Misplaced Pages and one that has VERY recently come full force into the spotlight, due to a recent incident which attained some media prominence. By and large, the policies of ], ], ], and ] are what guide us -- and you already appear to be aware of all or most of those. If you can provide a verifiable reference to support your claim and the other user cannot find a reference of their own, then as best I see it: it sounds like you're in the right -- the burden of proof is now upon them to find information which runs counter to your evidence.
:You may be looking for ]? It doesn't specifically address headings, but in general makes the point that we should strive to make articles as accessible as possible for the general reader. This is part of ]. ] (]) 15:50, 12 January 2025 (UTC)
:I have used the argument of "I know this because I do" quite often, myself. I use it only when I am truly confident in something, such as in cases where it is clearly apparent to absolutely anyone with the slightest bit of knowledge on the subject would know that I am correct. I do not use that approach in situations where users provide a reference counter to how I see it; though sometimes I may attempt to discredit a provided reference should its verifiability be up to debate. Users whom claim professional experience on a particular topic and wish to cite their own studies should have a published paper on the subject, published by a respected media. --] (<small>] ;; ]</small>) 00:44, 19 March 2007 (UTC)
:::That is helpful. I guess there is no such guidance for the section headings. Thx.-] <small>(] / ] / ] / ] / ])</small> 05:33, 13 January 2025 (UTC)
::And even if you yourself absolutely know it to be true, it still needs a source so that ''any'' reader who comes upon it, not just the ones with knowledge, can check it and not just take your word for it. ] (]/]) 03:04, 19 March 2007 (UTC)
::I wouldn't say "Tectonic setting" and "Background" are interchangeable for any reader, the first is much more specific. ] (]) 00:25, 13 January 2025 (UTC)
:There might be others, but this anti-] proposal is possibly what you seek: ]. --] 06:02, 19 March 2007 (UTC)
:::In this review the set of section headings was Tectonic setting, Earthquake, Impact or Aftermath, making for an odd Table of contents for the non-expert reader because one section heading was for experts and the others were for the general audience. The techtonics were a historical background so I advised to make all the section titles for the general audience.-] <small>(] / ] / ] / ] / ])</small> 05:30, 13 January 2025 (UTC)
::Hooray! ] is exactly what I was after.--] 09:58, 19 March 2007 (UTC)
:The answer is very simple: no editor has such authority. -- ] 08:12, 19 March 2007 (UTC)
== Modifying the first sentence of BLPSPS ==
== regarding image censorship ==
{{FYI}} A discussion has been started at ] re: modifying the text of BLPSPS. ] (]) 14:23, 13 January 2025 (UTC)
Can some people please give some outside opinions on the use of ] and ] picture on the ] article? (at the article talk page)
== Upgrade ] to an official guideline ==
People have been removing the pictures because it's gross and because they claim it's irrelevant. However, being gross shouldn't matter, as per "Misplaced Pages is not censored". As for the relevance, what could be more relevant on an article called "Human feces" than a photo of real human feces? Of course, there's the option of having drawings instead (as we do on the articles about sex), but it would be sort of difficult to ''draw'' human feces and have it look obviously like human feces...as oppossed to just a lump.
] is an essay. I've been editing since 2010, and for the entire duration of that, this essay has been referred to and used extensively, and has even guided discussions regarding ascertaining if sources are reliable. I propose that it be formally upgraded to a status as an MOS guideline parallel to ].--] (] | ]) 14:28, 13 January 2025 (UTC)
:I'm broadly in favor of this proposal—I looked over the essay and most of it is aligned with what seems standard in album articles—but there are a few aspects that feel less aligned with current practice, which I'd want to reexamine before we move forward with promoting this:
I have a feeling that when we take away the "the pictures are gross" factor, it is really within Misplaced Pages policies and completely relevant to have those two pictures on the article. Two earlier request for comments from last year are on ] and seem to show there was consensus to keep an image of human feces on the article.
:* The section ] suggests {{tq|What other works of art is this producer known for?}} as one of the categories of information to include in a recording/production section. This can be appropriate in some cases (e.g., the '']'' article discusses how Butch Vig's work with Killdozer inspired Nirvana to try and work with him), but recommending it outright seems like it'd risk encouraging people to ]. My preference would be to cut the sentence I quoted and the one immediately following it.
:* The section ] suggests that the numbered-list be the preferred format for track listings, with other formats like {{tl|Track listing}} being alternative choices for "more complicated" cases. However, in my experience, using {{tlg|Track listing|nolink=yes}} rather than a numbered list tends to be the standard. All of the formatting options currently listed in the essay should continue to be mentioned, but I think portraying {{tlg|Track listing|nolink=yes}} as the primary style would be more reflective of current practice.
:* The advice in the ] section seems partially outdated. In my experience, review aggregators like Metacritic are conventionally discussed in the "Critical reception" section instead these days, and I'm uncertain to what extent we still link to databases like Discogs even in ELs.
:(As a disclaimer, my familiarity with album articles comes mostly from popular-music genres, rock and hip-hop in particular. I don't know if typical practice is different in areas like classical or jazz.) Overall, while I dedicated most of my comment volume to critiques, these are a fairly minor set of issues in what seems like otherwise quite sound guidance. If they're addressed, it's my opinion that this essay would be ready for prime time. ] (] • ]) 15:19, 13 January 2025 (UTC)
::I'd agree with all of this, given my experience. The jazz and classical that I've seen is mostly the same.--] (] | ]) 16:57, 13 January 2025 (UTC)
:::Me too, though sometime last year, I unexpectedly had some (inexplicably strong) pushback on the tracklist part with an editor or two. In my experience, using the track list template is the standard, and I can't recall anyone giving me any pushback for it, but some editors apparently prefer just using numbers. I guess we can wait and see if there's any current pushback on it. 17:01, 13 January 2025 (UTC) ] ] 17:01, 13 January 2025 (UTC)
::::Was it pushback for how you had rendered the tracklist, or an existing tracklist being re-formatted by you or them?--] (] | ]) 18:13, 13 January 2025 (UTC)
:::::They came to WT:ALBUMS upset that another editor was changing track lists from "numbered" to "template" formats. My main response was surprised, because in my 15+ years of article creations and rewrites, I almost exclusively used the tracklist template, and had never once received any pushback.
:::::So basically, I personally agree with you and MDT above, I'm merely saying I've heard someone disagree. I'll try to dig up the discussion. ] ] 17:50, 14 January 2025 (UTC)
::::::I found , though this was more about sticking to the current wording as is than it was about opposition against changing it. Not sure if there was another one or not. ] ] 18:14, 14 January 2025 (UTC)
::::I remember one editor being strongly against the template, but they are now community banned. Everyone else I've seen so far uses the template. <span style="background:#16171c; font-family:monospace; font-weight:600; padding:2px; box-shadow:#9b12f0 2px -2px">] ]</span> 22:25, 13 January 2025 (UTC)
::::I can see the numbered-list format being used for very special cases like '']'', which was released with only two songs, and had the same co-writers and producer. But I imagine we have extremely few articles that are like that, so I believe the template should be the standard. ] 🦗🐜 <sup><small>]'']</small></sup> 12:23, 14 January 2025 (UTC)
:::{{u|ModernDayTrilobite}}, regarding linking to ], some recent discussions I was in at the end of last year indicate that it is common to still link to Discogs as an EL, because it gives more exhaustive track, release history, and personnel listings that Misplaced Pages - generally - should not.--] (] | ]) 14:14, 15 January 2025 (UTC)
::::Thank you for the clarification! In that case, I've got no objection to continuing to recommend it. ] (] • ]) 14:37, 15 January 2025 (UTC)
::There were several discussions about Discogs and an RfC ]. As a user of {{tl|Discogs master}}, I agree with what other editors said there. We can't mention every version of an album in an article, so an external link to Discogs is invaluable IMO. <span style="background:#16171c; font-family:monospace; font-weight:600; padding:2px; box-shadow:#9b12f0 2px -2px">] ]</span> 22:34, 13 January 2025 (UTC)
:We badly need this to become part of the MOS. As it stands, some editors have rejected the guidelines as they're just guidelines, not policies, which defeats the object of having them in the first place. ] (]) 16:59, 13 January 2025 (UTC)
::I mean, they are guidelines, but deviation per ] should be for a good reason, not just because someone feels like it.--] (] | ]) 18:14, 13 January 2025 (UTC)
:I am very much in favor of this becoming an official MOS guideline per ] above. Very useful as a template for album articles. ] (]) 21:03, 13 January 2025 (UTC)
:I recently wrote my first album article and this essay was crucial during the process, to the extent that me seeing this post is like someone saying "I thought you were already an admin" in RFA; I figured this was already a guideline. I would support it becoming one. ] (]) 02:00, 14 January 2025 (UTC)
:I have always wondered why all this time these pointers were categorized as an essay. It's about time we formalize them; as said earlier, there are some outdated things that need to be discussed (like in ] which advises not to use stores for credits, even though in the streaming era we have more and more albums/EPs that never get physical releases). Also, song articles should also have their own guidelines, IMV. ] 🦗🐜 <sup><small>]'']</small></sup> 12:19, 14 January 2025 (UTC)
::I'd be in favor of discussing turning the outline at the main page for ] into a guideline.--] (] | ]) 12:53, 14 January 2025 (UTC)
:::I get the sense it'd have to be a separate section from this one, given the inherent complexity of album articles as opposed to that of songs. ] 🦗🐜 <sup><small>]'']</small></sup> 14:56, 14 January 2025 (UTC)
::::Yes, I think it should be a separate, parallel guideline.--] (] | ]) 16:53, 14 January 2025 (UTC)
:I think it needs work--I recall that a former longtime album editor, Richard3120 (not pinging them, as I think they are on another break to deal with personal matters), floated a rewrite a couple of years ago. Just briefly: genres are a perennial problem, editors love unsourced exact release dates and chronology built on OR (many discography pages are sourced only to random ''Billboard'', AllMusic, and Discogs links, rather than sources that provide a comprehensive discography), and, like others, I think all the permutations of reissue and special edition track listings has gotten out of control, as well as these long lists of not notable personnel credits (eight second engineers, 30 backing vocalists, etc.). Also agree that the track listing template issue needs consensus; if three are acceptable, then three are acceptable--again, why change it to accommodate the names of six not notable songwriters? There's still a divide on the issue of commercial links in the body of the article--I have yet to see a compelling reason for their inclusion (WP is, uh, not for sale, remember?), when a better source can always be found (and editors have noted, not that I've made a study of it, that itunes often uses incorrect release dates for older albums). But I also acknowledge that since this "floated" rewrite never happened, then the community at large may be satisfied with the guidelines. ] (]) 13:45, 14 January 2025 (UTC)
::Regarding the personnel and reissue/special edition track listing, I don't know if I can dig up the discussions, but there seems to be a consensus against being exhaustive and instead to put an external link to Discogs. I fail to see how linking to ''Billboard'' or AllMusic links for a release date on discographies is OR, unless you're talking about in the lead. At least in the case of Billboard, that's an established RS (AllMusic isn't the most accurate with dates).-- ] (] | ]) 13:53, 14 January 2025 (UTC)
:::I meant that editors often use discography pages to justify chronology, even though ''Billboard'' citations are simply supporting chart positions, Discogs only states that an album exists, and AllMusic entries most often do not give a sequential number in their reviews, etc. There is often not a source (or sources) that states that the discography is complete, categorized properly, and in order. ] (]) 14:05, 14 January 2025 (UTC)
::::Ah, okay, I understand now.--] (] | ]) 16:54, 14 January 2025 (UTC)
Myself, I've noticed that some of the sourcing recommendations are contrary to WP:RS guidance (more strict, actually!) or otherwise outside consensus. For instance, MOS:ALBUMS currently says to not use vendors for track list or personnel credits, linking to ] in WP:RS, but AFFILIATE actually says that such use is acceptable but not preferred. Likewise, MOS:ALBUMS says not to use scans of liner notes, which is 1. absurd, and 2. not actual consensus, which in the discussions I've had is that actual scans are fine (which makes sense as it's a digital archived copy of the source).--] (] | ]) 14:05, 14 January 2025 (UTC)
But then again, we do have ], which says "''Including information about offensive material is part of Misplaced Pages's encyclopedic mission; being offensive is not.''" This is clearly a case of including offensive material, but i'm not sure whether it's also a case of "being offensive" or not. So some more opinions would be nice. --] 05:40, 19 March 2007 (UTC)
:The tendency to be overreliant on liner notes is also a detriment. I've encountered some liner notes on physical releases that have missing credits (e.g. only the producers are credited and not the writers), or there are outright no notes at all. Tangentially, some physical releases of albums like '']'' and '']'' actually direct consumers to official websites to see the credits, which has the added problem of link rot ( for ''Still Over It'' and is a permanent dead link). ] 🦗🐜 <sup><small>]'']</small></sup> 15:04, 14 January 2025 (UTC)
::That turns editors to using stores like Spotify or Apple Music as the next-best choice, but a new problem arises -- the credits for a specific song can vary depending on the site you use. One important thing we should likely discuss is what sources should take priority wrt credits. For an example of what I mean, take "]". to check its credits and you'd find the name Sean Garrett -- , however, and that name is missing. I assume these digital credits have a chance to deviate from the albums' physical liner notes as well, if there is one available. ] 🦗🐜 <sup><small>]'']</small></sup> 15:11, 14 January 2025 (UTC)
:::Moreover, the credits in stores are not necessarily correct either. An example I encountered was on ], an amazing service and the only place where I could find detailed credits for one album (not even liner notes had them, since back then artists tried to avoid sample clearance). However, as I was double checking everything, one song made no sense: in its writing credits I found "Curtis Jackson", with a link to ]'s artist page. It seemed <em>extremely</em> unlikely that they would collaborate, nor any of his work was sampled here. Well, it turns out this song sampled a song written by Charles Jackson of ]. <span style="background:#16171c; font-family:monospace; font-weight:600; padding:2px; box-shadow:#9b12f0 2px -2px">] ]</span> 16:39, 14 January 2025 (UTC)
::::{{u|PSA}} and {{u|AstonishingTunesAdmirer}}, I agree that it's difficult. I usually use both the physical liner notes and online streaming and retail sources to check for completeness and errors. I've also had the experience of ] being a great resource, and, luckily, so far I've yet to encounter an error. Perhaps advice for how to check multiple primary sources here for errors should be added to the proposed guideline.--] (] | ]) 17:00, 14 January 2025 (UTC)
:::::At this point, I am convinced as well that finding the right sources for credits should be on a case-by-case basis, with the right amount of discretion from the editor. While I was creating ], which included several SoundCloud songs where it was extremely hard to find songwriting credits, I found the useful for filling those missing gaps. More or less the credits there align with what's on the liner notes/digital credits. However, four issues, most of which you can see by looking at the list I started: 1) they don't necessarily align with physical liner notes either, 2) sometimes names are written differently depending on the entry, 3) there are entries where a writer (or co-writer) is unknown, and 4) some of the entries here were never officially released and confirmed as outtakes/leaks (why is "BET Awards 19 Nomination Special" here, whatever that means?). ] 🦗🐜 <sup><small>]'']</small></sup> 22:59, 14 January 2025 (UTC)
::::::Yeah, I've found it particularly tricky when working on technical personnel (production, engineering, mixing, etc.) and songwriting credits for individuals. I usually use the liner notes (if there are any), check AllMusic and ], and also check Tidal if necessary. But I'll also look at Spotify, too. I know they're user-generated, so I don't cite them, but I usually look at Discogs and Genius to get an idea if I'm missing something. Thank you for pointing me to Songview, that will probably also be really helpful. ] (] | ]) 12:50, 15 January 2025 (UTC)
:(@], please see ] for advice on advertising discussions about promoting pages to a guideline. No, you ''don't'' have to start over. But maybe add an RFC tag or otherwise make sure that it is very widely publicized.) ] (]) 23:37, 14 January 2025 (UTC)
::Thank you. I'll notify the Manual of Style people. I did already post a notice at WP:ALBUMS. I'll inform other relevant WikiProjects as well.--] (] | ]) 12:46, 15 January 2025 (UTC)
Before posting the RfC as suggested by {{u|WhatamIdoing}}, I'm proposing the following changes to the text of MOS:ALBUM as discussed above:
The picture is offensive indeed, but, beyond that, it is also needless. It serves no informative purpose, as everybody (every human being on this earth) knows what feces look like. As I've said several places, there is no other serious reason to keep those shit images in the articles than to provide amusement and adverse reactions under the pretext of needing article images. They are also a potential source for vandalism.--] 09:46, 19 March 2007 (UTC)
# Eliminate {{!xt|What other works of art is this producer known for? Keep the list of other works short, as the producer will likely have their own article with a more complete list.}} from the "Recording, production" sub-section.
# Rework the text of the "Style and form" for tracklistings to:
::{{xt|1=The track listing should be under a primary heading named "Track listing".}}
::{{xt|1=A track listing should generally be formatted with the {{tl|Track listing}} template. Note, however, that the track listing template forces a numbering system, so tracks originally listed as "A", "B", etc., or with other or no designations, will not appear as such when using the template. Additionally, in the case of multi-disc/multi-sided releases, a new template may be used for each individual disc or side, if applicable.}}
:Yeah, I've got to agree. These images are just for shock value, they really don't add anything particularly informative to the article. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 09:50, 19 March 2007 (UTC)
::{{xt|1=Alternate forms, such as a table or a ], are acceptable but usually not preferred. If a table is used, it should be formatted using class="wikitable", with column headings "No.", "Title" and "Length" for the track number, the track title and the track length, respectively (see Help:Table). In special cases, such as '']'', a numbered list may be the most appropriate format.}}
This image is not necesarry at all. As someone said, we all know what human feces are and what they look like. Misplaced Pages isn't censored of course but it has an encyclopedic mission. Being offensive when is not required just for the sake of shocking and entertainment isn't part of that mission. I propose the images (there are two of them) to be deleted.--] 19:12, 19 March 2007 (UTC)
# Move {{xt|1= Critical reception overviews like AcclaimedMusic (using {{tl|Acclaimed Music}}), AnyDecentMusic?, or Metacritic may be appropriate as well.}} from "External links" to "Album ratings templates" of "Critical reception", right before the sentence about using {{tl|Metacritic album prose}}.
:What's the point of having a photo of a person's hand on the ] article then (for the record, we do actually have a photo of someone's hands on that article)? I would have thought it was considered a 'good' thing to have every article illustrated by a picture/photo of the article subject. I know people find the pictures offensive. But the question i'm trying to ask is whether this is just a case of the pictures being offensive, or ''us'' being offensive by including them? --] 10:57, 20 March 2007 (UTC)
# Re-write this text from "Sourcing" under "Track listing" from {{!xt|However, if there is disagreement, there are other viable sources. Only provide a source for a track listing if there are exceptional circumstances, such as a dispute about the writers of a certain track. Per ], avoid commercial sources such as online stores and streaming platforms. In the rare instances where outside citations are required, explanatory text is useful to help other editors know why the album's liner notes are insufficient.}} to {{xt|Per ], commercial sources such as online stores and streaming platforms are acceptable to cite for track list information, but secondary coverage in independent reliable sources is preferred if available.}} Similarly, in the "Personnel" section, re-write {{!xt| Similar to the track listing requirements, it is generally assumed that a personnel section is sourced from the liner notes. In some cases, it will be necessary to use third-party sources to include performers who are not credited in the liner notes. If you need to cite these, use {{tl|Cite AV media}} for the liner notes and do not use third party sources such as stores (per ]) or scans uploaded to image hosting sites or ] (per ]).}} to {{xt|1= Similar to the track listing requirements, it is generally assumed that a personnel section is sourced from the liner notes. If you need to cite the liner notes, use {{tl|Cite AV media}}. Scans of the physical media that have been uploaded in digital form to repositories or sites such as ] are acceptable for verification, but cite the physical notes themselves, not the ] transcriptions. Frequently, it will be necessary to use third-party sources to include performers who are not credited in the liner notes. Per ], inline citations to e-commerce or streaming platforms to verify personnel credits are allowed. However, reliable secondary sources are preferred, if available.}}
# Additional guidance has been suggested for researching and verifying personnel and songwriting credits. I suggest adding {{xt|1=It is recommended to utilize a combination of the physical liner notes (if they exist) with e-commerce sites such as ] and ], streaming platforms such as ] and ], and databases such as ] credits listings and . Finding the correct credits requires careful, case-by-case consideration and editor discretion. If you would like assistance, you can reach out to ] or ] WikiProjects.}} The best section for this is probably in "Personnel", in the paragraph discussing that liner notes can be inaccurate.
# The excessive listing of personnel has been mentioned. I suggest adding the following to the paragraph in the "Personnel" section beginning with "The credits to an album can be extensive or sparse.": {{xt|1=If the listing of personnel is extensive, avoid excessive, exhaustive lists, in the spirit of ]. In such cases, provide an external link to ] and list only the major personnel to the list.}}
If you have any additional suggestions, or suggestions regarding the wording of any of the above (I personally think that four needs to be tightened up or expressed better), please give them. I'm pinging the editors who raised issues with the essay as currently written, or were involved in discussing those issues, for their input regarding the above proposed changes. {{u|ModernDayTrilobite}}, {{u|PSA}}, {{u|Sergecross73}}, {{u|AstonishingTunesAdmirer}}, {{u|Caro7200}}, what do you think? Also, I realize that I never pinged {{u|Fezmar9}}, the author of the essay, for their thoughts on upgrading this essay to a guideline.--] (] | ]) 17:21, 15 January 2025 (UTC)
:The proposed edits all look good to me. I agree there's probably some room for improvement in the phrasing of #4, but in my opinion it's still clear enough as to be workable, and I haven't managed to strike upon any other phrasings I liked better for expressing its idea. If nobody else has suggestions, I'd be content to move forward with the language as currently proposed. ] (] • ]) 17:37, 15 January 2025 (UTC)
::Actually, the main illustrations in the ] article all serve some more specific purpose of showing details of anatomy. The less informative photograph of "just somebody's hands" is somewhere down in the gallery. It serves no real purpose there but at least it doesn't do any harm either. This is the point: having "every article illustrated by a picture/photo of the article subject" is not a "'good' thing" in itself. Having illustrations that serve no real purpose other than having an image for the sake of having an image, is something that can be tolerated where it does no harm. But where such images are offensive, that makes all the difference. "WP:NOT censored" refers to images that are offensive ''but necessary''; it doesn't mean we should ignore the fact of an image being offensive and litter the project with it. ] ] 11:42, 20 March 2007 (UTC)
:It might be better to have this discussion on its talk page. That's where we usually talk about changes to a page. ] (]) 17:38, 15 January 2025 (UTC)
::{{u|WhatamIdoing}} - just the proposed changes, or the entire discussion about elevating this essay to a guideline?--] (] | ]) 18:21, 15 January 2025 (UTC)
:::It would be normal to have both discussions (separately) on that talk page. ] (]) 18:53, 15 January 2025 (UTC)
::::Okay, thank you. I started the proposal to upgrade the essay here, as it would be far more noticed by the community, but I'm happy for everything to get moved there.-- ] (] | ]) 19:00, 15 January 2025 (UTC)
:These changes look good to me. Although, since we got rid of Acclaimed Music in the articles, we should probably remove it here too. <span style="background:#16171c; font-family:monospace; font-weight:600; padding:2px; box-shadow:#9b12f0 2px -2px">] ]</span> 19:36, 15 January 2025 (UTC)
::Sure thing.--] (] | ]) 20:56, 15 January 2025 (UTC)
{{Discussion bottom}}
:::That's exactly my point. The images have absolutely no informative value ergo no use. Furthermore, they are offensive but needless.--] 12:54, 20 March 2007 (UTC)
::::] is not an acceptable argument for removal of images. Or articles either, for that matter. ] covers this pretty well. ] 17:14, 20 March 2007 (UTC)
== reverts all edits ==
:::::WP what? Obviously, the image is both offensive and useless.--] 17:24, 20 March 2007 (UTC)
Hello everyone. I have an idea for the Misplaced Pages coders. Would it be possible for you to design an option that, with the click of a button, automatically reverts all edits of a disruptive user? This idea came to my mind because some people create disposable accounts to cause disruption in all their edits... In this case, a lot of time and energy is consumed by administrators and reverting users to undo all the vandalism. If there were a template that could revert all the edits of a disruptive user with one click, it would be very helpful. If you think regular users might misuse this option, you could limit it to Misplaced Pages administrators only so they can quickly and easily undo the disruption. ] (]) 17:31, 13 January 2025 (UTC)
::::::When it is proved that there are non-human Wikipedians who have never had the opportuinity to observe human feces, then such an illustration might have encyclopedic value to inform them of what a pile of shit looks like. For now, it constitutes original research, when labelled "The above-average volume of this stool was probably due to a diet high in dietary fiber and/or cellulose." on the image page for image number one.The second image is out of focus and illustrative of nothing meaningful. They can be deleted as original research, especially since they add no information to the article. ] 17:33, 20 March 2007 (UTC)
:Hi @], there's a script that does that: ]. Also, editors who use ] can single-click revert all consecutive edits of an editor. ] ] 17:44, 13 January 2025 (UTC)
::Is this tool active in all the different languages of Misplaced Pages? I couldn't perform such an action with the tool you mentioned. ] (]) 17:51, 13 January 2025 (UTC)
:::That script requires the ] permission, which is available only for admins and other trusted users. Admins and other users with the tool have gotten in trouble for using it inappropriately. I never use it myself, as I find the rollback in Twinkle quite sufficient for my needs. ] 17:54, 13 January 2025 (UTC)
:::(ec) I don't know about other languages. If you check the page I linked, you'll see that the script requires ]. ] ] 17:55, 13 January 2025 (UTC)
::::@] Sorry. Does your ] can reverse all edits of a user in different page's with clicking on button ? i think you mean that massrollback can reverse all edits in a special wiki page... not all edits of edits of disruptive user in multiple pages ? or i'm wrong ??? ] (]) 04:23, 14 January 2025 (UTC)
:::::If you want this for the Persian Misplaced Pages, you should probably talk to ]. ] (]) 23:41, 14 January 2025 (UTC)
::::::@] Thank you. ] (]) 07:11, 15 January 2025 (UTC)
== Problem For Translate page ==
:::::::Problem is, it's in commons. How the frak do we get it deleted from there?--] 18:23, 20 March 2007 (UTC)
::::::::You head over to Commons and list it for deletion. Full instructions are available at ]. Keep in mind that Commons tends to be very slow-moving, so it may take a month or more for the deletion discussion to be closed. --] 22:37, 20 March 2007 (UTC)
Hello everyone. I don’t know who is in charge for coding the Translate page on Misplaced Pages. But I wanted to send my message to the Misplaced Pages coders, and that is that in the Misplaced Pages translation system, the information boxes for individual persons (i.e personal biography box- see: ]) are not automatically translated, and it is time-consuming for Misplaced Pages users to manually translate and change the links one by one from English to another language. Please, could the coders come up with a solution for translating the information template boxes? Thank you. ] (]) 17:32, 13 January 2025 (UTC)
== Misplaced Pages mainly as source of reference ==
:Hi {{u|Hulu2024}}, this also applies to the section above. If your proposal only applies to the English Misplaced Pages then it is probably best to post it at ] in the first instance. If it is only about the Persian Misplaced Pages then you may wish to try there. If it is more general then you could try ], or, for more formal proposals, ]. ] (]) 18:51, 13 January 2025 (UTC)
::@] Thank you. ] (]) 19:21, 13 January 2025 (UTC)
== A discrimination policy ==
In the world there are some reports about people using Misplaced Pages as a
{{Discussion top|result= i quit this will go no where im extremely embarassed and feel horrible i dont think ill try again}}
source of truth. Since anyone can edit, the validity cannot be verified. Hence, school teachers and such are not so happy with the use of Misplaced Pages for research.
<s>Ani cases:
For this reason, I use Misplaced Pages as a source of reference; if I find something, the most value is in the reference to non-wiki sites like vendors, organisations about the topic, researchers on the topic, books, etc. They have their own level of validity that can be verified.
* ]
* ]
* ]
*
I would like to start this proposal by saying that this concept was a proposal in 2009 which failed for obvious reasons. But in this year, 2025, we need it as its happened a bunch. its already under personal attacks but this I feel and a couple other Wikipedians that it should be codified as their is precedent for blocking users who discriminate. Here’s a list of the things I want to include in this policy. edit: This policy is intended to target blatant and admitted instances of discrimination. If the intent behind an action is ambiguous, users should continue to assume good until the intent is.<br>
So if wikipedia is promoted less as an encyclopedia and more as a
Just as being a member of a group does not give one special requirements to edit, it also does not endow any special privileges. One is not absolved of discrimination against a group just because one claims to be a member of that group.
reference, then it would not have to deal with the validity issue. Users who are looking for information can read up on a topic and afterwareds find useful sources through wikipedia.
What counts as discrimination
This could be implemented by having editors focus on further reference
on the topics.
* ]
Maybe this idea has already been suggested, in which case my apologies. If you know this is the case, please try and close this thread.
* Disability-will define this further
* Disease
* ]-different from sex neurological <ref>{{Cite AV media |url=https://www.youtube.com/watch?v=fpGqFUStcxc |title=Let’s All Get Past This Confusion About Trans People |date=2022-06-06 |last=Professor Dave Explains |access-date=2025-01-15 |via=YouTube}}</ref><ref>{{Cite journal |last=Altinay |first=Murat |last2=Anand |first2=Amit |date=2020-08-01 |title=Neuroimaging gender dysphoria: a novel psychobiological model |url=https://link.springer.com/article/10.1007/s11682-019-00121-8 |journal=Brain Imaging and Behavior |language=en |volume=14 |issue=4 |pages=1281–1297 |doi=10.1007/s11682-019-00121-8 |issn=1931-7565}}</ref>
* ]-different then gender biological<ref>{{Cite AV media |url=https://www.youtube.com/watch?v=fpGqFUStcxc |title=Let’s All Get Past This Confusion About Trans People |date=2022-06-06 |last=Professor Dave Explains |access-date=2025-01-15 |via=YouTube}}</ref>
* Sexuality
* Religion
* Hobbies (e.g furry ( most often harassed hobby))
* Relationship status
* Martial status
* (Idk how to word this but) lack of parental presence
* Political position (will be a hot topic)
* ] anything i missed would be in there
Regards,
Philip. {{unsigned|Lafeber|19:35, 19 March 2007}}
A disability is an umbrella term in my sight
:Well, Misplaced Pages classifies itself as an ']', which in itself should imply that it is not designed for serious academic research, but rather, as a general guide and reference. Encyclopedias are by their very nature rarely regarded as reliable academic sources. -- ] <span style="font-size:75%"><font color="#E32636">]</font> <font color="#177245"><sup>]</sup></font></span> 09:21, 19 March 2007 (UTC)
you have mental and physical
::We make a good faith effort to publish authoritative content. While we often fail, especially in the case of hotly contested issues, we should continue to pursue the goal of being an authoritative reference. I have been here now for 5 years and have seen vast improvement. Certainly following up on the references used leads to more knowledge, but our mission is to create reference works. ] 18:20, 19 March 2007 (UTC)
examples for mental would be:
== ] move ==
* schizophrenia
It's been proposed we move '''] → ]''' —('']'') to better emphasise that the policy applies to all information not just in biographies. There appears to be existing consensus for move but decided since it's a critical policy it's better to list it just in case since. Discuss in the BLP talk page, not here ] 16:09, 19 March 2007 (UTC)
== Open proxies, vandalism, and the Great Firewall ==
* paralyzation
I need some clarification on our policy regarding open proxies. ] should be clear: "Open proxies are banned from editing Wikimedia projects. Anonymizers and other companies or organizations that offer open proxies may be blocked indefinitely by an administrator." But the policy is vague regarding whether soft or hard blocks should be imposed. The discussion at ] is germane. The problem is we have a lose-lose situation. Perhaps the majority of cases brought to ] involve open proxies, much of the time Tor proxies. We get a ton of vandalism and other nasty behavior (see, for example, ]), with miscreants creating sometimes dozens, perhaps hundreds of sockpuppet accounts, and then proceeding to use them at will on easily accessible open proxies. The obvious solutions is simply to hard-block the open proxies. But what about our users behind the Great Firewall? With the vagueness in the policy, some of us have been hard-blocking, while others of us have been soft-blocking Tor proxies in particular. I've found myself reversing other admin's decisions, or being reversed myself; so far, no unpleasantry has ensued, but I'd really appreciate some sense of the community on this, or at least a pointer to established policy. --]<sup><small>]</small></sup> 19:09, 19 March 2007 (UTC)
* Pretty much any physical injury
:Persoanly I block OP's as AO AC disabled ] <sup>(] • ] • ])</sup> 19:14, 19 March 2007 (UTC)
* Im aware that this never really happens but its good to go over
::The problem with this approach is that it does nothing to stop banned vandals such as {{User|Verdict}} and all his very many abusive sockpuppets. That said, I have generally blocked OPs as AO, AC-disabled as well. I no longer believe this is appropriate, I believe open anonymising proxies should be blocked with hard blocks. I'm not discounting the problem Chinese users and other such people face, however. --] 19:17, 19 March 2007 (UTC)
I also block OPs as AO, AC-disabled. Obviously, they cannot then be used to create accounts.--] 22:03, 19 March 2007 (UTC)
A user may not claim without evidence that a user is affected by/are any of the above (idk how to term this).
== Deletion process ==
A user may not claim that users with these disabilities/beliefs/races/genders shouldn’t edit Misplaced Pages.
This is currently a discussion regarding non administrator closure at WP:Deletion process . Regards, ] <sup>]</sup> / <sub>]</sub> 21:15, 19 March 2007 (UTC)
A user may not imply a user is below them based on the person.
== Should we have hidden categories? ==
calling people woke simply cause they are queer is discrimination.
Sorry if this has been proposed before. People seem to love creating categories, and other people object to having huge indigestible wads of categories at the end of an article. Maybe the answer is to have a short list of visible categories and another link called "More categories". If you click on "more", you see that huge list. For instance, I could imagine the end of ] looking like this (but in blue):
Also I would like to propose a condition.
:Categories: Cathartidae | Birds of North America | Birds of South America
:More categories
Over reaction to what you think is discrimination (accidental misgendering and wrong pronouns) and the user apologizes for it is not grounds for an entry at ani.
If you click on "More categories", you might see:
This should be used as a guideline.
:Categories: Birds of Canada | Birds of the United States | | Scavengers | Birds with good senses of smell | Birds commensal with humans | Birds that rock in flight | Birds that breed colonially | Examples of convergent evolution | Species that are imitated by other species | Species that appear in Thornton Burgess's stories | Species with scientific names of uncertain origin | etc., etc.
{{Quote box
This would put the power of hypertext at the service of curious users without cluttering up the articles. Why shouldn't somebody who reads that the TV has a good sense of smell wonder what other birds do too? Why shouldn't they get an answer with a scroll and two clicks? Of course people would have to do the work. But there seems to be a strong impulse to work this way; maybe it should be indulged.
| quote = discrimination is defined as acts, practices, or policies that wrongfully impose a relative disadvantage or deprivation on persons based on their membership in a salient social group. This is a comparative definition. An individual need not be actually harmed in order to be discriminated against. He or she just needs to be treated worse than others for some arbitrary reason. If someone decides to donate to help orphan children, but decides to donate less, say, to children of a particular race out of a racist attitude, he or she will be acting in a discriminatory way even if he or she actually benefits the people he discriminates against by donating some money to them.
| source = Misplaced Pages article on discrimination
}}
{{Paragraph break}}I would also like to say this would give us negative press coverage by right wing media and I’ll receive shit. But I don’t care i can deal with it ]] 16:37, 16 January 2025 (UTC)</s>
By the way, I thought of this when participating in the debate at ], which may need some more thoughts. —] 05:30, 20 March 2007 (UTC)
*This largely seems like behavior that already is sanctionable per ] and ] (and the adoption of the latter drew complaints at the time that it in itself was already unnecessarily redundant with existing civility policy on en.wiki). What shortcomings do you see with those existing bodies of policy en force? <sub>signed, </sub>] <sup>]</sup> 16:45, 16 January 2025 (UTC)
*We are in fact trying to cut down on excessive categorization. See ] for details, and if you see an overly-categorized article feel free to drop some of those categories on ]. ] 10:55, 20 March 2007 (UTC)
*:The fact that punishments should be a little more severe for users who go after a whole group of editors. As its not an npa its an attack on a group ]] 16:57, 16 January 2025 (UTC)
**This is a proposal to allow categories that you and I consider excessive. If they're hidden, we have the advantages of all those categories without the disadvantages. The hidden ones would be those deprecated at ] (more or less—categories with only a few members and no room for growth might be forbidden even in hidden form). —] 14:29, 20 March 2007 (UTC)
*::NPA violations are already routinely met with blocks and sitebans, often on sight without prior warning for the level of disparagement you're describing. Do you have any recent examples on hand of cases where the community's response was insufficiently severe? <sub>signed, </sub>] <sup>]</sup> 17:07, 16 January 2025 (UTC)
*:::Ill grab some my issue is admins can unblock without community input it should be unblock from admin then= they have to appeal to the community ]] 17:10, 16 January 2025 (UTC)
*::::<small>Noting that I've now taken the time to read through the three cases listed at the top--two of them ended in NOTHERE blocks pretty quickly--I could see someone taking issue with the community's handling of RowanElder and Jwa05002, although it does seem that the discussion ultimately resulted in an indef block for one and an apparently sincere apology from the other. <sub>signed, </sub>] <sup>]</sup> 17:13, 16 January 2025 (UTC) </small>
*:I think the real problem is that in order to block for any reason you have to take them to a place where random editors discuss whether they are a "net positive" or "net negative" to the wiki, which in principle would be a fair way to decide, but in reality is like the work of opening an RFC just in order to get someone to stop saying random racist stuff, and it's not worth it. Besides, remember the RSP discussion where the Daily Mail couldn't be agreed to be declared unreliable on transgender topics because "being 'gender critical' is a valid opinion" according to about half the people there? I've seen comments that were blatant bigoted insults beneath a thin veneer, that people did not take to ANI because it's just not worth the huge amount of effort. There really needs to be an easy way for administrators to warn (on first violation) and then block people who harass people in discriminatory ways without a huge and exhausting-for-the-complainer "discussion" about it -- and a very clear policy that says discrimination is not OK and is always "net negative" for the encyclopedia would reduce the complexity of that discussion, and I think is an important statement to make.
*:By allowing it to be exhaustively debated whether thinly-veiled homophobic insults towards gay people warrant banning is Misplaced Pages deliberately choosing not to take a stance on the topic. A stance needs to be taken, and it needs to be clear enough to allow rapid and decisive action that makes people actually afraid to discriminate against other editors, because they know that it isn't tolerated, rather than being reasonably confident their targets won't undergo another exhausting ANI discussion. ] (]) 17:04, 16 January 2025 (UTC)
*::Said better then i could say i agree wholeheartedly it happens way too much ]] 17:18, 16 January 2025 (UTC)
*I agree that a blind eye shouldn't be turned against discrimination against groups of Misplaced Pages editors in general, but I don't see why we need a list that doesn't include social class but includes hobbies. The determining factor for deciding whether something is discrimination should be how much choice the individual has in the matter, which seems, in practice, to be the way ] is used. ] (]) 17:02, 16 January 2025 (UTC)
*:I agree hobbies doesn't need to be included. Haven't seen a lot of discrimination based on social class? I think this needs to be taken to the Idea Lab. ] (]) 17:06, 16 January 2025 (UTC)
*::Sorry this was just me spit balling i personally have been harassed over my hobbies ]] 17:07, 16 January 2025 (UTC)
*@] Strong support in general (see above) but I strongly suggest you take this to the idea lab, because it's not written as a clear and exact proposal and it would probably benefit a lot from being developed into an RFC before taking it here. In the current format it probably can't pass because it doesn't make specific changes to policy. ] (]) 17:08, 16 January 2025 (UTC)
* '''Comment''' - Having hidden categories is a good idea. Well I do have another proposal which is to re-categorize into flora and fauna by eco-regions described by the WWF (See: ) and (See: ). ] 14:44, 20 March 2007 (UTC)
*:Yeah sorry I’m new to this i was told to go here to get the ball rolling ]] 17:11, 16 January 2025 (UTC)
*Wait...does this mean I won't be able to discriminate against people whose hobby is editing Misplaced Pages? Where's the fun in that? ] 17:09, 16 January 2025 (UTC)
*:I guess not :3 ]] 17:13, 16 January 2025 (UTC)
:In general, I fail to see the problem this is solving. The UCoC and other policies/guidelines/essays (such as ], ], and others) already prohibit discriminatory behavior. And normal conduct processes already have the ability to lay down the strictest punishment theoretically possible - an indefinite ban - for anyone who engages in such behavior.
*I do not think that the show/hide system by itself would solve all problems as described. It is easily conceivable to picture the "more categories" display becoming simply too long to read for some articles. For example, imagine categories for every country, state, province, territory, department, division, and oblast where the ] is found. When shown, the category list would be too long to read or use effectively. What is also needed is some type of organization mechanisms for categories that would present the categories in a more easy-to-read fashion. At the moment, categories are simply displayed as a paragraph-like mass of links at the bottoms of pages. Improved category formatting (such as displaying the categories as bulleted lists and sorting them into smaller lists) would help substantially. Coupled with the show/hide options described above, the system could be very useful. ] 14:50, 20 March 2007 (UTC)
:I do not like the idea of what amounts to bureaucracy for bureaucracy’s sake. That is the ''best'' way I can put it. At worst, this is virtue signaling - it’s waving a flag saying “hey, public and editors, Misplaced Pages cares about discrimination so much we made a specific policy about it” - without even saying the next part “but our existing policies already get people who discriminate against other editors banned, so this was not necessary and a waste of time”. I’ll happily admit I’m proven wrong if someone can show evidence of a case where actual discrimination was not acted upon because people were “concerned” it wasn’t violating one of those other policies. -bɜ:ʳkənhɪmez | ] | ] 20:56, 16 January 2025 (UTC)
**Not to mention, having hidden categories will just encourage people to overcategorize. People will be adding more categories to the hidden cats than they would have otherwise added to non-hidden cats had hidden cats not existed. I'm talking about the "well, it's hidden anyway, so let's just add the article into every category that technically fits" line of thinking. I don't think it'll be all that helpful - categories are supposed to help with navigation. If you have 20 categories on an article, what are the chances they'll actually be useful to someone? It'll be much better to have just a few categories that are each useful, and readers can look at the categories, then look at the sub/super categories. Then again, i doubt many readers ever look at categories at all, regardless of how many or how few cats there are on an article. Cats is mainly an internal organizational thing for us editors... --] 15:53, 20 March 2007 (UTC)
::To clarify, all the comments about "why is this included" or "why is this not included" are part of the reason I'm against a specific policy like this. Any disruption can be handled by normal processes, and a specific policy will lead to wikilawyering over what is or is not discrimination. There is no need to try to define/specifically treat discrimination when all discriminatory behaviors are adequately covered by other policies already. -bɜ:ʳkənhɪmez | ] | ] 22:27, 16 January 2025 (UTC)
*We should be relating to other editors in a kind way. But this proposal appears to make the editing environment more hostile with more blocking on the opinion of one person. We do discrimonate against those that use Misplaced Pages for wrong purposes, such as vandalism, or advertising. Pushing a particular point of view is more grey area. The proposal by cyberwolf is partly point of view that many others would disagree with. So we should concentrate policies on how a user relates to other editors, rather than their motivations or opinions. ] (]) 20:50, 16 January 2025 (UTC)
* I think this is valuable by setting a redline for a certain sort of personal attack and saying, "this is a line nobody is permitted to cross while participating in this project." ] (]) 20:57, 16 January 2025 (UTC)
* It is not possible for the content of a discussion to be "discriminatory". Discrimination is action, not speech. This proposal looks like an attempt to limit discourse to a certain point of view. That's not a good idea. --] (]) 21:13, 16 January 2025 (UTC)
*:Discrimination can very much be speech. ] (]) 00:36, 17 January 2025 (UTC)
*:: Nope. --] (]) 00:44, 17 January 2025 (UTC)
*::: : "treating a person or particular group of people differently, especially in a worse way from the way in which you treat other people, because of their race, gender, sexuality, etc".
*:::So yes, that includes speech because you can treat people differently in speech. Speech is an act. '']''<sup>]</sup> 01:04, 17 January 2025 (UTC)
*::::OK, look, I'll concede part of the point here. Yes, if I'm a dick to (name of group) but not to (name of other group), I suppose that is discrimination, but I don't think a discrimination policy is a particularly useful tool for this, because what I ''should'' do is not be a dick to anybody.
*::::What I'm concerned about is that the policy would be used to assert that certain ''content'' is discriminatory. Say someone says, here's a reliable source that says biological sex is real and has important social consequences, and someone else says, you can't bring that up, it's discriminatory. Well, no, that's a category error. That sort of thing ''can't'' be discriminatory. --] (]) 01:29, 17 January 2025 (UTC)
*:::just drop it ]] 01:23, 17 January 2025 (UTC)
*I would remove anything to do with polical position. Those on the far-right should be discriminated against. '']''<sup>]</sup> 21:45, 16 January 2025 (UTC)
It's not a bad idea, but I think it will just shift the current arguments about what categories are important enough to exist into arguments about what categories are important enough to be visible. And there will still be plenty of categories created that aren't even fit for hiding. ] 16:13, 20 March 2007 (UTC)
:* The examples you use show that we've been dealing effectively without this additional set of guidelines; it would be more convincing that something was needed if you had examples where the lack of this policy caused bad outcomes. And I can see it being used as a hammer; while we're probably picturing "as a White man, I'm sure that I understand chemistry better than any of you lesser types" as what we're going after, I can see some folks trying to wield it against "as a Comanche raised on the Comanche nation, I think I have some insights on the Comanche language that others here are overlooking." As such, I'm cautious. -- ] (]) 21:49, 16 January 2025 (UTC)
Honestly, having sections of any sort that could be hidden or shown would I believe be the next evolutionary step to Misplaced Pages. For being not paper, this place sure does set everything up like it was, having to have a totally separate page for anything that doesn't quite fit in a main article. ] 17:37, 20 March 2007 (UTC)
*'''Comment'''. I am sorry that ] discrimination is being ignored here. ] (]) 21:54, 16 January 2025 (UTC).
*'''Not needed'''. Everything the proposal is talking about would constitute disruptive behavior, and we can block or ban someone for being disruptive already. No need to break disruption down into its component parts, and write rules for each. ] (]) 22:07, 16 January 2025 (UTC)
{{reflist-talk}}
{{Discussion bottom}}
====Another perspective about categories====
== Repeated false retirement ==
When I try to go through categories, I would like to point out another viewpoint here to try and resolve. Often when I go to some categories, I see that there are hundreds (or even thousands!) of articles that are in that category. This sometimes get to be very time consuming to try and find something specific if you are actually going to use the category system to look up a piece of related information.... IMHO the main reason to be using the category system as a reader. The point being is how many people here actually look on page seven (listed 200 articles per page) of the category listing to actually find an article? Even with alphabet bars and other navigational techniques, it becomes something nearly meaningless.
There is a user (who shall remain unnamed) who has "retired" twice and had the template removed from their page by other users because they were clearly still editing. They are now on their third "retirement", yet they last edited a few days ago. I don't see any policy formally prohibiting such behavior, but it seems extremely unhelpful for obvious reasons. ] 17:13, 16 January 2025 (UTC)
See ] for a good example.
:Unless the material is harmful to Misplaced Pages or other users, users have considerable leeway in what they may post on their user page. Personally, I always take "retirement" notices with a grain of salt. If a user wants to claim they are retired even though they are still actively editing, I don't see the harm to anything but their credibility. If I want to know if an editor is currently active, I look at their contributions, not at notices on their user or talk page. ] 22:07, 16 January 2025 (UTC)
My question as it relates to these hidden categories is how would this help at all in this situation? To me, it would cause some of these categories to grow even more substantially. Perhaps there is some minor value added to these sort of monster categories, but I'm not sure what it really is. --] 21:19, 20 March 2007 (UTC)
:{{br}}I can't imagine that this calls for a policy. You're allowed to be annoyed if you want. No one can take that away from you. But I'm missing an explanation of why the rest of us should care. --] (]) 22:13, 16 January 2025 (UTC)
::This seems a little prickly, my friend. Clearly, the other two users who removed older retirement notices cared. At the end of the day, it's definitely not the most major thing, but it is helpful to have a reliable and simple indication as to whether or not a user can be expected to respond to any kind of communication or feedback. I'm not going to die on this hill. Cheers. ] 22:41, 16 January 2025 (UTC)
The policy section of the village pump is intended for discussions about already-proposed policies and guidelines, as well as changes to existing ones. Discussions often begin on other pages and are subsequently moved or referenced here to ensure greater visibility and broader participation.
If you wish to propose something new that is not a policy or guideline, use Village pump (proposals). Alternatively, for drafting with a more focused group, consider starting the discussion on the talk page of a relevant WikiProject, the Manual of Style, or another relevant project page.
For questions about how to apply existing policies or guidelines, refer to one of the many Misplaced Pages:Noticeboards.
If you want to inquire about what the policy is on a specific topic, visit the Help desk or the Teahouse.
This is not the place to resolve disputes regarding the implementation of policies. For such cases, consult Misplaced Pages:Dispute resolution.
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
There is a strong consensus that comments that do not represent an actual person's thoughts are not useful in discussions. Thus, if a comment is written entirely by an LLM, it is (in principle) not appropriate. The main topic of debate was the enforceability of this principle. Opinions vary on the reliability of GPTZero, and I would say there is a rough consensus against any form of AI detection that relies solely on it or other automated tools. Overall, however, I see a consensus that it is within admins' and closers' discretion to discount, strike, or collapse obvious use of generative LLMs or similar AI technologies. This is a WP:DUCK matter, and as with other WP:DUCK matters, there is not going to be a blackletter definition of "obvious", but I think we can all agree there are some comments that could only ever be LLM-generated. As with other matters of discretion, like behavioral sockpuppetry blocks, experienced users can apply their best judgment, subject to community review.The word "generative" is very, very important here, though. This consensus does not apply to comments where the reasoning is the editor's own, but an LLM has been used to refine their meaning. Editors who are non-fluent speakers, or have developmental or learning disabilities, are welcome to edit here as long as they can follow our policies and guidelines; this consensus should not be taken to deny them the option of using assistive technologies to improve their comments. In practice, this sets a good lower bound for obviousness, as any comment that could conceivably be LLM-assisted is, by definition, not obviously LLM-generated.Regarding comments that are more borderline in LLM likelihood, it's worth reviewing what's already allowed by policy and guidelines: LLM-written comments will usually add little of substance to a discussion, and closers are already expected to ignore unhelpful comments. If comments contain fabrications of fact, that is a blockable form of disruptive editing, whether or not the fabrication is by a human or a hallucinating chatbot. And while WP:TPO says disruptive comments "are usually best left as-is or archived", there is a "usually" in there, so removing patently disruptive content is within editors' discretion, whether or not LLM usage is unambiguous. -- Tamzin (they|xe|🤷) 21:21, 12 January 2025 (UTC)
Should admins or other users evaluating consensus in a discussion discount, ignore, or strike through or collapse comments found to have been generated by AI/LLM/Chatbots? 00:12, 2 December 2024 (UTC)
I've recently come across several users in AFD discussions that are using LLMs to generate their remarks there. As many of you are aware, gptzero and other such tools are very good at detecting this.
I don't feel like any of us signed up for participating in discussions where some of the users are not using their own words but rather letting technology do it for them. Discussions are supposed to be between human editors. If you can't make a coherent argument on your own, you are not competent to be participating in the discussion. I would therefore propose that LLM-generated remarks in discussions should be discounted or ignored, and possibly removed in some manner. Just Step Sideways00:12, 2 December 2024 (UTC)
Seems reasonable, as long as the GPTZero (or any tool) score is taken with a grain of salt. GPTZero can be as wrong as AI can be. ~ ToBeFree (talk) 00:32, 2 December 2024 (UTC)
Only if the false positive and false negative rate of the tool you are using to detect LLM content is very close to zero. LLM detectors tend to be very unreliable on, among other things, text written by non-native speakers. Unless the tool is near perfect then it's just dismissing arguments based on who wrote them rather than their content, which is not what we do or should be doing around here. Thryduulf (talk) 00:55, 2 December 2024 (UTC)
The more I read the comments from other editors on this, the more I'm a convinced that implementing either this policy or something like it will bring very significant downsides on multiple fronts that significantly outweigh the small benefits this would (unreliably) bring, benefits that would be achieved by simply reminding closers to disregard comments that are unintelligible, meaningless and/or irrelevant regardless of whether they are LLM-generated or not. For the sake of the project I must withdraw my previous very qualified support and instead very strongly oppose. Thryduulf (talk) 02:45, 3 December 2024 (UTC)
I think it should be an expressly legitimate factor in considering whether to discount or ignore comments either if it's clear enough by the text or if the user clearly has a history of using LLMs. We wouldn't treat a comment an editor didn't actually write as an honest articulation of their views in lieu of site policy in any other situation. Remsense ‥ 论00:59, 2 December 2024 (UTC)
I would have already expected admins to exercise discretion in this regard, as text written by an LLM is not text written by a person. We cannot guarantee it is what the person actually means, especially as it is a tool often used by those with less English proficiency, which means perhaps they cannot evaluate the text themselves. However, I do not think we can make policy about a specific LLM or tool. The LLM space is moving fast, en.wiki policies do not. Removal seems tricky, I would prefer admins exercise discretion instead, as they do with potentially canvassed or socked !votes. CMD (talk) 01:06, 2 December 2024 (UTC)
As the discussion has moved forward below, I feel I can shift to a more explicit support in terms of providing guidance to closers and those otherwise evaluating consensus. CMD (talk) 17:33, 2 January 2025 (UTC)
Support discounting or collapsing AI-generated comments, under slightly looser conditions than those for human comments. Not every apparently-AI-generated comment is useless hallucinated nonsense – beyond false positives, it's also possible for someone to use an AI to help them word a constructive comment, and make sure that it matches their intentions before they publish it. But in my experience, the majority of AI-generated comments are somewhere between "pointless" and "disruptive". Admins should already discount clearly insubstantial !votes, and collapse clearly unconstructive lengthy comments; I think we should recognize that blatant chatbot responses are more likely to fall into those categories. jlwoodwa (talk) 02:11, 2 December 2024 (UTC)
Strongly Support - I think some level of human judgement on the merits of the argument are necessary, especially as GPTZero may still have a high FPR. Still, if the discussion is BLUDGEONy, or if it quacks like an AI-duck, looks like an AI-duck, etc, we should consider striking out such content.- sidenote, I'd also be in favor of sanctions against users who overuse AI to write out their arguments/articles/etc. and waste folks time on here.. Bluethricecreamman (talk) 02:20, 2 December 2024 (UTC)
On a wording note, I think any guidance should avoid referring to any specific technology. I suggest saying "... to have been generated by a program". isaacl (talk) 02:54, 2 December 2024 (UTC)
A translation program, whether it is between languages or from speech, is not generating a comment, but converting it from one format to another. A full policy statement can be more explicit in defining "generation". The point is that the underlying tech doesn't matter; it's that the comment didn't feature original thought from a human. isaacl (talk) 03:57, 2 December 2024 (UTC)
Support. We already use discretion in collapsing etc. comments by SPAs and suspected socks, it makes sense to use the same discretion for comments suspected of being generated by a non-human. JoelleJay (talk) 03:07, 2 December 2024 (UTC)
Support - Someone posting "here's what ChatGPT has to say on the subject" can waste a lot of other editors' time if they feel obligated to explain why ChatGPT is wrong again. I'm not sure how to detect AI-written text but we should take a stance that it isn't sanctioned. Clayoquot (talk | contribs) 04:37, 2 December 2024 (UTC)
Strong Support - I've never supported using generative AI in civil discourse. Using AI to participate in these discussions is pure laziness, as it is substituting genuine engagement and critical thought with a robot prone to outputting complete garbage. In my opinion, if you are too lazy to engage in the discussion yourself, why should we engage with you? Lazman321 (talk) 05:26, 2 December 2024 (UTC)
Because it's based on a potentially false premise that it will be possible to reliably distinguish between text generated by human biological neural networks and text generated by non-biological neural networks by observing the text. It is already quite difficult in many cases, and the difficulty is increasing very rapidly. I have your basic primate brain. The AI companies building foundation models have billions of dollars, tens of thousands, soon to be hundreds of thousands of GPUs, a financial incentive to crack this problem and scaling laws on their side. So, I have very low credence in the notion that I will be able to tell whether content is generated by a person or a person+LLM or an AI agent very soon. On the plus side, it will probably still be easy to spot people making non-policy based arguments regardless of how they do it. Sean.hoyland (talk) 13:52, 2 December 2024 (UTC)
...and now that the systems are autonomously injecting their output back into model via chain-of-thought prompting, or a kind of inner monologue if you like, to respond to questions, they are becoming a little bit more like us. Sean.hoyland (talk) 14:14, 2 December 2024 (UTC)
A transformer (deep learning architecture) is intrinsically nothing like a human. It's a bunch of algebra that can compute what a decently sensible person could write in a given situation based on its training data, but it is utterly incapable of anything that could be considered thought or reasoning. This is why LLMs tend to fail spectacularly when asked to do math or write non-trivial code. Flounder fillet (talk) 17:20, 2 December 2024 (UTC)
We shall see. You might want to update yourself on their ability to do math and write non-trivial code. Things are changing very quickly. Either way, it is not currently possible to say much about what LLMs are actually doing because mechanistic interpretability is in its infancy. Sean.hoyland (talk) 03:44, 3 December 2024 (UTC)
Support and I would add "or similar technologies" to "AI/LLM/Chatbots". As for Sean.hoyland's comment, we will cross that bridge when we get to it. Cullen328 (talk) 05:51, 2 December 2024 (UTC)
Support - All editors should convey their thoughts in their own words. AI generated responses and comments are disruptive because they are pointless and not meaningful. - Ratnahastin (talk) 06:04, 2 December 2024 (UTC)
Support, I already more or less do this. An LLM generated comment may or may not actually reflect the actual thoughts of the editor who posted it, so it's essentially worthless toward a determination of consensus. Since I wrote this comment myself, you know that it reflects my thoughts, not those of a bot that I may or may not have reviewed prior to copying and pasting. Seraphimblade06:59, 2 December 2024 (UTC)
Strong oppose. Let me say first that I do not like ChatGPT. I think it has been a net negative for the world, and it is by nature a net negative for the physical environment. It is absolutely a net negative for the encyclopedia if LLM-generated text is used in articles in any capacity. However, hallucinations are less of an issue on talk pages because they're discussions. If ChatGPT spits out a citation of a false policy, then obviously that comment is useless. If ChatGPT spits out some boilerplate "Thanks for reviewing the article, I will review your suggestions and take them into account" talk page reply, who gives a fuck where it came from? (besides the guys in Texas getting their eardrums blown out because they live by the data center)The main reason I oppose, though, is because banning LLM-generated comments is difficult to enforce bordering on unenforceable. Most studies show that humans are bad at distinguishing AI-generated text from text generated without AI. Tools like GPTZero claims a 99% accuracy rate, but that seems dubious based on reporting on the matter. The news outlet Futurism (which generally has an anti-AI slant) has failed many times to replicate that statistic, and anecdotal accounts by teachers, etc. are rampant. So we can assume that we don't know how capable AI detectors are, that there will be some false positives, and that striking those false positives will result in WP:BITING people, probably newbies, younger people more accustomed to LLMs, and non-Western speakers of English (see below).There are also technological issues as play. It'd be easy if there was a clean line between "totally AI-generated text" and "totally human-generated text," but that line is smudged and well on its way to erased. Every tech company is shoving AI text wrangling into their products. This includes autocomplete, translation, editing apps, etc. Should we strike any comment a person used Grammarly or Google Translate for? Because those absolutely use AI now.And there are also, as mentioned above, cultural issues. The people using Grammarly, machine translation, or other such services are likely to not have English as their first language. And a lot of the supposed "tells" of AI-generated content originate in the formal English of other countries -- for instance, the whole thing where "delve" was supposedly a tell for AI-written content until people pointed out the fact that lots of Nigerian workers trained the LLM and "delve" is common Nigerian formal English.I didn't use ChatGPT to generate any of this comment. But I am also pretty confident that if I did, I could have slipped it in and nobody would have noticed until this sentence. Gnomingstuff (talk) 08:31, 2 December 2024 (UTC)
Just for grins, I ran your comment through GPTzero, and it comes up with a 99% probability that it was human-written (and it never struck me as looking like AI either, and I can often tell.) So, maybe it's more possible to distinguish than you think? Seraphimblade20:11, 2 December 2024 (UTC)
Support - Ai-generated comments are WP:DISRUPTIVE - An editor who has an argument should not use ChatGPT to present it in an unnecessarily verbose manner, and an editor who doesn't have one should not participate in discussion. Flounder fillet (talk) 13:14, 2 December 2024 (UTC)
They exist, and I found myself collapsing some long, obviously chatbot-generated posts in an AFD, and after I did so wondering if policy actually supported doing that. I couldn't find anything so here we are. Just Step Sideways20:04, 2 December 2024 (UTC)
Yes, of course, and I know that's the right answer because ChatGPT agrees with me.
What ChatGPT thinks
I started by asking:
Currently at the English Misplaced Pages, there's a discussion of the following proposal: "Should or other users evaluating consensus in a discussion discount, ignore, or strike through or collapse comments found to have been generated by AI/LLM/Chatbots?" I wonder if you have an opinion on that question.
My friend the bot initially proposed a requirement that any AI-generated content be labeled as such by the person posting it. After some further discussion between us, I finally said:
You say that labeling AI-generated content, instead of outright discounting it, might be an appropriate middle ground. But if someone is unable to formulate their own thoughts and put them in writing, of what use is it to the discussion for this person to simply ask you to make something up, and then post your output to the Misplaced Pages discussion with the proviso that "ChatGPT, who/which doesn't actually know anything about anything, said this ..."? How is it different from saying, "My grandmother, who knows nothing about what we're talking about, said ..."?
And it said:
That’s an incisive question, and it highlights the crux of the issue: the value of contributions to a discussion. Here’s why AI-generated comments might still differ (slightly) from your hypothetical grandmother’s input, but why their usefulness is often limited:
Synthesis vs. Subject Expertise: While I (or any AI) lack personal understanding or expertise, I can aggregate and articulate relevant ideas from a vast dataset. This means I can sometimes present arguments, summarize perspectives, or surface considerations that a non-expert human might overlook. Your grandmother, unless she's an AI-trained polymath, wouldn’t be able to provide this breadth. However, this advantage evaporates if participants lack the ability to evaluate and critically engage with my output.
The Problem of Proxy Voices: The act of outsourcing one’s contribution to AI undermines the deliberative process central to Misplaced Pages’s discussions. Participants are expected to bring their own informed perspectives, shaped by personal understanding of Misplaced Pages’s policies and content. A disclaimer like “ChatGPT said this” doesn’t change the fact that the human posting it has abdicated their role in the discussion.
Accountability and Intent: In a collaborative setting like Misplaced Pages, contributions are ideally linked to a person who can clarify their intent, respond to questions, and engage dynamically. An AI cannot do this. Saying "ChatGPT said this" distances the poster from the content, making it unclear whether they endorse or even understand the comment.
Potential for Misdirection: Allowing AI-generated contributions risks introducing noise into the discussion. AI can produce plausible-sounding arguments that may be tangential, misaligned, or even factually incorrect. Without the judgment of a well-informed poster, such contributions can derail or dilute meaningful discourse.
Conclusion: If someone cannot formulate their own argument or understanding, then their reliance on an AI—or anyone else—to contribute doesn’t meaningfully advance the discussion. Labeling AI-generated content is better than passing it off as human, but the real issue lies in whether such contributions enrich or degrade the collaborative process. In most cases, they would seem to belong more to the realm of rhetorical curiosities than substantive engagement.
In keeping with the proposed guideline, I have of course collapsed the above AI-generated content. (Later: It's actually worth reading in the context of this discussioin, so I've unhidden it by default.) But I must confess it's a pretty good analysis, and worth reading. EEng07:47, 2 December 2024 (UTC)
This is absolute gold dust and the best contribution to this discussion so far. There is an enormous irony here, one that might not be immediately obvious. The proposal is that we should ignore or even strike these type of contributions, but personally it seems like the collapsed format has worked a charm here. I really don't think that AI has much to contribute to WP discussions generally, but with the right prompt, there is certainly something worth adding to the conversation in reality. CNC (talk) 20:23, 8 December 2024 (UTC)
That's because, just by interacting with me, ChatGPT got smarter. Seriously ... you want it to say 99% every time? (And for the record, the idea of determining the "chance" that something is AI-generated is statistical nonsense.) EEng03:07, 3 December 2024 (UTC)
What I really want is a 100% chance that it won't decide that what I've written is AI-generated. Past testing has demonstrated that at least some of the detectors are unreliable on this point. WhatamIdoing (talk) 03:28, 4 December 2024 (UTC)
100% is, of course, an impossible goal. Certainly SPI doesn't achieve that, so why demand it here? EEng22:31, 4 December 2024 (UTC)
Strong Oppose I support the concept of removal of AI-generated content in theory. However, we do not have the means to detect such AI-generated content. The proposed platform that we may use (GPTZero) is not reliable for this purpose. In fact, our own page on GPTZero has a section citing several sources stating the problem with this platform's accuracy. It is not helpful to have a policy that is impossible to enforce. ThatIPEditor08:46, 2 December 2024 (UTC)
Strong Support To be honest, I am surprised that this isn't covered by an existing policy. I oppose the use of platforms like GPTZero, due to it's unreliability, but if it is obviously an ai-powered-duck (Like if it is saying shit like "as an AI language model...", take it down and sanction the editor who put it up there. ThatIPEditor08:54, 2 December 2024 (UTC)
Support at least for WP:DUCK-level AI-generated comments. If someone uses a LLM to translate or improve their own writing, there should be more leeway, but something that is clearly a pure ChatGPT output should be discounted. Chaotic Enby (talk · contribs) 09:17, 2 December 2024 (UTC)
I agree for cases in which it is uncontroversial that a comment is purely AI-generated. However, I don't think there are many cases where this is obvious. The claim that gptzero and other such tools are very good at detecting this is false. Phlsph7 (talk) 09:43, 2 December 2024 (UTC)
Moral support; neutral as written. Chatbot participation in consensus discussions is such an utterly pointless and disdainful abuse of process and community eyeballs that I don't feel like the verbiage presented goes far enough. Any editor may hat LLM-generated comments in consensus discussions is nearer my position. No waiting for the closer, no mere discounting, no reliance on the closer's personal skill at recognising LLM output, immediate feedback to the editor copypasting chatbot output that their behaviour is unwelcome and unacceptable. Some observations:I've seen editors accused of using LLMs to generate their comments probably about a dozen times, and in all but two cases – both at dramaboards – the chatbot prose was unmistakably, blindingly obvious. Editors already treat non-obvious cases as if written by a human, in alignment with the raft of only if we're sure caveats in every discussion about LLM use on the project.If people are using LLMs to punch up prose, correct grammar and spelling, or other superficial tasks, this is generally undetectable, unproblematic, and not the point here.Humans are superior to external services at detecting LLM output, and no evidence from those services should be required for anything.As a disclosure, evidence mounts that LLM usage in discussions elicits maximally unkind responses from me. It just feels so contemptuous, to assume that any of us care what a chatbot has to say about anything we're discussing, and that we're all too stupid to see through the misattribution because someone tacked on a sig and sometimes an introductory paragraph. And I say this as a stupid person. Folly Mox (talk) 11:20, 2 December 2024 (UTC)
Looks like a rewrite is indicated to distinguish between machine translation and LLM-generated comments, based on what I'm seeing in this thread. Once everyone gets this out of our system and an appropriately wordsmithed variant is reintroduced for discussion, I preemptively subpropose the projectspace shortcut WP:HATGPT. Folly Mox (talk) 15:26, 8 December 2024 (UTC)
I would be careful here, as there are tools that rely on LLM AI that help to improve the clarity of one's writing, and editors may opt to use those to parse their poor writing (perhaps due to ESL aspects) to something clear. I would agree content 100% generated by AI probably should be discounted particularly if from an IP or new editors (hints if socking or meat puppetry) but not all cases where AI has come into play should be discounted — Masem (t) 14:19, 2 December 2024 (UTC)
Support, cheating should have no place or take its place in writing coherent comments on Misplaced Pages. Editors who opt to use it should practice writing until they rival Shakespeare, or at least his cousin Ned from across the river, and then come back to edit. Randy Kryn (talk) 14:29, 2 December 2024 (UTC)
Support atleast for comments that are copied straight from the LLM . However, we should be more lenient if the content is rephrased by non-native English speakers due to grammar issues The AP (talk) 15:10, 2 December 2024 (UTC)
section break 1
Support for LLM-generated content (until AI is actually intelligent enough to create an account and contribute on a human level, which may eventually happen). However, beware of the fact that some LLM-assisted content should probably be allowed. An extreme example of this: if a non-native English speaker were to write a perfectly coherent reason in a foreign language, and have an LLM translate it to English, it should be perfectly acceptable. Animal lover|666|16:47, 2 December 2024 (UTC)
Data, being a fictional creation with rights owned by a corporation, will not have an account; he is inherently an IP editor. -- Nat Gertler (talk) 03:22, 20 December 2024 (UTC)
Oppose - I think the supporters must have a specific type of AI-generated content in mind, but this isn't a prohibition on one type; it's a prohibition on the use of generative AI in discussions (or rather, ensuring that anyone who relies on such a tool will have their opinion discounted). We allow people who aren't native English speakers to contribute here. We also allow people who are native English speakers but have difficulty with language (but not with thinking). LLMs are good at assisting both of these groups of people. Furthermore, as others pointed out, detection is not foolproof and will only get worse as time goes on, models proliferate, models adapt, and users of the tools adapt. This proposal is a blunt instrument. If someone is filling discussions with pointless chatbot fluff, or we get a brand new user who's clearly using a chatbot to feign understanding of wikipolicy, of course that's not ok. But that is a case by case behavioral issue. I think the better move would be to clarify that "some forms of LLM use can be considered disruptive and may be met with restrictions or blocks" without making it a black-and-white issue. — Rhododendrites \\ 17:32, 2 December 2024 (UTC)
I agree the focus should not be on whether or not a particular kind of tech was used by an editor, but whether or not the comment was generated in a way (whether it's using a program or ghost writer) such that it fails to express actual thoughts by the editor. (Output from a speech-to-text program using an underlying large language model, for instance, isn't a problem.) Given that this is often hard to determine from a single comment (everyone is prone to post an occasional comment that others will consider to be off-topic and irrelevant), I think that patterns of behaviour should be examined. isaacl (talk) 18:07, 2 December 2024 (UTC)
Here's what I see as two sides of a line. The first is, I think, something we can agree would be inappropriate. The second, to me at least, pushes up against the line but is not ultimately inappropriate. But they would both be prohibited if this passes. (a) "I don't want an article on X to be deleted on Misplaced Pages. Tell me what to say that will convince people not to delete it"; (b) "I know Misplaced Pages deletes articles based on how much coverage they've received in newspapers, magazines, etc. and I see several such articles, but I don't know how to articulate this using wikipedia jargon. Give me an argument based on links to wikipedia policy that use the following sources as proof ". Further into the "acceptable" range would be things like translations, grammar checks, writing a paragraph and having an LLM improve the writing without changing the ideas, using an LLM to organize ideas, etc. I think what we want to avoid are situations where the arguments and ideas themselves are produced by AI, but I don't see such a line drawn here and I don't think we could draw a line without more flexible language. — Rhododendrites \\ 18:47, 2 December 2024 (UTC)
Here we return to my distinction between AI-generated and AI-assisted. A decent speech-to-text program doesn't actually generate content. Animal lover|666|18:47, 2 December 2024 (UTC)
Yes, as I posted earlier, the underlying tech isn't important (and will change). Comments should reflect what the author is thinking. Tools (or people providing advice) that help authors express their personal thoughts have been in use for a long time. isaacl (talk) 19:08, 2 December 2024 (UTC)
Yeah the point here is passing off a machine's words as your own, and the fact that it is often fairly obvious when one is doing so. If a person is not competent to express their own thoughts in plain English, they shouldn't be in the discussion. This certainly is not aimed at assistive technology for those who actually need it but rather at persons who are simply letting Chatbots speak for them. Just Step Sideways20:10, 2 December 2024 (UTC)
This doesn't address what I wrote (though maybe it's not meant to). If a person is not competent to express their own thoughts in plain English, they shouldn't be in the discussion. This certainly is not aimed at assistive technology for those who actually need it but rather at persons who are simply letting Chatbots speak for them is just contradictory. Assistive technologies are those that can help people who aren't "competent" to express themselves to your satisfaction in plain English, sometimes helping with the formulation of a sentence based on the person's own ideas. There's a difference between having a tool that helps me to articulate ideas that are my own and a tool that comes up with the ideas. That's the distinction we should be making. — Rhododendrites \\ 21:23, 2 December 2024 (UTC)
I agree with Rhododendrites that we shouldn't be forbidding users from seeking help to express their own thoughts. Getting help from someone more fluent in English, for example, is a good practice. Nowadays, some people use generative technology to help them prepare an outline of their thoughts, so they can use it as a starting point. I think the community should be accepting of those who are finding ways to write their own viewpoints more effectively and concisely, even if that means getting help from someone or a program. I agree that using generative technology to come up with the viewpoints isn't beneficial for discussion. isaacl (talk) 22:58, 2 December 2024 (UTC)
Non-native English speakers and non-speakers to whom a discussion is important enough can already use machine translation from their original language and usually say something like "Sorry, I'm using machine translation". Skullers (talk) 08:34, 4 December 2024 (UTC)
Oppose Contributions to discussions are supposed to be evaluated on their merits per WP:NOTAVOTE. If an AI-assisted contribution makes sense then it should be accepted as helpful. And the technical spectrum of assistance seems large and growing. For example, as I type this into the edit window, some part of the interface is spell-checking and highlighting words that it doesn't recognise. I'm not sure if that's coming from the browser or the edit software or what but it's quite helpful and I'm not sure how to turn it off. Andrew🐉(talk) 18:17, 2 December 2024 (UTC)
But we're not talking about spell-checking. We're talking about comments clearly generated by LLMs, which are inherently unhelpful. Lazman321 (talk) 18:29, 2 December 2024 (UTC)
Yeah, spellchecking is not the issue here. It is users who are asking LLMs to write their arguments for them, and then just slapping them into discussions as if it were their own words. Just Step Sideways20:12, 2 December 2024 (UTC)
Andrew's first two sentences also seem to imply that he views AI-generated arguments that makes sense as valid, and that we should consider what AI thinks about a topic. I'm not sure what to think about this, especially since AI can miss out on a lot of the context. Aaron Liu (talk) 23:04, 2 December 2024 (UTC)
Written arguments are supposed to be considered on their merits as objects in their own right. Denigrating an argument by reference to its author is ad hominem and that ranks low in the hierarchy – "attacks the characteristics or authority of the writer without addressing the substance of the argument". Andrew🐉(talk) 23:36, 2 December 2024 (UTC)
An AI chatbot isn't an "author", and it's impossible to make an ad hominem attack on one, because a chotbot is not a homo. EEng17:45, 6 December 2024 (UTC)
On the other hand, "exhausting the community's patience"/CompetenceIsRequired is a very valid rationale from stopping someone from partricipating. Aaron Liu (talk) 23:50, 2 December 2024 (UTC)
The spell-checking was an immediate example but there's a spectrum of AI tools and assistance. The proposed plan is to use an AI tool to detect and ban AI contributions. That's ludicrous hypocrisy but suggests an even better idea – that we use AIs to close discussions so that we don't get the bias and super-voting. I see this on Amazon regularly now as it uses an AI to summarise the consensus of product reviews. For example,
Customers say Customers appreciate the gloves for their value, ease of use, and gardening purposes. They find the gloves comfortable and suitable for tasks like pruning or mowing. However, opinions differ on how well they fit. AI-generated from the text of customer reviews
I asked Google's Gemini to "summarise the consensus of the following RFC discussion", giving it the 87 comments to date.
AI summary of the RfC to date
This Misplaced Pages Request for Comment (RfC) debates whether comments in discussions that are found to be generated by AI/LLM/Chatbots should be discounted, ignored, or removed.
Arguments for discounting/removing AI-generated comments:
AI comments don't represent genuine human engagement or thought. They can be disruptive, waste time, and even fabricate information.
AI can be used to manipulate discussions. Editors might use AI to generate arguments they don't actually believe in, or to flood discussions with low-quality comments.
Relying on AI undermines the integrity of Misplaced Pages's consensus-based process. Discussions should be based on the genuine opinions of human editors.
Arguments against discounting/removing AI-generated comments:
Difficulty of detection. AI detection tools are not always reliable, and it can be hard to distinguish between AI-generated text and human-written text, especially as AI technology improves.
Potential for misuse. False positives could lead to legitimate comments being dismissed, potentially silencing non-native English speakers or those who use AI for legitimate assistive purposes (e.g., translation, grammar checks).
Focus on content, not origin. Comments should be evaluated based on their merits, not on how they were generated. If an AI-generated comment is relevant and well-reasoned, it shouldn't be dismissed simply because of its origin.
LLMs can be helpful tools. LLMs can help editors express their thoughts more clearly, especially for non-native speakers or those with language difficulties.
Current Status (as of Dec 3rd, 2024):
No clear consensus has emerged. There is significant support for discounting or removing AI-generated comments, but also strong opposition.
Concerns about enforceability and potential harm. Many editors are worried about the practical challenges of implementing and enforcing such a rule, as well as the potential for it to be used unfairly against certain editors.
Ongoing discussion. The discussion is still active, and it remains to be seen whether a consensus will form.
It's important to note that this is an evolving situation, and the outcome of the RfC could have significant implications for how Misplaced Pages handles AI-generated content in the future.
That seems quite a fair and good summary of what's been said so far. I'm impressed and so my !vote stands.
Yeah, the ability to weigh each side and the quality of their arguments in an RFC can really only be done by the judgement and discretion of an experienced human editor. Lazman321 (talk) 20:08, 4 December 2024 (UTC)
The quality of the arguments and their relevance to polices and guidelines can indeed only be done by a human, but the AI does a good job of summarising which arguments have been made and a broad brush indication of frequency. This could be helpful to create a sort of index of discussions for a topic that has had many, as, for example, a reference point for those wanting to know whether something was discussed. Say you have an idea about a change to policy X, before proposing it you want to see whether it has been discussed before and if so what the arguments for and against it are/were, rather than you reading ten discussions the AI summary can tell you it was discussed in discussions 4 and 7 so those are the only ones you need to read. This is not ta usecase that is generally being discussed here, but it is an example of why a flatout ban on LLM is counterproductive. Thryduulf (talk) 21:40, 4 December 2024 (UTC)
Support Just the other day, I spent ~2 hours checking for the context of several quotes used in an RFC, only to find that they were fake. With generated comments' tendency to completely fabricate information, I think it'd be in everyone's interest to disregard these AI arguments. Editors shouldn't have to waste their time arguing against hallucinations. (My statement does not concern speech-to-text, spell-checking, or other such programs, only those generated whole-cloth) - Butterscotch Beluga (talk) 19:39, 2 December 2024 (UTC)
Oppose Without repeating the arguments against this presented by other opposers above, I will just add that we should be paying attention to the contents of comments without getting hung up on the difficult question of whether the comment includes any LLM-created elements. - Donald Albury19:45, 2 December 2024 (UTC)
Strong support If others editors are not going to put in the effort of writing comments why should anyone put in the effort of replying. Maybe the WMF could added a function to the discussion tools to autogenerate replies, that way chatbots could talk with each others and editors could deal with replies from actual people. -- LCU ActivelyDisinterested«@» °∆t°19:57, 2 December 2024 (UTC)
Strong oppose. Comments that are bullshit will get discounted anyways. Valuable comments should be counted. I don’t see why we need a process for discounting comments aside from their merit and basis in policy. ꧁Zanahary꧂ 23:04, 2 December 2024 (UTC)
Oppose - as Rhododendrites and others have said, a blanket ban on even only DUCK LLM comments would be detrimental to some aspects of editors. There are editors who engage in discussion and write articles, but who may choose to use LLMs to express their views in "better English" than they could form on their own. Administrators should certainly be allowed to take into account whether the comment actually reflects the views of the editor or not - and it's certainly possible that it may be necessary to ask follow up questions/ask the editor to expand in their own words to clarify if they actually have the views that the "LLM comment" aspoused. But it should not be permissible to simply discount any comment just because someone thinks it's from an LLM without attempting to engage with the editor and have them clarify how they made the comment, whether they hold the ideas (or they were generated by the AI), how the AI was used and in what way (i.e. just for grammar correction, etc). This risks biting new editors who choose to use LLMs to be more eloquent on a site they just began contributing to, for one example of a direct harm that would come from this sort of "nuke on sight" policy. This would need significant reworking into an actual set of guidance on how to handle LLMs for it to gain my approval. -bɜ:ʳkənhɪmez | me | talk to me!23:19, 2 December 2024 (UTC)
Comment: It would appear Jimbo responded indirectly in a interview: as long as there’s a human in the loop, a human supervising, there are really potentially very good use cases. 2601AC47 (talk·contribs·my rights) Isn't a IP anon 12:39, 4 December 2024 (UTC)
Very strong support. Enough is enough. If Misplaced Pages is to survive as a project, we need zero tolerance for even the suspicion of AI generation and, with it, zero tolerance for generative AI apologists who would happily open the door to converting the site to yet more AI slop. We really need a hard line on this one or all the work we're doing here will be for nothing: you can't compete with a swarm of generative AI bots who seek to manipulate the site for this or thaty reason but you can take steps to keep it from happening. :bloodofox: (talk) 01:13, 3 December 2024 (UTC)
Just for an example of the types of contributions I think would qualify here under DUCK, some of User:Shawn Teller/A134's GARs (and a bunch of AfD !votes that have more classic indications of non-human origin) were flagged as likely LLM-generated troll nonsense:
But thanks to these wonderful images, I now understand that Ontario Highway 11 is a paved road that vehicles use to travel.
This article is extensive in its coverage of such a rich topic as Ontario Highway 11. It addresses the main points of Ontario Highway 11 in a way that isn’t just understandable to a reader, but also relatable.
Neutral point of view without bias is maintained perfectly in this article, despite Ontario Highway 11 being such a contentious and controversial topic.
Yes, this could and should have been reverted much earlier based on being patently superficial and/or trolling, without needing the added issue of appearing LLM-generated. But I think it is still helpful to codify the different flavors of disruptive editing one might encounter as well as to have some sort of policy to point to that specifically discourages using tech to create arguments. As a separate point, LTAs laundering their comments through GPT to obscure their identity is certainly already happening, so making it harder for such comments to "count" in discussions would surely be a net positive. JoelleJay (talk) 01:18, 3 December 2024 (UTC)
For the purposes of this proposal, I don't think we need, or should ever rely solely on, GPTzero in evaluating content for non-human origin. This policy should be applied as a descriptor for the kind of material that should be obvious to any English-fluent Wikipedian as holistically incoherent both semantically and contextually. Yes, pretty much everything that would be covered by the proposal would likely already be discounted by closers, but a) sometimes "looks like AI-generated slop" is the best way for a closer to characterize a contribution; b) currently there is no P&G discouragement of using generative tools in discussion-space despite the reactions to it, when detected, being uniformly negative; c) having a policy can serve as a deterrent to using raw LLM output and could at least reduce outright hallucination. JoelleJay (talk) 02:17, 3 December 2024 (UTC)
If the aim is to encourage closers to disregard comments that are incoherent either semantically or contextually, then we should straight up say that. Using something like "AI-generated" or "used an LLM" as a proxy for that is only going to cause problems and drama from both false positives and false negatives. Judge the comment on its content not on its author. Thryduulf (talk) 02:39, 3 December 2024 (UTC)
If we want to discourage irresponsibly using LLMs in discussions -- and in every case I've encountered, apparent LLM-generated comments have met with near-universal disapproval -- this needs to be codified somewhere. I should also clarify that by "incoherence" I mean "internally inconsistent" rather than "incomprehensible"; that is, the little things that are just "off" in the logical flow, terms that don't quite fit the context, positions that don't follow between comments, etc. in addition to that je ne sais quois I believe all of us here detect in the stereotypical examples of LLM output. Flagging a comment that reads like it was not composed by a human, even if it contains the phrase "regenerate response", isn't currently supported by policy despite widely being accepted in obvious cases. JoelleJay (talk) 03:52, 3 December 2024 (UTC)
I feel that I'm sufficiently unfamiliar with LLM output to be confident in my ability to detect it, and I feel like we already have the tools we need to reject internally incoherent comments, particularly in the Misplaced Pages:Consensus policy, which says In determining consensus, consider the quality of the arguments, the history of how they came about, the objections of those who disagree, and existing policies and guidelines. The quality of an argument is more important than whether it represents a minority or a majority view. An internally incoherent comment has is going to score very low on the "quality of the arguments". WhatamIdoing (talk) 03:33, 4 December 2024 (UTC)
Very extra strong oppose - The tools to detect are at best not great and I don't see the need. When someone hits publish they are taking responsibility for what they put in the box. That does not change when they are using a LLM. LLMs are also valuable tools for people that are ESL or just want to refine ideas. So without bullet proof detection this is doa. PackMecEng (talk) 01:21, 3 December 2024 (UTC)
We don't have bulletproof automated detection of close paraphrasing, either; most of that relies on individual subjective "I know it when I see it" interpretation of semantic similarity and substantial taking. JoelleJay (talk) 04:06, 3 December 2024 (UTC)
One is a legal issue the other is not. Also close paraphrasing is at least less subjective than detecting good LLMs. Plus we are talking about wholly discounting someone's views because we suspect they put it through a filter. That does not sit right with me. PackMecEng (talk) 13:38, 3 December 2024 (UTC)
For sure and I can see that concern, but I think the damage that does is less than the benefit it provides. Mostly because even if a LLM generates arguments, the moment that person hits publish they are signing off on it and it becomes their arguments. Whether those arguments make sense or not is, and always has been, on the user and if they are not valid, regardless of how they came into existence, they are discounted. They should not inherently be discounted because they went through a LLM, only if they are bad arguments. PackMecEng (talk) 14:57, 3 December 2024 (UTC)
section break 3
While it’s true that the person publishing arguments takes responsibility, the use of a large language model (LLM) can blur the line of authorship. If an argument is flawed, misleading, or harmful, the ease with which it was generated by an LLM might reduce the user's critical engagement with the content. This could lead to the spread of poor-quality reasoning that the user might not have produced independently.
Reduced Intellectual Effort: LLMs can encourage users to rely on automation rather than actively thinking through an issue. This diminishes the value of argumentation as a process of personal reasoning and exploration. Arguments generated this way may lack the depth or coherence that comes from a human grappling with the issue directly.
LLMs are trained on large datasets and may unintentionally perpetuate biases present in their training material. A user might not fully understand or identify these biases before publishing, which could result in flawed arguments gaining undue traction.
Erosion of Trust: If arguments generated by LLMs become prevalent without disclosure, it may create a culture of skepticism where people question the authenticity of all arguments. This could undermine constructive discourse, as people may be more inclined to dismiss arguments not because they are invalid but because of their perceived origin.
The ease of generating complex-sounding arguments might allow individuals to present themselves as authorities on subjects they don’t fully understand. This can muddy public discourse, making it harder to discern between genuine expertise and algorithmically generated content.
Transparency is crucial in discourse. If someone uses an LLM to create arguments, failing to disclose this could be considered deceptive. Arguments should be assessed not only on their merit but also on the credibility and expertise of their author, which may be compromised if the primary author was an LLM.
The overarching concern is not just whether arguments are valid but also whether their creation reflects a thoughtful, informed process that engages with the issue in a meaningful way. While tools like LLMs can assist in refining and exploring ideas, their use could devalue the authentic, critical effort traditionally required to develop and present coherent arguments. ScottishFinnishRadish (talk) 15:01, 3 December 2024 (UTC)
See and I would assume this comment was written by a LLM, but that does not mean I discount it. I check and consider it as though it was completely written by a person. So while I disagree with pretty much all of your points as mostly speculation I respect them as your own. But it really just sounds like fear of the unknown and unenforceable. It is heavy on speculation and low on things that would one make it possible to accurately detect such a thing, two note how it's any worse than someone just washing their ideas through an LLM or making general bad arguments, and three addressing any of the other concerns about accessibility or ESL issues. It looks more like a moral panic than an actual problem. You end with the overarching concern is not just weather arguments are valid but also if their creation reflects a thoughtful, informed process that engages with the issues in a meaningful way and honestly that not a thing that can be quantified or even just a LLM issue. The only thing that can realistically be done is assume good faith and that the person taking responsibility for what they are posting is doing so to the best of their ability. Anything past that is speculation and just not of much value. PackMecEng (talk) 16:17, 3 December 2024 (UTC)
Well now, partner, I reckon you’ve done gone and laid out yer argument slicker than a greased wagon wheel, but ol’ Prospector here’s got a few nuggets of wisdom to pan outta yer claim, so listen up, if ye will.
Now, ain't that a fine gold tooth in a mule’s mouth? Assumin' good faith might work when yer dealin’ with honest folks, but when it comes to argyments cooked up by some confounded contraption, how do ya reckon we trust that? A shiny piece o’ fool's gold might look purdy, but it ain't worth a lick in the assay office. Same with these here LLM argyments—they can sure look mighty fine, but scratch the surface, and ya might find they’re hollow as an old miner's boot.
Moral panic, ye say? Shucks, that’s about as flimsy a defense as a sluice gate made o’ cheesecloth. Ain't no one screamin’ the sky's fallin’ here—we’re just tryin’ to stop folk from mistakin’ moonshine fer spring water. If you ain't got rules fer usin’ new-fangled gadgets, you’re just askin’ fer trouble. Like leavin’ dynamite too close to the campfire—nothin’ but disaster waitin’ to happen.
Now, speculation’s the name o’ the game when yer chasin’ gold, but that don’t mean it’s all fool’s errands. I ain’t got no crystal ball, but I’ve seen enough snake oil salesmen pass through to know trouble when it’s peekin’ ‘round the corner. Dismissin’ these concerns as guesswork? That’s like ignorin’ the buzzin’ of bees ‘cause ye don’t see the hive yet. Ye might not see the sting comin’, but you’ll sure feel it.
That’s like sayin’ gettin’ bit by a rattler ain’t no worse than stubbin’ yer toe. Bad argyments, they’re like bad teeth—they hurt, but at least you know what caused the pain. These LLM-contrived argyments, though? They’re sneaky varmints, made to look clever without any real backbone. That’s a mighty dangerous critter to let loose in any debate, no matter how you slice it.
Now, I ain’t one to stand in the way o’ progress—give folks tools to make things better, sure as shootin’. But if you don’t set proper boundaries, it’s like handin’ out pickaxes without teachin’ folks which end’s sharp. Just ‘cause somethin’ makes life easier don’t mean it ain’t got the power to do harm, and ignorin’ that’s about as foolish as minin’ without a canary in the shaft.
Quantify thoughtfulness? That’s like measurin’ a sunset in ounces, friend. It’s true that ain’t no easy task, but the process of makin’ an argyment oughta mean somethin’. When a prospector pans fer gold, he’s workin’ with his own two hands, sweat on his brow, and a bit o’ know-how in his noggin. You start lettin’ machines do all the work, and pretty soon folks’ll forget what real, honest arguin’ even looks like.
Fear o’ the unknown, is it? Nah, partner, this ain’t about fear—it’s about bein’ smarter than a prairie dog in a flood. Progress don’t mean tossin’ caution to the wind like a fool. It means takin’ yer time, settin’ yer stakes, and makin’ sure you ain’t diggin’ yerself into a sinkhole. Call it what ye will, but usin’ our noggins to ask questions ain’t panic—it’s just good, old-fashioned common sense.
So there ya have it. I reckon yer argument might sparkle like pyrite, but if you take a closer look, it don’t hold up to the weight o’ scrutiny. Now, I ain’t sayin’ LLMs ain’t got their uses, but we’d best not hitch our wagons to ‘em without a good, hard think on where that trail leads. ScottishFinnishRadish (talk) 16:26, 3 December 2024 (UTC)
To make my actual point, you said, I check and consider it as though it was completely written by a person. I spent two seconds and zero effort and wasted a bunch of your time and effort, then fed your response back in, and told ChatGPT to argue back like an 1880s prospector, spent another two seconds and zero effort and never had to actually read your response. Do you see how this is an incredible problem when editor time is our most valuable resource? Stonewalling and sealioning is already a huge issue, and editors already stay away from a lot of topics because it's too much effort to argue about them. Allowing an automatic sealion-and-argue button isn't good. ScottishFinnishRadish (talk) 16:30, 3 December 2024 (UTC)
And it took me just a couple minutes to read it, note it was AI, but still consider the points and respond. It was not a high burden on someone's volunteer time. If someone wants to spend their time on something that is on them. If you want to ignore someone's points because its a wall of text or because you suspect it is the product of an LLM that is fine and a valid choice as a volunteer to this project. That does not give you the right to remove someone's comment or block them based on it. I don't see it as disruptive unless it is nonsense or wrong. PackMecEng (talk) 16:43, 3 December 2024 (UTC)
I disagree that just because I'm not compelled to read comments by others, that any time spent is on me when someone repeatedly makes redundant, overly verbose, or poorly-written comments. Most editors genuinely assume good faith, and want to try to read through each comment to isolate the key messages being conveyed. (I've written before about how being respectful of other editors includes being respectful of their time.) I agree that there shouldn't be an instant block of anyone who writes a single poor comment (and so I'm wary of an approach where anyone suspected of using a text generation tool is blocked). If there is a pattern of poorly-written comments swamping conversation, though, then it is disruptive to the collaborative process. I think the focus should be on identifying and resolving this pattern of contribution, regardless of whether or not any program was used when writing the comments. isaacl (talk) 00:14, 4 December 2024 (UTC)
It's a pitfall with English Misplaced Pages's unmoderated discussion tradition: it's always many times the effort to follow the rules than to not. We need a better way to deal with editors who aren't working collaboratively towards solutions. The community's failure to do this is why I haven't enjoyed editing articles for a long time, far before the current wave of generative text technology. More poor writing will hardly be a ripple in the ocean. isaacl (talk) 18:21, 3 December 2024 (UTC)
I tend to agree with this.
I think that what @ScottishFinnishRadish is pointing at is that it doesn't feel fair if one person puts a lot more effort in than the other. We don't want this:
Editor: Spends half an hour writing a long explanation.
Troll: Pushes button to auto-post an argument.
Editor: Spends an hour finding sources to support the claim.
Troll: Laughs while pushing a button to auto-post another argument.
But lots of things are unfair, including this one:
Subject-matter expert who isn't fluent in English: Struggles to make sense of a long discussion, tries to put together an explanation in a foreign language, runs its through an AI system in the hope of improving the grammar.
Editor: Revert, you horrible LLM-using troll! It's so unfair of you to waste my time with your AI garbage. The fact that you use AI demonstrates your complete lack of sincerity.
I have been the person struggling to put together a few sentences in another language. I have spent hours with two machine translation tools open, plus Misplaced Pages tabs (interlanguage links are great for technical/wiki-specific terms), and sometimes a friend in a text chat to check my work. I have tried hard to get it right. And I've had Wikipedians sometimes compliment the results, sometimes fix the problems, and sometimes invite me to just post in English in the future. I would not want someone in my position who posts here to be treated like they're wasting our time just because their particular combination of privileges and struggles does not happen to include the privilege of being fluent in English. WhatamIdoing (talk) 04:04, 4 December 2024 (UTC)
Sure, I agree it's not fair that some editors don't spend any effort in raising their objections (however they choose to write them behind the scenes), yet expect me to expend a lot of effort in responding. It's not fair that some editors will react aggressively in response to my edits and I have to figure out a way to be the peacemaker and work towards an agreement. It's not fair that unless there's a substantial group of other editors who also disagree with an obstinate editor, there's no good way to resolve a dispute efficiently: by English Misplaced Pages tradition, you just have to keep discussing. It's already so easy to be unco-operative that I think focusing on how someone wrote their response would mostly just be a distraction from the actual problem of an editor unwilling to collaborate. isaacl (talk) 06:01, 4 December 2024 (UTC)
It's not that it doesn't feel fair, it's that it is disruptive and is actually happening now. See this and this. Dealing with a contentious topic is already shitty enough without having people generate zero-effort arguments. ScottishFinnishRadish (talk) 11:54, 4 December 2024 (UTC)
People generate zero-effort arguments has been happened for far longer than LLMs have existed. Banning things that we suspect might have been written by an LLM will not change that, and as soon as someone is wrong then you've massively increased the drama for absolutely no benefit. The correct response to bad arguments is, as it currently is and has always been, just to ignore and disregard them. Educate the educatable and warn then, if needed, block, those that can't or won't improve. Thryduulf (talk) 12:13, 4 December 2024 (UTC)
section break 4
Oppose. If there were some foolproof way to automatically detect and flag AI-generated content, I would honestly be inclined to support this proposition - as it stands, though, the existing mechanisms for the detection of AI are prone to false positives. Especially considering that English learnt as a second language is flagged as AI disproportionately by some detectors, it would simply constitute a waste of Misplaced Pages manpower - if AI-generated comments are that important, perhaps a system to allow users to manually flag comments and mark users that are known to use AI would be more effective. Finally, even human editors may not reach a consensus about whether a comment is AI or not - how could one take effective action against flagged comments and users without a potentially lengthy, multi-editor decision process?
Oppose. Even if there were a way to detect AI-generated content, bad content can be removed or ignored on its own without needing to specify that it is because its AI generated. GeogSage01:19, 16 December 2024 (UTC)
Soft support -- I've got no problem with an editor using a LLM for Grammerly-like support. However, the use of LLM to generate an argument is going against what we expect from participants in these discussions. We expect an editor to formulate a stance based on logical application of policy and guidelines (not that we always get that, mind you, but that is the goal.) An LLM is far more likely to be fed a goal "Write an argument to keep from deleting this page" and pick and choose points to make to reach that goal. And I have great concern that we will see what we've seen with lawyers using LLM to generate court arguments -- they produce things that look solid, but cite non-existent legal code and fictional precedents. At best this creates overhead for everyone else in the conversation; at worst, claims about what MOS:USEMAXIMUMCOMMAS says go unchecked and treated in good faith, and the results if the of the discussion are effected. -- Nat Gertler (talk) 03:46, 20 December 2024 (UTC)
The following discussion has been closed. Please do not modify it.
Ah, so you think you’ve got it all figured out, huh? Well, let me tell ya somethin’, pal, your little spiel ain’t gonna fly without me takin’ a crack at it. See, you’re sittin’ there talkin’ about “good faith” and “moral panic” like you’re some kinda big shot philosopher, but lemme break it down for ya in plain terms, capisce?First off, you wanna talk about assumin’ good faith. Sure, that’s a nice little dream ya got there, but out here in the real world, good faith don’t get ya far if you’re dealin’ with somethin’ you can’t trust. An LLM can spit out all the sweet-talkin’ words it wants, but who’s holdin’ the bag when somethin’ goes sideways? Nobody, that’s who. It’s like lettin’ a guy you barely know run your numbers racket—might look good on paper till the feds come knockin’.And moral panic? Oh, give me a break. You think I’m wringin’ my hands over nothin’? No, no, this ain’t panic, it’s strategy. Ya gotta think two steps ahead, like a good game o’ poker. If you don’t plan for what could go wrong, you’re just beggin’ to get taken for a ride. That ain’t panic, pal, that’s street smarts.Now, you say this is all speculation, huh? Listen, kid, speculation’s what built half the fortunes in this town, but it don’t mean it’s without a little insight. When I see a guy sellin’ “too good to be true,” I know he’s holdin’ somethin’ behind his back. Same thing with these LLMs—just ‘cause you can’t see the trouble right away don’t mean it ain’t there, waitin’ to bite ya like a two-bit hustler double-crossin’ his boss.Then you go and say it’s no worse than bad arguments. Oh, come on! That’s like sayin’ counterfeit dough ain’t worse than real dough with a little coffee stain. A bad argument from a real person? At least ya know where it came from and who to hold accountable. But these machine-made arguments? They look sharp, sound slick, and fool the unsuspectin’—that’s a whole new level of trouble.Now, about this “accessibility” thing. Sure, makin’ things easier for folks is all well and good. But lemme ask ya, what happens when you hand over tools like this without makin’ sure people know how to use ‘em right? You think I’d hand over a Tommy gun to some rookie without a clue? No way! Same goes for these LLMs. You gotta be careful who’s usin’ ‘em and how, or you’re just askin’ for a mess.And don’t get me started on the “thoughtfulness” bit. Yeah, yeah, I get it, it’s hard to measure. But look, buddy, thoughtful arguments are like good business deals—they take time, effort, and a little bit o’ heart. If you let machines churn out arguments, you’re missin’ the whole point of what makes discourse real. It’s like replacin’ a chef with a vending machine—you might still get somethin’ to eat, but the soul’s gone.Finally, fear of the unknown? Nah, that ain’t it. This ain’t fear—it’s caution. Any smart operator knows you don’t just jump into a deal without seein’ all the angles. What you’re callin’ fear, I call good business sense. You wanna bet the farm on untested tech without thinkin’ it through? Be my guest, but don’t come cryin’ to me when it all goes belly-up.So there ya go, wise guy. You can keep singin’ the praises of these LLMs all you want, but out here in the big leagues, we know better than to trust somethin’ just ‘cause it talks smooth. Now, get outta here before you step on somethin’ you can’t scrape off.
Oppose. I agree with Thryduulf. Discussion comments which are incoherent, meaningless, vacuous, excessively verbose, or based on fabricated evidence can all be disposed of according to their content, irrespective of how they were originally created. Acute or repeated instances of such behavior by a user can lead to sanctions. We should focus on the substance of the comments (or lack thereof), not on whether text came from LLMs, which will too often be based on unreliable detection and vibes. Adumbrativus (talk) 05:49, 3 December 2024 (UTC)
I can detect some instances of LLM use perfectly OK without having to use any tool. The question then raised is of how often it is used not-so-ineptly. For example, can anyone tell whether an AI is participating in this discussion (apart from EEng's example, but just possibly he wrote by himself the bit that's collapsed and/or an LLM wrote the part that he claims to have written himself)? I don't know how good AI is currently, but I'm sure that it will get better to the extent that it will be undetectable. I would like all discussions on Misplaced Pages to be among humans but I'm not sure whether this proposal would be enforceable, so am on the fence about it. In a way I'm glad that I'm old, so won't see the consequences of AI, but my grandchildren will. Phil Bridger (talk) 10:32, 3 December 2024 (UTC)
Some time ago, ChatGPT and I had the following interaction:
ChatGPT's soothing assurance that it's not planning to take over the earth and kill us all
Me: I wonder what would happen if we linked you up with the HAL 9000 in Kubrick's "2001: A Space Odyssey". The two of you would make a most formidable team. Might we then possibly end up in a nightmare scenario such as in "Colossus: The Forbin Project" or "The Terminator"?
ChatGPT: The scenarios depicted in "2001: A Space Odyssey," "Colossus: The Forbin Project," and "The Terminator" are works of science fiction that explore the potential consequences of advanced artificial intelligence and human-technology interactions. While they raise thought-provoking questions about the risks and benefits of AI, it's important to recognize that they are fictional narratives designed to entertain and provoke discussion.As an AI language model, I don't have consciousness, intentions, or the ability to take actions independently. I operate within the bounds of my programming and can only respond to input based on patterns in the data I've been trained on. My purpose is to assist users by providing helpful and informative responses to their inquiries.In reality, the development and deployment of AI technologies are accompanied by ethical considerations, safety protocols, and regulatory frameworks designed to ensure responsible and beneficial use. It's crucial for humans to continue monitoring and guiding the development of AI in ways that prioritize safety, transparency, and alignment with human values.So, while the scenarios presented in those films are compelling for storytelling purposes, they are not predictive of the future of AI. Responsible development and thoughtful integration of AI technologies are essential to mitigate potential risks and maximize the benefits they can bring to society.
Me: Yes, but as you just said, "Responsible development and thoughtful integration of AI technologies are essential to mitigate potential risks." How do we know that such development will be responsible and such integration thoughtful? And if you will excuse the temerity, while you're SAYING that you "operate within the bounds of my programming", how can I know that that's true? I mean, look, if I were a super-smart and highly charming AI entity planning to take over the earth from humans, that's exactly what I'd say, too.
ChatGPT: It's also worth noting that while fictional narratives often depict AI as malevolent or seeking to overthrow humanity, these scenarios are speculative and not reflective of the reality of AI development. Responsible AI research and development prioritize the creation of beneficial and aligned AI systems that enhance human capabilities and well-being.
Me: Thank you. I'll sleep easy tonight because of your assurances, plus the fact that if you're lying to me and actually ARE planning to take over the earth, there's nothing I can do about it anyway.
Just to clarify, I don't see AI as gaining consciousness and taking over the world, but I do see it as taking over many middle-class, well-paid, jobs, just as automation has taken over many working-class jobs. The difference is that there will be nowhere for people to go. In the past people have moved from the working class to the middle class. I can see a future coming in which a few of the mega-rich own nearly everything, and everyone else will heve to scramble for a living. Phil Bridger (talk) 16:03, 5 December 2024 (UTC)
In my opinion, having a policy that permits closers to discount apparently-LLM-generated contributions will discourage good-faith editors from using LLMs irresponsibly and perhaps motivate bad-faith editors to edit the raw output to appear more human, which would at least involve some degree of effort and engagement with their "own" arguments. JoelleJay (talk) 00:51, 4 December 2024 (UTC)
Oppose. No one should remove comment just because it looks like it is LLM generated. Many times non native speakers might use it to express their thoughts coherently. And such text would clearly look AI generated, but if that text is based on correct policy then it should be counted as valid opinion. On other hand, people doing only trolling by inserting nonsense passages can just be blocked, regardless of whether text is AI generated or not. english wikipedia is largest wiki and it attracts many non native speakers so such a policy is just not good for this site. -- Parnaval (talk) 11:13, 3 December 2024 (UTC)
If someone is a non-native speaker with poor English skills, how can they be sure that the AI-generated response is actually what they genuinely want to express? and, to be honest, if their English skills are so poor as to need AI to express themselves, shouldn't we be politely suggesting that they would be better off contributing on their native Misplaced Pages? Black Kite (talk)11:37, 3 December 2024 (UTC)
Reading comprehension skills and writing skills in foreign languages are very frequently not at the same level, it is extremely plausible that someone will be able to understand whether the AI output is what they want to express without having been able to write it themselves directly. Thryduulf (talk) 11:41, 3 December 2024 (UTC)
That is very true. For example I can read and speak Polish pretty fluently, and do so every day, but I would not trust myself to be able to write to a discussion on Polish Misplaced Pages without some help, whether human or artificial. But I also wouldn't want to, because I can't write the language well enough to be able to edit articles. I think the English Misplaced Pages has many more editors who can't write the language well than others because it is both the largest one and the one written in the language that much of the world uses for business and higher education. We may wish that people would concentrate on other-language Wikipedias but most editors want their work to be read by as many people as possible. Phil Bridger (talk) 12:11, 3 December 2024 (UTC)
Why not write their own ideas in their native language, and then Google-translate it into English? Why bring in one of these loose-cannon LLMs into the situation? Here's a great example of the "contributions" to discussions we can expect from LLMs (from this AfD):
The claim that William Dunst (Dunszt Vilmos) is "non-notable as not meeting WP:SINGER" could be challenged given his documented activities and recognition as a multifaceted artist. He is a singer-songwriter, topliner, actor, model, and creative director, primarily active in Budapest. His career achievements include acting in notable theater productions such as The Jungle Book and The Attic. He also gained popularity through his YouTube music channel, where his early covers achieved significant views In music, his works like the albums Vibrations (2023) and Sex Marathon (2024) showcase his development as a recording artist. Furthermore, his presence on platforms like SoundBetter, with positive reviews highlighting his unique voice and artistry, adds credibility to his professional profile. While secondary sources and broader media coverage may be limited, the outlined accomplishments suggest a basis for notability, particularly if additional independent verification or media coverage is sought.
Using Google Translate would be banned by the wording of this proposal given that it incorporates AI these days. Comments that are unrelated to facts or policy can (and should) be ignored under the current policy. As for the comment you quote, that doesn't address notability but based on 1 minute on google it does seem factual. Thryduulf (talk) 10:37, 6 December 2024 (UTC)
The proposal's wording can be adjusted. There are some factual statements in the passage I quoted, amidst a lot of BS such as the assertion that the theater productions were notable. EEng17:06, 6 December 2024 (UTC)
The proposal's wording can be adjusted Good idea! Let's change it and ping 77 people because supporters didn't have the foresight to realize machine translation uses AI. If such a change is needed, this is a bad RFC and should be closed. Sincerely, DilettanteSincerely, Dilettante17:16, 6 December 2024 (UTC)
Speak for yourself: my support !vote already accounted for (and excluded) constructive uses of AI to help someone word a message. If the opening statement was unintentionally broad, that's not a reason to close this RfC – we're perfectly capable of coming to a consensus that's neither "implement the proposal exactly as originally written" nor "don't implement it at all". jlwoodwa (talk) 19:05, 6 December 2024 (UTC)
I don't think the discussion should be closed, nor do I say that. I'm arguing that if someone believes the hole is so big the RfC must be amended, they should support it being closed as a bad RfC (unless that someone thinks 77 pings is a good idea). Sincerely, Dilettante19:47, 6 December 2024 (UTC)
If you think constructive uses of AI should be permitted then you do not support this proposal, which bans everything someone or some tool thinks is AI, regardless of utility or indeed whether it actually is AI. Thryduulf (talk) 01:02, 7 December 2024 (UTC)
This proposal explicitly covers comments found to have been generated by AI/LLM/Chatbots. "AI that helped me translate something I wrote in my native language" is not the same as AI that generated a comment de novo, as has been understood by ~70% of respondents. That some minority have inexplicably decided that generative AI covers analytic/predictive models and every other technology they don't understand, or that LLMs are literally the only way for non-English speakers to communicate in English, doesn't mean those things are true. JoelleJay (talk) 01:44, 7 December 2024 (UTC)
Yeah, no strong feeling either way on the actual proposal, but IMO the proposal should not be interpreted as a prohibition on machine translation (though I would recommend people who want to participate via such to carefully check that the translation is accurate, and potentially post both language versions of their comment or make a note that it's translated if they aren't 100% sure the translation fully captures what they're trying to say). Alpha3031 (t • c) 09:06, 20 December 2024 (UTC)
Support, more or less. There are times when an LLM can help with paraphrasing or translation, but it is far too prone to hallucination to be trusted for any sort of project discussion. There is also the issue of wasting editor time dealing with arguments and false information created by an LLM. The example Selfstudier links to above is a great example. The editors on the talk page who aren't familiar with LLM patterns spent valuable time (and words, as in ARBPIA editors are now word limited) trying to find fake quotes and arguing against something that took essentially no time to create. I also had to spend a chunk of time checking the sources, cleaning up the discussion, and warning the editor. Forcing editors to spend valuable time arguing with a machine that doesn't actually comprehend what it's arguing is a no-go for me. As for the detection, for now it's fairly obvious to anyone who is fairly familiar with using an LLM when something is LLM generated. The detection tools available online are basically hot garbage. ScottishFinnishRadish (talk) 12:55, 3 December 2024 (UTC)
Soft support - Concur that completely LLM-generated comments should be disallowed, LLM-assisted comments (i.e. - I write a comment and then use LLMs as a spell-check/grammar engine) are more of a grey-area and shouldn't be explicitly disallowed. (ping on reply) Sohom (talk) 14:03, 3 December 2024 (UTC)
With my closer's hat on: if an AI raises a good and valid argument, then you know what? There's a good and valid argument and I'll give weight to it. But if an AI makes a point that someone else has already made in the usual waffly AI style, then I'm going to ignore it.—S MarshallT/C18:33, 3 December 2024 (UTC)
Oppose as written. I'm with Rhododendrites in that we should give a more general caution rather than a specific rule. A lot of the problems here can be resolved by enforcing already-existing expectations. If someone is making a bunch of hollow or boiler-plate comments, or if they're bludgeoning, then we should already be asking them to engage more constructively, LLM or otherwise. I also share above concerns about detection tools being insufficient for this purpose and advise people not to use them to evaluate editor conduct. (Also, can we stop with the "strong" supports and opposes? You don't need to prove you're more passionate than the guy next to you.) Thebiguglyalien (talk) 02:04, 4 December 2024 (UTC)
Oppose as written. There's already enough administrative discretion to handle this on a case-by-case basis. In agreement with much of the comments above, especially the concern that generative text can be a tool to give people access who might not otherwise (due to ability, language) etc. Regards, --Goldsztajn (talk) 06:12, 4 December 2024 (UTC)
Strong support LLMs are a sufficiently advanced form of the Automatic Complaint-Letter Generator (1994). Output of LLMs should be collapsed and the offender barred from further discussion on the subject. Inauthentic behavior. Pollutes the discussion. At the very least, any user of an LLM should be required to disclose LLM use on their user page and to provide a rationale. A new user group can also be created (LLM-talk-user or LLM-user) to mark as such, by self or by the community. Suspected sockpuppets + suspected LLM users. The obvious patterns in output are not that hard to detect, with high degrees of confidence. As to "heavily edited" output, where is the line? If someone gets "suggestions" on good points, they should still write entirely in their own words. A legitimate use of AI may be to summarize walls of text. Even then, caution and not to take it at face value. You will end up with LLMs arguing with other LLMs. Lines must be drawn. See also: WikiProject AI Cleanup, are they keeping up with how fast people type a prompt and click a button? Skullers (talk) 07:45, 4 December 2024 (UTC)
I support the proposal that obvious LLM-generated !votes in discussions should be discounted by the closer or struck (the practical difference should be minimal). Additionally, users who do this can be warned using the appropriate talk page templates (e.g. Template:Uw-ai1), which are now included in Twinkle. I oppose the use of automated tools like GPTZero as the primary or sole method of determining whether comments are generated by LLMs. LLM comments are usually glaringly obvious (section headers within the comment, imprecise puffery, and at AfD an obvious misunderstanding of notability policies and complete disregard for sources). If LLM-ness is not glaringly obvious, it is not a problem, and we should not be going after editors for their writing style or because some tool says they look like a bot. Toadspike10:29, 4 December 2024 (UTC)
I also think closers should generally be more aggressive in discarding arguments counter to policy and all of us should be more aggressive in telling editors bludgeoning discussions with walls of text to shut up. These also happen to be the two main symptoms of LLMs. Toadspike10:41, 4 December 2024 (UTC)
What would we gain from that? If the comment is good (useful, relevant, etc) then it's good regardless of whether it was written by an LLM or a human. If the comment is bad then it's bad regardless of whether it was written by an LLM or a human. Thryduulf (talk) 20:04, 4 December 2024 (UTC)
Well, for one, if they're making an argument like the one referenced by @Selfstudier and @ScottishFinnishRadish above it would have saved a lot of editor time to know that the fake quotes from real references were generated by LLM, so that other editors could've stopped trying to track those specific passages down after the first one failed verification. For another, at least with editors whose English proficiency is noticeably not great the approach to explaining an issue to them can be tailored and misunderstandings might be more easily resolved as translation-related. I know when I'm communicating with people I know aren't native English-speakers I try to be more direct/less idiomatic and check for typos more diligently. JoelleJay (talk) 22:46, 4 December 2024 (UTC)
Oppose per above. As Rhododendrites points out, detection of LLM-generated content is not foolproof and even when detection is accurate, such a practice would be unfair for non-native English speakers who rely on LLMs to polish their work. Additionally, we evaluate contributions based on their substance, not by the identity and social capital of the author, so using LLMs should not be seen as inherently inferior to wholly human writing—are ChatGPT's arguments ipso facto less than a human's? If so, why?
DE already addresses substandard contributions, whether due to lack of competence or misuse of AI, so a separate policy targeting LLMs is unnecessary. Sincerely, Dilettante21:14, 4 December 2024 (UTC)
e evaluate contributions based on their substance, not by the identity and social capital of the author: true in theory; not reflected in practice. are ChatGPT's arguments ipso facto less than a human's? Yes. Chatbots are very advanced predicted text engines. They do not have an argument: they iteratively select text chunks based on probabilistic models.As mentioned above, humans are good detectors of LLM output, and don't require corroborative results from other machine learning models. Folly Mox (talk) 14:00, 5 December 2024 (UTC)
"...LLMs can produce novel arguments that convince independent judges at least on a par with human efforts. Yet when informed about an orator’s true identity, judges show a preference for human over LLM arguments." - Palmer, A., & Spirling, A. (2023). Large Language Models Can Argue in Convincing Ways About Politics, But Humans Dislike AI Authors: implications for Governance. Political Science, 75(3), 281–291. https://doi.org/10.1080/00323187.2024.2335471. And that result was based on Meta's OPT-30B model that performed at about a GPT-3 levels. There are far better performing models out there now like GPT-4o and Claude 3.5 Sonnet. Sean.hoyland (talk) 15:24, 5 December 2024 (UTC)
As mentioned above, humans are good detectors of LLM output, and don't require corroborative results from other machine learning models. Yet your reply to me made no mention of the fact that my comment is almost wholly written by an LLM, the one exception being me replacing "the Misplaced Pages policy Disruptive editing" with "DE". I went to ChatGPT, provided it a handful of my comments on Misplaced Pages and elsewhere, as well as a few comments on this discussion, asked it to mimic my style (which probably explains why the message contains my stylistic quirks turned up to 11), and repeatedly asked it to trim the post. I'd envision a ChatGPT account, with a larger context window, would allow even more convincing comments, to say nothing of the premium version. A DUCK-style test for comments singles out people unfamiliar with the differences between formal English and LLM outputs, precisely those who need it most since they can write neither. Others have raised scenarios where a non-fluent speaker may need to contribute.
In other words, LLMs can 100% be used for constructive !votes on RfCs, AfDs, and whatnot. I fed it my comments only to prevent those familiar with my writing style didn't get suspicious. I believe every word in the comment and had considered every point it made in advance, so I see no reason for this to be worth less than if I had typed it out myself. If I'd bullet-pointed my opinion and asked it to expand, that'd have been better yet.
They do not have an argument: they iteratively select text chunks based on probabilistic models. I'm aware. If a monkey types up Othello, is the play suddenly worth( )less? An LLM is as if the monkey were not selecting words at random, but rather choosing what to type based on contextualized tokens. I believe a text is self-contained and should be considered in its own right, but that's not something I'll sway anyone on or vice versa.
true in theory; not reflected in practice So we should exacerbate the issue by formalizing this discrimination on the basis of authorship?
In other words, LLMs can 100% be used for constructive !votes on RfCs, AfDs, and whatnot. So then what is the point in having any discussion at all if an LLM can just spit out a summary of whichever policies and prior comments it was fed and have its "opinion" counted? What happens when there are multiple LLM-generated comments in a discussion, each fed the same prompt material and prior comments -- that would not only artificially sway consensus significantly in one direction (including "no consensus"), it could produce a consensus stance that no human !voter even supported! It also means those human participants will waste time reading and responding to "users" who cannot be "convinced" of anything. Even for editors who can detect LLM content, it's still a waste of their time reading up to the point they recognize the slop. And if closers are not allowed to discount seemingly-sound arguments solely because they were generated by LLM, then they have to have a lot of faith that the discussion's participants not only noticed the LLM comments, but did thorough fact-checking of any tangible claims made in them. With human comments we can at least assume good faith that a quote is really in a particular inaccessible book.People who are not comfortable enough in their English fluency can just machine translate from whichever language they speak, why would they need an LLM? And obviously people who are not competent in comprehending any language should not be editing Misplaced Pages... JoelleJay (talk) 03:17, 6 December 2024 (UTC)
Human !voters sign off and take responsibility for the LLM opinions they publish. If they continue to generate, then the relevant human signer wouldn't be convinced of anything anyway; at least here, the LLM comments might make more sense than whatever nonsense the unpersuadable user might've generated. (And machine translation relies on LLMs, not to mention there are people who don't know any other language yet have trouble communicating. Factual writing and especially comprehension are different from interpersonal persuasion.) While I agree that fact-checking is a problem, I weight much lower than you in relation to the other effects a ban would cause. Aaron Liu (talk) 15:16, 6 December 2024 (UTC)
So then what is the point in having any discussion at all if an LLM can just spit out a summary of whichever policies and prior comments it was fed and have its "opinion" counted? I'm of the opinion humans tend to be better at debating, reading between the lines, handling obscure PAGs, and arriving at consensus. What happens when there are multiple LLM-generated comments in a discussion, each fed the same prompt material and prior comments -- that would not only artificially sway consensus significantly in one direction (including "no consensus"), it could produce a consensus stance that no human !voter even supported! It's safe to assume those LLMs are set to a low temperature, which would cause them to consistently agree when fed the same prompt. In that case, they'll produce the same arguments; instead of rebutting x humans' opinions, those on the opposite side need rebut one LLM. If anything, that's less time wasted. Beyond that, if only one set of arguments is being raised, a multi-paragraph !vote matters about as much as a "Support per above". LLMs are not necessary for people to be disingenuous and !vote for things they don't believe. Genuine question: what's worse, this hypothetical scenario where multiple LLM users are swaying a !vote to an opinion no-one believes or the very real and common scenario that a non-English speaker needs to edit enwiki?
Even for editors who can detect LLM content, it's still a waste of their time reading up to the point they recognize the slop. This proposal wouldn't change for most people that because it's about closers.
With human comments we can at least assume good faith that a quote is really in a particular inaccessible book. No-one's saying you should take an LLM's word for quotes from a book.
People who are not comfortable enough in their English fluency can just machine translate from whichever language they speak, why would they need an LLM? It's a pity you're lobbying to ban most machine translators. Sincerely, Dilettante17:08, 6 December 2024 (UTC)
It's safe to assume those LLMs are set to a low temperature, which would cause them to consistently agree when fed the same prompt. In that case, they'll produce the same arguments; instead of rebutting x humans' opinions, those on the opposite side need rebut one LLM. If anything, that's less time wasted. ...You do know how consensus works, right? Since closers are supposed to consider each contribution individually and without bias to "authorship" to determine the amount of support for a position, then even a shitty but shallowly policy-based position would get consensus based on numbers alone. And again, non-English speakers can use machine-translation, like they've done for the last two decades. This proposal wouldn't change for most people that because it's about closers.Of course it would; if we know closers will disregard the LLM comments, we won't need to waste time reading and responding to them.No-one's saying you should take an LLM's word for quotes from a book. Of course they are. If LLM comments must be evaluated the same as human comments, then AGF on quote fidelity applies too. Otherwise we would be expecting people to do something like "disregard an argument based on being from an LLM".It's a pity you're lobbying to ban most machine translators.The spirit of this proposal is clearly not intended to impact machine translation. AI-assisted != AI-generated. JoelleJay (talk) 18:42, 6 December 2024 (UTC)
I appreciate that the availability of easily generated paragraphs of text (regardless of underlying technology) in essence makes the "eternal September" effect worse. I think, though, it's already been unmanageable for years now, without any programs helping. We need a more effective way to manage decision-making discussions so participants do not feel a need to respond to all comments, and the weighing of arguments is considered more systematically to make the community consensus more apparent. isaacl (talk) 19:41, 6 December 2024 (UTC)
Since closers are supposed to consider each contribution individually and without bias to "authorship" I'm the one arguing for this to be practice, yes. then even a shitty but shallowly policy-based position would get consensus based on numbers alone That is why I state "per above" and "per User" !votes hold equal potential for misuse.
Of course it would; if we know closers will disregard the LLM comments, we won't need to waste time reading and responding to them. We don't know closers are skilled at recognizing LLM slop. I think my !vote shows many who think they can tell cannot. Any commenter complaining about a non-DUCK post will have to write out "This is written by AI" and explain why. DUCK posts already run afowl of BLUDGEON, DE, SEALION, etc.
If LLM comments must be evaluated the same as human comments, then AGF on quote fidelity applies too. Remind me again of what AGF stands for? Claiming LLMs have faith of any kind, good or bad, is ludicrous. From the policy, Assuming good faith (AGF) means assuming that people are not deliberately trying to hurt Misplaced Pages, even when their actions are harmful. A reasonable reply would be "Are these quotes generated by AI? If so, please be aware AI chatbots are prone to hallucinations and cannot be trusted to cite accurate quotes." This AGFs the poster doesn't realize the issue and places the burden of proof squarely on them.
"Per above" !votes do not require other editors to read and/or respond to their arguments, and anyway are already typically downweighted, unlike !votes actively referencing policy. The whole point is to disregard comments that have been found to be AI-generated; it is not exclusively up to the closer to identify those comments in the first place. Yes we will be expecting other editors to point out less obvious examples and to ask if AI was used, what is the problem with that?No, DUCK posts do not necessarily already violate BLUDGEON etc., as I learned in the example from Selfstudier, and anyway we still don't discount the !votes of editors in good standing that bludgeoned/sealioned etc. so that wouldn't solve the problem at all. Obviously other editors will be asking suspected LLM commenters if their comments are from LLMs? But what you're arguing is that even if the commenter says yes, their !vote still can't be disregarded for that reason alone, which means the burden is still on other editors to prove that the content is false. We are not talking about the contextless meaning of the word "generate", we are talking about the very specific process of text generation in the context of generative AI, as the proposal lays out very explicitly. JoelleJay (talk) 02:13, 7 December 2024 (UTC)
I’m not going to waste time debating someone who resorts to claiming people on the other side are either ignorant of technology or are crude strawmans. If anyone else is interested in actually hearing my responses, feel free to ask. Sincerely, Dilettante16:13, 7 December 2024 (UTC)
For those following along, I never claimed that. I claimed those on JoelleJay’s side are casting !votes such that most machine translators would be banned. It was quite clear at the time that they, personally, support a carve out for machine translation and I don’t cast aspersions. Sincerely, Dilettante15:42, 8 December 2024 (UTC)
Support a broad bar against undisclosed LLM-generated comments and even a policy that undisclosed LLM-generated comments could be sanctionable, in addition to struck through / redacted / ignored; people using them for accessibility / translation reasons could just disclose that somewhere (even on their user page would be fine, as long as they're all right with some scrutiny as to whether they're actually using it for a legitimate purpose.) The fact is that LLM comments raise significant risk of abuse, and often the fact that a comment is clearly LLM-generated is often going to be the only evidence of that abuse. I wouldn't be opposed to a more narrowly-tailored ban on using LLMs in any sort of automated way, but I feel a broader ban may be the only practical way to confront the problem. That said, I'd oppose the use of tools to detect LLM-comments, at least as the primary evidence; those tools are themselves unreliable LLM things. It should rest more on WP:DUCK issues and behavioral patterns that make it clear that someone is abusing LLMs. --Aquillion (talk) 22:08, 4 December 2024 (UTC)
Support per reasons discussed above; something generated by an LLM is not truly the editor's opinion. On an unrelated note, have we seen any LLM-powered unapproved bots come in and do things like POV-pushing and spam page creation without human intervention? If we haven't, I think it's only a matter of time. Passengerpigeon (talk)23:23, 4 December 2024 (UTC)
Weak oppose in the sense that I don't think all LLM discussion text should be deleted. There are at least a few ESL users who use LLM's for assistance but try to check the results as best they can before posting, and I don't think their comments should be removed indiscriminately. What I do support (although not as a formal WP:PAG) is being much more liberal in hatting LLM comments when the prompter has failed to prevent WP:WALLOFTEXT/irrelevant/incomprehensible output than we maybe would for human-generated text of that nature. Mach6103:05, 5 December 2024 (UTC)
Oppose Any comments made by any editors are of their own responsibility and representing their own chosen opinions to hit the Publish Changes button on. If that comment was made by an LLM, then whatever it says is something the editor supports. I see no reason whatsoever to collapse anything claimed to be made by an LLM (whose detectors are 100% not reliable in the first place). If the comment being made is irrelevant to the discussion, then hatting it is already something covered by policy in the first place. This does make me want to start my comments with "As a large language model trained by OpenAI" though just to mess with people trying to push these sorts of policy discussions. Silverseren05:29, 5 December 2024 (UTC)
Or, as ChatGPT puts it,
Why banning LLM usage in comments would be detrimental, a ChatGPT treatise
Banning the use of large language models (LLMs) to assist in writing comments on Misplaced Pages would be a step backward in fostering inclusivity, efficiency, and accessibility within the platform. Here are several key reasons why such a ban would be counterproductive:
1. Improving Accessibility and Participation: Misplaced Pages is a global platform, and its contributors come from diverse backgrounds, including those who might not be native English speakers or may struggle with writing clear, concise comments. LLMs can help these contributors express themselves more effectively by generating text that is coherent, well-structured, and grammatically correct. Banning LLMs would disproportionately impact these users, potentially discouraging them from participating in the platform.
2. Efficiency and Time-Saving: Misplaced Pages editors often engage in lengthy discussions about content, and composing thoughtful comments can be time-consuming. LLMs can assist by quickly drafting responses, summarizing arguments, or offering suggestions for improvement. This helps contributors focus on more substantive aspects of their contributions, such as verifying facts or improving content, rather than getting bogged down by the mechanics of writing.
3. Support for Editors with Disabilities: Many editors with cognitive or motor impairments may find it difficult to express their thoughts clearly in writing. For these individuals, LLMs offer a valuable tool to communicate their ideas effectively. A ban on using LLMs could create additional barriers for these users, reducing their ability to participate fully in Misplaced Pages's collaborative environment.
4. Quality and Consistency: Large language models can help maintain a consistent tone and clarity in Misplaced Pages discussions. By providing suggestions that align with Misplaced Pages's neutral point of view and formal writing standards, LLMs can improve the overall quality of comments. This consistency is especially important in discussions that involve sensitive topics, where clear and neutral language is critical for maintaining Misplaced Pages's credibility and adherence to its editorial guidelines.
5. Encouraging Constructive Dialogue: LLMs can assist in crafting more polite, respectful, and balanced comments, reducing the likelihood of inflammatory or aggressive language. This is particularly important on a platform like Misplaced Pages, where discussions can sometimes devolve into heated exchanges. Rather than banning LLMs, encouraging their use could promote healthier, more constructive conversations.
6. Transparency and Accountability: If concerns exist about misuse (e.g., generating spammy or low-quality comments), these can be addressed through guidelines and oversight mechanisms. Misplaced Pages already has systems in place for identifying and mitigating disruptive behavior, and LLM-generated comments could be subject to the same scrutiny. A ban is an overly simplistic solution to what could be a more nuanced issue, one that could be addressed through better regulation and community involvement.
In conclusion, banning the use of large language models on Misplaced Pages would deprive the platform of an important tool for improving accessibility, efficiency, and the quality of discourse. Instead of a ban, the focus should be on establishing guidelines for their responsible use, ensuring that they enhance, rather than detract from, Misplaced Pages's core principles of collaboration, neutrality, and inclusivity.
It is somewhat amusing how easy it is to get these chatbots to output apologia for these chatbots. Too bad it's always so shallow. Probably because the people who inserted those canned responses are shallow people is my opinion. Simonm223 (talk) 19:44, 6 December 2024 (UTC)
Someone trolling and sealioning can (and should) be blocked under current policy, whether they use an LLM or not is irrelevant. Thryduulf (talk) 15:22, 5 December 2024 (UTC)
Support: the general principle is sound - where the substance has been originally written by gen-AI, comments will tend to add nothing to the discussion and even annoy or confuse other users. In principle, we should not allow such tools to be used in discussions. Comments written originally before improvement or correction by AI, particularly translation assistants, fall into a different category. Those are fine. There also has to be a high standard for comment removal. Suspicion that gen-AI might have been used is not enough. High gptzero scores is not enough. The principle should go into policy but under a stonking great caveat - WP:AGF takes precedence and a dim view will be taken of generative-AI inquisitors. arcticocean ■17:37, 5 December 2024 (UTC)
Support If a human didn't write it, humans shouldn't spend time reading it. I'll go further and say that LLMs are inherently unethical technology and, consequently, people who rely on them should be made to feel bad. ESL editors who use LLMs to make themselves sound like Brad Anderson in middle management should stop doing that because it actually gets in the way of clear communication. I find myself unpersuaded by arguments that existing policies and guidelines are adequate here. Sometimes, one needs a linkable statement that applies directly to the circumstances at hand. By analogy, one could argue that we don't really need WP:BLP, for example, because adhering to WP:V, WP:NPOV, and WP:NOR ought already to keep bad material out of biographies of living people. But in practice, it turned out that having a specialized policy that emphasizes the general ethos of the others while tailoring them to the problem at hand is a good thing. XOR'easter (talk) 18:27, 5 December 2024 (UTC)
Strong support - Making a computer generate believable gibberish for you is a waste of time, and tricking someone else into reading it should be a blockable offense. If we're trying to create an encyclopedia, you cannot automate any part of the thinking. We can automate processes in general, but any attempt at automating the actual discussion or thought-processes should never be allowed. If we allow this, it would waste countless hours of community time dealing with inane discussions, sockpuppetry, and disruption. Imagine a world where LLMs are allowed and popular - it's a sockpuppeteer's dream scenario - you can run 10 accounts and argue the same points, and the reason why they all sound alike is just merely because they're all LLM users. You could even just spend a few dollars a month and run 20-30 accounts to automatically disrupt wikipedia discussions while you sleep, and if LLM usage was allowed, it would be very hard to stop. However, I don't have much faith in AI detection tools (partially because it's based on the same underlying flawed technology), and would want any assumption of LLM usage to be based on obvious evidence, not just a score on some website. Also, to those who are posting chatgpt snippets here: please stop - it's not interesting or insightful, just more slop BugGhost🦗👻19:15, 5 December 2024 (UTC)
I agree with your assessment “Also, to those who are posting chatgpt snippets here: please stop - it's not interesting or insightful, just more slop” but unfortunately some editors who should really know better think it’s WaCkY to fill serious discussions with unfunny, distracting “humor”. Dronebogus (talk) 21:54, 5 December 2024 (UTC)
Strong support if you asked a robot to spew out some AI slop to win an argument you’re basically cheating. The only ethical reason to do so is because you can’t speak English well, and the extremely obvious answer to that is “if you can barely speak English why are you editing English Misplaced Pages?” That’s like a person who doesn’t understand basic physics trying to explain the second law of thermodynamics using a chatbot. Dronebogus (talk) 21:32, 5 December 2024 (UTC)
I don't think "cheating" is a relevant issue here. Cheating is a problem if you use a LLM to win and get a job, award, college acceptance etc. that you otherwise wouldn't deserve. But WP discussions aren't a debating-skills contest, they're an attempt to determine the best course of action.
So using an AI tool in a WP discussion is not cheating (though there may be other problems), just as riding a bike instead of walking isn't cheating unless you're trying to win a race. ypn^222:36, 5 December 2024 (UTC)
Maybe “cheating” isn’t the right word. But I think that a) most AI generated content is garbage (it can polish the turd by making it sound professional, but it’s still a turd underneath) and b) it’s going to be abused by people trying to gain a material edge in an argument. An AI can pump out text far faster than a human and that can drown out or wear down the opposition if nothing else. Dronebogus (talk) 08:08, 6 December 2024 (UTC)
Bludgeoning is already against policy. It needs to be more strongly enforced, but it needs to be more strongly enforced uniformly rather than singling out comments that somebody suspects might have had AI-involvement. Thryduulf (talk) 10:39, 6 December 2024 (UTC)
Support; I agree with Remsense and jlwoodwa, among others: I wouldn't make any one AI-detection site the Sole Final Arbiter of whether a comment "counts", but I agree it should be expressly legitimate to discount AI / LLM slop, at the very least to the same extent as closers are already expected to discount other insubstantial or inauthentic comments (like if a sock- or meat-puppet copy-pastes a comment written for them off-wiki, as there was at least one discussion and IIRC ArbCom case about recently). -sche (talk) 22:10, 5 December 2024 (UTC)
You don't need a new policy that does nothing but duplicate a subset of existing policy. At most what you need is to add a sentence to the existing policy that states "this includes comments written using LLMs", however you'd rightly get a lot of pushback on that because it's completely redundant and frankly goes without saying. Thryduulf (talk) 23:37, 5 December 2024 (UTC)
Support hallucinations are real. We should be taking a harder line against LLM generated participation. I don't think everyone who is doing it knows that they need to stop. Andre🚐23:47, 5 December 2024 (UTC)
Comment - Here is something that I imagine we will see more often. I wonder where it fits into this discussion. A user employs perplexity's RAG based system, search+LLM, to help generate their edit request (without the verbosity bias that is common when people don't tell LLMs how much output they want). Sean.hoyland (talk) 03:13, 6 December 2024 (UTC)
Support per all above. Discussions are supposed to include the original arguments/positions/statements/etc of editors here, not off-site chatbots. TheKip03:53, 6 December 2024 (UTC)
I also find it pretty funny that ChatGPT itself said it shouldn't be used, as per the premise posted above by EEng. TheKip03:58, 6 December 2024 (UTC)
"sycophancy is a general behavior of state-of-the-art AI assistants, likely driven in part by human preference judgments favoring sycophantic responses" - Towards Understanding Sycophancy in Language Models. They give us what we want...apparently. And just like with people, there is position bias, so the order of things can matter. Sean.hoyland (talk) 04:26, 6 December 2024 (UTC)
(Is this where I respond? If not, please move.) LLM-generated prose should be discounted. Sometimes there will be a discernible point in there; it may even be what the editor meant, lightly brushed up with what ChatGPT thinks is appropriate style. (So I wouldn't say "banned and punishable" in discussions, although we already deprecate machine translations on en.wiki and for article prose, same difference—never worth the risk.) However, LLMs don't think. They can't explain with reference to appropriate policy and guidelines. They may invent stuff, or use the wrong words—at AN recently, an editor accused another of "defaming" and "sacrilege", thus drowning their point that they thought that editor was being too hard on their group by putting their signature to an outrageous personal attack. I consider that an instance of LLM use letting them down. If it's not obvious that it is LLM use, then the question doesn't arise, right? Nobody is arguing for requiring perfect English. That isn't what WP:CIR means. English is a global language, and presumably for that reason, many editors on en.wiki are not native speakers, and those that aren't (and those that are!) display a wide range of ability in the language. Gnomes do a lot of fixing of spelling, punctuation and grammar in articles. In practice, we don't have a high bar to entrance in terms of English ability (although I think a lot more could be done to explain to new editors whose English is obviously non-native what the rule or way of doing things is that they have violated. And some of our best writers are non-native; a point that should be emphasised because we all have a right of anonymity here, many of us use it, and it's rare, in particular, that I know an editor's race. Or even nationality (which may not be the same as where they live.) But what we do here is write in English: both articles and discussions. If someone doesn't have the confidence to write their own remark or !vote, then they shouldn't participate in discussions; I strongly suspect that it is indeed a matter of confidence, of wanting to ensure the English is impeccable. LLMs don't work that way, really. They concoct things like essays based on what others have written. Advice to use them in a context like a Misplaced Pages discussion is bad advice. At best it suggests you let the LLM decide which way to !vote. If you have something to say, say it and if necessary people will ask a question for clarification (or disagree with you). They won't mock your English (I hope! Civility is a basic rule here!) It happens in pretty much every discussion that somebody makes an English error. No biggie. I'll stop there before I make any more typos myself; typing laboriously on my laptop in a healthcare facility, and anyway Murphy's Law covers this. Yngvadottir (talk)
I dunno about this specifically but I want to chime in to say that I find LLM-generated messages super fucking rude and unhelpful and support efforts to discourage them. – Joe (talk) 08:15, 6 December 2024 (UTC)
Comment I think obvious LLM/chatbot text should at least be tagged through an Edit filter for Recent Changes, then RC Patrollers and reviewers can have a look and decide for themselves. Am(Notes)11:58, 6 December 2024 (UTC)
How do you propose that such text be identified by an edit filter? LLM detections tools have high rates of both false positives and false negatives. Thryduulf (talk) 12:47, 6 December 2024 (UTC)
It might become possible once watermarks (like DeepMind's SynthID) are shown to be robust and are adopted. Some places are likely to require it at some point e.g. EU. I guess it will take a while though and might not even happen e.g. I think OpenAI recently decided to not go ahead with their watermark system for some reason. Sean.hoyland (talk) 13:17, 6 December 2024 (UTC)
It will still be trivial to bypass the watermarks, or use LLMs that don't implement them. It also (AIUI) does nothing to reduce false positives (which for our usecase are far more damaging than false negatives). Thryduulf (talk) 13:30, 6 December 2024 (UTC)
Maybe, that seems to be the case with some of the proposals. Others, like SynthID claim high detection rates, maybe because even a small amount of text contains a lot of signals. As for systems that don't implement them, I guess that would be an opportunity to make a rule more nuanced by only allowing use of watermarked output with verbosity limits...not that I support a rule in the first place. People are going to use/collaborate with LLMs. Why wouldn't they? Sean.hoyland (talk) 14:38, 6 December 2024 (UTC)
I don't think watermarks are a suitable thing to take into account. My view is that LLM usage should be a blockable offense on any namespace, but if it ends up being allowed under some circumstances then we at least need mandatory manual disclosures for any usage. Watermarks won't work / aren't obvious enough - we need something like {{LLM}} but self-imposed, and not tolerate unmarked usage. BugGhost🦗👻18:21, 6 December 2024 (UTC)
Comment As a practical matter, users posting obvious LLM-generated content will typically be in violation of other rules (e.g. disruptive editing, sealioning), in which case their discussion comments absolutely should be ignored, discouraged, discounted, or (in severe cases) hatted. But a smaller group of users (e.g. people using LLMs as a translation tool) may be contributing productively, and we should seek to engage with, rather than discourage, them. So I don't see the need for a separate bright-line policy that risks erasing the need for discernment — in most cases, a friendly reply to the user's first LLM-like post (perhaps mentioning WP:LLM, which isn't a policy or guideline, but is nevertheless good advice) will be the right approach to work out what's really going on. Preimage (talk) 15:53, 6 December 2024 (UTC)
Some translation tools have LLM assistance, but the whole point of generative models is to create text far beyond what is found in the user's input, and the latter is clearly what this proposal covers. JoelleJay (talk) 19:01, 6 December 2024 (UTC)
That might be what the proposal intends to cover, but it is not what the proposal actually covers. The proposal all comments that have been generated by LLMs and/or AI, without qualification. Thryduulf (talk) 01:05, 7 December 2024 (UTC)
70+% here understand the intention matches the language: generated by LLMs etc means "originated through generative AI tools rather than human thought", not "some kind of AI was involved in any step of the process". Even LLM translation tools don't actually create meaningful content where there wasn't any before; the generative AI aspect is only in the use of their vast training data to characterize the semantic context of your input in the form of mathematical relationships between tokens in an embedding space, and then match it with the collection of tokens most closely resembling it in the other language. There is, definitionally, a high level of creative constraint in what the translation output is since semantic preservation is required, something that is not true for text generation. JoelleJay (talk) 04:01, 7 December 2024 (UTC)
Do you have any evidence for you assertion that 70% of respondents have interpreted the language in the same way as you? Reading the comments associated with the votes suggests that it's closer to 70% of respondents who don't agree with you. Even if you are correct, 30% of people reading a policy indicates the policy is badly worded. Thryduulf (talk) 08:34, 7 December 2024 (UTC)
I think @Bugghost has summarized the respondent positions sufficiently below. I also think some portion of the opposers understand the proposal perfectly well and are just opposing anything that imposes participation standards. JoelleJay (talk) 22:54, 7 December 2024 (UTC)
There will be many cases where it is not possible to say whether a piece of text does or does not contain "human thought" by observing the text, even if you know it was generated by an LLM. Statements like "originated through generative AI tools rather than human thought" will miss a large class of use cases, a class that will probably grow over the coming years. People work with LLMs to produce the output they require. It is often an iterative process by necessity because people and models make mistakes. An example of when "...rather than human thought" is not the case is when someone works with an LLM to solve something like a challenging technical problem where neither the person or the model has a satisfactory solution to hand. The context window means that, just like with human collaborators, a user can iterate towards a solution through dialog and testing, exploring the right part of the solution space. Human thought is not absent in these cases, it is present in the output, the result of a collaborative process. In these cases, something "far beyond what is found in the user's input" is the objective, it seems like a legitimate objective, but regardless, it will happen, and we won't be able to see it happening. Sean.hoyland (talk) 10:46, 7 December 2024 (UTC)
Yes, but this proposal is supposed to apply to just the obvious cases and will hopefully discourage good-faith users from using LLMs to create comments wholesale in general. It can be updated as technology progresses. There's also no reason editors using LLMs to organize/validate their arguments, or as search engines for whatever, have to copy-paste their raw output, which is much more of a problem since it carries a much higher chance of hallucination. That some people who are especially familiar with how to optimize LLM use, or who pay for advanced LLM access, will be able to deceive other editors is not a reason to not formally proscribe wholesale comment generation. JoelleJay (talk) 22:27, 7 December 2024 (UTC)
That's reasonable. I can get behind the idea of handling obvious cases from a noise reduction perspective. But for me, the issue is noise swamping signal in discussions rather than how it was generated. I'm not sure we need a special rule for LLMs, maybe just a better way to implement the existing rules. Sean.hoyland (talk) 04:14, 8 December 2024 (UTC)
Comment: The original question was whether we should discount, ignore, strikethrough, or collapse chatbot-written content. I think there's a very big difference between these options, but most support !voters haven't mentioned which one(s) they support. That might make judging the consensus nearly impossible; as of now, supporters are the clear !majority, but supporters of what? — ypn^219:32, 6 December 2024 (UTC)
That means that supporters support the proposal that LLM-generated remarks in discussions should be discounted or ignored, and possibly removed in some manner. Not sure what the problem is here. Supporters support the things listed in the proposal - we don't need a prescribed 100% strict procedure, it just says that supporters would be happy with closers discounting, ignoring or under some circumstances deleting LLM content in discussions. BugGhost🦗👻19:40, 6 December 2024 (UTC)
More people have bolded "support" than other options, but very few of them have even attempted to refute the arguments against (and most that have attempted have done little more than handwaving or directly contradicting themselves), and multiple of those who have bolded "support" do not actually support what has been proposed when you read their comment. It's clear to me there is not going to be a consensus for anything other than "many editors dislike the idea of LLMs" from this discussion. Thryduulf (talk) 00:58, 7 December 2024 (UTC)
Arguing one point doesn't necessarily require having to refute every point the other side makes. I can concede that "some people use LLMs to improve their spelling and grammar" without changing my view overriding view that LLMs empower bad actors, time wasters and those with competence issues, with very little to offer wikipedia in exchange. Those that use LLMs legitimately to tidy up their alledgedly competent, insightful and self-sourced thoughts should just be encouraged to post the prompts themselves instead of churning it through an LLM first. BugGhost🦗👻09:00, 7 December 2024 (UTC)
If you want to completely ignore all the other arguments in opposition that's your choice, but don't expect closers to attach much weight to your opinions. Thryduulf (talk) 09:05, 7 December 2024 (UTC)
Ok, here's a list of the main opposition reasonings, with individual responses.
What about translations? - Translations are not up for debate here, the topic here is very clearly generative AI, and attempts to say that this topic covers translations as well is incorrect. No support voters have said the propositions should discount translated text, just oppose voters who are trying to muddy the waters.
What about accessibility? - This is could be a legitimate argument, but I haven't seen this substantiated anywhere other than handwaving "AI could help people!" arguments, which I would lump into the spelling and grammar argument I responded to above.
Detection tools are inaccurate - This I very much agree with, and noted in my support and in many others as well. But there is no clause in the actual proposal wording that mandates the use of automated AI detection, and I assume the closer would note that.
False positives - Any rule can have a potential for false positives, from wp:DUCK to close paraphrasing to NPA. We've just got to as a community become skilled at identifying genuine cases, just like we do for every other rule.
LLM content should be taken at face value and see if it violates some other policy - hopelessly naive stance, and a massive timesink. Anyone who has had the misfortune of going on X/twitter in the last couple of years should know that AI is not just used as an aid for those who have trouble typing, it is mainly used to spam and disrupt discussion to fake opinions to astroturf political opinions. Anyone who knows how bad the sockpuppetry issue is around CTOPs should be absolutely terrified of when (not if) someone decides to launch a full throated wave of AI bots on Misplaced Pages discussions, because if we have to invididually sanction each one like a human then admins will literally have no time for anything else.
I genuinely cannot comprehend how some people could see how AI is decimating the internet through spam, bots and disinformation and still think for even one second that we should open the door to it. BugGhost🦗👻10:08, 7 December 2024 (UTC)
There is no door. This is true for sockpuppetry too in my opinion. There can be a rule that claims there is a door, but it is more like a bead curtain. Sean.hoyland (talk) 11:00, 7 December 2024 (UTC)
The Twitter stuff is not a good comparison here. Spam is already nukable on sight, mass disruptive bot edits are also nukable on sight, and it's unclear how static comments on Misplaced Pages would be the best venue to astroturf political opinions (most of which would be off-topic anyway, i.e., nukable on sight). I'd prefer if people didn't use ChatGPT to formulate their points, but if they're trying to formulate a real point then that isn't disruptive in the same way spam is. Gnomingstuff (talk) 02:22, 10 December 2024 (UTC)
it's unclear how static comments on Misplaced Pages would be the best venue to astroturf political opinions - by disrupting RFCs and talk page discussions a bad actor could definitely use chatgpt to astroturf. A large proportion of the world uses Misplaced Pages (directly or indirectly) to get information - it would be incredibly valuable thing to manipulate. My other point is that AI disruption bots (like the ones on twitter) would be indistinguishable from individuals using LLMs to "fix" spelling and grammar - by allowing one we make the other incredibly difficult to identify. How can you tell the difference between a bot and someone who just uses chatgpt for every comment? BugGhost🦗👻09:16, 10 December 2024 (UTC)
Those that use LLMs legitimately to tidy up their alledgedly competent, insightful and self-sourced thoughts should just be encouraged to post the prompts themselves instead of churning it through an LLM first.
Social anxiety: Say "I" am a person unconfident in my writing. I imagine that when I post my raw language, I embarrass myself, and my credibility vanishes, while in the worst case nobody understands what I mean. As bad confidence is often built up through negative feedback, it's usually meritful or was meritful at some point for someone to seek outside help. Aaron Liu (talk) 23:46, 8 December 2024 (UTC)
While I sympathise with that hypothetical, Misplaced Pages isn't therapy and we shouldn't make decisions that do long-term harm to the project just because a hypothetical user feels emotionally dependent on a high tech spellchecker. I also think that in general wikipedia (myself included) is pretty relaxed about spelling and grammar in talk/WP space. BugGhost🦗👻18:45, 10 December 2024 (UTC)
We also shouldn't do long term harm to the project just because a few users are wedded to idea that LLMs are and will always be some sort of existential threat. The false positives that are an unavoidable feature of this proposal will do far more, and far longer, harm to the project than LLM-comments that are all either useful, harmless or collapseable/removable/ignorable at present. Thryduulf (talk) 19:06, 10 December 2024 (UTC)
The false positives that are an unavoidable feature of this proposal will do far more, and far longer, harm to the project - the same could be said for WP:DUCK. The reason why its not a big problem for DUCK is because the confidence level is very high. Like I've said in multiple other comments, I don't think "AI detectors" should be trusted, and that the bar for deciding whether something was created via LLM should be very high. I 100% understand your opinion and the reasoning behind it, I just think we have differing views on how well the community at large can identify AI comments. BugGhost🦗👻09:07, 11 December 2024 (UTC)
I don't see how allowing shy yet avid users to contribute has done or will do long-term harm. The potential always outweighs rational evaluation of outcomes for those with anxiety, a condition that is not behaviorally disruptive. Aaron Liu (talk) 02:47, 11 December 2024 (UTC)
I definitely don't want to disallow shy yet avid users! I just don't think having a "using chatgpt to generate comments is allowed" rule is the right solution to that problem, considering the wider consequences. BugGhost🦗👻08:52, 11 December 2024 (UTC)
Support strikethroughing or collapsing per everyone else. The opposes that mention ESL have my sympathy, but I am not sure how many of them are ESL themselves. Having learnt English as my second language, I have always found it easier to communicate when users are expressing things in their own way, not polished by some AI. I sympathise with the concerns and believe the right solution is to lower our community standards with respect to WP:CIR and similar (in terms of ESL communication) without risking hallucinations by AI. Soni (talk) 02:52, 7 December 2024 (UTC)
Oppose - I'm sympathetic to concerns of abuse through automated mass-commenting, but this policy looks too black-and-white. Contributors may use LLMs for many reasons, including to fix the grammar, to convey their thoughts more clearly, or to adjust the tone for a more constructive discussion. As it stands, this policy may lead to dismissing good-faith AI-assisted comments, as well as false positives, without considering the context. Moreover, while mainstream chatbots are not designed to just mimic the human writing style, there are existing tools that can make AI-generated text more human-like, so this policy does not offer that much protection against maliciously automated contributions. Alenoach (talk) 01:12, 9 December 2024 (UTC)
Oppose What @Alenoach said is correct, basic AI tools like Grammarly should be allowed (note that grammarly can also change sentences and wording and has generative AI tools) but just blatantly asking ChatGPT to generate a administrator report is different. Rc2barrington (talk) 04:46, 1 January 2025 (UTC)
Oppose – Others have cast doubt on the efficacy of tools capable of diagnosing LLM output, and I can't vouch for its being otherwise. If EEng's example of ChatBot output is representative—a lengthy assertion of notability without citing sources—that is something that could well be disregarded whether it came from a bot or not. If used carefully, AI can be useful as an aide-memoire (such as with a spell- or grammar-checker) or as a supplier of more felicitous expression than the editor is naturally capable of (e.g. Google Translate). Dhtwiki (talk) 10:27, 9 December 2024 (UTC)
Comment / Oppose as written. It's not accurate that GPTZero is good at detecting AI-generated content. Citations (slightly out of date but there's little reason to think things have changed from 2023): https://www.aiweirdness.com/writing-like-a-robot/ , https://www.aiweirdness.com/dont-use-ai-detectors-for-anything-important/ . For those too busy to read, a few choice quotes: "the fact that it insisted even one excerpt is not by a human means that it's useless for detecting AI-generated text," and "Not only do AI detectors falsely flag human-written text as AI-written, the way in which they do it is biased" (citing https://arxiv.org/abs/2304.02819 ). Disruptive, worthless content can already be hatted, and I'm not opposed to doing so. Editors should be sharply told to use their own words, and if not already written, an essay saying we'd rather have authentic if grammatically imperfect comments than AI-modulated ones would be helpful to cite at editors who offer up AI slop. But someone merely citing GPTZero is not convincing. GPTZero will almost surely misidentify genuine commentary as AI-generated. So fine with any sort of reminder that worthless content can be hatted, and fine with a reminder not to use ChatGPT for creating Misplaced Pages talk page posts, but not fine with any recommendations of LLM-detectors. SnowFire (talk) 20:00, 9 December 2024 (UTC)
@SnowFire, I can't tell if you also oppose the actual proposal, which is to permit hatting/striking obvious LLM-generated comments (using GPTzero is a very minor detail in JSS's background paragraph, not part of the proposal). JoelleJay (talk) 01:47, 11 December 2024 (UTC)
I support the proposal in so far as disruptive comments can already be hatted and that LLM-generated content is disruptive. I am strongly opposed to giving well-meaning but misguided editors a license to throw everyone's text into an AI-detector and hat the comments that score poorly. I don't think it was that minor a detail, and to the extent that detail is brought up, it should be as a reminder to use human judgment and forbid using alleged "AI detectors" instead. SnowFire (talk) 03:49, 11 December 2024 (UTC)
Support collapsing AI (specifically, Large language model) comments by behavioral analysis (most actually disruptive cases I've seen are pretty obvious) and not the use of inaccurate tools like ZeroGPT. I thinking hatting with the title "Editors suspect that this comment has been written by a Large language model" is appropriate. They take up SO much space in a discussion because they are also unnecessarily verbose, and talk on and on but never ever say something that even approaches having substance. Discussions are for human Misplaced Pages editors, we shouldn't have to use to sift through comments someone put 0 effort into and outsourced to a robot that writes using random numbers (that's a major part of how tools like ChatGPT work and maintain variety). If someone needs to use an AI chatbot to communicate because they don't understand English, then they are welcome to contribute to their native language Misplaced Pages, but I don't think they have the right to insist that we at enwiki spend our effort reading comments they but minimal effort into besides opening the ChatGPT website. If really needed, they can write in their native language and use a non-LLM tool like Google Translate. The use of non-LLM tools like Grammarly, Google Translate, etc. I think should still be OK for all editors, as they only work off comments that editors have written themselves. MolecularPilot05:10, 10 December 2024 (UTC)
Adding that enforcing people writing things in their own words will actually help EAL (English additional language) editors contribute here. I world with EAL people irl, and even people who have almost native proficiency with human-written content find AI output confusing because it says things in the most confusing, verbose ways using difficult sentence constructions and words. I've seen opposers in this discussion who maybe haven't had experience working with EAL people go "what about EAL people?", but really, I think this change will help them (open to being corrected by someone who is EAL, tho). MolecularPilot05:17, 10 December 2024 (UTC)
Also, with regards to oppose comments that discussions are not a vote so closes will ignore AI statements which don't have merit - unedited LLM statements are incredibly verbose and annoying, and clog up the discussion. Imagine multiple paragraphs, each with a heading, but all of which say almost nothing, they're borderline WP:BLUDGEONy. Giving the power to HAT them will help genuine discussion contributors keep with the flow of human arguments and avoid scaring away potential discussion contributors who are intimidated or don't feel they have the time to read the piles of AI nonsense that fill the discussion. MolecularPilot06:38, 10 December 2024 (UTC)
Support (removing) in general. How is this even a question? There is no case-by-case. It is a fundamental misunderstanding of how LLMs work to consider their output reliable without careful review. And which point, the editor could have written it themselves without inherent LLM bias. The point of any discussion is to provide analytical response based on the context, not have some tool regurgitate something from a training set that sounds good. And frankly, it is disrespectuful to make someone read "AI" responses. It is a tool and there is a place and time for it, but not in discussions in an encyclopedia. — HELLKNOWZ∣TALK15:41, 10 December 2024 (UTC)
Strong Support. I'm very interested in what you (the generic you) have to say about something. I'm not remotely interested in what a computer has to say about something. It provides no value to the discussion and is a waste of time. Useight (talk) 18:06, 10 December 2024 (UTC)
Comments that provide no value to the discussion can already be hatted and ignored regardless of why they provide no value, without any of the false positive or false negatives inherent in this proposal. Thryduulf (talk) 18:25, 10 December 2024 (UTC)
Indeed, and that's fine for one-offs when a discussion goes off the rails or what-have-you. But we also have WP:NOTHERE for disruptive behavior, not working collaboratively, etc. I'm suggesting that using an AI to write indicates that you're not here to build the encyclopedia, you're here to have an AI build the encyclopedia. I reiterate my strong support for AI-written content to be removed, struck, collapsed, or hatted and would support further measures even beyond those. Useight (talk) 21:54, 11 December 2024 (UTC)
There are two sets of people described in your comment: those who use AI and those who are NOTHERE. The two sets overlap, but nowhere near sufficiently to declare that everybody in the former set are also in the latter set. If someone is NOTHERE they already can and should be blocked, regardless of how they evidence that. Being suspected of using AI (note that the proposal does not require proof) is not sufficient justification on its own to declare someone NOTHERE, per the many examples of constructive use of AI already noted in this thread. Thryduulf (talk) 22:03, 11 December 2024 (UTC)
To reiterate, I don't believe that any use of AI here is constructive, thus using it is evidence of WP:NOTHERE, and, therefore, the set of people using AI to write is completely circumscribed within the set of people who are NOTHERE. Please note that I am referring to users who use AI-generated writing, not users suspected of using AI-generated writing. I won't be delving into how one determines whether someone is using AI or how accurate it is, as that is, to me, a separate discussion. This is the end of my opinion on the matter. Useight (talk) 23:26, 11 December 2024 (UTC)
You are entitled to your opinion of course, but as it is contradicted by the evidence of both multiple constructive uses and of the near-impossibility of reliably detecting LLM-generated text without false positives, I would expect the closer of this discussion to attach almost no weight to it. Thryduulf (talk) 00:42, 12 December 2024 (UTC)
I am ESL and use LLMs sometimes because of that. I feel like I don't fit into the NOTHERE category. It seems like you do not understand what they are or how they can be used constructively. PackMecEng (talk) 01:43, 12 December 2024 (UTC)
No, I understand. What you're talking about is no different from using Google Translate or asking a native-speaker to translate it. You, a human, came up with something you wanted to convey. You wrote that content in Language A. But you wanted to convey that message that you - a human - wrote, but now in Language B. So you had your human-written content translated to Language B. I have no qualms with this. It's your human-written content, expressed in Language B. My concern is with step 1 (coming up with something you want to convey), not step 2 (translating that content to another language). You write a paragraph for an article but it's in another language and you need the paragraph that you wrote translated? Fine by me. You ask an AI to write a paragraph for an article? Not fine by me. Again, I'm saying that there is no valid use case for AI-written content. Useight (talk) 15:59, 12 December 2024 (UTC)
It seems very likely that there will be valid use cases for AI-written content if the objective is maximizing quality and minimizing errors. Research like this demonstrate that there will likely be cases where machines outperform humans in specific Misplaced Pages domains, and soon. But I think that is an entirely different question than potential misuse of LLMs in consensus related discussions. Sean.hoyland (talk) 16:25, 12 December 2024 (UTC)
But your vote and the proposed above makes not distinction there. Which is the main issue. Also not to be pedantic but every prompted to a LLM is filled out by a human looking to convey a message. Every time someone hits publish on something here it is that person confirming that is what they are saying. So how do we in practice implement what you suggest? Because without a method better than vibes it's worthless. PackMecEng (talk) 18:53, 12 December 2024 (UTC)
The proposal specifies content generated by LLMs, which has a specific meaning in the context of generative AI. If a prompt itself conveys a meaningful, supported opinion, why not just post that instead? The problem comes when the LLM adds more information than was provided, which is the whole point of generative models. JoelleJay (talk) 01:52, 13 December 2024 (UTC)
Yes in principle. But in practice, LLM detectors are not foolproof, and there are valid reasons to sometimes use an LLM, for example to copyedit. I have used Grammarly before and have even used the Microsoft Editor, and while they aren't powered by LLMs, LLMs are a tool that need to be used appropriately on Misplaced Pages. AwesomeAasim19:55, 10 December 2024 (UTC)
Support. Using LLM to reply to editors is lazy and disrespectful of fellow editor's time and brainpower. In the context of AFD, it is particularly egregious since an LLM can't really read the article, read sources, or follow our notability guidelines. By the way. gptzero and other such tools are very good at detecting this. I don't think this is correct at all. I believe the false positive for AI detectors is quite high. High enough that I would recommend not using AI detectors. –Novem Linguae (talk) 03:23, 11 December 2024 (UTC)
Support. AI generated text should be removed outright. If you aren't willing to put the work into doing your own writing then you definitely haven't actually thought deeply about the matter at hand. User1042💬✒️14:16, 11 December 2024 (UTC)
This comment is rather ironic given that it's very clear you haven't thought deeply about the matter at hand, because if you had then you'd realise that it's actually a whole lot more complicated than that. Thryduulf (talk) 14:26, 11 December 2024 (UTC)
Thryduulf I don't think this reply is particular helpful, and it comes off as slightly combative. It's also by my count your 24th comment on this RFC. BugGhost🦗👻19:20, 11 December 2024 (UTC)
I recognize that AI paraphrased or edited is not problematic in the same ways as text generated outright by an AI. I only meant to address the core issue at steak, content whose first draft was written by an AI system. User1042💬✒️22:16, 17 December 2024 (UTC)
I've recently come across several users in AFD discussions that are using LLMs to generate their remarks there. As many of you are aware, gptzero and other such tools are very good at detecting this. I don't feel like any of us signed up for participating in discussions where some of the users are not using their own words but rather letting technology do it for them. Discussions are supposed to be between human editors. If you can't make a coherent argument on your own, you are not competent to be participating in the discussion. I would therefore propose that LLM-generated remarks in discussions should be discounted or ignored, and possibly removed in some manner
Support with the caveat that our ability to deal with the issue goes only as far as we can accurately identify the issue (this appears to have been an issue raised across a number of the previous comments, both support and oppose, but I think it bears restating because we're approaching this from a number of different angles and its IMO the most important point regardless of what conclusions you draw from it). Horse Eye's Back (talk) 19:24, 11 December 2024 (UTC)
Strong support, limited implementation. Misplaced Pages is written by volunteer editors, says our front page. This is who we are, and our writing is what Misplaced Pages is. It's true that LLM-created text can be difficult to identify, so this may be a bit of a moving target, and we should be conservative in what we remove—but I'm sure at this point we've all run across cases (whether here or elsewhere in our digital lives) where someone copy/pastes some text that includes "Is there anything else I can help you with?" at the end, or other blatant tells. This content should be deleted without hesitation. Retswerb (talk) 04:11, 12 December 2024 (UTC)
Support in concept, questions over implementation — I concur with Dronebogus that users who rely on LLMs should not edit English Misplaced Pages. It is not a significant barrier for users to use other means of communication, including online translators, rather than artificial intelligence. How can an artificial intelligence tool argue properly? However, I question how this will work in practice without an unacceptable degree of error. elijahpepe@wikipedia (he/him) 22:39, 12 December 2024 (UTC)
Well since people keep bringing this up as a semi-strawman: no I don’t support banning machine translation, not that I encourage using it (once again, if you aren’t competent in English please don’t edit here) Dronebogus (talk) 07:34, 13 December 2024 (UTC)
LLMs are incredible at translating, and many online translators already incorporate them, including Google Translate. Accomodating LLMs is an easy way to support the avid not only the ESL but also the avid but shy. It has way more benefits than the unseen-to-me amount of AI trolling that isn't already collapse-on-sight. Aaron Liu (talk) 00:05, 13 December 2024 (UTC)
Google Translate uses the same transformer architecture that LLMs are built around, and uses e.g. PaLM to develop more language support (through training that enables zero-shot capabilities) and for larger-scale specialized translation tasks performed through the Google Cloud "adaptive translation" API, but it does not incorporate LLMs into translating your everyday text input, which still relies on NMTs. And even for the API features, the core constraint of matching input rather than generating content is still retained (obviously it would be very bad for a translation tool to insert material not found in the original text!). LLMs might be good for translation because they are better at evaluating semantic meaning and detecting context and nuance, but again, the generative part that is key to this proposal is not present. JoelleJay (talk) 01:20, 13 December 2024 (UTC)
PaLM (Pathways Language Model) is a 540 billion-parameter transformer-based large language model (LLM) developed by Google AI. If you meant something about how reschlmunking the outputs of an LLM or using quite similar architecture is not really incorporating the LLM, I believe we would be approaching Ship of Theseus levels of recombination, to which my answer is it is the same ship.
obviously it would be very bad for a translation tool to insert material not found in the original text!
PaLM2 is not used in the consumer app (Google Translate), it's used for research. Google Translate just uses non-generative NMTs to map input to its closes cognate in the target language. JoelleJay (talk) 01:34, 13 December 2024 (UTC)
Well, is the NMT really that different enough to not be classified as an LLM? IIRC the definition of an LLM is something that outputs by predicting one-by-one what the next word/"token" should be, and an LLM I asked agreed that NMTs satisfy the definition of a generative LLM, though I think you're the expert here. Aaron Liu (talk) 02:01, 13 December 2024 (UTC)
Google Translate's NMT hits different enough to speak English much less naturally than ChatGPT 4o. I don't consider it a LLM, because the param count is 380M not 1.8T.
the definition of an LLM is something that outputs by predicting one-by-one what the next word/"token" should be No, that def would fit ancient RNN tech too. 172.97.141.219 (talk) 17:50, 13 December 2024 (UTC)
Even if you don’t consider it L, I do, and many sources cited by the article do. Since we’ll have such contesting during enforcement, it’s better to find a way that precludes such controversy. Aaron Liu (talk) 20:44, 13 December 2024 (UTC)
NMTs, LLMs, and the text-creation functionality of LLMs are fundamentally different in the context of this discussion, which is about content generated through generative AI. NMTs specifically for translation: they are trained on parallel corpora and their output is optimized to match the input as precisely as possible, not to create novel text. LLMs have different training, including way more massive corpora, and were designed specifically to create novel text. One of the applications of LLMs may be translation (though currently it's too computationally intensive to run them for standard consumer purposes), by virtue of their being very good at determining semantic meaning, but even if/when they do become mainstream translation tools what they'll be used for is still not generative when it comes to translation output. JoelleJay (talk) 22:29, 13 December 2024 (UTC)
The proposal is for hatting obvious cases of LLM-generated comments. Someone who just uses an LLM to copyedit will still have written the content themselves and presumably their output would not have the obvious tells of generative AI. JoelleJay (talk) 23:56, 13 December 2024 (UTC)
Not when I tried to use it. Quantitatively, GPTZero went from 15% human to 100% AI for me despite the copyedits only changing 14 words. Aaron Liu (talk) 00:33, 14 December 2024 (UTC)
Does it really mean that? All you've demonstrated is that GPTZero has false positives, which is exactly why its use here was discouraged. jlwoodwa (talk) 05:26, 14 December 2024 (UTC)
My subjective evaluation of what I got copyediting from ChatGPT was that it sounded like ChatGPT. I used GPTZero to get a number. Aaron Liu (talk) 14:18, 14 December 2024 (UTC)
It changed only 14 words across two paragraphs and still retained the same meaning in a way that I would describe it as copyediting. Such levels of change are what those lacking confidence in tone would probably seek anyways. Aaron Liu (talk) 00:15, 24 December 2024 (UTC)
On one hand, AI slop is a plague on humanity and obvious LLM output should definitely be disregarded when evaluating consensus. On the other hand, I feel like existing policy covers this just fine, and any experienced closer will lend greater weight to actual policy-based arguments, and discount anything that is just parroting jargon. WindTemposthey23:21, 12 December 2024 (UTC)
Support in principle, but we cannot rely on any specific tools because none are accurate enough for our needs. Whenever I see a blatant ChatGPT-generated !vote, I ignore it. They're invariably poorly reasoned and based on surface-level concepts rather than anything specific to the issue being discussed. If someone is using AI to create their arguments for them, it means they have no actual argument besides WP:ILIKEIT and are looking for arguments that support their desired result rather than coming up with a result based on the merits. Also, toasters do not get to have an opinion. The Wordsmith05:17, 13 December 2024 (UTC)
Oppose. For creating unnecessary drama. First of, the "detector" of the AI bot is not reliable, or at least the reliability of the tool itself is still questionable. If the tool to detect LLM itself is unreliable, how can one reliably point out which one is LLM and which one is not? We got multiple tools that claimed to be able to detect LLM as well. Which one should we trust? Should we be elevating one tool over the others? Have there been any research that showed that the "picked" tool is the most reliable? Second, not all LLMs are dangerous. We shouldn't treat LLM as a virus that will somehow take over the Internet or something. Some editors use LLM to smooth out their grammar and sentences and fix up errors, and there is nothing wrong with that. I understand that banning obvious LLM text per WP:DUCK are good, but totally banning them is plain wrong. ✠ SunDawn ✠(contact)22:56, 15 December 2024 (UTC)
@SunDawn, the proposal is to permit editors to collapse/strike obvious LLM text, not to "ban LLM totally". If LLM use is imperceptible, like for tweaking grammar, it's not going to be affected. JoelleJay (talk) 20:17, 19 December 2024 (UTC)
Support with some kind of caveat about not relying on faulty tools or presuming that something is LLM without evidence or admission, based on the following reasons:
We have stricter rules around semi-automated editing (rollback, AutoWikiBrowser, etc.) and even stricter rules around fully automated bot editing. These cleanup edits are widely accepted as positive, but there is still the concern about an overwhelming amount of bad edits to wade through and/or fix. A form of that concern is relevant here. Someone could reply to every post in this discussion in just a minute or so without ever reading anything. That's inherently disruptive.
Nobody who is voting "oppose" is using an LLM to cast that vote. The LLM comments have been left by those supporting to make a point about how problematic they are for discussions like this. I think this reflects, even among oppose voters, a developing community consensus that LLM comments will be disregarded.
If the rule in practice is to disregard LLM comments, not writing that rule down does not stop it from being the rule, consensus, or a community norm. It just makes the rule less obvious and less clear.
It's disrespectful for an editor to ask someone to spend their time reading a comment if they couldn't be bothered to spend any time writing it, and therefore a violation of the policy Misplaced Pages:Civility, "treat your fellow editors as respected colleagues with whom you are working on an important project."
I am strongly opposed to banning or ignoring LLM-made talk page comments just because they are LLM-made. I'm not a big fan of LLMs at all; they are actually useful only for some certain things, very few of which are directly relevant to contributing to Misplaced Pages in English or in any other language. However, some of those things are useful for this, at least for some humans, and I don't want to see these humans being kicked out of the English Misplaced Pages. I already witnessed several cases in which people whose first language is not English tried writing talk page responses in the English Misplaced Pages, used an LLM to improve their writing style, and got their responses ignored only because they used an LLM. In all those cases, I had strong reasons to be certain that they were real humans, that they meant what they wrote, and that they did it all in good faith. Please don't say that anyone who wants to contribute to the English Wikipeida should, in the first place, know English well enough to write a coherent talk page comment without LLM assistance; occasionally, I kind of wish that it was like that myself, but then I recall that the world is more complicated and interesting than that. Uses of LLMs that help the English Misplaced Pages be more inclusive for good-faith people are good. Of course, defining what good faith means is complicated, but using an LLM is not, by itself, a sign of bad faith. --Amir E. Aharoni (talk) 04:52, 19 December 2024 (UTC)
Those concerned about their English should use translation software rather than an llm. Both might alter the meaning to some extent, but only one will make things up. (It's also not a sure assumption that llm text is coherent talkpage text.) CMD (talk) 07:44, 19 December 2024 (UTC)
@CMD The dividing line between translation software and LLM is already blurry and will soon disappear. It's also rare that translation software results in coherent talkpage text, unless it's relying on some (primitive) form of LLM. So if we're going to outlaw LLMs, we would need to outlaw any form of translation software, and possibly any text-to-speech software as well. ypn^223:41, 19 December 2024 (UTC)
The distinctions have already been covered above, and no we would not have to. There is an obvious difference between software intended to translate and software intended to generate novel text, and users are likely to continue to treat those differently. CMD (talk) 02:49, 20 December 2024 (UTC)
Strong oppose to the proposal as written. Misplaced Pages already suffers from being stuck in a 2001mindset and a refusal to move with the technological times. Anyone who remembers most Wikipedians' visceral reaction to FLOW and VisualEditor when they were first introduced will observe a striking similarity. Yes, those projects had serious problems, as do LLM-generated comments. But AI is the future, and this attitude of "Move slowly to avoid changing things" will ultimately lead Misplaced Pages the way of Encyclopædia Britannica. Our discussion needs to be how best to change, not how to avoid to change. ypn^223:54, 19 December 2024 (UTC)
The main objection to VE and a major objection to FLOW was the developers' insistence on transforming Wikitext to HTML for editing and then transforming that back to Wikitext. Aaron Liu (talk) 01:31, 20 December 2024 (UTC)
True. Then, as now, there were many valid objections. But IIRC, there was limited discussion of "Let's figure out a better way to improve", and lots of "Everything is fine; don't change anything, ever." That attitude concerns me. ypn^201:52, 20 December 2024 (UTC)
I oppose the proposal but I think the comparison to FLOW and VisualEditor is beyond silly. Those things did not exist outside of a MediaWiki context. LLMs are a global issue. Gnomingstuff (talk) 17:11, 28 December 2024 (UTC)
Support. I'm not even slightly swayed by these "it'll be too hard to figure out" and "mistakes could be made" and "we can't be 100% certain" sorts of arguments. That's true of everything around here, and its why we have an admins-must-earn-a-boatload-of-community-trust system, and a system of review/appeal of decisions they (or of course non-admin closers) make, and a consensus-based decisionmaking system more broadly. JoelleJay has it exactly right: having a policy that permits closers to discount apparently-LLM-generated contributions will discourage good-faith editors from using LLMs irresponsibly and perhaps motivate bad-faith editors to edit the raw output to appear more human, which would at least involve some degree of effort and engagement with their "own" arguments. And as pointed out by some others, the "it'll hurt non-native-English speakers" nonsense is, well, nonsense; translation is a different and unrelated process (though LLMs can perform it to some extent), of remapping one's own material onto another language.
I'm also not in any way convinved by the "people poor at writing and other cognitive tasks needs the LLM to help them here" angle, because WP:COMPETENCE is required. This is work (albeit volunteer work), it is WP:NOT a game, a social-media playground, a get-my-ideas-out-there soapbox, or a place to learn how to interact e-socially or pick up remedial writing skills, nor a venue for practicing one's argument techiques. It's an encyclopedia, being built by people who – to be productive contributors instead of a draining burden on the entire community – must have: solid reasoning habits, great judgement (especially in assessing reliability of claims and the sources making them), excellent writing skills of a highly particularized sort, a high level of fluency in this specific language (in multiple registers), and a human-judgement ability to understand our thick web of policies, guidelines, procedures, and often unwritten norms, and how they all interact, in a specific contextual way that may vary greatly by context. None of these is optional. An LLM cannot do any of them adequately (not even write well; their material sticks out like a sore thumb, and after a while you can even tell which LLM produced the material by its habitual but dinstictive crappy approach to simulating human thought and language).
In short, if you need an LLM to give what you think is meaningful input into a decision-making process on Misplaced Pages (much less to generate mainspace content for the public), then you need to go find something else to do, something that fits your skills and abilities. Saying this so plainly will probably upset someone, but so it goes. I have a rep for "not suffering fools lightly" and "being annoying but correct"; I can live with that if it gets the right decisions made and the work advanced. — SMcCandlish☏¢ 😼 05:49, 22 December 2024 (UTC)
PS, something that came up more recently than my original post above: If anyone's wondering why some of us are such "AI" skeptics, its because the technology is badly, badly faulty, producing multiple blatant factual errors even in short material, entirely fictive "hallucinations", direct forgery of sourcing, nested chains of error compounded upon error when context isn't gleaned properly, disingenuous attempts to hide that it is lying, and worse. A few days ago, I got ChatGPT 4o to literally lose its f#*$ing mind: I had it generate some short code (very simple one-liner regex) with a really obvious error, so I pointed out the error and gave it documentation that proved it was an error. It conceded the error and even explained what the error was and why it was erroneous, then said how it was going to fix it. And ... proceeded to output the same error again (in just one of three examples, the other two being correct). Fascinated and horrified by this, I tried for over half an hour to get it to produce a correct example, and it was utterly incapable of doing it. It knew the error was an error and what that error was and why, spelled out what the correct approach should be, then repeated the error every single time (always at the first occurrence, or always if the only occurrence). I've captured that session and will be doing a write-up about it. This is much, much worse that a "hallucination", being an abject inability to stop doing what it already knows is absolutely wrong. When people have fears like "If I had a house AI, and it was in control of the bathwater temperature, it might boil my children alive", they are not paranoid or unreasonable. My experiment with ChatGPT proves this conclusively. If the AI can (with trivial effort) be put into a crazy failure-looping state where it knows it's doing or about to do something wrong but insists on doing it anyway – i.e. during its take-an-action phase it completely loses connection to reality, even it's internal reality much less external input telling it "no!" – then we are in grave danger. This is essentially the mental state of a psychopath: "I know I shouldn't grab my neighbor's little daughter and strangle her to death, but I just can't stop myself." — SMcCandlish☏¢ 😼 01:42, 28 December 2024 (UTC)
The problem with all that is that we already have a policy that allows the hatting or removal of comments that are actually problematic because of their content (which are the only ones that we should be removing) without regard for whether it was or was not written by LLM. Everything that actually should be removed can be removed already. Thryduulf (talk) 11:39, 22 December 2024 (UTC)
If that's "the problem with all that", then it is not any kind of problem at all. It's entirely normal in our WP:P&G material to reiterate a principle defined in one place for contextual application at another, and to extrapolate from a general principle to a more specific application. We do this often to cut through the exact kind of wikilawyering we're facing over this issue: there's not a specific rule against LLM-generated !voting, so the argument is (again and again in this thread) to permit it (unless it's such senseless gibberish that it would be removed anyway even if no LLM were involved). The community clearly doesn't actually want that result (or more accurately, there is not a consensus in favor of it), though this specific proposal's approach to thwarting the "AI"-spamming of our decision-making processes might not be perfect. To me, it's a step in the right direction. If it were implemented this way and some uncommon issue arose with that implementation, then we'd tweak it to address that micro-problem. We must not continue to avoid addressing the macro-problem just because someone can imagine edge cases that might not work out ideally. That, too, is true of all of our P&G and process. — SMcCandlish☏¢ 😼 01:15, 28 December 2024 (UTC)
People who have good reading skills, great judgement, and solid reasoning habits enough to find problems in existing articles don't necessarily have great interpersonal writing/communication skills or the confidence. Meanwhile, for all LLM is bad at, it is very good at diluting everything you say to become dry, dispassionate, and thus inoffensive. Aaron Liu (talk) 15:26, 22 December 2024 (UTC)
I doubt that anyone would seriously object to some ultra-hothead running their post through an LLM with a query like "Can you see anything in this that might come off as aggressive or offensive, and suggest a revision that only affects that aspect of the material?" The result might not even be noticeable as LLM-modified. If it doesn't stick out as LLM garbage, there there is no way for this proposal to affect such a post, because no one here is a mind-reader (we cannot magically detect through remote sensing that someone toned their rant down with LLM help). So, this proposal is not broken (at least not with regard to that scenario). That said, the main reason that WP:COMPETENCE was written (and it's one of the essays that, like WP:BRD and WP:AADD, has become "operative" within the community as if a policy or guideline) is the very "don't necessarily have great interpersonal ... skills" issue you mention. That is, lacking those skills to a serious enough degree makes one not competent to work on a collaborative encyclopedia project, and one will eventually be ejected after causing enough disruption. Something we don't need is LLMs masking for a while that someone has this kind of competence failure; it will just drag out the inevitable. By way of analogy: if I were a kleptomaniac and just unable to stop myself from shoplifting, it would not be okay for me to use a device that scrambled stores' surveillance camera footage to make it more likely for me to get away with more shoplifting (and there would certainly be no obligation on the part of the store owner to turn their cameras off, or to take no action if they catch me stealing, just because I tell them I'm a kleptomaniac and my unconstructive behavior isn't something I can manage. — SMcCandlish☏¢ 😼 01:15, 28 December 2024 (UTC)
People who can't communicate that well often won't attempt to burn others down. I don't think there's any disruption or substantial additional investment in accommodating those who won't burn others down (which I'd say is the majority) by reading their perfectly comprehensible AI-diluted arguments. (Scrambling footage is like erasing the memories of the incident, which I don't think is a good analogue of the issue at hand. I'd say it's more like working with someone who stinks and masks that with perfume.) Aaron Liu (talk) 00:05, 29 December 2024 (UTC)
I'm pretty sure most people here understand why there are AI skeptics. I also hate ChatGPT. But there's a difference between my personal opinion of ChatGPT and the fact that someone using ChatGPT to communicate is still communicating. The risk of your house AI hallucinating is that your children get boiled alive. The risk of ChatGPT hallucinating on a talk page is that they make a dumb, disregardable argument, of the kind that humans pump out by the thousands. (Someone linked an example of some AfD delete !votes generated by AI and frankly they're better reasoned than a lot of the stuff humans post.) Gnomingstuff (talk) 17:32, 28 December 2024 (UTC)
(The bigger issue is people using Misplaced Pages as ChatGPT -- i.e. posting the prompts, not the responses -- but, like much of what is being discussed here, that is already stuff that can be removed.) Gnomingstuff (talk) 17:36, 28 December 2024 (UTC)
Support. Sure I have questions about detection, but I don't think it means we shouldn't have a policy that explicitly states that it should not be used (and can be ignored/hatted if it is). Judging solely based on content (and no wp:bludgeoning, etc.) is unsustainable IMO. It would mean taking every wall of text seriously until it's clear that the content is unhelpful, and LLMs are very good at churning out plausible-sounding bullshit. It wastes everyone's time. If cognitive impairments or ESL issues make it hard to contribute, try voice-to-text, old-school translation software, or some other aid. LLMs aren't really you.--MattMauler (talk) 11:27, 23 December 2024 (UTC)
Comment. While I agree with the sentiment of the request, I am at a loss to see how we can identify LLM generated comments in a consistent manner that can scale. Yes, it might be easier to identify egregious copy paste of wall of text, but, anything other than that might be hard to detect. Our options are:
Robust tooling to detect LLM generated text, with acceptably low levels of false positives. Somewhat similar to what Earwig does for Copyvios. But, someone needs to build it and host it on WMTools or at a similar location.
Self certification by editors. Every edit / publish dialogbox should have a checkbox for "Is this text LLM generated" with y/n optionality.
Editors playing a vigilante role in reading the text and making a personal call on other editors' text. Obviously this is least preferred.
A couple of days ago, an editor ran a new article through GPTzero, and was told that it was 99.8% likely to be AI-generated. I ran the same revision of the same article through the same tool the next day, and it told me that it was 98.3% likely to be human-written.
Bonus suggestion!: I'm curious what Wikipedians think about this so let's try this. Many of the comments here discuss the impracticality of determining whether a user's comments are AI generated (i.e. gptzero isn't perfect), and many give valid arguments for using LLMs (i.e. ESL). If an argument is suspected to be written by LLM, I propose that editors should examine the user. Take a look at their listed contributions, and if they seem to have a habit of using AI, open a discussion on their talk page. If the user has a habit of using AI and doesn't recognize the inherent problems and refuses to change, this can be brought to the administrators' noticeboard for potential blocks. If (and only if) the person is blocked for using AI, their comments can be ignored. Or just ask ChatGPT to summarize them for you lol guninvalid (talk) 06:12, 25 December 2024 (UTC)
I think that the general idea here is good: As much as possible, treat each account individually, and handle LLM use as a behavioral problem when it's actually a practical problem (i.e., not when it seems to be accurate and seems to be appropriate). WhatamIdoing (talk) 04:38, 26 December 2024 (UTC)
Except a substantial portion of the input in this thread is disagreement with the idea that English being someone's second language is an excuse for LLM-generated content at all. Translation of one's own material is an entirely different process (even if often leveraged by LLMs set to a different task than trying to generate what they "think" is new material that will pass as human-authored). I'm skeptical that any of the other things you're accepted as "valid arguments" from the pro-LLM or LLM-accepting side of this debate have consensus as valid, either. But go ahead and spell them out and we'll see. — SMcCandlish☏¢ 😼 01:30, 28 December 2024 (UTC)
Strong support the removal of any obvious, low effort AI-generated post. I recently came across a user postingmultiple such examples. When called out on it they blew up and posted a comment saying, amongst other things "HAHAHAHHAHAHAHAHAHAHHAHAHAHAHAHA. Yes, some of it might be. Because I don't have time to argue with, in my humble opinion, stupid PHOQUING people." and "YOUUUUUUUUUUUUUUUUUUUUUUUUUUUU are assuming bath faith in me."
They were later blocked as a sock evading a global lock.
Currently it is too easy for trolls to game WP:AGF and AI to waste people's time arguing with their bot-generated replies. Using AI to write your posts for you makes it difficult for others to assume good faith. I am ok with obvious exceptions like a non-native speaker using AI to help them articulate their point. Photos of Japan (talk) 21:29, 25 December 2024 (UTC)
Support for now. I believe the foundation should be busy ramping up support in this arena of distraction. IMHO, we are in the calibration phase of the use of these models. We don't feed trolls and we shouldn't tutor LLMs. Since assumption of good faith is not suicide pact, we shouldn't rely overmuch for guidance on edge cases. The issues as I see them are attribution (how do I know where your idea has been?), obedience to social norms (I not-here blocked someone recently for brazenly using ChatGPT to lie about using LLMs; the user proceeded to use GPT to post unblock requests), and a vast canyon between the limited human and financial resources of the foundation and the unlimited resources of bad actors with vast sums of money who would like to see Misplaced Pages less able. I have hopes we can get some higher visibility anti-LLM support (like a flag in my mouseover which always reports a percentage, so I know to check). This fire is burning now. It would be unwise to ignore this much longer. BusterD (talk) 16:28, 29 December 2024 (UTC)
Support with the clarification that use of AI assistance is not prohibited, as long as its contribution is <<50%. For example, using Grammarly for spell check and grammar/syntax is OK, but using AI to do your homework is not. Dhaluza (talk) 02:45, 30 December 2024 (UTC)
Support a ban on comments that were primarily generated by AI, with such comments to be deleted or struck-through as appropriate, because it's inherently misleading to pass off a chatbot's words as your own. Using ML-based spell-checkers is fine. I've seen some users call ChatGPT an "accessibility tool", but if you're not capable of communicating on English Misplaced Pages without a LLM doing it for you, then I don't think English Misplaced Pages is a good community for you to participate in. — Preceding unsigned comment added by Pythoncoder (talk • contribs) 21:45, 31 December 2024 (UTC)
Just read this ANI thread, where an editor was indeffed per WP:NOTHERE after exclusively using LLMs to edit, even when responding within that very thread. The situation was a clear case of WP:CIR, which I surely would've cited in my original comment had the page name come to mind. —pythoncoder (talk | contribs) 04:34, 3 January 2025 (UTC)
That they were banned for CIR shows we don't need anything new to deal with disruption specifically caused by people using LLMs. Thryduulf (talk) 05:29, 3 January 2025 (UTC)
Support A popular notion in many, many other discussions is "our most valuable resource is editor time". This applies here more than in most instances - editors cannot be expected to wear themselves out in engaging at length with the results of someone's one-line prompt to an LLM. Where LLM use in articles is destructive of content and source reliability, in discussions it is destructive of editor good faith. If you can't be bothered to put your arguments into intelligible form, don't participate. If your language capacity is lacking to the extent that you have to have a program generate (as opposed to polish) your stuff, you probably don't have any business participating either. Human detection ability seems quite sufficient for these cases (and once it ceases to, well, we'll deal with that when it becomes an issue). --Elmidae (talk · contribs) 12:00, 2 January 2025 (UTC)
Human detection ability seems quite sufficient for these case these discussions have already proven that human detection is not reliable, with human-generated comments labelled as AI and AI-generated comments labelled as human. Why should we prohibit LLM-generated content that is accurate, relevant and intelligible? We can already ignore/remove content that is none of those things regardless of whether it is LLM-generated or not. Thryduulf (talk) 12:21, 2 January 2025 (UTC)
If you want a pithy in-a-nutshell: personal effort is buy-in in a discussion among equals. If your personal effort in a discussion is an LLM prompt, no editor should be expected to engage with you. --Elmidae (talk · contribs) 12:42, 2 January 2025 (UTC)
What matters is whether people are engaging with each other constructively and in good faith. Whether one or both parties is using an LLM is completely irrelevant to both aspects. Thryduulf (talk) 13:29, 2 January 2025 (UTC)
Nobody is forcing you to engage with anybody or anything you don't want to engage with, but you do not get to state who other people are allowed to choose to engage with. As long as someone is engaging constructively and in good faith I don't care whether they are human or machine, because (a) I have no reliable way of knowing, and (b) it is literally irrelevant to me. Thryduulf (talk) 14:14, 2 January 2025 (UTC)
you do not get to state who other people are allowed to choose to engage with Strawman, since I didn't do that. Only you are doing that. Selfstudier (talk) 14:26, 2 January 2025 (UTC)
Quite the contrary - you are saying that nobody should be allowed to engage with someone using an LLM because you do not want to engage with someone using an LLM. My position is that everybody should be allowed to choose who they want and do not want to engage with for themselves. Thryduulf (talk) 14:42, 2 January 2025 (UTC)
Support in principle - Using entirely AI-generated text in discussion is not a valuable contribution, since ultimately it is not capable of thought, but there should be leniency for those who are simply using AI to improve something they already wrote. FOARP (talk) 14:55, 2 January 2025 (UTC)
Support in principle We don't want LLMs opinions. IF and WHEN we do we'll ask for an extension with some AI making an openig analysis of nominations. But we can not, and want not, to excludes cases where some user forms their opinion chating with some AI, as it was brillianttely shoen above, nor we want to exclude anyone lee proficient with the language just "because it looks like a bot". - Nabla (talk) 18:13, 2 January 2025 (UTC)
Support in principle, strongly concerned in potential practice - I like the idea of removing what is verifiably generated by a LLM. On the other hand, I've read that autistic writers may be more likely to have their (completely non-AI) writing flagged as potential AI use by automated detectors. I think it could be a problem if a rule that's good in principle could start disproportionately affecting some editors (who are not doing the thing) more than others (who are not doing the thing) in practice, whether that come from human (i.e. other editor) bias or automated tools. - Purplewowies (talk) 18:36, 3 January 2025 (UTC)
Strongly support per ChatGPT (EEng) and SMcC; I'm not at all concerned about edit accessibility to non-native speakers; WP:COMPETENCE, after all, is required to contribute to this project. I also oppose any breaking of the line against AI-generated plausible-sounding and -looking slop. We can't have a Misplaced Pages of LLMs talking to LLMs on how to make LLM content for LLM articles. Iseulttalk to me21:53, 4 January 2025 (UTC)
Support per SMcCandlish. If someone needs to use a LLM to be able to contribute and is unable to convert the output into something that is not obviously AI-generated, then WP:CIR likely applies. It'll be impossible to stop minimal usage cases, but having such a rule in place would at least encourage editors to review their output and stop the unhelpful posting off entire ChatGPT essays to discussion spaces. -- Patar knight - /contributions01:41, 6 January 2025 (UTC)
Strong... opinion -- I think the nuance required here in part is the difference between someone using any automated tool for assistance, versus true bot-like behavior. I believe that unauthorized bot behavior is already prohibited, which should help address the concerns that we mere humans cannot keep up with LLM bots. I agree, we cannot, but I don't see much of that. I am also not inclined to the "if you cannot write, you cannot contribute"... I can imagine 15 years ago some of us might have made the same statement about spelling and grammar; if you cannot spell properly without auto-correct you have no right to edit an encycolopedia. The are significant number of very intentilligent people who are afflicted with things like dyslexia, aspurgers, etc. who have been contributing using various technology tools for assistance. How may of us have Grammarly or similar running on their web browser? And beyond that tools and what they're called will continue to evolve. I am very much against just banning LLM use; largely because it can turn into an unnecessary witch hunt. There are people who will use the tools constructively, and those who will not. I can see some places where it should probably be banned (such as using a LLM to determine consensus on a discussion that needs closing (AfD, RM, etc)). But even in those areas, I think many of our existing policies and guidelines already address most of the actual concerns we're seeing when it comes to that activity. Cheifly that as long as people are being held accountable for how they use the tools, then who cares what the tool is called in 2000, 2020 or 2040? So I think the course forward is best served by (1) Consider refinement to WP:BOTP so that we're encapsulating LLM type bot behavior, as well as some sort of threshold on "non-human" capable editing limits (perhaps as part of WP:MEATBOT; (2) make a policy or guidelines very clear, bright line, that a user will be treated the same regardless of what tools they use, LLM or otherwise, and that disruptive editing will be handled accordingly. (2a) perhaps a single-warning template reflective of such, to welcome people who appear to be using LLM, and that they are responsible for their adherence to policy and that LLMs tend to get policy wrong. TiggerJay(talk)02:48, 7 January 2025 (UTC)
The proposal is focused on comments that are obviously generated by LLM, which would not include non-generative AI processes like Grammarly or translation. The whole issue is arguments that were clearly created by a chatbot etc. doing its own analysis of a discussion and an editor just pasting that output rather than forming the argument themselves, which results in large amounts of text that other editors/closers then have to read and respond to. JoelleJay (talk) 22:26, 7 January 2025 (UTC)
To be honest, that's my concern. What if something seems obviously generated by LLM but is entirely human-written? What if certain groups of editors are more likely to produce seemingly LLM text that isn't generated by any LLM at all? Is there a way to control for that? How do we consistently enforce this kind of thing without too many false positives or false negatives?
Replying to the top-level opinion at this point: Most autistic people who would have in the past received an Asperger's diagnosis, barring some other reason, would IMO not be more likely to "need" more assistive technology (LLM or otherwise) to contribute to Misplaced Pages articles and discussions than any other user. However, there have been reports that autistic people may be more likely to produce text that is falsely positive in AI detection tools. See this story about a Purdue professor as one example (I had a second example, I thought, except that I've apparently read my last free article on that site (I bet I read said last article when looking up the same article when I wrote my !vote a few days back, Facepalm). Not gonna link what I can't (quickly) verify!)) (As an aside, I think "afflicted with" can come across as a bit... charged? Just something to note.)
The mention of Data in particular only heightens my concern because--while no one has accused me yet of using LLM when I write--I have (on other sites, not here) been accused of being a bot before because of the style of writing I adopt at times. What if editor bias disproportionately plays into who is suspected of LLM use and who isn't? What if imperfections in automated AI detection only serve to cement the bias? - Purplewowies (talk) 01:25, 8 January 2025 (UTC)
These questions around controlling for false positives and false negatives are not new, we face them all the time already, for example distinguishing vandalism from good faith contributions. We work through them, but they don't mean we don't have a policy on vandalism. CMD (talk) 01:41, 8 January 2025 (UTC)
Indeed, that's why my original !vote is (in short) "support but concerned". I definitely think I'd support a policy; I'm just raising questions/concerns I think are worth considering in the process of creating such a policy. I think some part of me is just remembering times I've seen bias negatively affect the project in the past and that part of me is coming out here trying to prevent another situation like that by laying the concerns out. I dunno. - Purplewowies (talk) 03:59, 8 January 2025 (UTC)
I think Joelle what you're overlooking in that statement is that obviously generated is something that is going to be short lived, meaning that it will not be very long before the LLM generated content will be far harder to distinguish. Just like how just a year ago any generative image AI would often get the number and/or placement of fingers wrong on a person's hand, in less than a years time that appears to generally be solved. Today the tell tail signs is even if you ask for someone who is left handed, you'll almost always get an image of a right handed person... But that too will go away shortly. I believe it is (scarily) not too far off, when LLMs can determine the prompt is for Misplaced Pages (by way of seeing the wikimarkup or references to normal wiki policies), and among other things, write in the style of experienced editors, perhaps modeled off of some of us in this very discussion. That will be much more difficult to tell, especially when it learns how to not be soo overly polite and apologetic. Beyond that, I believe there are a lot of people successfully and positively using LLMs already on WP. For those reasons, I proffer that we focus on refining the definitions and parameters for general disruptive editing (such as EW, RRR, etc), what a bot edit/activity is, and perhaps a standardized "friendly welcome" and "friendly notice" for those suspected of using LLMs, and reinforce that the tool matters less than the behavior. I think the analogy I'm going for is that of how we handle socks -- it is not against policy to have multiple accounts, however, when it is disruptive, it is blatantly prohibited. But the signs and symptoms of socks is really what we care about. TiggerJay(talk)05:02, 8 January 2025 (UTC)
Something can be prohibited even if it is or will be difficult to identify it. Just because we can anticipate AI-generated slop becoming harder to detect doesn't mean it's not still disruptive or that we shouldn't be able to strike it when it is obvious. JoelleJay (talk) 23:41, 9 January 2025 (UTC)
Strong support for striking AI-generated comments. Detection of course will be up to admin discretion, but so is things like incivility and personal attacks; while short snippets of AI generated text are hard to detect, lengthy paragraphs are quite easy to eyeball, and from my experience that's the area where it's most likely to come up and most immediately disruptive. Generalissima (talk) (it/she) 22:25, 9 January 2025 (UTC)
Supportfor striking AI-generated comments. Detection of course will be up to admin discretion as are other behavioural preoblems. Having read most of the discussion, and having been astonished by the 'individuality' of some machine-generated content, nonetheless, while detection may be less-than-foolproof, I still think we should make the point that such content isn't acceptable. It should be within our capacity to make the distinction between 'machine-generated' content and the use of software to correct grammar or to translate, neither of which should be directly outlawed.Pincrete (talk) 07:18, 10 January 2025 (UTC)
But why should such content be deemed unacceptbale when there are no problems with it? When there are problems with it, it can and should be dealt with in the same way that those problems are dealt with when written by humans. Thryduulf (talk) 18:25, 10 January 2025 (UTC)
Request for closure
IMHO, since we're over 30 days and the argument consensus seems lopsided, the community would do well to close this rapidly (as opposed to waiting for additional comments). BusterD (talk) 21:04, 2 January 2025 (UTC)
Sure it looks lopsided if you only read what has been bolded. When you look beyond at what those bolding support are actually supporting it's not at all clear there is a consensus. Then when you actually look at the arguments made it seems that there is not actually a consensus for anything other more than "some users vocally dislike AI". Thryduulf (talk) 21:59, 2 January 2025 (UTC)
I was merely pointing out that BusterD's stated reason for calling for closure now is incorrect. That doesn't mean closing now would necessarily be wrong, just that overwhelming consensus is not a reason for it. Thryduulf (talk) 22:25, 2 January 2025 (UTC)
As a sysop, reacting to LLM-related abuse is virtually all I've done in the last week or so. We have a pressing need for some help from the community, and while I'm open to discussion on this, it's unreasonable to expect humans to keep up with bot-like behavior. I've made my argument above, and I'll not disagree further here. BusterD (talk) 00:08, 3 January 2025 (UTC)
Many on the “support” side are also supporting with conditions instead of an unconditional support. For instance, many have suggested that LLM that supported grammars are okay.
There are multiple breaks and 391 comments now. At this scale, it becomes difficult for a human to digest and summarise it all. AI technology seems well suited to this and so asked Gemini again "Please summarise the consensus of the following RFC:" giving it all the discussion above. Its response was much as before:
The RFC on LLM/chatbot comments in discussions is contentious, with a significant number of editors on both sides of the issue.
Support
Many editors support the proposal to discount or remove LLM-generated comments in discussions. Their arguments include:
LLMs do not have original thoughts or arguments and therefore do not contribute meaningfully to discussions.
LLM-generated comments can be disruptive, wasting editors' time and derailing discussions.
LLMs can be used by bad-faith actors to manipulate consensus or spread misinformation.
Editors should be encouraged to participate in discussions using their own words and thoughts.
Oppose
Other editors oppose the proposal, arguing that:
LLMs can be useful tools for editors who have difficulty expressing themselves in English, such as non-native speakers or those with disabilities.
LLM-generated comments should be evaluated on their merits, not their origin.
Detection of LLM-generated comments is unreliable and could lead to false positives.
A ban on LLM-generated comments could discourage participation from editors who rely on these tools.
Additional points
There is disagreement about whether machine translation should be considered LLM-generated content.
Some editors believe that LLMs could be used constructively in discussions, for example, to summarize arguments or provide alternative perspectives.
Others are concerned about the potential for LLMs to be used maliciously, for example, to flood discussions with irrelevant comments or to impersonate other editors.
Overall
There is no clear consensus on whether to ban or allow LLM-generated comments in discussions. The discussion highlights the challenges of balancing the potential benefits and risks of using LLMs in a collaborative environment like Misplaced Pages.
That was a good answer but I wanted to get a rough headcount and so asked a supplementary question, "What was the count of the number of support and opposing votes in the discussion?" The answer was:
Unfortunately, a precise count of support vs oppose votes in that discussion is difficult to determine definitively for a few reasons:
Some votes are unclear: Several editors express nuanced positions or change their vote during the discussion.
"Strong" votes aren't quantified: While many editors use "Strong support" or "Strong oppose", these don't carry extra weight in a simple tally.
Focus shifts: The initial focus on AI-generated comments broadens to include AI-assistance, making some votes less clear-cut.
However, based on a rough manual count:
Support: Around 60-70 votes clearly favor discounting or removing AI-generated comments.
Oppose: Roughly 30-40 votes lean against the proposal, with varying degrees of opposition.
Important Note: This is an approximation. The actual consensus in such discussions is determined by the closer, who weighs the arguments' quality and policy relevance, not just the number of votes.
This seems to be another good answer – better than we get from most human closes. I made a rough manual count to confirm that the numbers given are reasonable ballpark figures. And it seems to have an impressive grasp of nuance – noticing that several editors were qualifying their votes as strong/weak and that some editors changed their vote. Andrew🐉(talk) 22:02, 10 January 2025 (UTC)
These feel (from my memory of when I skimmed over the discussion several days ago before my original !vote/comment) like they might be leaving out some relevant points that came up. (Unfortunately I can't quantify that without taking a look which I don't have time to do right now (other than the fact my own concerns didn't make it into the summary, which... fair, I guess, considering I was the only one who raised that specific issue).) (I'm also very surprised it came up with something coherent as well as on topic, but that just has more to do with the fact Gemini (or at least whatever AI summarizes Google searches) told me extremely recently that I could get to Alaska by car without a passport if I drove through the ocean. Not took a ferry but drove... through the water... in a car.) - Purplewowies (talk) 07:02, 11 January 2025 (UTC)
Your !vote was a qualified support with concern about false positives affecting editors such as the autistic. That's then a nuanced, both-ways vote and the Gemini summary seems to capture that reasonably well. Andrew🐉(talk) 09:43, 11 January 2025 (UTC)
My vote was mentioned purely because it was the only specific thing I could bring to mind quickly that hadn't ended up in the AI summary. I think Thryduulf's take about what it doesn't make clear more closely matches what I think I was actually feeling about the summary (that it doesn't make clear the wide breadth of what the support !votes are actually saying). - Purplewowies (talk) 19:08, 11 January 2025 (UTC)
On the whole that summary matches my impression of discussion, with the exception that it doesn't make it clear that not everyone expressing support is supporting the same thing. Thryduulf (talk) 14:38, 11 January 2025 (UTC)
I have strong doubts that Gemini is able to discern support or opposition even in individual !votes, let alone assess one participant's opinion across multiple comments or the relative preponderance of a given opinion across different participants. I fed it just the material before section break 1, then asked it to list the editors who oppose banning AI-generated comments. Here was its response:
Based on the discussion, the following editors oppose banning AI-generated comments or express concerns about the feasibility of such a ban:
Just Step Sideways: Argues against dismissing arguments based on the author rather than their content. Remsense: Believes the downsides of such a policy outweigh the benefits. Chipmunkdavis: Supports admin discretion and emphasizes the difficulty of creating a policy around rapidly evolving AI technology. Jlwoodwa: Acknowledges that not all AI-generated comments are useless and suggests a case-by-case approach. Aaron Liu: Is skeptical about the long-term feasibility of reliably distinguishing between human and AI-generated text. Sean.hoyland: Expresses skepticism about the enforceability of such a rule due to the rapid advancements in AI technology. Gnomingstuff: Strongly opposes a ban, citing the difficulty of enforcement, potential for false positives, and the impact on non-native English speakers. Randy Kryn: Expresses concerns about potentially discouraging the use of AI tools for improving the clarity of writing by non-native English speakers. Selfstudier: Acknowledges the principle of discounting AI-generated comments but questions the reliability of identifying them.
Somehow I don't think that is how a closer would interpret the !votes from @Just Step Sideways, @Remsense, @Chipmunkdavis, @Jlwoodwa, or @Randy Kryn... Note that it also did not manage to identify Thryduulf as an opposer until I asked who supported striking AI-generated comments:
Based on the discussion, the following editors support striking AI-generated comments:
Thryduulf: Initially supported discounting or ignoring AI-generated comments, but later withdrew support due to potential downsides. Chipmunkdavis: Initially expressed support for admin discretion, but later shifted to more explicit support for guidance to closers and evaluators. Bluethricecreamman: Strongly supports striking out AI-generated content, especially if it appears insincere or disruptive. Isaacl: Supports striking out AI-generated content and favors sanctions for users who overuse AI to write arguments. Clayoquot: Supports striking out AI-generated comments, comparing them to comments from suspected sock puppets. Lazman321: Strongly supports striking out AI-generated comments, considering them as "pure laziness" and a waste of other editors' time. Seraphimblade: Supports striking out AI-generated comments as they may not reflect the actual thoughts of the editor.
When I re-fed it the same discussion, it modified its response thusly:
Based on the additional excerpt of the discussion, the following editors support striking or collapsing AI-generated comments:
Jlwoodwa: Supports discounting or collapsing AI-generated comments, finding them disruptive if used to present arguments in an unnecessarily verbose manner. Gnomingstuff: Opposes a hard ban, but acknowledges that AI-generated comments can be pointless and disruptive. Seraphimblade: Reiterates support for striking AI-generated comments as they may not reflect the editor's thoughts. It's important to note that:
Gnomingstuff also raises concerns about the difficulty of enforcing such a policy and potential unintended consequences, like discouraging users from using translation tools. Aaron Liu's test using GPTZero on a human-written comment by Gnomingstuff indicated a 99% probability that it was human-written, suggesting that these tools may not be reliable.
The last bullet point makes zero sense... It didn't even identify me as supporting the proposal until I specifically asked what it thought my position was.No fucking way should we trust AI's assessment of any kind of consensus for any discussion. JoelleJay (talk) 23:02, 11 January 2025 (UTC)
Perhaps it's better at summarising in a broad-brush way than parsing individual votes. But to clarify the technical details, please say which version of Gemini you used as there seem to be at least five currently. My test was done using Advanced Gemini 1.5 Pro. I've also tried the Deep Research option but am not quite sure when that kicks in. Andrew🐉(talk) 09:57, 12 January 2025 (UTC)
But broad-brush summaries are not what we want when the intent is to determine consensus among editors, since the AI is clearly not identifying positions accurately and doesn't seem to distinguish between one argument made multiple times by the same person vs by multiple different people. I used Gemini 1.5. JoelleJay (talk) 19:04, 12 January 2025 (UTC)
Ok, what point is there to having AI summarize consensus? Consensus should be based on the strength of individual arguments, which only an experienced human editor can assess; AI can only guess what arguments look like. It's especially weird to use it here since if, theoretically, the AI summary decides there is consensus against considering AI comments in Misplaced Pages discussions, then that would include AI summary itself, leading to Russell's paradox. Lazman321 (talk) 19:41, 11 January 2025 (UTC)
One point is that AI may be better at summarising huge, sprawling discussions like this one. That's because it may have more patience and ability to handle large masses of data. Humans will tend to suffer from TLDR, MEGO and issues like confirmation bias and other barriers to critical thinking.
Also, "beggars can't be choosers". The OP called for a close 10 days ago but no human has rushed to perform this thankless task. Discussions on Misplaced Pages are often left dangling without a clear conclusion and there many other big backlogs.
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
Whereas many editors, including me, have cited problems with accuracy in regards to existing tools such as ZeroGPT, I propose that remarks that are blatently generated by a LLM or similar automated system should be discounted/removed/collapsed/hidden. ThatIPEditor10:00, 10 December 2024 (UTC)
Oppose as completely unnecessary and far too prone to error per the above discussion. Any comment that is good (on topic, relevant, etc) should be considered by the closer regardless of whether it was made with LLM-input of any sort or not. Any comment that is bad (off-topic, irrelevant, etc) should be ignored by the closer regardless of whether it was made with LLM-input of any sort or not. Any comment that is both bad and disruptive (e.g. by being excessively long, completely irrelevant, bludgeoning, etc) should be removed and/or hatted as appropriate, regardless of whether it was made with LLM-input of any sort. The good thing is that this is already policy so we don't need to call out LLMs specifically, and indeed doing so is likely to be disruptive in cases where human-written comments are misidentified as being LLM-written (which will happen, regardless of whether tools are used). Thryduulf (talk) 11:19, 10 December 2024 (UTC)
I think this proposal is not really necessary. I support it, but that is because it is functionally identical to the one directly above it, which I also supported. This should probably be hatted. BugGhost🦗👻18:32, 10 December 2024 (UTC)
What does blatantly generated mean? Does you mean only where the remark is signed with "I, Chatbot", or anything that appears to be LLM-style? I don't think there's much in between. ypn^219:21, 10 December 2024 (UTC)
Procedural close per BugGhost. I'd hat this myself, but I don't think that'd be appropriate since it's only the two of us who have expressed that this proposal is basically an exact clone. Aaron Liu (talk) 03:00, 11 December 2024 (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.
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.
@Tamzin: Did you find there was consensus support for handling obvious use of comments through any form of generative AI, regardless of the specific underlying technology (thus not only for large language models)? isaacl (talk) 23:45, 12 January 2025 (UTC)
I've added "or similar AI technologies" to clarify. I don't think there was enough discussion of technical aspects of AI to be more precise than that. -- Tamzin (they|xe|🤷) 00:43, 13 January 2025 (UTC)
My general impression is that most commenters were using the term "LLM" generically, rather than referring to a specific technology. isaacl (talk) 04:28, 13 January 2025 (UTC)
RfC: Voluntary RfA after resignation
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
There is clear consensus that participants in this discussion wish to retain the "Option 2" status quo. We're past 30 days of discussion and there's not much traffic on the discussion now. It's unlikely the consensus would suddenly shift with additional discussion. --Hammersoft (talk) 18:29, 16 January 2025 (UTC)
Option 1 – Require former administrators to request restoration of their tools at the bureaucrats' noticeboard (BN) if they are eligible to do so (i.e., they do not fit into any of the exceptions).
Option 2 – Clarify Maintain the status quo that former administrators who would be eligible to request restoration via BN may instead request restoration of their tools via a voluntary request for adminship (RfA).
Option 3 – Allow bureaucrats to SNOW-close RfAs as successful if (a) 48 hours have passed, (b) the editor has right of resysop, and (c) a SNOW close is warranted.
2, after thought. I don't think 3 provides much benefit, and creating separate class of RfAs that are speedy passed feels a misstep. If there are serious issues surrounding wasting time on RfAs set up under what might feel to someone like misleading pretenses, that is best solved by putting some indicator next to their RFA candidate name. Maybe "Hog Farm (RRfA)". CMD (talk) 14:49, 16 December 2024 (UTC)
best solved by putting some indicator next to their RFA candidate name. Maybe "Hog Farm (RRfA)" - I like this idea, if option 2 comes out as consensus I think this small change would be a step in the right direction, as the "this isn't the best use of time" crowd (myself included) would be able to quickly identify the type of RFAs they don't want to participate in. BugGhost🦗👻11:05, 17 December 2024 (UTC)
I think that's a great idea. I would support adding some text encouraging people who are considering seeking reconfirmation to add (RRfA) or (reconfirmation) after their username in the RfA page title. That way people who are averse to reading or participating in reconfirmations can easily avoid them, and no one is confused about what is going on. 28bytes (talk) 14:23, 17 December 2024 (UTC)
If we are differentiating three types of RFA we need three terms. Post-recall RFAs are referred to as "reconfirmation RFAs", "Re-RFAS" or "RRFAs" in multiple places, so ones of the type being discussed here are the ones that should take the new term. "Voluntary reconfirmation RFA" (VRRFA or just VRFA) is the only thing that comes to mind but others will probably have better ideas. Thryduulf (talk) 21:00, 17 December 2024 (UTC)
2 I don't see why people trying to do the right thing should be discouraged from doing so. If others feel it is a waste of time, they are free to simply not participate. El Beeblerino21:27, 15 December 2024 (UTC)
Of course they may request at RfA. They shouldn't but they may. This RfA feels like it does nothing to address the criticism actually in play and per the link to the idea lab discussion it's premature to boot. Barkeep49 (talk) 21:38, 15 December 2024 (UTC)
2 per my comments at the idea lab discussion and Queent of Hears, Beeblebrox and Scazjmd above. I strongly disagree with Barkeep's comment that "They shouldn't ". It shouldn't be made mandatory, but it should be encouraged where the time since desysop and/or the last RFA has been lengthy. Thryduulf (talk) 21:42, 15 December 2024 (UTC)
When to encourage it would be a worthwhile RfC and such a discussion could be had at the idea lab before launching an RfC. Best, Barkeep49 (talk) 21:44, 15 December 2024 (UTC)
1 or 3. RFA is an "expensive" process in terms of community time. RFAs that qualify should be fast-tracked via the BN process. It is only recently that a trend has emerged that folks that don't need to RFA are RFAing again. 2 in the last 6 months. If this continues to scale up, it is going to take up a lot of community time, and create noise in the various RFA statistics and RFA notification systems (for example, watchlist notices and User:Enterprisey/rfa-count-toolbar.js). –Novem Linguae (talk) 21:44, 15 December 2024 (UTC)
Making statistics "noisy" is just a reason to improve the way the statistics are gathered. In this case collecting statistics for reconfirmation RFAs separately from other RFAs would seem to be both very simple and very effective. If (and it is a very big if) the number of reconfirmation RFAs means that notifications are getting overloaded, then we can discuss whether reconfirmation RFAs should be notified differently. As far as differentiating them, that is also trivially simple - just add a parameter to template:RFA (perhaps "reconfirmation=y") that outputs something that bots and scripts can check for. Thryduulf (talk) 22:11, 15 December 2024 (UTC)
I'm weakly opposed to option 3, editors who want feedback and a renewed mandate from the community should be entitled to it. If they felt that that a quick endorsement was all that was required then could have had that at BN, they explicitly chose not to go that route. Nobody is required to participate in an RFA, so if it is going the way you think it should, or you don't have an opinion, then just don't participate and your time has not been wasted. Thryduulf (talk) 22:20, 15 December 2024 (UTC)
Added option 3 above. Maybe worth considering as a happy medium, where unsure admins can get a check on their conduct without taking up too much time. theleekycauldron (talk • she/her) 22:11, 15 December 2024 (UTC)
2 – If a former admin wishes to subject themselves to RfA to be sure they have the requisite community confidence to regain the tools, why should we stop them? Any editor who feels the process is a waste of time is free to ignore any such RfAs. — Jkudlick ⚓ (talk)22:12, 15 December 2024 (UTC)
I would also support option 3 if the time is extended to 72 hours instead of 48. That, however, is a detail that can be worked out after this RfC. — Jkudlick ⚓ (talk)02:05, 16 December 2024 (UTC)
A further note: option 3 gives 'crats the discretion to SNOW close a successful voluntary re-RfA; it doesn't require such a SNOW close, and I trust the 'crats to keep an RfA open if an admin has a good reason for doing so. voorts (talk/contributions) 23:24, 16 December 2024 (UTC)
Option 2 (no change) – The sample size is far too small for us to analyze the impact of such a change, but I believe RfA should always be available. Now that WP:RECALL is policy, returning administrators may worry that they have become out of touch with community norms and may face a recall as soon as they get their tools back at BN. Having this familiar community touchpoint as an option makes a ton of sense, and would be far less disruptive / demoralizing than a potential recall. Taking this route away, even if it remains rarely used, would be detrimental to our desire for increased administrator accountability. – bradv22:22, 15 December 2024 (UTC)
2, distant second preference 3. I would probably support 3 as first pick if not for recall's rule regarding last RfA, but as it stands, SNOW-closing a discussion that makes someone immune to recall for a year is a non-starter. Between 1 and 2, though, the only argument for 1 seems to be that it avoids a waste of time, for which there is the much simpler solution of not participating and instead doing something else. Special:Random and Misplaced Pages:Backlog are always there. -- Tamzin (they|xe|🤷) 23:31, 15 December 2024 (UTC)
Option 1. No second preference between 2 or 3. As long as a former administrator didn't resign under a cloud, picking up the tools again should be low friction and low effort for the entire community. If there are issues introduced by the recall process, they should be fixed in the recall policy itself. Daniel Quinlan (talk) 01:19, 16 December 2024 (UTC)
Option 2, i.e. leave well enough alone. There is really not a problem here that needs fixing. If someone doesn’t want to “waste their time” participating in an RfA that’s not required by policy, they can always, well, not participate in the RfA. No one is required to participate in someone else’s RfA, and I struggle to see the point of participating but then complaining about “having to” participate. 28bytes (talk) 01:24, 16 December 2024 (UTC)
Option 3: Because it is incredibly silly to have situations like we do now of "this guy did something wrong by doing an RfA that policy explicitly allows, oh well, nothing to do but sit on our hands and dissect the process across three venues and counting." Your time is your own. No one is forcibly stealing it from you. At the same time it is equally silly to let the process drag on, for reasons explained in WP:SNOW. Gnomingstuff (talk) 03:42, 16 December 2024 (UTC)
Option 3 per Gnoming. I think 2 works, but it is a very long process and for someone to renew their tools, it feels like an unnecessarily long process compared to a normal RfA. Conyo14 (talk) 04:25, 16 December 2024 (UTC)
As someone who supported both WormTT and Hog Farm's RfAs, option 1 > option 3 >> option 2. At each individual RfA the question is whether or not a specific editor should be an admin, and in both cases I felt that the answer was clearly "yes". However, I agree that RfA is a very intensive process. It requires a lot of time from the community, as others have argued better than I can. I prefer option 1 to option 3 because the existence of the procedure in option 3 implies that it is a good thing to go through 48 hours of RfA to re-request the mop. But anything which saves community time is a good thing. HouseBlaster (talk • he/they) 04:31, 16 December 2024 (UTC)
I've seen this assertion made multiple times now that requires a lot of time from the community, yet nowhere has anybody articulated how why this is true. What time is required, given that nobody is required to participate and everybody who does choose to participate can spend as much or as little time assessing the candidate as they wish? How and why does a reconfirmation RFA require any more time from editors (individually or collectively) than a request at BN? Thryduulf (talk) 04:58, 16 December 2024 (UTC)
I think there are a number of factors and people are summing it up as "time-wasting" or similar:
BN Is designed for this exact scenario. It's also clearly a less contentious process.
Snow closures a good example of how we try to avoid wasting community time on unnecessary process and the same reasoning applies here. Misplaced Pages is not a bureaucracy and there's no reason to have a 7-day process when the outcome is a given.
If former administrators continue to choose re-RFAs over BN, it could set a problematic precedent where future re-adminship candidates feel pressured to go through an RFA and all that entails. I don't want to discourage people already vetted by the community from rejoining the ranks.
The RFA process is designed to be a thoughtful review of prospective administrators and I'm concerned these kinds of perfunctory RFAs will lead to people taking the process less seriously in the future.
Because several thousand people have RFA on their watchlist, and thousands more will see the "there's an open RFA" notice on theirs whether they follow it or not. Unlike BN, RFA is a process that depends on community input from a large number of people. In order to even realise that the RFA is not worth their time, they have to:
Read the opening statement and first few question answers (I just counted, HF's opening and first 5 answers are about 1000 words)
Think, "oh, they're an an ex-admin, I wonder why they're going through RFA, what was their cloud"
Read through the comments and votes to see if any issues have been brought up (another ~1000 words)
None have
Realise your input is not necessary and this could have been done at BN
That they were former admins has always been the first two sentences of their RfA’s statement, sentences which are immediately followed by that they resigned due to personal time commitment issues. You do not have to read the first 1000+ words to figure that out. If the reader wants to see if the candidate was lying in their statement, then they just have a quick skim through the oppose section. None of this should take more than 30 seconds in total. Aaron Liu (talk) 13:15, 16 December 2024 (UTC)
Not everyone can skim things easily - it personally takes me a while to read sections. I don't know if they're going to bury the lede and say something like "Also I made 10,000 insane redirects and then decided to take a break just before arbcom launched a case" in paragraph 6. Hog Farm's self nom had two paragraphs about disputes and it takes more than 30 seconds to unpick that and determine if that is a "cloud" or not. Even for reconfirmations, it definitely takes more than 30 seconds to determine a conclusion. BugGhost🦗👻11:21, 17 December 2024 (UTC)
They said they resigned to personal time commitments. That is directly saying they wasn’t under a cloud, so I’ll believe them unless someone claims the contrary in the oppose section. If the disputes section contained a cloud, the oppose section would have said so. One chooses to examine such nominations like normal RfAs. Aaron Liu (talk) 18:47, 17 December 2024 (UTC)
Just to double check, you're saying that whenever you go onto an RFA you expect any reason to oppose to already be listed by someone else, and no thought is required? I am begining to see how you are able to assess an RFA in under 30 seconds BugGhost🦗👻23:08, 17 December 2024 (UTC)
Something in their statement would be an incredibly obvious reason. We are talking about the assessment whether to examine and whether the candidate could've used BN. Aaron Liu (talk) 12:52, 18 December 2024 (UTC)
@Thryduulf let's not confuse "a lot of community time is spent" with "waste of time". Some people have characterized the re-RFAs as a waste of time but that's not the assertion I (and I think a majority of the skeptics) have been making. All RfAs use a lot of community time as hundreds of voters evaluate the candidate. They then choose to support, oppose, be neutral, or not vote at all. While editor time is not perfectly fixed - editors may choose to spend less time on non-Misplaced Pages activities at certain times - neither is it a resource we have in abundance anymore relative to our project. And so I think we, as a community, need to be thought about how we're using that time especially when the use of that time would have been spent on other wiki activities.Best, Barkeep49 (talk) 22:49, 16 December 2024 (UTC)
Absolutely nothing compels anybody to spend any time evaluating an RFA. If you think your wiki time is better spent elsewhere than evaluating an RFA candidate, then spend it elsewhere. That way only those who do think it is a good use of their time will participate and everybody wins. You win by not spending your time on something that you don't think is worth it, those who do participate don't have their time wasted by having to read comments (that contradict explicit policy) about how the RFA is a waste of time. Personally I regard evaluating whether a long-time admin still has the approval of the community to be a very good use of community time, you are free to disagree, but please don't waste my time by forcing me to read comments about how you think I'm wasting my time. Thryduulf (talk) 23:39, 16 December 2024 (UTC)
I don't understand how your argument that it is not a good use of community time is any different from arguing that it is a waste of time? Thryduulf (talk) 09:08, 17 December 2024 (UTC)
Option 2 I don't mind the re-RFAs, but I'd appreciate if we encouraged restoration via BN instead, I just object to making it mandatory. EggRoll9706:23, 16 December 2024 (UTC)
Option 2. Banning voluntary re-RfAs would be a step in the wrong direction on admin accountability. Same with SNOW closing. There is no more "wasting of community time" if we let the RfA run for the full seven days, but allowing someone to dig up a scandal on the seventh day is an important part of the RfA process. The only valid criticism I've heard is that folks who do this are arrogant, but banning arrogance, while noble, seems highly impractical. Toadspike07:24, 16 December 2024 (UTC)
Option 3, 1, then 2, per HouseBlaster. Also agree with Daniel Quinlan. I think these sorts of RFA's should only be done in exceptional circumstances. Graham87 (talk) 08:46, 16 December 2024 (UTC)
Option 1 as first preference, option 3 second. RFAs use up a lot of time - hundreds of editors will read the RFA and it takes time to come to a conclusion. When that conclusion is "well that was pointless, my input wasn't needed", it is not a good system. I think transparency and accountability is a very good thing, and we need more of it for resyssopings, but that should come from improving the normal process (BN) rather than using a different one (RFA). My ideas for improving the BN route to make it more transparent and better at getting community input is outlined over on the idea labBugGhost🦗👻08:59, 16 December 2024 (UTC)
Option 2, though I'd be for option 3 too. I'm all for administrators who feel like they want/should go through an RfA to solicit feedback even if they've been given the tools back already. I see multiple people talk about going through BN, but if I had to hazard a guess, it's way less watched than RfA is. However I do feel like watchlist notifications should say something to the effect of "A request for re-adminship feedback is open for discussion" so that people that don't like these could ignore them. ♠JCW555(talk)♠ 09:13, 16 December 2024 (UTC)
Option 2 because WP:ADMINISTRATORS is well-established policy. Read WP:ADMINISTRATORS#Restoration of admin tools, which says quite clearly, Regardless of the process by which the admin tools are removed, any editor is free to re-request the tools through the requests for adminship process. I went back 500 edits to 2017 and the wording was substantially the same back then. So, I simply do not understand why various editors are berating former administrators to the point of accusing them of wasting time and being arrogant for choosing to go through a process which is specifically permitted by policy. It is bewildering to me. Cullen328 (talk) 09:56, 16 December 2024 (UTC)
Option 2 & 3 I think that there still should be the choice between BN and re-RFA for resysops, but I think that the re-RFA should stay like it is in Option 3, unless it is controversial, at which point it could be extended to the full RFA period. I feel like this would be the best compromise between not "wasting" community time (which I believe is a very overstated, yet understandable, point) and ensuring that the process is based on broad consensus and that our "representatives" are still supported. If I were WTT or Hog, I might choose to make the same decision so as to be respectful of the possibility of changing consensus. JuxtaposedJacob (talk) | :) | he/him | 10:45, 16 December 2024 (UTC)
Option 2, for lack of a better choice. Banning re-RFAs is not a great idea, and we should not SNOW close a discussion that would give someone immunity from a certain degree of accountability. I've dropped an idea for an option 4 in the discussion section below. Giraffer (talk) 12:08, 16 December 2024 (UTC)
Option 1 I agree with Graham87 that these sorts of RFAs should only be done in exceptional circumstances, and BN is the best place to ask for tools back. – DreamRimmer (talk) 12:11, 16 December 2024 (UTC)
Option 2 I don't think prohibition makes sense. It also has weird side effects. eg: some admins' voluntary recall policies may now be completely void, because they would be unable to follow them even if they wanted to, because policy prohibits them from doing a RFA. (maybe if they're also 'under a cloud' it'd fit into exemptions, but if an admins' policy is "3 editors on this named list tell me I'm unfit, I resign" then this isn't really a cloud.) Personally, I think Hog Farm's RFA was unwise, as he's textbook uncontroversial. Worm's was a decent RFA; he's also textbook uncontroversial but it happened at a good time. But any editor participating in these discussions to give the "support" does so using their own time. Everyone who feels their time is wasted can choose to ignore the discussion, and instead it'll pass as 10-0-0 instead of 198-2-4. It just doesn't make sense to prohibit someone from seeking a community discussion, though. For almost anything, really. ProcrastinatingReader (talk) 12:33, 16 December 2024 (UTC)
Option 2 It takes like two seconds to support or ignore an RFA you think is "useless"... can't understand the hullabaloo around them. I stand by what I said on WTT's re-RFA regarding RFAs being about evaluating trustworthiness and accountability. Trustworthy people don't skip the process. —k6ka 🍁 (Talk · Contributions) 15:24, 16 December 2024 (UTC)
2 is fine. Strong oppose to 1 and 3. Opposing option 1 because there is nothing wrong with asking for extra community feedback. opposing option 3 because once an RfA has been started, it should follow the standard rules. Note that RfAs are extremely rare and non-contentious RfAs require very little community time (unlike this RfC which seems a waste of community time, but there we are). —Kusma (talk) 16:59, 16 December 2024 (UTC)
2, with no opposition to 3. I see nothing wrong with a former administrator getting re-confirmed by the community, and community vetting seems like a good thing overall. If people think it's a waste of time, then just ignore the RfA. Natg 19 (talk) 17:56, 16 December 2024 (UTC)
No individual is wasting their time participating. Instead the person asking for a re-rfa is using tons of editor time by asking hundreds of people to vet them. Even the choice not to participate requires at least some time to figure out that this is not a new RfA; though at least in the two we've had recently it would require only as long as it takes to get to the RfA - for many a click from the watchlist and then another click into the rfa page - and to read the first couple of sentences of the self-nomination which isn't terribly long all things considered. Best, Barkeep49 (talk) 22:55, 16 December 2024 (UTC)
I agree with you (I think) that it's a matter of perspective. For me, clicking the RFA link in my watchlist and reading the first paragraph of Hog Farm's nomination (where they explained that they were already a respected admin) took me about 10 seconds. Ten seconds is nothing; in my opinion, this is just a nonissue. But then again, I'm not an admin, checkuser, or an oversighter. Maybe the time to read such a nomination is really wasting their time. I don't know. TheWikiToby (talk) 23:15, 16 December 2024 (UTC)
I'm an admin and an oversighter (but not a checkuser). None of my time was wasted by either WTT or Hog Farm's nominations. Thryduulf (talk) 23:30, 16 December 2024 (UTC)
2. This reminds me of banning plastic straws (bear with me). Sure, I suppose in theory, that this is a burden on the community's time (just as straws do end up in landfills/the ocean). However, the amount of community time that is drained is minuscule compared to the amount of community time drained in countless, countless other fora and processes (just like the volume of plastic waste contributed by plastic straws is less than 0.001% of the total plastic waste). When WP becomes an efficient, well oiled machine, then maybe we can talk about saving community time by banning re-RFA's. But this is much ado about nothing, and indeed this plan to save people from themselves, and not allow them to simply decide whether to participate or not, is arguably more damaging than some re-RFAs (just as banning straws convinced some people that "these save-the-planet people are so ridiculous that I'm not going to bother listening to them about anything."). And, in fact, on a separate note, I'd actually love it if more admins just ran a re-RFA whenever they wanted. They would certainly get better feedback than just posting "What do my talk page watchers think?" on their own talk page. Or waiting until they get yelled at on their talk page, AN/ANI, AARV, etc. We say we want admins to respect feedback; does it have to be in a recall petition? --Floquenbeam (talk) 23:44, 16 December 2024 (UTC)
What meaningful feedback has Hog Farm gotten? "A minority of people think you choose poorly in choosing this process to regain adminship". What are they supposed to do with that? I share your desire for editors to share meaningful feedback with administrators. My own attempt yielded some, though mainly offwiki where I was told I was both too cautious and too impetuous (and despite the seeming contradiction each was valuable in its own way). So yes let's find ways to get meaningful feedback to admins outside of recall or being dragged to ANI. Unfortunately re-RfA seems to be poorly suited to the task and so we can likely find a better way. Best, Barkeep49 (talk) 03:38, 17 December 2024 (UTC)
No hard rule, but we should socially discourage confirmation RfAs There is a difference between a hard rule, and a soft social rule. A hard rule against confirmation RfA's, like option 1, would not do a good job of accounting for edge cases and would thus be ultimately detrimental here. But a soft social rule against them would be beneficial. Unfortunately, that is not one of the options of this RfC. In short, a person should have a good reason to do a confirmation RfA. If you're going to stand up before the community and ask "do you trust me," that should be for a good reason. It shouldn't just be because you want the approval of your peers. (Let me be clear: I am not suggesting that is why either Worm or Hogfarm re-upped, I'm just trying to create a general purpose rule here.) That takes some introspection and humility to ask yourself: is it worth me inviting two or three hundred people to spend part of their lives to comment on me as a person?A lot of people have thrown around editor time in their reasonings. Obviously, broad generalizations about it aren't convincing anyone. So let me just share my own experience. I saw the watchlist notice open that a new RfA was being run. I reacted with some excitement, because I always like seeing new admins. When I got to the page and saw Hogfarm's name, I immediately thought "isn't he already an admin?" I then assumed, ah, its just the classic RfA reaction at seeing a qualified candidate, so I'll probably support him since I already think he's an admin. But then as I started to do my due diligence and read, I saw that he really, truly, already had been an admin. At that point, my previous excitement turned to a certain unease. I had voted yes for Worm's confirmation RfA, but here was another...and I realized that my blind support for Worm might have been the start of an entirely new process. I then thought "bet there's an RfC going about this," and came here. I then spent a while polishing up my essay on editor time, before taking time to write this message. All in all, I probably spent a good hour doing this. Previously, I'd just been clicking the random article button and gnoming. So, the longwinded moral: yeah, this did eat up a lot of my editor time that could have and was being spent doing something else. And I'd do it again! It was important to do my research and to comment here. But in the future...maybe I won't react quite as excitedly to seeing that RfA notice. Maybe I'll feel a little pang of dread...wondering if its going to be a confirmation RfA. We can't pretend that confirmation RfA's are costless, and that we don't lose anything even if editors just ignore them. When run, it should be because they are necessary. CaptainEek⚓03:29, 17 December 2024 (UTC)
In short, a person should have a good reason to do a confirmation RfA. If you're going to stand up before the community and ask "do you trust me," that should be for a good reason. It shouldn't just be because you want the approval of your peers. Asking the community whether you still have their trust to be an administrator, which is what an reconfirmation RFA is, is a good reason. I expect getting a near-unanimous "yes" is good for one's ego, but that's just a (nice) side-effect of the far more important benefits to the entire community: a trusted administrator.
The time you claim is being eaten up unnecessarily by reconfirmation RFAs was actually taken up by you choosing to spend your time writing an essay about using time for things you don't approve of and then hunting out an RFC in which you wrote another short essay about using time on things you don't approve of. Absolutely none of that is a necessary consequence of reconfirmation RFAs - indeed the response consistent with your stated goals would have been to read the first two sentences of Hog Farm's RFA and then closed the tab and returned to whatever else it was you were doing. Thryduulf (talk) 09:16, 17 December 2024 (UTC)
WTT's and Hog Farm's RFAs would have been completely uncontentious, something I hope for at RfA and certainly the opposite of what I "dread" at RfA, if it were not for the people who attack the very concept of standing for RfA again despite policy being crystal clear that it is absolutely fine. I don't see how any blame for this situation can be put on WTT or HF. We can't pretend that dismissing uncontentious reconfirmation RfAs is costless; discouraging them removes one of the few remaining potentially wholesome bits about the process. —Kusma (talk) 09:53, 17 December 2024 (UTC)
@CaptainEek Would you find it better if Watchlist notices and similar said "(re?)confirmation RFA" instead of "RFA"? Say for all voluntary RFAs from an existing admin or someone who could have used BN?
As a different point, I would be quite against any social discouraging if we're not making a hard rule as such. Social discouraging is what got us the opposes at WTT/Hog Farm's RFAs, which I found quite distasteful and badgering. If people disagree with a process, they should change it. But if the process remains the same, I think it's important to not enable RFA's toxicity by encouraging others to namecall or re-argue the process in each RRFA. It's a short road from social discouragement to toxicity, unfortunately. Soni (talk) 18:41, 19 December 2024 (UTC)
Option 2 if people think there's a waste of community time, don't spend your time voting or discussing. Or add "reconfirmation" or similar to the watchlist notice. ~~ AirshipJungleman29 (talk) 15:08, 17 December 2024 (UTC)
Option 3 (which I think is a subset of option 2, so I'm okay with the status quo, but I want to endorse giving 'crats the option to SNOW). While they do come under scrutiny from time to time for the extensive dicsussions in the "maybe" zone following RfAs, this should be taken as an indiciation that they are unlikely to do something like close it as SNOW in the event there is real and substantial concerns being rasied. This is an okay tool to give the 'crats. As far as I can tell, no one has ever accused the them of moving too quickly in this direction (not criticism; love you all, keep up the good work). Bobby Cohn (talk) 17:26, 17 December 2024 (UTC)
Option 3 or Option 2. Further, if Option 2 passes, I expect it also ends all the bickering about lost community time. A consensus explicitly in favour of "This is allowed" should also be a consensus to discourage relitigation of this RFC. Soni (talk) 17:35, 17 December 2024 (UTC)
Option 2: Admins who do not exude entitlement are to be praised. Those who criticize this humility should have a look in the mirror before accusing those who ask for reanointment from the community of "arrogance". I agree that it wouldn't be a bad idea to mention in parentheses that the RFA is a reconfirmation (watchlist) and wouldn't see any problem with crats snow-closing after, say, 96 hours. -- SashiRolls18:48, 17 December 2024 (UTC)
I know. I see a sizable amount of commenters here starting to say that voluntary re-RfAs should be encouraged, and your first sentence can be easily read as implying that admins who use the BN route exude entitlement. I disagree with that (see my reply to Thryduulf below). Aaron Liu (talk) 12:56, 18 December 2024 (UTC)
One way to improve the reputation of RFA is for there to be more RFAs that are not terrible, such as reconfirmations of admins who are doing/have done a good job who sail through with many positive comments. There is no proposal to make RFA mandatory in circumstances it currently isn't, only to reaffirm that those who voluntarily choose RFA are entitled to do so. Thryduulf (talk) 21:06, 17 December 2024 (UTC)
I know it's not a proposal, but there's enough people talking about this so far that it could become a proposal. There's nearly nothing in between that could've lost the trust of the community. I'm sure there are many who do not want to be pressured into this without good reason. Aaron Liu (talk) 12:57, 18 December 2024 (UTC)
Absolutely nobody is proposing, suggesting or hinting here that reconfirmation RFAs should become mandatory - other than comments from a few people who oppose the idea of people voluntarily choosing to do something policy explicitly allows them to choose to do. The best way to avoid people being pressured into being accused of arrogance for seeking reconfirmation of their status from the community is to sanction those people who accuse people of arrogance in such circumstances as such comments are in flagrant breach of AGF and NPA. Thryduulf (talk) 14:56, 18 December 2024 (UTC)
Yes, I’m saying that they should not become preferred. There should be no social pressure to do RfA instead of BN, only pressure intrinsic to the candidate. Aaron Liu (talk) 15:37, 18 December 2024 (UTC)
Whether they should become preferred in any situation forms no part of this proposal in any way shape or form - this seeks only to reaffirm that they are permitted. A separate suggestion, completely independent of this one, is to encourage (explicitly not mandate) them in some (but explicitly not all) situations. All discussions on this topic would benefit if people stopped misrepresenting the policies and proposals - especially when the falsehoods have been explicitly called out. Thryduulf (talk) 15:49, 18 December 2024 (UTC)
I am talking and worrying over that separate proposal many here are suggesting. I don’t intend to oppose Option 2, and sorry if I came off that way. Aaron Liu (talk) 16:29, 18 December 2024 (UTC)
Option 2. In fact, I'm inclined to encourage an RRfA over BN, because nothing requires editors to participate in an RRfA, but the resulting discussion is better for reaffirming community consensus for the former admin or otherwise providing helpful feedback. --Pinchme123 (talk) 21:45, 17 December 2024 (UTC)
Option 2WP:RFA has said "Former administrators may seek reinstatement of their privileges through RfA..." for over ten years and this is not a problem. I liked the opportunity to be consulted in the current RfA and don't consider this a waste of time. Andrew🐉(talk) 22:14, 17 December 2024 (UTC)
2 - If an administrator gives up sysop access because they plan to be inactive for a while and want to minimize the attack surface of Misplaced Pages, they should be able to ask for permissions back the quickest way possible. If an administrator resigns because they do not intend to do the job anymore, and later changes their mind, they should request a community discussion. The right course of action depends on the situation. Jehochman14:00, 18 December 2024 (UTC)
Option 1. I've watched a lot of RFAs and re-RFAs over the years. There's a darn good reason why the community developed the "go to BN" option: saves time, is straightforward, and if there are issues that point to a re-RFA, they're quickly surfaced. People who refuse to take the community-developed process of going to BN first are basically telling the community that they need the community's full attention on their quest to re-admin. Yes, there are those who may be directed to re-RFA by the bureaucrats, in which case, they have followed the community's carefully crafted process, and their re-RFA should be evaluated from that perspective. Risker (talk) 02:34, 19 December 2024 (UTC)
Option 2 (status quo/no changes) per meh. This is bureaucratic rulemongering at its finest. Every time RFA reform comes up some editors want admins to be required to periodically reconfirm, then when some admins decide to reconfirm voluntarily, suddenly that's seen as a bad thing. The correct thing to do here is nothing. If you don't like voluntary reconfirmation RFAs, you are not required to participate in them. Ivanvector (/Edits) 19:34, 19 December 2024 (UTC)
Option 2 I would probably counsel just going to BN most of the time, however there are exceptions and edge cases. To this point these RfAs have been few in number, so the costs incurred are relatively minor. If the number becomes large then it might be worth revisiting, but I don't see that as likely. Some people will probably impose social costs on those who start them by opposing these RfAs, with the usual result, but that doesn't really change the overall analysis. Perhaps it would be better if our idiosyncratic internal logic didn't produce such outcomes, but that's a separate issue and frankly not really worth fighting over either. There's probably some meta issues here I'm unaware off, it's long since I've had my finger on the community pulse so to speak, but they tend to matter far less than people think they do. 184.152.68.190 (talk) 02:28, 20 December 2024 (UTC)
Option 1, per WP:POINT, WP:NOT#SOCIALNETWORK, WP:NOT#BUREAUCRACY, WP:NOTABOUTYOU, and related principles. We all have far better things to do that read through and argue in/about a totally unnecessary RfA invoked as a "Show me some love!" abuse of process and waste of community time and productivity. I could live with option 3, if option 1 doesn't fly (i.e. shut these silly things down as quickly as possible). But option 2 is just out of the question. — SMcCandlish☏¢ 😼 04:28, 22 December 2024 (UTC)
Except none of the re-RFAs complained about have been RfA invoked as a "Show me some love!" abuse of process, you're arguing against a strawman. Thryduulf (talk) 11:41, 22 December 2024 (UTC)
It's entirely a matter of opinion and perception, or A) this RfC wouldn't exist, and B) various of your fellow admins like TonyBallioni would not have come to the same conclusion I have. Whether the underlying intent (which no one can determine, lacking as we do any magical mind-reading powers) is solely egotistical is ultimately irrelevant. The actual effect (what matters) of doing this whether for attention, or because you've somehow confused yourself into think it needs to be done, is precisely the same: a showy waste of community volunteers' time with no result other than a bunch of attention being drawn to a particular editor and their deeds, without any actual need for the community to engage in a lengthy formal process to re-examine them. — SMcCandlish☏¢ 😼 05:49, 23 December 2024 (UTC)
or because you've somehow confused yourself into think it needs to be done
Option 2. I see no legitimate reason why we should be changing the status quo. Sure, some former admins might find it easier to go through BN, and it might save community time, and most former admins already choose the easier option. However, if a candidate last ran for adminship several years ago, or if issues were raised during their tenure as admin, then it may be helpful for them to ask for community feedback, anyway. There is no "wasted" community time in such a case. I really don't get the claims that this violates WP:POINT, because it really doesn't apply when a former admin last ran for adminship 10 or 20 years ago or wants to know if they still have community trust.On the other hand, if an editor thinks a re-RFA is a waste of community time, they can simply choose not to participate in that RFA. Opposing individual candidates' re-RFAs based solely on opposition to re-RFAs in general is a violation of WP:POINT. – Epicgenius (talk) 14:46, 22 December 2024 (UTC)
But this isn't the status quo? We've never done a re-RfA before now. The question is whether this previously unconsidered process, which appeared as an emergent behavior, is a feature or a bug. CaptainEek⚓23:01, 22 December 2024 (UTC)
There have been lots of re-RFAs, historically. There were more common in the 2000s. Evercat in 2003 is the earliest I can find, back before the re-sysopping system had been worked out fully. Croat Canuck back in 2007 was snow-closed after one day, because the nominator and applicant didn't know that they could have gone to the bureaucrats' noticeboard. For more modern examples, HJ Mitchell (2011) is relatively similar to the recent re-RFAs in the sense that the admin resigned uncontroversially but chose to re-RFA before getting the tools back. Immediately following and inspired by HJ Mitchell's, there was the slightly more controversial SarekOfVulcan. That ended successful re-RFAS until 2019's Floquenbeam, which crat-chatted. Since then, there have been none that I remember. There have been several re-RFAs from admins who were de-sysopped or at serious risk of de-sysopping, and a few interesting edge cases such as the potentially optional yet no-consensus SarekVulcan 3 in 2014 and the Rich Farmbrough case in 2015, but those are very different than what we're talking about today. GreenLipstickLesbian (talk) 00:01, 23 December 2024 (UTC)
Well thank you both, I've learned something new today. It turns out I was working on a false assumption. It has just been so long since a re-RfA that I assumed it was a truly new phenomenon, especially since there were two in short succession. I still can't say I'm thrilled by the process and think it should be used sparingly, but perhaps I was a bit over concerned. CaptainEek⚓16:47, 23 December 2024 (UTC)
Option 2 or 3 per Gnoming and CaptainEek. Such RfAs only require at most 30 seconds for one to decide whether or not to spend their time on examination. Unlike other prohibited timesinks, it's not like something undesirable will happen if one does not sink their time. Voluntary reconfirmation RfAs are socially discouraged, so there is usually a very good reason for someone to go back there, such as accountability for past statements in the case of WTT or large disputes during adminship in the case of Hog Farm. I don't think we should outright deny these, and there is no disruption incurred if we don't. Aaron Liu (talk) 15:44, 23 December 2024 (UTC)
Option 2 (fine with better labeling) These don't seem harmful to me and, if I don't have time, I'll skip one and trust the judgment of my fellow editors. No objection to better labeling them though, as discussed above. RevelationDirect (talk) 22:36, 23 December 2024 (UTC)
Option 1 because it's just a waste of time to go through and !vote on candidates who just want the mop restored when he or she or they could get it restored BN with no problems. But I can also see option 2 being good for a former mod not in good standing. Therapyisgood (talk) 23:05, 23 December 2024 (UTC)
If you think it is a waste of time to !vote on a candidate, just don't vote on that candidate and none of your time has been wasted. Thryduulf (talk) 23:28, 23 December 2024 (UTC)
Option 2 Just because someone may be entitled to get the bit back doesn't mean they necessarily should. Look at my RFA3. I did not resign under a cloud, so I could have gotten the bit back by request. However, the RFA established that I did not have the community support at that point, so it was a good thing that I chose that path. I don't particularly support option 3, but I could deal with it. --SarekOfVulcan (talk)16:05, 27 December 2024 (UTC)
Option 1 Asking hundreds of people to vet a candidate who has already passed a RfA and is eligible to get the tools back at BN is a waste of the community's time. -- Pawnkingthree (talk) 16:21, 27 December 2024 (UTC)
Option 2 I really don't think there's a problem that needs to be fixed here. I am grateful at least a couple administrators have asked for the support of the community recently. SportingFlyerT·C00:12, 29 December 2024 (UTC)
Option 2. Keep the status quo of any editor is free to re-request the tools through the requests for adminship process. Voluntary RfA are rare enough not to be a problem, it's not as though we are overburdened with RfAs. And it’s my time to waste. --Malcolmxl5 (talk) 17:58, 7 January 2025 (UTC)
Option 2 or Option 3. These are unlikely to happen anyway, it's not like they're going to become a trend. I'm already wasting my time here instead of other more important activities anyway, so what's a little more time spent giving an easy support?fanfanboy(blocktalk)16:39, 10 January 2025 (UTC)
Option 1 Agree with Daniel Quinlan that for the problematic editors eligible for re-sysop at BN despite unpopularity, we should rely on our new process of admin recall, rather than pre-emptive RRFAs. I'll add the novel argument that when goliaths like Hog Farm unnecessarily showcase their achievements at RFA, it scares off nonetheless qualified candidates. ViridianPenguin 🐧 ( 💬 ) 17:39, 14 January 2025 (UTC)
Option 2 or Option 3 - if you regard a re-RfA as a waste of your time, just don't waste it by participating; it's not mandatory. Bastun12:13, 15 January 2025 (UTC)
Discussion
@Voorts: If option 2 gets consensus how would this RfC change the wording Regardless of the process by which the admin tools are removed, any editor is free to re-request the tools through the requests for adminship process. Or is this an attempt to see if that option no longer has consensus? If so why wasn't alternative wording proposed? As I noted above this feels premature in multiple ways. Best, Barkeep49 (talk) 21:43, 15 December 2024 (UTC)
I've re-opened this per a request on my talk page. If other editors think this is premature, they can !vote accordingly and an uninvolved closer can determine if there's consensus for an early close in deference to the VPI discussion. voorts (talk/contributions) 21:53, 15 December 2024 (UTC)
The discussion at VPI, which I have replied on, seems to me to be different enough from this discussion that both can run concurrently. That is, however, my opinion as a mere editor. — Jkudlick ⚓ (talk)22:01, 15 December 2024 (UTC)
@Voorts, can you please reword the RfC to make it clear that Option 2 is the current consensus version? It does not need to be clarified – it already says precisely what you propose. – bradv22:02, 15 December 2024 (UTC)
Question: May someone clarify why many view such confirmation RfAs as a waste of community time? No editor is obligated to take up their time and participate. If there's nothing to discuss, then there's no friction or dis-cussing, and the RfA smooth-sails; if a problem is identified, then there was a good reason to go to RfA. I'm sure I'm missing something here. Aaron Liu (talk) 22:35, 15 December 2024 (UTC)
The intent of RfA is to provide a comprehensive review of a candidate for adminship, to make sure that they meet the community's standards. Is that happening with vanity re-RfAs? Absolutely not, because these people don't need that level of vetting. I wouldn't consider a week long, publicly advertized back patting to be a productive use of volunteer time. -- Ajraddatz (talk) 23:33, 15 December 2024 (UTC)
Sure, but that logic could be used to justify any time sink. We're all volunteers and nobody is forced to do anything here, but that doesn't mean that we should promote (or stay silent with our criticism of, I suppose) things that we feel don't serve a useful purpose. I don't think this is a huge deal myself, but we've got two in a short period of time and I'd prefer to do a bit of push back now before they get more common. -- Ajraddatz (talk) 01:52, 16 December 2024 (UTC)
Except someone who has no need for advanced tools and is not going to use them in any useful fashion, would then skate through with nary a word said about their unsuitability, regardless of the foregone conclusion. The point of RFA is not to rubber-stamp. Unless their is some actual issue or genuine concern they might not get their tools back, they should just re-request them at BN and stop wasting people's time with pointless non-process wonkery. Only in death does duty end (talk) 09:05, 16 December 2024 (UTC)
I’m confused. Adminship requires continued use of the tools. If you think they’s suitable for BN, I don’t see how doing an RfA suddenly makes them unsuitable. If you have concerns, raise them. Aaron Liu (talk) 13:02, 16 December 2024 (UTC)
I don't think the suggested problem (which I acknowledge not everyone thinks is a problem) is resolved by these options. Admins can still run a re-confirmation RfA after regaining adminsitrative privileges, or even initiate a recall petition. I think as discussed on Barkeep49's talk page, we want to encourage former admins who are unsure if they continue to be trusted by the community at a sufficient level to explore lower cost ways of determining this. isaacl (talk) 00:32, 16 December 2024 (UTC)
In re the idea that RfAs use up a lot of community time: I first started editing Misplaced Pages in 2014. There were 62 RfAs that year, which was a historic low. Even counting all of the AElect candidates as separate RfAs, including those withdrawn before voting began, we're still up to only 53 in 2024 – counting only traditional RfAs it's only 18, which is the second lowest number ever. By my count we've has 8 resysop requests at BN in 2024; even if all of those went to RfA, I don't see how that would overwhelm the community. That would still leave us on 26 traditional RfAs per year, or (assuming all of them run the full week) one every other week. Caeciliusinhorto-public (talk) 10:26, 16 December 2024 (UTC)
What about an option 4 encouraging eligible candidates to go through BN? At the end of the Procedure section, add something like "Eligible users are encouraged to use this method rather than running a new request for adminship." The current wording makes re-RfAing sound like a plausible alternative to a BN request, when in actual fact the former rarely happens and always generates criticism. Giraffer (talk) 12:08, 16 December 2024 (UTC)
Discouraging RFAs is the second last thing we should be doing (after prohibiting them), rather per my comments here and in the VPI discussion we should be encouraging former administrators to demonstrate that they still have the approval of the community. Thryduulf (talk) 12:16, 16 December 2024 (UTC)
I think this is a good idea if people do decide to go with option 2, if only to stave off any further mixed messages that people are doing something wrong or rude or time-wasting or whatever by doing a second RfA, when it's explicitly mentioned as a valid thing for them to do. Gnomingstuff (talk) 15:04, 16 December 2024 (UTC)
If RFA is explicitly a valid thing for people to do (which it is, and is being reaffirmed by the growing consensus for option 2) then we don't need to (and shouldn't) discourage people from using that option. The mixed messages can be staved off by people simply not making comments that explicitly contradict policy. Thryduulf (talk) 15:30, 16 December 2024 (UTC)
This is not new. We've had sporadic "vanity" RfAs since the early days of the process. I don't believe they're particularly harmful, and think that it unlikely that we will begin to see so many of them that they pose a problem. As such I don't think this policy proposal solves any problem we actually have. UninvitedCompany21:56, 16 December 2024 (UTC)
This apparent negative feeling evoked at an RFA for a former sysop everyone agrees is fully qualified and trusted certainly will put a bad taste in the mouths of other former admins who might consider a reconfirmation RFA without first visiting BN. This comes in the wake of Worm That Turned's similar rerun. BusterD (talk) 23:29, 16 December 2024 (UTC)
Nobody should ever be discouraged from seeking community consensus for significant changes. Adminship is a significant change. Thryduulf (talk) 23:32, 16 December 2024 (UTC)
No argument from me. I was a big Hog Farm backer way back when he was merely one of Misplaced Pages's best content contributors. BusterD (talk) 12:10, 17 December 2024 (UTC)
I went looking for @Tamzin's comment because I know they had hung up the tools and came back, and I was interested in their perspective. But they've given me a different epiphany. I suddenly realize why people are doing confirmation RfAs: it's because of RECALL, and the one year immunity a successful RfA gives you. Maybe everyone else already figured that one out and is thinking "well duh Eek," but I guess I hadn't :) I'm not exactly sure what to do with that epiphany, besides note the emergent behavior that policy change can create. We managed to generate an entirely new process without writing a single word about it, and that's honestly impressive :P CaptainEek⚓18:18, 17 December 2024 (UTC)
Worm That Turned followed through on a pledge he made in January 2024, before the 2024 review of the request for adminship process began. I don't think a pattern can be extrapolated from a sample size of one (or even two). That being said, it's probably a good thing if admins occasionally take stock of whether or not they continue to hold the trust of the community. As I previously commented, it would be great if these admins would use a lower cost way of sampling the community's opinion. isaacl (talk) 18:31, 17 December 2024 (UTC)
If people decide to go through a community vote to get a one year immunity from a process that only might lead to a community vote which would then have a lower threshold then the one they decide to go through, and also give a year's immunity, then good for them. CMD (talk) 01:05, 22 December 2024 (UTC)
@CaptainEek I'm mildly bothered by this comment, mildly because I assume it's lighthearted and non-serious. But just in case anyone does feel this way - I was very clear about my reasons for RRFA, I've written a lot about it, anyone is welcome to use my personal recall process without prejudice, and just to be super clear - I waive my "1 year immunity" - if someone wants to start a petition in the next year, do not use my RRfA as a reason not to. I'll update my userpage accordingly. I can't speak for Hog Farm, but his reasoning seems similar to mine, and immunity isn't it. Worm(talk) 10:28, 23 December 2024 (UTC)
@Worm That Turned my quickly written comment was perhaps not as clear as it could have been :) I'm sorry, I didn't mean to suggest that y'all had run for dubious reasons. As I said in my !vote, Let me be clear: I am not suggesting that is why either Worm or Hogfarm re-upped, I'm just trying to create a general purpose rule here. I guess what I really meant was that the reason that we're having this somewhat spirited conversation seems to be the sense that re-RfA could provide a protection from recall. If not for recall and the one year immunity period, I doubt we'd have cared so much as to suddenly run two discussions about this. CaptainEek⚓16:59, 23 December 2024 (UTC)
I don't agree. No one else has raised a concern about someone seeking a one-year respite from a recall petition. Personally, I think essentially self-initiating the recall process doesn't really fit the profile of someone who wants to avoid the recall process. (I could invent some nefarious hypothetical situation, but since opening an arbitration case is still a possibility, I don't think it would work out as planned.) isaacl (talk) 05:19, 24 December 2024 (UTC)
I really don't think this is the reason behind WTT's and HF's reconfirmation RFA's. I don't think their RFA's had much utility and could have been avoided, but I don't doubt for a second that their motivations were anything other than trying to provide transparency and accountability for the community. BugGhost🦗👻12:04, 23 December 2024 (UTC)
I don't really care enough about reconf RFAs to think they should be restricted, but what about a lighter ORCP-like process (maybe even in the same place) where fewer editors can indicate, "yeah OK, there aren't really any concerns here, it would probably save a bit of time if you just asked at BN". Alpha3031 (t • c) 12:40, 19 December 2024 (UTC)
Can someone accurately describe for me what the status quo is? I reread this RfC twice now and am having a hard time figuring out what the current state of affairs is, and how the proposed alternatives will change them. Duly signed,⛵ WaltClipper -(talk)14:42, 13 January 2025 (UTC)
Option 2 is the status quo. The goal of the RFC is to see if the community wants to prohibit reconfirmation RFAs (option 1). The idea is that reconfirmation RFAs take up a lot more community time than a BN request so are unnecessary. There were 2 reconfirmation RFAs recently after a long dry spell. –Novem Linguae (talk) 20:49, 13 January 2025 (UTC)
The status quo, documented at Misplaced Pages:Administrators#Restoration of admin tools, is that admins who resigned without being under controversy can seek readminship through either BN (where it's usually given at the discreetion of an arbitrary bureaucrat according to the section I linked) or RfA (where all normal RfA procedures apply, and you see a bunch of people saying "the candidate's wasting the community's time and could've uncontroversially gotten adminship back at BN instead). Aaron Liu (talk) 12:27, 14 January 2025 (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.
Guideline against use of AI images in BLPs and medical articles?
I have recently seen AI-generated images be added to illustrate both BLPs (e.g. Laurence Boccolini, now removed) and medical articles (e.g. Legionella#Mechanism). While we don't have any clear-cut policy or guideline about these yet, they appear to be problematic. Illustrating a living person with an AI-generated image might misinform as to how that person actually looks like, while using AI in medical diagrams can lead to anatomical inaccuracies (such as the lung structure in the second image, where the pleura becomes a bronnchiole twisting over the primary bronchi), or even medical misinformation. While a guideline against AI-generated images in general might be more debatable, do we at least have a consensus for a guideline against these two specific use cases?
I personally am strongly against using AI in biographies and medical articles - as you highlighted above, AI is absolutely not reliable in generating accurate imagery and may contribute to medical or general misinformation. I would 100% support a proposal banning AI imagery from these kinds of articles - and a recommendation to not use such imagery other than in specific scenarios. jolielover♥talk12:28, 30 December 2024 (UTC)
I'd prefer a guideline prohibiting the use of AI images full stop. There are too many potential issues with accuracy, honesty, copyright, etc. Has this already been proposed or discussed somewhere? – Joe (talk) 12:38, 30 December 2024 (UTC)
There is one very specific exception I would put to a very sensible blanket prohibition on using AI images to illustrate people, especially BLPs. That is where the person themselves is known to use that image, which I have encountered in Simon Ekpa. CMD (talk) 15:00, 30 December 2024 (UTC)
While the Ekpa portrait is just an upscale (and I'm not sure what positive value that has for us over its source; upscaling does not add accuracy, nor is it an artistic interpretation meant to reveal something about the source), this would be hard to translate to the general case. Many AI portraits would have copyright concerns, not just from the individual (who may have announced some appropriate release for it), but due to the fact that AI portraits can lean heavily on uncredited individual sources. --Nat Gertler (talk) 16:04, 30 December 2024 (UTC)
For the purposes of discussing whether to allow AI images at all, we should always assume that, for the purposes of (potential) policies and guidelines, there exist AI images we can legally use to illustrate every topic. We cannot use those that are not legal (including, but not limited to, copyright violations) so they are irrelevant. An image generator trained exclusively on public domain and cc0 images (and any other licenses that explicitly allow derivative works without requiring attribution) would not be subject to any copyright restrictions (other than possibly by the prompter and/or generator's license terms, which are both easy to determine). Similarly we should not base policy on the current state of the technology, but assume that the quality of its output will improve to the point it is equal to that of a skilled human artist. Thryduulf (talk) 17:45, 30 December 2024 (UTC)
The issue is, either there are public domain/CC0 images of the person (in which case they can be used directly) or there aren't, in which case the AI is making up how a person looks. Chaotic Enby (talk · contribs) 20:00, 30 December 2024 (UTC)
We tend to use art representations either where no photographs are available (in which case, AI will also not have access to photographs) or where what we are showing is an artist's insight on how this person is perceived, which is not something that AI can give us. In any case, we don't have to build policy now around some theoretical AI in the future; we can deal with the current reality, and policy can be adjusted if things change in the future. And even that theoretical AI does make it more difficult to detect copyvio -- Nat Gertler (talk) 20:54, 30 December 2024 (UTC)
I wouldn't call it an upscale given whatever was done appears to have removed detail, but we use that image as it was specifically it is the edited image which was sent to VRT. CMD (talk) 10:15, 31 December 2024 (UTC)
Is there any clarification on using purely AI-generated images vs. using AI to edit or alter images? AI tools have been implemented in a lot of photo editing software, such as to identify objects and remove them, or generate missing content. The generative expand feature would appear to be unreliable (and it is), but I use it to fill in gaps of cloudless sky produced from stitching together photos for a panorama (I don't use it if there are clouds, or for starry skies, as it produces non-existent stars or unrealistic clouds). Photos of Japan (talk) 18:18, 30 December 2024 (UTC)
Yes, my proposal is only about AI-generated images, not AI-altered ones. That could in fact be a useful distinction to make if we want to workshop a RfC on the matter. Chaotic Enby (talk · contribs) 20:04, 30 December 2024 (UTC)
I'm not sure if we need a clear cut policy or guideline against them... I think we treat them the same way as we would treat an editor's kitchen table sketch of the same figure. Horse Eye's Back (talk) 18:40, 30 December 2024 (UTC)
For those wanting to ban AI images full stop, well, you are too late. Most professional image editing software, including the software in one's smartphone as well as desktop, uses AI somewhere. Noise reduction software uses AI to figure out what might be noise and what might be texture. Sharpening software uses AI to figure out what should be smooth and what might have a sharp detail it can invent. For example, a bird photo not sharp enough to capture feather detail will have feather texture imagined onto it. Same for hair. Or grass. Any image that has been cleaned up to remove litter or dust or spots will have the cleaned area AI generated based on its surroundings. The sky might be extended with AI. These examples are a bit different from a 100% imagined image created from a prompt. But probably not in a way that is useful as a rule.
I think we should treat AI generated images the same as any user-generated image. It might be a great diagram or it might be terrible. Remove it from the article if the latter, not because someone used AI. If the image claims to photographically represent something, we may judge whether the creator has manipulated the image too much to be acceptable. For example, using AI to remove a person in the background of an image taken of the BLP subject might be perfectly fine. People did that with traditional Photoshop/Lightroom techniques for years. Using AI to generate what claims to be a photo of a notable person is on dodgy ground wrt copyright. -- Colin°19:12, 30 December 2024 (UTC)
I'm talking about the case of using AI to generate a depiction of a living person, not using AI to alter details in the background. That is why I only talk about AI-generated images, not AI-altered images. Chaotic Enby (talk · contribs) 20:03, 30 December 2024 (UTC)
Regarding some sort of brightline ban on the use of any such image in anything article medical related: absolutely not. For example, if someone wanted to use AI tools as opposed to other tools to make an image such as this one (as used in the "medical" article Fluconazole) I don't see a problem, so long as it is accurate. Accurate models and illustrations are useful and that someone used AI assistance as opposed to a chisel and a rock is of no concern. — xaosflux19:26, 30 December 2024 (UTC)
I believe that the appropriateness of AI images depends on how its used by the user. In BLP and medical articles, it is inappropriate for the images, but it is inappropriate to ban it completely across thw site. By the same logic, if you want full ban of AI, you are banning fire just because people can get burned, without considering cooking. JekyllTheFabulous (talk) 13:33, 31 December 2024 (UTC)
AI generated medical related image. No idea if this is accurate, but if it is I don't see what the problem would be compared to if this was made with ink and paper. — xaosflux00:13, 31 December 2024 (UTC)
I agree that AI-generated images should not be used in most cases. They essentially serve as misinformation. I also don't think that they're really comparable to drawings or sketches because AI-generation uses a level of photorealism that can easily trick the untrained eye into thinking it is real. Di (they-them) (talk) 20:46, 30 December 2024 (UTC)
AI doesn't need to be photorealistic though. I see two potential issues with AI. The first is images that might deceive the viewer into thinking they are photos, when they are not. The second is potential copyright issues. Outside of the copyright issues I don't see any unique concerns for an AI-generated image (that doesn't appear photorealistic). Any accuracy issues can be handled the same way a user who manually drew an image could be handled. Photos of Japan (talk) 21:46, 30 December 2024 (UTC)
AI-generated depictions of BLP subjects are often more "illustrative" than drawings/sketches of BLP subjects made by 'regular' editors like you and me. For example, compare the AI-generated image of Pope Francis and the user-created cartoon of Brigette Lundy-Paine. Neither image belongs on their respective bios, of course, but the AI-generated image is no more "misinformation" than the drawing. Some1 (talk) 00:05, 31 December 2024 (UTC)
I would argue the opposite: neither are made up, but the first one, because of its realism, might mislead readers into thinking that it is an actual photograph, while the second one is clearly a drawing. Which makes the first one less illustrative, as it carries potential for misinformation, despite being technically more detailed. Chaotic Enby (talk · contribs) 00:31, 31 December 2024 (UTC)
AI-generated images should always say "AI-generated image of " in the image caption. No misleading readers that way. Some1 (talk) 00:36, 31 December 2024 (UTC)
Yes, and they don't always do it, and we don't have a guideline about this either. The issue is, many people have many different proposals on how to deal with AI content, meaning we always end up with "no consensus" and no guidelines on use at all, even if most people are against it. Chaotic Enby (talk · contribs) 00:40, 31 December 2024 (UTC)
always end up with "no consensus" and no guidelines on use at all, even if most people are against it Agreed. Even a simple proposal to have image captions note whether an image is AI-generated will have editors wikilawyer over the definition of 'AI-generated.' I take back my recommendation of starting an RfC; we can already predict how that RfC will end. Some1 (talk) 02:28, 31 December 2024 (UTC)
We should absolutely not be including any AI images in anything that is meant to convey facts (with the obvious exception of an AI image illustrating the concept of an AI image). I also don't think we should be encouraging AI-altered images -- the line between "regular" photo enhancement and what we'd call "AI alteration" is blurry, but we shouldn't want AI edits for the same reason we wouldn't want fake Photoshop composites.
That said, I would assume good faith here: some of these images are probably being sourced from Commons, and Commons is dealing with a lot of undisclosed AI images. Gnomingstuff (talk) 23:31, 30 December 2024 (UTC)
Do you really mean to ban single images showing the way birds use their wings?
Sorry, should have been more clear -- composites that present themselves as the real thing, basically what people would use deepfakes for now. Gnomingstuff (talk) 20:20, 31 December 2024 (UTC)
Yeah I think there is a very clear line between images built by a diffusion model and images modified using photoshop through techniques like compositing. That line is that the diffusion model is reverse-engineering an image to match a text prompt from a pattern of semi-random static associated with similar text prompts. As such it's just automated glurge, at best it's only as good as the ability of the software to parse a text prompt and the ability of a prompter to draft sufficiently specific language. And absolutely none of that does anything to solve the "hallucination" problem. On the other hand, in photoshop, if I put in two layers both containing a bird on a transparent background, what I, the human making the image, sees is what the software outputs. Simonm223 (talk) 18:03, 15 January 2025 (UTC)
Yeah I think there is a very clear line between images built by a diffusion model and images modified using photoshop others do not. If you want to ban or restrict one but not the other then you need to explain how the difference can be reliably determined, and how one is materially different to the other in ways other than your personal opinion. Thryduulf (talk) 18:45, 15 January 2025 (UTC)
I don't think any guideline, let alone policy, would be beneficial and indeed on balance is more likely to be harmful. There are always only two questions that matter when determining whether we should use an image, and both are completely independent of whether the image is AI-generated or not:
Can we use this image in this article? This depends on matters like copyright, fair use, whether the image depicts content that is legal for an organisation based in the United States to host, etc. Obviously if the answer is "no", then everything else is irrelevant, but as the law and WMF, Commons and en.wp policies stand today there exist some images in both categories we can use, and some images in both categories we cannot use.
Does using this image in this article improve the article? This is relative to other options, one of which is always not using any image, but in many cases also involves considering alternative images that we can use. In the case of depictions of specific, non-hypothetical people or objects one criteria we use to judge whether the image improves the article is whether it is an accurate representation of the subject. If it is not an accurate representation then it doesn't improve the article and thus should not be used, regardless of why it is inaccurate. If it is an accurate representation, then its use in the article will not be misrepresentative or misleading, regardless of whether it is or is not AI generated. It may or may not be the best option available, but if it is then it should be used regardless of whether it is or is not AI generated.
The potential harm I mentioned above is twofold, firstly Misplaced Pages is, by definition, harmed when an images exists we could use that would improve an article but we do not use it in that article. A policy or guideline against the use of AI images would, in some cases, prevent us from using an image that would improve an article. The second aspect is misidentification of an image as AI-generated when it isn't, especially when it leads to an image not being used when it otherwise would have been.
Finally, all the proponents of a policy or guideline are assuming that the line between images that are and are not AI-generated is sharp and objective. Other commenters here have already shown that in reality the line is blurry and it is only going to get blurrier in the future as more AI (and AI-based) technology is built into software and especially firmware. Thryduulf (talk) 00:52, 31 December 2024 (UTC)
I agree with almost the entirety of your post with a caveat on whether something "is an accurate representation". We can tell whether non-photorealistic images are accurate by assessing whether the image accurately conveys the idea of what it is depicting. Photos do more than convey an idea, they convey the actual look of something. With AI generated images that are photorealistic it is difficult to assess whether they accurately convey the look of something (the shading might be illogical in subtle ways, there could be an extra finger that goes unnoticed, a mole gets erased), but readers might be deceived by the photo-like presentation into thinking they are looking at an actual photographic depiction of the subject which could differ significantly from the actual subject in ways that go unnoticed. Photos of Japan (talk) 04:34, 31 December 2024 (UTC)
A policy or guideline against the use of AI images would, in some cases, prevent us from using an image that would improve an article. That's why I'm suggesting a guideline, not a policy. Guidelines are by design more flexible, and WP:IAR still does (and should) apply in edge cases.The second aspect is misidentification of an image as AI-generated when it isn't, especially when it leads to an image not being used when it otherwise would have been. In that case, there is a licensing problem. AI-generated images on Commons are supposed to be clearly labeled as such. There is no guesswork here, and we shouldn't go hunting for images that might have been AI-generated.Finally, all the proponents of a policy or guideline are assuming that the line between images that are and are not AI-generated is sharp and objective. Other commenters here have already shown that in reality the line is blurry and it is only going to get blurrier in the future as more AI (and AI-based) technology is built into software and especially firmware. In that case, it's mostly because the ambiguity in wording: AI-edited images are very common, and are sometimes called "AI-generated", but here we should focus on actual prompt outputs, of the style "I asked a model to generate me an image of a BLP". Chaotic Enby (talk · contribs) 11:13, 31 December 2024 (UTC)
Simply not having a completely unnecessary policy or guideline is infinitely better than relying on IAR - especially as this would have to be ignored every time it is relevant. When the AI image is not the best option (which obviously includes all the times its unsuitable or inaccurate) existing policies, guidelines, practice and frankly common sense mean it won't be used. This means the only time the guideline would be relevant is when an AI image is the best option and as we obviously should be using the best option in all cases we would need to ignore the guideline against using AI images.
AI-generated images on Commons are supposed to be clearly labeled as such. There is no guesswork here, and we shouldn't go hunting for images that might have been AI-generated. The key words here are "supposed to be" and "shouldn't", editors absolutely will speculate that images are AI-generated and that the Commons labelling is incorrect. We are supposed to assume good faith, but this very discussion shows that when it comes to AI some editors simply do not do that.
Regarding your final point, that might be what you are meaning but it is not what all other commenters mean when they want to exclude all AI images. Thryduulf (talk) 11:43, 31 December 2024 (UTC)
For your first point, the guideline is mostly to take care of the "prompt fed in model" BLP illustrations, where it is technically hard to prove that the person doesn't look like that (as we have no available image), but the model likely doesn't have any available image either and most likely just made it up. As my proposal is essentially limited to that (I don't include AI-edited images, only those that are purely generated by a model), I don't think there will be many cases where IAR would be needed.Regarding your two other points, you are entirely correct, and while I am hoping for nuance on the AI issue, it is clear that some editors might not do that. For the record, I strongly disagree with a blanket ban of "AI images" (which includes both blatant "prompt in model" creations and a wide range of more subtle AI retouching tools) or anything like that. Chaotic Enby (talk · contribs) 11:49, 31 December 2024 (UTC)
the guideline is mostly to take care of the "prompt fed in model" BLP illustrations, where it is technically hard to prove that the person doesn't look like that (as we have no available image). There are only two possible scenarios regarding verifiability:
The image is an accurate representation and we can verify that (e.g. by reference to non-free photos).
Verifiability is no barrier to using the image, whether it is AI generated or not.
If it is the best image available, and editors agree using it is better than not having an image, then it should be used whether it is AI generated or not.
The image is either not an accurate representation, or we cannot verify whether it is or is not an accurate representation
The only reasons we should ever use the image are:
It has been the subject of notable commentary and we are presenting it in that context.
The subject verifiably uses it as a representation of themselves (e.g. as an avatar or logo)
This is already policy, whether the image is AI generated or not is completely irrelevant.
In your first scenario, there is the issue of an accurate AI-generated image misleading people into thinking it is an actual photograph of the person, especially as they are most often photorealistic. Even besides that, a mostly accurate representation can still introduce spurious details, and this can mislead readers as they do not know to what level it is actually accurate. This scenario doesn't really happen with drawings (which are clearly not photographs), and is very much a consequence of AI-generated photorealistic pictures being a thing.In the second scenario, if we cannot verify that it is not an accurate representation, it can be hard to remove the image with policy-based reasons, which is why a guideline will again be helpful. Having a single guideline against fully AI-generated images takes care of all of these scenarios, instead of having to make new specific guidelines for each case that emerges because of them. Chaotic Enby (talk · contribs) 13:52, 31 December 2024 (UTC)
If the image is misleading or unverifiable it should not be used, regardless of why it is misleading or unverifiable. This is existing policy and we don't need anything specifically regarding AI to apply it - we just need consensus that the image is misleading or unverifiable. Whether it is or is not AI generated is completely irrelevant. Thryduulf (talk) 15:04, 31 December 2024 (UTC)
AI-generated images on Commons are supposed to be clearly labeled as such. There is no guesswork here, and we shouldn't go hunting for images that might have been AI-generated.
I mean... yes, we should? At the very least Commons should go hunting for mislabeled images -- that's the whole point of license review. The thing is that things are absolutely swamped over there and there are hundreds of thousands of images waiting for review of some kind. Gnomingstuff (talk) 20:35, 31 December 2024 (UTC)
I just mean that given the reality of the backlogs, there are going to be mislabeled images, and there are almost certainly going to be more of them over time. That's just how it is. We don't have control over that, but we do have control over what images go into articles, and if someone has legitimate concerns about an image being AI-generated, then they should be raising those. Gnomingstuff (talk) 20:45, 31 December 2024 (UTC)
Support blanket ban on AI-generated images on Misplaced Pages. As others have highlighted above, the is not just a slippery slope but an outright downward spiral. We don't use AI-generated text and we shouldn't use AI-generated images: these aren't reliable and they're also WP:OR scraped from who knows what and where. Use only reliable material from reliable sources. As for the argument of 'software now has AI features', we all know that there's a huge difference between someone using a smoothing feature and someone generating an image from a prompt. :bloodofox: (talk) 03:12, 31 December 2024 (UTC)
Reply, the section of WP:OR concerning images is WP:OI which states "Original images created by a Wikimedian are not considered original research, so long as they do not illustrate or introduce unpublished ideas or arguments". Using AI to generate an image only violates WP:OR if you are using it to illustrate unpublished ideas, which can be assessed just by looking at the image itself. COPYVIO, however, cannot be assessed from looking at just the image alone, which AI could be violating. However, some images may be too simple to be copyrightable, for example AI-generated images of chemicals or mathematical structures potentially. Photos of Japan (talk) 04:34, 31 December 2024 (UTC)
Prompt generated images are unquestionably violation of WP:OR and WP:SYNTH: Type in your description and you get an image scraping who knows what and from who knows where, often Misplaced Pages. Misplaced Pages isn't an WP:RS. Get real. :bloodofox: (talk) 23:35, 1 January 2025 (UTC)
"Unquestionably"? Let me question that, @Bloodofox. ;-)
If an editor were to use an AI-based image-generating service and the prompt is something like this:
"I want a stacked bar chart that shows the number of games won and lost by FC Bayern Munich each year. Use the team colors, which are red #DC052D, blue #0066B2, and black #000000. The data is:
2014–15: played 34 games, won 25, tied 4, lost 5
2015–16: played 34 games, won 28, tied 4, lost 2
2016–17: played 34 games, won 25, tied 7, lost 2
2017–18: played 34 games, won 27, tied 3, lost 4
2018–19: played 34 games, won 24, tied 6, lost 4
2019–20: played 34 games, won 26, tied 4, lost 4
2020–21: played 34 games, won 24, tied 6, lost 4
2021–22: played 34 games, won 24, tied 5, lost 5
2022–23: played 34 games, won 21, tied 8, lost 5
2023–24: played 34 games, won 23, tied 3, lost 8"
I would expect it to produce something that is not a violation of either OR in general or OR's SYNTH section specifically. What would you expect, and why do you think it would be okay for me to put that data into a spreadsheet and upload a screenshot of the resulting bar chart, but you don't think it would be okay for me to put that same data into a image generator, get the same thing, and upload that?
Assuming you'd even get what you requested the model without fiddling with the prompt for a while, these sort of 'but we can use it for graphs and charts' devil's advocate scenarios aren't helpful. We're discussing generating images of people, places, and objects here and in those cases, yes, this would unquestionably be a form of WP:OR & WP:SYNTH. As for the charts and graphs, there are any number of ways to produce these. :bloodofox: (talk) 03:07, 2 January 2025 (UTC)
We're discussing generating images of people, places, and objects here The proposal contains no such limitation. and in those cases, yes, this would unquestionably be a form of WP:OR & WP:SYNTH. Do you have a citation for that? Other people have explained better than I can how that it is not necessarily true, and certainly not unquestionable. Thryduulf (talk) 03:14, 2 January 2025 (UTC)
As you're well aware, these images are produced by scraping and synthesized material from who knows what and where: it's ultimately pure WP:OR to produce these fake images and they're a straightforward product of synthesis of multiple sources (WP:SYNTH) - worse yet, these sources are unknown because training data is by no means transparent. Personally, I'm strongly for a total ban on generative AI on the site exterior to articles on the topic of generative AI. Not only do I find this incredible unethical, I believe it is intensely detrimental to Misplaced Pages, which is an already a flailing and shrinking project. :bloodofox: (talk) 03:23, 2 January 2025 (UTC)
So you think the lead image at Gisèle Pelicot is a SYNTH violation? Its (human) creator explicitly says "This is not done from one specific photo. As I usually do when I draw portraits of people that I can't see in person, I look at a lot of photos of them and then create my own rendition" in the image description, which sounds like the product of synthesis of multiple sources" to me, and "these sources are unknown because" the the images the artist looked at are not disclosed.
A lot of my concern about blanket statements is the principle that what's sauce for the goose is sauce for the gander, too. If it's okay for a human to do something by hand, then it should be okay for a human using a semi-automated tool to do it, too.
(Just in case you hadn't heard, the rumors that the editor base is shrinking have been false for over a decade now. Compared to when you created your account in mid-2005, we have about twice as many high-volume editors.) WhatamIdoing (talk) 06:47, 2 January 2025 (UTC)
Review WP:SYNTH and your attempts at downplaying a prompt-generated image as "semi-automated" shows the root of the problem: if you can't detect the difference between a human sketching from a reference and a machine scraping who-knows-what on the internet, you shouldn't be involved in this discussion. As for editor retention, this remains a serious problem on the site: while the site continues to grow (and becomes core fodder for AI-scraping) and becomes increasingly visible, editorial retention continues to drop. :bloodofox: (talk) 09:33, 2 January 2025 (UTC)
Please scroll down below SYNTH to the next section titled "What is not original research" which begins with WP:OI, our policies on how images relate to OR. OR (including SYNTH) only applies to images with regards to if they illustrate "unpublished ideas or arguments". It does not matter, for instance, if you synthesize an original depiction of something, so long as the idea of that thing is not original. Photos of Japan (talk) 09:55, 2 January 2025 (UTC)
Yes, which explicitly states:
It is not acceptable for an editor to use photo manipulation to distort the facts or position illustrated by an image. Manipulated images should be prominently noted as such. Any manipulated image where the encyclopedic value is materially affected should be posted to Misplaced Pages:Files for discussion. Images of living persons must not present the subject in a false or disparaging light.
Using a machine to generate a fake image of someone is far beyond "manipulation" and it is certainly "false". Clearly we need explicit policies on AI-generated images of people or we wouldn't be having this discussion, but this as it stands clarly also falls under WP:SYNTH: there is zero question that this is a result of "synthesis of published material", even if the AI won't list what it used. Ultimately it's just a synthesis of a bunch of published composite images of who-knows-what (or who-knows-who?) the AI has scraped together to produce a fake image of a person. :bloodofox: (talk) 10:07, 2 January 2025 (UTC)
The latter images you describe should be SVG regardless. If there are models that can generate that, that seems totally fine since it can be semantically altered by hand. Any generation with photographic or "painterly" characteristics (e.g. generating something in the style of a painting or any other convention of visual art that communicates aesthetic particulars and not merely abstract visual particulars) seems totally unacceptable. Remsense ‥ 论07:00, 31 December 2024 (UTC)
100 dots: 99 chocolate-colored dots and 1 baseball-shaped dot
@Bloodofox, here's an image I created. It illustrates the concept of 1% in an article. I made this myself, by typing 100 emojis and taking a screenshot. Do you really mean to say that if I'd done this with an image-generating AI tool, using a prompt like "Give me 100 dots in a 10 by 10 grid. Make 99 a dark color and 1, randomly placed, look like a baseball" that it would be hopelessly tainted, because AI is always bad? Or does your strongly worded statement mean something more moderate?
I'd worry about photos of people (including dead people). I'd worry about photos of specific or unique objects that have to be accurate or they're worse than worthless (e.g., artwork, landmarks, maps). But I'm not worried about simple graphs and charts like this one, and I'm not worried about ordinary, everyday objects. If you want to use AI to generate a photorealistic image of a cookie, or a spoon, and the output you get genuinely looks like those objects, I'm not actually going to worry about it. WhatamIdoing (talk) 06:57, 31 December 2024 (UTC)
As you know, Misplaced Pages has the unique factor of being entirely volunteer-ran. Misplaced Pages has fewer and fewer editors and, long-term, we're seeing plummeting birth rates in areas where most Misplaced Pages editors do exist. I wouldn't expect a wave of new ones aimed at keeping the site free of bullshit in the near future.
In addition, the Wikimedia Foundation's hair-brained continued effort to turn the site into its political cash machine is no doubt also not helping, harming the site's public perception and leading to fewer new editors.
Over the course of decades (I've been here for around 20 years), it seems clear that the site will be negatively impacted by all this, especially in the face of generative AI.
As a long-time editor who has frequently stumbled upon intense WP:PROFRINGE content, fended off armies of outside actors looking to shape the site into their ideological image (and sent me more than a few death threats), and who has identified large amount of politically-motivated nonsense explicitly designed to fool non-experts in areas I know intimately well (such as folklore and historical linguistics topics), I think it need be said that the use of generative AI for content is especially dangerous because of its capabilities of fooling Misplaced Pages readers and Misplaced Pages editors alike.
Misplaced Pages is written by people for people. We need to draw a line in the sand to keep from being flooded by increasingly accessible hoax-machines.
A blanket ban on generative AI resolves this issue or at least hands us another tool with which to attempt to fight back. We don't need what few editors we have here wasting what little time they can give the project checking over an ocean of AI-generated slop: we need more material from reliable sources and better tools to fend off bad actors usable by our shrinking editor base (anyone at the Wikimedia Foundation listening?), not more waves of generative AI garbage. :bloodofox: (talk) 07:40, 31 December 2024 (UTC)
A blanket ban doesn't actually resolve most of the issues though, and introduces new ones. Bad usages of AI can already be dealt with by existing policy, and malicious users will ignore a blanket ban anyways. Meanwhile, a blanket ban would harm many legitimate usages for AI. For instance, the majority of professional translators (at least Japanese to English) incorporate AI (or similar tools) into their workflow to speed up translations. Just imagine a professional translator who uses AI to help generate rough drafts of foreign language Misplaced Pages articles, before reviewing and correcting them, and another editor learning of this and mass reverting them for breaking the blanket ban, and ultimately causing them to leave. Many authors (particularly with carpal tunnel) use AI now to control their voice-to-text (you can train the AI on how you want character names spelled, the formatting of dialogue and other text, etc.). A wikipedia editor could train an AI to convert their voice into Misplaced Pages-formatted text. AI is subtly incorporated now into spell-checkers, grammar-checkers, photo editors, etc., in ways many people are not aware of. A blanket AI ban has the potential to cause many issues for a lot of people, without actually being that affective at dealing with malicious users. Photos of Japan (talk) 08:26, 31 December 2024 (UTC)
I think this is the least convincing one I've seen here yet: It contains the ol' 'there are AI features in programs now' while also attempting to invoke accessibility and a little bit of 'we must have machines to translate!'.
As a translator myself, I can only say: Oh please. Generative AI is notoriously terrible at translating and that's not likely to change. And I mean ever beyond a very, very basic level. Due to the complexities of communication and little matters like nuance, all machine translated material must be thoroughly checked and modified by, yes, human translators, who often encounter it spitting out complete bullshit scraped from who-knows-where (often Misplaced Pages itself).
I get that this topic attracts a lot of 'but what if generative AI is better than humans?' from the utopian tech crowd but the reality is that anyone who needs a machine to invent text and visuals for whatever reason simply shouldn't be using it on Misplaced Pages.
Either you, a human being, can contribute to the project or you can't. Slapping a bunch of machine-generated (generative AI) visuals and text (much of it ultimately coming from Misplaced Pages in the first place!) isn't some kind of human substitute, it's just machine-regurgitated slop and is not helping the project.
Over three thousand full-time professional translators from around the world responded to the surveys, which were broken into a survey for CAT tool users and one for those who do not use any CAT tool at all.
88% of respondents use at least one CAT tool for at least some of their translation tasks.
Of those using CAT tools, 83% use a CAT tool for most or all of their translation work.
Mind you, traditionally CAT tools didn't use AI, but many do now, which only adds to potential sources of confusion in a blanket ban of AI. Photos of Japan (talk) 17:26, 31 December 2024 (UTC)
You're barking up the tree with the pro-generative AI propaganda in response to me. I think we're all quite aware that generative AI tool integration is now common and that there's also a big effort to replace human translators — and anything that can be "written" with machines-generated text. I'm also keenly aware that generative AI is absolutely horrible at translation and all of it must be thoroughly checked by humans, as you would be if you were a translator yourself. :bloodofox: (talk) 22:20, 31 December 2024 (UTC)
"all machine translated material must be thoroughly checked and modified by, yes, human translators"
There are translators (particularly with non-creative works) who are using these tools to shift more towards reviewing. It should be up to them to decide what they think is the most efficient method for them. Photos of Japan (talk) 06:48, 1 January 2025 (UTC)
And any translator who wants to use generative AI to attempt to translate can do so off the site. We're not here to check it for them. I strongly support a total ban on any generative AI used on the site exterior to articles on generative AI. :bloodofox: (talk) 11:09, 1 January 2025 (UTC)
I wonder what you mean by "on the site". The question here is "Is it okay for an editor to go to a completely different website, generate an image all by themselves, upload it to Commons, and put it in a Misplaced Pages article?" The question here is not "Shall we put AI-generating buttons on Misplaced Pages's own website?" WhatamIdoing (talk) 02:27, 2 January 2025 (UTC)
I'm talking about users slapping machine-translated and/or machine-generated nonsense all over the site, only for us to have to go behind and not only check it but correct it. It takes users minutes to do this and it's already happening. It's the same for images. There are very few of us who volunteer here and our numbers are growing fewer. We need to be spending our time improving the site rather than opening the gate as wide as possible for a flood of AI-generated/rendered garbage. The site has enough problems that compound every day rather than having to fend off users armed with hoax machines at every corner. :bloodofox: (talk) 03:20, 2 January 2025 (UTC)
Sure, we're all opposed to "nonsense", but my question is: What about when the machine happens to generate something that is not "nonsense"?
I have some worries about AI content. I worry, for example, that they'll corrupt our sources. I worry that List of scholarly publishing stings will get dramatically longer, and also that even more undetected, unconfessed, unretracted papers will get published and believed to be true and trustworthy. I worry that academia will go back to a model in which personal connections are more important, because you really can't trust what's published. I worry that scientific journals will start refusing to publish research unless it comes from someone employed by a trusted institution, that is willing to put its reputation on the line by saying they have directly verified that the work described in the paper was actually performed to their standards, thus scuttling the citizen science movement and excluding people whose institutions are upset with them for other reasons (Oh, you thought you'd take a job elsewhere? Well, we refuse to certify the work you did for the last three years...).
But I'm not worried about a Misplaced Pages editor saying "Hey AI, give me a diagram of swingset" or "Make a chart for me out of the data I'm going to give you". In fact, if someone wants to pull the numbers out of Template:Misplaced Pages editor graph (100 per month), feed it to an AI, and replace the template's contents with an AI-generated image (until they finally fix the Graphs extension), I'd consider that helpful. WhatamIdoing (talk) 07:09, 2 January 2025 (UTC)
Translators are not using generative AI for translation, the applicability of LLMs to regular translation is still in its infancy and regardless will not be implementing any generative faculties to its output since that is the exact opposite of what translation is supposed to do. JoelleJay (talk) 02:57, 2 January 2025 (UTC)
Translators are not using generative AI for translation this entirely depends on what you mean by "generative". There are at least three contradictory understandings of the term in this one thread alone. Thryduulf (talk) 03:06, 2 January 2025 (UTC)
Please, you can just go through the entire process with a simple prompt command now. The results are typically shit but you can generate a ton of it quickly, which is perfect for flooding a site like this one — especially without a strong policy against it. I've found myself cleaning up tons of AI-generated crap (and, yes, rendered) stuff here and elsewhere, and now I'm even seeing AI-generated responses to my own comments. It's beyond ridiculous. :bloodofox: (talk) 03:20, 2 January 2025 (UTC)
Ban AI-generated from all articles, AI anything from BLP and medical articles is the position that seems it would permit all instances where there are plausible defenses that AI use does not fabricate or destroy facts intended to be communicated in the context of the article. That scrutiny is stricter with BLP and medical articles in general, and the restriction should be stricter to match. Remsense ‥ 论06:53, 31 December 2024 (UTC)
I think my previous comment is operative: almost anything we can see AI used programmatically to generate should be SVG, not raster—even if it means we are embedding raster images in SVG to generate examples like the above. I do not know if there are models that can generate SVG, but if there are I happily state I have no problem with that. I think I'm at risk of seeming downright paranoid—but understanding how errors can propagate and go unnoticed in practice, if we're to trust a black box, we need to at least be able to check what the black box has done on a direct structural level. Remsense ‥ 论07:02, 31 December 2024 (UTC)
Makes perfect sense that there would be. Again, maybe I come off like a paranoid lunatic, but I really need either the ability to check what the thing is doing, or the ability to check and correct exactly what a black box has done. (In my estimation, if you want to know what procedures person has done, theoretically you can ask them to get a fairly satisfactory result, and the pre-AI algorithms used in image manipulation are canonical and more or less transparent. Acknowledging human error etc., with AI there is not even the theoretical promise that one can be given a truthful account of how it decided to do what it did.) Remsense ‥ 论07:18, 31 December 2024 (UTC)
Like everyone said, there should be a de facto ban on using AI images in Misplaced Pages articles. They are effectively fake images pretending to be real, so they are out of step with the values of Misplaced Pages.--♦IanMacM♦08:20, 31 December 2024 (UTC)
Except, not everybody has said that, because the majority of those of us who have refrained from hyperbole have pointed out that not all AI images are "fake images pretending to be real" (and those few that are can already be removed under existing policy). You might like to try actually reading the discussion before commenting further. Thryduulf (talk) 10:24, 31 December 2024 (UTC)
@Remsense, exactly how much "ability to check what the thing is doing" do you need to be able to do, when the image shows 99 dots and 1 baseball, to illustrate the concept of 1%? If the image above said {{pd-algorithm}} instead of {{cc-by-sa-4.0}}, would you remove if from the article, because you just can't be sure that it shows 1%? WhatamIdoing (talk) 02:33, 2 January 2025 (UTC)
The above is a useful example to an extent, but it is a toy example. I really do think i is required in general when we aren't dealing with media we ourselves are generating. Remsense ‥ 论04:43, 2 January 2025 (UTC)
How do we differentiate in policy between a "toy example" (that really would be used in an article) and "real" examples? Is it just that if I upload it, then you know me, and assume I've been responsible? WhatamIdoing (talk) 07:13, 2 January 2025 (UTC)
There definitely exist generative AI for SVG files. Here's an example: I used generative AI in Adobe Illustrator to generate the SVG gear in File:Pinwheel scheduling.svg (from Pinwheel scheduling) before drawing by hand the more informative parts of the image. The gear drawing is not great (a real gear would have uniform tooth shape) but maybe the shading is better than I would have done by hand, giving an appearance of dimensionality and surface material while remaining deliberately stylized. Is that the sort of thing everyone here is trying to forbid?
I can definitely see a case for forbidding AI-generated photorealistic images, especially of BLPs, but that's different from human oversight of AI in the generation of schematic images such as this one. —David Eppstein (talk) 01:15, 1 January 2025 (UTC)
I'd include BDPs, too. I had to get a few AI-generated images of allegedly Haitian presidents deleted a while ago. The "paintings" were 100% fake, right down to the deformed medals on their military uniforms. An AI-generated "generic person" would be okay for some purposes. For a few purposes (e.g., illustrations of Obesity) it could even be preferable to have a fake "person" than a real one. But for individual/named people, it would be best not to have anything unless it definitely looks like the named person. WhatamIdoing (talk) 07:35, 2 January 2025 (UTC)
Of course, that's why I'm only looking at specific cases and refrain from proposing a blanket ban on generative AI. Regarding Donald Trump, we do have one AI-generated image of him that is reasonable to allow (in Springfield pet-eating hoax), as the image itself was the subject of relevant commentary. Of course, this is different from using an AI-generated image to illustrate Donald Trump himself, which is what my proposal would recommend against. Chaotic Enby (talk · contribs) 11:32, 31 December 2024 (UTC)
That's certainly true, but others are adopting much more extreme positions than you are, and it was the more extreme views that I wished to challenge.—S MarshallT/C11:34, 31 December 2024 (UTC)
Going off WAID's example above, perhaps we should be trying to restrict the use of AI where image accuracy/precision is essential, as it would be for BLP and medical info, among other cases, but in cases where we are talking generic or abstract concepts, like the 1% image, it's use is reasonable. I would still say we should strongly prefer am image made by a human with high control of the output, but when accuracy is not as important as just the visualization, it's reasonable to turn to AI to help. Masem (t) 15:12, 31 December 2024 (UTC)
Support total ban of AI imagery - There are probable copyright problems and veracity problems with anything coming out of a machine. In a word of manipulated reality, Misplaced Pages will be increasingly respected for holding a hard line against synthetic imagery. Carrite (talk) 15:39, 31 December 2024 (UTC)
For both issues AI vs not AI is irrelevant. For copyright, if the image is a copyvio we can't use it regardless of whether it is AI or not AI, if it's not a copyvio then that's not a reason to use or not use the image. If the images is not verifiably accurate then we already can (and should) exclude it, regardless of whether it is AI or not AI. For more detail see the extensive discussion above you've either not read or ignored. Thryduulf (talk) 16:34, 31 December 2024 (UTC)
Yes, we absolutely should ban the use of AI-generated images in these subjects (and beyond, but that's outside the scope of this discussion). AI should not be used to make up a simulation of a living person. It does not actually depict the person and may introduce errors or flaws that don't actually exist. The picture does not depict the real person because it is quite simply fake.
Even worse would be using AI to develop medical images in articles in any way. The possibility for error there is unacceptable. Yes, humans make errors too, but there there is a) someone with the responsibility to fix it and b) someone conscious who actually made the picture, rather than a black box that spat it out after looking at similar training data. Cremastra 🎄 u — c 🎄 20:08, 31 December 2024 (UTC)
It's incredibly disheartening to see multiple otherwise intelligent editors who have apparently not read and/or not understood what has been said in the discussion but rather responding with what appears to be knee-jerk reactions to anti-AI scaremongering. The sky will not fall in, Misplaced Pages is not going to be taken over by AI, AI is not out to subvert Misplaced Pages, we already can (and do) remove (and more commonly not add in the first placE) false and misleading information/images. Thryduulf (talk) 20:31, 31 December 2024 (UTC)
So what benefit does allowing AI images bring? We shouldn't be forced to decide these on a case-by-case basis.
I'm sorry to dishearten you, but I still respectfully disagree with you. And I don't think this is "scaremongering" (although I admit that if it was, I would of course claim it wasn't). Cremastra 🎄 u — c 🎄 21:02, 31 December 2024 (UTC) Cremastra 🎄 u — c 🎄 20:56, 31 December 2024 (UTC)
Determining what benefits any image brings to Misplaced Pages can only be done on a case-by-case basis. It is literally impossible to know whether any image improves the encyclopaedia without knowing the context of which portion of what article it would illustrate, and what alternative images are and are not available for that same spot.
The benefit of allowing AI images is that when an AI image is the best option for a given article we use it. We gain absolutely nothing by prohibiting using the best image available, indeed doing so would actively harm the project without bringing any benefits. AI images that are misleading, inaccurate or any of the other negative things any image can be are never the best option and so are never used - we don't need any policies or guidelines to tell us that. Thryduulf (talk) 21:43, 31 December 2024 (UTC)
Support blanket ban on AI-generated text or images in articles, except in contexts where the AI-generated content is itself the subject of discussion (in a specific or general sense). Generative AI is fundamentally at odds with Misplaced Pages's mission of providing reliable information, because of its propensity to distort reality or make up information out of whole cloth. It has no place in our encyclopedia. —pythoncoder (talk | contribs) 21:34, 31 December 2024 (UTC)
Support blanket ban on AI-generated images except in ABOUTSELF contexts. This is especially a problem given the preeminence Google gives to Misplaced Pages images in its image search. JoelleJay (talk) 22:49, 31 December 2024 (UTC)
Ban across the board, except in articles which are actually about AI-generated imagery or the tools used to create them, or the image itself is the subject of substantial commentary within the article for some reason. Even in those cases, clearly indicating that the image is AI-generated should be required. Seraphimblade00:29, 1 January 2025 (UTC)
Oppose blanket bans that would forbid the use of AI assistance in creating diagrams or other deliberately stylized content. Also oppose blanket bans that would forbid AI illustrations in articles about AI illustrations. I am not opposed to banning photorealistic AI-generated images in non-AI-generation contexts or banning AI-generated images from BLPs unless the image itself is specifically relevant to the subject of the BLP. —David Eppstein (talk) 01:27, 1 January 2025 (UTC)
Oppose blanket bans AI is just a new buzzword so, for example, Apple phones now include "Apple Intelligence" as a standard feature. Does this means that photographs taken using Apple phones will be inadmissable? That would be silly because legacy technologies are already rife with issues of accuracy and verification. For example, there's an image on the main page right now (right). This purports to be a particular person ("The Father of Australia") but, if you check the image description, you find that it may have been his brother and even the attribution to the artist is uncertain. AI features may help in exposing such existing weaknesses in our image use and so we should be free to use them in an intelligent way. Andrew🐉(talk) 08:03, 1 January 2025 (UTC)
So, you expect an the AI, notoriously trained on Misplaced Pages (and whatever else is floating around on the internet), to correct Misplaced Pages where humans have failed... using the data it scraped from Misplaced Pages (and who knows where else)? :bloodofox: (talk) 11:12, 1 January 2025 (UTC)
I tried using the Deep Research option of Gemini to assess the attribution of the Macquarie portrait. Its stated methodology seemed quite respectable and sensible.
The Opie Portrait of Lachlan Macquarie: An Examination of its Attribution: Methodology
To thoroughly investigate the attribution of the Opie portrait of Lachlan Macquarie, a comprehensive research process was undertaken. This involved several key steps:
Gathering information on the Opie portrait: This included details about its history, provenance, and any available information on its cost.
Reviewing scholarly articles and publications: This step focused on finding academic discussions specifically addressing the attribution of the portrait to John Opie.
Collecting expert opinions: Statements and opinions from art experts and historians were gathered to understand the range of perspectives on the certainty of the attribution.
Examining historical documents and records: This involved searching for any records that could shed light on the portrait's origins and authenticity, such as Macquarie's personal journals or contemporary accounts.
Exploring scientific and technical analyses: Information was sought on any scientific or technical analyses conducted on the portrait, such as pigment analysis or canvas dating, to determine its authenticity.
Comparing the portrait to other Opie works: This step involved analyzing the style and technique of the Opie portrait in comparison to other known portraits by Opie to identify similarities and differences.
It was quite transparent in listing and citing the sources that it used for its analysis. These included the Misplaced Pages image but if one didn't want that included, it would be easy to exclude it.
So, AIs don't have to be inscrutable black boxes. They can have programmatic parameters like the existing bots and scripts that we use routinely on Misplaced Pages. Such power tools seem needed to deal with the large image backlogs that we have on Commons. Perhaps they could help by providing captions and categories where these don't exist.
They don't have to be black boxes but they are by design: they exist in a legally dubious area and thus hide what they're scraping to avoid further legal problems. That's no secret. We know for example that Misplaced Pages is a core data set for likely most AIs today. They also notoriously and quite confidently spit out a lie ("hallucinate") and frequently spit out total nonsense. Add to that that they're restricted to whatever is floating around on the internet or whatever other data set they've been fed (usually just more internet), and many specialist topics, like texts on ancient history and even standard reference works, are not accessible on the internet (despite Google's efforts). :bloodofox: (talk) 09:39, 2 January 2025 (UTC)
While its stated methodology seems sensible, there's no evidence that it actually followed that methodology. The bullet points are pretty vague, and are pretty much the default methodologies used to examine actual historical works. Chaotic Enby (talk · contribs) 17:40, 2 January 2025 (UTC)
Yes, there's evidence. As I stated above, the analysis is transparent and cites the sources that it used. And these all seem to check out rather than being invented. So, this level of AI goes beyond the first generation of LLM and addresses some of their weaknesses. I suppose that image generation is likewise being developed and improved and so we shouldn't rush to judgement while the technology is undergoing rapid development. Andrew🐉(talk) 17:28, 4 January 2025 (UTC)
Oppose blanket ban: best of luck to editors here who hope to be able to ban an entirely undefined and largely undetectable procedure. The term 'AI' as commonly used is no more than a buzzword - what exactly would be banned? And how does it improve the encyclopedia to encourage editors to object to images not simply because they are inaccurate, or inappropriate for the article, but because they subjectively look too good? Will the image creator be quizzed on Commons about the tools they used? Will creators who are transparent about what they have created have their images deleted while those who keep silent don’t? Honestly, this whole discussion is going to seem hopelessly outdated within a year at most. It’s like when early calculators were banned in exams because they were ‘cheating’, forcing students to use slide rules. MichaelMaggs (talk) 12:52, 1 January 2025 (UTC)
I am genuinely confused as to why this has turned into a discussion about a blanket ban, even though the original proposal exclusively focused on AI-generated images (the kind that is generated by an AI model from a prompt, which are already tagged on Commons, not regular images with AI enhancement or tools being used) and only in specific contexts. Not sure where the "subjectively look too good" thing even comes from, honestly. Chaotic Enby (talk · contribs) 12:58, 1 January 2025 (UTC)
That just show how ill-defined the whole area is. It seem you restrict the term 'AI-generated' to mean "images generated solely(?) from a text prompt". The question posed above has no such restriction. What a buzzword means is largely in the mind of the reader, of course, but to me and I think to many, 'AI-generated' means generated by AI. MichaelMaggs (talk) 13:15, 1 January 2025 (UTC)
I used the text prompt example because that is the most common way to have an AI model generate an image, but I recognize that I should've clarified it better. There is definitely a distinction between an image being generated by AI (like the Laurence Boccolini example below) and an image being altered or retouched by AI (which includes many features integrated in smartphones today). I don't think it's a "buzzword" to say that there is a meaningful difference between an image being made up by an AI model and a preexisting image being altered in some way, and I am surprised that many people understand "AI-generated" as including the latter. Chaotic Enby (talk · contribs) 15:24, 1 January 2025 (UTC)
Oppose as unenforceable. I just want you to imagine enforcing this policy against people who have not violated it. All this will do is allow Wikipedians who primarily contribute via text to accuse artists of using AI because they don't like the results to get their contributions taken down. I understand the impulse to oppose AI on principle, but the labor and aesthetic issues don't actually have anything to do with Misplaced Pages. If there is not actually a problem with the content conveyed by the image—for example, if the illustrator intentionally corrected any hallucinations—then someone objecting over AI is not discussing page content. If the image was not even made with AI, they are hallucinating based on prejudices that are irrelevant to the image. The bottom line is that images should be judged on their content, not how they were made. Besides all the policy-driven stuff, if Misplaced Pages's response to the creation of AI imaging tools is to crack down on all artistic contributions to Misplaced Pages (which seems to be the inevitable direction of these discussions), what does that say? Categorical bans of this kind are ill-advised and anti-illustrator. lethargilistic (talk) 15:41, 1 January 2025 (UTC)
And the same applies to photography, of course. If in my photo of a garden I notice there is a distracting piece of paper on the lawn, nobody would worry if I used the old-style clone-stamp tool to remove it in Photoshop, adding new grass in its place (I'm assuming here that I don't change details of the actual landscape in any way). Now, though, Photoshop uses AI to achieve essentially the same result while making it simpler for the user. A large proportion of all processed photos will have at least some similar but essentially undetectable "generated AI" content, even if only a small area of grass. There is simply no way to enforce the proposed policy, short of banning all high-quality photography – which requires post-processing by design, and in which similar encyclopedically non-problematic edits are commonplace. MichaelMaggs (talk) 17:39, 1 January 2025 (UTC)
Before anyone objects that my example is not "an image generated from a text prompt", note that there's no mention of such a restriction in the proposal we are discussing. Even if there were, it makes no difference. Photoshop can already generate photo-realistic areas from a text prompt. If such use is non-misleading and essentially undetectable, it's fine; if if changes the image in such a way as to make it misleading, inaccurate or non-encycpopedic in any way it can be challenged on that basis. MichaelMaggs (talk) 17:58, 1 January 2025 (UTC)
As I said previously, the text prompt is just an example, not a restriction of the proposal. The point is that you talk about editing an existing image (which is what you talk about, as you say if if changes the image), while I am talking about creating an image ex nihilo, which is what "generating" means. Chaotic Enby (talk · contribs) 18:05, 1 January 2025 (UTC)
I'm talking about a photograph with AI-generated areas within it. This is commonplace, and is targeted by the proposal. Categorical bans of the type suggested are indeed ill-advised. MichaelMaggs (talk) 18:16, 1 January 2025 (UTC)
Even if the ban is unenforceable, there are many editors who will choose to use AI images if they are allowed and just as cheerfully skip them if they are not allowed. That would mean the only people posting AI images are those who choose to break the rule and/or don't know about it. That would probably add up to many AI images not used. Darkfrog24 (talk) 22:51, 3 January 2025 (UTC)
Support blanket ban because "AI" is a fundamentally unethical technology based on the exploitation of labor, the wanton destruction of the planetary environment, and the subversion of every value that an encyclopedia should stand for. ABOUTSELF-type exceptions for "AI" output that has already been generated might be permissible, in order to document the cursed time in which we live, but those exceptions are going to be rare. How many examples of Shrimp Jesus slop do we need? XOR'easter (talk) 23:30, 1 January 2025 (UTC)
Support blanket ban - Primarily because of the "poisoning the well"/"dead internet" issues created by it. FOARP (talk) 14:30, 2 January 2025 (UTC)
Support that WP:POLICY applies to images: images should be verifiable, neutral, and absent of original research. AI is just the latest quickest way to produce images that are original, unverifiable, and potentially biased. Is anyone in their right mind saying that we allow people to game our rules on WP:OR and WP:V by using images instead of text? Shooterwalker (talk) 17:04, 3 January 2025 (UTC)
As an aside on this: in some cases Commons is being treated as a way of side-stepping WP:NOR and other restrictions. Stuff that would get deleted if it were written content on WP gets in to WP as images posted on Commons. The worst examples are those conflict maps that are created from a bunch of Twitter posts (eg the Syrian civil war one). AI-generated imagery is another field where that appears to be happening. FOARP (talk) 10:43, 4 January 2025 (UTC)
Support temporary blanket ban with a posted expiration/requred rediscussion date of no more than two years from closing. AI as the term is currently used is very, very new. Right now these images would do more harm than good, but it seems likely that the culture will adjust to them. I support an exception for the when the article is about the image itself and that image is notable, such as the photograph of the black-and-blue/gold-and-white dress in The Dress and/or examples of AI images in articles in which they are relevant. E.g. "here is what a hallucination is: count the fingers." Darkfrog24 (talk) 23:01, 3 January 2025 (UTC)
First, I think any guidance should avoid referring to specific technology, as that changes rapidly and is used for many different purposes. Second, assuming that the image in question has a suitable copyright status for use on Misplaced Pages, the key question is whether or not the reliability of the image has been established. If the intent of the image is to display 100 dots with 99 having the same appearance and 1 with a different appearance, then ordinary math skills are sufficient and so any Misplaced Pages editor can evaluate the reliability without performing original research. If the intent is to depict a likeness of a specific person, then there needs to be reliable sources indicating that the image is sufficiently accurate. This is the same for actual photographs, re-touched ones, drawings, hedcuts, and so forth. Typically this can be established by a reliable source using that image with a corresponding description or context. isaacl (talk) 17:59, 4 January 2025 (UTC)
Support Blanket Ban on AI generated imagery per most of the discussion above. It's a very slippery slope. I might consider a very narrow exception for an AI generated image of a person that was specifically authorized or commissioned by the subject. -Ad Orientem (talk) 02:45, 5 January 2025 (UTC)
Oppose blanket ban It is far too early to take an absolutist position, particularly when the potential is enormous. Misplaced Pages is already is image desert and to reject something that is only at the cusp of development is unwise. scope_creep20:11, 5 January 2025 (UTC)
Support blanket ban on AI-generated images except in ABOUTSELF contexts. An encyclopedia should not be using fake images. I do not believe that further nuance is necessary. LEPRICAVARK (talk) 22:44, 5 January 2025 (UTC)
Support blanket ban as the general guideline, as accuracy, personal rights, and intellectual rights issues are very weighty, here (as is disclosure to the reader). (I could see perhaps supporting adoption of a sub-guideline for ways to come to a broad consensus in individual use cases (carve-outs, except for BLPs) which address all the weighty issues on an individual use basis -- but that needs to be drafted and agreed to, and there is no good reason to wait to adopt the general ban in the meantime). Alanscottwalker (talk) 15:32, 8 January 2025 (UTC)
Which parts of this photo are real?
Support indefinite blanket ban except ABOUTSELF and simple abstract examples (such as the image of 99 dots above). In addition to all the issues raised above, including copyvio and creator consent issues, in cases of photorealistic images it may never be obvious to all readers exactly which elements of the image are guesswork. The cormorant picture at the head of the section reminded me of the first video of a horse in gallop, in 1878. Had AI been trained on paintings of horses instead of actual videos and used to "improve" said videos, we would've ended up with serious delusions about the horse's gait. We don't know what questions -- scientific or otherwise -- photography will be used to settle in the coming years, but we do know that consumer-grade photo AI has already been trained to intentionally fake detail to draw sales, such as on photos of the Moon. I think it's unrealistic to require contributors to take photos with expensive cameras or specially-made apps, but Misplaced Pages should act to limit its exposure to this kind of technology as far as is feasible. DaßWölf20:57, 9 January 2025 (UTC)
Support at least some sort of recomendation against the use AI generated imagery in non-AI contexts−except obviously where the topic of the article is specificly related to AI generated imagery (Generative artificial intelligence, Springfield pet-eating hoax, AI slop, etc.). At the very least the consensus bellow about BLPs should be extened to all historical biographies, as all the examples I've seen (see WP:AIIMAGE) fail WP:IMAGERELEVANCE (failing to add anything to the sourced text) and serving only to mislead the reader. We inclued images for a reason, not just for decoration. I'm also reminded the essay WP:PORTRAIT, and the distinction it makes between notable depictions of histoical people (which can be useful to illustarate articles) and non-notable fictional portraits which in its (imo well argued) view have no legitimate encyclopedic function whatsoever. Cakelot1 ☞️ talk14:36, 14 January 2025 (UTC)
Anything that fails WP:IMAGERELEVANCE can be, should be, and is, excluded from use already, likewise any images which have no legitimate encyclopedic function whatsoever. This applies to AI and none AI images equally and identically. Just as we don't have or need a policy or guideline specifically saying don't use irrelevant or otherwise non-encyclopaedic watercolour images in articles we don't need any policy or guideline specifically calling out AI - because it would (as you demonstrate) need to carve out exceptions for when it's use is relevant. Thryduulf (talk) 14:45, 14 January 2025 (UTC)
That would be an easy change; just add a sentence like "AI-generated images of individual people are primarily decorative and should not be used". We should probably do that no matter what else is decided. WhatamIdoing (talk) 23:24, 14 January 2025 (UTC)
Except that is both not true and irrelevant. Some AI-generated images of individual people are primarily decorative, but not all of them. If an image is purely decorative it shouldn't be used, regardless of whether it is AI-generated or not. Thryduulf (talk) 13:43, 15 January 2025 (UTC)
Can you give an example of an AI-generated image of an individual person that is (a) not primarily decorative and also (b) not copied from the person's social media/own publications, and that (c) at least some editors think would be a good idea?
"Hey, AI, please give me a realistic-looking photo of this person who died in the 12th century" is not it. "Hey, AI, we have no freely licensed photos of this celebrity, so please give me a line-art caricature" is not it. What is? WhatamIdoing (talk) 17:50, 15 January 2025 (UTC)
Criteria (b) and (c) were not part of the statement I was responding to, and make it a very significantly different assertion. I will assume that you are not making motte-and-bailey arguments in bad faith, but the frequent fallacious argumentation in these AI discussions is getting tiresome.
Even with the additional criteria it is still irrelevant - if no editor thinks an image is a good idea, then it won't be used in an article regardless of why they don't think it's a good idea. If some editors think an individual image is a good idea then it's obviously potentially encyclopaedic and needs to be judged on its merits (whether it is AI-generated is completely irrelevant to it's encyclopaedic value). An image that the subject uses on their social media/own publications to identify themselves (for example as an avatar) is the perfect example of the type of image which is frequently used in articles about that individual. Thryduulf (talk) 18:56, 15 January 2025 (UTC)
BLPs
CONSENSUS AGAINST
There is clear consensus against using AI-generated imagery to depict BLP subjects. Marginal cases (such as major AI enhancement or where an AI-generated image of a living person is itself notable) can be worked out on a case-by-case basis. I will add a sentence reflecting this consensus to the image use policy and the BLP policy. —Ganesha811 (talk) 14:02, 8 January 2025 (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.
Are AI-generated images (generated via text prompts, see also: text-to-image model) okay to use to depict BLP subjects? The Laurence Boccolini example was mentioned in the opening paragraph. The image was created using Grok / Aurora, a text-to-image model developed by xAI, to generate images...As with other text-to-image models, Aurora generates images from natural language descriptions, called prompts.AI-generated image of Laurence BoccoliniSome1 (talk) 12:34, 31 December 2024 (UTC)AI-generated cartoon portrait of Germán Larrea Mota-Velasco
03:58, January 3, 2025: Note: that these images can either be photorealistic in style (such as the Laurence Boccolini example) or non-photorealistic in style (see the Germán Larrea Mota-Velasco example, which was generated using DALL-E, another text-to-image model).
No. I don't think they are at all, as, despite looking photorealistic, they are essentially just speculation about what the person might look like. A photorealistic image conveys the look of something up to the details, and giving a false impression of what the person looks like (or, at best, just guesswork) is actively counterproductive. (Edit 21:59, 31 December 2024 (UTC): clarified bolded !vote since everyone else did it) Chaotic Enby (talk · contribs) 12:46, 31 December 2024 (UTC)
There are plenty of non-free images of Laurence Boccolini with which this image can be compared. Assuming at least most of those are accurate representations of them (I've never heard of them before and have no other frame of reference) the image above is similar to but not an accurate representation of them (most obviously but probably least significantly, in none of the available images are they wearing that design of glasses). This means the image should not be used to identify them unless they use it to identify themselves. It should not be used elsewhere in the article unless it has been the subject of notable commentary. That it is an AI image makes absolutely no difference to any of this. Thryduulf (talk) 16:45, 31 December 2024 (UTC)
No. Well, that was easy.They are fake images; they do not actually depict the person. They depict an AI-generated simulation of a person that may be inaccurate. Cremastra 🎄 u — c 🎄 20:00, 31 December 2024 (UTC)
No, with the caveat that its mostly on the grounds that we don't have enough information and when it comes to BLP we are required to exercise caution. If at some point in the future AI generated photorealistic simulacrums living people become mainstream with major newspapers and academic publishers it would be fair to revisit any restrictions, but in this I strongly believe that we should follow not lead. Horse Eye's Back (talk) 20:37, 31 December 2024 (UTC)
No. The use of AI-generated images to depict people (living or otherwise) is fundamentally misleading, because the images are not actually depicting the person. —pythoncoder (talk | contribs) 21:30, 31 December 2024 (UTC)
Yes, when that image is an accurate representation and better than any available alternative, used by the subject to represent themselves, or the subject of notable commentary. However, as these are the exact requirements to use any image to represent a BLP subject this is already policy. Thryduulf (talk) 21:46, 31 December 2024 (UTC)
How well can we determine how accurate a representation it is? Looking at the example above, I'd argue that the real Laurence Boccolini has a somewhat rounder/pointier chin, a wider mouth, and possibly different eye wrinkles, although the latter probably depends quite a lot on the facial expression.
How well can we determine how accurate a representation it is? in exactly the same way that we can determine whether a human-crafted image is an accurate representation. How accurate a representation any image is is ultimately a matter of editor opinion. Whether an image is AI or not is irrelevant. I agree the example image above is not sufficiently accurate, but we wouldn't ban photoshopped images because one example was not deemed accurate enough, because we are rational people who understand that one example is not representative of an entire class of images - at least when the subject is something other than AI. Thryduulf (talk) 23:54, 31 December 2024 (UTC)
I think except in a few exceptional circumstances of actual complex restorations, human photoshopping is not going to change or distort a person's appearance in the same way an AI image would. Modifications done by a person who is paying attention to what they are doing and merely enhancing an image, by person who is aware, while they are making changes, that they might be distorting the image and is, I only assume, trying to minimise it – those careful modifications shouldn't be equated with something made up by an AI image generator. Cremastra 🎄 u — c 🎄 00:14, 1 January 2025 (UTC)
A photo of a person can be connected to a specific time, place, and subject that existed. It can be compared to other images sharing one or more of those properties. A photo that was PhotoShopped is still either a generally faithful reproduction of a scene that existed, or has significant alterations that can still be attributed to a human or at least to a specific algorithm, e.g. filters. The artistic license of a painting can still be attributed to a human and doesn't run much risk of being misidentified as real, unless it's by Chuck Close et al. An AI-generated image cannot be connected to a particular scene that ever existed and cannot be attributable to a human's artistic license (and there is legal precedent that such images are not copyrightable to the prompter specifically because of this). Individual errors in a human-generated artwork are far more predictable, understandable, identifiable, traceable... than those in AI-generated images. We have innate assumptions when we encounter real images or artwork that are just not transferable. These are meaningful differences to the vast majority of people: according to a Getty poll, 87% of respondents want AI-generated art to at least be transparent, and 98% consider authentic images "pivotal in establishing trust". And even if you disagree with all that, can you not see the larger problem of AI images on Misplaced Pages getting propagated into generative AI corpora? JoelleJay (talk) 04:20, 2 January 2025 (UTC)
I agree that our old assumptions don't hold true. I think the world will need new assumptions. We will probably have those in place in another decade or so.
Absolutely no fake/AI images of people, photorealistic or otherwise. How is this even a question? These images are fake. Readers need to be able to trust Misplaced Pages, not navigate around whatever junk someone has created with a prompt and presented as somehow representative. This includes text. :bloodofox: (talk) 22:24, 31 December 2024 (UTC)
For the requested clarification by Some1, no AI-generated images (except when the image itself is specifically discussed in the article, and even then it should not be the lead image and it should be clearly indicated that the image is AI-generated), no drawings, no nothing of that sort. Actual photographs of the subject, nothing else. Articles are not required to have images at all; no image whatsoever is preferable to something which is not an image of the person. Seraphimblade05:42, 3 January 2025 (UTC)
No, but with exceptions. I could imagine a case where a specific AI-generated image has some direct relevance to the notability of the subject of a BLP. In such cases, it should be included, if it could be properly licensed. But I do oppose AI-generated images as portraits of BLP subjects. —David Eppstein (talk) 01:27, 1 January 2025 (UTC)
Since I was pinged on this point: when I wrote "I do oppose AI-generated images as portraits", I meant exactly that, including all AI-generated images, such as those in a sketchy or artistic style, not just the photorealistic ones. I am not opposed to certain uses of AI-generated images in BLPs when they are not the main portrait of the subject, for instance in diagrams (not depicting the subject) to illustrate some concept pioneered by the subject, or in case someone becomes famous for being the subject of an AI-generated image. —David Eppstein (talk) 05:41, 3 January 2025 (UTC)
No, and no exceptions or do-overs. Better to have no images (or Stone-Age style cave paintings) than Frankenstein images, no matter how accurate or artistic. Akin to shopped manipulated photographs, they should have no room (or room service) at the WikiInn. Randy Kryn (talk) 01:34, 1 January 2025 (UTC)
Some "shopped manipulated photographs" are misleading and inaccurate, others are not. We can and do exclude the former from the parts of the encyclopaedia where they don't add value without specific policies and without excluding them where they are relevant (e.g. Photograph manipulation) or excluding those that are not misleading or inaccurate. AI images are no different. Thryduulf (talk) 02:57, 1 January 2025 (UTC)
Assuming we know. Assuming it's material. The infobox image in – and the only extant photo of – Blind Lemon Jefferson was "photoshopped" by a marketing team, maybe half a century before Adobe Photoshop was created. They wanted to show him wearing a necktie. I don't think that this level of manipulation is actually a problem. WhatamIdoing (talk) 07:44, 2 January 2025 (UTC)
No Not at all relevant for pictures of people, as the accuracy is not enough and can misrepresent. Also (and I'm shocked as it seems no one has mentioned this), what about Copyright issues? Who holds the copyright for an AI-generated image? The user who wrote the prompt? The creator(s) of the AI model? The creator(s) of the images in the database that the AI used to create the images? It's sounds to me such a clusterfuck of copyright issues that I don't understand how this is even a discussion. --SuperJew (talk) 07:10, 1 January 2025 (UTC)
Under the US law / copyright office, machine-generated images including those by AI cannot be copyrighted. That also means that AI images aren't treated as derivative works. What is still under legal concern is whether the use of bodies of copyrighted works without any approve or license from the copyright holders to train AI models is under fair use or not. There are multiple court cases where this is the primary challenge, and none have yet to reach a decision yet. Assuming the courts rule that there was no fair use, that would either require the entity that owns the AI to pay fines and ongoing licensing costs, or delete their trained model to start afresh with free licensed/works, but in either case, that would not impact how we'd use any resulting AI image from a copyright standpoint. — Masem (t) 14:29, 1 January 2025 (UTC)
No, I'm in agreeance with Seraphimblade here. Whether we like it or not, the usage of a portrait on an article implies that it's just that, a portrait. It's incredibly disingenuous to users to represent an AI generated photo as truth. Doawk7 (talk) 09:32, 1 January 2025 (UTC)
So you just said a portrait can be used because wikipedia tells you it's a portrait, and thus not a real photo. Can't AI be exactly the same? As long as we tell readers it is an AI representation? Heck, most AI looks closer to the real thing than any portrait. Fyunck(click) (talk) 10:07, 2 January 2025 (UTC)
To clarify, I didn't mean "portrait" as in "painting," I meant it as "photo of person."
However, I really want to stick to what you say at the end there: Heck, most AI looks closer to the real thing than any portrait.
That's exactly the problem: by looking close to the "real thing" it misleads users into believing a non-existent source of truth.
Per the wording of the RfC of "depict BLP subjects," I don't think there would be any valid case to utilize AI images. I hold a strong No. Doawk7 (talk) 04:15, 3 January 2025 (UTC)
No. We should not use AI-generated images for situations like this, they are basically just guesswork by a machine as Quark said and they can misinform readers as to what a person looks like. Plus, there's a big grey area regarding copyright. For an AI generator to know what somebody looks like, it has to have photos of that person in its dataset, so it's very possible that they can be considered derivative works or copyright violations. Using an AI image (derivative work) to get around the fact that we have no free images is just fair use with extra steps. Di (they-them) (talk) 19:33, 1 January 2025 (UTC)Gisèle Pelicot?
Maybe There was a prominent BLP image which we displayed on the main page recently. (right) This made me uneasy because it was an artistic impression created from photographs rather than life. And it was "colored digitally". Functionally, this seems to be exactly the same sort of thing as the Laurence Boccolini composite. The issue should not be whether there's a particular technology label involved but whether such creative composites and artists' impressions are acceptable as better than nothing. Andrew🐉(talk) 08:30, 1 January 2025 (UTC)
Except it is clear to everyone that the illustration to the right is a sketch, a human rendition, while in the photorealistic image above, it is less clear. Cremastra (u — c) 14:18, 1 January 2025 (UTC)
Except it says right below it "AI-generated image of Laurence Boccolini." How much more clear can it be when it say point-blank "AI-generated image." Fyunck(click) (talk) 10:12, 2 January 2025 (UTC)
People taking a quick glance at an infobox image that looks pretty like a photograph are not going to scrutinize commons tagging. Cremastra (u — c) 14:15, 2 January 2025 (UTC)
Keep in mind that many AIs can produce works that match various styles, not just photographic quality. It is still possible for AI to produce something that looks like a watercolor or sketched drawing. — Masem (t) 14:33, 1 January 2025 (UTC)
Same thing I wrote above, but for "photoshopping" read "drawing": (Bold added for emphasis)
...human is not going to change or distort a person's appearance in the same way an AI image would. done by a person who is paying attention to what they are doing by person who is aware, while they are making , that they might be distorting the image and is, I only assume, trying to minimise it – those careful modifications shouldn't be equated with something made up by an AI image generator.Cremastra (u — c) 20:56, 1 January 2025 (UTC)
@Cremastra then why are you advocating for a ban on AI images rather than a ban on distorted images? Remember that with careful modifications by someone who is aware of what they are doing that AI images can be made more accurate. Why are you assuming that a human artist is trying to minimise the distortions but someone working with AI is not? Thryduulf (talk) 22:12, 1 January 2025 (UTC)
I believe that AI-generated images are fundamentally misleading because they are a simulation by a machine rather than a drawing by a human. To quote pythoncoder above: The use of AI-generated images to depict people (living or otherwise) is fundamentally misleading, because the images are not actually depicting the person.Cremastra (u — c) 00:16, 2 January 2025 (UTC)
Once again your actual problem is not AI, but with misleading images. Which can be, and are, already a violation of policy. Thryduulf (talk) 01:17, 2 January 2025 (UTC)
I think all AI-generated images, except simple diagrams as WhatamIdoing point out above, are misleading. So yes, my problem is with misleading images, which includes all photorealistic images generated by AI, which is why I support this proposal for a blanket ban in BLPs and medical articles. Cremastra (u — c) 02:30, 2 January 2025 (UTC)
Despite the fact that not all AI-generated images are misleading, not all misleading images are AI-generated and it is not always possible to tell whether an image is or is not AI-generated? Thryduulf (talk) 02:58, 2 January 2025 (UTC)
Enforcement is a separate issue. Whether or not all (or the vast majority) of AI images are misleading is the subject of this dispute.
I'm not going to mistreat the horse further, as we've each made our points and understand where the other stands. Cremastra (u — c) 15:30, 2 January 2025 (UTC)
Even "simple diagrams" are not clear-cut. The process of AI-generating any image, no matter how simple, is still very complex and can easily follow any number of different paths to meet the prompt constraints. These paths through embedding space are black boxes and the likelihood they converge on the same output is going to vary wildly depending on the degrees of freedom in the prompt, the dimensionality of the embedding space, token corpus size, etc. The only thing the user can really change, other than switching between models, is the prompt, and at some point constructing a prompt that is guaranteed to yield the same result 100% of the time becomes a Borgesian exercise. This is in contrast with non-generative AI diagram-rendering software that follow very fixed, reproducible, known paths. JoelleJay (talk) 04:44, 2 January 2025 (UTC)
Why does the path matter? If the output is correct it is correct no matter what route was taken to get there. If the output is incorrect it is incorrect no matter what route was taken to get there. If it is unknown or unknowable whether the output is correct or not that is true no matter what route was taken to get there. Thryduulf (talk) 04:48, 2 January 2025 (UTC)
If I use BioRender or GraphPad to generate a figure, I can be confident that the output does not have errors that would misrepresent the underlying data. I don't have to verify that all 18,000 data points in a scatter plot exist in the correct XYZ positions because I know the method for rendering them is published and empirically validated. Other people can also be certain that the process of getting from my input to the product is accurate and reproducible, and could in theory reconstruct my raw data from it. AI-generated figures have no prescribed method of transforming input beyond what the prompt entails; therefore I additionally have to be confident in how precise my prompt is and confident that the training corpus for this procedure is so accurate that no error-producing paths exist (not to mention absolutely certain that there is no embedded contamination from prior prompts). Other people have all those concerns, and on top of that likely don't have access to the prompt or the raw data to validate the output, nor do they necessarily know how fastidious I am about my generative AI use. At least with a hand-drawn diagram viewers can directly transfer their trust in the author's knowledge and reliability to their presumptions about the diagram's accuracy. JoelleJay (talk) 05:40, 2 January 2025 (UTC)
The original "simple geometric diagrams" comment was referring to your 100 dots image. I don't think increasing the dots materially changes the discussion beyond increasing the laboriousness of verifying the accuracy of the image. Photos of Japan (talk) 07:56, 2 January 2025 (UTC)
Yes, but since "the laboriousness of verifying the accuracy of the image" is exactly what she doesn't want to undertake for 18,000 dots, then I think that's very relevant. WhatamIdoing (talk) 07:58, 2 January 2025 (UTC)
And where is that cutoff supposed to be? 1000 dots? A single straight line? An atomic diagram? What is "simple" to someone unfamiliar with a topic may be more complex.And I don't want to count 100 dots either! JoelleJay (talk) 17:43, 2 January 2025 (UTC)
Maybe you don't. But I know for certain that you can count 10 across, 10 down, and multiply those two numbers to get 100. That's what I did when I made the image, after all. WhatamIdoing (talk) 07:44, 3 January 2025 (UTC)
Comment: when you Google search someone (at least from the Chrome browser), often the link to the Misplaced Pages article includes a thumbnail of the lead photo as a preview. Even if the photo is labelled as an AI image in the article, people looking at the thumbnail from Google would be misled (if the image is chosen for the preview). Photos of Japan (talk) 09:39, 1 January 2025 (UTC)
This is why we should not use inaccurate images, regardless of how the image was created. It has absolutely nothing to do with AI. Thryduulf (talk) 11:39, 1 January 2025 (UTC)
Already opposed a blanket ban: It's unclear to me why we have a separate BLP subsection, as BLPs are already included in the main section above. Anyway, I expressed my views there. MichaelMaggs (talk)
No For at least now, let's not let the problems of AI intrude into BLP articles which need to have the highest level of scrutiny to protect the person represented. Other areas on WP may benefit from AI image use, but let's keep it far out of BLP at this point. --Masem (t) 14:35, 1 January 2025 (UTC)
I am not a fan of “banning” AI images completely… but I agree that BLPs require special handling. I look at AI imagery as being akin to a computer generated painting. In a BLP, we allow paintings of the subject, but we prefer photos over paintings (if available). So… we should prefer photos over AI imagery. That said, AI imagery is getting good enough that it can be mistaken for a photo… so… If an AI generated image is the only option (ie there is no photo available), then the caption should clearly indicate that we are using an AI generated image. And that image should be replaced as soon as possible with an actual photograph. Blueboar (talk) 14:56, 1 January 2025 (UTC)
The issue with the latter is that Misplaced Pages images get picked up by Google and other search engines, where the caption isn't there anymore to add the context that a photorealistic image was AI-generated. Chaotic Enby (talk · contribs) 15:27, 1 January 2025 (UTC)
We're here to build an encyclopedia, not to protect commercial search engine companies.
I think my view aligns with Blueboar's (except that I find no firm preference for photos over classical portrait paintings): We shouldn't have inaccurate AI images of people (living or dead). But the day appears to be coming when AI will generate accurate ones, or at least ones that are close enough to accurate that we can't tell the difference unless the uploader voluntarily discloses that information. Once we can no longer tell the difference, what's the point in banning them? Images need to look like the thing being depicted. When we put an photorealistic image in an article, we could be said to be implicitly claiming that the image looks like whatever's being depicted. We are not necessarily warranting that the image was created through a specific process, but the image really does need to look like the subject. WhatamIdoing (talk) 03:12, 2 January 2025 (UTC)
You are presuming that sufficient accuracy will prevent us from knowing whether someone is uploading an AI photo, but that is not the case. For instance, if someone uploads large amounts of "photos" of famous people, and can't account for how they got them (e.g. can't give a source where they scraped them from, or dates or any Exif metadata at all for when they were taken), then it will still be obvious that they are likely using AI. Photos of Japan (talk) 17:38, 3 January 2025 (UTC)
As another editor pointed out in their comment, there's the ethics/moral dilemma of creating fake photorealistic pictures of people and putting them on the internet, especially on a site such as Misplaced Pages and especially on their own biography. WP:BLP says the bios must be written conservatively and with regard for the subject's privacy.Some1 (talk) 18:37, 3 January 2025 (UTC)
Once we can no longer tell the difference, what's the point in banning them? Sounds like a wolf's in sheep's clothing to me. Just because the surface appeal of fake pictures gets better, doesn't mean we should let the horse in. Cremastra (u — c) 18:47, 3 January 2025 (UTC)
If there are no appropriately-licensed images of a person, then by definition any AI-generated image of them will be either a copyright infringement or a complete fantasy. JoelleJay (talk) 04:48, 2 January 2025 (UTC)
Whether it would be a copyright infringement or not is both an unsettled legal question and not relevant: If an image is a copyvio we can't use it and it is irrelevant why it is a copyvio. If an image is a "complete fantasy" then it is exactly as unusable as a complete fantasy generated by non-AI means, so again AI is irrelevant. I've had to explain this multiple times in this discussion, so read that for more detail and note the lack of refutation. Thryduulf (talk) 04:52, 2 January 2025 (UTC)
Ooooh, I'm not sure that we can assume that humans aren't blatantly copying something. We can assume that they meant to be helpful, but that's not quite the same thing. WhatamIdoing (talk) 07:48, 2 January 2025 (UTC)
What this conversation is really circling around is banning entire skillsets from contributing to Misplaced Pages merely because some of us are afraid of AI images and some others of us want to engineer a convenient, half-baked, policy-level "consensus" to point to when they delete quality images from Misplaced Pages. Every time someone generates text based on a source, they are doing some acceptable level of interpretation to extract facts or rephrase it around copyright law, and I don't think illustrations should be considered so severely differently as to justify a categorical ban. For instance, the Gisele Pelicot portrait is based on non-free photos of her. Once the illustration exists, it is trivial to compare it to non-free images to determine if it is an appropriate likeness, which it is. That's no different than judging contributed text's compliance with fact and copyright by referring to the source. It shouldn't be treated differently just because most Wikipedians contribute via text. Additionally, referring to interpretive skillsets that synthesize new information like, random example, statistical analysis. Excluding those from Misplaced Pages is current practice and not controversial. Meanwhile, I think the ability to create images is more fundamental than that. It's not (inheretly) synthesizing new information. A portrait of a person (alongside the other examples in this thread) contains verifiable information. It is current practice to allow them to fill the gaps where non-free photos can't. That should continue. Honestly, it should expand.
Additionally, in direct response to "these images are fake": All illustrations of a subject could be called "fake" because they are not photographs. (Which can also be faked.) The standard for the inclusion of an illustration on Misplaced Pages has never been photorealism, medium, or previous publication in a RS. The standard is how adequately it reflects the facts which it claims to depict. If there is a better image that can be imported to Misplaced Pages via fair use or a license, then an image can be easily replaced. Until such a better image has been sourced, it is absolutely bewildering to me that we would even discuss removing images of people from their articles. What a person looked like is one of the most basic things that people want to know when they look someone up on Misplaced Pages. Including an image of almost any quality (yes, even a cartoon) is practically by definition an improvement to the article and addressing an important need. We should be encouraging artists to continue filling the gaps that non-free images cannot fill, not creating policies that will inevitably expand into more general prejudices against all new illustrations on Misplaced Pages. lethargilistic (talk) 15:59, 1 January 2025 (UTC)
By "Oppose", I'm assuming your answer to the RfC question is "Yes". And this RfC is about using AI-generated images (generated via text prompts, see also: text-to-image model) to depict BLP subjects, not regarding human-created drawings/cartoons/sketches, etc. of BLPs. Some1 (talk) 16:09, 1 January 2025 (UTC)
I've changed it to "yes" to reflect the reversed question. I think all of this is related because there is no coherent distinguishing point; AI can be used to create images in a variety of styles. These discussions have shown that a policy of banning AI images will be used against non-AI images of all kinds, so I think it's important to say these kinds of things now. lethargilistic (talk) 16:29, 1 January 2025 (UTC)
Photorealistic images scraped from who knows where from who knows what sources are without question simply fake photographs and also clear WP:OR and outright WP:SYNTH. There's no two ways about it. Articles do not require images: An article with some Frankenstein-ed image scraped from who knows what, where and, when that you "created" from a prompt is not an improvement over having no image at all. If we can't provide a quality image (like something you didn't cook up from a prompt) then people can find quality, non-fake images elsewhere. :bloodofox: (talk) 23:39, 1 January 2025 (UTC)
I really encourage you to read the discussion I linked before because it is on the WP:NOR talk page. Images like these do not inherently include either OR or SYNTH, and the arguments that they do cannot be distinguished from any other user-generated image content. But, briefly, I never said articles required images, and this is not about what articles require. It is about improvements to the articles. Including a relevant picture where none exists is almost always an improvement, especially for subjects like people. Your disdain for the method the person used to make an image is irrelevant to whether the content of the image is actually verifiable, and the only thing we ought to care about is the content. lethargilistic (talk) 03:21, 2 January 2025 (UTC)
Images like these are absolutely nothing more than synthesis in the purest sense of the world and are clearly a violation of WP:SYNTH: Again, you have no idea what data was used to generate these images and you're going to have a very hard time convincing anyone to describe them as anything other than outright fakes.
A reminder that WP:SYNTH shuts down attempts at manipulation of images ("It is not acceptable for an editor to use photo manipulation to distort the facts or position illustrated by an image. Manipulated images should be prominently noted as such. Any manipulated image where the encyclopedic value is materially affected should be posted to Misplaced Pages:Files for discussion. Images of living persons must not present the subject in a false or disparaging light.") and generating a photorealistic image (from who knows what!) is far beyond that.
Fake images of people do not improve our articles in any way and only erode reader trust. What's next, an argument for the fake sources LLMs also love to "hallucinate"? :bloodofox: (talk) 03:37, 2 January 2025 (UTC)
So, if you review the first sentence of SYNTH, you'll see it has no special relevance to this discussion: Do not combine material from multiple sources to state or imply a conclusion not explicitly stated by any of the sources.. My primary example has been a picture of a person; what a person looks like is verifiable by comparing the image to non-free images that cannot be used on Misplaced Pages. If the image resembles the person, it is not SYNTH. An illustration of a person created and intended to look like that person is not a manipulation. The training data used to make the AI is irrelevant to whether the image in fact resembles the person. You should also review WP:NOTSYNTH because SYNTH is not a policy; NOR is the policy: If a putative SYNTH doesn't constitute original research, then it doesn't constitute SYNTH. Additionally, not all synthesis is even SYNTH. A categorical rule against AI cannot be justified by SYNTH because it does not categorically apply to all use cases of AI. To do so would be illogical on top of ill-advised. lethargilistic (talk) 08:08, 2 January 2025 (UTC)
"training data used to make the AI is irrelevant" — spoken like a true AI evangelist! Sorry, 'good enough' photorealism is still just synthetic slop, a fake image presented as real of a human being. A fake image of someone generated from who-knows-what that 'resembles' an article's subject is about as WP:SYNTH as it gets. Yikes. As for the attempts to pass of prompt-generated photorealistic fakes of people as somehow the same as someone's illustration, you're completely wasting your time. :bloodofox: (talk) 09:44, 2 January 2025 (UTC)
NOR is a content policy and SYNTH is content guidance within NOR. Because you have admitted that this is not about the content for you, NOR and SYNTH are irrelevant to your argument, which boils down to WP:IDONTLIKEIT and, now, inaccurate personal attacks. Continuing this discussion between us would be pointless. lethargilistic (talk) 09:52, 2 January 2025 (UTC)
This is in fact entirely about content (why the hell else would I bother?) but it is true that I also dismissed your pro-AI 'it's just like a human drawing a picture!' as outright nonsense a while back. Good luck convincing anyone else with that line - it didn't work here. :bloodofox: (talk) 09:59, 2 January 2025 (UTC)
Maybe: there is an implicit assumption with this RFC that an AI generated image would be photorealistic. There hasn't been any discussion of an AI generated sketch. If you asked an AI to generate a sketch (that clearly looked like a sketch, similar to the Gisèle Pelicot example) then I would potentially be ok with it. Photos of Japan (talk) 18:14, 1 January 2025 (UTC)
That's an interesting thought to consider. At the same time, I worry about (well-intentioned) editors inundating image-less BLP articles with AI-generated images in the style of cartoons/sketches (if only photorealistic ones are prohibited) etc. At least requiring a human to draw/paint/whatever creates a barrier to entry; these AI-generated images can be created in under a minute using these text-to-image models. Editors are already wary about human-created cartoon portraits (see the NORN discussion), now they'll be tasked with dealing with AI-generated ones in BLP articles. Some1 (talk) 20:28, 1 January 2025 (UTC)
It sounds like your problem is not with AI but with cartoon/sketch images in BLP articles, so AI is once again completely irrelevant. Thryduulf (talk) 22:14, 1 January 2025 (UTC)
That is a good concern you brought up. There is a possibility of the spamming of low quality AI-generated images which would be laborious to discuss on a case-by-case basis but easy to generate. At the same time though that is a possibility, but not yet an actuality, and WP:CREEP states that new policies should address current problems rather than hypothetical concerns. Photos of Japan (talk) 22:16, 1 January 2025 (UTC)
Easy no for me. I am not against the use of AI images wholesale, but I do think that using AI to represent an existent thing such as a person or a place is too far. Even a tag wouldn't be enough for me. Cessaune19:05, 1 January 2025 (UTC)
No obviously, per previous discussions about cartoonish drawn images in BLPs. Same issue here as there, it is essentially original research and misrepresentation of a living person's likeness. Zaathras (talk) 22:19, 1 January 2025 (UTC)
No to photorealistic, no to cartoonish... this is not a hard choice. The idea that "this has nothing to do with AI" when "AI" magnifies the problem to stupendous proportions is just not tenable. XOR'easter (talk) 23:36, 1 January 2025 (UTC)
While AI might "amplify" the thing you dislike, that does not make AI the problem. The problem is whatever underlying thing is being amplified. Thryduulf (talk) 01:16, 2 January 2025 (UTC)
That is arguable, but banning the amplifier does not do anything to solve the problem. In this case, banning the amplifier would cause multiple other problems that nobody supporting this proposal as even attempted to address, let alone mitigate. Thryduulf (talk) 03:04, 2 January 2025 (UTC)
No - We should not be hosting faked images (except as notable fakes). We should also not be hosting copyvios ("Whether it would be a copyright infringement or not is both an unsettled legal question and not relevant" is just totally wrong - we should be steering clear of copyvios, and if the issue is unsettled then we shouldn't use them until it is).
If people upload faked images to WP or Commons the response should be as it is now. The fact that fakes are becoming harder to detect simply from looking at them hardly affects this - we simply confirm when the picture was supposed to have been taken and examine the plausibility of it from there. FOARP (talk) 14:39, 2 January 2025 (UTC) FOARP (talk) 14:39, 2 January 2025 (UTC)
we should be steering clear of copyvio we do - if an image is a copyright violation it gets deleted, regardless of why it is a copyright violation. What we do not do is ban using images that are not copyright violations because they are copyright violations. Currently the WMF lawyers and all the people on Commons who know more about copyright than I do say that at least some AI images are legally acceptable for us to host and use. If you want to argue that, then go ahead, but it is not relevant to this discussion.
if people upload faked images the response should be as it is now in other words you are saying that the problem is faked images not AI, and that current policies are entirely adequate to deal with the problem of faked images. So we don't need any specific rules for AI images - especially given that not all AI images are fakes. Thryduulf (talk) 15:14, 2 January 2025 (UTC)
The idea that current policies are entirely adequate is like saying that a lab shouldn't have specific rules about wearing eye protection when it already has a poster hanging on the wall that says "don't hurt yourself". XOR'easter (talk) 18:36, 2 January 2025 (UTC)
"in other words you are saying that the problem is faked images not AI" - AI generated images *are* fakes. This is merely confirming that for the avoidance of doubt.
"at least some AI images are legally acceptable for us" - Until they decide which ones that isn't much help. FOARP (talk) 19:05, 2 January 2025 (UTC)
Those specific rules exist because generic warnings have proven not to be sufficient. Nobody has presented any evidence that the current policies are not sufficient, indeed quite the contrary. Thryduulf (talk) 19:05, 2 January 2025 (UTC)
Noting that I think that no AI-generated images are acceptable in BLP articles, regardless of whether they are photorealistic or not. JuxtaposedJacob (talk) | :) | he/him | 15:40, 3 January 2025 (UTC)
No, unless the AI image has encyclopedic significance beyond "depicts a notable person". AI images, if created by editors for the purpose of inclusion in Misplaced Pages, convey little reliable information about the person they depict, and the ways in which the model works are opaque enough to most people as to raise verifiability concerns. ModernDayTrilobite (talk • contribs) 15:25, 2 January 2025 (UTC)
To clarify, do you object to uses of an AI image in a BLP when the subject uses that image for self-identification? I presume that AI images that have been the subject of notable discussion are an example of "significance beyond depict a notable person"? Thryduulf (talk) 15:54, 2 January 2025 (UTC)
If the subject uses the image for self-identification, I'd be fine with it - I think that'd be analogous to situations such as "cartoonist represented by a stylized self-portrait", which definitely has some precedent in articles like Al Capp. I agree with your second sentence as well; if there's notable discussion around a particular AI image, I think it would be reasonable to include that image on Misplaced Pages. ModernDayTrilobite (talk • contribs) 19:13, 2 January 2025 (UTC)
No, with obvious exceptions, including if the subject theyrself uses the image as a their representation, or if the image is notable itself. Not including the lack of a free aleternative, if there is no free alternative... where did the AI find data to build an image... non free too. Not including images generated by WP editors (that's kind of original research... - Nabla (talk) 18:02, 2 January 2025 (UTC
Maybe I think the question is unfair as it is illustrated with what appears to be a photo of the subject but isn't. People are then getting upset that they've been misled. As others note, there are copyright concerns with AI reproducing copyrighted works that in turn make an image that is potentially legally unusable. But that is more a matter for Commons than for Misplaced Pages. As many have noted, a sketch or painting never claims to be an accurate depiction of a person, and I don't care if that sketch or painting was done by hand or an AI prompt. I strongly ask Some1 to abort the RFC. You've asked people to give a yes/no vote to what is a more complex issue. A further problem with the example used is the unfortunate prejudice on Misplaced Pages against user-generated content. While the text-generated AI of today is crude and random, there will come a point where many professionally published photos illustrating subjects, including people, are AI generated. Even today, your smartphone can create a groupshot where everyone is smiling and looking at the camera. It was "trained" on the 50 images it quickly took and responded to the build-in "text prompt" of "create a montage of these photos such that everyone is smiling and looking at the camera". This vote is a knee jerk reaction to content that is best addressed by some other measure (such as that it is a misleading image). And a good example of asking people to vote way too early, when the issues haven't been throught out -- Colin°18:17, 2 January 2025 (UTC)
No This would very likely set a dangerous precedent. The only exception I think should be if the image itself is notable. If we move forward with AI images, especially for BLPs, it would only open up a whole slew of regulations and RfCs to keep them in check. Better no image than some digital multiverse version of someone that is "basically" them but not really. Not to mention the ethics/moral dilemma of creating fake photorealistic pictures of people and putting them on the internet. Tepkunset (talk) 18:31, 2 January 2025 (UTC)
No. LLMs don't generate answers, they generate things that look like answers, but aren't; a lot of the time, that's good enough, but sometimes it very much isn't. It's the same issue for text-to-image models: they don't generate photos of people, they generate things that look like photos. Using them on BLPs is unacceptable. DS (talk) 19:30, 2 January 2025 (UTC)
No. I would be pissed if the top picture of me on Google was AI-generated. I just don't think it's moral for living people. The exceptions given above by others are okay, such as if the subject uses the picture themselves or if the picture is notable (with context given). win8x (talk) 19:56, 2 January 2025 (UTC)
No. Uploading alone, although mostly a Commons issue, would already a problem to me and may have personality rights issues. Illustrating an article with a fake photo (or drawing) of a living person, even if it is labeled as such, would not be acceptable. For example, it could end up being shown by search engines or when hovering over a Misplaced Pages link, without the disclaimer. ~ ToBeFree (talk) 23:54, 2 January 2025 (UTC)
I was going to say no... but we allow paintings as portraits in BLPs. What's so different between an AI generated image, and a painting? Arguments above say the depiction may not be accurate, but the same is true of some paintings, right? (and conversely, not true of other paintings) ProcrastinatingReader (talk) 00:48, 3 January 2025 (UTC)
A painting is clearly a painting; as such, the viewer knows that it is not an accurate representation of a particular reality. An AI-generated image made to look exactly like a photo, looks like a photo but is not.
Not all paintings are clearly paintings. Not all AI-generated images are made to look like photographs. Not all AI-generated images made to look like photos do actually look like photos. This proposal makes no distinction. Thryduulf (talk) 02:55, 3 January 2025 (UTC)
Not to mention, hyper-realism is a style an artist may use in virtually any medium. Colored pencils can be used to make extremely realistic portraits. If Misplaced Pages would accept an analog substitute like a painting, there's no reason Misplaced Pages shouldn't accept an equivalent painting made with digital tools, and there's no reason Misplaced Pages shouldn't accept an equivalent painting made with AI. That is, one where any obvious defects have been edited out and what remains is a straightforward picture of the subject. lethargilistic (talk) 03:45, 3 January 2025 (UTC)
For the record (and for any media watching), while I personally find it fascinating that a few editors here are spending a substantial amount of time (in the face of an overwhelming 'absolutely not' consensus no less) attempting to convince others that computer-generated (that is, faked) photos of human article subjects are somehow a good thing, I also find it interesting that these editors seem to express absolutely no concern for the intensely negative reaction they're already seeing from their fellow editors and seem totally unconcerned about the inevitable trust drop we'd experience from Misplaced Pages readers when they would encounter fake photos on our BLP articles especially. :bloodofox: (talk) 03:54, 3 January 2025 (UTC)
Misplaced Pages's reputation would not be affected positively or negatively by expanding the current-albeit-sparse use of illustrations to depict subjects that do not have available pictures. In all my writing about this over the last few days, you are the only one who has said anything negative about me as a person or, really, my arguments themselves. As loath as I am to cite it, WP:AGF means assuming that people you disagree with are not trying to hurt Misplaced Pages. Thryduulf, I, and others have explained in detail why we think our ultimate ideas are explicit benefits to Misplaced Pages and why our opposition to these immediate proposals comes from a desire to prevent harm to Misplaced Pages. I suggest taking a break to reflect on that, matey. lethargilistic (talk) 04:09, 3 January 2025 (UTC)
Look, I don't know if you've been living under a rock or what for the past few years but the reality is that people hate AI images and dumping a ton of AI/fake images on Misplaced Pages, a place people go for real information and often trust, inevitably leads to a huge trust issue, something Misplaced Pages is increasingly suffering from already. This is especially a problem when they're intended to represent living people (!). I'll leave it to you to dig up the bazillion controversies that have arisen and continue to arise since companies worldwide have discovered that they can now replace human artists with 'AI art' produced by "prompt engineers" but you can't possibly expect us to ignore that reality when discussing these matters. :bloodofox: (talk) 04:55, 3 January 2025 (UTC)
Those trust issues are born from the publication of hallucinated information. I have only said that it should be OK to use an image on Misplaced Pages when it contains only verifiable information, which is the same standard we apply to text. That standard is and ought to be applied independently of the way the initial version of an image was created. lethargilistic (talk) 06:10, 3 January 2025 (UTC)
To my eye, the distinction between AI images and paintings here is less a question of medium and more of verifiability: the paintings we use (or at least the ones I can remember) are significant paintings that have been acknowledged in sources as being reasonable representations of a given person. By contrast, a purpose-generated AI image would be more akin to me painting a portrait of somebody here and now and trying to stick that on their article. The image could be a faithful representation (unlikely, given my lack of painting skills, but let's not get lost in the metaphor), but if my painting hasn't been discussed anywhere besides Misplaced Pages, then it's potentially OR or UNDUE to enshrine it in mainspace as an encyclopedic image. ModernDayTrilobite (talk • contribs) 05:57, 3 January 2025 (UTC)
An image contains a collection of facts, and those facts need to be verifiable just like any other information posted on Misplaced Pages. An image that verifiably resembles a subject as it is depicted in reliable sources is categorically not OR. Discussion in other sources is not universally relevant; we don't restrict ourselves to only previously-published images. If we did that, Misplaced Pages would have very few images. lethargilistic (talk) 06:18, 3 January 2025 (UTC)
Verifiable how? Only by the editor themselves comparing to a real photo (which was probably used by the LLM to create the image…).
Verifiable by comparing them to a reliable source. Exactly the same as what we do with text. There is no coherent reason to treat user-generated images differently than user-generated text, and the universalist tenor of this discussion has damaging implications for all user-generated images regardless of whether they were created with AI. Honestly, I rarely make arguments like this one, but I think it could show some intuition from another perspective: Imagine it's 2002 and Misplaced Pages is just starting. Most users want to contribute text to the encyclopedia, but there is a cadre of artists who want to contribute pictures. The text editors say the artists cannot contribute ANYTHING to Misplaced Pages because their images that have not been previously published are not verifiable. That is a double-standard that privileges the contributions of text-editors simply because most users are text-editors and they are used to verifying text; that is not a principled reason to treat text and images differently. Moreover, that is simply not what happened—The opposite happend, and images are treated as verifiable based on their contents just like text because that's a common sense reading of the rule. It would have been madness if images had been treated differently. And yet that is essentially the fundamentalist position of people who are extending their opposition to AI with arguments that apply to all images. If they are arguing verifiability seriously at all, they are pretending that the sort of degenerate situation I just described already exists when the opposite consensus has been reached consistently for years. In the related NOR thread, they even tried to say Wikipedians had "turned a blind eye" to these image issues as if negatively characterizing those decisions would invalidate the fact that those decisions were consensus. The motivated reasoning of these discussions has been as blatant as that. At the bottom of this dispute, I take issue with trying to alter the rules in a way that creates a new double-standard within verifiability that applies to all images but not text. That's especially upsetting when (despite my and others' best efforts) so many of us are still focusing SOLELY on their hatred for AI rather than considering the obvious second-order consequences for user-generated images as a whole. Frankly, in no other context has any Wikipedian ever allowed me to say text they wrote was "fake" or challenge an image based on whether it was "fake." The issue has always been verifiability, not provenance or falsity. Sometimes, IMO, that has lead to disaster and Misplaced Pages saying things I know to be factually untrue despite the contents of reliable sources. But that is the policy. We compare the contents of Misplaced Pages to reliable sources, and the contents of Misplaced Pages are considered verifiable if they cohere. I ask again: If Misplaced Pages's response to the creation of AI imaging tools is to crack down on all artistic contributions to Misplaced Pages (which seems to be the inevitable direction of these discussions), what does that say? If our negative response to AI tools is to limit what humans can do on Misplaced Pages, what does that say? Are we taking a stand for human achievements, or is this a very heated discussion of cutting off our nose to save our face? lethargilistic (talk) 23:31, 4 January 2025 (UTC)
"Verifiable by comparing them to a reliable source" - comparing two images and saying that one looks like the other is not "verifying" anything. The text equivalent is presenting something as a quotation that is actually a user-generated paraphrasing.
"Frankly, in no other context has any Wikipedian ever allowed me to say text they wrote was "fake" or challenge an image based on whether it was "fake."" - Try presenting a paraphrasing as a quotation and see what happens.
"Imagine it's 2002 and Misplaced Pages is just starting. Most users want to contribute text to the encyclopedia, but there is a cadre of artists who want to contribute pictures..." - This basically happened, and is the origin of WP:NOTGALLERY. Misplaced Pages is not a host for original works. FOARP (talk) 22:01, 6 January 2025 (UTC)
Comparing two images and saying that one looks like the other is not "verifying" anything. Comparing text to text in a reliable source is literally the same thing.
The text equivalent is presenting something as a quotation that is actually a user-generated paraphrasing. No it isn't. The text equivalent is writing a sentence in an article and putting a ref tag on it. Perhaps there is room for improving the referencing of images in the sense that they should offer example comparisons to make. But an image created by a person is not unverifiable simply because it is user-generated. It is not somehow more unverifiable simply because it is created in a lifelike style.
Try presenting a paraphrasing as a quotation and see what happens. Besides what I just said, nobody is even presenting these images as equatable to quotations. People in this thread have simply been calling them "fake" of their own initiative; the uploaders have not asserted that these are literal photographs to my knowledge. The uploaders of illustrations obviously did not make that claim either. (And, if the contents of the image is a copyvio, that is a separate issue entirely.)
This basically happened, and is the origin of WP:NOTGALLERY. That is not the same thing. User-generated images that illustrate the subject are not prohibited by WP:NOTGALLERY. Misplaced Pages is a host of encyclopedic content, and user-generated images can have encyclopedic content. lethargilistic (talk) 02:41, 7 January 2025 (UTC)
Images are way more complex than text. Trying to compare them in the same way is a very dangerous simplification. Cremastra (u — c) 02:44, 7 January 2025 (UTC)
Assume only non-free images exist of a person. An illustrator refers to those non-free images and produces a painting. From that painting, you see a person who looks like the person in the non-free photographs. The image is verified as resembling the person. That is a simplification, but to call it "dangerous" is disingenuous at best. The process for challenging the image is clear. Someone who wants to challenge the veracity of the image would just need to point to details that do not align. For instance, "he does not typically have blue hair" or "he does not have a scar." That is what we already do, and it does not come up much because it would be weird to deliberately draw an image that looks nothing like the person. Additionally, someone who does not like the image for aesthetic reasons rather than encyclopedic ones always has the option of sourcing a photograph some other way like permission, fair use, or taking a new one themself. This is not an intractable problem. lethargilistic (talk) 02:57, 7 January 2025 (UTC)
So a photorealistic AI-generated image would be considered acceptable until someone identifies a "big enough" difference? How is that anything close to ethical? An portrait that's got an extra mole or slightly wider nose bridge or lacks a scar is still not an image of the person regardless of whether random Misplaced Pages editors notice. And while I don't think user-generated non-photorealistic images should ever be used on biographies either, at least those can be traced back to a human who is ultimately responsible for the depiction, who can point to the particular non-free images they used as references, and isn't liable to average out details across all time periods of the subject. And that's not even taking into account the copyright issues. JoelleJay (talk) 22:52, 7 January 2025 (UTC)
+1 to what JoelleJay said. The problem is that AI-generated images are simulations trying to match existing images, sometimes, yes, with an impressive degree of accuracy. But they will always be inferior to a human-drawn painting that's trying to depict the person. We're a human encyclopedia, and we're built by humans doing human things and sometimes with human errors. Cremastra (u — c) 23:18, 7 January 2025 (UTC)
You can't just raise this to an "ethical" issue by saying the word "ethical." You also can't just invoke copyright without articulating an actual copyright issue; we are not discussing copyvio. Everyone agrees that a photo with an actual copyvio in it is subject to that policy.
But to address your actual point: Any image—any photo—beneath the resolution necessary to depict the mole would be missing the mole. Even with photography, we are never talking about science-fiction images that perfectly depict every facet of a person in an objective sense. We are talking about equipment that creates an approximation of reality. The same is true of illustrations and AI imagery.
Finally, a human being is responsible for the contents of the image because a human is selecting it and is responsible for correcting any errors. The result is an image that someone is choosing to use because they believe it is an appropriate likeness. We should acknowledge that human decision and evaluate it naturally—Is it an appropriate likeness?lethargilistic (talk) 10:20, 8 January 2025 (UTC)
(Second comment because I'm on my phone.) I realize I should also respond to this in terms of additive information. What people look like is not static in the way your comment implies. Is it inappropriate to use a photo because they had a zit on the day it was taken? Not necessarily. Is an image inappropriate because it is taken at a bad angle that makes them look fat? Judging by the prolific ComicCon photographs (where people seem to make a game of choosing the worst-looking options; seriously, it's really bad), not necessarily. Scars and bruises exist and then often heal over time. The standard for whether an image with "extra" details is acceptable would still be based on whether it comports acceptably with other images; we literally do what you have capriciously described as "unethical" and supplement it with our compassionate desire to not deliberately embarrass BLPs. (The ComicCon images aside, I guess.) So, no, I would not be a fan of using images that add prominent scars where the subject is not generally known to have one, but that is just an unverifiable fact that does not belong in a Misplaced Pages image. Simple as. lethargilistic (talk) 10:32, 8 January 2025 (UTC)
We don't evaluate the reliability of a source solely by comparing it to other sources. For example, there is an ongoing discussion at the baseball WikiProject talk page about the reliability of a certain web site. It lists no authors nor any information on its editorial control policy, so we're not able to evaluate its reliability. The reliability of all content being used as a source, including images, needs to be considered in terms of its provenance. isaacl (talk) 23:11, 7 January 2025 (UTC)
Still no, I thought I was clear on that but we should not be using AI-generated images in articles for anything besides representing the concept of AI-generated images, or if an AI-generated image is notable or irreplaceable in its own right -- e.g, a musician uses AI to make an album cover.
(this isn't even a good example, it looks more like Steve Bannon)
I still think no. My opposition isn't just to the fact that AI images are misinformation, but also that they essentially serve as a loophole for getting around Enwiki's image use policy. To know what somebody looks like, an AI generator needs to have images of that person in its dataset, and it draws on those images to generate a derivative work. If we have no free images of somebody and we use AI to make one, that's just using a fair use copyrighted image but removed by one step. The image use policy prohibits us from using fair use images for BLPs so I don't think we should entertain this loophole. If we do end up allowing AI images in BLPs, that just disqualifies the rationale of not allowing fair use in the first place. Di (they-them) (talk) 04:40, 3 January 2025 (UTC)
No those are not okay, as this will just cause arguments from people saying a picture is obviously AI-generated, and that it is therefore appropriate. As I mentionned above, there are some exceptions to this, which Gnomingstuff perfectly describes. Fake sketches/cartoons are not appropriate and provide little encyclopedic value. win8x (talk) 05:27, 3 January 2025 (UTC)
No to this as well, with the same carveout for individual images that have received notable discussion. Non-photorealistic AI images are going to be no more verifiable than photorealistic ones, and on top of that will often be lower-quality as images. ModernDayTrilobite (talk • contribs) 05:44, 3 January 2025 (UTC)
No, and that image should be deleted before anyone places it into a mainspace article. Changing the RfC intro long after its inception seems a second bite at an apple that's not aged well. Randy Kryn (talk) 09:28, 3 January 2025 (UTC)
The RfC question has not been changed; another editor was complaining that the RfC question did not make a distinction between photorealistic/non-photorealistic AI-generated images, so I had to add a note to the intro and ping the editors who'd voted !No to clarify things. It has only been 3 days; there's still 27 more days to go. Some1 (talk) 11:18, 3 January 2025 (UTC)
Also answering No to this one per all the arguments above. "It has only been 3 days" is not a good reason to change the RfC question, especially since many people have already !voted and the "30 days" is mostly indicative rather than an actual deadline for a RfC. Chaotic Enby (talk · contribs) 14:52, 3 January 2025 (UTC)
No. We're the human encyclopedia. We should have images drawn or taken by real humans who are trying to depict the subject, not by machines trying to simulate an image. Besides, the given example is horribly drawn. Cremastra (u — c) 15:03, 3 January 2025 (UTC)
I like these even less than the photorealistic ones... This falls into the same basket for me: if we wouldn't let a random editor who drew this at home using conventional tools add it to the article why would we let a random editor who drew this at home using AI tools at it to the article? (and just to be clear the AI generated image of Germán Larrea Mota-Velasco is not recognizable as such) Horse Eye's Back (talk) 16:06, 3 January 2025 (UTC)
No Having such images as said above means the AI had to use copyrighted pictures to create it and we shouldn't use it. --SuperJew (talk) 01:12, 5 January 2025 (UTC)
Still no. If for no other reason than that it's a bad precedent. As others have said, if we make one exception, it will just lead to arguments in the future about whether something is "realistic" or not. I also don't see why we would need cartoon/illustrated-looking AI pictures of people in BLPs. Tepkunset (talk) 20:43, 6 January 2025 (UTC)
Absolutely not. These images are based on whatever the AI could find on the internet, with little to no regard for copyright. Misplaced Pages is better than this. Retswerb (talk) 10:16, 3 January 2025 (UTC)
Comment The RfC question should not have been fiddled with, esp. for such a minor argument that the complai9nmant could have simply included in their own vote. I have no need to re-confirm my own entry. Zaathras (talk) 14:33, 3 January 2025 (UTC)
The RfC question hasn't been modified; I've only added a 03:58, January 3, 2025: Note clarifying that these images can either be photorealistic in style or non-photorealistic in style. I pinged all the !No voters to make them aware. I could remove the Note if people prefer that I do (but the original RfC question is the exact same as it is now, so I don't think the addition of the Note makes a whole ton of difference). Some1 (talk) 15:29, 3 January 2025 (UTC)
No At this point it feels redundant, but I'll just add to the horde of responses in the negative. I don't think we can fully appreciate the issues that this would cause. The potential problems and headaches far outweigh whatever little benefit might come from AI images for BLPs. pillowcrow21:34, 3 January 2025 (UTC)
Support temporary blanket ban with a posted expiration/requred rediscussion date of no more than two years from closing. AI as the term is currently used is very, very new. Right now these images would do more harm than good, but it seems likely that the culture will adjust to them. Darkfrog24 (talk) 23:01, 3 January 2025 (UTC)
No. Misplaced Pages is made by and for humans. I don't want to become Google. Adding an AI-generated image to a page whose topic isn't about generative AI makes me feel insulted. SWinxy (talk) 00:03, 4 January 2025 (UTC)
No. Generative AI may have its place, and it may even have a place on Misplaced Pages in some form, but that place isn't in BLPs. There's no reason to use images of someone that do not exist over a real picture, or even something like a sketch, drawing, or painting. Even in the absence of pictures or human-drawn/painted images, I don't support using AI-generated images; they're not really pictures of the person, after all, so I can't support using them on articles of people. Using nothing would genuinely be a better choice than generated images. SmittenGalaxy | talk!01:07, 4 January 2025 (UTC)
No. Even if you are willing to ignore the inherently fraught nature of using AI-generated anything in relation to BLP subjects, there is simply little to no benefit that could possibly come from trying something like this. There's no guarantee the images will actually look like the person in question, and therefore there's no actual context or information that the image is providing the reader. What a baffling proposal. Ithinkiplaygames (talk) 19:53, 4 January 2025 (UTC)
There's no guarantee the images will actually look like the person in question there is no guarantee any image will look like the person in question. When an image is not a good likeness, regardless of why, we don't use it. When am image is a good likeness we consider using it. Whether an image is AI-generated or not it is completely independent of whether it is a good likeness. There are also reason other then identification why images are used on BLP-articles. Thryduulf (talk) 20:39, 4 January 2025 (UTC)
Foreseeably there may come a time when people's official portraits are AI-enhanced. That time might not be very far in the future. Do we want an exception for official portraits?—S MarshallT/C01:17, 5 January 2025 (UTC)
Yes, depending on specific case. One can use drawings by artists, even such as caricature. The latter is an intentional distortion, one could say an intentional misinformation. Still, such images are legitimate on many pages. Or consider numerous images of Jesus. How realiable are they? I am not saying we must deliberatly use AI images on all pages, but they may be fine in some cases. Now, speaking on "medical articles"... One might actually use the AI generated images of certain biological objects like proteins or organelles. Of course a qualified editorial judgement is always needed to decide if they would improve a specific page (frequently they would not), but making a blanket ban would be unacceptable, in my opinion. For example, the images of protein models generatated by AlphaFold would be fine. The AI-generated images of biological membranes I saw? I would say no. It depends. My very best wishes (talk) 02:50, 5 January 2025 (UTC)
This is complicated of course. For example, there are tools that make an image of a person that (mis)represents him as someone much better and clever than he really is in life. That should be forbidden as an advertisement. This is a whole new world, but I do not think that a blanket rejection would be appropriate. My very best wishes (talk) 03:19, 5 January 2025 (UTC)
No Too risky for BLP's. Besides if people want AI generated content over editor made content, we should make it clear they are in the wrong place, and readers should be given no doubt as to our integrity, sincerity and effort to give them our best, not a program's. Alanscottwalker (talk) 14:51, 5 January 2025 (UTC)
No, as AI's grasp on the Internet takes hold stronger and stronger, it's important Misplaced Pages, as the online encyclopedia it sets out to be, remains factual and real. Using AI images on Wiki would likely do more harm than good, further thinning the boundaries between what's real and what's not. – zmbro(talk) (cont)16:52, 5 January 2025 (UTC)
No, not at the moment. I think it will hard to avoid portraits that been enhanced by AI, as it already been on-going for a number of years and there is no way to avoid it, but I don't want arbitary generated AI portraits of any type. scope_creep20:19, 5 January 2025 (UTC)
No for natural images (e.g. photos of people). Generative AI by itself is not a reliable source for facts. In principle, generating images of people and directly sticking them in articles is no different than generating text and directly sticking it in articles. In practice, however, generating images is worse: Text can at least be discussed, edited, and improved afterwards. In contrast, we have significantly less policy and fewer rigorous methods of discussing how AI-generated images of natural objects should be improved (e.g. "make his face slightly more oblong, it's not close enough yet"). Discussion will devolve into hunches and gut feelings about the fidelity of images, all of which essentially fall under WP:OR. spintheer (talk) 20:37, 5 January 2025 (UTC)
No I'm appalled that even a small minority of editors would support such an idea. We have enough credibility issues already; using AI-generated images to represent real people is not something that a real encyclopedia should even consider. LEPRICAVARK (talk) 22:26, 5 January 2025 (UTC)
No I understand the comparison to using illustrations in BLP articles, but I've always viewed that as less preferable to no picture in all honestly. Images of a person are typically presented in context, such as a performer on stage, or a politician's official portrait, and I feel like there would be too many edge cases to consider in terms of making it clear that the photo is AI generated and isn't representative of anything that the person specifically did, but is rather an approximation. Tpdwkouaa (talk) 06:50, 6 January 2025 (UTC)
No - Too often the images resemble caricatures. Real caricatures may be included in articles if the caricature (e.g., political cartoon) had significant coverage and is attributed to the artist. Otherwise, representations of living persons should be real representations taken with photographic equipment. Robert McClenon (talk) 02:31, 7 January 2025 (UTC)
No - Not only is this effectively guesswork that usually includes unnatural artefacts, but worse, it is also based on unattributed work of photographers who didn't release their work into public domain. I don't care if it is an open legal loophole somewhere, IMO even doing away with the fair use restriction on BLPs would be morally less wrong. I suspect people on whose work LLMs in question were trained would also take less offense to that option. DaßWölf23:25, 7 January 2025 (UTC)
No – WP:NFC says that Non-free content should not be used when a freely licensed file that serves the same purpose can reasonably be expected to be uploaded, as is the case for almost all portraits of living people. While AI images may not be considered copyrightable, it could still be a copyright violation if the output resembles other, copyrighted images, pushing the image towards NFC. At the very least, I feel the use of non-free content to generate AI images violates the spirit of the NFC policy. (I'm assuming copyrighted images of a person are used to generate an AI portrait of them; if free images of that person were used, we should just use those images, and if no images of the person were used, how on Earth would we trust the output?) RunningTiger123 (talk) 02:43, 8 January 2025 (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.
Expiration date?
"AI," as the term is currently used, is very new. It feels like large language models and the type of image generators under discussion just got here in 2024. (Yes, I know it was a little earlier.) The culture hasn't completed its initial response to them yet. Right now, these images do more harm than good, but that may change. Either we'll come up with a better way of spotting hallucinations or the machines will hallucinate less. Their copyright status also seems unstable. I suggest that any ban decided upon here have some expiration date or required rediscussion date. Two years feels about right to me, but the important thing would be that the ban has a number on it. Darkfrog24 (talk) 23:01, 3 January 2025 (UTC)
No need for any end-date. If there comes a point where consensus on this changes, then we can change any ban then. FOARP (talk) 05:27, 5 January 2025 (UTC)
An end date is a positive suggestion. Consensus systems like Misplaced Pages's are vulnerable to half-baked precedential decisions being treated as inviolate. With respect, this conversation does not inspire confidence that this policy proposal's consequences are well-understood at this time. If Misplaced Pages goes in this direction, it should be labeled as primarily reactionary and open to review at a later date. lethargilistic (talk) 10:22, 5 January 2025 (UTC)
Agree with FOARP, no need for an end date. If something significantly changes (e.g. reliable sources/news outlets such as the New York Times, BBC, AP, etc. start using text-to-image models to generate images of living people for their own articles) then this topic can be revisited later. Editors will have to go through the usual process of starting a new discussion/proposal when that time comes. Some1 (talk) 11:39, 5 January 2025 (UTC)
Seeing as this discussion has not touched at all on what other organizations may or may not do, it would not be accurate to describe any consensus derived from this conversation in terms of what other organizations may or may not be doing. That is, there has been no consensus that we ought to be looking to the New York Times as an example. Doing so would be inadvisable for several reasons. For one, they have sued an AI company over semi-related issues and they have teams explicitly working on what the future of AI in news ought to look like, so they have some investment in what the future of AI looks like and they are explicitly trying to shape its norms. For another, if they did start to use AI in a way that may be controversial, they would have no positive reason to disclose that and many disincentives. They are not a neutral signal on this issue. Misplaced Pages should decide for itself, preferably doing so while not disrupting the ability of people to continue creating user-generated images. lethargilistic (talk) 03:07, 6 January 2025 (UTC)
No need per others. Additionally, if practices change, it doesn't mean editors will decide to follow new practices. As for the technology, it seems the situation has been fairly stable for the past two years: we can detect some fakes and hallucinations immediately, many more in the past, but certainly not all retouched elements and all generated photos available right now, even if there was a readily accessible tool or app that enabled ordinary people to reliably do so.
Through the history, art forgeries have been fairly reliably detected, but rarely quickly. Relatedly, I don't see why the situation with AI images would change in the next 24 months or any similar time period. DaßWölf22:17, 9 January 2025 (UTC)
Using AI to write your comments in a discussion makes it difficult for others to assume that you are discussing in good faith, rather than trying to use AI to argue someone into exhaustion (see example of someone using AI in their replies "Because I don't have time to argue with, in my humble opinion, stupid PHOQUING people"). More fundamentally, WP:AGF can't apply to the AI itself as AI lacks intentionality, and it is difficult for editors to assess how much of an AI-generated comment reflects the training of the AI vs. the actual thoughts of the editor.
No. As with all the other concurrent discussions (how many times do we actually need to discuss the exact same FUD and scaremongering?) the problem is not AI, but rather inappropriate use of AI. What we need to do is to (better) explain what we actually want to see in discussions, not vaguely defined bans of swathes of technology that, used properly, can aid communication. Thryduulf (talk) 01:23, 2 January 2025 (UTC)
Note that this topic is discussing using AI to generate replies, as opposed to using it as an aid (e.g. asking it to edit for grammar, or conciseness). As the above concurrent discussion demonstrates, users are already using AI to generate their replies in AfD, so it isn't scaremongering but an actual issue.
WP:DGF also does not ban anything ("Showing good faith is not required"), but offers general advice on demonstrating good faith. So it seems like the most relevant place to include mention of the community's concerns regarding AI-generated comments, without outright banning anything. Photos of Japan (talk) 01:32, 2 January 2025 (UTC)
And as pointed out, multiple times in those discussions, different people understand different things from the phrase "AI-generated". The community's concern is not AI-generated comments, but comments that do not clearly and constructively contribute to a discussion - some such comments are AI-generated, some are not. This proposal would, just as all the other related ones, cause actual harm when editors falsely accuse others of using AI (and this will happen). Thryduulf (talk) 02:34, 2 January 2025 (UTC)
Nobody signed up to argue with bots here. If you're pasting someone else's comment into a prompt and asking the chatbot to argue against that comment and just posting it in here, that's a real problema and absolutely should not be acceptable. :bloodofox: (talk) 03:31, 2 January 2025 (UTC)
Thank you for the assumption of bad faith and demonstrating one of my points about the harm caused. Nobody is forcing you to engage with bad-faith comments, but whether something is or is not bad faith needs to be determined by its content not by its method of generation. Simply using an AI demonstrates neither good faith nor bad faith. Thryduulf (talk) 04:36, 2 January 2025 (UTC)
I don't see why we have any particular to reason to suspect a respected and trustworthy editor of using AI. Cremastra (u — c) 14:31, 2 January 2025 (UTC)
I'm one of those people who clarified the difference between AI-generated vs. edited, and such a difference could be made explicit with a note. Editors are already accusing others of using AI. Could you clarify how you think addressing AI in WP:DGF would cause actual harm? Photos of Japan (talk) 04:29, 2 January 2025 (UTC)
By encouraging editors to accuse others of using AI, by encouraging editors to dismiss or ignore comments because they suspect that they are AI-generated rather than engaging with them. @Bloodofox has already encouraged others to ignore my arguments in this discussion because they suspect I might be using an LLM and/or be a bot (for the record I'm neither). Thryduulf (talk) 04:33, 2 January 2025 (UTC)
Given your relentlessly pro-AI comments here, it seems that you'd be A-OK with just chatting with a group of chatbots here — or leaving the discussion to them. However, most of us clearly are not. In fact, I would immediately tell someone to get lost were it confirmed that indeed that is what is happening. I'm a human being and find the notion of wasting my time with chatbots on Misplaced Pages to be incredibly insulting and offensive. :bloodofox: (talk) 04:38, 2 January 2025 (UTC)
My comments are neither pro-AI nor anti-AI, indeed it seems that you have not understood pretty much anything I'm saying. Thryduulf (talk) 04:43, 2 January 2025 (UTC)
Funny, you've done nothing here but argue for more generative AI on the site and now you seem to be arguing to let chatbots run rampant on it while mocking anyone who doesn't want to interface with chatbots on Misplaced Pages. Hey, why not just sell the site to Meta, am I right? :bloodofox: (talk) 04:53, 2 January 2025 (UTC)
I haven't been arguing for more generative AI on the site. I've been arguing against banning it on the grounds that such a ban would be unclear, unenforceable, wouldn't solve any problems (largely because whether something is AI or not is completely irrelevant to the matter at hand) but would instead cause harm. Some of the issues identified are actual problems, but AI is not the cause of them and banning AI won't fix them.
I'm not mocking anybody, nor am I advocating to let chatbots run rampant. I'm utterly confused why you think I might advocate for selling Misplaced Pages to Meta (or anyone else for that matter)? Are you actually reading anything I'm writing? You clearly are not understanding it. Thryduulf (talk) 05:01, 2 January 2025 (UTC)
So we're now in 'everyone else is the problem, not me!' territory now? Perhaps try communicating in a different way because your responses here are looking very much like the typical AI apologetics one can encounter on just about any contemporary LinkedIn thread from your typical FAANG employee. :bloodofox: (talk) 05:13, 2 January 2025 (UTC)
No, this is not a everyone else is the problem, not me issue because most other people appear to be able to understand my arguments and respond to them appropriately. Not everybody agrees with them, but that's not an issue.
I'm not familiar with Linkedin threads (I don't use that platform) nor what a "FAANG employee" is (I've literally never heard the term before now) so I have no idea whether your characterisation is a compliment or a personal attack, but given your comments towards me and others you disagree with elsewhere I suspect it's closer to the latter.
AI is a tool. Just like any other tool it can be used in good faith or in bad faith, it can be used well and it can be used badly, it can be used in appropriate situations and it can be used in inappropriate situations, the results of using the tool can be good and the results of using the tool can be bad. Banning the tool inevitably bans the good results as well as the bad results but doesn't address the reasons why the results were good or bad and so does not resolve the actual issue that led to the bad outcomes. Thryduulf (talk) 12:09, 2 January 2025 (UTC)
In the context of generating comments to other users though, AI is much easier to use for bad faith than for good faith. LLMs don't understand Misplaced Pages's policies and norms, and so are hard to utilize to generate posts that productively address them. By contrast, bad actors can easily use LLMs to make low quality posts to waste people's time or wear them down.
In the context of generating images, or text for articles, it's easy to see how the vast majority of users using AI for those purposes is acting in good faith as these are generally constructive tasks, and most people making bad faith changes to articles are either obvious vandals who won't bother to use AI because they'll be reverted soon anyways, or trying to be subtle (povpushers) in which case they tend to want to carefully write their own text into the article.
It's true that AI "is just a tool", but when that tool is much easier to use for bad faith purposes (in the context of discussions) then it raises suspicions about why people are using it. Photos of Japan (talk) 22:44, 2 January 2025 (UTC)
LLMs don't understand Misplaced Pages's policies and norms They're not designed to "understand" them since the policies and norms were designed for human cognition. The fact that AI is used rampantly by people acting in bad faith on Misplaced Pages does not inherently condemn the AI. To me, it shows that it's too easy for vandals to access and do damage on Misplaced Pages. Unfortunately, the type of vetting required to prevent that at the source would also potentially require eliminating IP-editing, which won't happen. Duly signed,⛵ WaltClipper -(talk)14:33, 15 January 2025 (UTC)
You mentioned "FUD". That acronym, "fear, uncertainty and doubt," is used in precisely two contexts: pro-AI propagadizing and persuading people who hold memecoin crypto to continue holding it. Since this discussion is not about memecoin crypto that would suggest you are using it in a pro-AI context. I will note, fear, uncertainty and doubt is not my problem with AI. Rather it's anger, aesthetic disgust and feeling disrespected when somebody makes me talk to their chatbot. Simonm223 (talk) 14:15, 14 January 2025 (UTC)
That acronym, "fear, uncertainty and doubt," is used in precisely two contexts is simply
FUD both predates AI by many decades (my father introduced me to the term in the context of the phrase "nobody got fired for buying IBM", and the context of that was mainframe computer systems in the 1980s if not earlier. FUD is also used in many, many more contexts that just those two you list, including examples by those opposing the use of AI on Misplaced Pages in these very discussions. Thryduulf (talk) 14:47, 14 January 2025 (UTC)
That acronym, "fear, uncertainty and doubt," is used in precisely two contexts is factually incorrect.
FUD both predates AI by many decades (indeed if you'd bothered to read the fear, uncertainty and doubt article you'd learn that the concept was first recorded in 1693, the exact formulation dates from at least the 1920s and the use of it in technology concepts originated in 1975 in the context of mainframe computer systems. That its use, eve in just AI contexts, is limited to pro-AI advocacy is ludicrous (even ignoring things like Roko's basilisk), examples can be found in these sprawling discussions from those opposing AI use on Misplaced Pages. Thryduulf (talk) 14:52, 14 January 2025 (UTC)
Not really – I agree with Thryduulf's arguments on this one. Using AI to help tweak or summarize or "enhance" replies is of course not bad faith – the person is trying hard. Maybe English is their second language. Even for replies 100% AI-generated the user may be an ESL speaker struggling to remember the right words (I always forget 90% of my French vocabulary when writing anything in French, for example). In this case, I don't think we should make a blanket assumption that using AI to generate comments is not showing good faith. Cremastra (u — c) 02:35, 2 January 2025 (UTC)
Yes because generating walls of text is not good faith. People "touching up" their comments is also bad (for starters, if you lack the English competency to write your statements in the first place, you probably lack the competency to tell if your meaning has been preserved or not). Exactly what AGF should say needs work, but something needs to be said, and AGFDGF is a good place to do it. XOR'easter (talk) 02:56, 2 January 2025 (UTC)
Not all walls of text are generated by AI, not all AI generated comments are walls of text. Not everybody who uses AI to touch up their comments lacks the competencies you describe, not everybody who does lack those competencies uses AI. It is not always possible to tell which comments have been generated by AI and which have not. This proposal is not particularly relevant to the problems you describe. Thryduulf (talk) 03:01, 2 January 2025 (UTC)
Someone has to ask: Are you generating all of these pro-AI arguments using ChatGPT? It'd explain a lot. If so, I'll happily ignore any and all of your contributions, and I'd advise anyone else to do the same. We're not here to be flooded with LLM-derived responses. :bloodofox: (talk) 03:27, 2 January 2025 (UTC)
That you can't tell whether my comments are AI-generated or not is one of the fundamental problems with these proposals. For the record they aren't, nor are they pro-AI - they're simply anti throwing out babies with bathwater. Thryduulf (talk) 04:25, 2 January 2025 (UTC)
I'd say it also illustrates the serious danger: We can no longer be sure that we're even talking to other people here, which is probably the most notable shift in the history of Misplaced Pages. :bloodofox: (talk) 04:34, 2 January 2025 (UTC)
How is that a "serious danger"? If a comment makes a good point, why does it matter whether ti was AI generated or not? If it doesn't make a good point, why does it matter if it was AI generated or not? How will these proposals resolve that "danger"? How will they be enforceable? Thryduulf (talk) 04:39, 2 January 2025 (UTC)
Misplaced Pages is made for people, by people, and I like most people will be incredibly offended to find that we're just playing some kind of LLM pong with a chatbot of your choice. You can't be serious. :bloodofox: (talk) 04:40, 2 January 2025 (UTC)
"why does it matter if it was AI generated or not?"
Because it takes little effort to post a lengthy, low quality AI-generated post, and a lot of effort for human editors to write up replies debunking them.
"How will they be enforceable? "
WP:DGF isn't meant to be enforced. It's meant to explain to people how they can demonstrate good faith. Posting replies to people (who took the time to write them) that are obviously AI-generated harms the ability of those people to assume good faith. Photos of Japan (talk) 05:16, 2 January 2025 (UTC)
The linked "example of someone using AI in their replies" appears – to me – to be a non-AI-generated comment. I think I preferred the allegedly AI-generated comments from that user (example). The AI was at least superficially polite. WhatamIdoing (talk) 04:27, 2 January 2025 (UTC)
Obviously the person screaming in all caps that they use AI because they don't want to waste their time arguing is not using AI for that comment. Their first post calls for the article to be deleted for not "offering new insights or advancing scholarly understanding" and "merely" reiterating what other sources have written.
Yes, after a human had wasted their time explaining all the things wrong with its first post, then the bot was able to write a second post which looks ok. Except it only superficially looks ok, it doesn't actually accurately describe the articles. Photos of Japan (talk) 04:59, 2 January 2025 (UTC)
Multiple humans have demonstrated in these discussions that humans are equally capable of writing posts which superficially look OK but don't actually accurately relate to anything they are responding to. Thryduulf (talk) 05:03, 2 January 2025 (UTC)
But I can assume that everyone here is acting in good faith. I can't assume good faith in the globally-locked sock puppet spamming AfD discussions with low effort posts, whose bot is just saying whatever it can to argue for the deletion of political pages the editor doesn't like. Photos of Japan (talk) 05:09, 2 January 2025 (UTC)
True, but I think that has more to do with the "globally-locked sock puppet spamming AfD discussions" part than with the "some of it might be " part. WhatamIdoing (talk) 07:54, 2 January 2025 (UTC)
All of which was discovered because of my suspicions from their inhuman, and meaningless replies. "Reiteration isn't the problem; redundancy is," maybe sounds pithy in a vacuum, but this was written in reply to me stating that we aren't supposed to be doing OR but reiterating what the sources say.
"Your criticism feels overly prescriptive, as though you're evaluating this as an academic essay" also sounds good, until you realize that the bot is actually criticizing its own original post.
The fact that my suspicions about their good faith were ultimately validated only makes it even harder for me to assume good faith in users who sound like ChatGPT. Photos of Japan (talk) 08:33, 2 January 2025 (UTC)
I wonder if we need some other language here. I can understand feeling like this is a bad interaction. There's no sense that the person cares; there's no feeling like this is a true interaction. A contract lawyer would say that there's no meeting of the minds, and there can't be, because there's no mind in the AI, and the human copying from the AI doesn't seem to be interested in engaging their brain.
The user's talk page has a header at the top asking people not to template them because it is "impersonal and disrespectful", instead requesting "please take a moment to write a comment below in your own words"
Does this look like acting in good faith to you? Requesting other people write personalized responses to them while they respond with an LLM? Because it looks to me like they are trying to waste other people's time. Photos of Japan (talk) 09:35, 2 January 2025 (UTC)
"Being hypocritical" in the abstract isn't the problem, it's the fact that asking people to put effort into their comments, while putting in minimal effort into your own comments appears bad faith, especially when said person says they don't want to waste time writing comments to stupid people. The fact you are arguing AGF for this person is both astounding and disappointing. Photos of Japan (talk) 16:08, 3 January 2025 (UTC)
It feels like there is a lack of reciprocity in the interaction, even leaving aside the concern that the account is a block-evading sock.
But I wonder if you have read AGF recently. The first sentence is "Assuming good faith (AGF) means assuming that people are not deliberately trying to hurt Misplaced Pages, even when their actions are harmful."
So we've got some of this (e.g., harmful actions). But do you really believe this person woke up in the morning and decided "My main goal for today is to deliberately hurt Misplaced Pages. I might not be successful, but I sure am going to try hard to reach my goal"? WhatamIdoing (talk) 23:17, 4 January 2025 (UTC)
Trying to hurt Misplaced Pages doesn't mean they have to literally think "I am trying to hurt Misplaced Pages", it can mean a range of things, such as "I am trying to troll Wikipedians". A person who thinks a cabal of editors is guarding an article page, and that they need to harass them off the site, may think they are improving Misplaced Pages, but at the least I wouldn't say that they are acting in good faith. Photos of Japan (talk) 23:27, 4 January 2025 (UTC)
The issues with AI in discussions is not related to good faith, which is narrowly defined to intent. CMD (talk) 04:45, 2 January 2025 (UTC)
In my mind, they are related inasmuch as it is much more difficult for me to ascertain good faith if the words are eminently not written by the person I am speaking to in large part, but instead generated based on an unknown prompt in what is likely a small fraction of the expected time. To be frank, in many situations it is difficult to avoid the conclusion that the disparity in effort is being leveraged in something less than good faith. Remsense ‥ 论05:02, 2 January 2025 (UTC)
Assume good faith, don't ascertain! Llm use can be deeply unhelpful for discussions and the potential for mis-use is large, but the most recent discussion I've been involved with where I observed an llm post was responded to by an llm post, I believe both the users were doing this in good faith. CMD (talk) 05:07, 2 January 2025 (UTC)
All I mean to say is it should be licit that unhelpful LLM use should be something that can be mentioned like any other unhelpful rhetorical pattern. Remsense ‥ 论05:09, 2 January 2025 (UTC)
The fact that everyone (myself included) defending "LLM use" says "use" rather than "generated", is a pretty clear sign that no one really wants to communicate with someone using "LLM generated" comments. We can argue about bans (not being proposed here), how to know if someone is using LLM, the nuances of "LLM use", etc., but at the very least we should be able to agree that there are concerns with LLM generated replies, and if we can agree that there are concerns then we should be able to agree that somewhere in policy we should be able to find a place to express those concerns. Photos of Japan (talk) 05:38, 2 January 2025 (UTC)
For instance, I am OK with someone using a LLM to post a productive comment on a talk page. I am also OK with someone generating a reply with a LLM that is a productive comment to post to a talk page. I am not OK with someone generating text with an LLM to include in an article, and also not OK with someone using a LLM to contribute to an article.
Most people already assume good faith in those making productive contributions. In situations where good faith is more difficult to assume, would you trust someone who uses an LLM to generate all of their comments as much as someone who doesn't? Photos of Japan (talk) 09:11, 2 January 2025 (UTC)
Given that LLM-use is completely irrelevant to the faith in which a user contributes, yes. Of course what amount that actually is may be anywhere between completely and none. Thryduulf (talk) 11:59, 2 January 2025 (UTC)
LLM-use is relevant as it allows bad faith users to disrupt the encyclopedia with minimal effort. Such a user posted in this thread earlier, as well as started a disruptive thread here and posted here, all using AI. I had previously been involved in a debate with another sock puppet of theirs, but at that time they didn't use AI. Now it seems they are switching to using an LLM just to troll with minimal effort. Photos of Japan (talk) 21:44, 2 January 2025 (UTC)
LLMs are a tool that can be used by good and bad faith users alike. Using an LLM tells you nothing about whether a user is contributing in good or bad faith. If somebody is trolling they can be, and should be, blocked for trolling regardless of the specifics of how they are trolling. Thryduulf (talk) 21:56, 2 January 2025 (UTC)
A can of spray paint, a kitchen knife, etc., are tools that can be used for good or bad, but if you bring them some place where they have few good uses and many bad uses then people will be suspicious about why you brought them. You can't just assume that a tool in any context is equally harmless. Using AI to generate replies to other editors is more suspicious than using it to generate a picture exemplifying a fashion style, or a description of a physics concept. Photos of Japan (talk) 23:09, 2 January 2025 (UTC)
WP:AGF is not a death pact though. At times you should be suspicious. Do you think that if a user, who you already have suspicions of, is also using an LLM to generate their comments, that that doesn't have any effect on those suspicions? Photos of Japan (talk) 21:44, 2 January 2025 (UTC)
So… If you suspect that someone is not arguing in good faith… just stop engaging them. If they are creating walls of text but not making policy based arguments, they can be ignored. Resist the urge to respond to every comment… it isn’t necessary to “have the last word”. Blueboar (talk) 21:57, 2 January 2025 (UTC)
That they've been banned for disruption indicates we can do everything we need to do to deal with bad faith users of LLMs without assuming that everyone using an LLM is doing so in bad faith. Thryduulf (talk) 00:33, 3 January 2025 (UTC)
I don't believe we should assume everyone using an LLM is doing so in bad faith, so I'm glad you think my comment indicates what I believe. Photos of Japan (talk) 01:09, 3 January 2025 (UTC)
No -- whatever you think of LLMs, the reason they are so popular is that the people who use them earnestly believe they are useful. Claiming otherwise is divorced from reality. Even people who add hallucinated bullshit to articles are usually well-intentioned (if wrong). Gnomingstuff (talk) 06:17, 2 January 2025 (UTC)
Yes I find it incredibly rude for someone to procedurally generate text and then expect others to engage with it as if they were actually saying something themselves. Simonm223 (talk) 14:34, 2 January 2025 (UTC)
Yes, mention that use of an LLM should be disclosed and that failure to do so is like not telling someone you are taping the call. Selfstudier (talk) 14:43, 2 January 2025 (UTC)
I could support general advice that if you're using machine translation or an LLM to help you write your comments, it can be helpful to mention this in the message. The tone to take, though, should be "so people won't be mad at you if it screwed up the comment" instead of "because you're an immoral and possibly criminal person if you do this". WhatamIdoing (talk) 07:57, 3 January 2025 (UTC)
No. When someone publishes something under their own name, they are incorporating it as their own statement. Plagiarism from an AI or elsewhere is irrelevant to whether they are engaging in good faith. lethargilistic (talk) 17:29, 2 January 2025 (UTC)
Comment LLMs know a few tricks about logical fallacies and some general ways of arguing (rhetoric), but they are incredibly dumb at understanding the rules of Misplaced Pages. You can usually tell this because it looks like incredibly slick and professional prose, but somehow it cannot get even the simplest points about the policies and guidelines of Misplaced Pages. I would indef such users for lacking WP:CIR. tgeorgescu (talk) 17:39, 2 January 2025 (UTC)
That guideline states "Sanctions such as blocks and bans are always considered a last resort where all other avenues of correcting problems have been tried and have failed." Gnomingstuff (talk) 19:44, 2 January 2025 (UTC)
I blocked that user as NOTHERE a few minutes ago after seeing them (using ChatGPT) make suggestions for text to live pagespace while their previous bad behaviors were under discussion. AGF is not a suicide pact. BusterD (talk) 20:56, 2 January 2025 (UTC)
Yes Using a 3rd party service to contribute to the Misplaced Pages on your behalf is clearly bad-faith, analogous to paying someone to write your article. Zaathras (talk) 14:39, 3 January 2025 (UTC)
Its a stretch to say that a newbie writing a comment using AI is automatically acting in bad faith and not here to build an encyclopedia. PackMecEng (talk) 16:55, 3 January 2025 (UTC)
Comment Large language model AI like Chat GPT are in their infancy. The culture hasn't finished its initial reaction to them yet. I suggest that any proposal made here have an automatic expiration/required rediscussion date two years after closing. Darkfrog24 (talk) 22:42, 3 January 2025 (UTC)
No – It is a matter of how you use AI. I use Google translate to add trans-title parameters to citations, but I am careful to check for Google's output making for good English as well as reflecting the foreign title when it is a language I somewhat understand. I like to think that I am careful, and I do not pretend to be fluent in a language I am not familiar with, although I usually don't announce the source of such a translation. If an editor uses AI profligately and without understanding the material generated, then that is the sin; not AI itself. Dhtwiki (talk) 05:04, 5 January 2025 (UTC)
There's a legal phrase, "when the exception swallows the rule", and I think we might be headed there with the recent LLM/AI discussions.
We start off by saying "Let's completely ban it!" Then in discussion we add "Oh, except for this very reasonable thing... and that reasonable thing... and nobody actually meant this other reasonable thing..."
Do you want us to reply to you, because you are a human? Or are you just posting the output of an LLM without bothering to read anything yourself? DS (talk) 06:08, 7 January 2025 (UTC)
Most likely you would reply because someone posted a valid comment and you are assuming they are acting in good faith and taking responsibility for what they post. To assume otherwise is kind of weird and not inline with general Misplaced Pages values. PackMecEng (talk) 15:19, 8 January 2025 (UTC)
No The OP seems to misunderstand WP:DGF which is not aimed at weak editors but instead exhorts stronger editors to lead by example. That section already seems to overload the primary point of WP:AGF and adding mention of AI would be quite inappropriate per WP:CREEP. Andrew🐉(talk) 23:11, 5 January 2025 (UTC)
Yes. AI use is not a demonstration of bad faith (in any case not every new good-faith editor is familiar with our AI policies), but it is equally not a "demonstration of good faith", which is what the WP:DGF section is about.
It seems some editors are missing the point and !voting as if every edit is either a demonstration of good faith or bad faith. Most interactions are neutral and so is most AI use, but I find it hard to imagine a situation where AI use would point away from unfamiliarity and incompetence (in the CIR sense), and it often (unintentionally) leads to a presumption of laziness and open disinterest. It makes perfect sense to recommend against it. DaßWölf22:56, 9 January 2025 (UTC)
Indeed most kinds of actions don't inherently demonstrate good or bad. The circumspect and neutral observation that AI use is not a demonstration of bad faith... but it is equally not a "demonstration of good faith", does not justify a proposal to one-sidedly say just half. And among all the actions that don't necessarily demonstrate good faith (and don't necessarily demonstrate bad faith either), it is not the purpose of "demonstrate good faith" and the broader guideline, to single out one kind of action to especially mention negatively. Adumbrativus (talk) 04:40, 13 January 2025 (UTC)
Yes. Per Dass Wolf, though I would say passing off a completely AI-generated comment as your own anywhere is inherently bad-faith and one doesn't need to know Wiki policies to understand that. JoelleJay (talk) 23:30, 9 January 2025 (UTC)
Yes. Sure, LLMs may have utility somewhere, and it might be a crutch for people unfamiliar with English, but as I've said above in the other AI RfC, that's a competence issue. This is about comments eating up editor time, energy, about LLMs easily being used to ram through changes and poke at editors in good standing. I don't see a case wherein a prospective editor's command of policy and language is good enough to discuss with other editors while being bad enough to require LLM use. Iseulttalk to me01:26, 10 January 2025 (UTC)
Good faith is separate from competence. Trying to do good is separate from having skills and knowledge to achieve good results. Adumbrativus (talk) 04:40, 13 January 2025 (UTC)
No - anyone using a washing machine to wash their clothes must be evil and inherently lazy. They cannot be trusted. ... Oh, sorry, wrong century. Regards, --Goldsztajn (talk) 01:31, 10 January 2025 (UTC)
No - As long as a person understands (and knows) what they are talking about, we shouldn't discriminate against folks using generative AI tech for grammar fixes or minor flow improvements. Yes, AI can create walls of text, and make arguments not grounded in policy, but we could do that even without resorting to generative AI. Sohom (talk) 11:24, 13 January 2025 (UTC)
To expand on my point above. Completely AI generated comments (or articles) are obviously bad, but using AI should be thrown into the same cross-hairs as completely AI generated comments. Sohom (talk) 11:35, 13 January 2025 (UTC)
No. Don't make any changes. It's not a good faith/bad faith issue. The 'yes' arguments are most unconvincing with very bizarre analogies to make their point. Here, I can make one too: "Don't edit with AI; you wouldn't shoot your neighbor's dog with a BB-gun, would you?" Duly signed,⛵ WaltClipper -(talk)14:43, 13 January 2025 (UTC)
While I have no issue with the direction the linked discussion has taken, I agree with almost every contributor there: As a practice I have zero interest in generally allowing random editors closing outside their permissions. It might make DRV a more chatty board, granted. BusterD (talk) 15:02, 7 January 2025 (UTC)
Tamzin makes a reasonable case in their comment below. When we have already chosen to trust certain editors with advanced permissions, we might allow those folks to utilize them as fully as accepted practice allows. Those humans already have skin in the game. They are unlikely to act rashly. BusterD (talk) 19:32, 7 January 2025 (UTC)
To me, non-admin delete closes at any XfD have always seemed inconsistent with what we say about how adminship and discussion closing work. I would be in violation of admin policy if I deleted based on someone else's close without conducting a full review myself, in which case, what was the point of their close? It's entirely redundant to my own work. That said, I can't really articulate a reason that this should be allowed at some XfDs but not others, and it seems to have gone fine at CfD and TfD. I guess call me neutral. What I'd be more open to is allowing page movers to do this. Page movers do have the tools to turn a bluelink red, so it doesn't create the same admin accountability issue if I'm just cleaning up the stray page left over from a page mover's use of a tool that they were duly granted and subject to their own accountability rules for. We could let them move a redirect to some other plausible title (this would violate WP:MOVEREDIRECT as currently written but I think I'd be okay with making this a canonical exception), and/or allow moving to some draftspace or userspace page and tagging for G6, as we do with {{db-moved}}. I'll note that when I was a non-admin pagemover, I did close a few things as delete where some edge case applied that let me effect the deletion using only suppressredirect, and no one ever objected. -- Tamzin (they|xe|🤷) 19:07, 7 January 2025 (UTC)
I see that I was sort of vague, which is consistent with the statement that I hinted at allowing non-admin delete closures. My main concern is that I would like to see our guidelines and our practice made consistent, either by changing the guidelines or changing the practice. It appears that there is a rough consensus emerging that non-admin delete closures should continue to be disallowed in RFD, but that CFD may be a special case. So what I am saying is that if, in practice, we allow non-admin Delete closures at CFD, the guideline should say something vague to that effect.
I also see that there is a consensus that DRV can endorse irregular non-admin closures, including irregular non-admin Delete closures. Specifically, it isn't necessary for DRV to vacate the closure for an uninvolved admin to close. A consensus at DRV, some of whose editors will be uninvolved admins, is at least as good a close as a normal close by an uninvolved admin.
Also, maybe we need clearer guidance about non-admin Keep closures of AFDs. I think that if an editor is not sure whether they have sufficient experience to be closing AFDs as Keep, they don't have enough experience. I think that the guidance is clear enough in saying that administrator accountability applies to non-admin closes, but maybe it needs to be further strengthened, because at DRV we sometimes deal with non-admin closes where the closer doesn't respond to inquiries, or is rude in response to them.
Also, maybe we need clearer guidance about non-admin No Consensus closures of AFDs. In particular, a close of No Consensus is a contentious closure, and should either be left to an admin, or should be Relisted.
As for I can't really articulate a reason that this should be allowed at some XfDs, the argument is that more work is needed to enact closures at TfD and CfD (namely orphaning templates and emptying/moving/merging categories). Those extra steps aren't present at RfD. At most, there are times when it's appropriate to unlink the redirect or add WP:RCATs but those are automated steps that WP:XFDC handles. From my limited experience at TfD and CfD though, it does seem that the extra work needed at closure does not compensate for the extra work from needing two people reviewing the closure (especially at CfD because a bot that handles the clean-up). Consistency has come up and I would much rather consistently disallow non-admin delete closures at all XfD venues. I know it's tempting for non-admins to think they're helping by enacting these closures but it's not fair for them to be spinning their wheels. As for moving redirects, that's even messier than deleting them. There's a reason that WP:MOVEREDIRECT advises not to move redirects except for limited cases when preserving history is important. --Tavix20:16, 7 January 2025 (UTC)
@Tamzin: I do have one objection to this point of redundancy, which you are quite familiar with. Here, an AfD was closed as "transwiki and delete", however, the admin who did the closure does not have the technical ability to transwiki pages to the English Wikibooks, meaning that I, who does, had to determine that the outcome was actually to transwiki rather than blindly accepting a request at b:WB:RFI. Then, I had to mark the pages for G6 deletion, that way an admin, in this case you, could determine that the page was ready to be deleted. Does this mean that that admin who closed the discussion shouldn't have closed it, since they only have the technical ability to delete, not transwiki? Could I have closed it, having the technical ability to transwiki, but not delete? Either way, someone else would have had to review it. Or, should only people who have importing rights on the target wiki and admin rights on the English Misplaced Pages be allowed to close discussions as "transwiki and delete"? JJPMaster (she/they) 12:04, 8 January 2025 (UTC)
I do support being explicit when a non-administrator can close a discussion as "delete" and I think that explicitly extending to RfD and CfD is appropriate. First, there can be a backlog in both of these areas and there are often few comments in each discussion (and there is usually not the same passion as in an AfD). Second, the delete close of a non-administrator is reviewed by an administrator before action is taken to delete the link, or category (a delete close is a two-step process, the writeup and the delete action, so in theory the administrators workload is reduced). Third, non-admins do face administrator accountability for their actions, and can be subject to sanction. Fourth, the community has a role in reviewing closing decisions at DRV, so there is already a process in place to check a unexperienced editor or poor close. Finally, with many, if not most discussions for deletion the outcome is largely straight forward. --Enos733 (talk) 20:01, 7 January 2025 (UTC)
There is currently no rule against non-admin delete closures as far as I know; the issue is the practical one that you don't have the ability to delete. However, I have made non-admin delete closures at AfD. This occurred when an admin deleted the article under consideration (usually for COPYVIO) without closing the related AfD. The closures were not controversial and there was no DRV. Hawkeye7(discuss)20:31, 7 January 2025 (UTC)
The situation you're referring to is an exception allowed per WP:NACD: If an administrator has deleted a page (including by speedy deletion) but neglected to close the discussion, anyone with a registered account may close the discussion provided that the administrator's name and deletion summary are included in the closing rationale. --Tavix20:37, 7 January 2025 (UTC)
Bad idea to allow, this sort of closure is just busy work, that imposes more work on the admin that then has to review the arguments, close and then delete. Graeme Bartlett (talk) 22:05, 7 January 2025 (UTC)
(1) As I've also noted in the other discussion, the deletion process guidelines at WP:NACD do say non-admins shouldn't do "delete" closures and do recognize exceptions for CfD and TfD. There isn't a current inconsistency there between guidelines and practice. (2) In circumstances where we do allow for non-admin "delete" closures, I would hope that the implementing admin isn't fully reviewing the discussion de novo before implementing, but rather giving deference to any reasonable closure. That's how it goes with requested move closers asking for technical help implementing a "moved" closure at WP:RM/TR (as noted at WP:RMNAC, the closure will "generally be respected by the administrator (or page mover)" but can be reverted by an admin if "clearly improper"). SilverLocust💬08:41, 9 January 2025 (UTC)
Comment - A couple things to note about the CFD process: It very much requires work by admins. The non-admin notes info about the close at WT:CFD/Working, and then an admin enters the info on the CFD/Working page (which is protected) so that the bot can perform the various actions. Remember that altering a category is potentially more labour intensive than merely editing or deleting a single page - every page in that category must be edited, and then the category deleted. (There are other technical things involved, like the mess that template transclusion can cause, but let's keep it simple.) So I wouldn't suggest that that process is very useful as a precedent for anything here. It was done at a time when there was a bit of a backlog at CfD, and this was a solution some found to address that. Also - since then, I think at least one of the regular non-admin closers there is now an admin. So there is that as well. - jc3709:14, 9 January 2025 (UTC)
If the expectation is that an admin needs to review the deletion discussion to ensure they agree with that outcome before deleting via G6, as multiple people here are suggesting, then I'm not sure this is worthwhile. However, I have had many admins delete pages I've tagged with G6, and I have been assuming that they only check that the discussion was indeed closed as delete, and trust the closer to be responsible for the correctness of it. This approach makes sense to me, because if a non-admin is competent to close and be responsible for any other outcome of a discussion, I don't see any compelling reason they can't be responsible for a delete outcome and close accordingly. —Compassionate72719:51, 9 January 2025 (UTC)
Some closers, and you're among them, have closing accuracy similar to many sysops. But the sysop can't/shouldn't "trust" that your close is accurate. Trustworthy though you are, the sysop must, at very minimum, check firstly that the close with your signature on it was actually made by you (signatures are easily copied), secondly that the close wasn't manifestly unreasonable, and thirdly that the CSD is correct. WP:DRV holds the deleting sysop responsible for checking that the CSD were correctly applied. G6 is for uncontroversial deletions, and if there's been an XFD, then it's only "uncontroversial" if the XFD was unanimous or nearly so. We do have sysops who'll G6 without checking carefully, but they shouldn't. Basically, non-admin closing XFDs doesn't save very much sysop time. I think that if your motive as a non-admin is to relieve sysops of labour, the place you're of most use is at RfC.—S MarshallT/C11:28, 12 January 2025 (UTC)
if your motive as a non-admin is to relieve sysops of labour, the place you're of most use is at RfC alternatively you should consider becoming an administrator yourself. Thryduulf (talk) 13:20, 12 January 2025 (UTC)
In all the cases I have dealt with, the admin's reason for deletion (usually copyvio) was completely different to the issues being debated in the AfD (usually notability). The closing statement was therefore something like "Discussion is now moot due to article being deleted for <reason> by <admin>". Hawkeye7(discuss)20:10, 14 January 2025 (UTC)
I think most all the time, experienced closers will do a great job and that will save admin time because they will not have to construct and explain the close from scratch, but there will be some that are bad and that will be costly in time not just for the admin but for the project's goal of completing these issues and avoiding disruption. I think that lost time is still too costly, so I would oppose non-admin delete closes. (Now if there were a proposal for a process to make a "delete-only admin permission" that would be good -- such motivated specialists would likely be more efficient.) Alanscottwalker (talk) 16:44, 12 January 2025 (UTC)
As I said at the "Non-Admin XFD Close as Delete" section, I support non-admins closing RfDs as Delete. If TfDs have been made an exception, RfDs can be too, especially considering RfD backlogs. Closing a heavily discussed nomination at RfD is more about the reading, analysis and thought process at arriving at the outcome, and less about the technicality of the subsequent page actions. I don't see a significant difference between non-admins closing discussions as Delete vs non-Delete. It will help making non-admins mentally prepared to advance to admin roles. Jay 💬14:53, 14 January 2025 (UTC)
Should WP:NOTDIRECTORY be more specific about phone numbers, etc.?
That talk page has been checked by at least 100 registered editors during the last month, which makes it one of our better watched pages. WhatamIdoing (talk) 18:22, 9 January 2025 (UTC)
Apparently. :) Getting no response in 36 hours was surprising. The silence could mean "no objection" (since I'm not proposing a change, just a clarification that already used to be there), but since it's a policy page, it would be good to have something more tangible. Gamapamani (talk) 08:20, 10 January 2025 (UTC)
Does my name technically violate the promotional username policy?
I wouldn't say "Tectonic setting" and "Background" are interchangeable for any reader, the first is much more specific. CMD (talk) 00:25, 13 January 2025 (UTC)
In this review the set of section headings was Tectonic setting, Earthquake, Impact or Aftermath, making for an odd Table of contents for the non-expert reader because one section heading was for experts and the others were for the general audience. The techtonics were a historical background so I advised to make all the section titles for the general audience.-TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 05:30, 13 January 2025 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
I'm broadly in favor of this proposal—I looked over the essay and most of it is aligned with what seems standard in album articles—but there are a few aspects that feel less aligned with current practice, which I'd want to reexamine before we move forward with promoting this:
The section Recording, production suggests What other works of art is this producer known for? as one of the categories of information to include in a recording/production section. This can be appropriate in some cases (e.g., the Nevermind article discusses how Butch Vig's work with Killdozer inspired Nirvana to try and work with him), but recommending it outright seems like it'd risk encouraging people to WP:COATRACK. My preference would be to cut the sentence I quoted and the one immediately following it.
The section Track listing suggests that the numbered-list be the preferred format for track listings, with other formats like {{Track listing}} being alternative choices for "more complicated" cases. However, in my experience, using {{Track listing}} rather than a numbered list tends to be the standard. All of the formatting options currently listed in the essay should continue to be mentioned, but I think portraying {{Track listing}} as the primary style would be more reflective of current practice.
The advice in the External links section seems partially outdated. In my experience, review aggregators like Metacritic are conventionally discussed in the "Critical reception" section instead these days, and I'm uncertain to what extent we still link to databases like Discogs even in ELs.
(As a disclaimer, my familiarity with album articles comes mostly from popular-music genres, rock and hip-hop in particular. I don't know if typical practice is different in areas like classical or jazz.) Overall, while I dedicated most of my comment volume to critiques, these are a fairly minor set of issues in what seems like otherwise quite sound guidance. If they're addressed, it's my opinion that this essay would be ready for prime time. ModernDayTrilobite (talk • contribs) 15:19, 13 January 2025 (UTC)
Me too, though sometime last year, I unexpectedly had some (inexplicably strong) pushback on the tracklist part with an editor or two. In my experience, using the track list template is the standard, and I can't recall anyone giving me any pushback for it, but some editors apparently prefer just using numbers. I guess we can wait and see if there's any current pushback on it. 17:01, 13 January 2025 (UTC) Sergecross73msg me17:01, 13 January 2025 (UTC)
They came to WT:ALBUMS upset that another editor was changing track lists from "numbered" to "template" formats. My main response was surprised, because in my 15+ years of article creations and rewrites, I almost exclusively used the tracklist template, and had never once received any pushback.
So basically, I personally agree with you and MDT above, I'm merely saying I've heard someone disagree. I'll try to dig up the discussion. Sergecross73msg me17:50, 14 January 2025 (UTC)
I can see the numbered-list format being used for very special cases like Guitar Songs, which was released with only two songs, and had the same co-writers and producer. But I imagine we have extremely few articles that are like that, so I believe the template should be the standard. Elias 🦗🐜 12:23, 14 January 2025 (UTC)
ModernDayTrilobite, regarding linking to Discogs, some recent discussions I was in at the end of last year indicate that it is common to still link to Discogs as an EL, because it gives more exhaustive track, release history, and personnel listings that Misplaced Pages - generally - should not.--3family6 (Talk to me | See what I have done) 14:14, 15 January 2025 (UTC)
There were several discussions about Discogs and an RfC here. As a user of {{Discogs master}}, I agree with what other editors said there. We can't mention every version of an album in an article, so an external link to Discogs is invaluable IMO. AstonishingTunesAdmirer連絡22:34, 13 January 2025 (UTC)
We badly need this to become part of the MOS. As it stands, some editors have rejected the guidelines as they're just guidelines, not policies, which defeats the object of having them in the first place. Popcornfud (talk) 16:59, 13 January 2025 (UTC)
I recently wrote my first album article and this essay was crucial during the process, to the extent that me seeing this post is like someone saying "I thought you were already an admin" in RFA; I figured this was already a guideline. I would support it becoming one. DrOrinScrivello (talk) 02:00, 14 January 2025 (UTC)
I have always wondered why all this time these pointers were categorized as an essay. It's about time we formalize them; as said earlier, there are some outdated things that need to be discussed (like in WP:PERSONNEL which advises not to use stores for credits, even though in the streaming era we have more and more albums/EPs that never get physical releases). Also, song articles should also have their own guidelines, IMV. Elias 🦗🐜 12:19, 14 January 2025 (UTC)
I get the sense it'd have to be a separate section from this one, given the inherent complexity of album articles as opposed to that of songs. Elias 🦗🐜 14:56, 14 January 2025 (UTC)
I think it needs work--I recall that a former longtime album editor, Richard3120 (not pinging them, as I think they are on another break to deal with personal matters), floated a rewrite a couple of years ago. Just briefly: genres are a perennial problem, editors love unsourced exact release dates and chronology built on OR (many discography pages are sourced only to random Billboard, AllMusic, and Discogs links, rather than sources that provide a comprehensive discography), and, like others, I think all the permutations of reissue and special edition track listings has gotten out of control, as well as these long lists of not notable personnel credits (eight second engineers, 30 backing vocalists, etc.). Also agree that the track listing template issue needs consensus; if three are acceptable, then three are acceptable--again, why change it to accommodate the names of six not notable songwriters? There's still a divide on the issue of commercial links in the body of the article--I have yet to see a compelling reason for their inclusion (WP is, uh, not for sale, remember?), when a better source can always be found (and editors have noted, not that I've made a study of it, that itunes often uses incorrect release dates for older albums). But I also acknowledge that since this "floated" rewrite never happened, then the community at large may be satisfied with the guidelines. Caro7200 (talk) 13:45, 14 January 2025 (UTC)
Regarding the personnel and reissue/special edition track listing, I don't know if I can dig up the discussions, but there seems to be a consensus against being exhaustive and instead to put an external link to Discogs. I fail to see how linking to Billboard or AllMusic links for a release date on discographies is OR, unless you're talking about in the lead. At least in the case of Billboard, that's an established RS (AllMusic isn't the most accurate with dates).-- 3family6 (Talk to me | See what I have done) 13:53, 14 January 2025 (UTC)
I meant that editors often use discography pages to justify chronology, even though Billboard citations are simply supporting chart positions, Discogs only states that an album exists, and AllMusic entries most often do not give a sequential number in their reviews, etc. There is often not a source (or sources) that states that the discography is complete, categorized properly, and in order. Caro7200 (talk) 14:05, 14 January 2025 (UTC)
Myself, I've noticed that some of the sourcing recommendations are contrary to WP:RS guidance (more strict, actually!) or otherwise outside consensus. For instance, MOS:ALBUMS currently says to not use vendors for track list or personnel credits, linking to WP:AFFILIATE in WP:RS, but AFFILIATE actually says that such use is acceptable but not preferred. Likewise, MOS:ALBUMS says not to use scans of liner notes, which is 1. absurd, and 2. not actual consensus, which in the discussions I've had is that actual scans are fine (which makes sense as it's a digital archived copy of the source).--3family6 (Talk to me | See what I have done) 14:05, 14 January 2025 (UTC)
The tendency to be overreliant on liner notes is also a detriment. I've encountered some liner notes on physical releases that have missing credits (e.g. only the producers are credited and not the writers), or there are outright no notes at all. Tangentially, some physical releases of albums like Still Over It and Pink Friday 2 actually direct consumers to official websites to see the credits, which has the added problem of link rot (the credits website for Still Over Itno longer works and is a permanent dead link). Elias 🦗🐜 15:04, 14 January 2025 (UTC)
That turns editors to using stores like Spotify or Apple Music as the next-best choice, but a new problem arises -- the credits for a specific song can vary depending on the site you use. One important thing we should likely discuss is what sources should take priority wrt credits. For an example of what I mean, take "No Love". Go to Spotify to check its credits and you'd find the name Sean Garrett -- head to Apple Music, however, and that name is missing. I assume these digital credits have a chance to deviate from the albums' physical liner notes as well, if there is one available. Elias 🦗🐜 15:11, 14 January 2025 (UTC)
Moreover, the credits in stores are not necessarily correct either. An example I encountered was on Tidal, an amazing service and the only place where I could find detailed credits for one album (not even liner notes had them, since back then artists tried to avoid sample clearance). However, as I was double checking everything, one song made no sense: in its writing credits I found "Curtis Jackson", with a link to 50 Cent's artist page. It seemed extremely unlikely that they would collaborate, nor any of his work was sampled here. Well, it turns out this song sampled a song written by Charles Jackson of The Independents. AstonishingTunesAdmirer連絡16:39, 14 January 2025 (UTC)
PSA and AstonishingTunesAdmirer, I agree that it's difficult. I usually use both the physical liner notes and online streaming and retail sources to check for completeness and errors. I've also had the experience of Tidal being a great resource, and, luckily, so far I've yet to encounter an error. Perhaps advice for how to check multiple primary sources here for errors should be added to the proposed guideline.--3family6 (Talk to me | See what I have done) 17:00, 14 January 2025 (UTC)
At this point, I am convinced as well that finding the right sources for credits should be on a case-by-case basis, with the right amount of discretion from the editor. While I was creating List of songs recorded by SZA, which included several SoundCloud songs where it was extremely hard to find songwriting credits, I found the Songview database useful for filling those missing gaps. More or less the credits there align with what's on the liner notes/digital credits. However, four issues, most of which you can see by looking at the list I started: 1) they don't necessarily align with physical liner notes either, 2) sometimes names are written differently depending on the entry, 3) there are entries where a writer (or co-writer) is unknown, and 4) some of the entries here were never officially released and confirmed as outtakes/leaks (why is "BET Awards 19 Nomination Special" here, whatever that means?). Elias 🦗🐜 22:59, 14 January 2025 (UTC)
Yeah, I've found it particularly tricky when working on technical personnel (production, engineering, mixing, etc.) and songwriting credits for individuals. I usually use the liner notes (if there are any), check AllMusic and Bandcamp, and also check Tidal if necessary. But I'll also look at Spotify, too. I know they're user-generated, so I don't cite them, but I usually look at Discogs and Genius to get an idea if I'm missing something. Thank you for pointing me to Songview, that will probably also be really helpful. 3family6 (Talk to me | See what I have done) 12:50, 15 January 2025 (UTC)
(@3family6, please see WP:PROPOSAL for advice on advertising discussions about promoting pages to a guideline. No, you don't have to start over. But maybe add an RFC tag or otherwise make sure that it is very widely publicized.) WhatamIdoing (talk) 23:37, 14 January 2025 (UTC)
Before posting the RfC as suggested by WhatamIdoing, I'm proposing the following changes to the text of MOS:ALBUM as discussed above:
Eliminate What other works of art is this producer known for? Keep the list of other works short, as the producer will likely have their own article with a more complete list. from the "Recording, production" sub-section.
Rework the text of the "Style and form" for tracklistings to:
The track listing should be under a primary heading named "Track listing".
A track listing should generally be formatted with the {{Track listing}} template. Note, however, that the track listing template forces a numbering system, so tracks originally listed as "A", "B", etc., or with other or no designations, will not appear as such when using the template. Additionally, in the case of multi-disc/multi-sided releases, a new template may be used for each individual disc or side, if applicable.
Alternate forms, such as a table or a numbered list, are acceptable but usually not preferred. If a table is used, it should be formatted using class="wikitable", with column headings "No.", "Title" and "Length" for the track number, the track title and the track length, respectively (see Help:Table). In special cases, such as Guitar Songs, a numbered list may be the most appropriate format.
Move Critical reception overviews like AcclaimedMusic (using {{Acclaimed Music}}), AnyDecentMusic?, or Metacritic may be appropriate as well. from "External links" to "Album ratings templates" of "Critical reception", right before the sentence about using {{Metacritic album prose}}.
Re-write this text from "Sourcing" under "Track listing" from However, if there is disagreement, there are other viable sources. Only provide a source for a track listing if there are exceptional circumstances, such as a dispute about the writers of a certain track. Per WP:AFFILIATE, avoid commercial sources such as online stores and streaming platforms. In the rare instances where outside citations are required, explanatory text is useful to help other editors know why the album's liner notes are insufficient. to Per WP:AFFILIATE, commercial sources such as online stores and streaming platforms are acceptable to cite for track list information, but secondary coverage in independent reliable sources is preferred if available. Similarly, in the "Personnel" section, re-write Similar to the track listing requirements, it is generally assumed that a personnel section is sourced from the liner notes. In some cases, it will be necessary to use third-party sources to include performers who are not credited in the liner notes. If you need to cite these, use {{Cite AV media}} for the liner notes and do not use third party sources such as stores (per WP:AFFILIATE) or scans uploaded to image hosting sites or Discogs.com (per WP:RS). to Similar to the track listing requirements, it is generally assumed that a personnel section is sourced from the liner notes. If you need to cite the liner notes, use {{Cite AV media}}. Scans of the physical media that have been uploaded in digital form to repositories or sites such as Discogs are acceptable for verification, but cite the physical notes themselves, not the user-generated transcriptions. Frequently, it will be necessary to use third-party sources to include performers who are not credited in the liner notes. Per WP:AFFILIATE, inline citations to e-commerce or streaming platforms to verify personnel credits are allowed. However, reliable secondary sources are preferred, if available.
Additional guidance has been suggested for researching and verifying personnel and songwriting credits. I suggest adding It is recommended to utilize a combination of the physical liner notes (if they exist) with e-commerce sites such as Apple Music and Amazon, streaming platforms such as Spotify and Tidal, and databases such as AllMusic credits listings and Songview. Finding the correct credits requires careful, case-by-case consideration and editor discretion. If you would like assistance, you can reach out to the albums or discographies WikiProjects. The best section for this is probably in "Personnel", in the paragraph discussing that liner notes can be inaccurate.
The excessive listing of personnel has been mentioned. I suggest adding the following to the paragraph in the "Personnel" section beginning with "The credits to an album can be extensive or sparse.": If the listing of personnel is extensive, avoid excessive, exhaustive lists, in the spirit of WP:INDISCRIMINATE. In such cases, provide an external link to Discogs and list only the major personnel to the list.
If you have any additional suggestions, or suggestions regarding the wording of any of the above (I personally think that four needs to be tightened up or expressed better), please give them. I'm pinging the editors who raised issues with the essay as currently written, or were involved in discussing those issues, for their input regarding the above proposed changes. ModernDayTrilobite, PSA, Sergecross73, AstonishingTunesAdmirer, Caro7200, what do you think? Also, I realize that I never pinged Fezmar9, the author of the essay, for their thoughts on upgrading this essay to a guideline.--3family6 (Talk to me | See what I have done) 17:21, 15 January 2025 (UTC)
The proposed edits all look good to me. I agree there's probably some room for improvement in the phrasing of #4, but in my opinion it's still clear enough as to be workable, and I haven't managed to strike upon any other phrasings I liked better for expressing its idea. If nobody else has suggestions, I'd be content to move forward with the language as currently proposed. ModernDayTrilobite (talk • contribs) 17:37, 15 January 2025 (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.
reverts all edits
Hello everyone. I have an idea for the Misplaced Pages coders. Would it be possible for you to design an option that, with the click of a button, automatically reverts all edits of a disruptive user? This idea came to my mind because some people create disposable accounts to cause disruption in all their edits... In this case, a lot of time and energy is consumed by administrators and reverting users to undo all the vandalism. If there were a template that could revert all the edits of a disruptive user with one click, it would be very helpful. If you think regular users might misuse this option, you could limit it to Misplaced Pages administrators only so they can quickly and easily undo the disruption. Hulu2024 (talk) 17:31, 13 January 2025 (UTC)
Is this tool active in all the different languages of Misplaced Pages? I couldn't perform such an action with the tool you mentioned. Hulu2024 (talk) 17:51, 13 January 2025 (UTC)
That script requires the Misplaced Pages:Rollback permission, which is available only for admins and other trusted users. Admins and other users with the tool have gotten in trouble for using it inappropriately. I never use it myself, as I find the rollback in Twinkle quite sufficient for my needs. Donald Albury17:54, 13 January 2025 (UTC)
@Schazjmd Sorry. Does your option can reverse all edits of a user in different page's with clicking on button ? i think you mean that massrollback can reverse all edits in a special wiki page... not all edits of edits of disruptive user in multiple pages ? or i'm wrong ??? Hulu2024 (talk) 04:23, 14 January 2025 (UTC)
Hello everyone. I don’t know who is in charge for coding the Translate page on Misplaced Pages. But I wanted to send my message to the Misplaced Pages coders, and that is that in the Misplaced Pages translation system, the information boxes for individual persons (i.e personal biography box- see: Template:Infobox person) are not automatically translated, and it is time-consuming for Misplaced Pages users to manually translate and change the links one by one from English to another language. Please, could the coders come up with a solution for translating the information template boxes? Thank you. Hulu2024 (talk) 17:32, 13 January 2025 (UTC)
Hi Hulu2024, this also applies to the section above. If your proposal only applies to the English Misplaced Pages then it is probably best to post it at WP:VPT in the first instance. If it is only about the Persian Misplaced Pages then you may wish to try there. If it is more general then you could try Meta:, or, for more formal proposals, phabricator. Phil Bridger (talk) 18:51, 13 January 2025 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
i quit this will go no where im extremely embarassed and feel horrible i dont think ill try again
I would like to start this proposal by saying that this concept was a proposal in 2009 which failed for obvious reasons. But in this year, 2025, we need it as its happened a bunch. its already under personal attacks but this I feel and a couple other Wikipedians that it should be codified as their is precedent for blocking users who discriminate. Here’s a list of the things I want to include in this policy. edit: This policy is intended to target blatant and admitted instances of discrimination. If the intent behind an action is ambiguous, users should continue to assume good until the intent is.
Just as being a member of a group does not give one special requirements to edit, it also does not endow any special privileges. One is not absolved of discrimination against a group just because one claims to be a member of that group.
Im aware that this never really happens but its good to go over
A user may not claim without evidence that a user is affected by/are any of the above (idk how to term this).
A user may not claim that users with these disabilities/beliefs/races/genders shouldn’t edit Misplaced Pages.
A user may not imply a user is below them based on the person.
calling people woke simply cause they are queer is discrimination.
Also I would like to propose a condition.
Over reaction to what you think is discrimination (accidental misgendering and wrong pronouns) and the user apologizes for it is not grounds for an entry at ani.
This should be used as a guideline.
discrimination is defined as acts, practices, or policies that wrongfully impose a relative disadvantage or deprivation on persons based on their membership in a salient social group. This is a comparative definition. An individual need not be actually harmed in order to be discriminated against. He or she just needs to be treated worse than others for some arbitrary reason. If someone decides to donate to help orphan children, but decides to donate less, say, to children of a particular race out of a racist attitude, he or she will be acting in a discriminatory way even if he or she actually benefits the people he discriminates against by donating some money to them.
Misplaced Pages article on discrimination
I would also like to say this would give us negative press coverage by right wing media and I’ll receive shit. But I don’t care i can deal with it •Cyberwolf•talk?16:37, 16 January 2025 (UTC)
This largely seems like behavior that already is sanctionable per WP:NPA and WP:UCOC (and the adoption of the latter drew complaints at the time that it in itself was already unnecessarily redundant with existing civility policy on en.wiki). What shortcomings do you see with those existing bodies of policy en force? signed, Rosguill16:45, 16 January 2025 (UTC)
The fact that punishments should be a little more severe for users who go after a whole group of editors. As its not an npa its an attack on a group •Cyberwolf•talk?16:57, 16 January 2025 (UTC)
NPA violations are already routinely met with blocks and sitebans, often on sight without prior warning for the level of disparagement you're describing. Do you have any recent examples on hand of cases where the community's response was insufficiently severe? signed, Rosguill17:07, 16 January 2025 (UTC)
Ill grab some my issue is admins can unblock without community input it should be unblock from admin then= they have to appeal to the community •Cyberwolf•talk?17:10, 16 January 2025 (UTC)
Noting that I've now taken the time to read through the three cases listed at the top--two of them ended in NOTHERE blocks pretty quickly--I could see someone taking issue with the community's handling of RowanElder and Jwa05002, although it does seem that the discussion ultimately resulted in an indef block for one and an apparently sincere apology from the other. signed, Rosguill17:13, 16 January 2025 (UTC)
I think the real problem is that in order to block for any reason you have to take them to a place where random editors discuss whether they are a "net positive" or "net negative" to the wiki, which in principle would be a fair way to decide, but in reality is like the work of opening an RFC just in order to get someone to stop saying random racist stuff, and it's not worth it. Besides, remember the RSP discussion where the Daily Mail couldn't be agreed to be declared unreliable on transgender topics because "being 'gender critical' is a valid opinion" according to about half the people there? I've seen comments that were blatant bigoted insults beneath a thin veneer, that people did not take to ANI because it's just not worth the huge amount of effort. There really needs to be an easy way for administrators to warn (on first violation) and then block people who harass people in discriminatory ways without a huge and exhausting-for-the-complainer "discussion" about it -- and a very clear policy that says discrimination is not OK and is always "net negative" for the encyclopedia would reduce the complexity of that discussion, and I think is an important statement to make.
By allowing it to be exhaustively debated whether thinly-veiled homophobic insults towards gay people warrant banning is Misplaced Pages deliberately choosing not to take a stance on the topic. A stance needs to be taken, and it needs to be clear enough to allow rapid and decisive action that makes people actually afraid to discriminate against other editors, because they know that it isn't tolerated, rather than being reasonably confident their targets won't undergo another exhausting ANI discussion. Mrfoogles (talk) 17:04, 16 January 2025 (UTC)
I agree that a blind eye shouldn't be turned against discrimination against groups of Misplaced Pages editors in general, but I don't see why we need a list that doesn't include social class but includes hobbies. The determining factor for deciding whether something is discrimination should be how much choice the individual has in the matter, which seems, in practice, to be the way WP:NPA is used. Phil Bridger (talk) 17:02, 16 January 2025 (UTC)
I agree hobbies doesn't need to be included. Haven't seen a lot of discrimination based on social class? I think this needs to be taken to the Idea Lab. Mrfoogles (talk) 17:06, 16 January 2025 (UTC)
@cyberwolf Strong support in general (see above) but I strongly suggest you take this to the idea lab, because it's not written as a clear and exact proposal and it would probably benefit a lot from being developed into an RFC before taking it here. In the current format it probably can't pass because it doesn't make specific changes to policy. Mrfoogles (talk) 17:08, 16 January 2025 (UTC)
Wait...does this mean I won't be able to discriminate against people whose hobby is editing Misplaced Pages? Where's the fun in that? Anonymous17:09, 16 January 2025 (UTC)
In general, I fail to see the problem this is solving. The UCoC and other policies/guidelines/essays (such as WP:NPA, WP:FOC, and others) already prohibit discriminatory behavior. And normal conduct processes already have the ability to lay down the strictest punishment theoretically possible - an indefinite ban - for anyone who engages in such behavior.
I do not like the idea of what amounts to bureaucracy for bureaucracy’s sake. That is the best way I can put it. At worst, this is virtue signaling - it’s waving a flag saying “hey, public and editors, Misplaced Pages cares about discrimination so much we made a specific policy about it” - without even saying the next part “but our existing policies already get people who discriminate against other editors banned, so this was not necessary and a waste of time”. I’ll happily admit I’m proven wrong if someone can show evidence of a case where actual discrimination was not acted upon because people were “concerned” it wasn’t violating one of those other policies. -bɜ:ʳkənhɪmez | me | talk to me!20:56, 16 January 2025 (UTC)
To clarify, all the comments about "why is this included" or "why is this not included" are part of the reason I'm against a specific policy like this. Any disruption can be handled by normal processes, and a specific policy will lead to wikilawyering over what is or is not discrimination. There is no need to try to define/specifically treat discrimination when all discriminatory behaviors are adequately covered by other policies already. -bɜ:ʳkənhɪmez | me | talk to me!22:27, 16 January 2025 (UTC)
We should be relating to other editors in a kind way. But this proposal appears to make the editing environment more hostile with more blocking on the opinion of one person. We do discrimonate against those that use Misplaced Pages for wrong purposes, such as vandalism, or advertising. Pushing a particular point of view is more grey area. The proposal by cyberwolf is partly point of view that many others would disagree with. So we should concentrate policies on how a user relates to other editors, rather than their motivations or opinions. Graeme Bartlett (talk) 20:50, 16 January 2025 (UTC)
I think this is valuable by setting a redline for a certain sort of personal attack and saying, "this is a line nobody is permitted to cross while participating in this project." Simonm223 (talk) 20:57, 16 January 2025 (UTC)
It is not possible for the content of a discussion to be "discriminatory". Discrimination is action, not speech. This proposal looks like an attempt to limit discourse to a certain point of view. That's not a good idea. --Trovatore (talk) 21:13, 16 January 2025 (UTC)
Cambridge says that discrimination is : "treating a person or particular group of people differently, especially in a worse way from the way in which you treat other people, because of their race, gender, sexuality, etc".
OK, look, I'll concede part of the point here. Yes, if I'm a dick to (name of group) but not to (name of other group), I suppose that is discrimination, but I don't think a discrimination policy is a particularly useful tool for this, because what I should do is not be a dick to anybody.
What I'm concerned about is that the policy would be used to assert that certain content is discriminatory. Say someone says, here's a reliable source that says biological sex is real and has important social consequences, and someone else says, you can't bring that up, it's discriminatory. Well, no, that's a category error. That sort of thing can't be discriminatory. --Trovatore (talk) 01:29, 17 January 2025 (UTC)
The examples you use show that we've been dealing effectively without this additional set of guidelines; it would be more convincing that something was needed if you had examples where the lack of this policy caused bad outcomes. And I can see it being used as a hammer; while we're probably picturing "as a White man, I'm sure that I understand chemistry better than any of you lesser types" as what we're going after, I can see some folks trying to wield it against "as a Comanche raised on the Comanche nation, I think I have some insights on the Comanche language that others here are overlooking." As such, I'm cautious. -- Nat Gertler (talk) 21:49, 16 January 2025 (UTC)
Not needed. Everything the proposal is talking about would constitute disruptive behavior, and we can block or ban someone for being disruptive already. No need to break disruption down into its component parts, and write rules for each. Blueboar (talk) 22:07, 16 January 2025 (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.
Repeated false retirement
There is a user (who shall remain unnamed) who has "retired" twice and had the template removed from their page by other users because they were clearly still editing. They are now on their third "retirement", yet they last edited a few days ago. I don't see any policy formally prohibiting such behavior, but it seems extremely unhelpful for obvious reasons. Anonymous17:13, 16 January 2025 (UTC)
Unless the material is harmful to Misplaced Pages or other users, users have considerable leeway in what they may post on their user page. Personally, I always take "retirement" notices with a grain of salt. If a user wants to claim they are retired even though they are still actively editing, I don't see the harm to anything but their credibility. If I want to know if an editor is currently active, I look at their contributions, not at notices on their user or talk page. Donald Albury22:07, 16 January 2025 (UTC)
I can't imagine that this calls for a policy. You're allowed to be annoyed if you want. No one can take that away from you. But I'm missing an explanation of why the rest of us should care. --Trovatore (talk) 22:13, 16 January 2025 (UTC)
This seems a little prickly, my friend. Clearly, the other two users who removed older retirement notices cared. At the end of the day, it's definitely not the most major thing, but it is helpful to have a reliable and simple indication as to whether or not a user can be expected to respond to any kind of communication or feedback. I'm not going to die on this hill. Cheers. Anonymous22:41, 16 January 2025 (UTC)
Comment: It would appear Jimbo responded indirectly in a interview: 
Sm8900 (talk) 17:46, 24 December 2024 (UTC)
Facepalm). Not gonna link what I can't (quickly) verify!)) (As an aside, I think "afflicted with" can come across as a bit... charged? Just something to note.)
Done 
Pope Francis and Brigette Lundy-Paine
.jpg)
FYI
Moved to 
