Wikipedia:Village pump (idea lab)/Archive 62

• Village pump
  • Policy
  • Technical
  • Proposals (persistent)
  • Idea lab
  • WMF
  • Miscellaneous

Village pump (idea lab) archive  

This page contains discussions that have been archived from Village pump (idea lab). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.

---

< Older discussions · Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62

Can we consider EC level pending changes?

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. Awesome Aasim 16:54, 27 September 2024 (UTC)

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)

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. Awesome Aasim 22:00, 27 September 2024 (UTC)

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é Couriano v^_^v ^{threads critiques} 15:37, 28 September 2024 (UTC)

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. Awesome Aasim 16:22, 28 September 2024 (UTC)

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)

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. Awesome Aasim 18:26, 29 September 2024 (UTC)

@Aaron Liu 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. 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. Mach61 19:53, 29 September 2024 (UTC)

Untrue, articles in ECR topics can and are pre-emptively locked.

Could you add an example? There is a long list of declined RFPP requests for arbitration enforcement. Aaron Liu (talk) 20:42, 29 September 2024 (UTC)

See this exchange between an admin who refused to protect based on ECR due to a lack of disruption and a (former) admin who explained to them otherwise. Mach61 19:46, 1 October 2024 (UTC)

Thanks, I get the "can" now. Aaron Liu (talk) 20:59, 1 October 2024 (UTC)

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)

Because there are enough people who dislike or distrust pending changes that it's hard to get a consensus to use it. See, for example, Wikipedia:Village pump (proposals)/Archive 183#RFC: Pending-changes protection of Today's featured article. Anomie⚔ 14:41, 28 September 2024 (UTC)

Well, gee, I fucking wonder why? —Jéské Couriano v^_^v ^{threads critiques} 15:39, 28 September 2024 (UTC)

Would you care to elaborate on your point? I'm not seeing it. Anomie⚔ 17:04, 28 September 2024 (UTC)

@Anomie: Read the "Proposal" section on the linked page. The fact that RfC even exists should give you a clue as to why CRASHlock is so mistrusted by a significant minority of editors. —Jéské Couriano v^_^v ^{threads critiques} 18:01, 9 October 2024 (UTC)

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)

You familiar with the idiom of the Camel's nose? —Jéské Couriano v^_^v ^{threads critiques} 18:47, 9 October 2024 (UTC)

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)

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. Awesome Aasim 19:00, 9 October 2024 (UTC)

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. Awesome Aasim 18:16, 9 October 2024 (UTC)

@Awesome Aasim: The RfC was linked specifically to point out one of the reasons for the mistrust in the PC system. The most recent RfC on CRASHlock, as I said, predates XCP as a concept. —Jéské Couriano v^_^v ^{threads critiques} 18:20, 9 October 2024 (UTC)

Also, please explain what you mean by "crashlock". I cannot find any discussion or glossary entry on "crashlock". Awesome Aasim 18:21, 9 October 2024 (UTC)

@Awesome Aasim: It should be VERY obvious from context. —Jéské Couriano v^_^v ^{threads critiques} 18:26, 9 October 2024 (UTC)

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. Awesome Aasim 18:40, 9 October 2024 (UTC)

(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)

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)

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)

It's one reason, and probably the biggest for some (who viewed the trial's mishandling as trying to force CRASHlock/FlaggedRevisions down our throats). Another reason is that, from 2010 to 2014, CRASHlock RfCs were called at least once a year, with most of them being written by pro-CRASHlock editors. —Jéské Couriano v^_^v ^{threads critiques} 18:42, 9 October 2024 (UTC)

Ok for those not into WP politics, there's an overview opinion piece from the August 2011 WSP that seems to capture the attitude and aftermath. It appears the closure results of the RfCs left admins in an indeterminate state as to whether PC can ever be applied or removed. SamuelRiv (talk) 18:47, 9 October 2024 (UTC)

as to whether PC can ever be applied or removed True in 2011 when that was written, but later RFCs resolved that. Anomie⚔ 19:02, 9 October 2024 (UTC)

Could you link to said RfCs? All else that's linked previously regards the main page. SamuelRiv (talk) 19:56, 9 October 2024 (UTC)

Wikipedia:Pending changes/Request for Comment 2012 established basic consensus to use PC, with Wikipedia:PC2012/RfC 2 and Wikipedia:PC2012/RfC 3 clearing up some details. PC level 2, on the other hand, never got consensus for use and eventually in 2017 there was consensus to remove it from the configuration. Template:Pending changes discussions has a lot of links. Anomie⚔ 22:14, 9 October 2024 (UTC)

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 the 2016 RfCs, none of which were particularly comprehensive. (The last comprehensive RfC was the 2014 clusterfuck.) —Jéské Couriano v^_^v ^{threads critiques} 06:47, 10 October 2024 (UTC)

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)

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.

Apologies for the hastily typed response, I'm a little pressed for time; hopefully there was something useful in there. 184.152.68.190 (talk) 16:06, 22 October 2024 (UTC)

Maybe what is needed is this...

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. Awesome Aasim 19:52, 1 October 2024 (UTC)

I view the ECR in the PIA area to be absolute (no editing full stop by those who do not meet 500/30), so CRASHlock would be off the table there in any event. I'm not sure if this also applies to WP:GS/RUSUKR (which falls into the EE area). —Jéské Couriano v^_^v ^{threads critiques} 18:57, 9 October 2024 (UTC)

Can we build the proposal here?

Here is some starter text maybe to get the ball rolling:

• What is the best way to enforce WP:ARBECR on articles?
  • Option 1: Preemptive XCON protection
  • Option 2: Preemptive XCON pending changes
  • Option 3: Edit filters
  • anything else?

This probably is incomplete, anyone else have ideas for this proposal? Awesome Aasim 19:41, 16 October 2024 (UTC)

I'd say remove "preemptive", as it is sometimes placed only in response to disruptive activity from non-ECs. Aaron Liu (talk) 11:31, 17 October 2024 (UTC)

So should reactive also be an option? Awesome Aasim 17:32, 17 October 2024 (UTC)

I think so. That's what I support. Cremastra — talk — c 19:29, 17 October 2024 (UTC)

So we should have it like this?:

• What is the best way to enforce WP:ARBECR on articles? Please rate whether these options should be preemptive, reactive, or not used.
  • Option 1: XCON protection
  • Option 2: XCON pending changes
  • Option 3: Edit filters/Revert filters
  • anything else?

Awesome Aasim 19:39, 17 October 2024 (UTC)

sure. Cremastra — talk — c 19:42, 17 October 2024 (UTC)

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é Couriano v^_^v ^{threads critiques} 16:26, 26 October 2024 (UTC)

@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)

My point still stands - a new RfC, developer buy-in, and ArbCom not interdicting the RfC would be required for this to become a reality. —Jéské Couriano v^_^v ^{threads critiques} 17:34, 27 October 2024 (UTC)

No, we're discussing "pending changes protection". Crashlock is a type of cardboard box. --Ahecht (TALK
PAGE) 21:18, 28 October 2024 (UTC)

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)

Read what I wrote above in re an RfC. EC!CRASHlock does not exist, and would need a consensus to use it and the devs being willing to work on it for it to be a thing. Spitballing anything about this is a waste of time until that happens, especially as the current consensus is that (1) anything beyond standard CRASHlock is deprecated and (2) ECP renders EC!CRASHlock pointless. —Jéské Couriano v^_^v ^{threads critiques} 17:17, 28 October 2024 (UTC)

Please, stop calling it "CRASHLOCK" it's confusing and pointless. At least explain why pending changes = crashing. Cremastra (u — c) 19:59, 28 October 2024 (UTC)

@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)

@Bunnypranav: Which is why I'm saying "start a new RfC." Something everyone seems to be glossing over despite me saying something to this effect four separate times in this thread. —Jéské Couriano v^_^v ^{threads critiques} 06:44, 3 November 2024 (UTC)

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. Awesome Aasim 16:41, 30 October 2024 (UTC)

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)

That would be hard-required, as I've repeatedly been saying. Without an existing consensus for the former, any discussion on using it for 500/30 rule areas is academic. —Jéské Couriano v^_^v ^{threads critiques} 06:51, 3 November 2024 (UTC)

RFC started

See WP:VPPR#RfC: Extended confirmed pending changes (PCECP). Awesome Aasim 19:58, 5 November 2024 (UTC)

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)

I believe that would require changes to the software. Thryduulf (talk) 00:46, 2 November 2024 (UTC)

I mean, temporary accounts are already on. I doubt that the WMF isn't already planning this. Aaron Liu (talk) 00:49, 2 November 2024 (UTC)

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)

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)

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)

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)

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. Zero^talk 02:40, 6 November 2024 (UTC)

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?

Wikieditor662 (talk) 20:34, 23 October 2024 (UTC)

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)

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)

Hey @Folly Mox@Chaotic Enby I posted to Wikipedia talk:WikiProject Vital Articles and a week later there's still no response... Is there anything else I could do?

Thanks,

Wikieditor662 (talk) 20:25, 1 November 2024 (UTC)

@Wikieditor662: you may have set yourself up for a poor reception with the question should people be inclu­ded based off on how significant, famous, or both they are/were?. Both of these attributes are not quantifiable: the only inclusion criteria VA would recog­nise as feasible would probably be "limit to Level 3" (112 figures), or "include Level 3 and Level 4" (1995 addi­tional 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)

That sounds like a giant pile of WP:OR – Joe (talk) 12:26, 24 October 2024 (UTC)

Researcher group

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)

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)

@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)

What sort of editors are you thinking might wish to get this right, EggRoll97? Espresso Addict (talk) 06:38, 6 November 2024 (UTC)

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)

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.

You would replace this with convincing RFA voters that you should have this but not have admin rights. Have you read Wikipedia:Perennial proposals#Hierarchical structures on partial adminship?

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)

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)

@WhatamIdoing Edit filter managers don't need to be administrators, see WP:EFM. Thryduulf (talk) 08:33, 6 November 2024 (UTC)

You're right. I should have looked it up instead of relying on memory. Thank you. WhatamIdoing (talk) 16:26, 6 November 2024 (UTC)

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)

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)

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)

• 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. — xaosflux ^Talk 18:59, 6 November 2024 (UTC)

  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. — xaosflux ^Talk 18:59, 6 November 2024 (UTC)

  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)

  Duplicated? No, for example apihighlimits isn't likely required at all here. — xaosflux ^Talk 10:17, 7 November 2024 (UTC)

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)

LA2, this doesn't sound like it would be possible to implement entirely in client-side scripting, and would require dev involvement. Software changes like this can be suggested at the global Community Wishlist. Folly Mox (talk) 12:06, 7 November 2024 (UTC)

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)

 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)

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. — xaosflux ^Talk 14:23, 28 October 2024 (UTC)

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)

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)

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)

I feel like if a petition is unnecessary, then no one would sign it. fanfanboy (block) 15:02, 28 October 2024 (UTC)

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)

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)

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)

Noting I've withdrawn the petition. Sincerely, Dilettante 15:41, 28 October 2024 (UTC)

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)

Two weeks as a baseline sounds like a more reasonable time, that could very much work. Chaotic Enby (talk · contribs) 16:15, 28 October 2024 (UTC)

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)

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)

• 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)

  That's exactly what I suggested a few months back Mach61 16:44, 28 October 2024 (UTC)

• 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)

  @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. Mach61 16:47, 28 October 2024 (UTC)

  I have no idea what that means. Any single editor can just change the process by WP:BOLD editing it? If that's the case, why are we having this discussion? Chetsford (talk) 16:52, 28 October 2024 (UTC)

  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)

• 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.

Any views on that? Ritchie333 ^{(talk) (cont)} 16:51, 28 October 2024 (UTC)

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)

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)

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)

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)

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 | talk 20:52, 28 October 2024 (UTC)

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)

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)

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 Albury 13:39, 29 October 2024 (UTC)

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)

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)

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)

That could work, in a way. Every editor can start a petition, but two editors have to sign within 48 hours or it gets closed without further ado. Chaotic Enby (talk · contribs) 18:50, 29 October 2024 (UTC)

• 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)

  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)

  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)

  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)

  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)

  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)

  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)

  I think that's a good course of action. Aaron Liu (talk) 22:25, 29 October 2024 (UTC)

  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. Chaotic Enby (talk · contribs) 22:48, 29 October 2024 (UTC)

  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)

  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.

  Nobody inspects every nook and cranny in history for bad things people have said to agree with it. Aaron Liu (talk) 01:29, 30 October 2024 (UTC)

  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)

  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)

• 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. Zero^talk 02:10, 30 October 2024 (UTC)

  Very good point, and why I would favor "allow nobody to comment" as a general rule. Chaotic Enby (talk · contribs) 02:22, 30 October 2024 (UTC)

• 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. Zero^talk 02:10, 30 October 2024 (UTC)

  On the other hand, editors victims of administrator misconduct should definitely be able to support the administrator being brought to recall. Chaotic Enby (talk · contribs) 02:26, 30 October 2024 (UTC)

  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)

  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)

  That makes sense. Zero^talk 02:42, 30 October 2024 (UTC)

  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)

  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)

  I agree. Anything more complicated would be too complicated. —Alalch E. 22:30, 30 October 2024 (UTC)

Workshopping the RfC

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)

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)

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)

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)

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.

The talk page will be open anyway, so people who want to elaborate on why can do it as they prefer Soni (talk) 05:14, 30 October 2024 (UTC)

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)

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)

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)

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)

"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)

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)

Will this: Any ... comment may be struck based on the same criteria used during requests for adminship (from WP:RECALL) hold true on the talk page? —Alalch E. 16:33, 30 October 2024 (UTC)

I think that is something that will need to actively decided. Thryduulf (talk) 16:45, 30 October 2024 (UTC)

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)

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)

By two-part, I mean asking two questions simultaneously, not running one RfC and then another. The second RfC had more then ten simultaneous questions, so two should be manageable. Chaotic Enby (talk · contribs) 17:28, 30 October 2024 (UTC)

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)

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)

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)

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 Albury 19:42, 30 October 2024 (UTC)

@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)

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)

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)

Notification: RfC: Shorten the recall petition period

Wikipedia:Administrator recall has an RfC for possible consensus. A discussion is taking place. If you would like to participate in the discussion, you are invited to add your comments on the discussion page. Thank you. CNC (talk) 21:59, 1 November 2024 (UTC)

Notification: RfC: Should we add text prescribing just signatures, no discussion?

Wikipedia:Administrator recall has an RfC for possible consensus. A discussion is taking place. If you would like to participate in the discussion, you are invited to add your comments on the discussion page. Thank you. Chaotic Enby (talk · contribs) 15:58, 3 November 2024 (UTC)

The first notification is for shortening the period and the second one is for limiting comments to just signatures. Aaron Liu (talk) 16:03, 3 November 2024 (UTC)

Have modified title of first notification to make more sense. CNC (talk) 16:38, 3 November 2024 (UTC)

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)

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)

Hooman Mallahzadeh, this project is already underway. See m:Abstract Wikipedia. Folly Mox (talk) 11:08, 7 November 2024 (UTC)

@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".

I really think that "Machine Wikipedia" project can be made very fast, and the delay that "Abstract Wikipedia" project had made is unreasonable. Hooman Mallahzadeh (talk) 11:35, 7 November 2024 (UTC)

Ok, it sounds like you know quite a bit about machine learning. But, kindly, this has no relation to English Wikipedia. m:Talk:Abstract Wikipedia has 236 watchlisters, and the project has a public mailing list, if you want to get in touch about your ideas with the team involved. Folly Mox (talk) 12:01, 7 November 2024 (UTC)

@Folly Mox I added a comment there. Thanks for your response. Hooman Mallahzadeh (talk) 12:35, 7 November 2024 (UTC)

"Thank" as a button in threaded discussions

Is there a script or gadget that adds "[Thank]" before "[Reply]"? After is fine too, but I think before might be better.

If not, is someone willing/able to make one? It would make thanking easier, I think. Gråbergs Gråa Sång (talk) 14:12, 7 November 2024 (UTC)

@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)

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)

You can also turn off the feature to change signature positions. Aaron Liu (talk) 15:17, 7 November 2024 (UTC)

Thanks for the replies! Gråbergs Gråa Sång (talk) 15:37, 7 November 2024 (UTC)

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.

Above is the output of the template, for those unfamiliar with it.

Thoughts? — rsjaffe 🗣️ 19:59, 5 November 2024 (UTC)

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)

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)

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)

It's just "move to draft". I have no idea why more CSD taggers don't use it. -- asilvering (talk) 20:41, 5 November 2024 (UTC)

I don't think we give clear enough guidance on what the taggers can/can't do. — rsjaffe 🗣️ 22:24, 5 November 2024 (UTC)

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.

Pi.1415926535 (talk) 22:11, 5 November 2024 (UTC)

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)

@Rsjaffe if anything, people are less sophisticated about this now, since many mobile browsers try very hard to obscure URLs. -- asilvering (talk) 22:37, 5 November 2024 (UTC)

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)

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)

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)

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. —Cryptic 22:29, 5 November 2024 (UTC)

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. —Cryptic 22:34, 5 November 2024 (UTC)

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)

It already does that? WhatamIdoing (talk) 01:17, 6 November 2024 (UTC)

Thanks, @WhatamIdoing, I thought I was the crazy one. -- asilvering (talk) 01:18, 6 November 2024 (UTC)

The theme Minerva does not appear to me to show the User: prefix, but does seem to for most namespaces <https://en.wikipedia.org/wiki/User:Example?useskin=minerva>. Skynxnex (talk) 02:23, 6 November 2024 (UTC)

And Folly Mox is on the mobile site. @SGrabarczuk (WMF), could you please talk to the Web team about this? User pages ought to say that they're User: pages, even if someone would like to hide that fact. WhatamIdoing (talk) 03:33, 6 November 2024 (UTC)

Whoops I didn't think to check in other skins. Apologies for the confusion. Folly Mox (talk) 14:05, 6 November 2024 (UTC)

This problem is especially bad on mobile since, as asilvering points out, mobile browsers hide URLs. McYeee (talk) 07:06, 7 November 2024 (UTC)

• 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)

  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)

  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)

  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)

  @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)

  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)

  asilvering, according to Wikipedia:Editnotice § User and user talk (confirmed at Template:Editnotices/Namespace/User), When editing a new user page, {{base userpage editnotice}} will show. The editnotice is already pretty clear. Folly Mox (talk) 00:42, 8 November 2024 (UTC)

  Welp. You can't fix that level of banner-blindness with anything. -- asilvering (talk) 00:46, 8 November 2024 (UTC)

  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)

• Wouldn't adding {{Userspace draft}} to the userpage fix the issue? Nobody (talk) 10:44, 6 November 2024 (UTC)

Enable interlanguage links to author links in cite templates

Apologies if this should be go to Village_pump_(proposals) or Village pump (technical). Please let me know if I should make this proposal there instead, or to some other place.

One of the edits I most often do is to use author link to wiklink names in citations, including in citations that use templates like Template:Cite book. This works great if the author already has an article in English Wikipedia.

Unfortunately, when the author only has an article about him in some other language, this cannot be taken advantage of. Interlanguage links do not work in cite templates. I think Wikipedia does not allow one set of braces or curly brackets {{}} to be inside another set {{}}; in other words does not permit nested layers of templates.

Proposal

I propose that Wikipedia, via some way (whether or not that means allowing nested layers of curly-bracketed templates), enable interlanguage links in citations that use cite templates.

Example

To make this concrete rather than abstract, look at Basic Law for the Federal Republic of Germany. Currently the second citation is:

Eberhard Straub (2011). Eine kleine Geschichte Preußens. Klett-Cotta. p. 17.

The wiki markup for the citation reads:

{{cite book|title=Eine kleine Geschichte Preußens|author=Eberhard Straub|year= 2011|pages=17|publisher=Klett-Cotta}}

To make the author's name in the citation be a wikilink to his article, one would insert a new field in the citation like this:

|author-link=Eberhard Straub

but that would create a red link in English Wikipedia, because Eberhard Straub does not currently have an article in English Wikipedia.

However, he does in German Wikipedia, making it preferable for such a link to be an interlanguage link, thus empowering readers who want to know more about the cited author to at least be able to look at the article about him in German, and also inviting readers to be editors and create a new English-language article about him. If and when that English-language article is posted, then the red link to his name and the smaller bracketed blue link to the German article disappear from view and the link appears to readers to be an ordinary blue link to the new English language article.

How?

I don't know how to accomplish this.

I don't know if it's technically feasible to change the Wiki software to allow for a nested layer of curly-bracketed template to be used within another curly-bracketed template, using the already-existing author-link field, like this:

{{cite book|title=Eine kleine Geschichte Preußens|author=Eberhard Straub|author-link={{interlanguage link|Eberhard Straub|de}}|year= 2011|pages=17|publisher=Klett-Cotta}}

Or if a new interlanguage author-link field in the citation template needs to be created instead, like

{{cite book|title=Eine kleine Geschichte Preußens|author=Eberhard Straub|ill-author-link-de=Eberhard Straub|year= 2011|pages=17|publisher=Klett-Cotta}}

What do you think?

Carney333 (talk) 17:12, 12 November 2024 (UTC)

just put :de:Eberhard Straub

Eberhard Straub [in German] (2011). Eine kleine Geschichte Preußens. Klett-Cotta. p. 17.

The real reason it didn't work is because the template already generated a [[]], so the parameter tries to linkify a link and render "[[[[:de:Eberhard Straub]]]]], causing it to fail. You can nest templates easily.

Doe, John (1 April 2020). [I witnessed Tom Hanks admitting to actually being born one year earlier, faking his age to enlist in the scouts] (Dream). Lucid. Recurring Tom Hanks scouts dream number 8. Doe's bedroom, 412 Example Street, Suburbiaville, London: REM stage R.

Aaron Liu (talk) 17:30, 12 November 2024 (UTC)

Thanks for your feedback, but the main problem with your suggestion is that it doesn't work with author links, which can draw from separately provided surnames and given names, and then display the results as surname first, then comma, then given name, hyperlinking to the article about the author. I didn't mention this in my original comment for reasons of space and focus.

In other words, what I really want to be able to do is to do something like

{{cite book|title=Eine kleine Geschichte Preußens|author-first=Eberhard author-last=Straub |ill-author-link-de=Eberhard Straub|year= 2011|pages=17|ill-publisher-de=Klett-Cotta}}

to produce something like:

Straub, Eberhard. (2011). Eine kleine Geschichte Preußens (in German), Klett-Cotta. p. 17.

Carney333 (talk) 01:25, 14 November 2024 (UTC)

If you want to suggest something to do with with the citation templates I suggest you post it to Help talk:Citation Style 1. This, and similar ideas, have been discussed before. The solution is to use:
{{cite book |title=Eine kleine Geschichte Preußens |author-first=Eberhard |author-last=Straub |author-link=:de:Eberhard Straub |year= 2011 |pages=17 |publisher=[[:de:Klett-Cotta|Klett-Cotta]]}}
which produces:
Straub, Eberhard [in German] (2011). Eine kleine Geschichte Preußens. Klett-Cotta. p. 17.

It definitely works with both |author= and |last=, |first=. -- LCU ActivelyDisinterested «@» °∆t° 13:29, 14 November 2024 (UTC)

I'd suggest not suggesting this, since it was just suggested in July at Help talk:Citation Style 1/Archive 95 § Doesn't play well with {{ill}}. Just use the standard interwiki link format in the |author-link= parameter, without trying to transclude {{ill}}. Folly Mox (talk) 14:03, 14 November 2024 (UTC)

Disclosure: I hate {{ill}} since it breaks title display in non-ASCII scripts on Firefox; i.e. you have to click through and load the sister Wikipedia page just to retrieve the title instead of a bunch of percent escaped garbage numbers for unicode codepoints. Folly Mox (talk) 14:08, 14 November 2024 (UTC)

In principle, one could set up a disambiguation page (thereby allowing for multiple languages) for the target and use {{interlanguage link}} on the disambiguation page. Of course, there may be a mild "surprise" for the user, but there can be sufficient explanatory text on the disambiguation page to explain the situation.

A side-effect of this (unless there's some provision to suppress this behavior), is that the page will be recognized as a valid "local wiki" page for other purposes as well, but IMO, that's not necessarily a bad thing ... and we can always include a qualifier in the title of the disambiguation page to help address that concern. Also, this is a little more work, but I think it's an improvement over the current practice of not providing the link. Fabrickator (talk) 15:26, 14 November 2024 (UTC)

Another option would be to create a stub/start article, link it to wikidata to get the language links, and tag it with the relevant "Expand language" template EdwardUK (talk) 17:49, 14 November 2024 (UTC)

I'm not sure a bunch of transwiki dabpages or nearly content-free stubs are the solution to this unproblem. {{ill}} formatting aside, what's wrong with linking an article on a sister project? We do it with Wikisource, Wiktionary, and Wikidata all the time. Folly Mox (talk) 21:44, 14 November 2024 (UTC)

In the context of citations, the actual target is only visible when you mouse over it (assuming the user bothers to examine the link preview), so it will typically be a surprise when a non-English page is displayed. Also, the general intent is to let the user select their preferred language, if multiple languages are available. (Of course, there will be a list of all available languages when you go to any language version of the article.) As a fairly minor point, the existing use of {{ill}} provides for the replacement of {{ill}} when a local link becomes available. Fabrickator (talk) 02:16, 15 November 2024 (UTC)

Feedback for articles about years

It's been nearly two years since I brought this up here, but I've done some more work on articles about years since then and could use more feedback. I've just finished working on 2002. To ensure WP:WEIGHT/WP:PROPORTION, the information in the body of the article is based on sources that cover the year as a whole, such as Britannica Book of the Year and The Annual Register as well as more subject-specific sources. The timeline then reflects what's in the body, with sources like newspapers to verify the specific dates. I want to get more opinions to see if this is a good approach for other year articles going forward and whether there are any other ideas that should be considered. Thebiguglyalien (talk) 00:30, 17 November 2024 (UTC)

BLUF: It's been nearly two years, and I still really like the work you've been doing with these articles. The new format in 2002 is so much nicer than the older format (e.g., in 2012). WhatamIdoing (talk) 21:03, 17 November 2024 (UTC)

Yeah, comparing 2002 to 2012 as Whatamidoing suggested I much prefer your revised format. --User:Khajidha (talk) (contributions) 13:07, 18 November 2024 (UTC)

A Link Rot Bestiary

After 5 years repairing a wide variety of link rot cases at WP:URLREQ, I created a manual describing a system of first principles, A Link Rot Bestiary: Types-Of and Methods-For Link Rot Repair. -- GreenC 16:52, 18 November 2024 (UTC)

Favoriting articles for logged-out and IP users

Hi. Before i joined Wikipedia, i always wanted a way to save my favorite articles somehow. When i logged in, i was excited to see a star button on a article (which signaled it was a sort of a favorite button) but to my disappointment it just made articles go on the watchlist. So what if there was a way to save certain articles to, say, read later or gather a collection for a school assignment. This would be very useful to both logged-out and in users. This could mean good for Wikipedia editing too! If you favorite a article, there should be a way to easily come back too it. This would make more efficient editing, rather then a confusing “watch list” of articles. Another way to implete this idea is to add it to a group, where you can come back to later. But either way, there should be a way to save articles to a dedicated area, logged in or not. Edit: I apologize if this is the wrong area,i couldn’t quite figure out if i should out this in Proposals or here.K.O.518 (talk) 06:49, 15 November 2024 (UTC)

Note that the “View and edit watchlist” tab of the watchlist has a list of all your watched articles in alphabetic order, which could be used as a favourites list.  novov talk edits 10:44, 15 November 2024 (UTC)

The official Android and iOS Wikipedia apps also have the ability to bookmark and save articles for offline reading. the wub "?!" 16:35, 15 November 2024 (UTC)

Special:Book. It's in poor maintenance though, so it's not advertised much Aaron Liu (talk) 16:49, 19 November 2024 (UTC)

Reference templates

Wikipedia reference templates

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 ___________________

(put DOI and PMID in “extra fields”)

Print references in same order of information as in the template above. Pbergerd (talk) 14:19, 7 November 2024 (UTC)

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 Albury 18:53, 7 November 2024 (UTC)

As a minor correction, not all of the CS1|2 templates support the same parameter set. For example, as of 2023, calling {{Cite book}} with the parameter |website= (or any of its aliases, like |work=, |journal=, |periodical=, |magazine=) will cause a template error, and add the article to Category:CS1 errors: periodical ignored (22,953).

To address the substance of the OP, that there is any consistency among the most commonly used citation templates is the result of years of effort and discussion. The multiplicity of display formattings is a feature, not a drawback. There will never be just one single citation template, uniform in formatting across all sources and transclusions.

Pbergerd, if you want the input fields in whatever editor you're using (not clear from tags in your contribs) to match the displayed format of those templates, that would best be addressed to whomever maintains your editing interface of choice (if anyone). The formatting will not be changed in the other direction (i.e. display matches input field ordering). Additionally, to my knowledge no citation template display leads with the title when the author is known, so I doubt you'll find consensus for your specific implementation proposal anywhere. All the best, Folly Mox (talk) 18:39, 9 November 2024 (UTC)

As a less gloomy follow up, our editing guideline WP:CITEVAR allows for articles to maintain the style used by the first major contributor or adopted by the consensus of editors already working on the page. So if you feel strongly about title-headed citations, you can implement your preferred formatting on articles you create, or unreferenced articles you provide the first citations for. But don't be surprised if bots come along and change it.

With respect to your specific example David Graham Phillips § Notes: three two of the six citations – Fellow, Mencken, and Ravitz – are manually formatted (not the result of any citation template) and shouldn't be used as examples of a surfeit of citation formats. Two of the three four sources used in citation templates do not provide any authorial or editorial attribution (verified in sources), so naturally the format will differ from that of sources where the author is known.

Tangentially, it is somewhat common for articles to use a mixture of Shortened footnotes and regular "defined in place" citations. Usually this is unintentional, as editors new to an article will almost never add citations in shortened format, except improperly, adding to Category:Harv and Sfn no-target errors (4,850). Converting all the new sources to shortened footnote form happens very irregularly. Sometimes articles will intentionally adopt a mixed style, where "main sources", multiply cited sources, or sources cited at more than one in-source location (a subset of the previous criterion) will be formatted in shortened form, and the remainder in the standard fashion. Folly Mox (talk) 19:22, 9 November 2024 (UTC) corrected per below 20:38, 10 November 2024 (UTC)

One reason for using <ref>CS1 or CS2 template</ref> instead {{sfn}} is the cs1|2 fields that sfn does not have, e.g., |quote=, |access-date=, |section-link=. This will be even more true if and when <ref extends=base>...</ref>, Wikipedia:Village pump (technical)#Coming soon: A new sub-referencing feature – try it! permalink/1241515798, becomes available. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 15:23, 10 November 2024 (UTC)

There are plenty of reasons not to use shortened footnote templates, and the lack of support for extra parameters is a feature (the footnotes, after all, are supposed to be short).

I'm wondering why |access-date= in particular would ever be helpful to support: it's one of the cruftiest parameters, displaying rather a lot of text for information only really needed during archive snapshot hunting; it's not useful for print sources, which have a stable form per publication date, and are the most common types of sources where shortened footnotes are used; and why would you have different access dates for different sections of the source? Can't it just be added to the full citation template the shortened footnote links to?

Quotes are another matter, but are easily included within the <ref>...</ref> tags following a harv family template like {{harvp}} or {{harvnb}}, which can be embedded within ref tags. Folly Mox (talk) 15:51, 10 November 2024 (UTC)

The attributes I mentioned were just random examples, but, e.g., |sectionlink= certainly seems important, and lots of printed sources are also available as PDF. Placing detail as free text in <ref>{{harvnb}}...</ref> does not create the proper metadata, so while it might work for |quote= it does not for other attributes. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 11:40, 11 November 2024 (UTC)

Thanks for all of your information. (I actually did use the book template for the Ravitz citation.) Pbergerd (talk) 15:58, 10 November 2024 (UTC)

Whoops, sorry; not sure how I misread / misre­membered that. Corrected my earlier reply. Folly Mox (talk) 20:38, 10 November 2024 (UTC)

I agree with the OP that it's silly to have lots of different templates for citations – {{cite book}}, {{cite journal}}, etc. But there is a generic template for this and it's {{citation}}.

I usually use {{citation}} so that if, for example, I'm citing the Times using a URL, I don't have to worry about whether it's a web site or a newspaper when it's obviously both.

The main problem nowadays is that the Visual Editor generates the more specific templates rather than the generic one. I usually switch to the text editor to correct it but that's a nuisance.

Andrew🐉(talk) 16:55, 19 November 2024 (UTC)

thanks, I'll try that Pbergerd (talk) 02:45, 20 November 2024 (UTC)

istrue template that returns a boolean

See Template talk:Australian dollar#Why can't link=True work?

It would save time to have a true template but what would the word list be; y/Y/yes/Yes/YES n/N/no/No/NO t/T/true/True/TRUE f/F/false/False/FALSE? Anthony2106 (talk) 05:21, 19 November 2024 (UTC)

How would it work? How would |link={{true}} be different for bot parsing than |link=true? Thryduulf (talk) 05:26, 19 November 2024 (UTC)

In templates like plot and AUD they have an option for "true" e.g {{AUD|10,000|link=yes}} putting "True" in place of "yes" does not work, so this functionality could be added into the AUD template or AUD could use a istrue template - a global template that has all the yeses and no's, so AUD would have a template in a template. This way each template that needed a yes/no could use this global template. Anthony2106 (talk) 07:32, 19 November 2024 (UTC)

{{yesno}} Aaron Liu (talk) 12:48, 19 November 2024 (UTC)

Thank you. Anthony2106 (talk) 03:41, 20 November 2024 (UTC)

Has anyone proposed using the military history's criteria for C-class universally before?

The Wikipedia:WikiProject Military history/Assessment has much clearer criteria for C-class than what we currently have. Here's Wikipedia:Content assessment:

"The article cites more than one reliable source and is better developed in style, structure, and quality than Start-Class, but it fails one or more of the criteria for B-Class. It may have some gaps or missing elements, or need editing for clarity, balance, or flow."

The heuristic for C-class is "substantial but is still missing important content". The heuristic for Start-class is, similarly "developing but still quite incomplete": not very different. As an alternative, you can try to determine whether the article is "Useful to a casual reader, but would not provide a complete picture for even a moderately detailed study" or "Provides some meaningful content, but most readers will need more."

And here's the military history version of C-class:

"The article meets B1 or B2 as well as B3 and B4 and B5 of the B-Class criteria.

Detailed criteria

• B1. It is suitably referenced, and all major points have appropriate inline citations.
• B2. It reasonably covers the topic, and does not contain obvious omissions or inaccuracies.
• B3. It has a defined structure, including a lead section and one or more sections of content.
• B4. It is free from major grammatical errors.
• B5. It contains appropriate supporting materials, such as an infobox, images, or diagrams.

See also the B-Class assessment & criteria FAQ."

Here, rather than having to make a difficult heuristic judgement between C-class and start-class, clear criteria determine whether an article is start-class and other clear criteria determine whether it is C-class. It seems to me to be a reasonable formalization of the two heuristics (referencing and completeness) used to determine C versus Start class anyways. I think if Wikipedia adopted this generally, it would make rating articles much faster and simpler and less confusing given that the criteria for distinguishing C-class articles are formalized rather than subject to essentially how complete the article feels. When I rate articles, I usually spend a good bit of time worrying about whether it is C-class or Start-class -- a major part of the decision making currently is informed by observing other people's decisions. WP:MILHIST has basically solved that and added a FAQ.

Has anybody ever proposed using the MILHIST criteria before? I do remember seeing proposals (not successful) to merge C and Start class, but not this specifically. Mrfoogles (talk) 08:55, 11 November 2024 (UTC)

Making the assessment process any more formalized than it is is a non-starter when we have hundreds of thousands of articles that aren't assessed at all. PARAKANYAA (talk) 15:32, 12 November 2024 (UTC)

Well, the idea of this would be to make it easier to assess them. Mrfoogles (talk) 23:09, 12 November 2024 (UTC)

C-class came from Wikipedia:Content assessment, not MILHIST. (See Wikipedia talk:Content assessment/Archive 4#Proposal - adding C-class between GA-Class and Start-Class, Wikipedia talk:Content assessment/Archive 4#Results of the poll and Wikipedia talk:Content assessment/Archive 4#New C class live.) It was subsequently adopted by the Military History Project in 2009 in the manner described in order to minimise the amount of work required. (A single change to our project template.) (See Wikipedia talk:WikiProject Military history/Coordinators/March 2009). Hawkeye7 (discuss) 23:58, 12 November 2024 (UTC)

My experience is that any article ratings other than those which are part of a formal process (i.e. all those except GA, A, and FA) tend to be assigned based on vibes rather than any strict concern with the criteria, and mostly are not updated when the article changes. If assessments are largely made without reference to the criteria, I'm not sure that changing the criteria will have much effect. Even assuming for the sake of argument that people are carefully rating articles based on the assessment criteria, ratings are updated so infrequently that there's no guarantee that they are still appropriate at any given time.
I don't object to clearer criteria for what is a start/C/B class article, but I also don't know that I really see the point: at this point in Wikipedia's development, what if anything do people actually use these ratings for? Generally I agree with the view which has been expressed by various people in the past (I know Iridescent used to make this point, as in this thread) that the distinctions between start/C/B class are pretty pointless and we'd be just as well off scrapping them entirely and ending up with a scale which goes stub/standard/good/featured or even unassessed/good/featured. (You mention proposals to merge start- and C-class, but I cannot find them in the archives of Wikipedia talk:Content assessment or WP:VP) Caeciliusinhorto-public (talk) 12:58, 13 November 2024 (UTC)

I'd pretty much agree with this, adding that in my experience most ratings are assigned almost entirely on article length, and also that nearly all our readers and most of our editors never look at them. Johnbod (talk) 13:37, 13 November 2024 (UTC)

They are pointless, generally speaking, other than that it's nice to say you've improved the quality of X article to Y, which can be a nice achievement. You might be right than eliminating the distinctions might be a good idea -- stub/start/C are very difficult to distinguish meaningfully, and checking that everything is cited correctly in B requires a mini-GA review level of work for long articles. Mrfoogles (talk) 02:58, 14 November 2024 (UTC)

Given the reception, probably not going to propose this. What the system really needs is a reform based on determining what purposes it actually serves. Mrfoogles (talk) 02:59, 14 November 2024 (UTC)

The rating system was created by, belongs to, and primarily benefits the Wikipedia:Version 1.0 Editorial Team. This group is still active, even though they do most of their work via specialized off-wiki tools these days (so don't be fooled if you look at the page history and don't see any recent edits; that's not where the action is). AFAICT it serves their purpose (i.e., selecting articles for offline distribution based on a multi-factor calculation that reflects centrality [most internal links work], popularity [students want to read it], and quality [via ratings]) well. WhatamIdoing (talk) 20:57, 17 November 2024 (UTC)

My impression is that the ratings are associated with the projects such as Milhist but the project templates seem to be placed in an indiscriminate and rote way.

It would be good to rationalise the ratings in a functional way. For example, what I notice is that DYK and ITN perform their own independent quality assessments without regard to the project assessments. The {{article history}} attempts to pull all these things together but is only used on 50,000 pages. There ought to be a standard talk page template to unify these things.

Andrew🐉(talk) 09:28, 20 November 2024 (UTC)

Enabling history merge permissions for importers?

While I'm not the most versed on that technical issue, one of the important points raised during Graham's RRfA was that admin tools were needed for him to do history merges and deal with more complex imports. Since Graham will no longer have these tools as an administrator, would there be a way to add these capabilities to the importer role? It could also help make the latter more accessible for non-admins potentially interested in helping out with this. Chaotic Enby (talk · contribs) 11:26, 20 November 2024 (UTC)

Yes, it would be possible. Need (a) a community discussion that supports adding the (mergehistory) permission to the import group, here on the English Wikipedia. Then (b) a configuration request can be made to add such. — xaosflux ^Talk 11:29, 20 November 2024 (UTC)

Thanks! Wasn't sure about the specific technical details, since it looks like it's technically possible, I guess I can open the community discussion on WP:VPT? Chaotic Enby (talk · contribs) 11:33, 20 November 2024 (UTC)

WP:VPR would be better, as it is asking for community support not just a technical question. Please advertise the discussion to WP:AN (as it is currently an admin-only permission) and Wikipedia talk:Requests for page importation (due to the special group). — xaosflux ^Talk 11:44, 20 November 2024 (UTC)

Thanks! Would you recommend me to make it a formal RfC or a "regular" community discussion? Chaotic Enby (talk · contribs) 11:45, 20 November 2024 (UTC)

Unbundling of an admin permission will almost certainly need to be an RFC. Thryduulf (talk) 11:51, 20 November 2024 (UTC)

And it's done! Chaotic Enby (talk · contribs) 12:30, 20 November 2024 (UTC)

Also, I'd support this, as anyone who can use xmlimport is already going to be trusted enough to not cause history damage. — xaosflux ^Talk 11:31, 20 November 2024 (UTC)

Don’t put up Ip addresses for those who are not signed in.

You see, if someone edits Wikipedia and they are not signed in, their IP address is exposed. That means one could track where they live and dox them further. So yeah, don’t put the Ip adrees. But what if the person does an edit that ruins the page, or something bad? you see Wikipedia will have the ip address, and all what they have to do is report the anonymous person, Who will have a name, like not logged in or something, then Wikipedia will block it. Have a good day. Bye bye! Datawikiperson (talk) 09:46, 19 November 2024 (UTC)

@Datawikiperson Please see Trust and Safety Product/Temporary Accounts - a project to implement more-or-less what you've described is planned and currently in the process of rolling out! Sam Walton (talk) 09:53, 19 November 2024 (UTC)

FYI, you can't get an exact location from an ip. 𝙏𝙚𝙧𝙧𝙖𝙞𝙣𝙢𝙖𝙣地形人 (talk) 16:01, 19 November 2024 (UTC)

Sometimes you can. It might not come down to "third desk on the right", but IPs sometimes identify a single building. WhatamIdoing (talk) 18:00, 19 November 2024 (UTC)

IP addresses will give the location of the ISP node, or if the router has a location recorded with the ISP it will show that, most private routers do not show their location and will just show the ISP node. Try it yourself on a website like https://www.iplocation.net/. But you're right, sometimes it can that's true. 𝙏𝙚𝙧𝙧𝙖𝙞𝙣𝙢𝙖𝙣地形人 (talk) 18:12, 19 November 2024 (UTC)

It's certainly true less often than it was in 1990s. WhatamIdoing (talk) 21:46, 19 November 2024 (UTC)

The disaster of "IP masking" is that it will give all the different IP addresses used by the editor over the past 90 days, and of course you can keep sampling so you can effectively build up a profile of the editor's movements in perpetuity. This highly personal information is made available to autoconfirmed editors, so virtually everyone. This is dynamite, and the GDPR has specific safeguards so that the editor can see what she is getting herself into before she commits herself. The Foundation knows nobody would ever accept these terms so lies by omission - it simply says "a temporary account will be opened for you" without warning that the editor's control over her personal information will be cut off. They run a talkpage over at Mediawiki, but even when they are pinged they ignore the awkward questions. LD asked a question of Niharika Kohli at 13:22 on 15 November and is still waiting for an answer. — Preceding unsigned comment added by 92.25.132.250 (talk) 14:24, 28 November 2024 (UTC)

Agree that the requirements should very much not be available that easily (although the actual terms are 6 months and 300 edits). I wouldn't be opposed to making it available only to CheckUsers or administrators, as they actually have some level of community vetting (or to make a new specific permission for that purpose). Another possible thing that could be done would be to log the IP checks to ensure transparency. Chaotic Enby (talk · contribs) 15:08, 28 November 2024 (UTC)

See the Guardian article by Victoria Turk, In our house, 'smart' devices aren't welcome (9 November). 92.25.132.250 (talk) 14:33, 28 November 2024 (UTC)

Wiki AI?

I would happily pay 25 cents per query if Wikipedia had its own AI chat interface. I use the Co-Star app (astrology) in this way already. I find the cost is worth the value. Free AI summaries available in search engines suffer from having too much garbage input (aka, the unrestrained data of the internet) to produce viable output. I would find it useful to have an AI interface built into Wikipedia. I already trust the information here and all "training data" for the hypothetical bot would effectively be open source. I would trust an AI bot managed by Wikipedia much more than I would trust an AI bot managed by any other entity. And I would be willing to pay for the service more often than I would be able to continue supporting the site through donation. 2603:6080:9F00:B05D:6205:4DF2:8C83:4343 (talk) 22:14, 18 November 2024 (UTC)

Well, Wikipedia is free and open-source, so we won't be implementing a paid AI chatbot on principle. Regarding the idea of an AI chatbot in general, they are often prone to hallucinations and not necessarily as accurate as they are confident. And they can't be edited by individual users in case they were trained on factual errors, which again goes against Wikipedia's principles. Chaotic Enby (talk · contribs) 22:22, 18 November 2024 (UTC)

I find the cost is worth the value. But is the value worth the cost? —Tamfang (talk) 21:03, 24 November 2024 (UTC)

You could try NotebookLM from Google Labs as your interface to Wikipedia content. It's a pretty useful tool in general. Sean.hoyland (talk) 12:49, 30 November 2024 (UTC)

Potentially moving the deletion venue for MediaWiki: pages

The nature of MediaWiki: pages is always such that there will almost never be deletions. And when there are, it is because some message is no longer used. Because of the very technical nature of MediaWiki: pages, I don't think WP:MFD is a suitable venue, since not all users at WP:MFD will have the technical expertise to determine something like whether a MediaWiki message is used or not, etc.

We have WP:TFD primarily for templates and modules. I want to see maybe we can workshop a proposal for determining if, when, and how MediaWiki pages are deleted. I do wonder if maybe due to the nature of MediaWiki: namespace that maybe it should be exempt from most of the speedy criteria and only deleted after a discussion at WP:VPT, where editors can discuss the MediaWiki software, etc.

See Special:PrefixIndex/Wikipedia:Miscellany_for_deletion/MediaWiki: which shows very few MFD discussions. Awesome Aasim 03:45, 30 November 2024 (UTC)

No matter where the discussions are hosted, it will still be true that "not all users...will have the technical expertise to determine something", or anything, about the page. This is a case where the hosting location is much less important than the efforts to advertise the discussion in suitable places. Fortunately, since there are very few discussions about deleting those pages – 49 since MFD's creation, and only one this entire calendar year that wasn't started by you – it won't require be a significant burden to make sure that those few get advertised. WhatamIdoing (talk) 08:00, 30 November 2024 (UTC)

Hmmm... That is also true. The closest thing I can think about for technical discussion of pages, etc. would be WP:TFD. We could probably rename that process "Technical pages for discussion" and then it would include MediaWiki: pages as well (as well as maybe user scripts). WP:VPT and WP:TFD seem to have the highest number of technical editors discussing functionality, etc., so maybe we should lean there. Awesome Aasim 16:49, 30 November 2024 (UTC)

I actually started workshopping what a "Technical pages for discussion" process might look like. Awesome Aasim 18:57, 30 November 2024 (UTC)

See also the two proposals Awesome Aasim has made regarding speedy deletion of MediaWiki pages: November 2024, March 2024 and an earlier one by a different editor Wikipedia talk:Criteria for speedy deletion/Archive 78#Add criteria for MediaWiki namespaces.

Wikipedia:Miscellany for deletion/MediaWiki:Abusefilter-disallowed/de, initiated by Awesome Aasim in February 2021, came to the consensus that an RFC should be held to determine whether the community desired the deletion of those pages. A discussion was held at Wikipedia:Village pump (proposals)/Archive 183#Foreign-language interface messages. There was a unanimous consensus to keep either most or all. Thryduulf (talk) 13:33, 30 November 2024 (UTC)

Requested move ECR notices

WP:GS/RUSUKR, WP:GS/AA, and WP:GS/KURD all state that:

[…] non-extended-confirmed editors may not make edits to internal project discussions related to the topic area, even within the "Talk:" namespace. Internal project discussions include, but are not limited to, Articles for deletion nominations, WikiProjects, requests for comment, requested moves, and noticeboard discussions.

Of those discussions:

• WikiProjects, RfCs, and noticeboards aren't visible to readers, so non-extended-confirmed editors are less likely to encounter them.
• AfDs are on their own page, so they can simply be given extended-confirmed protection.
• RMs are the exception – they're advertised on the relevant articles, and they're held on article talk pages. These talk pages are only protected sparingly (in response to significant disruption), since there are legitimate reasons for non-extended-confirmed editors to be editing them.

Currently, the only way for non-extended confirmed editors to know that they're not permitted to participate in these RMs is to:

1. Spontaneously scroll to the top of the talk page.
2. Read the entire GS notice, and understand that requested moves are an exception to the exception to the extended-confirmed restriction.
3. Click on the "extended-confirmed editors" link, learn what the term means, and understand that they are not extended-confirmed.

I think this is a highly implausible sequence. If we want non-extended-confirmed editors to stop participating in these move requests, we should put a template in the RM section that instructs non-extended-confirmed editors, in plain language, not to participate in them. The {{if extended confirmed}} template could be used to directly let editors know whether they are extended-confirmed (and possibly tailor other parts of the message as well). jlwoodwa (talk) 17:43, 27 November 2024 (UTC)

I mean sure, but WP:Nobody reads the directions. So it might reduce the numbers a little, but the unfortunate truth is that much of the time we are just going to end up explaining this on user talk pages to unhappy people. 184.152.68.190 (talk) 20:11, 28 November 2024 (UTC)

Then I wonder if we should only be displaying the {{requested move notice}} to extended-confirmed editors, on those articles where the ECR forbids non-extended-confirmed editors from participating in RMs. On the other hand, extended-confirmed editors might be reading Wikipedia while logged out, who would log in and participate if they see the notice. jlwoodwa (talk) 20:17, 28 November 2024 (UTC)

Not a bad idea, and yes I could still see where some would object because an EC editor might encounter an article while logged out, seems enough of an edge case to where hiding might be worth it anyway. The other concern is that even people who only ever read should be alerted that something might happen to the page that has come up in discussions about the utility of AfD notices for example, but in considering the tradeoffs hiding from non-EC may well be the least bad option here, though it's certainly no panacea. 184.152.68.190 (talk) 20:59, 28 November 2024 (UTC)

Since move discussions normally result in working redirects, I don't think that there's a need for non-editors to be warned that the page's title might be spelled differently in a week or two. The argument with AFD is that the article might cease to exist, so the non-editor might want to save an offline copy in case it disappears altogether. WhatamIdoing (talk) 07:54, 30 November 2024 (UTC)

That's a good point, and further strengthens the case for hiding, can be combined with the originally proposed notice in hopes of reducing numbers a little further still. For the remainder maybe some type of user talk page notice that explains what happened and why as gently as can be managed while still stressing the seriousness of GS restrictions. 184.152.68.190 (talk) 02:16, 1 December 2024 (UTC)

Template for Tetragrammaton

In article concerning Judaism, there ae multiple references to the Tetragrammaton, both in Hebrew and romanized. It would be convenient to have a template that generated יהוה (YHVH, YHWH), possibly with an option for the older Canaanite script. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:53, 26 November 2024 (UTC)

This is the English language Wikipedia and so there's already a template for the English version of this: {{LORD}}, which displays as LORD, as per the KJV. Andrew🐉(talk) 17:57, 3 December 2024 (UTC)

That template generates the English translation of the substitution אֲדֹנָי (Adonai transl. my Lord[s]), not the actual Tetragrammaton. There are multiple places in wiki where the actual Tetragrammaton is given, and it would be convenient if there were a template to save typing. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 20:58, 3 December 2024 (UTC)

Disambiguation pages should auto-generate

Hello all,

Per MOS:BOLD, the first appearance of an article's titular subject should be bolded, as should any alternate names for the article. When I first started editing Wikipedia, I was surprised that those were just manual boldfaces with HTML tags. I was wondering whether it would be better to apply it with something like this: " {{article main name|Apples}}, also known as {{article alternate title|Oranges|oranges}}, are a fruit. " which would display as "Apples, also known as oranges". The two templates would auto-populate the title and short description into a disambiguation page if there were multiple instances of the same name. Further, a hatnote would be auto-created (if there were multiple instances of similarly-named pages, the hatnote would lead to the disambiguation page, and if there was only one, it would lead to the other article).

I think that this would vastly improve the simplicity of maintainging disambiguation pages and hatnotes. However, it could increase barriers to entry for new users, but that could be mitigated with editnotices, template documentation, etc. It may also be difficult to implement, but I foresee bots being able to implement the work.

JuxtaposedJacob (talk) | :) | he/him | 21:00, 30 November 2024 (UTC)

"Apples, also known as oranges"? I'm not sure I understand your use case for making such pages so inaccessible and code-ridden for newcomers. Aaron Liu (talk) 04:09, 1 December 2024 (UTC)

@Aaron Liu - Yeah, I see what you're saying, but I think most of the learning curve could be eliminated if, when someone tries to edit a disambiguation page, an editnotice of some sort appears and recommends that they go edit the source page.

JuxtaposedJacob (talk) | :) | he/him | 07:51, 1 December 2024 (UTC)

On the technical side, disambiguation pages already have edit notices, so that part would be feasible.

On the more practical side, disambiguation pages are often more complex than just listing articles with the same title. For instance, a concept might be listed in a disambiguation page even if it doesn't have an article, but is prominently mentioned at an existing page (the kind of thing that would warrant a {{R to section}} or {{R to related topic}}). Spelling variants (especially for languages written in the Arabic script where romanizations can often vary) are also grouped together in a similar page, while more subtle issues come up with partial title matches. I can also foresee the issue of organizing the disambiguation page itself, especially with things like proper names that are often (but not always) moved to a separate page. Chaotic Enby (talk · contribs) 09:41, 2 December 2024 (UTC)

@Chaotic Enby - Ahh, good points, thanks.

JuxtaposedJacob (talk) | :) | he/him | 10:19, 2 December 2024 (UTC)

@JuxtaposedJacob, for the list of entries on a dab page, would Template:Annotated link be a step in the direction of what you want?

• Apple – Fruit that grows on a tree
• Apple Inc. – American multinational technology company
• Apple pie – Dessert pie made with apples

WhatamIdoing (talk) 00:59, 4 December 2024 (UTC)

Sometimes I wish consensus was on my side more, sigh. "This template should not be used for annotating links on disambiguation pages." However, thank you for pointing me to that link, that is helpful.

JuxtaposedJacob (talk) | :) | he/him | 01:26, 4 December 2024 (UTC)

Well, that was 2018. WP:Consensus can change. Maybe it's time that it did. WhatamIdoing (talk) 04:46, 4 December 2024 (UTC)

Looking at the three reasons given for not using them, while the first one (style issue) can be easily fixed with a new template parameter, the other two are still very much problematic. Short descriptions are not necessarily written with disambiguation pages in mind (or even consistent from one disambiguated term to the next), and different use cases of short descriptions might conflict with each other's needs. And, well, transcluding data on disambiguation pages from other pages (which is actually close to the current proposal) still brings the issue of traceability of the edits. Chaotic Enby (talk · contribs) 08:21, 4 December 2024 (UTC)

Independent Politicians

Where possible add a section where general info is for sn independent politicians indicate what political position they are ie center, left, right etc 2001:BB6:514B:A300:D35B:58F7:1327:A55 (talk) 00:39, 22 November 2024 (UTC)

I don’t know what that means Dronebogus (talk) 10:59, 24 November 2024 (UTC)

{{Infobox officeholder}} already has a parameter for "Other political affiliations", which might be what you are looking for. Otherwise, yes, a section in the article text can be written if there are enough sources to position the person on the political spectrum, but there shouldn't be a strict guideline mandating it to be present, especially since these affiliations can be controversial or contested. Chaotic Enby (talk · contribs) 12:02, 24 November 2024 (UTC)

There are also many politicians whose views do not neatly fit into a simple left-centre-right box, especially as right-of-centre UK politics is roughly equivalent to the left wing of mainstream US politics. Thryduulf (talk) 00:49, 5 December 2024 (UTC)

The Nolan chart would be slightly better, but as you say, would have to be adjusted for different countries. Donald Albury 02:14, 5 December 2024 (UTC)

Dead pixels, an expansion to WP:CITEWATCH, a new noticeboard?

Bit of a long one... more of an essay at this point really, but IMO, it might be worth it to prevent editor burnout and bring in new users, so here goes: You know how once one spots a dead pixel, they can't seem to ignore it? Then one starts wondering whether the monitor vendor has either: gotten sloppy with their work... or if they just got unlucky given the volume of monitors that get put out by the vendor. Then the dread of calling the warranty department...

Just like the analogy above, the news and research outputted by reliable sources is generally problem free. But because of the volume of information, occasionally errors will get in. Sometimes even unscrupulous outlets gets in. But unless one is motivated or knowledgeable enough, few will go through the effort of comparing what the reference says to its references (reference-in-reference). This is the dead pixel problem I'm talking about, and just like a dead pixel, annoys the crap of the person who sees it, for better or worse. Then comes the process of "fixing" it: currently, original research issues, and reference-in-reference issues are handled in science by PubPeer, whose extension is used by a paltry number of users. Response times by authors take days, maybe years even with relentless journalism. At any rate, most people who feel compelled to edit Wikipedia due to accuracy problems have probably never heard of PubPeer. And as for issues with regular journalists, I suppose one could turn to opinions by third parties like NewsGuard? And meanwhile, they can usually get away with publishing contradictory health news without being called out for it.

All made more worrying given that impact Wikipedia has on the real-world non-Wikipedians, like judges and scientists. Recent political developments, as well as LLM usage (see WP:CNET), mean that once reliable sources could suddenly hallucinate or contradict other sources on a whim. Maybe the errors made daily won't be indicative of LLM usage... but they could. In any case, we don't currently track these issues, so whose to say what patterns unreliable sources follow?

Mistake or no mistake, when the inaccuracy is inevitably spotted (probably by us, I wonder why...), an attempt will probably be made to re-balance the article or add footnotes following WP:Inaccuracy. This works great... if you are the only editor of a given article. For everyone else, because not everyone will necessarily see a dead pixel as a big deal, the actions may seem disproportionate and/or violate certain consensus policies, and the talk page will go on and on, maybe then to WP:DRN driving away casual but knowledgeable editors, all of which will be seen by hardly anyone, let alone the original author of the source. One could then go to WP:RSN, but that noticeboard is really only equipped to handle the most problematic and fringe sources, not really the daily errors that get published by sources day to day. We burn out, and the world, by and large, hardly notices the dispute.

To solve this, I propose some sort of objective-ish tracking in WP:CITEWATCH of reference-in-reference accuracy (in line with Wikipedia's policy of WP:NOR) as well as other issues like typos, linking issues, cotogenesis, copyright violations, notable omissions, and most importantly, corrections (sure sign of a RS), and the time elapsed from error spotting to correction for refs, all heuristics that, when aggregated, could be indicative of a sloppy copyeditors or cursory peer review. Editors could put in a template with the relevant issue, hidden by default until patrolled. If there is a dispute, a new reference-in-reference noticeboard, split into categories (typos, copyright violations, etc.)

Bonus benefits - we might finally:

• Know which MDPI journals have decent peer review, allowing them to build a reputation?
• Create an easy place to show that the consensus on WP:ALJAZEERA is justified?
• Create an incentive to keep more accountable (especially on health related topics)? As well as obscure sources on obscure topics that may only be read by the Wikipedian.
• Reduce biting and attrition by creating an easy place for sub-WP:RSN issues to be reported, counted and easily exportable to PubPeer or elsewhere?
  • Problematically high counts could then easily be reported to WP:RSN without the need for extensive, hard-to-read discussion.

Other references

External videos No, Sabine, Science is Not Failing, Somewhat related video by Professor Dave that was coincidentally published while I was thinking about this. Mentions PubPeer. See also WP:WTW. Retraction Watch: 'An isolated incident': Should reviewers check references? The whole category Basis for "notable omissions": PNAS wouldn’t let authors cite unpublished manuscript. Now, it admits it was wrong. Ask Retraction Watch: Is it OK to cite a retracted paper? Miscellaneous papers: [1][2]

Unfinished ideas, subject to change

Older pre-internet sources might be less affected by ref-in-ref errors, since the reader could be reasonably expected to check the sources, necessity. WVhere ref-in-ref notices go to the reader: Probably inside ref tags, after the chosen citation template? This proposal could involve multiple changes to various guideline pages. WP:Inaccuracy will probably be changed the most by this proposal. Patrolling - Mostly in anticipation of misunderstanding of policy, and WP:NOR. Noiceboard name - RRN, reference-in-reference noticeboard? To avoid flooding the noticeboard, require discussion on talk page first? Split noticeboard into categories? Categories - Categories will be separated into errors that will be reported to readers when patrolled, and those that will just be tracked by an expanded SOURCEWATCH table, for later discussion on RSN. General typos - just track, probably a mistake, and shouldn't happen often with vigilant peer reviewers. Ref-in-ref notable omission - Things like not disclosing a certain ref-in-ref is a preprint, failed, etc. Probably should report to the reader. Ref-in-ref typo - Linking to the wrong paper in the paper's references. This should be reported to to the reader. Ref-in-ref contradiction - Errors in copying data from another paper to the paper, making statements that are not supported by the other paper. I feel like this should be reported, like other the other Ref-in-ref categories Copyright violation/plagiarism - Ref should be removed as soon as possible. If not, report, provide copyvio report. Verifably illogical - Claims such as "birds don't exist" or "FDR invented the Federal Register" that would require overlooking enough sources to be problematic. This is mostly a catch-all category, for LLM hallucinations or otherwise, that should be used with caution, and should probably just be tracked. Citogenesis/Citing Wikipedia - Apparently it's still a thing, but I'd prefer sources be honest rather than hide it (see [3][4]). Policies should encourage the use of permalinks to properly cite Wikipedia. Speaking of perverse incentives... Perverse incentives? Less citing of sources overall? Counterpoints: Existing incentives to cite to increase impact or whatever. Could be solved with another category: General contradiction - Tracking only, focus only on all refs that were ever cited on Wikipedia to reduce scope. Some contradictions are expected, but an excessive number of contradiction notes - more likely to be fringe?

Rolling this out might take an extended period of time, and will probably involve the WMF as well as new templates, modules, instructions, etc. Thoughts on this, as well as how improvements could be broken up or rolled out? ⸺(Random)staplers 03:56, 25 November 2024 (UTC)

This seems to have a lot of thought, but frankly I have no idea what this proposal is actually proposing. Ca ^{talk to me!} 07:30, 1 December 2024 (UTC)

Is the proposal about placing discussions of reliability about the cited source inside the citations themselves? Ca ^{talk to me!} 07:32, 1 December 2024 (UTC)

I must be tired I think, but I do not think I understood anything at all about the idea, whether it is the how or the why. The entire way the reliability of sources is approached is that no matter how trusted they are, no publication ever gets a blank check on any subject, and to me it does not seem like there is an issue of under-reporting perceived inaccuracies or bias either, so I am not sure I see the point. Choucas Bleu^talk_contribs 12:51, 5 December 2024 (UTC)

Linking years for specific topics

Per MOS:UNLINKDATES, years are not linked by a large majority of articles. Though, many articles do link to "xxxx in ____" articles (e.g. 2000 in television or 1900 in baseball). I do not feel like these types of articles should be linked to. The topics are broad, and in some cases there are better articles to be linked to. Roasted (talk) 18:43, 7 December 2024 (UTC)

We had a discussion about this recently, although I'm unable to immediately find it. IIRC the consensus was that the links add value in some cases (and thus should be retained) and don't in others (and thus should be removed). If my memory is correct, then this is something that can only be determined at the level of the individual article or small groups of articles. In general you can be WP:BOLD, especially if a single more specific relevant article exists, but explain why you think a change is beneficial and be prepared to discuss if others disagree. I don't believe there is (or should be) a default preference either for or against these links. Thryduulf (talk) 23:32, 7 December 2024 (UTC)

I remember that discussion, and my recollection is the same as yours. WhatamIdoing (talk) 03:38, 11 December 2024 (UTC)

Photo gathering drive for town, village, and city halls

Like how Wikipedia and Wikimedia Commons has the National Register of Historic Places drives for pictures. There should be effort put into getting the town halls, village halls, and city halls pictures. Every town, every village, every borough, every city, and county has a Wikipedia page and I think they should all have a picture posted of the administrative building. Wikideas1 (talk) 08:21, 4 December 2024 (UTC)

One consideration is that shorter articles have limited space for images, and a photo of the building housing administrative offices of a politically defined place may not be the best representation of that place. It is fine to upload such pictures to Commons, but their use may not be justified in every article about a place. Donald Albury 15:44, 4 December 2024 (UTC)

I like the concept, but I feel the drive would be better if any picture of a populated place would be admissible. Places like unincorporated communities and ghost towns don't have municipal buildings, but still would be bettered with a picture. Roasted (talk) 18:30, 7 December 2024 (UTC)

This sounds similar to Wikipedia:Wiki Loves Monuments. @Wikideas1, if you want to pursue this, then you should probably look at similar campaigns in c:Category:Wiki Loves and see if there's one that overlaps with your goal. WhatamIdoing (talk) 03:31, 11 December 2024 (UTC)

It's all fun and games until the photos get deleted due to a lack of freedom of panorama. If you think somewhere in Wikipedia consistently lacks building photos, there's a good chance it's a copyright issue. CMD (talk) 03:38, 11 December 2024 (UTC)

I'm not sure if the law of every country would apply. EEpic (talk) 04:50, 11 December 2024 (UTC)

@EEpic: See Wikipedia:Image use policy#Photographs. We generally respect all copyrights, even if the material would not be copyrightable in every country. Donald Albury 16:56, 11 December 2024 (UTC)