This is the Village pump (all) page which lists all topics for easy viewing. Go to the village pump to view a list of the Village Pump divisions, or click the edit link above the section you'd like to comment in. To view a list of all recent revisions to this page, click the history link above and follow the on-screen directions.
Discussions older than 7 days (date of last made comment) are moved to a sub page of each section (called (section name)/Archive).
Policy
Looking for guideline, forgot where it is
I recall a while ago, I found and/or was pointed to a guideline that basically stated cosmetic changes to links or templates should not be done if there is no change in functionality or where the page links (such as replacing a link to an redirect with the link to the target page). Can anyone point me into the direction of that guideline? Steel1943 (talk) 19:26, 25 October 2024 (UTC)[reply]
COSMETICBOT is a policy for bots, which includes tools that assist manual editing, and it identifies itself as a general guideline for other "bot-like" purely manual editing. So it might apply with different strength depending on how many such edits someone is doing, how they are doing them, and if/how-much disruption it's creating for other editors working on certain pages. DMacks (talk) 13:30, 27 October 2024 (UTC)[reply]
Digital storage time by law
Is there a legal time frame that WMF is forced to store IP addresses of users? It seems the WMF has given them out before and has said to an Indian court that they are going to again. If there is no legal reason then they should be purged after a certain time frame. This would make it difficult for checkusers and sockpuppet admin. We could easily store them in an area that only those groups would have access to. Then the WMF could say that the court would have to subpoena someone from those groups. Thoughts?Music Air BB (talk) 17:08, 27 October 2024 (UTC)[reply]
Foundation:Privacy policy#How Long Do We Keep Your Data? states Once we receive Personal Information from you, we keep it for the shortest possible time that is consistent with the maintenance, understanding, and improvement of the Wikimedia Sites, and our obligations under applicable law. In most instances, Personal Information is deleted, aggregated or de-identified after 90 days. and further links to Foundation:Legal:Data retention guidelines, which states that IP addresses will be kept for "at most 90 days" and then "deleted, aggregated or deintentified".
The Sharing section of the privacy policy details when, why and with whom your data may be shared by the Foundation. The "For legal reasons" subsection begins We will access, use, preserve, and/or disclose your Personal Information if we reasonably believe it necessary to satisfy a valid and legally enforceable warrant, subpoena, court order, law or regulation, or other judicial or administrative order. However, if we believe that a particular request for disclosure of a user's information is legally invalid or an abuse of the legal system and the affected user does not intend to oppose the disclosure themselves, we will try our best to fight it.Thryduulf (talk) 17:20, 27 October 2024 (UTC)[reply]
We should knock that 90 days down to 7 days but leave in a limited access area for 90. Only sockpuppet and checkusers would have access to it. What about email addresses? I thought no human had access to those? Music Air BB (talk) 17:31, 27 October 2024 (UTC)[reply]
The IP information (for accounts) is already limited access - only checkusers (with good reason), stewards (sometimes), some techies and some staff can access it. It gets automatically removed from the database after 90 days. That seems a reasonable timescale to me - it's mostly used to reduce abuse of the site, which can be chronic. As for email, if it's in a database and can be displayed to a human, then a human can access it. The people operating a database (in this case the WMF) can access pretty much anything that's in there, with enough effort. They surely have policies and checks in place to prevent willy-nilly access, but it can't really be stopped on a technical level. -- zzuuzz(talk)18:39, 27 October 2024 (UTC)[reply]
The WMF's privacy policy is not something that the en.wp community has any control over. If you want to suggest changes to them you need to do so elsewhere. I don't know where that place is, but the people who watch meta:Wikimedia Forum are likely to. Thryduulf (talk) 18:42, 27 October 2024 (UTC)[reply]
There is a shedload of fora I could have posted to including Wikipedia:Village pump (WMF) where there seems to be some drama about the WMF take down of an article and doxing because of a court order in India. The article contents are still in a sub-section of a parent article so I don't know why the grand uproar. Just expand that section like a WP:COAT. I doubt many people have Wictionary:Village Pump (WMF) on a watchlist nor the main WMF ones. This page probably has the best input. Music Air BB (talk) 19:45, 27 October 2024 (UTC)[reply]
Perhaps somewhat ironically, the OP is the sock of a user who has already been subject to multiple blocks. The 90 day limited access was enough to confirm this without any doubt. GirthSummit (blether)16:48, 29 October 2024 (UTC)[reply]
I have trouble locating AfD deletion discussion
How do I find the discussion concerning deletion of Effie Awards? I attempted to search the tool in Articles for Deletion section, but it doesn't yield the relevant result.
I have encountered many kinds of COI editors, autobiographers and paid editors (disclosed and undisclosed) in my time but I've just stumbled upon something that I've never seen before; a page where the text strongly suggested the user had paid someone else to write text for them that they were then posting on Wikipedia. The telling part was that when copying the text they had left in part of the correspondence they'd been having, not unlike when users forget to remove the "Sure, here is a draft Wikipedia page" text from a chatbot.
The page has already been tagged for speedy deletion by @FifthFive because it was in any event autobiographical, promotional and NOTAWEBHOST, but out of mere academic curiosity: is there any area of policy that deals with this kind of thing? AntiDionysius (talk) 21:20, 29 October 2024 (UTC)[reply]
Copyright is the first thing that comes to mind. AIUI, unless it is a work for hire or you explicitly assign the copyright to me (or release it under a Wikipedia-compatible free license), you own the copyright and my posting it here would be a violation of your copyright. Other than that I don't think there is any need for policy here - if I wrote it and it would be deleted (NOTWEBHOST, spam, etc) then delete it for that reason, if it isn't a copyright violation and it wouldn't be deleted if it was self written then I don't see any benefit to deleting it. Thryduulf (talk) 22:06, 29 October 2024 (UTC)[reply]
Re copyright, really depends on jurisdiction, the communications between the parties and (as mentioned) an absence of any express licence, but if it was clear between the parties the text was going to be used for Wikipedia, it wouldn't be unreasonable to argue that an implied licence exists compliant with Wikipedia's requirements. Regards, Goldsztajn (talk) 23:45, 29 October 2024 (UTC)[reply]
In this particular case, it seemed like it was very clear that the writer was aware their work was for Wikipedia (not that this stopped them from writing promotionally, but anyway) but yeah I can see how those contextual questions would be important. AntiDionysius (talk) 00:26, 30 October 2024 (UTC)[reply]
For sure, yeah - it strikes me as likely to end up being promotional most of the time (why else would you pay someone if not to promote something?) but I'm not suggesting we need a policy to ban the practice as such. AntiDionysius (talk) 00:27, 30 October 2024 (UTC)[reply]
If it's promotional enough that deletion is better than rewriting, then it should be deleted for being promotional regardless of who wrote it. If it's not that promotional then it shouldn't be deleted, regardless of who wrote it. Thryduulf (talk) 01:35, 30 October 2024 (UTC)[reply]
In my limited dealings with COI's, a thought occurred to me that, in working with them, I risk subjecting myself to suspicion of being a COI editor myself (Wikilawyering intensifies). Cheers. DN (talk) 00:07, 30 October 2024 (UTC)[reply]
Date redirects to portals?
16 August 2006 points to the current events portal as a result of this discussion. However, date redirects will continue to come up at RfD, some some wider community discussion and input is helpful on whether or not the current events portal is an appropriate target for mainspace redirects. See also: this ongoing discussion for some context.
The second question is easy: Yes, portals are part of the encyclopaedia. As to the first question, portals are reader-facing content and so I see no reason why they wouldn't be appropriate targets for mainspace redirects, given that uncontroversially target mainspace redirects to reader-facing templates and categories when they are the best target. Whether the port is the best target for a given date will depend on the specific date but in general the portal should always be an option to consider. Thryduulf (talk) 01:32, 30 October 2024 (UTC)[reply]
I agree with this. The portal is definitely not always the best option and it has its limitations, but, as I wrote at WP:RDATE it should be considered and assessed along with mainspace articles. Cremastra (u — c) 01:44, 30 October 2024 (UTC)[reply]
If a namespace doesn't have the same standards as mainspace, then the reader shouldn't be redirected there while possibly not realizing they are now outside of mainspace. Yes, there is more content at Portal:Current events/August 2006 than at 2006#August, but the reader is now facing a decades-old page with no quality control, where links to Breitbart are misleadingly labeled as (AP). Chaotic Enby (talk · contribs) 00:50, 6 November 2024 (UTC)[reply]
Portal does have the same standards as mainspace. That a portal is not up to those standards is no different to an article being in bad shape - fix it. Thryduulf (talk) 00:54, 6 November 2024 (UTC)[reply]
No, because they are not articles. Two things can be held to the same standard without being the same thing. Criterion P1 previously allowed that (indirectly) but it was repealed in 2023 due to lack of use. Thryduulf (talk) 19:42, 7 November 2024 (UTC)[reply]
Then they aren't held to the same standards... More in general, no, they obviously aren't held to the same standards, e.g. a portal page doesn't have to be a notable topic but may be purely decorative or (as is the case with the date pages) be a list of mainly non-notable things, failing WP:NOTNEWS and WP:LISTN. That some standards are the same (BLP, copyvio, ...) can also be said for e.g. user talk pages, and we don't redirect to these pages either. Fram (talk) 20:24, 7 November 2024 (UTC)[reply]
We don't redirect to user talk pages because they aren't reader-facing, so that's irrelevant. We don't hold reader-facing templates and categories to article content policies (because they aren't articles) but we do redirect to them. Don't conflate quality standards with inclusion policies, they are not the same thing. Thryduulf (talk) 21:15, 7 November 2024 (UTC)[reply]
I wasn´t aware that the standards we were talking about were solely quality standards, whatever these may be, and not content standards, sourcing standards, ... I´m sadly not amazed that you consider these irrelevant when deciding what to present to our readers. Fram (talk) 21:37, 7 November 2024 (UTC)[reply]
In theory, I think portals should be held to the same CSD criteria as articles. But of course the A criteria actually only apply to articles. Cremastra (u — c) 22:08, 7 November 2024 (UTC)[reply]
There's a lot of random junk in portalspace, but yes, it is part of the encyclopedia. Just like categories and templates, portals are reader-facing content. CFA💬
I didn't really have super strong opinions on portals until seeing this one link to Breitbart, twice, in a misleading way. This is not okay. I agree with Fram that clearly Portals are not being held up to the same standards as regular articles and it might be a bad idea to redirect readers to them. Toadspike[Talk]23:00, 7 November 2024 (UTC)[reply]
I saw this on CENT, and I am confused by the question. Portal:Current events/2006 August 16 is very different from something like Portal:Belgium, and it doesn't make sense to pretend they are the same to establish policy. And what does "part of the encyclopedia" even mean? "Interpreting a confusing phrase" is a terrible way to decide redirect targets. For the specific question of "Should dates redirect to the Current Events portal rather than to a page like August 2006 ... I don't know. I don't see a compelling reason why they can't, nor a compelling reason why they should. Walsh90210 (talk) 15:45, 8 November 2024 (UTC)[reply]
Issues with antiquated guideline for WP:NBAND that essentially cause run of the mill non-notable items to be kept
5.) Has released two or more albums on a major record label or on one of the more important indie labels (i.e., an independent label with a history of more than a few years, and with a roster of performers, many of whom are independently notable).
6.) Is an ensemble that contains two or more independently notable musicians, or is a musician who has been a reasonably prominent member of two or more independently notable ensembles. This should be adapted appropriately for musical genre; for example, having performed two lead roles at major opera houses. Note that this criterion needs to be interpreted with caution, as there have been instances where this criterion was cited in a circular manner to create a self-fulfilling notability loop (e.g., musicians who were "notable" only for having been in two bands, of which one or both were "notable" only because those musicians had been in them.)
These appear to have been put together by a very small number of editors over a decade ago and hasn't seen much change since then and I feel it's much more lenient than just about anything else. This SNG defines a "label" that has been around for over "a few years" that has a roster of performers as "important". So, any group of people who have released two albums through ANY verifiable label that has exited for more than a few year can end up being kept and this isn't exactly in line with GNG. I believe a discussion needs to be held in order to bring it to GNG expectations of now.
Especially given how broadly the various criteria have been "interpreted" in deletion discussions, the best way to go about it is just to deprecate the whole thing. Rely on the GNG for band notability, and if that results in a heap of articles on ephemeral outfits, garage bands and local acts vanishing, huzzah. Ravenswing 09:07, 30 October 2024 (UTC)[reply]
The SNG isn't workable in the age of digital distribution. It's very easy to create "an independent label with a history of more than a few years". If someone wants to suggest a way to reform the SNG, I am open to solutions. But deprecation is a simple alternative if we can't. The GNG is always a good standard because it guarantees we have quality sources to write an article. Shooterwalker (talk) 14:22, 30 October 2024 (UTC)[reply]
I was active in AfD discussions when NBAND was pretty new, and it was useful for dealing with a flood of articles about garage bands and such, but I think our standards in general have tightened up since then, and I agree it is time to review it. There is the possibility, however, that revising NBAND may require as much discussion as revising NSPORT did. Donald Albury17:49, 30 October 2024 (UTC)[reply]
I guess the underlying question is: Is there actual harm in having a permastub about a band that proves to be borderline in GNG terms? Consider this:
"Alice and Bob are a musical duo in the science fiction genre.[1] They released their first album, Foo, in 2019 and their second, Bar, in 2020. Both albums were released by Record Label.[2] They are primarily known for singing during a minor event.[3]"
I'm asking this because I think that the nature of sources has changed, particularly for pop culture, since NBAND and the GNG were written. We now have subjects that get "attention from the world at large", but which aren't the Right™ kind of sources and, while these Wrong™ sources definitely provide "attention", some of that attention might not provide biographical information (which means we're looking at a short article).
For example, instead of getting attention in the arts section of a daily newspaper, they're getting attention from Anthony Fantano on YouTube. He's an important music critic,[1] but I suspect that our knee-jerk reaction is "Pffft, just some YouTuber, totally unreliable". Consequently, we might rate a band that we theoretically intend to include ("attention from the world at large") as not meeting the GNG (because the whole field relies on the Wrong™ style of sources). WhatamIdoing (talk) 19:02, 30 October 2024 (UTC)[reply]
Keep in mind that like most other notability guidelines, it is a presumed assumption that a topic is notable if it meets these criteria. If you do an exhaustive Before and demonstrate there is no significant coverage beyond the sourcing to satisfy there criteria, the article should still be deleted. None of the SNGs are geared towards preventing this type of challenge. — Masem (t) 19:30, 30 October 2024 (UTC)[reply]
If we had to yield to presumptive notability about some random band because it released two albums with Backyard Trampoline Recordings established few years ago and had to do exhaustive search to disprove notability, we're getting setup for a situation where removal is 10x more challenging than article creation. So.. I see a great value in scrapping NBAND 5, and 6. Graywalls (talk) 00:47, 31 October 2024 (UTC)[reply]
Welcome to WP:SNGs. As Masem said, they're supposed to be a rough idea of gauging notability before exhaustively searching for sources. But pretty much all of them have ended up being used as means to keep articles about trivial or run-of-the-mill subjects. Thebiguglyalien (talk) 19:37, 30 October 2024 (UTC)[reply]
Graywalls listed two criteria but the main discussion seems to be about the 1st (#5). I agree with Graywalls on that. With the evolution of the industry, the label criteria is no longer a useful indicator as it once was and IMO #5 should be removed or modified. Sincerely, North8000 (talk) 19:13, 30 October 2024 (UTC)[reply]
I've noticed that as well. I think #6 has some value still, while #5 is like saying an author who has published two or more books by a major publishing house is presumed notable. Way too low a bar without requiring some level of reception of those albums/books. (WP:NAUTHOR doesn't have that 2-book criteria, of course, just seems like parallel benchmarks.) Schazjmd(talk)13:25, 31 October 2024 (UTC)[reply]
On the other hand, in this case, I suspect that an artist that "has released two or more albums on a major record label or on one of the more important indie labels" will in 99% of cases have enough coverage to clear the GNG bar. I'd like to see an example of one that doesn't. Black Kite (talk)13:29, 31 October 2024 (UTC)[reply]
The definition of important as said in #5 is "history of more than a few years, and with a roster of performers, many of whom are independently notable". This would mean that a garage band is notable, because they've released two CD-R albums on Rotten Peach Recordings which has been around for 3 1/2 years, has a roster of performers and some of whom have a Wikipedia page on them. Often time "notable" is determined by the presence of a stand alone Wikipedia page. When you look at the page, many band member pages are hopelessly non-notable, but removal takes an AfD. So a simple deletion can become a time consuming multi-step AfD. Graywalls (talk) 19:18, 31 October 2024 (UTC)[reply]
Not opining on that band's notability, but Metal Blade is a famous independent label that has existed for 42 years, has released material by very high-profile bands, and is distributed by Sony - it's not some one-person imprint operating out of their garage. Black Kite (talk)11:28, 1 November 2024 (UTC)[reply]
One suggestion I would add is to make these two criteria apply only to bands before a specific year, that year being where physical releases still dominated over digital sales. I don't know the exact year but I am thinking it's like around 2000 to 2010. There may still be older groups during the time of physical releases that don't yet have articles that would fall into one of these criteria. Masem (t) 20:02, 31 October 2024 (UTC)[reply]
As someone who's had WP:DSMUSIC watchlisted for most of their editing history, and who tends towards deletion at that, I actually don't see much of a problem with these criterions. It certainly seems true that the majority of musicians who are signed to a label or a member of multiple bands with two other musicians who meet WP:GNG themselves meet GNG. I do think it is sometimes justified to accept less-than-GNG sourcing in articles where a SNG is met (see Wikipedia:Articles for deletion/John LeCompt for this as it applies to c6 specifically) and more importantly, NMUSIC contains language that allows deleting articles even where it is technically met (see Wikipedia:Articles for deletion/Rouzbeh Rafie for an extended argument about that. Mach6123:29, 31 October 2024 (UTC)[reply]
I've understood these criterion to be supplementing GNG, that is, that if a band or individual artist meets one or more of these criterion, they *likely* are notable. However, in the past when I was a younger and less experienced editor, I think I did understand these as being additions or alternatives to GNG. So I think that should be clarified. This has come up on the deletion discussion for Jayson Sherlock. He is a member or former member of several very notable bands, and for that reason I presumed that he would easily have independent coverage about him specifically. However, to my surprise, there's only one interview of him in a reliable source that would provide notability (there's some interviews on personal blogs or minor sites that wouldn't be RS except for him making statements about himself). But at least one editor has used the above criterion to argue that the article should be kept.--3family6 (Talk to me | See what I have done) 12:20, 1 November 2024 (UTC)[reply]
Just as an aside, interviews do not contribute to GNG unless they include secondary independent SIGCOV (such as a substantial background introduction by the interviewer). JoelleJay (talk) 15:39, 1 November 2024 (UTC)[reply]
That's how I see most SNGs (and the outliers ought to follow their lead). At the very least, we can clarify that NBAND is meant as an indicator for the GNG, and not a substitute. Shooterwalker (talk) 02:04, 2 November 2024 (UTC)[reply]
As someone who thought the old NSPORTS was wildly overinclusive and needed cleanup... these NBAND guidelines don't seem that bad? If two plainly notable musicians were discovered to have done some obscure team-up in the 1970s, that does indeed seem to be a notable topic and useful to have linked somewhere, even if there isn't tons of info on this collaboration. It's worth mentioning because minor subtopics are often merged to the overarching topic (e.g. songs to the album), but there may not be a clear merge location for this if both parties were equal contributors, and a short separate article is an acceptable compromise. Similarly, the complaint about #5 seems to be about just how "indie" the hypothetical label is, but this seems like a solvable problem. If a band fails GNG, that implies that either their two albums really were from a very obscure indie outfit and thus also fail NBAND, or else that we have some sort of non-English sources issue where we may consider keeping on WP:CSB grounds (i.e. that sources probably do exist to pass GNG, but they're difficult to find, and we can trust they exist because this was a major and notable label releasing the band's work). About the only suggestion I can offer is that the comment in 6 about avoiding circular notability could probably be phrased in the sense of GNG, i.e. that the two notable musicians need to both meet GNG and then this will create a new, safe NBAND notability for their collaboration. SnowFire (talk) 17:36, 4 November 2024 (UTC)[reply]
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
To anyone unfamiliar with this, admin recall is a new process that is exactly what it sounds like. Currently, there is a 30 day petition period: if 25 people sign it, the admin then needs to pass a new RfA within 30 days to keep the tools. Should we change the petition period?
Option A: Keep the petition period the same (30 days)
Option B: Change the petition period to 7 days
Option C: Some other time period (like 14 or 15 days?) that's longer than a week but shorter than a month.
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.
Drm310 and I have a polite disagreement on the interpretation of WP:PAID, and I may very well be mistaken. What is very clear is if an editor is an employee of a company, they are a paid editor. What's not clear is what happens if the editor is the owner of a company. Sure, there's a conflict of interest, but are they a paid editor? I'll quote Drm310, as he says it better than me. "They said that they were a company owner and not an employee. You said that makes them a paid editor. I always interpreted the policy as: if a person is receiving (or expecting) compensation as part of their job, then they're a paid editor. But if they have an ownership stake in the company/organization, then they fall outside the definition of employee. Are we now interpreting it so that owners are paid editors too, because they are drawing an income from their business?" My position is that an owner of a company counts as a paid editor by virtue of the ownership (they don't even need to be drawing an income). Is that position correct, or is it a step too far wrt WP:PAID? --Yamla (talk) 15:25, 4 November 2024 (UTC)[reply]
I would read it as you do, @Yamla:; they have a vested interest in the company being successful, which, in my book, ultimately means getting "something" out of it (which in most cases will mean an income of sorts). Reading it differently smacks slightly of (wiki-)lawyering. Lectonar (talk) 15:35, 4 November 2024 (UTC)[reply]
Hmm. Well, Lectonar, it has always seemed to me that the line "you stand to gain from your editing, so it's effectively paid, even if you aren't actually paid for the editing" is wikilawyering, so evidently that's a matter of point of view.
I have always taken it that paid editing does not include editing about one's own business, in line with what Drm310 says, but my experience is that many, perhaps most, administrators take it the way that Yamla and Lectonar do. In a way it doesn't make much difference, as in either case the conflict of interest issue applies, but there are ways in which it may make a difference. In my opinion the most important way it may make a difference is the purely practical consideration that most owners of businesses writing about their own businesses don't recognise "paid editing" as a description of what they are doing, so it is, in my opinion, more helpful to use other wording which they will be more likely to understand than insisting "yes it is paid editing". (There's already enough of a problem with: "No, I'm not paid to edit Wikipedia, it's just part of my job" ... "Yes, but if it's part of a job that you are paid for then it's paid work" ... "Yes, but..." without adding another layer of room for misunderstanding.) I therefore think it's more helpful to treat the expression "paid editing" as not applying to editing about one's own business.
Theoretically it isn't up to us to decide what the expression means, because it's part of the Wikimedia Foundation's terms of use, over which we have no jurisdiction. However, those terms of use refer to "each and any employer, client, intended beneficiary and affiliation" and as far as I can see there is no definition or clarification of the word "affiliation", so that doesn't really help. JBW (talk) 16:10, 4 November 2024 (UTC)[reply]
I'm of the opinion that PAID applies to owners, but the wording of WP:PAID is ambiguous enough that a reasonable person might very well disagree with that opinion, and I think that should be clarified on that page. An owner of a company can still be an employee of that company (e.g. if the company is set up as a C corporation they can be considered an employee for tax and insurance purposes). I don't think the applicability of the paid-contribution disclosure should change depending on how you structure your company if the role in the company is similarly situated. If you are compensated by working at a company as an owner or otherwise, that needs to be disclosed. Even situations where an owner does not receive direct financial payments or dividends from their ownership of the company (like with a smaller startup company) they would still need to disclose that under WP:PAID, as money is not the only form of compensation. Even in a sole proprietorship they are directly paid for their work at the company, the same as if they were an employee. Owning the company should not be a loophole precluding the need for disclosure. - Aoidh (talk) 16:48, 4 November 2024 (UTC)[reply]
@Aoidh: Has anyone suggested that it should preclude the need for disclosure? If they have, I haven't seen where tgey have done so. I assumed it was obvious that there is a need for disclosure of one's position because it is a conflict of interest. JBW (talk) 22:30, 4 November 2024 (UTC)[reply]
@JBW: I'm sure I've seen it come up but I can't recall where. Someone with a COI reading Wikipedia:Conflict of interest might reasonably assume that if they are not considered a paid editor, then they are not required to disclose anything. The difference between the PAID verbiage (required...requirement..you must disclose...you must not use administrative tools for any paid-editing activity) contrasts with the less strict wording of non-PAID COI (expected to disclose...should disclose...COI editing is strongly discouraged). The section Wikipedia:Plain and simple conflict of interest guide#Disclosure also makes this distinction. I'm not saying I don't think COIs should be disclosed, but someone with a COI who is going to split hairs about whether an owner of a company make one a paid editor would be likely to split hairs there as well. - Aoidh (talk) 23:51, 4 November 2024 (UTC)[reply]
Jessintime I do not intend to tell you that your opinion on this as "absurd"; I prefer to just say that I respectfully disagree. You may like to consider which of those two approaches is more constructive. JBW (talk) 16:28, 4 November 2024 (UTC)[reply]
Jessintime OK, thanks for clarifying that. However, having looked at the article that you have linked, I am wondering what the absurd result you think would ensue. What is it that an owner of a company would be allowed to do which an employee wouldn't? Certainly not editing without disclosure of conflict of interest. JBW (talk) 22:36, 4 November 2024 (UTC)[reply]
From the policy page: Interns are considered employees for this purpose. So unpaid interns count as paid editors when editing the Starlink Wikipedia article for their employer. But edits by Elon Musk would not count as paid editing. That sounds like an absurd result to me. Do I misunderstand the policy? BusterD (talk) 19:42, 4 November 2024 (UTC)[reply]
Someone who has a few shares in a large company is one of its "owners" in law, but likely doesn't have a big enough financial stake in it to amount to a COI in Wikipedia terms. Someone who has most of the shares in a small company, on the other hand, has a COI.—S MarshallT/C22:10, 4 November 2024 (UTC)[reply]
If I may extend your example, if I were in the business of stocks or futures, I might actually have a stake (direct or otherwise) sufficient to put me in direct conflict, no matter which company is the subject. BusterD (talk) 23:00, 4 November 2024 (UTC)[reply]
I have just seen a message on Yamla's talk page, where I think he makes a point that I have tried to make, but he has expressed it perhaps more clearly than I have. He said: "In the end, whichever way the consensus goes, I think the combination of WP:PAID and WP:COI means the end result (though not the communication) ends up the same." Many of the comments above appear to be based on the assumption that not interpreting "paid editing" as including owner-editing would mean letting owners edit without disclosure, but it wouldn't. JBW (talk) 22:50, 4 November 2024 (UTC)[reply]
Thanks for copying my comment here, JBW. In my initial post, I meant "Sure, there's a conflict of interest" to cover this point, but failed to be clear. I do think the communication around paid editing is important, even if the end result (user has to declare a conflict) is the same. This is frequently a challenging concept to communicate to new editors. --Yamla (talk) 22:56, 4 November 2024 (UTC)[reply]
I think there may be a more fundamental misunderstanding of WP:PAID here than you think. Paid editing is about people being paid to edit. Let's take What is very clear is if an editor is an employee of a company, they are a paid editor to the point of absurdity: a burger flipper at a 40,000-location chain fast-food restaurant who edits the article about the chain is in no way being paid to make that edit. Their job is to flip burgers, not to do corporate PR. They do have a COI (positive or negative) due to the employment relationship, but unless the CEO or PR department or whoever is telling employees that editing Wikipedia is now part of their job it's not WP:PAID.But like many other things around here, since WP:PAID has stricter requirements and penalties than WP:COI, people tend to try to stretch the definitions as far as they possibly can to use the stricter requirements and penalties to combat editing they don't like. I won't be surprised if people in that space take objection to my paragraph above on the basis that restricting WP:PAID to the clear definitions would hamper their efforts to combat the spammer scourge.As for the business owner, if the business is making paid edits on behalf of clients then the company as a whole, including the owner, is being WP:PAID to edit on behalf of the company's clients. And the required disclosure includes those clients, not just their general ownership of the paid-editing company. On the other hand, if the business is making widgets then I'd say the owner's editing is a very major COI but it's not specifically WP:PAID. Anomie⚔00:21, 5 November 2024 (UTC)[reply]
I disagree with that interpretation of WP:PAID. The policy says: "Users who are compensated for any publicity efforts related to the subject of their Wikipedia contributions are deemed to be paid editors, regardless of whether they were compensated specifically to edit Wikipedia." I think it's completely reasonable to hold the belief that "publicity" is almost always part of the job of a company owner and other senior officers e.g., C-suite occupants, governing board members. ElKevbo (talk) 02:43, 5 November 2024 (UTC)[reply]
Yes, and even more than that, the owner, officers and board members are fiduciaries of the company, and "compensated" and "incentivized" by ownership and/or other compensation (money, goods or services -- possession of the company is a good) to work in the company's best interest, whether in editing Wikipedia, or elsewhere. -- Alanscottwalker (talk) 12:52, 5 November 2024 (UTC)[reply]
Certainly the sole or majority owner of the company has an actual or risk of COI (depending on which definition of COI you use), But "Paid" implies more that that.....that somebody is paying them and telling them what to do. North8000 (talk) 02:53, 5 November 2024 (UTC)[reply]
IMO WP:PAID should be split into its main two interpretations: "instructed (even if implicit, e.g. hired for publicity in general) to edit Wikipedia for compensation" and "direct financial interest in a subject". JoelleJay (talk) 17:39, 5 November 2024 (UTC)[reply]
The issue here is WP:COI, not WP:PAID. When you're PAID to edit, the owner (or someone acting on behalf on the owner) tells you 'your job is to do this for me'. If you don't, you lose your job/don't get paid, so that's where your incentive comes from. WP:PAID exists, among other reasons, because there are firms trying to sell these services to companies/owners, and companies/owners paying people to edit on their behalf so they can go 'we hired professionals, if they're an issue blame them!'. It's a special type of COI-editting that's common enough to have a special policy for that special type of COI editing.
When the owner themselves are doing the editing, all the special concerns of PAID disappears, save for the remaining one: COI-editting. But that's covered by WP:COI. There is nothing special about the owner of Mary Sue, owner of Certified Reiki Thetan-Level 3 Shop editing an article on her business, than Rocker Boy Joe writing about his band Rocket Bobs, or Jensen Huang vandalizing AMD articles through an account named User:AMDTROLL4V3R. They don't lose their jobs, they still have their income, and they don't get in trouble if they fail to deliver.
Headbomb {t · c · p · b}17:50, 5 November 2024 (UTC)[reply]
If your job includes promoting a business and you come to Wikipedia to promote that business, that is PAID editing, owner or otherwise. That someone would be fired for refusing is not the criteria, an owner is highly incentivized to promote their business and can expect to be compensated for that effort through business growth and profit, and it is the compensation element that makes an editor a paid editor. - Aoidh (talk) 17:58, 5 November 2024 (UTC)[reply]
There is no part of WP:PAID that suggests that a power dynamic or consequence for a failure to deliver is a determining factor, and owners are indeed compensated for their work. This is especially true when taking into account that compensation is not limited to remuneration. - Aoidh (talk) 19:27, 5 November 2024 (UTC)[reply]
Hey all. This was raised at Wikipedia:Edit_filter_noticeboard#graph_links_broken, but it appears the edit filter graphs, seen at [2], are not currently working and display an internal error. Would anyone happen to have an idea what happened to it? One idea that was raised over at EFN was that the log table may have been messed up by protected variables being introduced, but I'm not sure if that's the case or it's something else. — Preceding unsigned comment added by EggRoll97 (talk • contribs) 03:26, 23 October 2024 (UTC)[reply]
@EggRoll97: I'm about to get on a flight, but a quick look at the tool's error logs shows:
The abuse_filter_log table was deliberately removed from the wiki replicas in gerrit:1077360, pointing to two Phabricator tasks I don't have access to. It's likely to remain broken unless Danilo.mac puts in an amount of effort that's basically rewriting the tool from scratch. * Pppery *it has begun...04:30, 23 October 2024 (UTC)[reply]
I can not do anything while the abuse_filter_log tables are inaccessible. They were removed from replicas databases because some data in those tables are restricted, se T375751. Danilo.mac (talk) 19:49, 29 October 2024 (UTC)[reply]
So when I click on Notices a little popup show up and tells my notifications.
According to it I have 7 new notifications.
But if I press on it says I have no notifications. If I click on all notices it shows an error message: 7ab4ef4a-e38b-462a-ab56-edfdc2d62732] 2024-10-27 04:43:21: Fatal exception of type "InvalidArgumentException"
Weird. I have this problem, but they don't work when I click "all notifications". (If you reply to this, ping me - I still get those, for some reason.) -- asilvering (talk) 16:44, 28 October 2024 (UTC)[reply]
Same problem for me the notifications icon shows I have alerts, but when I click on it I get the error message: [2b363018-cbbb-45da-8f73-056cf4cbd0de] 2024-10-31 12:53:02: Fatal exception of type "InvalidArgumentException". and the icon greys out. A temporary work around is to go to Commons and click on your notifications from other wikis. Then they can be read, but only on Commons once, then they disappear from Commons. Mysterious! Netherzone (talk) 12:56, 31 October 2024 (UTC)[reply]
I've found that I can read them if they get over 30 notifs or so. So now I'm banking a truly stupid number of notifications so that I can at least tell what discussions the most recent ones are for. -- asilvering (talk) 14:43, 31 October 2024 (UTC)[reply]
Don't let it get too high. If the counter reaches 99 and more notifs come in, the icon doesn't show 100, 101 etc. but 99+ and the only way to find out how many you really have is to delete some until it drops to 99 or lower. Unread notifs get automatically deleted after a while, I think that it's about 16 months. --Redrose64 🌹 (talk) 20:24, 31 October 2024 (UTC)[reply]
Hello, when I click on my alerts bell at the top, it says "There are no notifications", even thought I can see there are. When I then click on "all notifications", I get the following: "[5aff3dcb-50f3-4b16-9566-60ba693bfa63] 2024-10-27 21:50:42: Fatal exception of type "InvalidArgumentException".
Any help would be appreciated. Thank you. Magnolia677 (talk) 21:54, 27 October 2024 (UTC)[reply]
Sounds just like my problem, just the other notification system.
I have been unable to test that one since I have no new Alerts. It does show my previous Alerts.
Searching for pages by category and talk page content
Does anyone know how you would search for all of the pages in a certain category whose associated talk page contains a certain string in its source? So, for instance, what search would return all of the pages in Category:Princesses in Greek mythology which contain "WikiProject Classical Greece and Rome" in their talk page's source? – Michael Aurel (talk) 07:18, 30 October 2024 (UTC)[reply]
Can be done in PetScan. Put that category name in "Categories", then go to "Templates&links" tab, put that template name there with " Use talk pages instead" checked. – SD0001 (talk) 08:25, 30 October 2024 (UTC)[reply]
As of recently (probably last Thursday), the snackbar popup I get from an archived / missing section link has stopped unpopping-up until I navigate away from the page.
For clarity, my other snackbars (e.g. "Redirected from Wikipedia:vpt") pop away normally. It's just the archived section one that persists. Folly Mox (talk) 13:03, 30 October 2024 (UTC)[reply]
That popup is generated by DiscussionTools, not the gadget. You can dismiss a popup on Minerva by tapping it (around a link if it includes one). Nardog (talk) 00:26, 31 October 2024 (UTC)[reply]
That's the DiscussionTools notification. It's supposed to stick around until you interact with it. Could you confirm whether it's dismissed if you directly tap on it? (If it is, it's working as-intended. If not, that's a bug we should fix.) DLynch (WMF) (talk) 02:45, 31 October 2024 (UTC)[reply]
Apologies for the delay everyone; yesterday was exhausting. After constructing a test case, I can confirm that the snackbar disappears properly when tapped. I feel like the persistence is new behaviour(?) but understand why such a message would be intentionally left around until interacted with.Perhaps removing the snackbar once e.g. the editing interface is opened might make more sense: it does look like a bug in the screenshots I posted (to me, anyway).And apologies for throwing the find-archived-section gadget under the bus: I wasn't previously aware that Mediawiki had incorporated the same functionality until reviewing the documentation for my OP above.I guess I was also wrong about DiscussionTools having no effect in Minerva: I don't see the "people in conversation" or "subscribe to thread", but upon reflection I suppose the linkable timestamps that point straight to a comment supplanting the prior requirement of diff hunting must be part of the extension as well. Folly Mox (talk) 12:58, 31 October 2024 (UTC)[reply]
Mobile editing and the reply tool don't reload the page when editing and then the popup remains. I don't know whether something could be done to make it disappear automatically on those actions. PrimeHunter (talk) 13:27, 31 October 2024 (UTC)[reply]
mw:Help:SourceEditor is pretty uninformative on this point, but maybe one of the devs who frequent this venue knows which hook triggers the opening of the edit interface and can add a snackbar disappear function there? Folly Mox (talk) 17:49, 31 October 2024 (UTC)[reply]
When using Twinkle to welcome new users, I am unable to add an article input to the Welcome Cookie Template like I can for some of the other welcome templates (e.g., "I noticed your contributions to Article")- it would be great if I could do this so I don't have to leave a separate message. Let me know if I am making any sense.
Are articles moved from userspace to mainspace not indexed?
So, recently I created FoodPharmer in my userspace and later moved to the mainspace. I keep noticing that search engines (Google, Bing) do not show this if you search "FoodPharmer Wikipedia" or "Revant Himatsingka Wikipedia". But the DYK page on him created 4 days after moving the page and his picture uploaded 8 days after (yesterday) shows up in the search results. This makes me wonder, is the article not showing up because it was initially in userspace (not-indexed)? —CX Zoom[he/him](let's talk • {C•X})16:35, 31 October 2024 (UTC)[reply]
How do overlapping range blocks work? For example, with these two:
51.191.128.0/17 blocked (block-evasion) on 2024-10-31T14:55:40Z by JBW until 2025-02-21T19:11:00Z. anononly: False, account creation blocked: False
51.191.0.0/16 blocked (block-evasion) on 2023-11-27T22:25:01Z by JBW until 2025-01-21T19:11:00Z. anononly: False, account creation blocked: False
An edit from 51.191.128.1 would (if I've done the math right) be in both ranges. In this particular case, both blocks have the same effect, but what if one was a hard block and the other a soft block? Which would apply? RoySmith(talk)03:14, 1 November 2024 (UTC)[reply]
I have notifications but it shows that there are no notifications
Occasionally when I check my notifications, the popup that appears will display "There are no notifications." even when at least one notification is present. Here is a picture:
is there a script to change parameter mane on every wiki article in a wiki project (si.wikipedia.org). The change i want to do is; replace "deadurl" or "dead-url" with "url-status" on all wiki articles using the cite web template. Or can someone fix the module so it happen automatically? si:Module:Citation/CS1VihirLak007hmu!/duh.05:51, 1 November 2024 (UTC)[reply]
For JWB, once you have it up and running, go to https://en.wikipedia.org/w/index.php?title=User:Ahecht/Scripts/Replace_dead-url.json&action=raw&ctype=application/json and save it as a .json file on your computer. In JWB, on the Setup tab, click "Import" and choose the file you saved. In the "Load" drop-down, choose "Replace dead-url". Then click on the Generate button, make sure Wiki Search is checked with insource:/dead\-?url *= */ in the search box, and hit the Generate button. When it's done, click outside the Generate box to close it. Then go to the "Edit" tab and click "Start" to start going through all the pages.
Once you're done, you can go to this page to see the remaining pages that need to be manually fixed. You may need to wait a few minutes first as there can be some lag between when you edit pages and when the search results catch up. --Ahecht (TALK PAGE)17:11, 1 November 2024 (UTC)[reply]
Perhaps someone who hangs out at VPT could take a look at this HD discussion. The OP seems to be experiencing the same issue described here, but it's not clear whether the problem is on the OP's side or Wikipedia's side. -- Marchjuly (talk) 06:12, 1 November 2024 (UTC)[reply]
Is it possible to find out a list of articles and redirects for Climate change in .... ?
Hi all
I'd like to spend a significant amount of time writing and working with experts on creating Climate change in NAME OF COUNTRY / STATE etc articles. First I would like to understand which do and don't exist. I tried making a simple list of all the countries to see redlinks however it seems that one or more users created a significant number of redirects so this doesn't work. I've been using List of sovereign states to create a list, but I'm sure there are other options like islands, states within countries etc. Is it possible to do a query or is there another way to find:
A list of existing articles for Climate Change in ...
A list of redirects for Climate change in ...
A way to have a live list of missing Climate change in NAME OF COUNTRY articles since simple redlinks don't work because of the redirects that have been created (I guess I could make a table of redlinks with comments on which are redirects as a basic version)
PrimeHunter thanks so much :) you always know the right answer! I can create a manual to update page from this now I think, if you or anyone else has any ideas about creating an automated page please let em know. Thanks again. John Cummings (talk) 12:57, 1 November 2024 (UTC)[reply]
PrimeHunter thanks again, super helpful. One final question, do you know if there is a template I could use to tell if a page includes a specific word or phrase? I would love a way to tell if articles for countries mention climate change. I know this is probably a very niche use case but I'm wondering if there is template that might do this for another reason. John Cummings (talk) 19:31, 1 November 2024 (UTC)[reply]
Is there a way to create a graph that shows how many pages are in a category (y-axis) over time (x-axis)? It would be particularly useful for error tracking categories. Failing that, a text-based way to monitor category population changes. -- GreenC02:40, 4 November 2024 (UTC)[reply]
There's also User:SDZeroBot/Category counter which I just finished setting up. Raw counts only, no graphs for now. (I noticed that the MusikBot task, apart from being disabled, stores the counts on-wiki which seems like an unsuitable place for large-scale storage, and it also requires an admin to enable new categories for counting.) – SD0001 (talk) 18:10, 4 November 2024 (UTC)[reply]
Tech News: 2024-45
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
Stewards can now make global account blocks cause global autoblocks. This will assist stewards in preventing abuse from users who have been globally blocked. This includes preventing globally blocked temporary accounts from exiting their session or switching browsers to make subsequent edits for 24 hours. Previously, temporary accounts could exit their current session or switch browsers to continue editing. This is an anti-abuse tool improvement for the Temporary Accounts project. You can read more about the progress on key features for temporary accounts. [3]
Wikis that have the CampaignEvents extension enabled can now use the Collaboration List feature. This list provides a new, easy way for contributors to learn about WikiProjects on their wikis. Thanks to the Campaign team for this work that is part of the 2024/25 annual plan. If you are interested in bringing the CampaignEvents extension to your wiki, you can follow these steps or you can reach out to User:Udehb-WMF for help.
The text color for red links will be slightly changed later this week to improve their contrast in light mode. [4]
View all 32 community-submitted tasks that were resolved last week. For example, on multilingual wikis, users can now hide translations from the WhatLinksHere special page.
Updates for technical contributors
XML data dumps have been temporarily paused whilst a bug is investigated. [5]
In depth
Temporary Accounts have been deployed to six wikis; thanks to the Trust and Safety Product team for this work, you can read about the deployment plans. Beginning next week, Temporary Accounts will also be enabled on seven other projects. If you are active on these wikis and need help migrating your tools, please reach out to User:Udehb-WMF for assistance.
The latest quarterly Language and Internationalization newsletter is available. It includes: New languages supported in translatewiki or in MediaWiki; New keyboard input methods for some languages; details about recent and upcoming meetings, and more.
Meetings and events
MediaWiki Users and Developers Conference Fall 2024 is happening in Vienna, Austria and online from 4 to 6 November 2024. The conference will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users.
It works for me in Firefox. You have to be logged in. Are you sure your login is working when they are missing? Please post an example link. PrimeHunter (talk) 15:27, 5 November 2024 (UTC)[reply]
Would it be possible to have redirects show up at the same level of importance as they would if the article was at that title? This is a little weird to explain but basically from my level of understanding search bar results are currently sorted roughly by how likely a user is to need that article. For example when you type Apollo in looking for the Apollo missions the first relevant result is Apollo 11, then 13, then others. This makes a lot of sense to me but I want to know if it's possible to include redirects into this.
Right now redirects only show up in the search bar below all the possible exact match results until fully typed exactly. For example if you start typing "New York Times" into the search bar it puts a bunch of court cases involving the NYT before the newspaper right up until you type the final S, at which point the newspaper goes to the top like it should have been. This is not intuitive for readers and if "New York Times" showed up at the level of importance that "The New York Times" did, it would be better for navigation. Another example is the Edvard Munch painting The Scream. It's really iconic and notable but a reader could very easily forget the "the" and just type "scream", at which point they would have to remember exactly "Scream (painting)" before they get the one they want because there are a bunch of other less important articles that do start with exactly "scream". This is terrible for navigation, obviously. But if "Scream (painting)" showed up in the search results where it would if the article was called that, that would fix the issue.
Redirects vary greatly in relevance. Science Times also redirects to The New York Times but isn't mentioned there. The redirect currently has seven views in the last 30 days.[6] I don't think it should inherit the importance of the newspaper and rank high when you start typing "science". PrimeHunter (talk) 21:58, 5 November 2024 (UTC)[reply]
there are in principle two kinds of redirecting, the orthographic and the semantic one. The semantic redirect has one extraneous property. It can point to a part of the article, that is some semantically dependent section. An orthographic redirect is about different writing of the lemma,so it will never point to only a part of the article. So both kinds of redirects can be differentiated by the presence or absence of the "#" separator in the target. And if you need to set a semantic redirect to a whole article, then add the separator without a section name. 2A02:3035:B07:530:180:786A:E014:DDFD (talk) 13:12, 6 November 2024 (UTC)[reply]
I fear that weighting all redirects equally to the main article title would do more harm than good. Many popular articles have lots of redirects, and in particular redirects that start with different letters than the main title. If there are ten really popular articles with redirects starting xyz... then they could dominate the completion suggestions. If you typed bro into the search box, you might be disappointed to see the top suggestions being Youtube, Barack Obama, Los Angeles Dodgers, New York Yankees, France, Brooklyn, Autism, HTTP cookie, Malcolm X, and Brooklyn Dodgers. (The relevant redirects are: Broadcast yourself, Brock Obama, Brooklyn/Los Angeles Dodgers, Bronx Bombers, Bro-C'hall, —, Broad Autism Phenotype, Browser cookie, Brother Malcolm, and —).
The common factor in your two examples are that they start with The. I think "ignoring common completion prefixes" might be a better approach. (It was #4 on our list of most promising tasks for working with an outside consultant in 2018.) Obvious ways to attempt this would be to ignore stop words (the, a, an, of, etc.), though we don't have stop word lists for all the languages we'd want to support, and it wouldn't catch wiki-specific common title prefixes like List of. Automatically finding candidates is possible, but I'd be afraid of blindly trusting them since, for example, Maria might be a very common prefix, since it is a very common name cross-culturally. You could also compare titles to existing redirects (The New York Times vs New York Times) for common ignorable prefixes, though there may not be enough data on smaller wikis. Implementation details require more thought, like preventing the "prefix" from being the whole title (The The) or everything up to a paren (To Be or Not to Be (book))—how do you know when to stop in those cases? What happens when a prefix-stripped title matches another title (The Dog vs Dog)? Do you require prefixes to be whole words (then you miss naj- in Polish, but you don't want to strip The off the front of Theater or Theodore)? If you automatically find el, la and los in Spanish, how do you make sure you get las? If you have à, le, la, and les, in French, should you add au and aux, and if so, how do you know? What do we do in Chinese or Japanese? Etc., etc., etc. Language is always complicated.
So, this is something that is on the Search Team's radar, but not currently near the top of our priority list. (Unfortunately we have a lot of infrastructure and query service work that needs our attention.) TJones (WMF) (talk) 19:50, 6 November 2024 (UTC)[reply]
Hi, thanks so much for the detailed reply. That's a great issue that I hadn't considered. Ignoring common prefixes isn't perfect (there are examples like Facebook, Inc. → Meta Platforms or Marquis de Lafayette → Gilbert du Motier, Marquis de Lafayette that I think also need to be fixed) but given I have no idea how to solve the problem you've pointed out I would settle for ignoring prefixes.
I do think there are some feasible ways around the other issues, though. The obvious question would be, does the change have to roll out for every language at once? Starting with one and then adding more seems a lot easier. That way a lot of the rules can be placed manually; I'll go through possible solutions to each of these issues, and while I'm sure some of them won't work and there will be many more issues, this seems like a surmountable challenge to me.
Okay, one at a time:
Manually include wiki-specific prefixes like List of
Manually exclude anything that will obviously cause problems like Maria
Like you said, specifically rely on existing redirects and don't remove prefixes unless it matches an existing redirect (The (band) for this example, the book has no redirects and could be excluded). Remember, while this isn't perfect and a lot of redirects will be missing, any improvement is good for navigation.
Even though the title is stripped internally for navigation purposes, display the actual article title in the dropdown menu so people can differentiate; this is already done for redirects, so someone typing dog could easily see The Dog and realize it's not what they're looking for.
Do not strip off whole words in the English Wikipedia, in Polish Wikipedia naj- can be marked to be stripped off from the word itself without it affecting anything in other languages
For cases like las, au, and aux, again ensure that it must be matched with an existing redirect. I don't know nearly enough about Chinese or Japanese to even venture at a solution, but I'm sure one could be found, and while that is being worked on it could be implemented in other language Wikipedias.
This sounds like phab:T372702 (though I don't think anyone else reported it clearing up for a bit); the latest update there (from about two weeks ago) is that the devs are having a hard time telling what the cause is, but added some additional logging to help track down the issue. 129.170.197.163 (talk) 02:24, 8 November 2024 (UTC)[reply]
All redlinks showing up as blue in Vector 2022 and Minerva when using older browsers
Hi! Recently, all redlinks (such as this one) have started showing up as blue. This only seems to happen when using the Vector 2022 or Minerva skins on Firefox 77/Chrome 87 and below (haven't checked other browsers), and doesn't affect the original Vector.
The question is, why is the user running those browser versions? Windows 7 (which is EOL) and up should be able to run Chrome 109 and Firefox 115. What OS are you using? Sjoerd de Bruin(talk)13:41, 7 November 2024 (UTC)[reply]
I'm actually using Firefox 66 on Estobuntu [et] 14.04 (which I know is really outdated, but I'm currently working on figuring out how to install a newer OS). I used this site to check what browser versions the issue happened on. I'll just use the original Vector skin as a workaround until I can install a newer browser. 2A00:807:E5:D017:AD41:2CD8:279A:980F (talk) 00:50, 8 November 2024 (UTC)[reply]
If you have to run the old browsers for some reason then you can create an account and save the last CSS version in your CSS to automatically load it on all English Wikipedia pages when you are logged in. Or save it in meta:Special:MyPage/global.css to load in all Wikipedia languages and Wikimedia wikis when you are logged in. Your account automatically works at all of them and keeps you logged in. PrimeHunter (talk) 15:40, 7 November 2024 (UTC)[reply]
Which means the rule will not work for browsers from before that time.
MediaWiki does support some pretty old browsers, but skins are neither core nor does the level of support provided by core for old browsers require more than "you can read the page" for some value of "reasonable". See also mw:Compatibility. Izno (talk) 15:45, 7 November 2024 (UTC)[reply]
Doing this is prone to false positives (since not all references are inline and/or correctly formatted, and there’s a number of special cases), and therefore should be done cautiously instead of blindly running through them. There have been bots that have flagged these in the past but they have had community-wide approval. novovtalkedits12:54, 8 November 2024 (UTC)[reply]
When editing on mobile, I've noticed what I think is a bug, but I haven't posted to Phabricator, because I'm not entirely sure, so I wanted to hear others input. When I edit on my phone (which is a OnePlus phone runnning on Android, if that matters) in the browser Google (don't have the app, did not test with it and only tested Google), whether in visual or source editing I can't highlight a word or phrase that has the red wavy line underneath. If I try, the screen freezes and I get booted from Google. When I reenter, it's as though I never tried to edit in the first place. Doesn't occur on my computer editing with Google however.
Does anyone else have this bug? Its not like I can't just edit on computer, but I wanted to bring this to someone's attention, so it can be fixed in the future.Thank you in advance for replies. 90.133.232.139 (talk) 21:36, 7 November 2024 (UTC)[reply]
Proposal for trial: assignment to a small random group of editors to elevated permissions for a fixed short term by sortition.
Test 1: Selected extended-confirmed editors, who have edited in the past 100 days, get AfC and/or new page reviewer, which have backlogs. They still have to read the instructions. (PCR is too weak for a practical experiment imo.)
Test 2: Selected auto/confirmed editors, who edited recently, get bumped into extended-confirmed.
Rules: Any admin can strike for any behavior at any time; one strike and you're out; no extension of term; no exceptions. Also: you cannot refuse permissions, and your editing or sanction history (but not block history) has no bearing on whether you get or don't get permissions. Every admin and editor with equal permissions capable of oversight will have a readily-accessible list of test editors. (It's not difficult to deduce otherwise.)
Numbers: As a conservative estimate for a first experiment, maybe 200 editors on both tests simultaneously for 6 months, depending on the activity level of those in the sample -- if 20 editors substantially increase their activity in response, that's measurable and manageable.
The purpose is to increase engagement by somewhat active editors across the spectrum, and perhaps even motivate requests for permanent permissions and adminship down the line. In that spirit, if a test editor loses permissions in the one-strike rule, it should have minimal or zero bearing on requesting permissions in future. This is a learning and motivational experience. That permissions here are ultimately reversible and have oversight means that, on balance, if an ill-behaved editor now ends up being able to credibly seek permissions in future, this model, should it be causative, was indeed a success.
A high barrier to entry of WP adminship and some permissions, combined with thanklessness of tasks and relatively low social prestige, means that we are probably below rate-of-replacement on adminship, and there are backlogs for areas needing permissions. Sortition, if it results in participation, relieves this burden. It also increases representative fairness and ideological diversity to those who would handle the content and administrative backlogs. (Afaik this is a WP-unique issue.) In Polish Wikipedia the exclusionary effect on new candidates of acquaintancy among admins was studied (Spychała et al 2014 "Does the Administrator Community ... Acquaintance Relation?"); so if a similar phenomenon exists in all permissions then sortition would help disrupt it.
On the effects of granting priveliges/power: In (Sassenberg et al 2014 "Power corrupts: revisited"), the relationship of elevated power and a sense of communal responsibility vs individual corruption (whether one is elevated as opposed to the other) is complex with contradictory results in the literature. In general, if people are in a socially-oriented environment and goals, which I'd suggest epitomizes WP editing, then power would orient them toward the former. However, the review also suggests that the perception of power as an increase opportunity or promtion, rather than just increased responsibility, is a big part of the increased motivational effects, which would suggest that since sortition may lower the prestige of elevated priveliges, it would have a negative effect on motivation; but this seems again highly social-context- and goal-dependent in the literature.
I have trouble imagining us (i.e., those of us who have achieved a measure of power and control in the current system) being willing to give up control over permissions, no matter how slight this might be.
That said, I think that both Test 1 and Test 2 would be worthwhile experiments, and I specifically suggest considering selecting candidates for Test 2 from among those who are nearly EXTCONF anyway (e.g., they have the time but they're short 100–200 edits, or they have the edits, but they're short 1–2 months).
Even if there's an element of power and status to them, the vast majority of what people with advanced permissions do is just drudgery. It seems really unlikely to me that somebody randomly assigned NPP or even admin is actually going to want to use them. And one of the main functions of the perm system is to reduce the attack surface these rights offer by only giving them to people motivated enough to ask for it.
Also, yes AfC and NPP are backlogged, but 'reviewing the reviewers' is also work and there are very few admins doing it. This would massively increase that workload - who's going to pick up the slack? – Joe (talk) 17:58, 9 October 2024 (UTC)[reply]
I imagine that an editor who receives a note saying something like "You've been given this permission temporarily. Please read up and use it if you want" might use it a few times, at least to try it out. If they have a positive experience, they might request to the perm later through the usual channels.
Giving a perm only to those motivated enough to ask means that a higher percentage of the requesters is improperly motivated. Undeclared paid editors will be more motivated to ask for the permission than an ordinary volunteer. WhatamIdoing (talk) 18:20, 9 October 2024 (UTC)[reply]
I think "checking up on whether people did the thing correctly" and "doing the thing" are really different actions. So while I think it's obvious that this would increase the amount of "checking up on each other" work, I'm not sure it's the admins at AfC and NPP that will be shouldering that work, though I'm sure we probably would do so somewhat disproportionately. -- asilvering (talk) 21:44, 25 October 2024 (UTC)[reply]
I am quite a fan of sortition for filling real-world positions, both where it is used in many countries (mainly for selecting juries) and for some other positions. A few thoughts on its applicability to Wikipedia:
I doubt that many people would devote much time to the task, because they have to earn a living, and paying the people selected would cause many other issues.
Many people would try out their new permissions, but most would drop out.
There need to be clear success/failure criteria. Too many things are tried here, then clearly fail, but continue to be used because of the sunken cost fallacy (I know this is controversial, but I would class draft space as being one of these).
Clear criteria are highly desirable. Unfortunately, I'm not sure that a single metric works (e.g., we don't want to lose these randomly selected editors and we don't want WP:UGLY articles in the mainspace), and it's entirely possible that doing the jobs correctly would result in the selected editors quitting. For example:
Existing AFC promotions have a very low rate of deletion at AFD. (I believe that the normal rate is about 75%.) Given that they're supposed to promote articles that are likely (i.e., 51%, not 90%) to survive AFD, this means that they are underpromoting and overrestricting.
If the new AFC people collectively promote articles that get deleted only 40% of the time, that's a sign that they're doing it correctly (still underpromoting, actually), even though theirs are getting deleted more often than older AFC folks. Thie AFD metric would show success.
But: if each AFD, or the run up to those AFDs, comes with recriminations and complaints about how they're being too "lenient", then the yelled-at editors might quit. The editor-retention metric would show failure.
If the new AFC people collectively promote articles that get deleted only 40% of the time, that's a sign that they're doing it correctly (still underpromoting, actually)Not necessarily. If they promote articles with a chance to survive AfD above 50%, and we assume they are uniformly distributed in probability, the average promoted article would have 75% of chance to survive AfD, or in other words get deleted 25% of the time. If they get deleted 40% of the time, there might be a level of overpromotion going on. Chaotic Enby (talk · contribs) 16:38, 16 October 2024 (UTC)[reply]
(I love people who can math.)
I think it depends on your underlying assumptions about the distribution. If you have 10 articles, each with a 51% chance of surviving AFD, and you promote them all, and all 10 get sent to AFD, then you'd expect five to get deleted – and they were all still correct promotions. WhatamIdoing (talk) 16:55, 16 October 2024 (UTC)[reply]
That definitely depends on our hypotheses about the distribution, indeed. If the 10 articles range from 51%, 56%, ... up to 96%, then you'd have a lower expectation of deleted articles (2.65 if I mathed correctly). But there's also a hidden assumption in here, in that an article with 96% chances of surviving an AfD will probably not be sent there to begin with, meaning the deletion rate of articles being sent at AfD will naturally be higher than the total deletion rate.All in all, it would be interesting to have more statistics about both the deletion chance of AfC articles at AfD, and how much AfC articles are underrepresented at AfD to begin with. Chaotic Enby (talk · contribs) 18:18, 16 October 2024 (UTC)[reply]
Deletion stats are difficult to measure retrospectively. It might be something that we need to study prospectively. There's also the complication of experience: people submitting articles through AFC are not going to have the same deletion rate as people like you and me. WhatamIdoing (talk) 18:51, 16 October 2024 (UTC)[reply]
Complicating this, I don't think most AfC reviewers go for "50% likelihood of AfD survival" so much as "I'm more than 50% sure this would survive AfD" - not quite the same thing. I think I'm one of the more lenient AfC reviewers (well, of those among us who aren't socks), and if 25% of my accepts went to AfD I'd be shocked. Also I think people would be telling me to resign. -- asilvering (talk) 21:42, 25 October 2024 (UTC)[reply]
I suspect that you're correct. Just having more than a small number of articles sent to AFD, even if they were all kept in the end, would raise some eyebrows. WhatamIdoing (talk) 22:26, 25 October 2024 (UTC)[reply]
Also while it's tempting to consider, if this experiment is successful, a radical future proposed sortition of admins, akin to the admin-for-a-day proposed in 2012, but per WMF this is not legally doable, the prohibitive priveliges being rollback and deleted material. That doesn't necessarily have to prevent it; the WMF doesn't set an actual bar for the community review. Therefore, we could have a much lower-pressure, lower-stakes community review of every editor who meets a certain threshold of edits and age to determine eligibility for one day obtaining those rights via sortation, with the sole focus being "is this person likely to abuse rollback or access to deleted material?" (which would almost always lean towards acceptance, since it is automatic, done for everyone, and doesn't directly grant adminship.) Only arguments and rationales specifically related to that question would be allowed and considered by closers when closing such discussions, not general discussions of whether they'd make a good admin in other ways; and they wouldn't require bcrat closures or anything. This would then allow admin status to be granted to those editors via sortition because they'd previously passed a community review on the aspects the WMF cares about. --Aquillion (talk) 19:12, 16 October 2024 (UTC)[reply]
the prohibitive priveliges being rollback and. Rollback doesn't seem very dangerous. I doubt wmf would put their foot down about handing out that one too easily. Agree that wmf would object to handing out view deleted though for legal reasons. This has been well discussed before. –Novem Linguae (talk) 19:19, 16 October 2024 (UTC)[reply]
I don't think that the WMF cares about Wikipedia:Rollback (which doesn't even get used much, because Twinkle and other scripts can mimic the same effect). The legal problem is viewdeleted. They have consistently said that they want proof that the community trusts the people who have that particular right (e.g., we trust them not to restore copyvios or re-post uploaded revenge porn to another site). The process of community vetting can change, but there must be a community vetting process. WhatamIdoing (talk) 19:43, 16 October 2024 (UTC)[reply]
(e.g., we trust them not to restore copyvios or re-post uploaded revenge porn to another site). I've never heard that. WMF's stated reason for viewdeleted being sensitive is that they want to be able to say in court that when something is deleted, it is well and truly deleted, and that only vetted individuals will have access to it, rather than it being easily accessible. The vibe I'm getting is to make sure BLP, libel and defamation, etc. stays deleted and that they can argue it is truly deleted in court. –Novem Linguae (talk) 20:40, 16 October 2024 (UTC)[reply]
If someone is restoring the inappropriate here or posting it on other websites, then that's not "staying deleted", and nobody could argue that it is, even around the dinner table. We need to be able to trust that admins won't do that. WhatamIdoing (talk) 21:59, 16 October 2024 (UTC)[reply]
Either way, though, my point is that we can have a more lightweight vetting process focused specifically and exclusively on whether someone is likely to abuse the specific tools the WMF is worried about. Whenever alternative approaches to adminship come up, people bring up that WMF concern, and it's easily addressed. The WMF isn't worried about people abusing blocks, or unblocks, or weighing in at WP:AE, or AE enforcement actions; and the (perceived, at least) high risk associated with those things under the current system is what actually makes people reluctant to promote admins and which therefore makes RFAs hard. This is also self-perpetuating in that the fewer admins there are the more impact each one has, raising the stakes of RFA in a way that risks breaking it. The community and the WMF are worried about different things. --Aquillion (talk) 22:34, 16 October 2024 (UTC)[reply]
I agree. This is a solvable problem. Also, it doesn't have to be solved in the first iteration. We could test the system on a couple of other userrights, and circle back to test some others later. WhatamIdoing (talk) 23:09, 16 October 2024 (UTC)[reply]
WMF doesn't care about rollback. We could even auto-promote users to some "been around a while" group that includes all of Autopatrolled, New page reviewer, Page mover, Pending changes reviewer, Rollback and they wouldn't care. — xaosfluxTalk13:53, 17 October 2024 (UTC)[reply]
I'd be tempted to do it slightly the other way around - go ask the editors whose sortition perms are about to expire if they want it taken away, and leave it otherwise, so long as they used it non-disruptively. -- asilvering (talk) 22:32, 25 October 2024 (UTC)[reply]
I think the idea about temporary permissions is that you can't build a fiefdom. Do the work for a designated period of time, and then your turn's up, and someone else takes over to do their best. WhatamIdoing (talk) 02:13, 26 October 2024 (UTC)[reply]
I wonder if we could do this in reverse. Specifically, I worry that the regulars at ANI and COIN (in particular) see so much bad behavior that they develop a distorted view of the community and its goals. For example, if you see an endless parade of accusations about undeclared paid editing because the complainant believes the content to be 'promotional', then you'll start seeing UPE scammers behind everything, even when it's just an ordinary person, not fully aware of our house style[*], trying to write about a subject that interests them. Could we pick a random set of 'regulars' and invite them to take a break for three months? And invite, say, 10x as many uninvolved folks to step up to take their places?
[*] For example, our house style declares that "offices in 26 countries and as of October 2024 in the process of opening offices in two more countries" is okay, but "offices in more than 25 countries" is culpable promotionalism, and the maintenance cost of the first style is unimportant.
I don't like proposal 1. NPP and AfC are the most important roles to encourage new editor–retention. Overzealous deletion/declines can drive new editors, content, and ideas out. (Speaking personally, it also doesn't seem very nice to have your fun revoked after making just 1 goof. The strike thing would be agonizing to enforce. Admins may get angried against for "why did you strike this patroller just because they were too officious, jargony, and laconic and scared a newbie away?". Meanwhile, I see no better alternative to the 1-strike system, therefore I do not like proposal 1.) I don't really see the purpose of proposal 2 as pretty much only editing contentious topics directly without edit request relies on this (who would be autoconfirmed and run for administrator?), and such experience is quite essential towards editing such flamewar-inducing pages directly, but I could be fine with it, I suppose. Aaron Liu (talk) 22:34, 1 November 2024 (UTC)[reply]
Are you assuming that someone new to NPP and AFC would be more likely to delete/decline new articles than the existing folks? I'm not sure that would be true, honestly. WhatamIdoing (talk) 00:38, 2 November 2024 (UTC)[reply]
I don't think this will work. Firstly, we need to at least attempt to establish that someone understands the rules and instructions before we give them these rights. Secondly we don't expect perfection from admins, so one strike and you're out is excessively harsh - particularly as that strike will count against them if they ever want to apply for advanced permissions in the future (whether it should nor it, it will). It will be a big disincentive to actually use the tools, particularly if they have shown no interest in the job (and not using the tools when they had them will be something they have to defend at RFA if they stand). Thryduulf (talk) 03:07, 2 November 2024 (UTC)[reply]
Redesigning shackles and other icons
Re-instating this proposal, I want to make the icons look more clear and sleek; I will eventually add on more to the icons (such as good articles, audio articles, etc.) I also want to add region-based letter shackles, so for example 拡 (拡張, Kakuchō) would be the Japanese extended-protection icon, same with 満 (満杯, Manpai) for full-protection.
Agree with others that these new icons look dated. However, if we are discussing changes to lock icons, then I must say the the purple for upload protected is incongruously gaudy. Cremastra — talk — c20:23, 17 October 2024 (UTC)[reply]
Oppose. I think the gradients or bevels make these icons less clear and sleek, at least in their current iteration. The icons also become less readable at smaller resolutions since the shackle part of the padlocks takes up more space, making the actual symbol inside smaller.
Pretty strong oppose trying to run a geolocation script on every load to try to make dynamic labels here. If anything (which I also don't like) labels should follow user interface language. — xaosfluxTalk17:39, 16 October 2024 (UTC)[reply]
I understand the differences, I was just suggesting (because I don't really speak any other language you could propose a specific version) Also, I will later add the letters on the shackles.
Oppose making the primary (only) differentiation be color, as that gives out less information then the current scheme and is useless for those without color viewing abilities. — xaosfluxTalk17:41, 16 October 2024 (UTC)[reply]
Agree with Xaosflux on this one. Furthermore, the two issues of the old icon scheme (color and "realistic" shading that doesn't look great on small icons), which were the reasons for the change to begin with, are present on this one too.Regarding the region-based symbols, it would make more sense to display them based on the language edition, and, since each language edition already sets its own standards for this stuff, there isn't much more we can do. Chaotic Enby (talk · contribs) 18:13, 16 October 2024 (UTC)[reply]
Agree, but only slightly. If you added the letters, it would be better. Also, a solution to your region-basing could be to do a Language-based (like "O" for "Office" would become "S" for "Schoolhouse" in a theoretical "Reversed English") The Master of Hedgehogs(converse)(hedgehogs)14:33, 17 October 2024 (UTC)[reply]
I thought we were using "shackle" as the word to describe a thing by a single aspect for the purposes of avoiding conflation with protecting/locking editing. Aaron Liu (talk) 18:13, 2 November 2024 (UTC)[reply]
Well, we shouldn't, because as @WhatamIdoing noted, the shackle is one part of a padlock. And simply using the word "padlock" avoids conflation, without calling things the wrong thing. (It's even the exact same number of letters.) FeRDNYC (talk) 03:55, 3 November 2024 (UTC)[reply]
Per WP:WIKICLICHE we've been asked to not say this quite as much, due to supply chain issues – if we use them too much we could see a huge shortage down the road. But I hope I'm not generating more heat than light with this comment, or throwing the baby out with the bathwater. Cremastra — talk — c20:22, 17 October 2024 (UTC)[reply]
Never throw the baby out with the bathwater. This will contaminate your greywater collection system. Like other meats, babies are not compostable, so they should be sorted into the landfill waste stream unless otherwise advised by your municipal waste management authority. Folly Mox (talk) Folly Mox (talk) 20:46, 17 October 2024 (UTC)[reply]
The pseudo-3D shading looks dated compared to the current flat icons. Most modern design systems (including codex, which is the new design system for Wikimedia wikis) are built around flat icons. --Ahecht (TALK PAGE)18:36, 17 October 2024 (UTC)[reply]
Just for funStill feel like a step backwards. The current "Good article" icon, on top of having less of a distracting shading and being more readable, is in a consistent style with a lot of our other icons. The current "Featured article" icon, although not consistent with the others, is pretty unique and recognizable in design, while this one looks like a generic star.Just for fun, I did once make a "Good article" star in the style of the FA one – not meant for any official implementation beyond my personal script of course, but it's neat to see how it would look like. Chaotic Enby (talk · contribs) 22:14, 17 October 2024 (UTC)[reply]
Have you ever looked at the Featured Article icon, full-size? (If not, check it out at File:Cscr-featured.png. I'll wait.) ...Like or lump @Chaotic Enby's GA star, it's actually of a fairly harmonious style with the current FA star, which is (as noted) currently not consistent with anything else anywhere. Arguably it's well-known/recognizable — Chaotic makes that argument, anyway — but TBH I have a feeling the great majority of readers never see it larger than head-of-a-pin-scaled, and wouldn't even recognize the actual, full-sized image AS our FA icon. FeRDNYC (talk) 04:10, 3 November 2024 (UTC)[reply]
I have seen the full FA icon; the GA star is just straight out of Cthulhu (...positively). It is fun, but I think GA should be more inline with the rest of the article-rating icons because of the kinda lesser rigor. Aaron Liu (talk) 13:26, 3 November 2024 (UTC)[reply]
To be fair, it's definitely a concept design rather than an actual proposal. If anything, I far prefer having the current GA icon as our official one, as it is more harmonious with basically anything that isn't the FA star. Chaotic Enby (talk · contribs) 22:18, 4 November 2024 (UTC)[reply]
These are not visual improvements whatsoever, unfortunately. They are clear regressions in design, and the current icons are fine. Our system is particular to the English Wikipedia, so it's perfectly appropriate for their design to be relative to the English language.Remsense ‥ 论19:29, 17 October 2024 (UTC)[reply]
Color me baffled. By starting with Re-instating this proposal, you make me think you want to reinvigorate some failed proposal. But then I follow your link and see that the proposal led to the implementation of new padlock icons, which; I guess, you mean to reverse. I also fail to understand what you mean by region-based letter shackles; do you mean for articles about, e.g., Japan? Or articles viewed by somebody we're supposed to have guessed might be in Japan? Or somebody with the Japanese language listed in a userbox on their User page? It's English Wikipedia, so I can't see the last two being useful options, and the first one will only lead to arguments and confusion and we've got that already. The current icons seem clear enough to me, although I don't know how to measure "sleek", I guess. In summary: baffled. — JohnFromPinckney (talk / edits)12:15, 18 October 2024 (UTC)[reply]
I mean region-based letter shackles basically like the letters on shackles but different regional translations. (This'll probably not work because of @Chaotic Enby's post.)
So (just to see if I understand it finally), you're proposing on English Wikipedia that Japanese Wikipedia use icons with Japanese symbology, and Spanish Wikipedia use some Spanish-language indicator on the padlock, etc. Yes? — JohnFromPinckney (talk / edits)22:30, 18 October 2024 (UTC)[reply]
Oppose for now. Status quo is fine. It's really cool that you're contributing your graphics skills to the movement though. I'm sure there's some less high profile areas that could really benefit from your skills. –Novem Linguae (talk) 03:55, 23 October 2024 (UTC)[reply]
Oppose: New proposals are nice but I personally like the style of the old ones better, and flat icons also seem more up-to-date to me. Regional shackles sound like a good idea, but don't appear to be in this proposal, so I'll just say I support those (maybe in the old design-style in my preference). Mrfoogles (talk) 20:22, 23 October 2024 (UTC)[reply]
Oppose per Remsense. The new 3D icons look like something from the early days of the internet. Plus the shadowing makes the icons appear unnecessarily "bulky" (not sure how to say this). Nythar (💬-🍀) 22:33, 25 October 2024 (UTC)[reply]
Oppose here as well. It's not about status quo or resistance to change, I vastly prefer the current icons to the proposed replacements. (Admittedly subjective) points in favor of the current icons over the new ones:
The flatter look will render better at small sizes (since these icons are actually shown at a fraction of the size they're displayed in this thread)
Ditto the blockier font
Ditto the thicker shackle arcs
The skinny shackles and rectangular body give the proposed replacements the appearance of handbags, not padlocks
The letter placement is more uniform and precise in the current icons; the proposed replacements appear to have been "eyeballed". IMHO SVG art of this sort is best hand-coded (if not from scratch, then at least as a finalization pass to clean up the code), with all of the dimensions precise and uniform.
I appreciate the effort, and I'm sorry to be critical, but I'm just not into them at all. The current set, OTOH, are actually fairly well-designed and optimized for their purpose, which is an important consideration in designing functional artwork of this sort. It's puzzling to me that anyone would be looking to replace them, as there's surprisingly little room for improvement IMHO. FeRDNYC (talk) 13:19, 26 October 2024 (UTC)[reply]
I think the proposed sets may been cool at the time of the previous proposal. Those locks would be more appropriate for something like in 2008. It's for the same reason why traffic lights are always (from top to bottom) red yellow green. And why train doors on British trains need doors to have sufficient contrast to the rest (see PRM TSI). In other words, using colour alone for distinguishing isn't enough.
Oppose - not a fan of the proposed icons (see also Nythar's comment), and the current locks work quite well. however, I would be supportive of a redesign of the GA/FA icons (/the various icons of the same style) in a style similar to the current locks. Rexo (talk | contributions) 20:30, 29 October 2024 (UTC)[reply]
What if we kept the shackles and good icon, get a new featured icon, and make a built-in feature that allows shackles to be compatible with dark mode? 2I3I3 (talk) 03:07, 2 November 2024 (UTC)[reply]
(to clarify: the style used by a lot of icons across the wiki (including FA/GA) feels dated, and the locks have a cleaner look that I think could be used as a basis for further redesigns. I don't think that would inherently lead to the quality symbols implying protection.) Rexo (talk | contributions) 13:54, 4 November 2024 (UTC)[reply]
I don't think the Norro or FA icons are dated, and using padlocks to indicate quality just makes no semantic sense. We adopted padlocks because it showed that the article was locked from editing. Aaron Liu (talk) 14:07, 4 November 2024 (UTC)[reply]
Our article Shackle says "A shackle is also the similarly shaped piece of metal used with a locking mechanism in padlocks.[1]". Some here seem confused, but anyone using "shackle" to refer to the handle part of the handbag-looking icon is correct. Anomie⚔21:18, 2 November 2024 (UTC)[reply]
Enabling SecurePoll elections with the electionadmin right
The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion.A summary of the conclusions reached follows.
WP:SNOW: unanimous support to have the ability to hold local SecurePoll elections, including enabling the electionadmin right on enwiki. An RFC to determine how the new right should be distributed can be launched at any time; it may be advisable to advertise that RFC on WP:CENT. Levivich (talk) 14:48, 27 October 2024 (UTC) Levivich (talk) 14:48, 27 October 2024 (UTC)[reply]
Hello! My name is Joe Sutherland and I'm on the Trust and Safety team at the Wikimedia Foundation. In the past, your community has shown interest in holding elections with SecurePoll — perhaps you already have through votewiki. We are now looking into making this available to local communities to run elections themselves. This will require the "electionadmin" right to be enabled on your project, which is a right that allows access to sensitive information.
As such, it is likely that you will need to run a Request for Comment (or similar process) to ascertain consensus for the implementation of this feature. To help guide such a discussion, we've put together a Meta-Wiki page with more information about what enabling the right will mean for your community.
If your community does discuss and decides to move forward with this, T&S would like to support you — please let us know via email ( ca@wikimedia.org ) if and when consensus is reached. Thank you!
Sorry, I wasn't totally clear - this would be for future (admin/ArbCom) elections that the community would like to run. The elections scheduled to start soon will use the existing votewiki system. Joe Sutherland (WMF) (talk) 19:43, 18 October 2024 (UTC)[reply]
Support. This isn't a requirement holding for admin elections, arbcom elections (or any other type of elections) but (if I've understood correctly) it will reduce the amount of support we need from the WMF when we do hold them. I agree completely with Sdkb's last sentence. Thryduulf (talk) 20:35, 17 October 2024 (UTC)[reply]
Support. This would help us host local administrator elections and arbitration committee elecitons that aren't so dependent on the limited bandwidth of the stewards (scrutineers) and WMF T&S (for vote.wikimedia.org setup). By the way, are electionadmins basically checkusers within the SecurePoll tool (being able to see IP information for voters)? So we'd need to make sure that folks that receive that permission are a functionary and/or sign an NDA? –Novem Linguae (talk) 20:35, 17 October 2024 (UTC)[reply]
P.S. Is there a ticket on Phab to separate election checkuser capabilities from election creation/editing capabilities? This might be worth looking into. The person that sets up polls doesn't necessarily need to be the same person that checks all the voters. And it may make sense to have a division here. For example, someone technical can set up SecurePoll, and existing checkusers could do the scrutineering. –Novem Linguae (talk) 20:39, 17 October 2024 (UTC)[reply]
I did some research and it looks like any admin can create a poll, but only electionadmins (scrutineers) can edit a poll or view checkuser-like data on voters. This split is a bit odd, as I think it'd be better if admins could also edit polls that they were added to when the polls were created, so I've filed phab:T377531 to explore that idea a bit further. –Novem Linguae (talk) 23:56, 17 October 2024 (UTC)[reply]
Support to help us implement administrator elections in a more practical way for both us and the WMF. However, will electionadmins be a new user group? They seem to combine characteristics of checkusers and bureaucrats, and I'm not sure whether it would work to bundle the right into either by default. On the other hand, Novem Linguae's proposal of splitting the user right could work better, with a technical-minded crat setting up the poll, while checkusers get the scrutineering right. Chaotic Enby (talk · contribs) 22:20, 17 October 2024 (UTC)[reply]
If I'm reading the code right... yes, electionadmin would either need to be a new user group, or the permissions for it (securepoll-create-poll, securepoll-view-voter-pii) added to an existing user group such as the checkusers. The latter might be simpler than creating a whole new appointment process for electionadmins.
At first glance, I don't see a relationship between bureaucrats and electionadmins. Electionadmins can't grant any user groups, unlike bureaucrats. Again, if I'm reading the code right, any admin can create a poll. –Novem Linguae (talk) 00:01, 18 October 2024 (UTC)[reply]
For the relationship between bureaucrats and electionadmins, it's more to have the same group in charge of regular RfAs and admin elections, and to decouple checkusers from this additional responsibility. But that might be too redundant, and having any technical-minded admin able to do it could be enough, although it would be a major responsibility to give to any admin and might make it more difficult for potential candidates to gain the voters' trust. Chaotic Enby (talk · contribs) 13:14, 18 October 2024 (UTC)[reply]
The technical village pump is for questions about how to do X, whereas how to grant the electionadmin right requires a proposal for a policy, so this page is the appropriate place. Since the right provides access to voter information (as per meta:SecurePoll/Local elections § What does the electionadmin right do?), a process is needed to establish who is trusted with this access. The options I can think of are by consensus discussion, by election, or by appointment (which would push the question up one level on how to decide what group does the appointing). Being part of an existing trusted group, such as those with the oversight right or the checkuser right, could be a requirement to become an election admin. isaacl (talk) 23:35, 17 October 2024 (UTC)[reply]
It might be simplest to grant the permissions securepoll-create-poll and securepoll-view-voter-pii to the checkusers. That way we don't need the overhead of a separate user group or separate appointment process. I think you have to specifically be added to a poll by the poll creator to see its PII, so there shouldn't be any security risk from giving all the checkusers the ability to be added to polls by the poll creator. –Novem Linguae (talk) 00:03, 18 October 2024 (UTC)[reply]
This feels like a major oversight. The admin elections are modeled after WP:ACE but apparently nobody thought about the scrutineers that need to be approved and tooled up each year for ACE. I'm presuming this means the elections are on hold until we clear this up? Just Step Sidewaysfrom this world ..... today00:15, 18 October 2024 (UTC)[reply]
Locally, we have a few options that we could consider if we decide to do polls. First, we don't HAVE to encrypt the database, it doesn't make the votes readily available - but a developer could access them, so that is something to consider (also means not having to deal with key escrow to finalize the election). Additionaly, we don't have to let SP collect private info. We would still have the usernames - it would just prevent using the checkuser info on the securepoll votes. These are all just things to consider if we set up polls - point is that there are options. — xaosfluxTalk13:41, 18 October 2024 (UTC)[reply]
Support Local communities should have the autonomy to conduct elections when they see fit, and not be so dependent on a certain WMF team that has a tight calendar. Also, the inability to conduct separate elections on multiple sites at the same time is a big limitation of the current system that would be addressed by this. – SD0001 (talk) 08:55, 19 October 2024 (UTC)[reply]
Support -- Per SD and Xaos above, I think deploying SecurePoll locally so that individual communities can conduct elections in a autonomous and decentralized manner at the tradeoff of some confidentiality is a good idea in general. Sohom (talk) 14:26, 19 October 2024 (UTC)[reply]
Support An RFC will definitely be necessary to determine who can scrutineer. I imagine we have a few options, the first two I can think of being either assigning the CheckUser group (or perhaps a different set of users?) the electionadmin right, or just creating a new usergroup and having Stewards go ahead and assign it to the relevant scrutineers a week or so before an SP is scheduled to occur, then remove it afterwards. EggRoll97(talk) 03:33, 23 October 2024 (UTC)[reply]
Support I have organized Wikimedia elections for affiliate organizations and after trying open processes, have found that commercial software is the only practical option. The Wikimedia community loves democratic process and elections, but has never had tools to support that. Making an option for SecurePoll has been a longstanding community request since at least 2016 when meta:SecurePoll was set up. Bluerasberry (talk)15:05, 26 October 2024 (UTC)[reply]
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.
Task: When an edit adds an file link without "|(\s*)?frameless" or "|(\s*)?thumb" within it, warn the user and tell them they probably wanted to put a |thumb in. Still allow them to save the edit. Can also scan for every format supported if wanted.
Needs wider discussion but until then, {{EFR}}. The basis for this request is on one accidential removal of a colon. This seems more like something that might be raised at Phab if nothing else, but I don't think we need a filter to warn people to use thumb. EggRoll97(talk) 23:52, 23 October 2024 (UTC)[reply]
Coming from VPR. I'm not sure what our standards are for edit filters enough to be able to comment on the appropriateness of one for this. But I can say that I've certainly been guilty of forgetting to add thumb and not previewing, resulting in situations exactly like the linked diff.
Actually, no, I'm not sure if edit check applies. Its project page defines it as a set of improvements for the visual editor, where I highly doubt editors make this mistake. Aaron Liu (talk) 02:19, 24 October 2024 (UTC)[reply]
Ah, true, I forgot that. In that case, we might want a different sort of warning, perhaps akin to the disambiguation link added one. Sdkbtalk02:24, 24 October 2024 (UTC)[reply]
Might be a good idea for community wishlist more than anything else. I don't think an edit filter is really the best way to go here. Even on a warn-only, it will be catching good-faith edits, and (temporarily) slowing down these contributions. This isn't to say this isn't a problem, just that edit filters may not be the best way to solve it. EggRoll97(talk) 04:39, 25 October 2024 (UTC)[reply]
Technically a lot of the formulas in maths articles are inline images (see e.g. series (mathematics)). These are generated rather than transcluded, but it wouldn't surprise me if there is some edge case where an image is transcluded inline for a similar purpose. Thryduulf (talk) 11:39, 25 October 2024 (UTC)[reply]
There are certainly articles containing inline images for discussing symbols (which may not have straightforward Unicode character representations), e.g. rare historical letter glyphs or musical notation elements (see Archaic Greek alphabets or Mensural notation, to name just two that I happen to have worked on). Yes, I guess articles like these are few, but if an article requires them, it will require them numerous times. Fut.Perf.☼11:59, 25 October 2024 (UTC)[reply]
I don't think that will be scalable, given the number of potential articles and the number of potential images. What might work would be something in the syntax to say "I am intentionally using this image inline" Thryduulf (talk) 12:05, 25 October 2024 (UTC)[reply]
From testing in my sandbox it seems to me that this would work in all cases where there isn't a caption being used as alt text (#10) as that removes the alt text. Glagolitic script#Characteristic uses captions in this manner.
However, when I tabulated the results (Special:Permalink/1253409176) any double pipes were interpreted as table syntax, even inside the file link, so broke things. Which makes things complicated. I'd also like to know if this breaks anything for users of screen readers.
We could also do [[File:Slinky shrewsbury.jpg|inline|]][[File:Slinky shrewsbury.jpg|inline|caption]] for case 1 (no caption) and case 2 (w/ caption). Regex would scan for |inline|. Aaron Liu (talk) 21:04, 25 October 2024 (UTC)[reply]
Another thought is that we'd need to get VE to insert this parameter too, otherwise it would trigger the warning for the next person to edit the source, with the potential for confusion and lost edits. Thryduulf (talk) 01:19, 26 October 2024 (UTC)[reply]
(edit conflict) I agree with both those suppositions, but I don't know if there are other uses than maths articles. However my main point was that good faith reasons for using an inline image, however rare, almost certainly do exist and so there needs to be some provision for allowing them. Thryduulf (talk) 12:00, 25 October 2024 (UTC)[reply]
There are lots of templates that use inline images, so be careful. I general I would say, please don't make too many assumptions about how people should NOT use wikicode. People are for more inventive with the syntax than you expect :) —TheDJ (talk • contribs) 12:05, 25 October 2024 (UTC)[reply]
Thanks for the examples. However, I think we all should refocus the conversation onto the |inline| override idea proposed above. With the override idea, editors adding new inline images can see how to stop the message from popping up again and go on on their merry way. Aaron Liu (talk) 00:52, 26 October 2024 (UTC)[reply]
What you're modeling here – thinking about how a policy/convention could be programmed into editing experiences – is precisely the kind of practice we're intending Edit Check to inspire.
I like and support this idea for that very example you state (geez that was a big image). My one concern related to the warning message encouraging the usage of these parameters, however, is that it needs to be very clear upfront that |frame, |frameless, and |thumb may NOT be used in any combination together since these three are contradictory parameters. When these conflicting parameters do appear together on a single image, it triggers a Bogus/Invalid Image Option syntax error, a Wikipedia tracked error that sprouts a dozen or so new cases daily. I and another editor teamed up this summer and finally eliminated the existing backlog of the 7000+ cases of active Invalid Image Options, and is one of a few error types our little community has caught up with and are keeping mowed down so that it doesn't resprout and grow wild again. My main concern is that if Wikipedia is not clear up front that these cannot be used together, people might think to there is no issue in just adding all the options and being done with it, (a "Heck with it all" reaction) leading to a higher rate of repopulation of this error type. Would stating use only one (to discourage combinations) be effective, or might a second/subcheck message be reasonable on (re)submission in these cases? Zinnober9 (talk) 05:53, 28 October 2024 (UTC)[reply]
A proposed override for the edit filter above is introducing multiple captions, which is also a linter error. Do you know if there's a way to configure the linter extension so that the override is an exception? Aaron Liu (talk) 12:52, 28 October 2024 (UTC)[reply]
That is well beyond my knowledge. Jonesey95 knows more than I do, they might know, but I'd suspect that's more of a question for WMF. If multiple captions were introduced, I'm concerned with how that would work and how are the controls for determining which caption displays. I think the current WP:EIS syntax is fairly straight forward, and people make all sorts of unintended messes with it now. Zinnober9 (talk) 15:50, 28 October 2024 (UTC)[reply]
If multiple captions were introduced, I'm concerned with how that would work and how are the controls for determining which caption displays.
The software currently handles this well: by always only displaying the last caption, as you've probably seen at Thryduulf's sandbox. Aaron Liu (talk) 16:58, 28 October 2024 (UTC)[reply]
I have, as that's how I learned about this discussion. (see discussion User talk:Thryduulf#Image syntax). Multiple captions, while "handled" in the way you expect, are not error-free syntax in current WP:EIS code, and Thryduulf's current sandbox example has four cases demonstrating multiple captions, which are each causing invalid image errors (Lint report page) (cases 10 and 16, 11 and 17). These reported errors from the EIS syntax usage are the objection I have have in regards to this proposal. 22:11, 1 November 2024 (UTC) Zinnober9 (talk) 22:11, 1 November 2024 (UTC)[reply]
Yeah, I understand. Would you have any objections if only adding "|inline|" before another caption would not trigger a linter error? Aaron Liu (talk) 22:23, 1 November 2024 (UTC)[reply]
I'm coming to this discussion late, so forgive me if I misunderstand. I read through it twice, and I don't get it. The proposal is to stop people from inserting File:/Image: calls unless they have thumb or frameless? If that is the proposal, I don't see how it is reasonable. People insert such images all the time and have done so for decades, and things are generally fine. I did a semi-random search for insource:/\[\[File:/ -insource:/thumb/, and I got List of world sports championships, Nephrozoa, Filozoa, Countries of the United Kingdom, Papua New Guinea at the 2015 Pacific Games, PubChem, and more than 100,000 other pages that do not appear to be causing any trouble. I think there may be an XY problem here. – Jonesey95 (talk) 15:31, 28 October 2024 (UTC)[reply]
Not stop completely, give a warning for new additions through an edit filter that won't stop them if they save a second time or include some kind of override. Aaron Liu (talk) 16:54, 28 October 2024 (UTC)[reply]
But why stop or warn at all for a completely valid usage that appears in more than 100,000 pages without a problem? What is wrong, for example, with the image used in the infobox at PubChem, which is not an inline image and does not use thumb or frameless? What is wrong with the image used at Short story, which uses neither thumb nor frameless and is not inline? What is wrong with the map images at Political divisions of Bosnia and Herzegovina, which use neither thumb nor frameless and are not inline? These are just three easily accessible examples from well over 100,000 pages. – Jonesey95 (talk) 03:45, 2 November 2024 (UTC)[reply]
In the PubChem case, I'm not sure if the image was correctly added, as from what I recall the file name should be given directly as a parameter in infoboxes. However, basically every article with a phylogenetic tree, a series template, or a list of countries with flagicons would be affected, which isn't great. Chaotic Enby (talk · contribs) 04:22, 2 November 2024 (UTC)[reply]
Would this stop occur when someone adds a template using {{ambox}} or a similar message box to a page? Those templates use images that are not inline, frameless, or thumbnails. I think this idea may need a significant re-think. – Jonesey95 (talk) 04:39, 2 November 2024 (UTC)[reply]
Looking back the original issue was accidentally transcluding very large (in terms of dimensions) images at full size, which is an issue, but one that is very significantly narrower in scope than the proposed solution would address (and I agree that is not practical). Adding a warning only when the image exceeds say 2000px wide or 1200px high (larger than standard 1080p resolution) is unlikely to inconvenience many pages. My gut feeling though is that this would need to be done in software as whatever generates the warning would to get image dimensions from Commons as part of the parsing of the wikitext. Thryduulf (talk) 04:49, 2 November 2024 (UTC)[reply]
On second thoughts maybe only the width criterion is needed, as something long and thin will just vertically scroll without too much disruption? Most very wide images should probably be using {{wide image}} or thumb. Thryduulf (talk) 04:52, 2 November 2024 (UTC)[reply]
That could work, but, if we wish to tackle the narrow issue of wide images, I am not sure whether an edit filter alone would work. As far as I know, regex can't go in the file page and check its metadata? (Or maybe the edit filters have more capabilities I don't know about) Chaotic Enby (talk · contribs) 15:24, 2 November 2024 (UTC)[reply]
As you've said, that would require quite a bit more work than an edit filter. The issue is also that valid new usages of inline images without a template are quite little. Aaron Liu (talk) 17:05, 2 November 2024 (UTC)[reply]
The issue is also that valid new usages of inline images without a template are quite little. Are you sure about that? There are lots of examples noted in just this thread? How often are problematic (i.e. extremely large) images added inline accidentally? Unless it is significantly more than valid uses of inline images then it's not going to be worth it. Thryduulf (talk) 17:11, 2 November 2024 (UTC)[reply]
How often are valid images added inline? Anecdotally, it happens quite occasionally enough. In fact, its usage at NCAA Division III—one of the results on the first page of search—was a mistake that had been there for 4 years before I fixed it today. I was preparing a paragraph that evaluated the first page of the search results when I realized that I can't find any guidelines on using non-small inline images instead of frameless images within infoboxes and tables, therefore, half of my basis for this proposal may be incorrect. Aaron Liu (talk) 18:09, 2 November 2024 (UTC)[reply]
For the short story case, could you explain which image? If your concern is the sidebar, I'm pretty sure we can exclude the template namespace, which also tends to have arcane wizardry. (Also, the edit filter would not warn just for existing usages. It would only warn on additions and new usages that don't use some e.g. Liechtenstein flag template (it only detects the relevant wikitext)) Aaron Liu (talk) 17:02, 2 November 2024 (UTC)[reply]
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.
I frequently edit articles about small towns in Iowa. When the 2020 US Census results were released, the vast majority of these articles had multi-paragraph summaries of the 2000 and 2010 Census results, usually under the heading "Demographics". The 2010 summaries appear to have been made by a bot, which is no longer active. The 2020 Census results have been available for several years now, and no bot has run through these articles and inserted 2020 Census summaries. For a few of the larger cities in Iowa, editors had added 2020 summaries, but for the vast majority of cities, towns and CDPs, the articles only had 2000 and 2010 summaries. So I updated the 974 articles for the Iowa towns with no 2020 summary, manually (I didn't clobber any exisiting 2020 summaries, unless they had fewer than 3 sentences). I spot checked the situation for other states, and found a similar situation. There may be as many as 40,000 articles that have this issue (for example: Northfield, Minnesota).
I think a case could be made that these articles really don't need extensive summaries of the census results. But I don't think many people would think that these articles should have extensive summaries of past censuses, but not the most recent one. Surely the most recent census is the most relevant. Having the summaries end at 2010 makes the article look abandoned.
Before I edited all those Iowa city articles, I made a Python script that called the US Census Department servers' API, to fetch the data, and the script produced a text block formatted properly for Wikipedia. I think it would be useful to to make a bot to update the articles for other states, but there are tricky issues, and I have never made a Wikipedia bot. Is there anyone who would be willing to work with me to make a bot to do these updates? If this is the wrong place to be asking that, can someone direct me to the correct place? Thanks for any info! PopePompus (talk) 01:51, 27 October 2024 (UTC)[reply]
@PopePompus, you're definitely correct that census data for U.S. cities is a very lacking area.
I'd start by reviewing the discussion here from 2020 — as you'll see toward the end, my view is that we very badly need to be converting this information into template form, rather than copying and pasting it (which is a large part of what has created the mess). I'd then open new discussion at WT:CITIES to get a sense of where current consensus is at. You may also want to look at what information Wikidata has and whether that can be of use. Once you've established consensus there to make changes, bot approvals go at WP:BOTREQ.
Overall, this will certainly be a major project, given the complexity of the information involved and the wide scale at which changes are needed. Good luck! Sdkbtalk04:12, 27 October 2024 (UTC)[reply]
I will just add that a bot created almost all of the articles about places in the US that were enumerated by the US Census in 2000. Many of those articles for years consisted of very little more than the demographic section. I believe that most of the 2010 census data was added manually, generally attempting to follow the 2000 bot-created format. Adding the 2020 census data has been piecemeal, at best. A bot to handle this sounds good, but getting agreement on the format for the data in articles may require some discussion. Donald Albury13:26, 27 October 2024 (UTC)[reply]
I think the mass creation of the articles by a bot was a very good thing. At least in the case of Iowa, most of the articles have accumulated non-bot content. Since the barrier to entry for editing an existing article is far lower than creating a new one, it's safe to say that most of the post-bot content would not ever have appeared absent the bot. I agree with Sdkb that a template is the way to go. I had not seen the 2020 discussion he pointed to, and I found that discussion somewhat disappointing, because a lot of the discussion was about details, rather than focusing on what I think are the major issues: Template or not, should old results be retained in the main body of the text, and perhaps most importantly who's gonna do it. PopePompus (talk) 13:53, 27 October 2024 (UTC)[reply]
Consistency of the Demographics sections across articles about (Census enumerated) populated places in the US is desirable. Unfortunately, I have no experience with bots, and have fallen into the hole of trying to expand articles about almost 80 species in a genus. Donald Albury14:32, 27 October 2024 (UTC)[reply]
I would like to see a bot add this information. Adding the same thing as last time is okay with me, though a complete re-write might eventually be desirable. It looks like Yellowcard has done some work at getting the US census numbers into Wikidata. Perhaps he has the needed skills, or at least is familiar with the format of the database?
(In terms of a complete re-write, imagine that an exact replica would result in these three sentences in the article (in separate sub-sections):
[From 2000] The racial makeup of the city was 95.67% White, 3.29% Native American, 0.17% from other races, and 0.87% from two or more races.
Would it be possible to combine this into a single statement like:
The racial makeup of the city was 88.5% White, 0.5% African American, 1.5% Native American, 1.5% from other races, and 8% from two or more races, representing a decline in <name listed groups with significant change> and an increase in <name other groups> since the 2000 census.
Thanks @WhatamIdoing for the ping. We (a interested user group in the German Wikipedia) have invested a lot of time and effort by extracting the data from the US Census Bureau website/database and uploading it to Wikidata. This is done for data like population, number of households, area, water area, per capita income (which comes from the ACS) etc. The population data is available for the 2010 and 2020 census.
Creating a bot that fetches the information from the Census Bureau's website and creates plain text (!) is a horrible idea to me. The data is available on Wikidata and usable for Wikipedia already (and has been since 2021). The project on German Wikipedia has a bit stopped due to real-life timing issues, but could be restarted. For the German Wikipedia (where article creation by a bot is rejected, for whatever reasons), we use the data in the infoboxes for all US cities that have an article. The data is so reliable that we even have removed the parameters for population and household counts in the infobox - they are fetched from Wikidata no matter what. No manual updating of Census information in the article necessary nor possible any more.
Articles in German face the same issue as in the English Wikipedia - totally outdated, bot-generated and therefore boring Demographics paragraphs. There is a clear consensus that we will not make this mistake again. Data like this should go into the article via templates, not via plaintext. Yellowcard (talk) 16:06, 28 October 2024 (UTC)[reply]
Some editors at the English Wikipedia distrust Wikidata, so relying entirely on Wikidata isn't accepted. They worry that vandalism (or innocent mistakes) will go unnoticed and uncorrected. We also have a substantial group of editors who believe that paragraphs are preferable to infoboxes, or necessary in addition to infoboxes. Between them, I think the most likely outcome is plain old paragraphs. WhatamIdoing (talk) 17:43, 28 October 2024 (UTC)[reply]
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.
When discussion has ended, remove this tag and it will be removed from the list. If this page is on additional lists, they will be noted below.
Should a new pending changes protection level - extended confirmed pending changes (hereby abbreviated as PCECP) - be added to Wikipedia? AwesomeAasim19:58, 5 November 2024 (UTC)[reply]
Background
WP:ARBECR (from my understanding) encourages liberal use of EC protection in topic areas authorized by the community or the arbitration committee. However, some administrators refuse to protect pages unless if there is recent disruption. Extended confirmed pending changes would allow non-XCON users to propose changes for them to be approved by someone extended confirmed, and can be applied preemptively to these topic areas.
It is assumed that it is technically possible to have PCECP. That is, we can have PCECP as "[auto-accept=extended confirmed users] [review=extended confirmed users]" Right now it might not be possible to have extended confirmed users review pending changes with this protection with the current iteration of FlaggedRevs, but maybe in the future.
Survey (PCECP)
Support (PCECP)
Support for multiple reasons: WP:ARBECR only applies to contentious topics. Correcting typos is not a contentious topic. Second, WP:ARBECR encourages the use of pending changes when protection is not used. Third, pending changes effectively serves to allow uncontroversial edit requests without needing to create a new talk page discussion. And lastly, this is within line of our protection policy, which states that protection should not be applied preemptively in most cases. AwesomeAasim19:58, 5 November 2024 (UTC)[reply]
It's better than EC, which already restricts being the free encyclopedia more. As I've said below, the VisualEditor allows much more editing from new people than edit requesting, which forces people to use the source editor. Aaron Liu (talk) 03:52, 6 November 2024 (UTC)[reply]
Support, functionally a more efficient form of edit requests. The volume of pending changes is still low enough for this to be dealt with, and it could encourage the pending changes reviewer right to be given to more people currently reviewing edit requests, especially in contentious topics. Chaotic Enby (talk · contribs) 20:25, 5 November 2024 (UTC)[reply]
Support having this as an option. I particularly value the effect it has on attribution (because the change gets directly attributed to the individual who wanted it, not to the editor who processed the edit request). WhatamIdoing (talk) 20:36, 5 November 2024 (UTC)[reply]
Support: better and more direct system than preemptive extended-confirmed protection followed by edit requests on the talk page. Cremastra (u — c) 20:42, 5 November 2024 (UTC)[reply]
Support, Pending Changes has the capacity to take on this new task. PC is much better than the edit request system for both new editors and reviewers. It also removes the downsides of slapping ECP on everything within contentious topic areas. Toadspike[Talk]20:53, 5 November 2024 (UTC)[reply]
Support Agree with JPxG's principle that it is better to "have drama on a living project than peace on a dead one," but this is far less restrictive than preemptively setting EC protection for all WP:ARBECR pages. From a new editor's perspective, they experience a delay in the positive experience of seeing their edit implemented, but as long as pending changes reviewers are equipped to minimize this delay, then this oversight seems like a net benefit. New users will get feedback from experienced editors on how to operate in Wikipedia's toughest content areas, rather than stumbling through. ViridianPenguin 🐧 ( 💬 ) 08:57, 8 November 2024 (UTC)[reply]
Oppose (PCECP)
Oppose There's a lot of history here, and I've opposed WP:FPPR/FlaggedRevs consistently since ~2011. Without reopening the old wounds over how the initial trial was implemented/ended, nothing that's happened since has changed my position. I believe that proceeding with an expansion of FlaggedRevs would be a further step away from our commitment to being the free encyclopedia that anyone can edit without actually solving any critical problems that our existing tools aren't already handling. While the proposal includes However, some administrators refuse to protect pages unless if there is recent disruption as a problem, I see that as a positive. In fact that's the entire point; protection should be preventative and there should be evidence of recent disruption. If a page is experiencing disruption, protection can handle it. If not, there's no need to limit anyone's ability to edit. The WordsmithTalk to me03:45, 6 November 2024 (UTC)[reply]
The Wordsmith, regarding "However, some administrators refuse to protect pages unless if there is recent disruption as a problem, I see that as a positive.", for interest, I see it as a negative for a number of reasons, at least in the WP:PIA topic area, mostly because it is subjective/non-deterministic.
The WP:ARBECR rules have no dependency on subjective assessments of the quality of edits. Non-EC editors are only allowed to make edit requests. That is what we tell them.
If it is the case that non-EC editors are only allowed to make edit requests, there is no reason to leave pages unprotected.
If it is not the case that non-EC editors can only allowed to make edit requests, then we should not be telling them that via talk page headers and standard notification messages.
There appears to be culture based on an optimistic faith-based belief that the community can see ARBECR violations, make reliable subjective judgements based on some value system and deal with them appropriately through action or inaction. This is inconsistent with my observations.
Many disruptive violations are missed when there are hundreds of thousands of revisions by tens of thousands of actors.
The population size of editors/admins who try to address ARBECR violations is very small, and their sampling of the space is inevitably an example of the streetlight effect.
The PIA topic area is largely unprotected and there are thousands of articles, templates, categories, talk pages etc. Randomness plays a large part in ARBECR enforcement for all sorts of reasons (and maybe that is good to some extent, hard to tell).
Wikipedia's lack of tools to effectively address ban evasion in contentious topic areas means that it is not currently possible to tell whether a revision by a non-EC registered account or IP violating WP:ARBECR that resembles an okay edit (to me personally with all of my biases and unreliable subjectivity) is the product of a helpful person or a ban evading recidivist/member of an off-site activist group exploiting a backdoor.
Oppose, I hate pending changes. Using them widely will break the wiki. We need to be as welcoming as possible to new editors, and the instant gratification of wiki editing should be there on as many pages as possible. —Kusma (talk) 21:47, 6 November 2024 (UTC)[reply]
We already have a similar and larger backlog at CAT:EEP. All this does is move the backlog into an interface handled by server software that allows newcomers to use VE for their "edit requests", where currently they must use the source editor due to being confined to talk pages. Aaron Liu (talk) 23:06, 6 November 2024 (UTC)[reply]
... if the number of protected pages does not increase. I expect an increase in protected pages from the proposal, even if the terrifying proposal to protect large classes of articles preemptively does not pass. —Kusma (talk) 13:08, 7 November 2024 (UTC)[reply]
Most PCECP pages should be ECP pages (downgraded?) as they have lesser traffic/disruption. So, the number of pages that will be increase should not be that much. ~/Bunnypranav:<ping>13:35, 7 November 2024 (UTC)[reply]
@Kusma Isn't the loss of instant gratification of editing better than creating a request on the talk page of an ECP page, and having no idea by when will it be reviewed and implemented. ~/Bunnypranav:<ping>11:25, 7 November 2024 (UTC)[reply]
Oppose — Feels unnecessary and will only prevent other good faith editors from editing, not to mention the community effort required to monitor and review pending changes requests given that some areas like ARBIPA apply to hundreds of thousands of pages. Ratnahastin(talk)01:42, 7 November 2024 (UTC)[reply]
There is a very good reason I reference Community Resources Against Street Hoodlums in my preferred name for the protection scheme, and the answer is generally no since the topic area we are primarily talking about is an ethno-political contentious topic, which tend to draw partisans interested only in "winning the war" on Wikipedia. This is not limited to just new users coming in, but also established editors who have strong opinions on the topic and who may be put into the position of reviewing these edits, as a read of any random Eastern Europe- or Palestine-Israel-focused Arbitration case would make clear just from a quick skim. —Jéské Courianov^_^vthreadscritiques18:21, 7 November 2024 (UTC)[reply]
Oppose, per what JSS has said. I am a little uncomfortable at the extent to which we've seemingly accepted preemptive protection of articles in contentious areas. It may be a convenient way of reducing the drama us admins and power users have to deal with... but only at the cost of giving up on the core principle that anybody can edit. I would rather have drama on a living project than peace on a dead one. jp×g🗯️18:16, 7 November 2024 (UTC)[reply]
Someone who is an expert at configuring mw:Extension:FlaggedRevs will need to confirm that it is possible to simultaneously have our current type of pending changes protection plus this new type of pending changes protection. The current enwiki FlaggedRevs config looks something like the below and may not be easy to configure. You may want to ping Ladsgroup or post at WP:VPT for assistance.
Extended content
// enwiki// InitializeSettings.php$wgFlaggedRevsOverride=false;$wgFlaggedRevsProtection=true;$wgSimpleFlaggedRevsUI=true;$wgFlaggedRevsHandleIncludes=0;$wgFlaggedRevsAutoReview=3;$wgFlaggedRevsLowProfile=true;// CommonSettings.php$wgAvailableRights[]='autoreview';$wgAvailableRights[]='autoreviewrestore';$wgAvailableRights[]='movestable';$wgAvailableRights[]='review';$wgAvailableRights[]='stablesettings';$wgAvailableRights[]='unreviewedpages';$wgAvailableRights[]='validate';$wgGrantPermissions['editprotected']['movestable']=true;// flaggedrevs.phpwfLoadExtension('FlaggedRevs');$wgFlaggedRevsAutopromote=false;$wgHooks['MediaWikiServices'][]=staticfunction(){global$wgAddGroups,$wgDBname,$wgDefaultUserOptions,$wgFlaggedRevsNamespaces,$wgFlaggedRevsRestrictionLevels,$wgFlaggedRevsTags,$wgFlaggedRevsTagsRestrictions,$wgGroupPermissions,$wgRemoveGroups;$wgFlaggedRevsNamespaces[]=828;// NS_MODULE$wgFlaggedRevsTags=['accuracy'=>['levels'=>2]];$wgFlaggedRevsTagsRestrictions=['accuracy'=>['review'=>1,'autoreview'=>1],];$wgGroupPermissions['autoconfirmed']['movestable']=true;// T16166$wgGroupPermissions['sysop']['stablesettings']=false;// -aaron 3/20/10$allowSysopsAssignEditor=true;$wgFlaggedRevsNamespaces=[NS_MAIN,NS_PROJECT];# We have only one tag with one level$wgFlaggedRevsTags=['status'=>['levels'=>1]];# Restrict autoconfirmed to flagging semi-protected$wgFlaggedRevsTagsRestrictions=['status'=>['review'=>1,'autoreview'=>1],];# Restriction levels for auto-review/review rights$wgFlaggedRevsRestrictionLevels=['autoconfirmed'];# Group permissions for autoconfirmed$wgGroupPermissions['autoconfirmed']['autoreview']=true;# Group permissions for sysops$wgGroupPermissions['sysop']['review']=true;$wgGroupPermissions['sysop']['stablesettings']=true;# Use 'reviewer' group$wgAddGroups['sysop'][]='reviewer';$wgRemoveGroups['sysop'][]='reviewer';# Remove 'editor' and 'autoreview' (T91934) user groupsunset($wgGroupPermissions['editor'],$wgGroupPermissions['autoreview']);# Rights for Bureaucrats (b/c)if(isset($wgGroupPermissions['reviewer'])){if(!in_array('reviewer',$wgAddGroups['bureaucrat']??[])){// promote to full reviewers$wgAddGroups['bureaucrat'][]='reviewer';}if(!in_array('reviewer',$wgRemoveGroups['bureaucrat']??[])){// demote from full reviewers$wgRemoveGroups['bureaucrat'][]='reviewer';}}# Rights for Sysopsif(isset($wgGroupPermissions['editor'])&&$allowSysopsAssignEditor){if(!in_array('editor',$wgAddGroups['sysop'])){// promote to basic reviewer (established editors)$wgAddGroups['sysop'][]='editor';}if(!in_array('editor',$wgRemoveGroups['sysop'])){// demote from basic reviewer (established editors)$wgRemoveGroups['sysop'][]='editor';}}if(isset($wgGroupPermissions['autoreview'])){if(!in_array('autoreview',$wgAddGroups['sysop'])){// promote to basic auto-reviewer (semi-trusted users)$wgAddGroups['sysop'][]='autoreview';}if(!in_array('autoreview',$wgRemoveGroups['sysop'])){// demote from basic auto-reviewer (semi-trusted users)$wgRemoveGroups['sysop'][]='autoreview';}}};
I basically came here to ask if this is even possible or if it would need WMMF devs involvement or whatever.
For those unfamiliar, pending changes is not the same thing as the flagged revisions used on de.wp. PC was developed by the foundation specifically for this project after we asked for it. We also used to have WP:PC2 but nobody really knew what that was supposed to be and how to use it and it was discontinued. Just Step Sidewaysfrom this world ..... today21:21, 6 November 2024 (UTC)[reply]
Depends on what exactly is meant by "implementation". A configuration where edits by non-extendedconfirmed users need review by reviewers would probably be similar to what was removed in gerrit:/r/334511 to implement T156448 (removal of PC2). I don't know whether a configuration where edits by non-extendedconfirmed users can be reviewed by any extendedconfirmed user while normal PC still can only be reviewed by reviewers is possible or not. Anomie⚔13:32, 7 November 2024 (UTC)[reply]
Looking at the MediaWiki documentation, it is not possible atm. That said, currently the proposal assumes that it is possible and we should work with that (though I would also support allowing all extended-confirmed to review all pending changes). Aaron Liu (talk) 13:56, 7 November 2024 (UTC)[reply]
I think the RfC summary statement is a bit incomplete. My understanding is that the pending changes feature introduces a set of rights which can be assigned to corresponding user groups. I believe all the logic is based on the user rights, so there's no way to designate that one article can be autoreviewed by one user group while another article can be autoreviewed by a different user group. Thus unless the proposal is to replace autoconfirmed pending changes with extended confirmed pending changes, I don't think saying "enabled" in the summary is an adequate description. And if the proposal is to replace autoconfirmed pending changes, I think that should be explicitly stated. isaacl (talk) 22:06, 6 November 2024 (UTC)[reply]
The proposal did not specify if it assumed co-existence is possible, or enabling it is possible, which could mean replacement. Thus I feel the summary statement (before the timestamp, which is what shows up in the central RfC list) is incomplete. isaacl (talk) 22:31, 6 November 2024 (UTC)[reply]
While on a re-read, It is assumed that it is technically possible to have PCECP does not explicitly imply co-existence, that is how I interpreted it. Anyways, it would be wonderful to hear from @Awesome Aasim about this. Aaron Liu (talk) 22:42, 6 November 2024 (UTC)[reply]
The key question that ought to be clarified is if the proposal is to have both, or to replace the current one with a new version. (That ties back to the question of whether or not the arbitration committee's involvement is required.) Additionally, it would be more accurate not to use a word in the summary that implies the only cost is turning on a switch. isaacl (talk) 22:49, 6 November 2024 (UTC)[reply]
It is assuming that we can have PC1 where only reviewers can approve edits and PCECP where only extended confirmed users can approve edits AND make edits without requiring approval. With the current iteration I don't know if it is technically possible. If it requires an extension rewrite or replacement, that is fine. If something is still unclear, please let me know. AwesomeAasim23:06, 6 November 2024 (UTC)[reply]
I suggest changing the summary statement to something like, "Should a new pending changes protection level be added to Wikipedia – extended confirmed pending changes (hereby abbreviated as PCECP)?". The subsequent paragraph can provide the further explanation on who would be autoreviewed and who would serve as reviewers with the new proposed level. isaacl (talk) 23:19, 6 November 2024 (UTC)[reply]
I think inclusion of the preemptive-protection part in the background statement is causing confusion. AFAIK preemptive protection and whether we should use PCECP over ECP are separate questions. Aaron Liu (talk) 19:11, 7 November 2024 (UTC)[reply]
Q2: If this proposal passes, should PCECP be applied preemptively to WP:ARBECR topics?
Support, including on talk pages. With edit requests mostly dealt with through pending changes, protecting the talk pages too should limit the disruption and unconstructive comments that are often commonplace there. (Changing my mind, I don't think applying PCECP on all pages would be a constructive solution. The rules of ARBECR limit participation to extended-confirmed editors, but the spirit of the rules has been to only enforce that on pages with actual disruption, not preemptively. 20:49, 7 November 2024 (UTC)) Chaotic Enby (talk · contribs) 20:21, 5 November 2024 (UTC)[reply]
Support I'm going to disagree with the "no" argument entirely - we should be preemptively ECPing (even without pending changes). It's a perversion of logic to say "you can't (per policy) do push this button", and then refuse to actually technically stop you from pushing the button even though we know you could. * Pppery *it has begun...20:52, 5 November 2024 (UTC)[reply]
Support (Summoned by bot): While I disagree with ECR in general, this is a better way of enforcing it as long as it exists. Constructive "edit requests" can be accepted, and edits that people disagree with can be easily reverted. I'm slightly concerned with how this could affect the pending changes backlog (which has a fairly small number of active reviewers at the moment), but I'm sure that can be figured out. CFA💬23:41, 5 November 2024 (UTC)[reply]
Oppose (Preemptive PCECP)
No, I don't think this is necessary at this time. I think it should be usable there, but I don't feel like this is a necessary step at this time. We could revisit it later. WhatamIdoing (talk) 20:37, 5 November 2024 (UTC)[reply]
No, we still shouldn't be protecting preemptively. Wait until there's disruption, and then choose between PCXC or regular XC protection (I would strongly favour the former for the reasons I gave above). Cremastra (u — c) 20:43, 5 November 2024 (UTC)[reply]
No, I feel this would be a bad idea. Critics of Wikipedia already use the idea that it's controlled by a select group, this would only make that misconception more common. -- LCU ActivelyDisinterested«@» °∆t°14:36, 6 November 2024 (UTC)[reply]
Absolutely not. No need for protection if there is no disruption. The number of protected pages should be kept low, and the number of pages that cry out "look at me!" on your watchlist (anything under pending changes) should be as close to zero as possible. —Kusma (talk) 21:44, 6 November 2024 (UTC)[reply]
I'm not saying such a discussion exists, but changes to Arbitration remedies/discretionary sanctions are something they would want to weigh in on. Arbitration policy (which includes WP:Contentious topics) is in their wheelhouse and this would have serious implications for WP:CT/A-I and any further instances where ArbCom (rather than individual editors, as a discretionary sanction) would need to resort to a 500/30 rule as an explicit remedy. —Jéské Courianov^_^vthreadscritiques04:58, 6 November 2024 (UTC)[reply]
That is not my reading of WP:ARBECR. Specifically, On any page where the restriction is not enforced through extended confirmed protection, this restriction may be enforced by...the use of pending changes... (bold added by me for emphasis). But if there is consensus not to use this preemptively so be it. AwesomeAasim05:13, 6 November 2024 (UTC)[reply]
While I appreciate the forward thinking that PCECP may want to be used in Arb areas, this feels like a considerable muddying of the delineation between the Committee's role and the community's role. Traditionally, Contentious Topics have been the realm of ArbCom, and General Sanctions have been the realm of the Community. Part of the logic comes down to who takes the blame when things go wrong. The Community shouldn't take the blame when ArbCom makes a decision, and vice versa. Part of the logic is separation of powers. If the community wants to say "ArbCom, you will enforce this so help you God," then that should be done by amending ArbPol. Part of the logic is practical. If the community creates a process that adds to an existing Arb process, what happens when the Arbs want to change that process? Or even end it altogether? Bottomline: Adopting PCECP for ARBECR is certainly something ArbCom could do. But I'd ask the community to consider the broader structural problems that would arise if the community adopted it on behalf of ArbCom. CaptainEekEdits Ho Cap'n!⚓05:18, 7 November 2024 (UTC)[reply]
Interesting. I'd say ArbCom should be able to override the community if they truly see such action fit and worthy of potential backlash. Aaron Liu (talk) 12:30, 7 November 2024 (UTC)[reply]
Just a terminology note, although I appreciate many think of general sanctions in that way, it's defined on the Wikipedia:General sanctions page as ... a type of Wikipedia sanctions that apply to all editors working in a particular topic area. ... General sanctions are measures used by the community or the Arbitration Committee ("ArbCom") to improve the editing atmosphere of an article or topic area.. Thus the contentious topics framework is a form of general sanctions. isaacl (talk) 15:22, 7 November 2024 (UTC)[reply]
Regarding the general point: I agree that it is cumbersome for the community to impose a general sanction that is added on top of a specific arbitration remedy. I would prefer that the community work with the arbitration committee to amend its remedy, which would facilitate keeping the description of the sanction and logging of its enforcement together, instead of split. (I appreciate that for this specific proposal, logging of enforcement is not an issue.) isaacl (talk) 15:30, 7 November 2024 (UTC)[reply]
Extended confirmed started off as an arbcom concept - 500 edits/30 days - which the community then choose to adopt. ArbCom then decided to make its remedy match the community's version - such that if the community were to decide extended confirmed were 1000 edits/90 days all ArbCom restrictions would update. I find this a healthy feedback loop between ArbCom and the community. The community could clearly choose (at least on a policy level, given some technical concerns) to enact PCECP. It could choose to apply this to some/all pages. If it is comfortable saying that it wants to delegate some of which pages this applies to the Arbitration Committee I think it can do so without amending ArbPol. However, I think ArbCom could could decide that PCECP would not apply in some/all CTOP areas given that the Committee is exempt from consensus for areas with-in its scope. And so it might ultimately make more sense to do what isaacl suggests. Best, Barkeep49 (talk) 16:02, 7 November 2024 (UTC)[reply]
The "contentious topics" procedure does seem like something that the community should absolutely mirror and that ultimately both the community and ArbCom should work out of. If one diverges, there is probably a good reason why it diverged.
As for the broader structural problems that would arise if the community adopted it on behalf of ArbCom, there are already structural problems with general sanctions because of the community's failure to adopt the new CTOP procedure for new contentious topics. Although the community has adopted the contents of WP:ARBECR for other topic areas like WP:RUSUKR, they don't adopt it by reference but by copying the whole text verbatim. AwesomeAasim17:13, 7 November 2024 (UTC)[reply]
That's not the same structural problem. The community hasn't had a lot of discussion about adopting the contentious topic framework for its own use (in my opinion, because it's a very process-wonky discussion that doesn't interest enough editors to generate a consensus), but that doesn't interfere with how the arbitration committee uses the contentious topic framework. This proposal is suggesting that the community automatically layer on its own general sanction on top of any time the arbitration committee decides to enact a specific sanction. Thus the committee would have to consider each time whether or not to override the community add-on, and amendment requests might have to be made both to the committee and the community. isaacl (talk) 17:33, 7 November 2024 (UTC)[reply]
Prior to contentious topics there were discretionary sanctions. Those became very muddled and so the committee created Contentious topics to help clarify the line between community and committee (disclosure: I help draft much of that work). As part of that the committee also established ways for the community to tie-in to contentious topics if it wanted. So for the community hasn't made that choice which is fine. But I do this is an area that, in general, ArbCom does better than the community because there is more attention paid to having consistency across areas and when a problem arises I have found (in basically this one area only) ArbCom to be more agile at addressing it. But the community is also more willing to pass a GS than ArbCom is to designate something a CT (which I think is a good hting all around) and so having the community come to consensus about how, if at all, it wants to tie in to CT (and its evolutions) or if it would prefer to do its own thing (including just mirroring whatever happens to be in CT at the time but not subsequent changes) would probably be a good meta discussion to have. But it also doesn't seem necessary for this particular proposal. Best, Barkeep49 (talk) 17:41, 7 November 2024 (UTC)[reply]
Q3: If this proposal does not pass, should ECP be applied preemptively to articles under WP:ARBECR topics?
Support (preemptive ECP)
Support as a second option, but only to articles. Talk pages can be enforced solely through reverts and short protections so I see little reason why those should be protected. AwesomeAasim19:58, 5 November 2024 (UTC)[reply]
Support for articles per Aasim. Talk pages still need to be open for edit requests. (Also changing my mind, per above. If anything, we should clarify ARBECR so that the 500-30 limit is only applied in cases where it is needed, not automatically, to resolve the ambiguity. 20:52, 7 November 2024 (UTC)) Chaotic Enby (talk · contribs) 20:20, 5 November 2024 (UTC)[reply]
I agree with Chaotic Enby and Pppery above and think all CT articles should be protected. I am generally not a fan of protecting Talk pages, but it's true that many CT Talk pages are cesspools of hate, so I am not sure where I sit on protecting Talk pages. Toadspike[Talk]20:57, 5 November 2024 (UTC)[reply]
Oppose (preemptive ECP)
Oppose because I think this is a bad idea. For one thing, just making a list of all the covered articles could produce disputes that we don't need. (This article might be covered, but is it truly covered? Reasonable people could easily disagree about whether some articles are "mostly" about the restricted area vs "partly", and therefore about whether the rule applies.) Second, where a serious and obvious problem, such as blatant vandalism, is concerned, it would be better to have an IP revert it than to mindlessly follow the rules. It is important to remember that our rules exist as a means to an end. We follow them because, and to the extent that, they help overall. We expect admins and other editors to exercise discretion. It is our policy that Wikipedia:If a rule prevents you from improving or maintaining Wikipedia, ignore it. This is a proposal to declare that the IAR policy never applies to the rule about who should normally be editing these articles, and that exercising discretion is not allowed. WhatamIdoing (talk) 20:42, 5 November 2024 (UTC)[reply]
While there's already precedent for preemptive protection at e.g. RFPP, I do not like this. For one, as talk pages (and, by extension, edit requests) cannot use the visual editor, this makes it much harder for newcomers to contribute edits, often unnecessarily on articles where there are no disruption. Aaron Liu (talk) 23:47, 5 November 2024 (UTC)[reply]
Mu - This is basically my reading of the 500/30 rule as writ. Anything that would fall into the 500/30'd topic should be XCP'd on discovery. It's worth noting I don't view this as anywhere close to ideal but then neither did ArbCom, and given the circumstances of the real-world ethnopolitical conflict only escalating as of late (which in turn feeds the disruption) the only other - even worse - option would be full-protection across the board everywhere in the area. So why am I not arguing Support? Because just like the question above, this is putting the cart before the horse and this is better off being discussed after this RfC ends, not same time as. —Jéské Courianov^_^vthreadscritiques02:47, 6 November 2024 (UTC)[reply]
Absolutely not, pages that do not experience disruption should be open to edit. Pending changes should never become widely used to avoid situations like dewiki's utterly absurd 53-day backlog. —Kusma (talk) 21:53, 6 November 2024 (UTC)[reply]
Very strong oppose, again Kusma puts it excellently. Protection should always be the exception, not the norm. Even in the Israel-Palestine topic area most articles do not experience disruption. Thryduulf (talk) 13:50, 7 November 2024 (UTC)[reply]
Since we're assuming that PCECP is possible and the last two questions definitely deal with policy, I feel like maybe this should go to VPP instead, with the header edited to something like "Extended-confirmed pending changes and preemptive protection in contentious topics" to reflect the slightly−larger-than-advertised scope? Aaron Liu (talk) 23:53, 5 November 2024 (UTC)[reply]
I think policy proposals are also okay here, though I see your point. There is definitely overlap, though. This is both a request for a technical change as well as establishing policy/guidelines around that technical change (or lack thereof). AwesomeAasim00:26, 6 November 2024 (UTC)[reply]
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.
Okay, to make this clear, The content should NOT be taken down. NSFW and NSFl content needs to be shown because Wikipedia is a censor free website. No content should be treated over the other and NSFW and NSFL content needs to be treated the same as all the others. Now the proposal I will make is that since a lot of kids use Wikipedia to learn stuff and they may come across these things. For the sake of safety, gory, offensive and sexual content should have a blur or a black screen, and in order to view the image, they have to click the image and click I am over 18 or something like for example, they come across the Russo-Ukrainian war. In this article there is a gory picture. What there should be instead is a blur or a black box, the description of the picture still stays, and in order to view the content they have to press the picture, and it will ask for verification, like when you press the picture it says, this picture has gore in it or something like that, then it says you have to be 18 to view the image or something like that, then there is a button saying I am over 18 or something like that, then to view the content just press the button. If this somehow doesn’t work at least have a disclaimer at the top saying there is bad stuff in it. So yeah, here is my suggestion. Datawikiperson (talk) 11:11, 6 November 2024 (UTC)[reply]
This has been proposed many times previously. It has failed for multiple reasons, including what should be censored being highly context and culturally (and even subculturally) dependent - for example person A might wish to blur a photograph of a woman breastfeeding but not a photograph of a gunshot wound, while person B might wish the exact opposite. If you take the view that anything anybody wants to be blurred should be blurred, even if others do not, but that would lead to extremes like all images of people being blurred.
A second reason is that there is no practical reason to apply the setting en-masse. At first glance, images in Commons:Category:Sex and subcategories would seem to be fairly uncontroversial, but that falls apart very quickly when you see what sort of images that would catch, for example:
So it would have be to set for at least each category, without subcategories, and there are at least thousands of them on Commons. At the individual image level you are looking at over 110 million. And that's assuming you can get agreement (per above). Thryduulf (talk) 11:57, 6 November 2024 (UTC)[reply]
I agree with what Lectonar and Thryduulf have said above. If this was implemented it would (since most of our editors are American) be as a very Americo-centric view of what is not safe - it would be Thryduulf's person A's view, not mine. The only way to guarantee safety is to block all images using one of the approaches on the page mentioned by Lectonar, Phil Bridger (talk) 13:17, 6 November 2024 (UTC)[reply]
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.
Add AI translation option for translating from English to non-English article.
AI certainly improved a lot by now. It can translate to many non-english language better than traditional translators . My suggestion is to add AI translation option for translating from English to non-English article. User will review the AI translation to see if its correct. It will increase the translation quality. I dont suggest using AI for English article, that could have a devastating impact. Dark1618 (talk) 18:50, 7 November 2024 (UTC)[reply]
That's out of scope here, and would need to be asked on each and every individual language-edition of Wikipedia, as those would be the ones dictating policy for translations into their respective languages. —Jéské Courianov^_^vthreadscritiques19:10, 7 November 2024 (UTC)[reply]
Why would a translation into English be devastating, but a translation from English into any other language be acceptable? English just happens to be that most used language in the world by some measures: beyond that it has no special status. Anyway, we can not decide here what is appropriate for other language Wikipedias. Phil Bridger (talk) 19:33, 7 November 2024 (UTC)[reply]
"Wikipedia:Redirect sandbox"
A sandbox for testing redirects, which redirects to Wikipedia:Sandbox and has a sandbox notice when you click for more information about that sandbox. It can be redirected anywhere and is automatically reverted like all other sandboxes.
What is there to test that this would be good for? If you make a mistake while creating a redirect, you can just fix it. Remsense ‥ 论08:42, 8 November 2024 (UTC)[reply]
Draftification has long been criticized as a backdoor to deletion. In New Pages Patrol (NPP), it is common to move new articles that are not ready for mainspace to draftspace. This way, articles that could potentially be suitable for Wikipedia, but are not yet, are preserved. The article creator then gets a chance to improve their article without NPPers breathing down their necks or having it taken to Articles for Deletion. If anyone, including the article creator, objects to draftification, the article should be moved back to mainspace (draftification should be reversed). This is explained by DRAFTNO #6 and #7. No reason is required for the objection.
Problem: However, we also have a rule that drafts that haven't been edited for six months get automatically deleted, under Criterion for Speedy Deletion G13. So, well-meaning New Page Patrollers will unilaterally draftify new articles that are not yet ready for the encyclopedia. The new editors who created the article may disagree with the move, without knowing that they can object. The new users can get discouraged and leave Wikipedia altogether, and after six months the draft is deleted under CSD G13. As this process happens without community discussions, it results in draftification being called a "backdoor to deletion".
Solution: This problem can be solved without changing policy or current practice. We just need to make it very obvious to new users that they can object to draftification. We can also make it easy to reverse the draftication (assuming the new user is autoconfirmed). I suggest we do this by adding a template to all draftified articles. The template would include a big blue button, similar to the "Submit the draft for review!" button at Template:AfC submission/draft, which says "Object to this move". Clicking this button either: 1. Leaves a message on the talk page of the editor who draftified, notifying them that there has been an objection to the move and requesting that it be immediately reversed. 2. Moves the page back to mainspace automatically, or if the editor's account is unable to perform this task, creates an entry at Requested moves/Technical moves to that effect. The latter is better, but also more technically complex. Adding a similar button to Template:Uw-articletodraft, the warning typically given upon draftification, would also be helpful.
Implementation: Once the new template is ready, it can be added to MPGuy's MoveToDraft userscript, which is the most common way for NPPers to draftify articles. It should be placed above the AfC template on all draftified articles.
I would appreciate comments from technically skilled editors, who could create this template (or tell me that it's impossible), from NPPers who draftify articles, and from uninvolved editors who have opinions on the draftification process. Toadspike[Talk]10:37, 26 September 2024 (UTC)[reply]
This idea isn't really my own, it was obviously sparked by the most recent RfA. A similar idea was previously discussed here, but that discussion proposed a requirement that all editors have to follow (policy), not a technical solution, and turned into a trainwreck. To prevent something similar, I ask all participants to please focus on improving the current situation instead of debating the morality of draftification as a whole. Toadspike[Talk]11:03, 26 September 2024 (UTC)[reply]
Notifying the users who commented most directly on this topic at the RfA: @Alalch E.@User:Onel5969@User:Hobit@User:Fangz@User:Nsk92. I have also notified the NPP Talk page and posted a message on Discord. I am not sure how to notifying all participants of the previous discussion (aside from doing it manually) and I am not sure that is productive considering how many people were involved and how offtopic it got, so I won't do that for now. Toadspike[Talk]11:07, 26 September 2024 (UTC)[reply]
Oppose: The draftification message could be tweaked, but a big button to reverse the move will lead to more AfDs, higher strain on NPP, more BITEY behaviour, and worse editor retention. Draft space is incredibly valuable, and people have some incredibly warped views about the space. If we did something like this then we'd end up chasing away new editors because learning how to make your article meet our complicated guidelines in under 7 days (AfD tag) is not easy for a lot of folks. Draft space gives them the opportunity to work on the content, to receive advise, and to make articles that will actually survive at AfD and allow them to stick around. Really we need to draftify more, and I've taken it upon myself to begin to do so again and encourage others to do. I'm big on editor retention. This is not the way to do it. Hey man im josh (talk) 12:15, 26 September 2024 (UTC)[reply]
The problem with unilateral draftification is that it can also be incredibly bitey, especially when done for arbitrary reasons that have nothing to do with any of the reasons why something might be deleted at AfD (although this is less prevalent than the trivial reasons things are rejected at AfC). We should be draftifying fewer articles and not sending them to AfD either but rather leaving them in the mainspace (With appropriate tags where justified) so that they can be found and improved rather than pretending that they don't exist for six months and then deleting them. Thryduulf (talk) 12:34, 26 September 2024 (UTC)[reply]
I'm not really convinced draftification is any worse than the alternatives - tagging is *also* bitey as well, and one user tagging an article and leaving it in mainspace could lead to another user seeing it and deciding to AfD. Draftification could be a way to protect an article until it enters a better state. But I think the other part I have an issue with is the lack of clear guidelines. Clearly some people have an issue with draftification and others do not, and people have different ideas what it is for. That needs to be made more concrete. Otherwise just saying "we should use draftification less" isn't going to lead to any positive changes. Fangz (talk) 12:43, 26 September 2024 (UTC)[reply]
I agree with the general sentiment – arguing for more or less draftification does not solve the problem that new users basically can't object to it. Toadspike[Talk]12:47, 26 September 2024 (UTC)[reply]
I envision a template (possibly one specific for relatively new users?) being something like:
1. Hi, this article has been moved to a draft form because another user thinks it has potential but is not ready for the encyclopedia just yet. REASON:
2. You can continue to work on it while it's not published, though note that if not editted for 6 months it will be deleted. Here are some useful resources.
3. When you think the article is ready you can submit the article to a review, which can give useful feedback. []
4. Alternatively you may return the article to the main encyclopedia at any time and have it be editted while part of the main encyclopedia. See WP: Draft Object. Note however that if other users think there are unfixable issues with the article it may be put forward as a candidate for deletion. Fangz (talk) 12:54, 26 September 2024 (UTC)[reply]
In my view draftified articles should (semi?) automatically return to the mainspace after timeout instead of be deleted. Or at least be re-evaluated for notability. I do not really see the reason for automatic speedy deletion, except as backdoor deletion. Fangz (talk) 18:59, 26 September 2024 (UTC)[reply]
Why can't they just improve it in mainspace, without the sting on of an initial rejection and a six month deletion countdown hanging over them? I don't get why you keep presenting this as a choice between draftspace and AfD. – Joe (talk) 18:46, 26 September 2024 (UTC)[reply]
The reason is that "improving it in mainspace" has its own issues. An article in mainspace has to juggle being of service to the reader to being of service to the editor. This implies formal processes and wikijargon for consistency, unified templates for issues in the article, clear and ruthless labelling of problems and so on. There's a strong tendency for the first experience of an editor to be a very public and humiliating fight against established editors who have a better understanding of wikipedia processes, quickly driving the editor away or getting them blocked. It is also very difficult to improve on this experience as it would imply fundamental changes affecting all sorts of things. Meanwhile improving an article in draft mode allows for a more informal process of communication to shepherd an article towards an acceptable state. Fangz (talk) 19:10, 26 September 2024 (UTC)[reply]
I did a little work on page view statistics recently. The median article gets about one page view per week. So if the new article is typical, then it doesn't have to "be of service to the reader", because there aren't really any readers. Editors (especially NPP and RecentChanges folks) may look at a brand-new article a few dozen times on the first day, but once the reviewers leave it alone, most articles just don't have much traffic.
I think the reason we are unwilling to "improve it in mainspace" is because we're scared that we'll forget that it was there, and years later, someone will be embarrassed to discover that an WP:UGLY article has been neglected ever since. We are using draftification and other threats as a way to make otherWP:VOLUNTEERS improve the article to our idea of acceptable quality. WhatamIdoing (talk) 20:40, 26 September 2024 (UTC)[reply]
I don't know if we're looking at different draft namespaces, but an "informal process of communication to shepherd an article towards an acceptable state" sounds like the precise opposite of our current AfC process. – Joe (talk) 06:19, 27 September 2024 (UTC)[reply]
I don't like the idea of a button but I do think the template should be changed. I think having a button suggests it's a default option, but I think a link is okay. Fangz (talk) 12:37, 26 September 2024 (UTC)[reply]
But articles aren't inherently "AfC drafts" once draftified. People are allowed to move them back to mainspace themselves, no questions asked, or optionally submit them to AfC. The AfC draft template makes no mention of the first option. CFA💬12:48, 26 September 2024 (UTC)[reply]
I wonder if we will ever quit using the inappropriate and legally unsound "publication" language in that template. On this wiki, it's the author, not the AFC reviewer, who "publishes" it. WhatamIdoing (talk) 20:43, 26 September 2024 (UTC)[reply]
Yeah but then you have to specify "move to mainspace" or something and that feels really jargony. "Move out of draft", maybe? – Joe (talk) 04:49, 1 October 2024 (UTC)[reply]
Well, that might solve the problem. I doesn't explain to new users how their article turned into a draft, but at least there's an easy way to reverse it. I won't withdraw this for now, maybe others have thoughts. (P.S. you might want to update User:MPGuy2824/MoveToDraft) Toadspike[Talk]12:51, 26 September 2024 (UTC)[reply]
This is the idea lab so no bolded comment from me, but I have mixed feelings. I am in favour of softening the experience for newcomers, but I'm opposed to the concept of draftification being automatically reversible. If a new page patroller reviews a new article and moves it to draft because it's clearly unsuitable for mainspace, the creator should need to do more than just say "I object" in order to move their clearly unsuitable article back again. I've recently proposed that all of draftspace should be move-protected at the semi level (the proposal was not well received - fair enough). This is probably the rule I ignore more than any other on Wikipedia, mostly dealing with spam sockfarms that try to abuse the rule to promote their garbage. Besides, a new user whose submission is quarantined to draft space and they're left with instructions and a list of suggestions with helpful links is already getting better treatment than most editors ever have or will, and if their reaction to that is to rage-quit then they're probably not a good fit for the collaborative environment of Wikipedia anyway. Ivanvector (Talk/Edits) 12:57, 26 September 2024 (UTC)[reply]
@Ivanvector, you know the joke about "If you ask three people, you'll get four opinions"? I wonder if we ask three NPPers what "ready for mainspace" means, if we'd get four opinions. AFAICT, "ready for mainspace" most often means "contains at least as many refs as the median article, but higher quality ones". All the children in Lake Wobegon are above average, and all the new Wikipedia articles must be, too. WhatamIdoing (talk) 20:12, 26 September 2024 (UTC)[reply]
As far as I see it draftification should never be used for subjects which pass GNG, and it should only be standard for things like films/TV series/games which are in the works but have not yet begun production. Subjects with debatable notability should be sent to AFD to the issue can be resolved.★Trekker (talk) 13:00, 26 September 2024 (UTC)[reply]
Subjects that pass WP:GNG should never be draftified at all, instead they should be tagged and dealt with using normal community procedures. I agree that films/TV series/games/political events probably best fit the bill for draftifications, but so do potentially notable but underdeveloped articles. Sohom (talk) 13:33, 26 September 2024 (UTC)[reply]
This is out of step with the present form of Wikipedia:DRAFTIFY, and I don't think it makes sense anyway. Articles that fail GNG should not be draftified, they should be AfDed. Films etc that are in the works should not be draftified merely because they aren't in production, and it's not really a great use for draft space because there's no guarantee that there would be a change of situation to establish notability within 6 months. Articles should be draftified only if the reviewer believes the article can be editted into an acceptable state within the time window. This implies a pass of GNG - i.e. a belief that reliable sources are potentially out there. Remember that GNG is about the *subject*, not about the state of the article. Fangz (talk) 14:09, 26 September 2024 (UTC)[reply]
In my view the correct use of draftification is sort of as an alternative version of the WIP template. An acknowledgement that the article is not ready and should be being worked on and will likely have multiple issues, but in a protected sandboxed environment to avoid overly zealous moderation and promotion of misunderstanding for casual readers, and without implying the original editor is the one working on it. For new users it should offer a less formal and jargony process to learning how to improve an article than tagging based methods, because the latter has to balance the need to inform *readers* as well as editors. Fangz (talk) 14:23, 26 September 2024 (UTC)[reply]
If you evaluate that a article passes WP:GNG, then there is not point in draftifying it, you could just add a {{sources exist}} template, patrol and move on. Alternatively, if you evaluate that a article fails WP:GNG, there is no point in wasting the article creator's time and you should WP:AFD/PROD it.
The only case where you would draftify a article is if you saw a article that a) had a credible claim to significance/notability b) does not meet/prove notability in it's current state c) has been created in the last week or so by a inexperienced article creator. Sohom (talk) 14:43, 26 September 2024 (UTC)[reply]
Not sure if we're disagreeing or we're having some semantics thing about what "passes GNG" means.
I think then you're pretty much arguing that the draftification process should be removed entirely, and I don't agree with that. It has its advantages. It should not be made a mandatory process by any means but just as some users prefer to work on articles as a draft and then push to the public wiki, it can be a better resolution to certain issues than the alternatives. Fangz (talk) 17:44, 26 September 2024 (UTC)[reply]
I do think that we've fallen into a false binary here. The options are not "garbage in the mainspace" vs "auto-deleted as in the draftspace". There are other options (e.g., sticky prods for uncited articles, userification, bold stubbification, bold merging, developing a more consistent and predictable standard for evaluating articles, etc.). WhatamIdoing (talk) 20:20, 26 September 2024 (UTC)[reply]
I think there is a argument to be made that this landscape might have changed a fair bit since this research was done. The latest data that these projects consider is from 2014-2017. WP:ACTRIAL happened after that research was done, and Wikipedia's policies have changed since those times. Sohom (talk) 20:48, 26 September 2024 (UTC)[reply]
It's possible that things have changed, and I'm never one to turn down a new research project if you happen to be volunteering to do it (I believe that all the necessary data is public), but looking at the overall deletion rate in that namespace, it seems unlikely that the result will be materially different. WhatamIdoing (talk) 20:31, 27 September 2024 (UTC)[reply]
I think then you're pretty much arguing that the draftification process should be removed entirely, and I don't agree with that. I'm sorry to pick on you but this is the clearest example yet of the circular reasoning that has got us into this mess: draftification must be good because we do it, so we must keep doing it because it's good. From literally the moment draftspace was created and people started doing this (before that, the equivalent process of userfication was expressly forbidden without prior discussion), others have been pointing out that the underlying logic makes no sense. Draftification is only for articles that shouldn't be deleted, but it's also only for articles that can't be in mainspace. But since fix good content in place is a part of the editing policy and almost all the community accepted reasons for deletion involve the potential of the article, not it's current state, the intersection of those two sets is functionally zero (apart from some consensus-established edge cases like paid creations or upcoming films).
This is why attempts to clarify and improve policy around draftification—and I've been closely involved in many of them—keep failing. You try to find a solid basis for guidelines and there just isn't one. We really need to stop trying to square the circle of justifying draftification as it is practiced now, and start asking what we the community actually wants to achieve with it and whether what we're doing now fulfils that aim. So far it's not looking good for the send-them-all-to-draftspace-and-the-god-of-notability-will-recognise-his-own camp, because there's not a shred of evidence that it helps improve content, retain editors or manage the NPP workload, and as WAID says above the empirical studies we do have concluded the precise opposite. But that picture could change with more research – somebody just needs to step up and do it! – Joe (talk) 07:01, 27 September 2024 (UTC)[reply]
@Joe RoeDraftification is only for articles that shouldn't be deleted, but it's also only for articles that can't be in mainspace. That is the exact reason why draftspace exists in the first place. Imagine you see a article with the following content: Nicholas Carlini is an amazing researcher at Google working on adversarial machine learning. created in the last week or so and sourced to a person's personal web-page. On doing a quick google search, you see that the person exists and is a researcher at said company, however, due to your unfamiliarity with adversarial machine learning topic-area you are not able to immediately identify the person's impact on the field. Do you 1) WP:BITEly nominate the article for deletion 2) leave the content up for somebody to deal with it (and hope that the other somebody will not choose option 1) or 3) draftify the article with a note that more sources are required to prove notability? Sohom (talk) 11:25, 27 September 2024 (UTC)[reply]
@Sohom Datta None of them. What you do is add a template to the article noting the lack of sources, leave a friendly message on the creator's talk page explaining the issues in plain English, and leave a note about it at Wikipedia talk:WikiProject Computer science. Depending on what your research found you could add more information, add some sources that might or might not demonstrate notability, remove the peacock terms, etc. Yes, this is more effort than blinding draftifying or AfDing but it is far more important that things get done well than things get done quickly. Thryduulf (talk) 12:37, 27 September 2024 (UTC)[reply]
@Sohom Datta, thanks for creating Nicholas Carlini, whose first version does not contain the hypothetical sentence you gave in your comment above. In your example above, why can't that stay in the mainspace? I frankly don't love it, and I'd immediately pull the word "amazing" out, but what's the policy basis for saying "that article truly can't be in mainspace"? WhatamIdoing (talk) 21:10, 27 September 2024 (UTC)[reply]
@Fangz I'm not arguing for the elimination of draftspace, it has it's uses as an optional space where articles can be developed over time so they don't have to meet all the relevant content policies from the very first edit. I'm also not arguing for the elimination of all draftifcation, just the majority of unilateral draftification because, as Joe has put better than I can, it is not a net benefit to the project as currently practised. Thryduulf (talk) 12:46, 27 September 2024 (UTC)[reply]
There's a middle ground between meets-GNG-mark-as-reviewed and fails-GNG-send-to-AfD: recently created articles where the sources in the article do not validate GNG, but where the new page reviewer hasn't done a BEFORE search. I think it's perfectly fair (and permissioned within the current draftification process) to say "this recently created article doesn't demonstrate GNG yet, but I'll kick it back to the creator in draft form to put in some more sources." Dclemens1971 (talk) 04:43, 29 September 2024 (UTC)[reply]
This would mean we're either leaving these articles unpatrolled (which is obviously undesirable), or giving new page patrollers the job of finding sources on every article where the original author hasn't, which would be ideal in, well, ideal conditions, but puts the burden of actually sourcing the encyclopedia on a very small group of editors. In my opinion, there should be a way to ask the original author to add sources to show it meets GNG, beyond just putting a "notability" tag and being done with it. Chaotic Enby (talk · contribs) 19:53, 1 October 2024 (UTC)[reply]
I agree with Chaotic Enby. Drafification is a good solution because it strongly encourages the author to improve the article, and, most importantly, gets it out of mainspace so that it isn't a problem for innocent readers – without forcing NPPers to clean up other peoples' messes. Cremastra (talk) 20:06, 1 October 2024 (UTC)[reply]
Drafticiation [...] strongly encourages the author to improve the article. That's the theory but the evidence is that in practice it very rarely does this. There is also little to no evidence that most pages moved to draftspace are actually a problem for innocent readers rather than being a problem for those who want immediate perfection. Thryduulf (talk) 20:47, 1 October 2024 (UTC)[reply]
About wanting to ask the original author to add sources to show it meets GNG, beyond just putting a "notability" tag and being done with it, I wonder if it's actually possible to do this in a non-coercive way. The options right now are:
Move article to Draft: space (essentially holding the article hostage, to be deleted if you give up or can't figure out how to do it).
Send to AFD today.
AFAICT a method for "force another WP:VOLUNTEER to improve the article to my standards" option has proven pretty elusive. But if you want to reach that point, I suggest that you take a baby step towards it in the form of getting a policy (any policy, really) to actually, directly, unambiguously say that every article must cite at least one source. Until the community agrees that this actually is a requirement, then we have no hope of getting them to increase the requirement all the way up to "show it meets GNG". WhatamIdoing (talk) 00:20, 2 October 2024 (UTC)[reply]
If a new editor thinks their article is ready for mainspace, they will put it there. They will also happily revert the move. If a new editor is unsure, they will probably ask for help first or use draftspace. Cremastra (talk) 19:35, 26 September 2024 (UTC)[reply]
I think the concern expressed by Joe and others who support the "backdoor" theory is that new users do not know how to revert the move to draftspace. Do you disagree with that assumption? Toadspike[Talk]19:53, 26 September 2024 (UTC)[reply]
I think most users do not know how to revert the move, yes. I also think we shouldn't hand it to them on a silver platter, because that likely largely annuls the whole point of draftification. What is the solution to this? I couldn't tell you. Cremastra (talk) 20:09, 26 September 2024 (UTC)[reply]
They don't know how, maybe, but more importantly that they don't know that they're allowed to. We have to remember how very unusual our collaborative process is. If an inexperienced editor contributes an article to Wikipedia and then it is swiftly unpublished with a message that there's something wrong with it, they won't think, hmm, I'm not sure if I agree with that, I'm going to revert and/or discuss this with my peer-editors to find a consensus. They'll think that with someone the authority to decide what happens to articles has rejected my contribution, and I'm a mere newbie. At that point they will either give up (the majority) or they'll persevere and get into cycle of trying to satisfy first the NPP reviewer and then a succession of AfC reviewers until they finally give up or manage to write a GA, which seems to be roughly the standard AfC is applying these days Even very experience editors fall into this trap because even though the templated messages try to communicate the full range of options the user has (now at least, after I and others have spent several years fighting for it), it's really hard to communicate that we're all equal and all have a say here within a draft–review structure that implicitly elevates the opinions of reviewers over others. – Joe (talk) 07:31, 27 September 2024 (UTC)[reply]
I've pulled the most recent 10 articles moved to mainspace with the AFCH script. They are:
That's an average of 372.5 words and 12.6 refs. The median article has 338 words and 4 refs. Compared to existing articles, 53% of our existing articles have fewer than 372.5 words, and 83% have fewer fewer than 12.6 refs. One in six articles has fewer words than the shortest in this list. One of three articles is shorter than the second-shortest in this list.
I think it is clear from these numbers that AFC is expecting more refs than existing community practice, and that they are trying to accept only articles that are already as long as ones that editors have been working on in the mainspace for years.
BTW, during the same span of time, more than 100 pages were deleted from the Draft: namespace. You shouldn't assume this means that more than 90% of drafts get deleted, because deletions are bursty and this is a relatively small sample size, but that's about what I expected. WhatamIdoing (talk) 20:56, 27 September 2024 (UTC)[reply]
A Conclusion: I am sadly not surprised at the current state of this discussion. Some of the heated off-topic arguments verge on NOTHERE behavior. I am very disappointed to see this from experienced editors. To those of you who simply commented on the proposal: I appreciate you a lot.
Since the default NPP draft template was changed to Template:Draft article a day before this discussion began, I think my proposal is moot. I don't see how we could improve that template much, but I may raise some minor wording changes on the Template Talk. If someone wants to close this discussion, that's fine; if others wish to continue discussing other things here, I wish you the all best. Toadspike[Talk]21:16, 27 September 2024 (UTC)[reply]
Worth also talking about the usertalk notification MTD leaves, which only provides one option: submit for review. Agree in principle we shouldn't trick people into thinking draftification/AfC is mandatory for a typical article creator. — Rhododendritestalk \\ 13:29, 28 September 2024 (UTC)[reply]
Strong Oppose All it will do is destroy the draft system as it stands and eventualy destroy Wikipedia. This almost happened between 2008 and 2012, before the draft process was available, when Wikipedia was flooded with paid/coi editors and there was no effective system to deal with them. Do folk not understand what draftification is. Every publisher has draft process. It is NOT a route to deletion. That is what the detractors of the system say, many of them who are paid to oppose it and destroy it. It is the one of the core safeguards we have against the complete destruction of Wikipedia. scope_creepTalk11:46, 29 September 2024 (UTC)[reply]
That comment is almost entirely evidence free assumptions of bad faith. Please try engaging with the discussion rather than just knee-jerking oppose to changing the status quo because it would change the status quo. Thryduulf (talk) 12:56, 29 September 2024 (UTC)[reply]
Its not evidence free and I resent the fact that you have said my comment bad faith. Why would I make the comment if I didn't know what I was talking about. I've worked in NPP/AFC since it was created and was involved in some of the early discussions. I now how exactly how UPE/paid editors behave. It would lead to an exodus of editors after the place gets flooded with adverts. It would be free-for-all. The reality is that the editor who posted hasn't thought it through and hasn't looked in the archives to see what the situation was like then. scope_creepTalk16:05, 29 September 2024 (UTC)[reply]
"Trust me, I was there" is not evidence. Your comment assumes bad faith from those disagreeing with you, and of everybody submitting new articles. Not every editor is paid (and disclosed paid editing is explicitly allowed), not every paid edit (disclosed or otherwise) is bad, not every paid editor (disclosed or otherwise) is attempting to harm the encyclopaedia, not every paid edit (even undisclosed ones) does harm the encyclopaedia. Thryduulf (talk) 16:19, 29 September 2024 (UTC)[reply]
That is true to certain extent, but the majority of editors who create modern biographical, organisational and product articles which make up the majority are undeclared paid editors. They do not have our best interests at heart and never have done. scope_creepTalk16:53, 29 September 2024 (UTC)[reply]
Even if that is true (and you haven't provided any evidence, of either your assertion or the implications of it that these articles harm Wikipedia and/or that draftification as currently implemented and practice prevents that harm), that doesn't mean that draftification as implemented currently can't be improved and that any changes to the status quo will mean the death of Wikipedia. Thryduulf (talk) 17:02, 29 September 2024 (UTC)[reply]
If drafts get deleted, that's because their creators have abandoned them. That's what G13 is. Perhaps more effort should be spent encouraging article writers to improve their articles after they got moved to draft (where they can be improved without interference), but draftification is not deliberate, malicious backdoor deletion, and I resent it being characterized as such. Cremastra (talk) 19:47, 29 September 2024 (UTC)[reply]
Is this a Double-barreled question? The comment you're replying to said only "route to deletion", and you've turned it into four separate parts:
deliberate
malicious
backdoor
deletion.
I wouldn't personally characterize any of them as malicious, but I think a fraction of them are deliberate. IMO claiming that nobody ever sent a borderline subject to AFC instead of AFD (which has lower standards in practice) would be rather extraordinary. I frankly don't think we're all so stupid that we can't figure out which route is most likely to end up with the result we prefer.
If we characterize AFD as the "front door" for deletion, then it seems fair to describe letting articles expire in the Draft: space as the "back door".
But the original comment is merely that it's not a route to deletion. But if 90–95% all of the articles put on that path actually do end up getting deleted, then is it not basically fair to say that it is one of our routes to deletion? WhatamIdoing (talk) 20:22, 29 September 2024 (UTC)[reply]
Oppose. The current verbiage of the tag makes it clear to anyone with a lick of common sense, that the article has potential, but in its current form it is not ready for mainspace. Some of the comments here from folks clearly indicate a lack of understanding of what the draftification process is for. If an article, in its current form, passes GNG, then there are only certain circumstances where it should be draftified (e.g. paid editing), but if an article probably would pass GNG, but does not in its current form (e.g. there are not enough in-depth sources from independent, reliable sources to meet the standard), than that is a poster child for draftification. When I was more active in reviewing articles, I created several custom responses, which took the standard message and massaged it a bit depending on the reason for draftification (e.g. UPE, lack of GNG) or a specific topic (e.g. NFOOTY, Populated places). In some instances those messages contained an offer to ping me directly when they felt the article was ready for mainspace. I am all for article creation, but I also care about the quality and reputation of Wikipedia, which is often seen as the punchline for jokes regarding garbage information on the internet. And I would completely disagree with those who say that draftification is not a net benefit. In fact, I think it is one of the most useful tools to helping improve the quality on WP. Is it always used correctly? No. But that's an education problem with individual users, not an overriding issue with the process itself.Onel5969TT me14:34, 29 September 2024 (UTC)[reply]
That might be fine in theory, but it doesn't match the what is happening in practice. Especially given that articles are being moved to draftspace for not being of sufficient quality that are C or even B class. If an article is neutrally written and meets the GNG then there is no justification for moving it to draftspace just because someone might (or might not) have been paid to edit it. Thryduulf (talk) 15:21, 29 September 2024 (UTC)[reply]
Draft:Kian Breckin (footballer) – 316 words, 15 refs (moved by the author with no reason given, but it was deleted at AFD last year)
I have skipped redirects, some round-robin page swaps, and a couple of editors moving AFC submissions from User: space to the Draft: space, and tried to include only articles being moved from the mainspace to the Draft: space. I can't get the ORES ratings for these articles, but at a glance, I think that Start and C-class is not an unreasonable description. WhatamIdoing (talk) 19:31, 29 September 2024 (UTC)[reply]
First, thanks for providing the list. The issue is, in reviewing those drafts, most are solid drafts, and not " Especially given that articles are being moved to draftspace for not being of sufficient quality that are C or even B class." Although I think a more careful explanation could have been made. For example, the first one would have been better with a "more in-depth references from independent, reliable sources" needed, rather than simply saying "more sources needed", as there isn't a single, in-depth reference from an independent, reliable source in the draft. The second and third examples are the exact same issue. The 4th and 5th examples are properly labeled as covert advertising (both editors have been blocked for it - in addition, the 4th one didn't have a single in-depth reference from an independent source, either). The 6th example, while having 3 sources, none are in-depth, and while it might be a spelling difference on the translations of the 2nd and 3rd refs, it does not appear that the article's subject is mentioned in any of them. The 7th article is not a true example of draftification, as it was moved by the author. The 8th and 9th article have zero independent reliable sources (for the 9th, the newspaper referenced does not have a page number, and the link does not appear to bring up anything in depth about the hack lab). Not sure about the 10th, for the history is a bit wacky, but again, does not look like an example of draftification.
I think this illustrates some of the misunderstanding that folks who don't like draftification make. You look at the list provided, and you go, wow, lots of references, most not stubs or micro-stubs, why in the hell were they draftified? Hell, I did that myself, wondering if all 10 were done by a single editor, who perhaps did not have a firm grasp of draftification. But then you dive into the merits of the sourcing, or the upe issues, and it appears all 8 of the draftifications appear justified.Onel5969TT me20:32, 29 September 2024 (UTC)[reply]
@Onel5969, I wonder if you could explain "the newspaper" in the 9th article a little better. You say that the article has "zero independent reliable sources", but traditional print newspapers are independent reliable sources. Then you say it doesn't have a page number, but the link takes you directly to a scanned copy of the correct page; the cited article [title given in the citation] is in the last two columns. None of that makes the newspaper less independent. Is your concern that the article appears to predate the use of the name in the article title ("De Zanbak" means "The Sandbox")? WhatamIdoing (talk) 20:51, 29 September 2024 (UTC)[reply]
Could be the translation, but there does not appear to be anything connecting the group mentioned in that article, with De Zanbak. But even if there is, agf, that still is the only in-depth independent source. Onel5969TT me01:15, 30 September 2024 (UTC)[reply]
If a new editor includes 5 sources in their submission and it gets moved to [somewhere I didn't put it] because "more sources needed" or "no sources" how many of them are going to take the time to learn that the experienced editor actually meant none of these sources contain what I think is significant, in-depth coverage in independent reliable sources and then have the confidence to say "actually, this experienced person with the power to remove my article from Wikipedia is wrong and I'm right, I'll learn how to challenge them and how and where to express my view in a way that the powerful people will listen to me" rather than just give up at some point along that path? And before anyone says it, no, just because a few bad faith editors might be among the dissuaded does not justify the loss of good faith editors. Thryduulf (talk) 21:29, 29 September 2024 (UTC)[reply]
I guess that's the difference between editors who care about quality on WP, and those who care about quantity. But that's why I said that the rationale given could have been better. Onel5969TT me01:17, 30 September 2024 (UTC)[reply]
Is it really a quality vs quantity question?
Or is this the difference between editors who would rather see a page run through Wikipedia:Articles for deletion or Wikipedia:Proposed article mergers instead of being unilaterally hidden until it gets deleted without the level of community oversight that we expect from AFD? For example, I'm not convinced that "De Zanbak" is a viable subject for an article, but I think there are several ways that we could address that concern, and I don't see the Draft: space helping. In fact, the only thing that moving that page to the Draft: space does that's different from moving that page to the User: space is: It's far more likely to get deleted during the next year if it's in Draft: space than if it's in User: space. WhatamIdoing (talk) 01:26, 30 September 2024 (UTC)[reply]
Well, since draftification isn't a "backdoor to deletion", nor is it "hiding an article", it's definitely a question of quality vs. quantity. Draftification, in short, is a quality control measure. These are articles that might be notable enough for mainspace, but simply aren't in good enough shape to be there. But, like other vehicles in WP, good faith editors might disagree on an article's notability, so for example in the De Zandbak articlem, Jay8g (who tagged it for notability), and Jonathan Deamer (who draftified it) might deem it potentially notable, while you, WhatamIdoing, might have simply sent it to AfD, because you do not feel it notable. But that doesn't mean the system isn't working. Perhaps we can tweak the current verbiage in the template to include where resources about where an editor can reach out for help might be added (e.g. AFC or Teahouse)?Onel5969TT me09:20, 30 September 2024 (UTC)[reply]
Well, since draftification isn't a "backdoor to deletion", nor is it "hiding an article", you say that as if there is no possible way good faith editors could disagree, but that simply isn't true. Whether either of those things is true is a matter of opinion (and, in my opinion, one that is consistent with the evidence presented). Thryduulf (talk) 10:07, 30 September 2024 (UTC)[reply]
Hi. No, editors can certainly have different interpretations and disagree on issues. However, in this instance, it is not a matter of disagreement. In order to hold those views indicates a lack of understanding of what the draftification process is. That's not what draftification is, it is, as I've said, simply a quality control measure. It would be like saying, it's a matter of opinion whether or not this person wrote an article about themselves, that can be interpreted as not being COI editing. Of if a an article simply cut and paste the info from Encyclopedia Brittanica, you cannot say it's your opinion that that isn't a copyvio. I mean, I have the utmost respect for you, Thryduulf, and you do a great job on WP. There are things on WP which are subjective (e.g. exactly what constitutes SIGCOV), while others are objective, (e.g. UPE/COI editing, copyvio). What draftification is falls into the latter category. All that being said, we can disagree on whether or not an individual article should or should not have been draftified. You say the evidence presented shows that it was not warranted that those articles be sent to draft. Going through the sources, however, it looks like draftification was justified. That is a difference of opinion. Onel5969TT me14:20, 30 September 2024 (UTC)[reply]
It's your opinion that moving an article to the Draft: space is simply a quality control measure.
It's my opinion that moving an article to the Draft: space is also simply a quality control measure that, compared to the available alternatives of leaving it in the mainspace, sending it to AFD, or moving it to User: space, substantially decreases the likelihood of the quality being improved and substantially increases the likelihood of the article being deleted.
Oh, right: Those last two points ("substantially decreases the likelihood of the quality being improved" and "substantially increases the likelihood of the article being deleted") aren't "opinions". They're objective facts. WhatamIdoing (talk) 22:17, 30 September 2024 (UTC)[reply]
Rhodesia Railways 19th class is not a list; it's a train that was in operation for multiple ranges of time. Even if it were a list, the empty headings and only content being a table is nowhere near start-class, maybe even substub. Aaron Liu (talk) 20:47, 29 September 2024 (UTC)[reply]
only content being a table have you actually read the page? That infobox is full of content, there are two apparently reliable sources and the table itself has about 20 rows of content. Thryduulf (talk) 21:33, 29 September 2024 (UTC)[reply]
This is just an idea, and I want to workshop this a bit more, but I think it would be helpful to have pending changes at the extended confirmed level. This could be called "PC2" again (not to be confused with the original PC2) or "PCECP". The idea would be to help enforce WP:ARBECR and similar restrictions where non-extended confirmed users are prohibited from certain topic areas. Under this level, edits by non-extended-confirmed editors would be held for review, while extended confirmed users can approve these edits and thus take responsibility under WP:PROXYING.
I think it would be helpful for pages where (1) parts of the article intersect with a contentious topic, or (2) the article in its entirety intersects with a contentious topic, but not edited frequently. AwesomeAasim16:54, 27 September 2024 (UTC)[reply]
This seems like it could be useful. It would have to be restricted to infrequently edited pages (likely excluding all current events articles) so as not to overwhelm Pending Changes every time Reuters publishes a new story or an edit war erupts. The big question is: what problem are you trying to solve? Toadspike[Talk]20:39, 27 September 2024 (UTC)[reply]
There are some contentious topics designated either by ArbCom or the community where only extended confirmed users are allowed to participate. However, admins refuse to protect pages where there isn't enough disruption to justify protection. Although, it should be considered that the XCON restriction applies regardless of whether a page is protected or not.
What PCECP would do is essentially remove fears that there "isn't enough disruption to justify protection" while buffering all non-extended-confirmed contributions so they have to be approved, in line with "non-extended-confirmed can only make edit requests". Templates that are specifically for this case like {{edit protected}} break when the page is not protected. AwesomeAasim22:00, 27 September 2024 (UTC)[reply]
The problem with that is that the 500/30 rule is specifically designed to keep newer editors out due to extreme amounts of disruption as a rule. There's a good reason why both of the world's main hot wars (the Arab-Israeli conflict and the Russo-Ukrainian war) are under 500/30. And, as has been brought up repeatedly and bears repeating again, high volumes of edits on a given article contraindicate CRASHlock.
But the biggest stumbling block here is that no consensus exists yet for an extended-confirmed CRASHlock. The last discussion about expanding CRASHlock to higher protection levels predates XCP entirely. There would need to be a formal RfC for this, not VP spitballing. —Jéské Courianov^_^vthreadscritiques15:37, 28 September 2024 (UTC)[reply]
XCON protection makes sense for high traffic articles, but low traffic articles? If the edit is minor such as fixing spelling mistakes or grammatical errors, there should be no problem. Fixing spelling and grammar is generally outside of contentious topic areas anyway. From WP:ARBECR: On any page where the restriction is not enforced through extended confirmed protection, this restriction may be enforced by other methods, including ... the use of pending changes.
I probably would set up abuse filters as well to see if a page is in a category that primarily deals with a contentious topic, and then warn and tag the edit in question. AwesomeAasim16:22, 28 September 2024 (UTC)[reply]
Most low-traffic CT articles don't have any protection since they never saw amounts of vandalism necessitating protection. Protection requests that solely rely on arb enforcement and little to no evidence of vandalism get declined. Aaron Liu (talk) 23:26, 28 September 2024 (UTC)[reply]
Yeah I see that, but the problem is that a non-XCON edit will get approved on pages that not many people are watching. Pending changes still allows non-XCON users to make these edits, but their edits will need to be approved and they can be reverted if in violation of WP:ARBECR. This is also in line with how pending changes is used on low-traffic articles to monitor (not prevent) disruption. AwesomeAasim18:26, 29 September 2024 (UTC)[reply]
@Aaron LiuMost low-traffic CT articles don't have any protection since they never saw amounts of vandalism necessitating protection. Protection requests that solely rely on arb enforcement and little to no evidence of vandalism get declined. Untrue, articles in ECR topics can and are pre-emptively locked. What actually happens is that articles with minimal disruption are usually not brought to WP:RFPP or noticed by a wayward admin. Mach6119:53, 29 September 2024 (UTC)[reply]
Untrue, articles in ECR topics can and are pre-emptively locked.
Seems reasonable. I've always wondered why pending changes isn't deployed more often. It seems a useful tool, and there are lots of pending changes reviewers so very little backlog Cremastra (talk) 14:18, 28 September 2024 (UTC)[reply]
Still not seeing it. People supposedly mistrust it because there was a trial 14 years ago and enwiki admins didn't immediately stop using it after the trial period pending a consensus on the future of the feature? Anomie⚔18:43, 9 October 2024 (UTC)[reply]
The TL;DR I'm taking away from this discussion is that you're still butthurt over consensus not going your way 12 or 13 years ago, and assuming that anyone opposed to PC shares that reason and no other. I think it's unlikely continuing this conversation is going to go anywhere useful. Anomie⚔18:59, 9 October 2024 (UTC)[reply]
That isn't how consensus works, either. Consensus can be determined by an RfC, yes. But it can also develop just by the way that things are done already, regardless of whether it has formally discussed.
I think about the example given by Technology Connections about "the danger of but sometimes". The LED traffic light is superior in energy savings and much more, but sometimes snow and ice builds up on them, so they are bad. Likewise, XCON pending changes will help with enforcement of WP:ARBECR but sometimes admins might apply this to pages out of policy, so it shouldn't be used again. The correct response would be to place in policy guardrails so that admins don't do that. AwesomeAasim19:00, 9 October 2024 (UTC)[reply]
How is an RfC from over 13 years ago still reflective of consensus today? I am pretty certain that while some opinions might not have changed, others definitely will have. No one is saying there should be full pending changes. AwesomeAasim18:16, 9 October 2024 (UTC)[reply]
I guess you might be the only one using this terminology; as it is not in WP:GLOSSARY or anywhere else.
Nonetheless, this is the Idea Lab; it is the place to develop ideas, not to show stark opposition to ideas. That is what the other discussion boards are for; consensus polling. It should be noted that WP:ECP was created originally for the purpose of enforcing arbitration decisions and community sanctions. It was never intended for anything else; it just got used for other stuff de facto. AwesomeAasim18:40, 9 October 2024 (UTC)[reply]
(edit conflict) All these things you think are obvious really are not. You should try explaining yourself better instead of emphatically waving your hands at something random. Anomie⚔18:43, 9 October 2024 (UTC)[reply]
Obvious perhaps, but it still doesn't make much sense. I'm not sure how using your own special terms of unclear implications to disparage things you dislike is helping communication or community understanding here. Cremastra (talk) 19:37, 9 October 2024 (UTC)[reply]
I don't understand. People mistrust PC because of a bureaucratic misimplementation of an experiment over 10 years ago? (In a noncentralized bureaucracy where dumb shit happens all the time?) The RfC is explicit that it makes no normative judgement on PC, and it seems the !voters are not doing so either. SamuelRiv (talk) 18:37, 9 October 2024 (UTC)[reply]
It's worth noting that the 2017 RfC is the last one about any aspect of CRASHlock, to my knowledge. As I said above, there would need to be a new RfC in order to get consensus for extended-confirmed CRASHlock, as PC2 was originally full-protection level and no ECP!CRASHlock question was asked in the2016RfCs, none of which were particularly comprehensive. (The last comprehensive RfC was the 2014 clusterfuck.) —Jéské Courianov^_^vthreadscritiques06:47, 10 October 2024 (UTC)[reply]
I think the main reasons editors don't want to expand the use of pending changes are practical: no technical support for fixes (or additional feature development) is on the horizon, in spite of documented bugs; and uncertainty in the community's ability to manage expanded use. There are certainly vocal editors who are wary due to past history, but this has already been a factor in other decisions, and they have accordingly been influenced to be more definitive about how any trials will proceed. isaacl (talk) 18:55, 9 October 2024 (UTC)[reply]
Ok so there's a lot of history here as you are already seeing above, and no one's even gotten to discussing Phillipe's little misadventure yet. Despite all that I actually think the general idea here is sound. And since we are discussing history its worth pointing out that as a practical matter this is actually closer to what the EC restriction was intended to do in its earliest incarnation where it functioned as a softer version of 1RR originally enforced as a bespoke AE remedy on one specific article reverts of non-qualifying accounts did not count towards 1RR.
Times have changed, ECR now tends to be enforced in mainspace with ECP and is applied far more broadly than anyone from then would have envisioned, for better and for worse.
The best use case here is for quiet pages where the history of non-EC editing is largely one of minor non-contentious fixes and improvements, but have caught attention due to sporadic contentious edits, where it can offer a middle way between leaving enforcement to post-edit reverts and preventing all non-EC editing.
As a practical matter the limitations of the extension mean that it really only works-well on low-traffic pages and realistically improvements to the extension aren't coming anytime soon. So use case (2) makes sense, but (1) is a harder sell. Might not be enough of a use case to justify the hassle. Personally I'd have to do some research and think about this a little but the basic idea is sound.
A multi-part RfC asking how ECR should be enforced for existing pages, including based on activity. High traffic pages will need extended protection retroactively as those tend to get the most disruption from ECR violations. Low-traffic pages, not so much, but we can use abuse filters and workshop ECP pending changes for this. Spelling and grammar fixes as far as I am aware are excluded from WP:ARBECR. AwesomeAasim19:52, 1 October 2024 (UTC)[reply]
Sounds good - but bear in mind we are discussing CRASHlock (which would require developer buy-in to make XC happen) and an Arbitration policy (which ArbCom may short-circuit). Also note that there would likely need to be a separate RfC consensus to allow XC CRASHlock in the first place; like I said above we haven't had a comprehensive discussion about it since 2014. —Jéské Courianov^_^vthreadscritiques16:26, 26 October 2024 (UTC)[reply]
@Jéské Couriano, I do wish you would quit using that made-up word. WP:PC is shorter to type, and when editors use the same words for the same thing, then we're less likely to end up with avoidable confusion ("CRASHlock sounds really bad, but I'm just asking for WP:PC"). WhatamIdoing (talk) 00:26, 27 October 2024 (UTC)[reply]
WP:ARBECR can first just be XCON PC. After extensive edits by non-EC, piling on to PC backlog, then it can just be upgraded to normal XCON. If the disruption is already severe before being brought to RFPP or other venue, then XCON protection can just be the first action. ~/Bunnypranav:<ping>13:05, 28 October 2024 (UTC)[reply]
@Jéské Couriano the discussions that you linked are from 2016, so we cannot assume the consensus has not changed. Also, I believe that this is a platform for building ideas and new proposals, hoping to bring them to reality while abiding by consensus. ~/Bunnypranav:<ping>15:28, 30 October 2024 (UTC)[reply]
On another thought I am actually wondering if we can just have a two-part RfC as to whether to turn on this feature I discuss. Part 1 would just be about PCECP and part 2 would be just about replacing ECP with PCECP on low-traffic WP:ARBECR and related articles. AwesomeAasim16:41, 30 October 2024 (UTC)[reply]
That makes sense, but the second RfC might fail, as it one would have to discuss page wise about the change in protection. Also proving that PCECP is enough for said pages will be complicated, and also have to think about the storming of backlog in PC if it is not enough. ~/Bunnypranav:<ping>16:45, 30 October 2024 (UTC)[reply]
I think that the Wikipedia main page would be more educative and with a section riddles, proverbs, idioms, wise saying. You know, a collection from many languages around, their origins, past meanings, reforms, present meanings, examples of their usage in history (past & present), their literal meanings, word for word rendering in english, etc. I don't know, who has better ideas? Let Wikipedia be a fun place too for visitors and readers to always learn more. I'm looking forward to seeing this by the start of next year and in other language wikis. Any and all contributions are accepted. elias_fdafs (talk) 20:02, 13 October 2024 (UTC)[reply]
The thing is, one person's "wise saying" is another person's "deepity". I don't think having these on the Main Page, especially in a dedicated section, would actually be very encyclopedic. However, like Folly Mox says, a more general concept of showcasing sister project content (a word etymology, a quote, etc.) could be interesting! Chaotic Enby (talk · contribs) 21:03, 13 October 2024 (UTC)[reply]
The problem with idioms and proverbs is that, usually, they are regional. They are widely used at some area, but hardly mentioned or even unknown in others. For each user that see such a section and says "oh, that's the origin of that proverb" we'll have several who will say "what, was that a proverb? Never heard about it". Besides, explaining their background is just impossible with the limited text in main page boxes. Perhaps DYK may be a better venue to show those articles in the main page. Cambalachero (talk) 13:18, 15 October 2024 (UTC)[reply]
I know that editors should seek to remain unbiased, but it seems on divisive topics we can end up with one side who manages to tilt the article toward their POV. We can then end up with half of the editors saying "This article is perfectly fine" and the other half of the editors saying "There are big POV issues, here they are..."
The side who are happy with the bias can actively work to prevent any fixes to the page to address the bias, while simultaneously blocking the addition of a NPOV tag to the page.
It seems that if half of the editors are saying "it's fine" and the other half are saying "there are big issues" this is extremely indicative of a POV problem even if there is not consensus that one exists.
So I'm wondering if there should be an exemption to the Consensus Required Restriction and if some sort of critical mass short of consensus should be enough to allow for NPOV tag.
Putting the {{POV}} should never be an end goal. The goal should be to fix the problem, and adding the banner frequently provides no practical benefit at all. Imagine a wildly non-neutral article about an article under the Wikipedia:Consensus required restriction. Maybe it's an article called 2+2. The article says that 2+2 is generally understood to equal four, but there is a significant minority of respectable mathematicians says that 2+2=5. Here's the story you seem to want:
The discussion on the talk page about the tag ends in a stalemate. Because of the 'consensus required' rules, the tag would normally not be added, but because of the newly carved-out exception, the tag can be added.
End result: The article is tagged, but it's still wildly unbalanced.
The discussion on the talk page about the tag ends in a stalemate. Because of the 'consensus required' rules, the tag is not added.
Alice decides to quit worrying about the tag and start worrying about the content of the article. The regulars on the talk page can't reach a satisfactory agreement, so she takes the dispute to a relevant noticeboard or starts an RFC.
Remember: Maintenance tags are not badges of shame. They do not exist to 'warn the reader' or to formally express your disagreement with the article. They exist in a (mostly vain) hope that editors will fix the article's content. If you can fix the article's content without a tag, then everyone wins. If you can't fix an article (tagged or otherwise), then read up on Wikipedia:Dispute resolution. WhatamIdoing (talk) 19:05, 22 October 2024 (UTC)[reply]
Depends… how many are on each “side” of the debate?
If there are multiple editors on each “side”, then I don’t think we can say that a consensus actually exists (in either direction). However, if it’s just one or two disgruntled editors against many, then we can say there is consensus, and that consensus does not require unanimity. Blueboar (talk) 19:08, 22 October 2024 (UTC)[reply]
Describing Notability in plain English
The name we use for Wikipedia:Notability has long been a source of confusion. People can guess the basic concept of many policies and guidelines from the plain-English meaning of the title (e.g., Wikipedia:Reliable sources are sources you rely on; Wikipedia:Copyright violations is about violations of copyright etc.), but this one has quite a different meaning. You can have several sources that directly say ____ is a notable musician, and we'll reply that he's not WP:Notable.
I'd like to brainstorm some alternative phrases that could be used instead of "notability", or as a supplement to it, that would be less confusing to people unfamiliar with our internal jargon.
Abbreviation found in comments at Wikipedia:Articles for deletion and in edit summaries, indicating that the article's subject is not notable enough for a Wikipedia entry. A subject is non-notable if editors agree not to have an article about this subject. Their decision is usually based on things like not finding enough reliable sources to write a decent encyclopedia article, but it can also be based on things like a desire to present a small subject as part of a larger one.
A characteristic held by article subjects that qualify for separate, stand-alone articles. A notable topic is one that "is suitable for a stand-alone article or list when it has received significant coverage in reliable sources that are independent of the subject." Note that "notability" is a property of a topic, and has nothing to do with the quality of an article, or whether an article exists for the topic.
Words for the concept: criteria, concept, test, quality, qualities, requirements, notedness, guideline, threshold, when to create an article
Words for the result: separate article, stand-alone article, separate page, stand-alone topic, new topic, own page, article creation, article suitability, inclusion
Some specific ideas:
Collapsed list of prior ideas
The following discussion has been closed. Please do not modify it.
Article concept guideline
Article creation criteria
Article creation guideline
Article sourcing test
Article suitability criteria
Article test guideline
Article threshold
Criteria for article creation
Guide to which topics should be included as articles on Wikipedia
Guideline for when a topic should have its own article
Inclusion criteria
Is the subject written about in reliable sources?
New topic test
Notedness
Own page threshold test
Page sourcing guide
Primary notability criterion
Qualifying for a separate article
Separate article criteria
Source availability
Source depth
Stand-alone concept
Stand-alone article criteria
Stand-alone topic criteria
Stand-alone topic criterion #1 (#2, #3, etc.)
When to create an article
Feel free to expand the box if you want to see some of the prior ideas. It's collapsed because some research on brainstorming ideas suggests that looking at other people's ideas can reduce the total number of ideas shared. Duplicates are fine!
I had also been thinking about this. The core issue, in my opinion, is that we're trying to describe as "notability" something that is closer to "for someone/something to have an article, they should be well-documented in reliable sources". At its core, the term "notability" carries more of a connotation of relative importance, leading to a lot of newcomers, and sometimes even other users, being misled as to what makes a topic notable. On the other hand, the actual guidelines describing it focus on the existence of reliable sources about the topic, with importance only being used by some guidelines as a proxy for these sources being likely to exist.A word like well-sourced or well-documented would carry this idea better, without the a priori of "importance/fame is what matters" that "notability" carries. Chaotic Enby (talk · contribs) 21:13, 22 October 2024 (UTC)[reply]
Lots of topics are documented by primarily primary sources (eg like many news event), but we require coverage by secondary sources, so those would worsen the situation. — Masem (t) 21:20, 22 October 2024 (UTC)[reply]
Good point, although it could still be a first start, and no word can fully convey our notability guidelines either. Maybe encyclopedically sourced could help convey the fact that not any source works? Or, as you employ the term "coverage", we could make the difference between (primary) documentation and (secondary) coverage and call it well-covered? Chaotic Enby (talk · contribs) 21:27, 22 October 2024 (UTC)[reply]
Chaotic Enby: I am still chewing over all this. I fear that encyclopedically sourced could be easily misunderstood and potentially lead to more newbies trying to cite Wikipedia itself. I really don't have a sense of how well people outside Wikipedia and academia understand the distinctions between primary, secondary, and tertiary sources. I think well-covered does capture the essence of what we're trying to convey without causing more confusion. — ClaudineChionh (she/her · talk · contribs · email) 23:42, 22 October 2024 (UTC)[reply]
I'd say that people outside the wiki-verse and academia understand primary/secondary/tertiary "not at all", and I'd say that people in the wiki-verse understand the distinction "poorly". Editors struggle with WP:PRIMARYNEWS, especially when it comes to the question of notability ("But event is obviously important, so obviously this breaking news article is secondary"), and most of them could not explain why Wikipedia:Secondary does not mean independent. WhatamIdoing (talk) 00:17, 23 October 2024 (UTC)[reply]
Masem, the GNG requires secondary sources, but NPROF does not. Both are still wiki-notable. We therefore need a handle for this concept that does not assume the GNG approach. WhatamIdoing (talk) 00:13, 23 October 2024 (UTC)[reply]
I caution against this because as it is used now, notability is not used as a check at new page review, and primarily is a method used for evaluating whether to delete an article at AFD. We should have an advice page with that title about how to make sure you have a good topic and reviewing the notability of the topic is a good starting point as part of it. — Masem (t) 21:35, 22 October 2024 (UTC)[reply]
A nod to WP:Structurism as an existing concept. Also a hint that newcomers should add content to existing article, and no be trying to add a new orphan topic as their first contribution.
I'm inclined to something like "stand-alone topic criteria" (to clarify that the point is determining whether a topic warrants a stand-alone article) or, in a similar vein, "when to create an article" (or possibly "when it can be appropriate to create an article", since in occasional cases it can be appropriate to cover a small number of closely related topics that could be notable in the same article rather than separately). I do agree with the notion that notability isn't the best name for this guideline and that having a term that's more like plain English. Hydrangeans (she/her | talk | edits) 21:26, 22 October 2024 (UTC)[reply]
Maybe something like suitable topics or suitable article topics would work. That implies the existence of editorial judgement and that some topics simply aren't suitable. User:Chaotic Enby, this was inspired by your idea of "well-sourced", which has the potential to be confused with well-cited (i.e., the number of refs in the article right now, rather than the number of sources in the real world). WhatamIdoing (talk) 00:21, 23 October 2024 (UTC)[reply]
From all the suggestions so far, this seems the most understandable so far. It's short, it communicates that some things are excluded and that there is 'judgement' involved. —TheDJ (talk • contribs) 09:46, 23 October 2024 (UTC)[reply]
I really like this, because (1) it removes the emotional pain of being deemed "not notable", and (2) it avoids the confusion we currently have of subjects that are notable but about which we cannot have a meaningful article. To clarify: (1) AfD and Teahouse waste a lot of time trying to explain to upset people that Wikipedian notability has nothing to do with importance, creativity, or future value to humanity. We could save a lot of trouble by focusing on the objective need for sources rather than the subjective view of importance. (2) Notability is currently only half of the two tests we need to pass: We can't have an article unless the subject is notable and someone's written something about it for us to summarise. We have a lot of guidelines that say "XXX is generally considered notable", which result in unexpandable stubs because although it can be demonstrated from primary sources that two old ladies and a chicken once lived near a railway siding in Ohio (making it a genuine inhabited settlement), there is now nothing there, and no one has ever written anything about it, or ever will. Focusing on what is necessary to create an article would cut to what actually matters, practically, rather than getting tied up in legalistic debates about what constitutes a notable thing. Elemimele (talk) 16:14, 23 October 2024 (UTC)[reply]
But all too often, we get the argument that we should have an article on XXX because sources exist, even though no one has demonstrated the existence of such sources. Attempts to add the requirement that reliable sources must be cited to create or keep an article have been repeatedly rejected. I would support replacing "notability" with something like "specific topics are suitable for articles if they are well-sourced, NPOV, and meet certain broad topic requirements (i.e., replacements for SNGs)". Donald Albury17:32, 23 October 2024 (UTC)[reply]
@Donald Albury, do you mean that topics are suitable/notable if they're neutral, or do you mean that articles are suitable/notable if they're neutral? I'm not sure if you mean that you want to repeal WP:NRVE and expand the deletion policy to say that a (deserved) {{POV}} tag is grounds for deletion, or if you mean that citing sources in a neutrally written article must be possible, even if it hasn't happened yet (including for many years). WhatamIdoing (talk) 17:44, 23 October 2024 (UTC)[reply]
I was just trying to express that availability of reliable sources is required, but not sufficient, and that other policies and guidelines also must be met for an article to be suitable for inclusion in WP. Donald Albury18:30, 23 October 2024 (UTC)[reply]
I do like suitable much better than notable (and came here to suggest it). It's more accurate, but still gives some flexibility in definition, where something like well documented might be open to misinterpretation / lawyering. Folly Mox (talk) 17:50, 23 October 2024 (UTC)[reply]
@Seraphimblade also deserves credit for this idea, since a comment from him is the source of "article suitability" in the list above.
I'm leaning a bit towards "topics" (or "subjects"?), because "articles" could be argued to exclude lists, and because of the endless problem of "it's not notable because the article's quality is currently too low". WhatamIdoing (talk) 02:13, 24 October 2024 (UTC)[reply]
I like that a lot. On Wikipedia, a suitable topic for an article is one where either sufficient reliable, independent sources can be found or which meets the criteria outlined in a subject-specific suitability guideline (SSG)... – sounds both more understandable and closer to how we actually decide whether or not to keep articles, in practice. – Joe (talk) 08:02, 25 October 2024 (UTC)[reply]
Just to throw out an idea that I think can minimize disruption, is to consider a comparable situation to the relatively recent rename of of the old Naming Convention page to WP:Article Titles while specific advice of naming for various fields are still at "Naming Convention". In that same vein, if the GNG was moved to its own page (thus sitting alongside the sepearate SNG pages) and what's left at WP:N left there, then renaming that leftover to some of the suggestions above would still allow us to keep the principle of notability via the GNG and SNG while having a better landing page at a more familiar term and to explain the GNG and SNG functions within that. It would minimize a mass edit on p&g pages. The GNG and SNGs can be described as tests used on Wikipedia to measure how notable (real world definition) a topic is within the suitability on an encyclopedia. Masem (t) 18:11, 23 October 2024 (UTC)[reply]
Well, in terms of providing g a word that is closer to the real definition for our practice related to when a topic is suitable for it's own article, treating the existing idea of notability through the GNG and SNGs as is and focusing on a clear word for the broad concept is a clean solution. Masem (t) 19:39, 23 October 2024 (UTC)[reply]
The issue is that GNG is about how well-documented the topic is in independent secondary sources, which doesn't necessarily map to real-world notability, and using the latter word for it has been just as much source of confusion. Chaotic Enby (talk · contribs) 19:45, 23 October 2024 (UTC)[reply]
We can frame the GNG and SNGs as semi objective, source based tests to evaluate real-world notability, and establih in the top level guideline that one reason to allow a topic to have an article is via demonstrating real world notability using the GNG and SNGs tests. That moves us away from having notability take the wiki definition. We still need a clear understandable title for the top level guideline, and that would also discuss more that the GNG and SNGs, such as the current NLIST advice. — Masem (t) 16:55, 24 October 2024 (UTC)[reply]
The issue is, basing article suitability on real-world notability is a very iffy definition. GNG (and to a lesser extent the SNGs) provide us with a better foundation for defining what is suitable for our encyclopedia, which is quality of independent secondary sourcing. "This person is important" is ultimately a less relevant criterion than "this person has enough secondary sources to write an article about them", if our goal is to write an encyclopedia (tertiary source, i.e. relying on secondary sourcing). Chaotic Enby (talk · contribs) 17:02, 24 October 2024 (UTC)[reply]
Consider that several of the SNG do give measure of real world notability based on claims of importance which can be given by a single reliable primary source, the expectation they can be expanded. The key is that with a tiny bit of rewording of the GNG and SNGs are set as the evaluation of real world notability with the expectation of sourcing and coverage required for an encyclopedia, either which establishes one way a topic is suitable for a stand alone article. Masem (t) 17:35, 24 October 2024 (UTC)[reply]
The reality is that wp:notability is the operative word for "allowed to have a separate article" and the talisman for the fuzzy ecosystem/process which decides that. It incorporates with wp:notability guidelines, degree of compliance with WP:not (a measure of the degree of enclyclopedicness of the article) and a bit of influences from real world notability/importance. Any term needs to acknowledge this. If one tries to base it on summarizing just what the wp:notability guidelines say, IMO it won't work. Sincerely, North8000 (talk) 02:00, 24 October 2024 (UTC)[reply]
Yes. And the strongest consideration in it would be wp:notability per the notability guidelines, but the above other factors described above are also a part of that consideration. North8000 (talk) 15:31, 24 October 2024 (UTC)[reply]
I prefer to see a more obvious name for the guideline for article creation. Something such as like "Guideline for article creation" would be more obvious. TFD (talk) 16:21, 24 October 2024 (UTC)[reply]
Agree. My point was agreeing with the structure/content. If we want this to have legs, we'll need something with an even shorter with a good acronym for it. North8000 (talk) 17:08, 24 October 2024 (UTC)[reply]
Procedural request I don't mean to gum up the process. But there's a risk of having 100 different ideas from 99 different editors, which can make it difficult to reach a consensus. Whenever this brainstorming step is over, I want to recommend compiling them into a list, sorted by some type of subcategory. That way we can slowly funnel our way towards something that can earn a consensus. I believe you'd probably find (at least) three or four types of names:
Non-descriptive (compare WP:NOT or WP:SIZE): inclusion criteria, inclusion test, article creation threshold, etc.
Type of outcome (compare WP:DISAMBIG or WP:STANDALONELIST): separate article, stand-alone article, separate page
Standard of sources (compare WP:RELIABLE or WP:VERIFIABLE): independent sources, third party sources
Standard of coverage (compare WP:OR or WP:COPYRIGHT): significant coverage, minimum coverage, coverage threshold
I lean towards something more descriptive, because "inclusion criteria" just shifts the complaints from "Wikipedia has an arbitrary definition of notability!" to "Wikipedia has an arbitrary list of inclusion criteria!" Newcomers and outsiders notoriously don't read passed the headline, or even twist ambiguity in bad faith to attack Wikipedia with misinformation campaigns. It would help the project much more if the guideline title summarized an uncontroversial standard for our encyclopedia. (Currently: if no reliable, independent sources can be found on a topic, then it should not have a separate article. or A topic is presumed to be suitable for a stand-alone article or list when it has received significant coverage in reliable sources that are independent of the subject.) Shooterwalker (talk) 17:24, 24 October 2024 (UTC)[reply]
I agree that "inclusion criteria" could shift the complaints from "Wikipedia has an arbitrary definition of notability!" to "Wikipedia has an arbitrary list of inclusion criteria!" However, the current name has an additional problem, namely "I have three Wikipedia:Reliable sources that WP:Directly support a claim that this subject is 'notable', so why are you claiming that it's non-notable?" That problem would go away with a name like "inclusion criteria". WhatamIdoing (talk) 19:57, 24 October 2024 (UTC)[reply]
We do have arbitrary criteria, though. All the WP:SNGs are arbitrary. The WP:GNG is arbitrary in what it considers "significant", "reliable", and "independent". Individual decisions on articles are arbitrary in how these guidelines are interpreted and how strictly they are applied. It's better to be open about that than pretend, like too many 'notability theorists' do, that we've come up with a 350 word rubric that objectively divides all of human knowledge into worthy and unworthy. I think most people can understand that to make a large project like this manageable, you have to agree on some boundaries – and respect them, even if they don't agree with them. – Joe (talk) 08:18, 25 October 2024 (UTC)[reply]
Except we do also have rubrics, and we also have to work together, so we have found it necessary to define together. There's boundaries, you say? What are they? We have to go about answering that question together. -- Alanscottwalker (talk) 11:20, 25 October 2024 (UTC)[reply]
Yes, that's what I'm saying. WP:GNG and the WP:SNGs are the boundaries we've arrived upon. They aren't objective, they're arbitrary and subjective, but that's okay. – Joe (talk) 11:31, 25 October 2024 (UTC)[reply]
Perhaps it would be more precise to say that there is an element of arbitrariness and subjectivity to decisions, especially for borderline subjects. WhatamIdoing (talk) 16:35, 25 October 2024 (UTC)[reply]
But, they are not just arbitrary. They describe real world things (sources) and using them for coming to decision (measure), and even more importantly, the rationale for doing so (writing based on what reliable others do). Arbitrary would be no definition, no rubric at all among us. We may suck, but we don't usually just rely on throwing darts or dice to delete articles. Alanscottwalker (talk) 18:39, 25 October 2024 (UTC)[reply]
Do they really describe real-world sources? Consider "The person has had a substantial impact outside academia in their academic capacity." The basis for deciding this is: Wikipedia editors say so.
Yes, they do, those impacts are sourced, somehow -- you actually do have to prove it to each other. (Besides, you already know, this "independence" is a both matter of degree, and not strictly necessary to be in the definition for all real world sources -- and as a matter of various qualities a real world source might have, we are generally more concerned with trustworthy). Alanscottwalker (talk) 20:56, 25 October 2024 (UTC)[reply]
I've been told that the usual way of qualifying under the second one ("significant impact") is to write a book that is used in (undergraduate?) classes at multiple universities. But some classes, and some universities, appear to be more equal than others for this determination, which is arbitrary, using the definition as a decision made according to individual personal preference rather than by its intrinsic qualities.
I agree with you that supporters of these two criteria use sources whose independence can often be most politely described as a "matter of degree", and they appear to agree with you that independent sources are "not strictly necessary". (For example, I have seen sources accepted by other editors that were just a few links to class syllabi, saying that the text for the class would be Big Textbook by Alice Expert. In GNG terms, these are mere passing mentions in self-published sources, and would not be accepted for any other subject at all.) WhatamIdoing (talk) 21:36, 25 October 2024 (UTC)[reply]
I strongly disagree with the statement that the WP:GNG is arbitrary. (Or even the additional requirements of the WP:SNGs.) At worst, the application of WP:N requires some level of judgment, based on a consensus of editors applying the principle. But the evidentiary standard for writing an article is based on real, practical, and empirical experience. And it helps our project when the world understands that we write articles based on evidence. Shooterwalker (talk) 01:41, 29 October 2024 (UTC)[reply]
It's not completely random, but it is arbitrary, in the sense that nobody on the face of the earth except for English Wikipedia editors uses this definition of "notable". For example, I think virtually all people would agree that a YouTube celebrity with twenty million fans was "a famous or important person" -- it is only Wikipedians who have a secret alternate definition where it means "has had three newspaper articles written about them". jp×g🗯️12:11, 29 October 2024 (UTC)[reply]
That's a different point, and the real point of this brainstorm. Asking for sources isn't an arbitrary standard, but in hindsight, the word "notability" is an odd choice of words to describe it. Shooterwalker (talk) 22:04, 29 October 2024 (UTC)[reply]
Frankly, I think that it is an obvious error that we incorrectly refer to our guideline as "notability", and that we call things that meet this guideline "notable". It is not arbitrary -- there are rules -- but they aren't about notability. No normal speaker of the English language, when they say "notability", means what that guideline says.
If I'm going to be totally honest, it feels like -- whether designed intentionally or not -- the guideline's name is designed to make sure that newbies give invalid arguments during deletion debates, thus ensuring that their autobiographies/advertisements/etc are deleted and they are dismissed, because they stupidly assume that the word means the thing it means in 99.999% of its usage in the English language. For example, the obvious direct interpretation of "Smith is not notable" is:
The speaker's subjective opinion, which you can argue against by saying "Yes he is".
A claim that he is not very famous, which you can argue against by saying X million people listen to his podcast
A claim that he is not very successful, which you can argue against by saying he made X million dollars or has Y thousand clients or employs Z hundred people.
A claim that he is not very unique, which you can argue against by saying that he's the first X to ever Y, or the only Z who's ever Qd while Zing.
We do not accept any of these arguments. If you make any of these arguments, we sneer and ridicule you for being an idiot.
I would propose that the "notability" guideline be called something that does not, in any way, create "two-tier" sentences (e.g. ones where there's an obvious plain English interpretation, and then a second Wikipedian English interpretation where it means something else). For this reason I think stuff like "impactfulness topic criteria" might be helpful, but would not fully solve the issue, as people still know what the word "impactful" means, and would argue that things were impactful, when what we actually meant was impactful, and only a moron would think that meant impactful. It should be something that nobody would ever think to define in terms other than looking up the Wikipedia policy for it. For example: "includability" or "florfbap". jp×g🗯️12:07, 29 October 2024 (UTC)[reply]
Maybe "sourceability"? It brings the idea of having quality sources, while not being an already existing word, to make it clear that it's a unique Wikipedia concept. Chaotic Enby (talk · contribs) 16:01, 29 October 2024 (UTC)[reply]
Honest answer, you deprecate NPROF. I don't know why this one guideline has been repeatedly giving exemptions to sourcing requirements in an encyclopedia that should rely on secondary sources. Chaotic Enby (talk · contribs) 15:53, 1 November 2024 (UTC)[reply]
"Sourcability" is far too close in meaning to WP:Verifiability and implies a weaker aspect when in fact what notability currently is is more complex than just WP:V itself. (that's one reason why notability remains a guideline rather than a policy, because of how complex it is) Masem (t) 17:08, 1 November 2024 (UTC)[reply]
Binominal expression or complete sentence This is a great discussion and thank you to OP for starting it. I think all the suggestions presented so far are great, though, they each introduce some of the ambiguity that already exists with Notability. I guess my comment is that we seem to be caught up on coining an all-encapsulating single word that could replace Notability. Maybe this is a case where a binominal expression ("Nice and Plenty") or even a complete sentence would be more appropriate to communicate the complexity that WP:NOTABILITY houses? Chetsford (talk) 18:10, 1 November 2024 (UTC)[reply]
Timeline of significant figures
While many people have made contributions to history (many more than could fit in one timeline), it's undoubtable that some people's influence far exceeds that of others. 
Therefore, I think we should have a timeline of the significant figures in history. 
I completely understand that determining how significant some people are is a difficult task. It's expected to take struggle and effort to make this work. However, people deserve to know who made the greatest contributions to the advancement of humanity.
Also, many scholars themselves have written about who they believe are to be the most significant people.
I have created a sketch of this idea at User:Wikieditor662/sandbox. It's far from perfect, but you get the main idea. The people are colored based on the era they were in. The most significant people make it to the overview and those who are not as important but still nonetheless significant (as well as people born earlier so the overview doesn't get clumped) go to the individual timelines (below the overview) along with those in the overview.
I would again like to reiterate that this is something that is going to take effort, dedication, and much debate, but if we do this, then I think it could be worth it. What do you all think?
Kindly, I'm experiencing philosophical opposition to this project. History has been a team effort, and further elevation of the already elevated is not likely to improve genuine understanding of historical processes. The Great man theory correctly fell out of fashion early last century.Having said that, I don't mean to dissuade you from undertaking a project you're clearly interested in, and this seems like it could serve as some kind of subpage of WikiProject Vital Articles. Using the inclusion criterion "listed at WP:VA" is probably the only way you'd ever develop any kind of agreement as to which historical figures to include. That WikiProject has already done a lot of debating over which topics are more important than others.The periodisation scheme is pretty parochial and Eurocentric, and would have to be converted to numeric year spans or whatever schema WP:VA uses (and the section headings would have to be delinked per MOS:NOSECTIONLINKS). You'll also want to consider how to handle cases where vital dates are approximate, unknown, disputed, etc. Folly Mox (talk) 00:12, 24 October 2024 (UTC)[reply]
I would tend to agree with Folly Mox on this. I'll add that it might be pretty much impossible to find an actual inclusion criteria, that is, any kind of consensus in reliable sources as to who is a significant enough figure – or even if we can compare the significance of historical figures across times, cultures, and domains. If anything, that page will inform more about our own selection than about any historical truth behind it.However, having it as part of WP:VA, rather than as an encyclopedic article, could make it a pretty useful reference for articles about famous figures needing improvement, without claiming that these are necessarily the most significant ever. Chaotic Enby (talk · contribs) 01:07, 24 October 2024 (UTC)[reply]
@Wikieditor662: you may have set yourself up for a poor reception with the questionshould people be included based off on how significant, famous, or both they are/were?. Both of these attributes are not quantifiable: the only inclusion criteria VA would recognise as feasible would probably be "limit to Level 3" (112 figures), or "include Level 3 and Level 4" (1995 additional figures; 2107 total). (Delta qualifiers like "vital dates securely known".)When a discussion is opened on a page and nobody responds for almost two weeks – as is the case here – this can often be understood as signalling lack of interest.If you really are interested in this data visualisation existing somewhere outside your userspace – which has seen no buy-in by participants at this thread nor any of the 93 watchlisters of the WikiProject talkpage – a next step might be to make a new timeline including precisely the figures listed at Wikipedia:Vital articles/Level/3 § People, and pitch the idea again, specifically as a WikiProject subpage, perhaps at WT:VA instead of WT:PVITAL.I'm afraid I feel compelled to reiterate that this idea does not feel pedagogically sound, and is likely to tell us more about the people who select the figures to include than it teaches about history. Folly Mox (talk) 01:06, 7 November 2024 (UTC)[reply]
Is there any reason we aren't or can't scrape and extract basic cite template information (webpage title, domain, visited datetime) at submit-time from bare URL <ref>s? Personally, I use bare URLs all the time as I consider filling out the cite template the most emphatically tedious part of editing WP (as it is when writing scholarly manuscripts) and know that some robot editor will just come along and fix it for me anyway. Since the code already exists and could be done more efficiently server-side, why don't we just pull it into the WP core? Just a small and probably extant idea I had while feeling a little guilty for adding a bare <ref> to a nicely-formatted article with proper tag attributes and template use. Cheers, fellows. Elliott-AtomicInfinity (talk) 01:38, 24 October 2024 (UTC)[reply]
Not quite what you are looking for, but there is reFill for bare URLs, and Wikipedia:Citation expander for when the URL is within <ref> ... /ref>. You can save your edit, and then immediately run those tools. As always, the output of any such tool must be reviewed and verified. Donald Albury14:32, 24 October 2024 (UTC)[reply]
You might be looking for this.
Or use the visual editor, or use the ref filler in the 2010 wikitext editor's toolbar. Or maybe even embrace the idea that everyone contributes in different ways, and that WP:CITE means what it says about doing your best to accurately communicate what your source is, and that editors can, do, and should work together on the formatting. WhatamIdoing (talk) 20:01, 24 October 2024 (UTC)[reply]
Nice, but it doesn't always work. It is particularly annoying when I'm trying to cite something that I have accessed through the Wikilibrary (with a long list of authors) and it doesn't work, and I am unable to go to the non-Wikilibrary page for the article. Donald Albury20:26, 24 October 2024 (UTC)[reply]
It is indeed unfortunate that many websites do not properly mark up their pages so that the automated tools and Zotero etc are unable to extract the appropriate information from webpages. But that is a problem that we cannot really solve. —TheDJ (talk • contribs) 20:48, 24 October 2024 (UTC)[reply]
Recently (1-2 months back?) I saw a project to improve the automated tools (or maybe just one tool), iirc by adding local code for specific commonly cited websites it consistently gets wrong. Unfortunately I can't find the discussion now, but if someone remembers it (user:WhatamIdoing?) you may be interested. Thryduulf (talk) 22:48, 24 October 2024 (UTC)[reply]
No, this was about better (more complete, more correct) automated filling of source metadata (author, publisher, title, etc) when a reference is added. Thryduulf (talk) 00:01, 25 October 2024 (UTC)[reply]
Oh right, and the "Edit Check" thread I guessed first had a tangential subthread about better metadata, including adding a local translation layer to Citoid as invoked from the Visual Editor interface, but no one gave the subthread a heading for me to link. I think it starts around here.Folly Mox (talk) 11:57, 25 October 2024 (UTC)[reply]
Or they do mark them up, but they block our servers. That's probably happening with The New York Times. Properly formatted refs are in their interest, too, but it's likely that all they see is some automated thing or another and automatically block it. WhatamIdoing (talk) 23:41, 24 October 2024 (UTC)[reply]
I think I've also had the problem using DOI. It looks like WikiLibrary sets cookies on my device (when I go back to a source a day or two after I looked it up with WL, WL immediately jumps in. I saw this happening even when I was logged in with my alternate account, which is not eligible for WL.), so any attempt to reach a link outside of WL gets diverted back to WL. Donald Albury18:15, 25 October 2024 (UTC)[reply]
Wikipedia talk:Please do not bite the newcomers § RfC: Is this rewrite ready to replace the current page?, which only got 8 responses in 3 months, with 4-4 deadlock. In particular, two editors have expressed concern that the rewrite was not persuasive enough, which I attempted to mitigate by expanding the lead with more emotionally-driven prose. I have therefore withdrawn the RfC. There seems to be a consensus that an rewrite is needed, however. While many of the suggestions provided on the RfC and the previous idea lab were added to the rewrite, I am thinking of advertising the next RfC on WP:Centralised discussion, so I would like further feedback for the proposed rewrite: Wikipedia:Please do not bite the newcomers/rewrite.
I would lean towards option 1, with option 2a as a second choice. The less bureaucracy the better, and CUs are trusted enough to use the permission responsibly. They have also already signed the NDA. If we are going to create a separate right, ArbCom is the body which is best equipped to assign (and importantly, monitor the use of) tools which give access to non-public information. Are there other options I am not thinking of? Reasons to pick a particular option? Other comments? HouseBlaster (talk • he/they) 02:47, 28 October 2024 (UTC)[reply]
Option 2a with the right being given initially to any current CU or former CU in good standing who asks for it. That way it can be added/removed independently of the CU rights if there is any reason to do so, and allows for any changes in the future. Thryduulf (talk) 03:34, 28 October 2024 (UTC)[reply]
Given that ACE scrutineers are routinely granted local CU for the purpose of properly scrutinizing the election, I do not think an electionadmin without CU makes any sense. (I can see the argument for having CUs without electionadmin, however.) In other words, I do not think it should be added independently of the CU right, but removing it would be acceptable. HouseBlaster (talk • he/they) 03:40, 28 October 2024 (UTC)[reply]
I think the ability to assign/remove it independently of CU is more important than whether it ever is given to a non-CU or removed from someone without removing CU. Thryduulf (talk) 03:45, 28 October 2024 (UTC)[reply]
Option 2a and personally, I don't think it necessarily needs to be restricted to CheckUsers. As long as the appointment comes with a vote of ArbCom and has community consultation, it satisfies the WMF's criteria for access, assuming the recipient is identified as well. I see no reason to lock it behind the CheckUser right, though I do think ArbCom is the right choice for who should be assigning it. EggRoll97(talk) 04:38, 28 October 2024 (UTC)[reply]
We should postpone considering this until phab:T377531 is resolved. Communication from WMF regarding SecurePoll related groups/rights has not been technically accurate. In particular I want to note the following points:
electionadmin group gives access to sensitive data as of today, but this is actually because of a bug. If/when the bug fix is merged (gerrit:1083337), no PII would be leaked – and the ability to setup and configure polls becomes quite low-risk and can be bundled into the sysop toolkit.
The user right which actually does expose PII, securepoll-view-voter-pii, is extremely sensitive! It allows viewing the IPs and UAs of all the voters in a single page. This is a much higher level of access than CheckUser which only allows viewing the data for a user individually, and the use of such access along with the given reason go into logs which are audited by ArbCom/Ombuds for compliance with local and global CheckUser policy. Compare that with securepoll-view-voter-pii which allows viewing PII en masse without any audit trail (phab:T356442).
This idea starts with the presupposition that PII must be collected on these. That is something that can be discussed. Perhaps it doesn't need to be, especially if we are going to keep using manual whitelists for the electoral rolls. — xaosfluxTalk09:48, 28 October 2024 (UTC)[reply]
Per SD, I think that all admins should have electionadmin right, since scheduling elections seems like great mop work. However, I disagree that the right to view voter private information shouldn’t be given to all CheckUsers. I think that it should, since the users that have accessed the information are already logged (T271276), so there is an audit trail. CheckUsers are also the ones who know about socks, so they seem like a great fit.
Unless we start doing an election a week we'll ever need more than a handful of election admins, so I'm not sure giving it to every admin is necessary. It sounds more like interfaceadmin (of which we have 10) or bureaucrat in that regard (15, and they aren't busy). – Joe (talk) 11:32, 28 October 2024 (UTC)[reply]
What benefits would there be in having way (as in perhaps 100x) more people than needed? The drawbacks I can see immediately are: increased risk/attack surface (we generally follow the principle of least privilege for even the most minor rights); increased chance of misunderstandings arising from the lack of clarity over who's responsible for elections (look at what's happened already); increased chance of conflicts when too many people are trying to coordinate one election; increased expectations for new admins from adding yet another bundled responsibility. – Joe (talk) 18:01, 28 October 2024 (UTC)[reply]
The arbitration committee election is run by volunteers who co-ordinate to avoid overlapping work. I'm confident that Wikipedia's collaborative community will continue in this tradition with administrator elections.
Bundling privileges together is a tradeoff: sure, election admins could be a separate user group, with the overhead cost of the processes to add or remove members. That has to be weighed against the risk of someone setting up votes without community approval. I think I agree with SD0001 that it's not a high-risk scenario. There are much better ways for someone who obtained access to an admin's account to disrupt Wikipedia than trying to setup clandestine polls. isaacl (talk) 18:34, 28 October 2024 (UTC)[reply]
That's what I'm basing my numbers off. The ArbCom election is run by three coordinators, three scrutineers, and a couple of people setting up the pre-RfC. So eight people, and none of them seem particularly run off their feet. We have over eight hundred admins.
I imagine the potential for abuse would not be in setting up bogus elections but in manipulating or sabotaging real ones or (if CU ends up being included in this) doxxing voters en masse. Admin accounts are scarce and valuable enough commodity for it to be worth the effort for some people. But again, we apply the principle of least privilege to rollback and page mover. Why wouldn't we do it here? – Joe (talk) 19:54, 28 October 2024 (UTC)[reply]
Regarding the arbitration committee election: anyone is eligible to co-ordinate the election RfC and the non-votewiki portion of the election itself. They don't all rush in and try to perform tasks without co-ordinating with each other.
SD0001 suggested that the electionadmin right be bundled with the admin toolset since, after the bug is fixed, it does not require CheckUser privileges. I appreciate that, in your view, the risk is sufficiently high to warrant the overhead of managing the electionadmin right with a separate process.
Regarding the page mover and rollback rights, they remain bundled with the sysop group, though. Since those rights are granted separately, if the principle of least privilege were followed, admins should have to apply for them separately rather than getting them bundled. I've previously stated my support for tailoring permissions with matching roles (see this comment thread on protection for Did You Know queues for example). But I recognize that there is an overhead cost, and there have to be willing volunteers to pay it. isaacl (talk) 22:09, 28 October 2024 (UTC)[reply]
Who will have access to the vote details? Unrelated to the other private details who voted, and how they voted should be encrypted and access extremely limited. If that's not the case these won't be 'secure' elections, and voters need to be very visibly warned that their votes aren't private -- LCU ActivelyDisinterested«@» °∆t°12:51, 28 October 2024 (UTC)[reply]
The creation and setup can be done by 'crats as Joe mentioned. For the PII exposing rights, I do agree with SD's views, I also have another option, this right can be asked only by existing Check Users, and the ArbCom can grant it to the ones who have a respectable experience using CU tools. ~/Bunnypranav:<ping>12:55, 28 October 2024 (UTC)[reply]
One thing to keep in mind, to see SP PII you have to be listed on the specific poll (and you have to be in the electionadmin group to be eligible to be listed on the specific poll). So if we decide to collect the enhanced PII in SP, then it is still limited to only the users registered to the specific poll. — xaosfluxTalk13:21, 28 October 2024 (UTC)[reply]
Regarding the attack vector for users with the electionadmin, a compromised account could add more scrutineers to the poll. Thus the risk would be that everyone in the group with the securepoll-view-voter-pii right could gain access. So for simplicity, I think we should be prepared to accept that everyone with the securepoll-view-voter-pii right might have access. If want to be able to move users in and out of this group on a per-poll basis, then there should be a separate user group for it. isaacl (talk) 18:45, 28 October 2024 (UTC)[reply]
Note: It is certainly possible we could have multiple, overlapping secure polls at the same time on different topics with different admins, etc. — xaosfluxTalk18:52, 28 October 2024 (UTC)[reply]
So one thing that needs to be considered is, first assuming we collect the PII in SP, is that if a scrutineer wants to be able to further investigate a voter using other on-wiki data, they will also need to be a local checkuser to be able to check those logs. So it needs to be established that those checks are appropriate, and additionally we currently give arbcom exclusive decision making authority on who may be a local checkuser. — xaosfluxTalk18:50, 28 October 2024 (UTC)[reply]
Echoing Xaosflux above, I believe electionadmin / securepoll-view-voter-pii does not grant every electionadmin the ability to see every voter's data ever. I think it just grants the ability to be added to a poll during setup. There is compartmentalization. So how this would work in practice if we gave the right to all the checkusers is that when we have an election, we'd probably want to pre-pick 3 checkusers to scrutineer the election, add them to the poll, then only those 3 would have access to the data. Right now the way I am asking WMF to set up SecurePoll for us is to let any admin create a poll, and then only that poll's designated electionadmins can edit a poll or scrutineer. phab:T378287. There's 3 pending patches related to phab:T377531 that may change some details of how SecurePoll permissions work. We may have some additional clarity after those patches are merged and have been in production for a few weeks. –Novem Linguae (talk) 19:08, 28 October 2024 (UTC)[reply]
I think we need a discussion of who should have it. The RfC linked above gave this meta page as an explanation of what an 'electionadmin' is, and it says (perhaps contrary to the default in the documentation) that it's a right that allows users to set up elections with SecurePoll. – Joe (talk) 07:38, 29 October 2024 (UTC)[reply]
I'm opposed to local CUs doing scrutineering. For electionadmin (excl PII), I don't see why we don't give it to the Electoral Commission only? They're elected to manage the ACE process. This is distinct to option 2 in my eyes; it would be assumed consensus upon election of an Electoral Commission (perhaps the crats could action the userrights changes). For AELECT, it's trickier but could be discussed in post-trial discussions. For PII scrutineering, I think we should continue using stewards for ACE; for AELECT it's up in the air (and subject to them willing to do it, and the frequency of admin elections being reasonable for them, I'd prefer stewards handling it). ProcrastinatingReader (talk) 22:11, 29 October 2024 (UTC)[reply]
But is it really good to require relying on Stewards for local stuff? It just seems more logical to me that we make it all an on-wiki process. I just don't see why not local CU. Aaron Liu (talk) 22:22, 29 October 2024 (UTC)[reply]
I think so, at least for scrutineering. Stewards are happy to deal with it AFAICT and it's been the way it's done historically. Aside from independence reasons, I'd be concerned with local CUs doing election scrutineering with PII because that would give local CUs a dual-purpose. Their purpose atm is tackling abuse, and they're restricted by the Wikipedia:CheckUser policy. In particular, they need cause, and their checks are logged. But scrutineers see all voters', which is a large portion of the active editor userbase, and their checks aren't logged. I find it hard to reconcile this in my head with the restrictions placed upon CUs in our local policy, which become meaningless to my mind if CUs can see most active editors' IPs come ACE/AELECT anyway. ProcrastinatingReader (talk) 22:29, 29 October 2024 (UTC)[reply]
Not exactly sure what @Xaosflux meant above, but the task he mentioned only said that it was a bit too easy (as in friction, not permission) to access the PII, not that it's not logged; in fact, the task links to phab:T271276, which made access logged. Correct me if I'm wrong, but don't the list of users who can access PII have to be whitelisted by the electionadmin for every election? Aaron Liu (talk) 23:42, 29 October 2024 (UTC)[reply]
Yes, to see securepoll data you have to be an explicitly listed admin for the specific poll you want to view; to be eligible to be listed you have to currently be in the electionadmin group. Viewing the securepoll data is logged in securepoll. It is also possible to configure a poll to not collect personal data at all, so just the public list of usernames would be available. — xaosfluxTalk23:53, 29 October 2024 (UTC)[reply]
I didn't know about the feature mentioned in phab:T271276 and didn't see it in localhost, probably because of some missing setup. It does seem to be logged after all. Nevertheless, it just records that someone saw the full list – there's obviously no way of logging whose PII they happened to look at or take note of. That's more of what I meant. – SD0001 (talk) 22:19, 30 October 2024 (UTC)[reply]
A possible solution CUs having a lot of instant access, if a CU wants to become a PII scurtineer, they would have to apply to it, and a group of trusted users (crats/ArbCom/anyone else that the community deems trusted) can approve it. This perm can be granted/requested per election, and they would be added into the securepoll view PII whitelist. ~/Bunnypranav:<ping>10:35, 30 October 2024 (UTC)[reply]
In summary, you're proposing we ask bureaucrats to give people the electadmin right. Honestly, since we (probs. justifiably) don't appear to want SecurePoll to be frictionless, I think that's a good-enough idea. Aaron Liu (talk) 22:21, 29 October 2024 (UTC)[reply]
The original purpose of the arbitration committee election commission was to be able to decide on questions that needed to be settled quickly to be effective, and thus a community RfC discussion wouldn't be feasible. Community expectations has shifted the role to include more management of community comments. Most of the election management continues to be done by other volunteers. Personally, I don't like continuing the trend of making the commission more central to the arbitration committee election process as I'd prefer that it remain a largely hands-off role. I like how the arbitration committee elections are run through a grassroots effort. isaacl (talk) 22:38, 29 October 2024 (UTC)[reply]
How are election admins on votewiki currently decided? It looks like Cyberpower and Xaosflux have had electionadmin for various periods.[9][10] Is consensus needed, or do WMF just appoint people who express interest in helping manage the process? ProcrastinatingReader (talk) 22:46, 29 October 2024 (UTC)[reply]
When an election is being configured on votewiki the coordinators have accounts made and are added to the group, then are added to the election, as are the scrutineers. In elections such as ACE, the coordinators are removed when voting begins so they can't access the PII that gets collected. — xaosfluxTalk23:55, 29 October 2024 (UTC)[reply]
When there are non-technical coordinators, they may not get added as they wouldn't have anything to do - in which case the WMF resource generally does all the work. — xaosfluxTalk23:56, 29 October 2024 (UTC)[reply]
I'm going to split a couple of ideas out in to subsections below. There are a few complicated things that need to be considered. Let's assume this isn't for ACE right now, but for any other use case we decide to use securepoll for. — Preceding unsigned comment added by Xaosflux (talk • contribs)
create new separate userright Setting up elections is a specialized, new, sensitive, very social process. Although elections require checkuser services and support, there is little overlap in the roles. I presume how this is going to work is that we have a noticeboard for requesting elections, a form to complete in that noticeboard, and then the electionadmin will use the tool which generates the election instance. When the election is complete, then I think the electionadmin should turn the results over to a checkuser for scrutiny. The major English Wikipedia election is Wikipedia:Arbitration Committee Elections December 2023/Coordination, but I think that whomever is in this role for English Wikipedia should be open and eager to collaborate across wikis with elections including Picture of the Year, WMF board elections, special elections like the Movement Charter, and Community Wishlist. All of these elections have had very serious social challenges which are beyond the role of technical functionary. It may not fall to the role of electionadmin to resolve all social issues, but the electionadmin certainly should not create election instances carelessly or without confirming that community support for an election is in place. The results of Wikimedia elections direct investments at least in the tens of millions of dollars. This election committee should consider the possibility of requesting a budget from the Wikimedia Foundation to communicate the elections, train election coordinators, discuss election policy and best practices across languages and wikiprojects, and try to establish some social and ethical norms that apply through Wikimedia projects. I would like for people to trust our elections and believe that Wikipedia is democratic. Activities like "promoting democracy" are not in the scope of checkuser duties. If we assign this userright to checkusers, then I think that will restrict elections to what checkusers currently do, rather than allow us to design elections to meet community needs. And yes of course - people with electionadmin rights should not get checkuser access to personal data. Bluerasberry (talk)21:11, 1 November 2024 (UTC)[reply]
While I have many words to say against your argument on electionadmins, this is a workshop, so at this point I think we should accept "create new electionadmin user group" and "add electionadmin to all admins" as separate options.
If we assign this userright to checkusers, then I think that will restrict elections to what checkusers currently do, rather than allow us to design elections to meet community needs.
@Aaron Liu: Scrutineering and election administration are non-overlapping workflows. Part of scrutineering is checkusering. Another part of scrutineering could include confirming that someone is eligible to vote by non-standard, non-machine readable criteria, which Wikimedia elections often include. For example, elections over off-wiki processes often give voting rights to people who contribute to Wikipedia outside the Wikimedia platform, such as by processing Wikimedia Commons content for upload or similar. Bluerasberry (talk)00:31, 2 November 2024 (UTC)[reply]
I'm fairly sure election administrators configure the list of eligible voters, not scrutineers. I have trust in administrators to conduct diplomacy and even more trust in a potential group of "specialized, sensitive, and very social" users. Aaron Liu (talk) 00:39, 2 November 2024 (UTC)[reply]
Scrutineering and election administration are non-overlapping workflows. I agee. I envision splitting electionadmin into a user right that adds and edits polls, and a user right that scrutineers polls. They are currently kind of combined. phab:T377531. –Novem Linguae (talk) 05:55, 2 November 2024 (UTC)[reply]
You lost me a bit in the second half of your post, because you switched to talking about global elections and WMF budgets. I think that would be unrelated to what we're talking about here, which is developing the ability for enwiki to host its own non-global elections, with the goal of 1) not depending on and using the resources of global partners such as stewards and WMF Trust & Safety, 2) developing the technical and social ability to hold many more elections than we do currently, and 3) increasing autonomy. Our use cases are things like WP:ACE and WP:AELECT. By the way, global elections are their own special beast, and are much more technically challenging than local elections (phab:T355594, wikitech:SecurePoll#How to run a board election), and basically require WMF Trust & Safety and WMF software engineer support no matter what, unlike local elections which will run completely self-sufficiently once we have a system in place. –Novem Linguae (talk) 05:53, 2 November 2024 (UTC)[reply]
Do we need PII in SP for local elections?
So this is something that is going to be important as to who is going to be allowed to do what, and how they will be allowed to do that. Polls don't have to collect PII. If they don't, they will still collect usernames. PRO's are that if we don't collect PII in the vote action, then the bar of who can administer elections is much lower. The con is that checkuser data of the vote-action isn't collected. Keep in mind the username is still collected - and checkuser investigations of everything that person has done on-wiki can continue as per normal. This is very close to how it is in RFA now, if the only edit/action that wasn't checkuser recorded for someone was their "vote". — xaosfluxTalk14:26, 30 October 2024 (UTC)[reply]
I like the idea of collecting the PII from the voting data, as it's a good way of excluding some socks and catching others. However that's not the really the purpose of having a poll, so I don't see why its collected. Maybe I'm missing something, is there some other reason to collect the data? -- LCU ActivelyDisinterested«@» °∆t°15:33, 30 October 2024 (UTC)[reply]
The purpose of collecting the PII is to detect attempts to circumvent the one person, one vote requirement by one person voting from multiple accounts. This is done by analysing the public and non-public information in the same way that checkusers at SPI do. At arbcom elections struck votes fall into five categories:
Editors in good standing voting twice from the same account. This is permitted and should just automatically invalidate the older vote but occasionally it doesn't happen. Scrutineers strike the earlier vote.
Editors in good standing voting twice with different accounts in good faith. e.g. someone with a valid alt account wanting to change their vote but forgetting which account they used first time, or forgetting that they'd already voted. Scrutineers strike the earlier vote.
Editors discovered to be sockpuppetteers by normal means after they have cast votes. If only one account has been used to vote the most recent vote by that account is allowed to stand, if multiple accounts have been used to cast votes then all the votes are struck.
Known sockpuppetteers voting with one or more accounts discovered to be sockpuppets by the scrutineers. Scrutineers strike all votes.
Editors, not previously known to be sockpuppetteers, discovered by scrutineers to be voting with multiple accounts in bad faith. Scrutineers strike all votes.
Without PII being collected I believe that the first three types of multiple voting would still be detectable, the rest would not. Sockpuppetteers who vote using only one account will not be detected by scrutineers regardless of whether PII is collected or not. Thryduulf (talk) 16:43, 30 October 2024 (UTC)[reply]
The last two fall into the using the poll to catch editors who are socking that I mentioned, but should this be something that's part of the poll? I guess the main issues would be a sockpuppetiers setting up accounts that allow for voting, and then never using them again. That would be near impossible to catch unless they slipped up before hand.
Say the was a EC requirement to vote, a malicious actor could setup multiple accounts, use them to make good edits in completely separate areas to avoid scrutiny, and only bring them together within a vote in an attempt to sway the outcome. The normal methods for catching sockpuppets would be ineffectual in stopping that.
CUs who aren't election admins can't see anything more about the vote/voter that a normal admin can, even if they have a reason to look. Thryduulf (talk) 20:20, 30 October 2024 (UTC)[reply]
Sorry, I meant the scrutineers, not either of the above. I know that this is somewhat CU procedure and typed my thoughts out wrong :) thanks for the correction Aaron Liu (talk) 20:32, 30 October 2024 (UTC)[reply]
only if the poll is set to collect PII. I don't see any option to turn off PII collection on the page Special:SecurePoll/create. One way to turn that off would be to not grant the user right securepoll-view-voter-pii to anyone. Unless I am missing an option somewhere. –Novem Linguae (talk) 21:13, 30 October 2024 (UTC)[reply]
Hmmm, seems like this feature didn't get off the ground (only hide the voter list from other voters did). Sort of why we are in idea lab though -- if this is useful we could put in a feature request do "disable PII collection". — xaosfluxTalk22:02, 30 October 2024 (UTC)[reply]
Electionadmins do not need access to personally identifying information Someone should be able to scrutineer election data. Right now checkusers do that. I do not think electionadmins should have access to personally identifying information, but they should be able to consult with checkusers or have some way to confirm election validity. Bluerasberry (talk)21:15, 1 November 2024 (UTC)[reply]
This is about whether scrutineers should have access to PII, not about electionadmins. Scrutineers are the people whitelisted for each election to view a list of the browser-used and IP-used for every vote. Aaron Liu (talk) 22:21, 1 November 2024 (UTC)[reply]
?? I must be misunderstanding. Who gets whitelisted to scrutineer, and on what basis? As I understood, checkusers can already do this, and the discussion is about whether users with the electionadmin right could additionally scrutineer. Is "whitelist to scrutineer" an additional class of users? Bluerasberry (talk)00:36, 2 November 2024 (UTC)[reply]
No, this subheading is about whether scrutineers should be able to access PII, not electamins. For each election, highly trusted users (so far, with the votewiki elections, those users have been stewards) are asked if any of them would like to volunteer to scrutinize the election (and just that election, though they can also volunteer to scrutinize futre elections separately). After that, when setting up the election, two lists have to be added by an electamin: 1. a list of all users who may vote; and 2. a list of users who may view the PII-containing logs of voting.A list from which a software may "bouncer" to deny everybody not on the list is called a whitelist. Aaron Liu (talk) 00:49, 2 November 2024 (UTC)[reply]
Who gets whitelisted to scrutineer, and on what basis? Depends on the election. One common format is to pick 3 stewards to scrutineer an election. Then WMF T&S gives them electionadmin permissions on votewiki, and they are added to just the election they'll be scrutineering. As I understood, checkusers can already [scrutineer]. I don't think this is correct. The checkuser group does not have any SecurePoll related permissions by default. We would have to change the #Wikimedia-site-config via a Phabricator ticket. However giving checkusers these permissions is a logical idea since checkusers have already signed the NDA and are already trusted to handle the kind of voter data that SecurePoll collects. –Novem Linguae (talk) 06:03, 2 November 2024 (UTC)[reply]
Checkusers do not currently scrutineer our elections and never have. Stewards, those who are not from enwiki, do it. Nobody aside from the three designated stewards who are scrutineering (which are any three stewards who volunteer) are the only ones who see the PII of voters in elections. ProcrastinatingReader (talk) 09:55, 3 November 2024 (UTC)[reply]
No PII means no scrutineering. Are we comfortable with having 600 vote WP:AELECTs or 1,600 vote WP:ACEs without anyone double checking IPs and user agents for obvious socks? I'm leaning towards yes collect PII. Also SecurePoll does not currently appear to have an option to turn off PII collection. –Novem Linguae (talk) 06:22, 2 November 2024 (UTC)[reply]
No PII means no scrutineering. I wouldn't say so. It would mean elections have the same level of (sockpuppetry) scrutineering as RfAs, where only usernames are visible. I don't really think a sock is going to change the outcome of an ACE election. At the same time, it may well help ensure the integrity of elections, if even through deterrence, thus I'm ambivalent on whether to collect PII.
I think either stewards scrutineering with PII or no PII scrutineering are OK with me. I'd prefer either of those options to local CUs scrutineering though, which I find a bit discomforting. ProcrastinatingReader (talk) 09:54, 3 November 2024 (UTC)[reply]
It would mean elections have the same level of (sockpuppetry) scrutineering as RfAs At the moment, not exactly – an RfA vote is an edit, so its PII is available to CUs, whereas a SecurePoll vote is not logged to Special:Log, so the CU tool has no access to its PII. I've filed phab:T378892 regarding this. I concur that local CUs should not get access to the wholesale PII of all voters. Scrutineering should be either done by local CUs using the CU tool only (assuming the ticket is resolved), or by external stewards like currently. – SD0001 (talk) 10:48, 3 November 2024 (UTC)[reply]
Do we need to encrypt the backend poll data?
How people voted isn't available through the securepoll system, but when setting up a poll you can optionally choose the configure encryption. This will prevent vote data from being able to be accessed by system administrators who read the datastores. This provides quite strong voter secrecy. The downside is that cryptography is hard, and will require election administrators to understand these aspects, develop and strictly adhere to secure processes for key management. As this larger idea is about who can be an election admin, if we need this component we will need a way to ensure that such admins are not only trustworthy, but that they are also technically competent. — xaosfluxTalk14:26, 30 October 2024 (UTC)[reply]
I'm confused, you say How people voted isn't available through the securepoll system and encryption will prevent vote data from being able to be accessed by system administrators. So to clarify without encryption can system admins see how people voted, or is that information store elsewhere? -- LCU ActivelyDisinterested«@» °∆t°14:35, 30 October 2024 (UTC)[reply]
When you create a poll, you can choose to optionally encrypt the poll data. This can be done with SSL or GPG keys. If you encrypt the poll, the stored data can't be read by system admins (note, this is not a wikipedia admin, or 'election admin', but the back-end server administrators). Finalizing the poll requires loading the decryption key in to the tallying mechanism. If the poll isn't encrypted it is possible the vote data could be accessed by system admins accessing the raw stored data. In either case, the software doesn't ever produce a voter:choice output. — xaosfluxTalk15:01, 30 October 2024 (UTC)[reply]
Ok so the choice that voters make isn't accessible even without encryption, which would suggest encryption isn't needed. What general type of information about the vote data is accessible without encryption? -- LCU ActivelyDisinterested«@» °∆t°15:05, 30 October 2024 (UTC)[reply]
It's not available through the poll system (the confidentially risk is only of stored raw data for server admins). The public data is what you can already see on all elections: date of vote, name of voter, and if the vote has been replaced or stuck. — xaosfluxTalk15:19, 30 October 2024 (UTC)[reply]
Note that the current poll encryption feature still doesn't entirely prevent an actively malicious sysadmin from, say, modifying the software to do something with the unencrypted data either before it's encrypted or after it's been decrypted to be counted. Of course that's much harder to pull off than just reading the unencrypted database (especially if you don't want to leave any traces) and requires a bit more server-side access, but not impossible. Taavi (talk!) 15:14, 30 October 2024 (UTC)[reply]
(no opinion in whether it should be encrypted, just stating some facts) Not all sysadmins are WMF staff. And there are a total of 192 sysadmins, which is much more than you might expect. * Pppery *it has begun...17:34, 30 October 2024 (UTC)[reply]
Out of curiosity, where's the 192 number coming from? Folks in the ops LDAP group would definitely have enough database access to modify votes in the SQL database, but that's only 65 people I think. Who'm I missing? –Novem Linguae (talk) 21:26, 30 October 2024 (UTC)[reply]
Yes. The first two can modify the running code, and analytics-privatedata-users can also read things from the database (in addition to the restricted group). Taavi (talk!) 04:20, 31 October 2024 (UTC)[reply]
analytics-privatedata-users contains 270 people, 128 of whom are already in one of the other groups, making 334 people total. No, I don't expect any of them to go snooping, but it is what it is ... * Pppery *it has begun...21:53, 31 October 2024 (UTC)[reply]
Given that voting choices could be accessed I would say it needs to be encrypted. Obviously this only makes it harder to access the information not impossible, but that is true of all such measures. Account passwords are required even though as a security measure they can be overcome.
This should be decided on a case-by-case basis. If a WikiProject is using SecurePoll to elect its coordinators, using encryption seems like overkill. For ArbCom elections, on the other hand, I see no reason not to encrypt. For such significant elections, there would be no shortage of volunteers who can handle OpenSSL keys. – SD0001 (talk) 17:59, 30 October 2024 (UTC)[reply]
Leaning no to encryption. Seems like overkill. "Make the workflow more complicated for every electionadmin in every election" vs "make it harder for a rogue sysadmin to tamper with an election one time or a couple times until they get caught/fired/access removed" seems to be the tradeoff to weigh here. –Novem Linguae (talk) 21:28, 30 October 2024 (UTC)[reply]
It's not tampering with the result that is the problem, and reading the vote choices is unlikely to get caught. I wouldn't vote if I knew my vote was so easily accessible. -- LCU ActivelyDisinterested«@» °∆t°22:01, 30 October 2024 (UTC)[reply]
I'll have to try out encryption in a SecurePoll test wiki sometime. I should probably also take a peek at the database and see exactly what it encrypts. But my impression is it increases complexity for the electionadmin, who has to do stuff like generate encryption keys, then make sure the encryption key doesn't get lost else the entire election's results are lost. This will reduce the pool of folks that can easily administrate an election, limiting it to a small pool of technical users who are familiar with this encryption workflow. –Novem Linguae (talk) 06:08, 2 November 2024 (UTC)[reply]
Avoiding a long month of drama
Well. WP:RECALL is upon us now, and, while clearly an improvement for community accountability, the first petition is already showing that the system has its limits. To be fair, that is to be expected – we can't really brainstorm a perfect system without any real-life testing, and such a new system should be open to community inputs for tweaking it into a more functional state.
Namely, the issue is with recall proposals that are, from the start, overwhelmingly likely not to succeed. In a case such like this one, where the number of (informal) opposes far outweighs the number of signatories, prolonging the long drawn-out process (the petition being open for a month, and then potentially seven days of RRfA) isn't desirable if the outcome is already pretty much known. I figure there should be a way to cut short petitions where it is clear that most editors are not behind it, a sort of WP:SNOW close, to avoid dragging the admin and the community through a month-long slog.
Of course, the petition itself shouldn't be the final !vote on admin accountability, but only a means to bring up the issue. So, if we go through an opposes/signatories ratio to close it early, for instance, it should be pretty high (maybe 3 to 1?), but still allow a way to cut short petitions with no chances of succeeding. Chaotic Enby (talk · contribs) 13:55, 28 October 2024 (UTC)[reply]
Discussion ongoing: limiting petition participation to signatures Discussion ongoing: shortening the recall period Links added 12:24, 7 November 2024 (UTC) —Folly Mox (talk)
Agreed. If each person were allowed to write a single short statement (absolute maximum 2 sentences) about why they support/oppose and no discussion or replies were allowed then a month would be reasonable. A month of what's currently happening at the first petition is completely unreasonable - a week of that plus a week of RFA hell is not reasonable even for someone whose conduct is beyond the pale (and they should be at Arbcom anyway) let alone a month for someone who has just made a few minor mistakes or pissed off a few people.
The Crats should be empowered to close petitions early if the result is clear (either way). Arbcom still exists as a venue should people think that a petition that was going to succeed was closed too early. Thryduulf (talk) 14:15, 28 October 2024 (UTC)[reply]
Isn't the primary point of the petition process to ensure that we don't have frivolous RRFAs? It seems that most of the participants are already trying to skip to a future RRFA discussion that may not even materialize. — xaosfluxTalk14:23, 28 October 2024 (UTC)[reply]
That is indeed an issue, the petition is itself getting a RfA-like amount of discussion before the RRfA even started. Thryduulf's proposal of limiting the conversation to a single short statement per person could make it much more manageable, and cut short the problem by making 30 days long petitions less awful. Chaotic Enby (talk · contribs) 14:59, 28 October 2024 (UTC)[reply]
Opposes don't formally affect the outcome of the petition, that's what the RRfA is for. From my own thought process (and from what I read from that discussion), opposes can only dissuade potential petition signers to NOT sign the petition. fanfanboy(block)14:39, 28 October 2024 (UTC)[reply]
I know, that's why I was referring to them as informal opposes above. But there should still be a way for the community to formally state that the vast majority is not in support of a petition. At least to shut down frivolous petitions in advance. Chaotic Enby (talk · contribs) 14:57, 28 October 2024 (UTC)[reply]
The Lizardman's Constant means that pretty much all views will be supported by some people, so no, I don't think we can rely on that. It's a complete waste of everyone's time if we only pay attention to the support votes and force a WP:SNOWBALL petition to go to RRfA. Theknightwho (talk) 18:34, 30 October 2024 (UTC)[reply]
There is no drama except what some editors are creating. I don't think an admin is going to quit because they discover that five people think they shouldn't be an admin. Those that oppose the petition can just... not sign it. It'll be over in 30 days. I'm not opposed to shortening the 30 days but I'd rather wait at least one full cycle before deciding. Preferably more than one full cycle. Levivich (talk) 14:47, 28 October 2024 (UTC)[reply]
As I have said elsewhere, we need to reduce the drama surrounding these. I agree that people opposing the petition should just leave it alone. There should be no discussion section and no threaded responses to endorsement; a week of discussion (which is plenty) happens once the petition is successful. Additional discussion only makes the signal to noise level worse and cranks up the heat. —Kusma (talk) 22:54, 29 October 2024 (UTC)[reply]
Agree with some of the others that shortening the time makes sense, though I don't think we should be cutting it to shorter than 2 weeks if we started at 30 days. 25 signatures in 30 days does seem really out of wack - less than one signature a day, in a community this large, where RFAs have some 200 votes in a week and we've already got more than 400 votes in the admin elections? Seems very off. -- asilvering (talk) 16:12, 28 October 2024 (UTC)[reply]
Thing is that many editors (including myself) voted for the 30 days. Now seeing what has happened, I agree it should be shortened. 2 weeks seems like a good number. fanfanboy(block)16:21, 28 October 2024 (UTC)[reply]
I suppose, we'll have to be mindful of the potential for editors to seek an administrator's recall, who blocked/banned them, in the past. Grudges are always possible as being a core of recall attempts. GoodDay (talk) 14:46, 28 October 2024 (UTC)[reply]
I think shortening the time period for the petition to 10 or 14 days makes sense. I would oppose allowing snow closes regardless of how unlikely it appears that a petition will pass. ~~ Jessintime (talk) 15:18, 28 October 2024 (UTC)[reply]
I'm inclined to believe that, instead of tinkering with this on an ad hoc basis with every new petition, we modify the terms of the recall process to be a six-months trial and then -- at the end of that -- evaluate everything that worked and didn't and make whatever modifications are needed in one fell and final swoop. Chetsford (talk) 16:25, 28 October 2024 (UTC)[reply]
@Chetsford The close of the final RfC establishing recall instructed that any outstanding issues may be resolved through normal editing. (emphasis mine), and personally, I am very burnt out by all the multi-step trials and ratification RfCs that sprung out of RFA2024. Mach6116:47, 28 October 2024 (UTC)[reply]
To be fair, this is a discussion on the idea lab, so the goal is first to figure out what to change before figuring out how to change it. And also because, even if a user could technically make a WP:BOLD edit, having a consensus behind it is always good. Chaotic Enby (talk · contribs) 17:00, 28 October 2024 (UTC)[reply]
I looked at the petition before it closed, and realised multiple editors opposing it despite it not having any effect. I think it should be possible to run a petition in a closer timeframe to an RfA or AfD. To summarise, petitions could be changed as follows :
Each petition runs for exactly a week.
Any extended confirmed editor can support or oppose the petition
If consensus is reached to desysop after a week (ie: support / support + oppose = 70% per current RfA thresholds) then the admin is desysopped
I think holding an admin to the threat of being desysopped for over a month is worse than what happens at Arbcom. Conversely, if the community is in obvious agreement than an admin has outstayed their welcome and must go, it gets the job done far more quickly without people getting frustrated about when it's going to happen. And furthermore, if somebody starts a petition in retaliation ("Desysop this admin, he blocked me for no reason!") it'll get short shrift and SNOW opposed by the community.
The only issue I have with that is theoretical. Ostensibly, the petition is supposed to create a turnstile sparing an Admin from having to go through the back-and-forth of an entire RfA unless there's some minimum support for that. In other words, ideally, the Admin simply ignores the petition until or if the threshold is met. Only then do they need to ramp up to start compiling, potentially, years of diffs, etc. to defend themselves at RfA. Going straight to RfA means any single, aggrieved editor can encumber an Admin with the significant angst of a full RfA. Of course, that's all theoretical. As we've seen from the current example, the mere act of petitioning creates the angst it was designed to mitigate. So, if we're going to introduce a Reign of Terror anyway, we may as well make it the most efficient Reign of Terror we can come up with, on which basis I'd support this suggestion. Chetsford (talk) 17:01, 28 October 2024 (UTC)[reply]
The other option would be to make it so that the petition doesn't turn into a Reign of Terror to begin with. Which is easier said than done, but a good first step would be to limit back-and-forth conversation and just have it be, well, a petition. Chaotic Enby (talk · contribs) 17:05, 28 October 2024 (UTC)[reply]
I do have a few concerns on that. In this situation the Admin is being recalled for reasons no one is allowed to articulate to them, but maybe they'll learn them during sentencing (RfA)? I liked The Trial as much as anyone, but I'm not sure how I feel about recreating it IRL. But I'm open to whatever. Chetsford (talk) 17:13, 28 October 2024 (UTC)[reply]
No it wouldn't prevent reasons being given, it would just restrict discussion of those reasons. So everybody supporting or opposing the petition would be able to (arguably should be required to) give a single short statement (50 words or 2 sentences have been suggested) about why they are supporting/opposing. However there would be no discussion unless and until an RRFA was opened. There would be no restriction on clarification being sought on user talk pages, e.g. if user:Example wrote "Support because of their actions at the recent AfD" anyone would be allowed to go to user talk:Example and ask which AfD(s) they were referring to if it wasn't clear. Thryduulf (talk) 17:20, 28 October 2024 (UTC)[reply]
I would say no. If the petition can get 25 people to agree (despite all the issues of the discussion section), then the RFA should run. Y'all are Streisanding the current petition and bringing people in. If it was as sterile and clinical as the process laid out was supposed to be, it would more than likely died in a month. spryde | talk20:52, 28 October 2024 (UTC)[reply]
I think any petition is going to get significant amounts of attention, maybe not quite this much if they become routine, but certainly enough that it's never going to be "sterile and clinical" under the current setup. Thryduulf (talk) 21:14, 28 October 2024 (UTC)[reply]
If the time is reduced to a week, then the number of signatures needed should be reduced. I also don't understand the point of opposition statements. If it is a petition, then there should just be people signing it, maybe proposing changes to the petition statement. It seemed like a lot of the opposition was based on people not likely the process. There is already a problem with accountability for admins in Wikipedia, because admins are not only well known, but have power to block people, and probably have more knowledge of how Wikipedia works than the poor editors who try to recall them. Admins are pretty safe. Term limits would have been a better solution, as well as temporary blocks for admins. Tinynanorobots (talk) 11:35, 29 October 2024 (UTC)[reply]
For now, we have a sample set of one incomplete case. Ten editors have signed the petition in the first 40 hours. A linear projection would predict that 25 signatures would be reached in less than five days. Some commenters have assumed that the level of opposition expressed to this petition indicates that Graham87 would retain the admin bit in an RRFA. If a case that appears this weak does reach 25 signatures in less than a week, why should we have to wait a month for cases where there is less enthusiasm for signing a petition. I will note that the rate of new signatures likely will decline, prolonging the end, and that some commenters are claiming that many potential signers will wait to the last minute to sign to avoid social pressure, but that is not an argument for waiting a month, as they can sign the petition at the last minute whether the duration is for a week, two weeks, or a month. But, as I said, this is the first case, and my crystal ball is very murky. Donald Albury13:39, 29 October 2024 (UTC)[reply]
I think that that first recall petition showed some of the warts of the process in a really stark way. Floating 4 significant changes for the community to think about here, either separately or in combination:
1) - The petition process is too long. If these are going to turn into mini-RfAs, then the petition needs to be significantly shorter than a RFA. 24-72 hours is plenty of time to see whether the petition has legs, anything more is cruel.
2) - The petition is too easy to initiate. I know that people will complain about cabals, but I really think it should take an admin to initiate one of these. Alternatively a small group (3 ish) of extended confirmed users works.
3) - We should move from number of supports to number of net supports. If a petition has 1 net support at closing time, it can go through as prima facie evidence that the petition has legs. If the ratio of opposes to supports gets over 2-3 to 1, we can close early without losing many petitions that would wind up successful.
4) - The commentary is too much. Restrict people, both support and oppose, to something very short, like 10 words and 1 link.
Obviously this is idea lab, so please discuss which of these have merit fluidly either alone or in any combination. tweak numbers, break things. Tazerdadog (talk) 17:07, 28 October 2024 (UTC)[reply]
I'd agree with shortening the petition process (although 72 hours might be too drastic), but I think turning them into mini-RfAs is not the goal. The point of the petition is to see if there is a substantial number of editors wanting a recall election to begin with, not to replace the recall election entirely. And, if you need to get 3 people on board to start the petition, you're functionally making a petition for the petition.For the same reason, net supports shouldn't really be what is measured (as it isn't about whether the admin has majority support, but only about whether some people are questioning it). A large oppose ratio, however, would indicate the petition will likely not be successful, so the early close you suggest could work. Also agree with your idea of restricting commentary, as said above. Chaotic Enby (talk · contribs) 17:11, 28 October 2024 (UTC)[reply]
The old RFC/U process required two editors to sign within 48 hours, or the page would get deleted. These two editors had to show evidence(!) of having attempted to resolve the same(!) dispute with the targeted editor. This was fairly effective at preventing RFC/Us over disputes that just needed a Wikipedia:Third opinion. WhatamIdoing (talk) 18:43, 29 October 2024 (UTC)[reply]
It's impossible to constrain the discussion when the petition has started and for the petition page not to turn into a quasi-RfA. That's why the petition signatures and comments should be understood as RRfA !votes. The signatures would begin counting as !votes when 25 of them are collected, and prior to that, the signatures would be null !votes, and only valid as fulfilling a precondition to their collective validity as !votes. A signature is actually a latent 'oppose adminship' RRfA !vote. An "oppose petition" comment is actually a 'support adminship' RRfA !vote. At any point, if the admin does not like the protraction and feels secure about passing, the admin can cut the petition stage short and start the RRfA with their statement, answers and all, without a need to wait for signatories to reach 25. That imbues all signatures with the power of a !vote immediately, regardless of how many there are, whereas the "oppose petition" comments have had the power of a 'support adminship' !vote all along. If the admin doesn't feel secure, they can wait it out, and are protected by the fact that the opposition to their adminship is ineffective until it reaches the critical mass of 25 signatories. It isn't reasonable to think that the admin is unfairly treated by the fact that opposition to their adminship is rendered ineffective until a difficult procedural barrier is overcome; that's obviously a mechanism that protects their status. If they don't feel like they need that protection, if the climate seems friendly to their adminship, they can relinquish it and start the RRfA.—Alalch E.17:32, 28 October 2024 (UTC)[reply]
I'm not sure we should understand them as quasi-votes, since it would be perfectly reasonable for someone to sign the petition because they think a re-RFA ought to be initiated, not because they think the admin should step down. That is, I can easily see someone putting their name on the petition because they believe a re-RFA is the right thing to do, not because they desire for the admin in question to be de-sysopped. But it's true that nothing is stopping an admin from "calling the bluff" and standing for re-RFA before the petition reaches 25 signatories. At this point, frankly, that doesn't look like it would be a bad move for our unfortunate first candidate. -- asilvering (talk) 19:27, 28 October 2024 (UTC)[reply]
The way the process is currently set up, you're right. But I would argue that it should be different (that's the idea I'm presenting): If you do not think that the admin should cease being admin, you should not sign the petition. On the material side, the petition should be presented as: "By signing you are stating that the administrator has lost your confidence"; and on the procedural side: "By signing you are stating that (because the administrator has lost your confidence and provided that he has also lost the confidence of many other editors) the administrator should undergo a RRfA". —Alalch E.11:09, 29 October 2024 (UTC)[reply]
It isn't impossible to constrain discussion. We are capable of setting and enforcing a rule that says "Signatures only. No diffs, no explanations, no discussion, no opposes". This might be fairer, since even a few words or a single diff could prompt "me too" votes from people who had no concerns of their own, and a diff or a brief comment could be taken unfair or out of context. It would probably be stressful for the admin, as people would be publicly expressing dislike without any reason.
Editors generally oppose efforts to prevent them from talking about other editors, though, so I doubt we'll end up there. More realistically, we could insist that any discussion happen on the talk page. WhatamIdoing (talk) 20:00, 29 October 2024 (UTC)[reply]
ArbCom manages to have strict rules about constraining discussion, and it does lead to more productive cases (read: not a shiftest). I would support a "Signatures only" rule, especially considering the opening comment should already be expected to have the needed context.A talk page discussion would be already lower profile and likely more calm, and ultimately look less like a !vote or like its own mini-RfA. Chaotic Enby (talk · contribs) 20:21, 29 October 2024 (UTC)[reply]
Any rule restricting what can and can't be said on the page needs to come with explicit instructions to this on the page and a clear statement of who is allowed to remove things that objectively break the rules (I'd favour "anybody"). Perhaps accompanied with a "you will be partially blocked from this page if you reinsert, without explicit advanced consensus, something removed." Thryduulf (talk) 20:46, 29 October 2024 (UTC)[reply]
That could definitely work. WP:RECALL doesn't need a set of clerks like the (much more complex) ArbCom cases do, if the only rule is "just leave a signature" or close to that. Also agree with the disclaimer, and good of you to be thinking of the implementation details already!I'm thinking of having a formal proposal with both the restriction on discussion and the shortened timeframe as independent options. Given how the WP:RECALL RfCs have been criticized for not being well-advertised, it might be good to bring this one up on WP:CENT. Chaotic Enby (talk · contribs) 21:55, 29 October 2024 (UTC)[reply]
Discussion will migrate elsewhere. ArbCom is mentioned as a counterexample, but discussion there is quite free-flowing, only formatted differently to avoid long non-constructive threads... but the stated problem here is not non-constructive threads, the stated problem is comments. That is completely different. "Discuss calmly and with measure" and "don't talk" is different. It will be possible to have an adjacent discussion on some other page or pages. And if you are blocked from the page, so what, what you added to the page, diffs and all, stays in history and can be viewed by anyone. —Alalch E.23:36, 29 October 2024 (UTC)[reply]
And if you are blocked from the page, so what, what you added to the page, diffs and all, stays in history and can be viewed by anyone.
I agree that a complete ban on discussion will result in the discussion happening elsewhere, but that's not necessarily a bad thing. Wherever there are humans, there will be gossip mongers, but gossip whispered between a few people (e.g., via Special:EmailUser) for a few days, or even for 30 days, is not as widely and as permanently destructive as accusations posted on the internet forever. WhatamIdoing (talk) 18:04, 30 October 2024 (UTC)[reply]
That elsewhere could just be the talk page, and it appears that it might just be that. Edit: All in all, "discussion elsewhere" + word limits + RfA monitor function preserved + "five uninvolved signatories first" latch mechanism could all add up to something good. I'm for trying. —Alalch E.22:32, 30 October 2024 (UTC)[reply]
It all depends on who you want to sign up to a petition. If it is only "editors who have independently decided that an admin's conduct should be examined", the only way is to disallow comments from both signatories and opponents. Otherwise many signatories will sign because they are convinced by the arguments, even if they never heard of the admin before. In that case, allowing only signatories to comment will dramatically skew the results and be quite unfair. In summary, allow everyone to comment or allow nobody to comment. Zerotalk02:10, 30 October 2024 (UTC)[reply]
I'd also like to raise another issue. We have created a risk-free way for editors to get back at an admin who has sanctioned them. I think that editors who have received a recent (definition?) personal sanction from an the admin should not be a signatory. Zerotalk02:10, 30 October 2024 (UTC)[reply]
I can see both sides of this. Perhaps a reasonable way forwards is to disallow someone from initiating a petition if they have received a recent (within the last 3 months?) personal sanction from the admin. They can still support a petition initiated by someone else, but perhaps only if 5 uninvolved editors have already supported. If there is a genuine issue this should be an easy bar to clear but it would make retaliatory petitions much harder to initiate and harder for them to succeed. Thryduulf (talk) 02:35, 30 October 2024 (UTC)[reply]
Maybe we could make it so that the first five signatures (other than the initiator) must not have been involved with any dispute in which the admin concerned acted in their capacity as an administrator within the last (1? 2? 3?) months. If five uninvolved editors are prepared to sign a petition that suggests it's more likely to have some merit than if no such group of five are? Thryduulf (talk) 02:39, 30 October 2024 (UTC)[reply]
Let's say it's day three and there are fifteen signatures. The first five signatories have not been involved in the discussed sense, followed by ten signatures from people who have been involved (they were the greater cohort that was waiting for the special signatures to add up so that they can add theirs; imagine ANI participants). One among the first five withdraws their signature ("I changed my mind after reading the talk page"). There are no longer five signatures from uninvolved signatories. What then? All's good? (Probably not.) Petition has failed? (Probably not.) Monitor halts signature collection only allowing signatures from uninvolved signatories, until one such additional signature is collected? (Probably not.) Monitor notes that the petition will be invalid unless at least one more special signature is supplied during the entire remaining period? (Maybe.) Monitor notes that the petition will be invalid unless at least one more special signature is supplied during a set period, for example three days? (Maybe.) —Alalch E.17:00, 30 October 2024 (UTC)[reply]
I hadn't thought of that scenario. The simplest option would just be a latch - once five uninvolved people have signed the petition is unlocked and remains that way for the duration. Thryduulf (talk) 19:03, 30 October 2024 (UTC)[reply]
As the two main proposals that editors seem to converge on (limiting discussion and shortening the petition timeframe) are essentially independent, I'm thinking it can be best to go for a two-part RfC, with the following questions:
Should input to WP:RECALL petitions be limited to signatures only?
Should the petition duration be limited to X amount of days?
There is also the possibility of having multiple options for each question. For the first one, an alternate proposal of limiting input to to a short statement per person was also suggested, while multiple timeframes for the petition could also be proposed. Chaotic Enby (talk · contribs) 22:59, 29 October 2024 (UTC)[reply]
I think a RFC like this needs to happen. I think the second bullet point is fairly self-explanatory, but the first needs more thought. On a recall petition, is there value in having a statement from the initiator? A statement from the admin being recalled? Statements from people bringing up new evidence? Statements/signatures from supporters? Which belong on the main page, and which belong on the talk page? If we impose a length limit, can anyone truncate statements to fit in it? Do we need clerks, arb style?
For example, I favor the initiator getting a short statement, the admin having unlimited length to respond optionally (hidden comment in the template that makes a section if they choose to respond), all recallers signature only on the main page, with limited commentary on the talk page, and any list of supporters with limited commentary on the talk page, no threaded discussion anywhere. Any editor except the initiator and the admin being recalled can move comments to enforce length/threading/talk page. This is not about my preference, but more saying that this bullet point can get really complex really fast, and we should think about that now in workshopping. Tazerdadog (talk) 02:04, 30 October 2024 (UTC)[reply]
Thanks a lot for the feedback! You're right that the first bullet point should definitely be clarified before the actual RfC.In my mind, the initiator would be able to make a short statement, with the rest being only signatures (as the point of the petition isn't to be its own RRfA, but only to gauge whether it has enough support). Regarding the admin responding, I think it (and other replies) should be reserved to the talk page, to avoid it becoming a RfA-lite where the admin has to respond to the claims to not be seen as suspicious. Chaotic Enby (talk · contribs) 02:20, 30 October 2024 (UTC)[reply]
If the admin is allowed a right of reply, but only on the talk page, it should be possible to see from just the main page whether they have chosen to respond or not. Regardless of where, everybody who has the right to comment (including the responding admin) should be subject to a word limit, although not necessarily the same limit. Thryduulf (talk) 02:30, 30 October 2024 (UTC)[reply]
In my mind, the initiator is no more or less important than anyone else who prefers to recall that admin, I prefer not creating a "first mover" advantage. So I'd rather just be strictly signatures only, or strictly "Short statement on main page without replies" for everyone.
I can get behind a word limit for the responding admin. I do think it's important that the admin have the ability to present their case in the same location that the initiator does. Tazerdadog (talk) 06:55, 30 October 2024 (UTC)[reply]
I agree with that as well, I just end up at "Initiator and all future signatures should be given same weightage" and "Maybe both should be on talk" as my preferences. Soni (talk) 05:20, 30 October 2024 (UTC)[reply]
I start with "someone should say why we're all here" and "I don't want everyone piling on with extensive commentary. I will concede that I create a first mover advantage as a consequence of those, but I think that's the best we can do. Either way, I think we can craft a RFC that presents all this fairly without too much difficulty. Tazerdadog (talk) 06:52, 30 October 2024 (UTC)[reply]
Ultimately, a "first mover" advantage makes sense in that, since they're starting the petition, they are responsible for explaining it. We don't need 25 redundant explanations, but we don't need an unexplained petition either, so it is logical that the creator of the petition be the one to state the case for it. Chaotic Enby (talk · contribs) 08:10, 30 October 2024 (UTC)[reply]
"The talk page will be open anyway", will that result in all the "pre-RRFA RRFA" stuff just happening there instead of on the petition itself? Anomie⚔07:49, 30 October 2024 (UTC)[reply]
Moving the discussion to a less prominent place behind the petition, plus a word limit as Thryduulf suggested, would definitely limit the "pre-RRFA RFA" stuff. Not everyone will go through long talk pages, making it less critical to respond than with the "in-your-face" discussion that currently runs in the middle of the signatures. Chaotic Enby (talk · contribs) 08:07, 30 October 2024 (UTC)[reply]
If it's mandated that no discussion happen on the petition page, I'm not so sure the petition's talk page would remain very much "less prominent". Sure, not everyone will bother to check the talk page, but knowing that's where discussion is I suspect anyone who would have pre-RRFA RFFA-ed as things are now would. Anomie⚔07:51, 31 October 2024 (UTC)[reply]
I don't think it's a good idea to start a two-part RFC so soon after we just ended a three-part RFC. Take note of the backlash to the third RFC; a fourth RFC will get even more backlash; a fifth even more. Levivich (talk) 16:45, 30 October 2024 (UTC)[reply]
But you really think, three days into the first petition, you've learned enough about this process to know how to change it for the better? There's no part of you that's thinking "it's too soon to draw any conclusions"? Levivich (talk) 17:33, 30 October 2024 (UTC)[reply]
I share Levivich's concerns here. Now's a fine time to take some notes, but we're 10% of the way through the first use of a process. We might learn something in the coming days, or in a second petition. We might also discover that the RFC question needs to be "Well, that was a disaster. All in favor of canning the idea completely?" WhatamIdoing (talk) 18:12, 30 October 2024 (UTC)[reply]
And this is why I said, above, We can start workshopping the RfC right now, but it's probably best to hold off opening the RfC itself for the moment given how heated emotions are. I do not claim to personally know exactly how to change the process, but we can already start discussing the shortcomings we can see, even if we are not going to open the RfC right now. Chaotic Enby (talk · contribs) 18:21, 30 October 2024 (UTC)[reply]
People have been proposing changes all over the place. Why not have a discussion that will hopefully bring up possible problems with proposed changes, even if it will be a while before any RfC should start? Donald Albury19:42, 30 October 2024 (UTC)[reply]
@Chaotic Enby: I've been thinking about how to format this RfC for a fair while. If someone has a better idea than yet another dedicated subpage, I'm all ears, because I'm not sure how else to deal with the number of proposals and changes people are asking for. theleekycauldron (talk • she/her) 18:44, 31 October 2024 (UTC)[reply]
I think subpages is fine, but we probably should try to limit the number of options to be voted on, in some way. Either by number or some other ways.
Say if a proposal is something like "For 2 future RECALL petition, the petition will not have any discussion. After this trial, you need consensus to make it permanent" - that's self contained and gives place to start off from. Much better than just trying to push through every change at once. Soni (talk) 20:56, 31 October 2024 (UTC)[reply]
That's the point of starting this discussion now. We're at the ideas stage, at some point after the first petition ends (and, if one happens, after the subsequent RRFA ends) this will move into the stage of collating those ideas that both could work and got some indication they might be supported and refining them into draft proposals. Once we have a rough idea of what and how many proposals there are is the time to work out the best structure for an RFC, as until we know those things we can't know what will and won't work. Thryduulf (talk) 00:39, 1 November 2024 (UTC)[reply]
One should exist for Authors to personally fill out a profile. Many book readers would like to know the "about" information about writers that have books published. 91.242.149.121 (talk) 09:15, 29 October 2024 (UTC)[reply]
If you're referring to the authors/editors of an article, editors already have their own user pages, which are accessible from an article edit history. If you're referring to the authors of books that merit Wikipedia articles, this isn't a place for people to tell about themselves(see WP:AUTO). 331dot (talk) 09:18, 29 October 2024 (UTC)[reply]
Allow IP editors to set preferences
IP editors now have the ability to turn on dark mode, which previously was limited to logged in users setting a preference. We should extend this concept to allow IP editors to set other prefernces such as disabling fundraising banners or whatever other preference they prefer. RudolfRed (talk) 23:33, 1 November 2024 (UTC)[reply]
Supporting preferences in general would mean the caching infrastructure could no longer be used for non-logged in users, which would have a big impact on the amount of computing resources required to handle Wikipedia's traffic. So I don't believe that general support is in the works. isaacl (talk) 05:40, 2 November 2024 (UTC)[reply]
They could 1. restrict preferences to a subset that won't interfere with caching; or 2. figure out a way to serve cache to everyone who didn't touch certain preferences. Aaron Liu (talk) 18:28, 2 November 2024 (UTC)[reply]
I've discussed this before so don't really want to get into the details again, beyond saying that making the servers do anything is more expensive than reading ready-to-go HTML content and sending it back. Please feel free to discuss your ideas with the WMF engineering team. isaacl (talk) 21:33, 2 November 2024 (UTC)[reply]
There was some talk in 2023 about a limited set of prefs. mw:Temporary accounts are only created upon editing, not ordinary readers. I can't remember whether they settled on creating the account at the time you open the page to edit, or if it's created only when you click the big blue Publish button, but we should expect only a few logged-out users to gain access that way. However, that requires getting temp accounts fully deployed everywhere, which will happen eventually rather than soon. (Fundraising banners can already be suppressed [for a week at a time?] via cookie; just click the button to make it go away.)
As for the desirability: You should believe Isaacl when he says that this is a lot more expensive and difficult than people think it 'should' be. WhatamIdoing (talk) 01:14, 6 November 2024 (UTC)[reply]
I don't see the slightest problem in restricting privileges like preferences to logged-in editors. If the default editing experience for IPs can be improved, that's fine, but if someone wants an experience different from the default, they already have a very simple way to get it. Zerotalk02:40, 6 November 2024 (UTC)[reply]
Comparison shopping with data from factboxes
As more information is put in Wikidata and is presented in Wikipedia's fact boxes, I think this opens a possible new feature or gadget similar to the comparison shopping offered by many e-commerce websites. As I visit the article Thailand, the factbox should have a little tick box to add this article to my personal comparison basket, and when I tick that box on another comparable object (using the same factbox template), say Chile, I should be able to view my current comparson set, presenting a table with two columns for Thailand and Chile, and rows for their attributes: capital city, main language, population, area, GDP, etc. LA2 (talk) 11:45, 2 November 2024 (UTC)[reply]
Idea to reduce issue with user pages being used for hosting a vanity page or advertisement
Some of the recent discussion on AN/I regarding Fastily and U5 closures centered on the challenges of properly addressing misuse of user pages. I believe the high volume of apparent misuse is causing difficulty in balancing protecting Wikipedia and taking due care in deletions. Anything that would reduce misuse (or reduce the consequences of misuse) should help relieve some of the pressure.
Thus my half-baked proposal below. The goal of this proposal is to reduce the attractiveness of putting up fake Wikipedia pages and holding yourself out to the world as having a page about you.
Proposal
The primary user page will automatically have the output of {{User page}} displayed at the top. Once a user becomes extended confirmed, they will have the ability to suppress display of the template. Extended confirmed users who abuse this by making an inappropriate user page can have the right to suppress display taken away by an admin. When first enacting this change, all current extended confirmed users will have the display suppressed, though they can enable the display if desired.
This is a Wikipediauser page. This is not an encyclopedia article or the talk page for an encyclopedia article. If you find this page on any site other than Wikipedia, you are viewing a mirror site. Be aware that the page may be outdated and that the user whom this page is about may have no personal affiliation with any site other than Wikipedia. The original page is located at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(all).
Above is the output of the template, for those unfamiliar with it.
That could be a good idea. For new users who might not know it, a message could also be added to inform them that drafts should ideally not be written on their main userpage, with a link to automatically move it to their user sandbox. Chaotic Enby (talk · contribs) 20:16, 5 November 2024 (UTC)[reply]
I don't have any objection to this in principle. I think the application of this is likely to get pretty hairy, though. And I think most people write promo drafts on their userpage because they don't know they're promo and don't know that's not the place for drafts - so I don't think this would really help. But if I woke up tomorrow and this was the status quo, I wouldn't be mad about it or anything. -- asilvering (talk) 20:35, 5 November 2024 (UTC)[reply]
After giving it more thought, one objection I can see is that enforcing a banner on people's userpages might not be well-received, especially since the target demographic (non-ECP editors) likely won't overlap much with the people who will take the decision. I agree with your explanation for why people write promo drafts on their userpage, and a way to gently inform them that that isn't the place might be better.Now that I think about it, we need an equivalent of U5 that isn't "speedy deletion" but "speedy move to sandbox" (with a message informing the user of what happened, of course). Now that would be helpful. Chaotic Enby (talk · contribs) 20:40, 5 November 2024 (UTC)[reply]
The main issues with user pages seem to be promotional drafts and non-Wikipedia uses (like fake election articles for alternate history forums). It's non merely an enwiki issue - while userspace pages aren't prominently visible, images uploaded for them are. It's a big problem for Commons to have spam and hoaxes mixed in with other images. I'm not sure there's actually a common problem with userspace pages being passed off as real articles; I don't object to this proposal, but I think other changes might be more effective. In particular, I would propose stricter rules and other changes for userspace, with the primary aim of reducing incorrect userspace usage to reduce admin work:
Edit filters disallowing commonly misused elements like external links, images, and infoboxes for new users in userspace. This would essentially kill userspace for fake articles and make promotional userpages less attractive. Maybe even have a fairly strict character limit for new users - that would allow them to have a bluelinked user page introducing themselves, but not enough space for their CV or fake article.
Prominent edit notices for userspace explaining restrictions and directing users to draftspace
Disable the "upload file" link in userspace. The vast, vast majority of crosswiki uploads from userspace are junk.
Better bot patrolling of userspace. This could include creating lists of new userspace pages for easier patrolling, or even automatic moves of likely drafts to draftspace.
Partial blocks from userspace for those who misuse it. This should be more akin in seriousness to an edit filter than a mainspace block.
Formally expand U5 to include any clearly non-Wikipedia usage, regardless of whether the user has mainspace edits, after other interventions reduce userspace usage overall. Obvious junk shouldn't have to go to MfD just because the creator has mainspace edits.
As to passing off user pages as Wikipedia articles, I have encountered it once in real life, and everyone in that conversation was convinced it was real until I started reading the URL more carefully. Admittedly, this was a while ago, and perhaps people are more sophisticated now, but I suspect it is still a bit of an issue, and one that would be easily stomped out with this change. — rsjaffe🗣️22:21, 5 November 2024 (UTC)[reply]
I do agree that there's lots more things that should/could be done and appreciate your list. Perhaps the discussants here could put together a package of changes to improve the situation, though approval of each one would be independent, as some items in the package may be more of an issue than others. — rsjaffe🗣️22:23, 5 November 2024 (UTC)[reply]
I particularly like the edit filter preventing links idea. A plaintext page without through links is (generally) essentially harmless. I don't like the idea of a character limit unless it could be just applied to the top-level user page, rather than subpages which can legitimately be used for draft development. Espresso Addict (talk) 06:35, 6 November 2024 (UTC)[reply]
This is mostly in response to the first point. When creating a new article in mainspace, the little popup on the side always invites me to create the article in my userspace instead. Help:Your first article#Where to start writing also recommends placing drafts in a user subpage. I could very easily see a new editor not understanding the difference between their main userpage and a user subpage. If we block things such as infoboxes, external links, or set word limits, we will be sending a very mixed message to new users. Maybe an edit filter to block new editors from adding external links to commercial/social media sites? (LinkedIn, YouTube, blogspot, what have you). There's very valid reasons why we don't block these types of links in general, but if we're thinking about userspace spam from non-contributors, then maybe? Lots of good faith users do end up adding links to these sorts of websites, but I also think discouraging them from doing that until they've been around long enough to learn the intricacies of WP:SPS isn't a bad idea. I don't really know edit filters, however, so I have no idea how practical this would be. I also don't have enough data to throw myself behind this suggestion just yet.
Not a fan of expanding u5. But maybe, for abandoned SPAs with a spammy vibe, a process similar to PROD? A user tags something as obviously unencyclopedic, and the creator has a month or so to return to their account and contest it, or else an admin reads the userpage, confirms it's never likely to be useful, and either a)declines the tag (so it can never be tagged again) or b) bins it on the understanding that should the creator return, they can request undeletion. MfD doesn't get clogged up with long-abandoned quasi-spam, and it limits the risk of biting newer contributors since it wouldn't work on them. This won't do anything for active spam-like users, but neither does U5, seeing as they can just re-create the page as many times as they'd like before getting inevitably blocked. (And then we go back to userspace prod). There's probably flaws with this idea. I could absolutely see somebody trying to abuse it in the way U5 is abused. The most obvious way is if two editors get into a dispute, one of them is blocked, and the other tries to delete their userspace now that their "enemy" is gone. I like to think that would be noticeable, however. Also, admins would still be required, and thus required to read the pages before deleting them. If the admin fails to do so, that would be very bad.
I like the idea of removing the "upload file" link in userspace. I also think we should remove it in draftspace. I also think we should make the "upload to commons!" link less prominent. A few gours ago, I nearly accidentally uploaded a non-free book file to commons; it was only once I got to the second page when I realised I'd mistakenly clicked the giant blue box as opposed to the tiny grey one. If I'm doing that, then goodness knows what a new user who doesn't understand the difference between their own work and a screenshot is thinking. (And that's just talking about good-faith newbies who are still hunting for clues. Commons does not need anymore copyvio spam than it already puts up with.) This also would not stop users from adding images to their userspace. They would still have other ways. It would merely slow them down, force them to ask questions, and hopefully learn about copyright. GreenLipstickLesbian (talk) 09:46, 7 November 2024 (UTC)[reply]
This isn't a good template for this use. The header is harmless, but of the main text only the first sentence (to the effect of "this is not an encyclopedia article") is relevant. That sentence is needed, though, as well as a statement that this page hasn't been reviewed or quality-checked (even to the extent that normal Wikipedia articles are).Also, we don't need the option to let the page owner turn it off for everybody else, just a handy gadget to hide it for logged-in users who don't know to edit their own css. Without that, we could do this right now without the proposed software changes, which probably would never happen anyway. —Cryptic22:29, 5 November 2024 (UTC)[reply]
Oh, and I see no reason at all to limit it to the primary user page. I don't think I've seen anybody passing off a main user page in their "now read our article on Wikipedia!" link, but have to sandboxes and other subpages a couple times. —Cryptic22:34, 5 November 2024 (UTC)[reply]
Is there any way to get the software to display the namespace in User: and User talk: the way it shows up for every other namespace? Seems like that would be a step towards the goal here. Folly Mox (talk) 00:49, 6 November 2024 (UTC)[reply]
What is the onboarding (or whatever it's called) doing in the way of suggesting very new editors start user pages by the way? I did wonder if we were inadvertently inviting users to make a profile in their first or second edit, and then immediately deleting it U5 with unfriendly messages. Espresso Addict (talk) 06:59, 6 November 2024 (UTC)[reply]
Unless things have changed in the twelve months since I tested the new user signup flow, accounts are presented with a couple messages about Suggested Edits, then land at Special:Homepage. I don't remember there being (and definitely didn't screencap) anything related to creating a userpage. Folly Mox (talk) 11:19, 7 November 2024 (UTC)[reply]
It is, however, a pretty normal impulse to have, creating a userpage. Social media and various apps outright make you do it before being able to do anything else, and many newcomers will have been trained on that kind of behaviour. Also, if you're nervous, userspace edits feel safe, like you're not disturbing anybody while you're mucking around. -- asilvering (talk) 14:18, 7 November 2024 (UTC)[reply]
It's something that is encouraged in in-person training for new editors. A new editor with a userpage tends to be treated less harshly by some new page patrollers than one whose name is a redlink. Thryduulf (talk) 19:00, 7 November 2024 (UTC)[reply]
@Folly Mox, Asilvering, and Thryduulf: Thanks, Folly Mox. I think we need more advice on what the top-level user page may be used for, aimed both at new editors trying to create a profile and, perhaps more importantly, at patrollers. I've seen user pages that were entirely appropriate even for an editor with no other edits ("Hello world, my name is EA, I'm excited to edit Wikipedia!" sort of thing) being tagged G11/U5 by patrollers. (As far as I can tell, some patrollers think U5 is for anything created by a user with few non-userspace edits.) Asilvering writes, "if you're nervous, userspace edits feel safe", and I've found new patrollers think the same, it's a safe space to patrol without offending anyone who knows how to complain. And the flipside to Thrydulf's "A new editor with a userpage tends to be treated less harshly by some new page patrollers than one whose name is a redlink" is that patrollers are suspicious that a blue-linked user page is just the first step in a campaign of terror spam. Espresso Addict (talk) 23:09, 7 November 2024 (UTC)[reply]
Is there an editnotice for new users when they go to edit their userpage? I don't think there is. I don't see one when I try to edit mine, at any rate. -- asilvering (talk) 23:27, 7 November 2024 (UTC)[reply]
I'm getting the impression that some don't speak English at all and have used AI to draft something. Certainly that's true of promotional autobios submitted to draftspace in perfect American Marketing Speak, where I sometimes find it is impossible to communicate with the creator because they don't speak plain-old (British) English (and I don't speak their language). Espresso Addict (talk) 02:14, 8 November 2024 (UTC)[reply]
Okay, so this is a very barebones proposal at the moment, and I'm looking for thoughts into it, especially about viability and how likely this would be to gather consensus. This seems like the right place. Essentially, the idea I'd like to develop is allowing requests for the researcher group. At Special:ListGroupRights, it has the three rights commonly referred to as viewdeleted, as well as apihighlimits. This was discussed a bit at Wikipedia_talk:Requests_for_adminship/Archive_269#Temperature_check:_Applying_for_the_Researcher_right. Essentially, this would add a third section to WP:RFA, perhaps called Requests for Researcher, and would follow the same general process as an RFA, compliant with the WMF's requirements for viewdeleted access. Unlike other unbundling proposals, this includes only viewing rights, and while it would probably be a fairly rare ask, it would avoid many of the issues that plague other unbundling proposals, since it does not necessary unbundle actions, just viewing permissions, meaning it doesn't touch the block/delete/protect triad of rights that will likely never be unbundled. EggRoll97(talk) 00:09, 6 November 2024 (UTC)[reply]
The WP:RESEARCHER right, since its inception, has required approval from the WMF (specifically from the Legal department, if memory serves). I suspect, but don't know for sure, that this approval requires signing contracts about protecting privacy, etc. It sounds like your plan is to make this userright available to more people, with fewer controls. Is that your goal? WhatamIdoing (talk) 03:36, 6 November 2024 (UTC)[reply]
@WhatamIdoing: Based on the general response from the WMF, we (the community) are allowed to use it as a normal usergroup, if we wish, based on Joe Sutherland's response of Generally you all can do as you want with the Researcher right, though of course Legal will require that anyone who receives it still pass some form of RfA-like process. It historically was only given to those who signed NDAs with the WMF, but as of now is unused and the WMF has indicated they are fine with us using it. I would say the controls would actually be greater, since it would require anyone seeking it request community approval. EggRoll97(talk) 06:05, 6 November 2024 (UTC)[reply]
I imagine the usecase would probably depend, and might need to be somewhat flexible (similar to how those who make a request for adminship generally have areas they're requesting the tools for), though it should serve to provide some benefit to others. I imagine good use cases might include those who work with LTAs, SPI, edit filters, or other areas where the ability to view deleted contributions would enable them to make a better contribution to the project and where a good case can be made that they are handicapped by its absence, using the wording that ArbCom in 2008 used about viewdeleted. Overall though, I'd think it would be very much still up to the community at large to determine "is this a good use-case, or is there no reason to actually grant this?". EggRoll97(talk) 06:56, 6 November 2024 (UTC)[reply]
Right now, the process is closer to provide your real name, sign a legally binding contract, and have a good reason, probably involving paperwork showing approval from your Institutional review board.
I'm not sure your use cases are realistic. People working with LTAs need a block button. SPI needs more CheckUsers. The edit filter managers have to be admins. WhatamIdoing (talk) 07:18, 6 November 2024 (UTC)[reply]
I agree with WhatamIdoing that those people with a genuine need to view deleted material are usually admin or admin+ already. There's some scope for research on what WP deletes, which I suppose is why it has been referred to as "researcher", but that's not really benefiting the community directly. Espresso Addict (talk) 07:59, 6 November 2024 (UTC)[reply]
I agree this would be very useful for non-admin EFMs. I asked xaosflux about this once upon a time - he raised some pitfalls at the time. My feeling is that the use case is too niche for most to feel it's worth the community time needed to develop a process around this, when probably less than 10 people will ever hold this right. ProcrastinatingReader (talk) 18:43, 6 November 2024 (UTC)[reply]
I wonder if, similar to how the import right was assigned without necessarily having a dedicated process behind it, it might be easier and less of a burden on community time to simply have individual requests at WP:VPP for the researcher right if it's that niche of a usecase. The usecase you describe was actually part of my motivation for making this. EggRoll97(talk) 21:42, 6 November 2024 (UTC)[reply]
As just a bit of an addendum to the previous comment, I checked the listing of all EFMs and checked through which ones are non-admins. We have a total of 15 non-admin accounts that have EFM. Of those, 8 were granted the right by a consensus discussion, 5 were self-granted as the user was formerly an administrator, 1 is a bot (so technically 14 human EFMs), and 1 was granted the right for bug checking(?) with a user talk page discussion. I imagine your estimate is quite right, in that case, since the 5 who self-granted as admins I believe can simply ask for their admin rights back at WP:BN if they need viewdeleted. The bot obviously doesn't need it, so that leaves 9, at least for that particular usecase. EggRoll97(talk) 21:55, 6 November 2024 (UTC)[reply]
Short note on this: I don't think we should not use that group for anything from the community and once no longer required it should be removed. We could make a process for a community-managed group that allows viewing non-suppressed deleted content, however the approval process will need to be "rfa like" to meet foundation requirements. It would need not be strenuous and should be able to get by so long as it: accepts both support and opposition feedback from the community, be able to measure that appropriate support exists, be well-advertised, and be well-attended. — xaosfluxTalk18:59, 6 November 2024 (UTC)[reply]
Example is our RFA system, which we could even use the existing system with an option that someone is only running for "view deleted admin". If it ran for at least a week, had at least 25 attendees, and had good consensus (i.e. ~2/3 support) think that would more than suffice. Could be assignable by 'crats. — xaosfluxTalk18:59, 6 November 2024 (UTC)[reply]
So if I follow you correctly, the ideal path would probably involve creating a separate group with the permissions duplicated, and some form of "request for view deleted" being added to WP:RFA? EggRoll97(talk) 21:42, 6 November 2024 (UTC)[reply]
Creating "Machine Wikipedia" as an edition of Wikipedia
Hi, according to Tim Berners Lee's proposal, that is "Web 3.0" or semantic web, we should make our existing web machine-readable. But current editions of Wikipedia (English, French, etc.) are not machine-readable. Even though "Wikidata" provides some "structured machine-readable data", it does not implement Web 3.0, because Wikidata only provides structured data for one concept and the article may contain many concepts that are not included in its Wikidata item.
So I propose to create "Machine Wikipedia" like other editions of Wikipedia (such as English) which is written in the "machine language", e.g. triples of RDF (Resource Description Framework). This way, Chat-bots and other machines can access required information more accurately and more conveniently. This new edition of Wikipedia (Machine Wikipedia) can be filled with RDFs, both by humans and by artificial intelligence using natural language processing (NLP). Thanks. Hooman Mallahzadeh (talk) 10:08, 7 November 2024 (UTC)[reply]
Sigh. Since I'm genuinely not sure whether you're aware, I'm going to head off with the obligatory remark that a sizable plurality of editors are either highly skeptical of or firmly oppose operation of the Chat-bots and artificial intelligence using natural language processing (NLP) you see as the primary benefactors of this proposal—either as they presently exist, or in principle. That is to say, I would not get invested in this proposal, as the benefits you envision are already seen instead as clearly negative outcomes by much of the community.
I'll give fair warning that I am not really volunteering to have you pitch me on why these things are actually good, but I just don't want you to get your hopes up. Remsense ‥ 论11:00, 7 November 2024 (UTC)[reply]
@Folly Mox I propose to change the project name from "Abstract Wikipedia" to "Machine Wikipedia" to match Tim Berners-Lee's vocabulary, and finally add it an interWiki like other editions of Wikipedia. We can call the goal article "Machine article".
I should note that extraction RDFs from an article by humans needs some expertise, i.e. this is an encoding process, but the product of this extraction process is very simple, it contains many lines of RDF triples, and we call that "Machine article".
@Gråbergs Gråa Sång, Convenient Discussions does that (after). Beneath each comment on a talk page are the options Reply Edit Thank. If you highlight some text in the comment, Reply changes to Quote, and it automatically includes the text in your reply formatted with Template:TQ. I like CD because it shows signatures before the comment, which has made it a lot easier for me to follow threads. Schazjmd(talk)14:52, 7 November 2024 (UTC)[reply]
For a by default feature that would benefit to all users, the Editing team has a thank button on the works. This deployment is currently blocked as this "Thank" button is dependent of other design changes. These changes have been deployed to 50% of users at English Wikipedia; we have to make it a default component. I'm a bit behind schedule regarding this deployment (listed as T379264) as other priorities came up. If you think these design changes and the thank button would be welcomed, I more than welcome support to prioritize this! Trizek_(WMF) (talk) 14:57, 7 November 2024 (UTC)[reply]
Having started some Wikipedia articles and added to others, I have the following questions and suggestions:
Why are there four different reference templates, when they all have roughly the same content?
Why does one template call it “Journal”, and another call it “Work”?
Why does there need to be a Page slot and a Pages slot? (printer drivers handle both together)
Should there not be one uniform format for all references when published? (see "Notes", David Graham Phillips: six different references, six different formats)
I suggest there be one reference template that has places for all necessary content, and that all references follow the same format when published:
Template
Title of source _________________ URL ___________________
Last name of source creator _________________ First name ________________________
News agency _____________________ Website name ___________________________
Name of journal, magazine, newspaper, etc. ___________________________ Volume _____ Issue _________ Page(s) ________
Name of publisher ________________________________ Location of publisher _________________________
Date source published __________________ Date source accessed____________________
Ref name ________________ Ref group __________________ Ref ID for anchor ___________________
There are quite a few more citation templates, it is just the four most commonly used that are available in the tool bar. All of the citation templates use the same set of fields, and you can build a citation from scratch using Template:Citation. The four citation formats available in the tool bar just start you with the fields most commonly used for each type of citation. You can leave fields empty, and you can add other fields as needed, as is needed when citing a chapter in a book, for instance. Donald Albury18:53, 7 November 2024 (UTC)[reply]
WMF
The Asian News International vs. Wikimedia Foundation situation
Wiki for Human Rights is organizing a call for South Asia, East, Southeast Asia and the Pacific communities to discuss the Future of WikiForHumanRights on October 24 at 10 UTC.
Campaign Events tool: a call with the Indonesian communities will be hosted on October 25.
Tech News: In issue 2024/42, read about the removal of the Structured Discussion extension (also known as Flow), work on making text searches easier, and more. In issue 2024/43, read about improvements to mobile app navigation, temporary accounts pilot details, the Content Discovery Experiments, and more updates.
MediaWiki: The latest monthly MediaWiki Product Insights newsletter is available and include updates on Wikimedia’s authentication system, research to simplify feature development in the MediaWiki platform, and more.
CampaignEvents extension: The CampaignEvents extension provides tools to create, manage, and promote collaborative activities on the wikis, such as edit-a-thons, meetups, and more. You can visit the Deployment page to learn how to get the extension on your wiki.
New Content Translation feature: Translators using Content Translation on wikis with mobile support can now customize their article suggestions with 41 filtering options. This feature helps translators find relevant articles based on their interests for translation.
Temporary Accounts: Temporary accounts will begin rolling out on October 29 to production wikis with an aim to do a complete deployment by May 2025. You can see the deployment plan and timeline on the project page. As we rollout this change, it is likely that some tools (gadgets, user scripts, templates and bots) will be impacted by it. We have a developer FAQto help developers with making necessary changes to their maintained tool(s). Please let us know on our talk page if you have any tool in mind that may need updating or if you need help with updating your maintained tools.
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. Let askcacwikimedia.org know if you have any feedback or suggestions for improvement!
Given that it's recent (May 2024) and it has suggestions directed at Wikimedia Foundation, I was just wondering if Wikimedia Foundation is aware of this article. And I am not asking with respect to editor conduct, but with respect to any potential initiatives (such as partnerships with potential volunteer experts to audit few articles). Bogazicili (talk) 19:12, 4 November 2024 (UTC)[reply]
Here is a quick overview of highlights from the Wikimedia Foundation over the first half of November 2024. Please help translate.
WikiCelebrate Mārtiņš Bruņenieks
Upcoming and current events and conversations Talking: 2024 continues
Commons Community Call: The first community call with Wikimedia Commons volunteers and stakeholders to help prioritize support efforts for 2025-2026 Fiscal Year will take place on November 21. The theme of this call will be about how content should be organised on Wikimedia Commons. The call will be hosted by Chief Product and Technology Officer Selena Deckelmann.
Wikifunctions: The Abstract Wikipedia team is working toward a rewrite of our backend services in a different programming language, likely Rust. More status updates.
Temporary accounts: Logged-out editors on 12 wikis, including Norwegian, Romanian, Serbian, Danish, and Cantonese Wikipedia, receive temporary accounts now. This new account type enhances the privacy of logged-out editors and makes it easier for community members to communicate with them. Read the new Diff post to learn more about temporary accounts.
Mobile apps: The Mobile Apps team has released an update to the iOS app’s navigation, now available in the latest App store version.
Admin Retention: A survey on Wikipedia Administrator Recruitment, Retention, and Attrition is open until November 11. As part of the Foundation's 2024-2025 Annual Plan, the research team and collaborators are studying recruitment, retention, and attrition patterns among long-tenured community members in official moderation and administration roles.
Knowledge is Human: The campaign web page, which educates visitors on Wikipedia’s model and why it’s trustworthy, has earned over 140,000 clicks. The campaign has increased pageviews on WikimediaFoundation.org by more than 50%.
Annual Goals Progress on Equity See also a list of all movement events: on Meta-Wiki
WikiCelebrate: From making a minor maintenance edit in 2005 to being one of the most appreciated Wikimedians in the Central Eastern European (CEE) region: this month we celebrate Mārtiņš Bruņenieks.
Future of Language Incubation: As part of a new Future of Language Incubation initiative to support language onboarding, Wikipedia is now live for five languages: Pannonian Rusyn, Tai Nüa, Iban, Obolo, and Southern Ndebele.
Global Advocacy: Reflecting on the anniversary of the EU’s Digital Service Act (DSA), Wikimedians share successes and public policy priorities at digital rights Global Gathering event, and more global advocacy updates.
Fundraising Report: Our annual fundraising report for the 2023-2024 fiscal year is published. Last year, we had over 8 million donors giving an average donation of m:Fundraising/2023-24 Report0.58. We ran campaigns in 33 countries, 18 languages, and received donations from over 200 countries.
I know this will be completely ignored especially considering corporations who don’t care at all about user’s privacy like Google but I will say this anyway. I want all the edits I have made reverted. I want everything I have added onto Wikipedia removed.
I believe it is my right to privacy and just as people are allowed to add content to Wikipedia they should also be allowed to remove content they have added. 92.9.187.249 (talk) 22:11, 21 October 2024 (UTC)[reply]
Whenever you edited Wikipedia in the past, you were informed in writing with each individual edit that you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 4.0 License and GFDL. That was a legally binding agreement that you accepted with each edit. Accordingly, you have no such right and no basis for making this request. Cullen328 (talk) 22:18, 21 October 2024 (UTC)[reply]
Ah yes. The good old terms and services trick. Well, I am not surprised. Well then, you continue editing Wikipedia if it makes you feel good but as for me well I am getting out of what I consider a digital rubbish can set on fire. With that being said safe travels fellow internet surfers. This is me finally signing off from this site once and for all! 92.9.187.249 (talk) 22:36, 21 October 2024 (UTC)[reply]
It is not a "trick". It is a legal agreement that you voluntarily entered into every time you made an edit, and it is essential to the success of the #7 website on earth, with page views exceeding ten billion per month. I hope that you find a hobby that will be more satisfying to you. Cullen328 (talk) 23:28, 21 October 2024 (UTC)[reply]
Not to minimize the licensing issue, but there's also a practical side to this. Let's say you created an article some time ago and over the ensuing years, multiple people continued to edit it. A good example from my own editing might be The Lincoln Project. I created it four years ago but at this point only 7% of the text is mine. Even assuming we wanted to revert everything I wrote, how could we possibly unravel that and leave anything coherent? RoySmith(talk)23:35, 21 October 2024 (UTC)[reply]
This being an IP address, we have no way of knowing who was editing from it when past edits were made. For all we know, the person making this request only just gained access to this IP address today, and is actually asking us to remove someone else's work. BD2412T01:09, 22 October 2024 (UTC)[reply]
I wonder if the IP regrets not the edits, but the fact of not logging in (and thus exposing the IP address). I clicked through a handful of edits, and they seem to be quite ordinary, with no obvious privacy implications (e.g., punctuation fix). If hiding the IP address is what's actually wanted here, then it is conceivably possible that this could be accomplished somehow (e.g., Wikipedia:Revision deletion) without actually removing the content itself. WhatamIdoing (talk) 04:02, 23 October 2024 (UTC)[reply]
It seems to me that the IP was upset because of this filter action; OhNoitsJamie almost immediately implemented the IP's changes, but perhaps the IP did not notice this? --jpgordon𝄢𝄆𝄐𝄇04:21, 24 October 2024 (UTC)[reply]
It is an interesting problem in that the inability to apply the 'right to disappear' might be a problem for EU editors. Reverting 360 edits is trivial compared to some 'right to disappear' actions needed; for instance, a person participating in a Clinical Trial asking that all information about them be removed from all databases - completely non-trivial, and completely doable via approved procedures at pharma companies. --User:Ceyockey (talk to me) 02:53, 25 October 2024 (UTC)[reply]
I also believe that you agreed to this. If you want everything reverted, why did you add it in the first place? I am agreeing to the following terms by sending this message:
By clicking "Reply", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 4.0 License and GFDL. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Which means that once it is put, you can't take it back, the word irrevocably in the legal terms is what is stopping you. Also, you have an IP address instead of an account, which means that again, you may be removing hundreds of people's work, and they might actually want that. Hellow Hellow i am here16:51, 25 October 2024 (UTC)[reply]
Even when people agree to something, they sometimes come to regret it later. That's okay. They're stuck with (most of) it in this case, but it's okay for them to be sorry about their past decisions. WhatamIdoing (talk) 17:25, 25 October 2024 (UTC)[reply]
I agree. If "irrevocably" wasn't in the legally binding contract, I would be on their side. However, it is, and so once you have added it it is too late to remove. Hellow Hellow i am here17:40, 25 October 2024 (UTC)[reply]
And while if a company has your personal information they must delete it at your request, you gave the Wikimedia Foundation no personal information, and instead research, or fixed typos. To follow up, it is ridiculously hard to undo your edits if someone already edited over your edits. Hellow Hellow i am here16:54, 25 October 2024 (UTC)[reply]
Finally, this IP address has created several articles, which would be deleted (the creation of an article is an edit) which means that every created article by this IP address would be deleted, which is something us Wikipedians won't accept. Hellow Hellow i am here17:00, 25 October 2024 (UTC)[reply]
The OP's request as originally worded violates Wikipedia's Terms of Use and would be pragmatically impossible to implement in general for reasons others have pointed out. But it is interesting to explore how far their request could accomplished, especially in light of the GDPR. There's a page at Mediawiki:GDPR (General Data Protection Regulation) and MediaWiki software that discusses some of the issues related to deleting a user's contributions and their IP addresses. A hyper-liberal interpretation of the GDPR and what private data means would make using Wikipedia impossible. For example, the OP's interpretation where all content they've added somehow involves their privacy is absurd: a typo fix in an article, for example, does not have anything to do with privacy and is not private data. WhatamIdoing's suggestion that their IP address be hidden in histories, etc., is reasonable and doable. But this redaction cannot reasonably for practical purposes extend to mere mentions of your IP address everywhere, for example, in comments by others. And the comments that we don't know if the same person made all the IP edits is a good one. Imagine if a handful of our most active editors decided to do what the OP wants, it would eviscerate Wikipedia. I am not versed in EU law but would surely hope the nature of collaborative websites are factored in to how the GDPR is interpreted by the courts and some technical common sense would prevail. Plus, I don't see how a GDPR right to disappear would overrule the legal agreement you made every time you made an edit. Without further clarification, we don't know what the OP wanted or why but it is an interesting topic to see how a "right to disappear" could actually be implemented and to what extent. Jason Quinn (talk) 13:11, 26 October 2024 (UTC)[reply]
Check the notablity of this article and after approval then delete the speedy delete template
Hello dear Wikipedians. This article (Najmeddin Shariati) was created once before in an unprincipled manner and without citing reliable references. For this reason, it was deleted under the title of not notablity and fame with the Wikipedia:Articles for deletion. But this time I created it with basic editing and citing more than 20 reliable references from official Iranian news agencies (Because this person is Iranian) that independently covered the news of this person. Please review this article and its references and after approval, delete the speedy deletion template. This person's article is available in Persian Wikipedia, and its notablity and fame was confirmed by the administrators and editors of Persian Wikipedia according to the reliable sources mentioned in it. If you think this is a stub article. Add the stub template to it and let it stay. The final decision is yours. very thanks 4ipid (talk) 22:17, 27 October 2024 (UTC)[reply]
@SafariScribe, Have you considered the value of a custom reason in these cases? The draft now has two identical messages at the top, neither of which says anything about interviews. (Interviews are usually reliable; the point of WP:Interviews is that when the subject is being interviewed about himself, his answers – but not the introduction, questions, or other content that came out of someone else's mouth – isn't independent. If you are interested in this subject, then feel free to join the conversation at Wikipedia talk:Notability#Can we please settle on some guidance for interviews?) WhatamIdoing (talk) 05:29, 31 October 2024 (UTC)[reply]
Question regarding copyright, spoiler, summary
In Japan, police in Miyagi prefecture recently arrested members of a company which post spoiler of copyrighted shows onto the company's website, and try to earn ad revenue.
Copyright holders and interest groups claim they permissionlessly transcribed character names, dialogue, actions, scenes, and plot which reveal the whole view of the story to an extent beyond quotation and is obvious copyright violation, damaging rhe right of copyright holders as it will lower the desore of people paying proper price for the content and lead to people not actually watching the movie itself.
Given that while Wikipedia is a nonprofit site, and sunmaries of fictional works on Wikipedia usually wouldn't include direct quotation of dialogue of characters inside performance, many such articles still include very extensive summary on full plots of the fictional works they are describing, and all content published on Wikipedia unless otherwise specific should be reusable for profit, is there any risks that summary section of articles currently included in Wikipedia could be deemed copyright violation? C933103 (talk) 12:37, 30 October 2024 (UTC)[reply]
The law is quite clear in making a distinction between plot summaries (even including spoilers) and the like, and actual copyright violations such as extensive transcriptions of dialogue. We are at no risk. --Orange Mike | Talk12:54, 30 October 2024 (UTC)[reply]
@C933103, I would prefer that articles included "full plots of the fictional works" but not "very extensive summaries". When I run across them, I try to take a minute or two to remove overly detailed content.
That said, what I really dislike, and what might actually be a copyvio problem, is a "plot summary" that is just a word-for-word copy of the publisher's marketing blurb. They're unlikely to complain (free advertising!), but it's IMO a disservice to the reader, and would be IMO undesirable even if the publisher had formally dedicated that text to the public domain. WhatamIdoing (talk) 18:35, 30 October 2024 (UTC)[reply]
To expand on the first point, often a more concise plot summary that succintly outlines the work's story is a lot more useful than something that is painful to read since it's weighed down with details only superfans are interested in.
That is what I would like to believe that the law is clear enough, but screenshot provided by relevant party (which is censored so text cannot be read) seems to indicate the website they arrest the operator this time do not actually publish dialogues of the original work line by line, instead look like a prose style description of the original work. So I am not sure about the degree of violation on that website that lead to the conclusion of that website is considered a transcription of original work and thus copyvio. C933103 (talk) 01:51, 31 October 2024 (UTC)[reply]
In most countries, ordinary copyright violations are a matter of civil law (i.e., not criminal), so the police aren't involved and nobody gets arrested. However, it is sometimes more complicated than that; for example, if someone breaks into a computer system to copy the author's original files (=a crime) and then posts them on the internet in violation of copyright law (=a civil tort), then the police could arrest the person for breaking into the computer system, but not for the copyright violation. Also, a creative lawyer could suggest others: perhaps the circumstances suggest fraud, or perhaps it's computer piracy. WhatamIdoing (talk) 05:41, 31 October 2024 (UTC)[reply]
Japan made copyright violation a criminal offense since year 2018 after the signing of TTP (Now known as CP-TTP) trade pact, according to my understanding. C933103 (talk) 00:32, 1 November 2024 (UTC)[reply]
((uh-oh ... IF the above "attempted" wikilink does not work, then ... maybe try thisinstead.))
By the way, perhaps that above-mentioned "Talk:" page section -- which is brand new, right now -- might be difficult to find, in the future ... if/when it has been archived.
(Perhaps even when using the link displayed as "this", where, besides those [ill-advised?] square brackets in the section name, having been "escaped" [in some way] by using "percent-5B" and "percent-5D", it also uses a full URL starting with "https" instead of a syntax involving "double"square brackets.)
@Schazjmd: It's not always that simple. "Just fixing the target" can be a real problem if someone reorganizes the target article and changes sections' titles. Been there, experienced that. CiaPan (talk) 18:37, 6 November 2024 (UTC)[reply]
Let me clarify what I meant: fix the target on the redirect page. If the redirect page is pointing to a section that has been renamed, change the wikilink on the redirect page to the new section name. Schazjmd(talk)18:44, 6 November 2024 (UTC)[reply]
Fictional flag used in multiple places
This problem is not unique to the English-language Wikipedia, but I'm starting here because this is my native language. I'm bringing this to an explicit discussion here rather than just editing so that we can build an explicit consensus that I can then show the other Wikipedias.
I think this is a more general case of Commons is not a reliable source. I often see people take images in commons completely at face value, including them in articles without any real source. Commons has very different rules than enwiki. They are mostly concerned with copyright and licensing, and (intentionally) make no attempt to verify that images are "real" or that the descriptions are factually correct. That's just not their job. But it is our job when we use one of their images in an enwiki article. RoySmith(talk)16:21, 7 November 2024 (UTC)[reply]
I belong to an organization which has a flag. The design is described in exquisite detail in our charter ("white stripe, whose width is one-sixth of the hoist", that kind of thing). I sat down one day and carefully drew an example in a drawing app, taking pains to get the geometry exactly as described. The charter (long) predates things like Pantone, but I did consult with a commercial artist to get their input on the correct RGB values to use for the colors and attempted to get all the people who produce material for us to use these "official" versions. Eventually I gave up and accepted that people will just copy-paste from whatever is handy. Now I just amuse myself by tracing the lineage of various bits of marketing material by which version of the flag they've got. But, yeah, we should do better than that. RoySmith(talk)17:25, 7 November 2024 (UTC)[reply]
You are invited to join the discussion at WP:HD § Red Links are All blue now. -- Marchjuly (talk) 06:10, 1 November 2024 (UTC)
icon next to redirects (similar to the icon next to external links). --Ahecht (TALK
White
Silver
Blue
Pink
Gold
Red
Green
Skyblue
Purple
Turquoise
Black
Agree, but only slightly. If you added the letters, it would be better. Also, a solution to your region-basing could be to do a Language-based (like "O" for "Office" would become "S" for "Schoolhouse" in a theoretical "Reversed English") The Master of Hedgehogs (converse) (hedgehogs) 14:33, 17 October 2024 (UTC)
Needs wider discussion but until then, {{EFR}}. The basis for this request is on one accidential removal of a colon. This seems more like something that might be raised at Phab if nothing else, but I don't think we need a filter to warn people to use 
Liechtenstein flag template (it only detects the relevant wikitext)) Aaron Liu (talk) 17:02, 2 November 2024 (UTC)
.jpg)
.jpg)
Moved from WP:VPT
Discussion ongoing: limiting petition participation to signatures
wikimedia.org know if you have any feedback or suggestions for improvement!
CiaPan (talk) 18:37, 6 November 2024 (UTC)
