Policy | Technical | Proposals Idea lab | WMF | Miscellaneous |
The proposals section of the village pump is used to offer specific changes for discussion. Before submitting:
Discussions are automatically archived after remaining inactive for nine days.
Should all community discretionary sanctions (DS) be updated to use the new contentious topics procedure? Awesome Aasim Refreshed 01:18, 8 March 2024 (UTC) 05:55, 7 February 2024 (UTC)Reply
Background
edit
In late 2022/early 2023, the discretionary sanctions procedure was overhauled by ArbCom and converted to "contentious topics". With now two different processes for two different kinds of sanctions there is now a lot of fragmentation and inconsistency in how contentious topics should be handled, with even conflicting wording. The main goal of this RfC is to unify the procedure used for all areas where general sanctions are in effect with the one designated by ArbCom, going forward.
As proposed at this time, there will be the some similarities and differences between community and arbitration contentious topics, including:
And of course, ArbCom would be able to convert community contentious topics to those designated by the committee, after which all the ArbCom venues would have to be used from that point forward, though existing restrictions would remain appealable to WP:AN until renewed at ArbCom.
I wonder if adding in stuff to the WP:CTOP page and similar would require the petition and referendum process. If so, then I guess the merging of templates would have to hold off until a former petition and request for amendment actually passes. It is possible ArbCom will green light the merge if this RfC passes, but I do not know. Awesome Aasim 05:55, 7 February 2024 (UTC)Reply
The statement I refreshed the RfC tag because there is not enough input to gauge consensus. Could this be because this is uncontroversial or what? Awesome Aasim 19:58, 8 March 2024 (UTC)Reply
Could well be :) Selfstudier (talk) 10:27, 9 March 2024 (UTC)Reply
I think it's because many editors simply don't know what's going on. I didn't know this discussion was taking place. I'm still not sure what the change in policy is, only that, if it has been changed, the system should be clear about it. Are we dissolving Discretionary Sanctions? Is AE not going to be a thing any more? Is it merging with ANI? Darkfrog24 (talk) 22:37, 17 March 2024 (UTC)Reply
@Darkfrog24 The question is really just about making community sanctions use the new contentious topics procedure. Awesome Aasim 23:45, 17 March 2024 (UTC)Reply
Okay. What is the new CT procedure? Do you know how it's different? I just read through one of the links that Newslinger provided above, and I'm having trouble picking out differences. Darkfrog24 (talk) 00:35, 18 March 2024 (UTC)Reply
For full details, see Wikipedia:Contentious topics. It's basically a renamed version of discretionary sanctions, with changes made based on community feedback received during the 2021–22 review of discretionary sanctions. Some highlights: there is a standard set of restrictions that a single administrator can impose on their own discretion. Restrictions outside of these can be imposed by a consensus discussion at the arbitration enforcement noticeboard. Sanctions are no longer limited to one year, but after a year, sanctions that were imposed by a single adminstrator no longer have to be discussed at the arbitration enforcement noticeboard to be modified. Survey (community contentious topics)
edit
Cooperation of ArbCom
edit
all community general sanctions (DS)
in the initial question is misleading. "General sanctions" is not synonymous with community authorization for discretionary sanctions. I think the intent should be clarified that the proposal only affects discretionary sanctions authorized by the community, and not all general sanctions. isaacl (talk) 19:03, 7 February 2024 (UTC)Reply
Users no longer have to be made aware of each specific topic area. They only have to be notified once using a specific template about the contentious topic system. Striking out inaccurate description. isaacl (talk) 01:56, 18 March 2024 (UTC)Reply
Users no longer have to be made aware of each specific topic area. They only have to be notified once using a specific template about the contentious topic system.
That would contradict the CTOP regime. Even among the Arbcom sanctions, editors still have to be notified about topic areas individually. The WordsmithTalk to me 19:54, 18 March 2024 (UTC)Reply
I am proposing that tp:
be added as an alias to the Template:
namespace per this discussion.
Note: Though previous aliases were already listed on perennial proposals, it proposed t:
, which would have conflicted with some article titles, or be confused with the Talk:
namespace. Tp:
, on the other hand, wouldn't, and would make it way quicker to look up a template in the search bar.
It seems to me we might have wide enough support for this to pass as a general concept. But I think a closer would be unable to decide on the specific alias to use, so we'd be looking at another RfC to decide that (ugh). Therefore a separate survey is in order. Eliminating This section is not for opposition to the general concept; see my reply to Anomie's Oppose, below. ―Mandruss ☎ 00:53, 10 April 2024 (UTC)Reply
I do not know about the rest, but on chrome, using the search engine shortcut feature worked perfectly.
That's it. After that, just type out your shortcut, followed by title, separated by a space/tab, on the address bar and hit enter. Everyone can pick whatever shortcut they like, for all namespaces and even page prefixes of their choice. You can add one for https://en.wikipedia.org/wiki/Wikipedia:Requests_for_adminship/%s to go to RFAs by just typing out usernames, for example. Best, Usedtobecool ☎️ 05:47, 9 April 2024 (UTC)Reply
Edit (during rfc): tp:
was not fully supported due to it being confused with "Talk Page", however other options were proposed, like hard coding {{
being replaced by Template:
in the search bar, or other aliases like tmp:
. Cocobb8 (💬 talk • ✏️ contribs) 15:19, 16 March 2024 (UTC)Reply
Oppose "Template" is not a long word, and nobody abbreviates it as "tp" these days. This seems pointless. * Pppery * it has begun... 15:27, 16 March 2024 (UTC)Reply
wp:
for Wikipedia:
, which is 10 characters, while Template:
is 9 characters. Cocobb8 (💬 talk • ✏️ contribs) 15:29, 16 March 2024 (UTC)ReplyNobody abbreviates it as "tp" these days
. Even if that is true it is not a reason for us not to do so. Wikipedia is big enough to be making fashions rather than following them. Phil Bridger (talk) 21:16, 16 March 2024 (UTC)Reply
Well said. — Frostly (talk) 06:28, 5 April 2024 (UTC)Reply
Support I'd find it useful. It's less effort to type "tp:infobox person" in the search box than "template:infobox person" (which is how I usually navigate to wp: and template: pages). Schazjmd (talk) 15:52, 16 March 2024 (UTC)Reply
Support per Schazjmd. 🌺 Cremastra (talk) 15:57, 16 March 2024 (UTC)Reply
Support I'd absolutely love this. I've often wondered if there was some technical problem that was preventing us doing this. Usedtobecool ☎️ 16:00, 16 March 2024 (UTC)Reply
Support: Pretty nice QOL change. Per Schazjmd. ARandomName123 (talk)Ping me! 16:35, 16 March 2024 (UTC)Reply
there's nothing available to use for the corresponding talk pages
See Nirvana fallacy. — Frostly (talk) 06:29, 5 April 2024 (UTC)Reply
The template for linking a template is called {{tl}}. Shouldn't we have some consistency between this and the short-cut? Or is "tl" already used? Phil Bridger (talk) 21:16, 16 March 2024 (UTC)Reply
{{
to Template:
, a namespace shortcut (tp:
) would help in edit summaries and customised browser search boxes. -- Michael Bednarek (talk) 23:55, 16 March 2024 (UTC)Reply
Oppose Adding layers of obfuscation is not helpful. If I want to refer to {{convert}}, writing Template:Convert
is easy and helpful to someone reading my comment. Writing Tp:Convert
is unnecessary jargon that saves under a second of typing at the cost of head-scratching for readers. tp
would be "talk page" for many. Johnuniq (talk) 01:00, 17 March 2024 (UTC)Reply
Oppose As someone who has next to no involvement with template editing, I immediately think of 'talk page' when I see 'tp'. It would confuse many people who edit outside of the technical areas of Wikipedia. (Summoned by bot) JML1148 (talk | contribs) 06:57, 17 March 2024 (UTC)Reply
Rename the template mainspace from "Template:" to "Plantilla:" and use "Pl:" as a shortcut CactiStaccingCrane (talk) 18:02, 18 March 2024 (UTC)Reply
WP
prefix, at least the shortcut links are mostly self explanatory, but it wouldn't be obvious to a newcomer what, for example, tp:birds is, or why it's not an article. --Ahecht (TALK
PAGE) 18:17, 18 March 2024 (UTC)Reply
tp:
wasn't the best as others have pointed out. I'll continue gathering some ideas and then conduct a sub-RfC to see what option would be best, as long as the consensus doesn't seem to be oppose. Cocobb8 (💬 talk • ✏️ contribs) 19:52, 18 March 2024 (UTC)Reply
neutral i could go either way. I like the hard coding option of having 'template' be dropdown option in the menu. Slacker13 (talk) 01:29, 20 March 2024 (UTC)Reply
Support – I don't think that adding the t: will add an another level of obfuscation. The current method of making interwiki link is already obscure and complicated, specially for newbies, instead a simple alias to the template namespace will be easy and handy in researches. -- ZandDev 13:57, 20 March 2024 (UTC)Reply
tp:
though, not t:
as it was rejected previously: does that work for you? Cocobb8 (💬 talk • ✏️ contribs) 13:58, 20 March 2024 (UTC)Reply
tp:
directly with templates, but with talk pages. -- ZandDev 16:04, 26 March 2024 (UTC)Reply
Oppose I do work with templates but I feel that this is not an intuitive shortcut and could easily be confused with "talk page". (t · c) buidhe 04:57, 21 March 2024 (UTC)Reply
Support , I had typed TP: prefix in the past thinking that I would get the template page without success. This would be useful in different scenarios (just like the WP: prefix). And its use is optional, so if someone doesn't like it, they can go with the full Template: as ever. Alexcalamaro (talk) 05:32, 21 March 2024 (UTC)Reply
Oppose. Unnecessary, and just as with T=Talk, TP=Talk Page. wjematherplease leave a message... 08:01, 21 March 2024 (UTC)Reply
Neutral Agree with the principle, would prefer access to a shortened version; but also agree that the proposal is too close to talk page. Regards, --Goldsztajn (talk) 22:08, 21 March 2024 (UTC)Reply
I think supporting {{ in the search bar would be sufficient to support the use case of issue. But beside that, I agree with oppose comments above. Izno (talk) 02:48, 22 March 2024 (UTC)Reply
Oppose per above. Not intuitive and I'm not convinced this solves a genuine problem -Fastily 21:26, 24 March 2024 (UTC)Reply
Strong support because I have typed "Twmplate" in the search bar too many goddamn times. Mach61 21:03, 26 March 2024 (UTC)Reply
Support: I have to do everything on mobile, and am looking up templates all the time. This would make that a significantly less laborious and typo-prone experience. But I'd be happy with some other 2- or 3-letter shortcut if TP: is a problem. No more than 3 letters, though. Also I keep typing TP:, TMP: or TPL: without thinking, expecting them to work. But I only want it for search purposes. I'd be opposed to its use as jargon for referring to templates. — Preceding unsigned comment added by Musiconeologist (talk • contribs) 01:34, 28 March 2024 (UTC)Reply
{{|}}
. There are two points, though: (i) it's counterintuitive and annoying that the whole word is needed, in contrast to wp: etc.; and (ii) beyond three characters, it stops really being a shortcut because it's only a bit shorter. Part of the annoyance is in having to remember that there isn't a 2-letter prefix to use. Musiconeologist (talk) 00:43, 10 April 2024 (UTC)Reply
Alias {{ (if technically possible): no ambiguity and concise. Typing {{Rfc should take you to Template:Rfc and so should {{Rfc}}
. I'm neutral on aliasing TP
as the ambiguity may be balanced out by utility. I like T
better despite previous community rejection. — Bilorv (talk) 22:37, 29 March 2024 (UTC)Reply
It is technically possible for {{ to be implemented, and there already is code for it if you want to try it out. Cocobb8 (💬 talk • ✏️ contribs) 22:41, 29 March 2024 (UTC)Reply
Support any shortcut except just T. Aaron Liu (talk) 02:00, 30 March 2024 (UTC)Reply
Support saves me a few characters/seconds when accessing templates through the search bar, might even make up for the seconds wasted to write this comment. Tl, tmp or tpl works for me if people object to tp. Draken Bowser (talk) 21:24, 3 April 2024 (UTC)Reply
Support, this is an excellent idea. I type "Template:" in the search box a lot and it seems many other users do as well, so it makes sense to add a prefix. Preferably it wouldn't be "TP" if a good amount of people have issues with that; I don't care about what ends up being chosen as it remains relatively short (2 or 3 letters). ― novov (t c) 02:59, 6 April 2024 (UTC)Reply
Support. Aliasing {{ is less preferable to me because a shortcut would also allow shortening template links in edit summaries, where {{tl}} is unavailable. The particular shortcut used doesn't matter to me, just that I won't have to type "Template:" every time. Nickps (talk) 12:46, 8 April 2024 (UTC)Reply
Think about the possibility of [[{{example}}]] Aaron Liu (talk) 15:11, 8 April 2024 (UTC)Reply
No. Why should we introduce a way to link to pages that only works in edit summaries and nowhere else? (Note that using it elsewhere will transclude example instead.) TMP:example on the other hand, will work in Search, in talk pages and in edit summaries and the fact that it's a unified syntax makes it easier for non power users to learn. I'm not opposed to introducing {{ for Search (alongside a regular shortcut) as long as we take measures to make sure that people don't end up on the wrong page. That is, if e.g. {{foo}} exists we should add a {{technical reasons}} hatnote to Template:foo/doc. Nickps (talk) 16:21, 8 April 2024 (UTC)Reply
{{
. Nickps (talk) 12:57, 9 April 2024 (UTC)Reply
Support. I've been at this for ten years and still hate calling up a template doc because it requires so damn much typing. The more typing, the more opportunity for typos that have to be corrected (and I'm good at typos). No objection to something other than TP, such as TM, although no doubt someone would say that could be confused with something else. The longer it gets (e.g. TMP), the less benefit. Something like this doesn't need to be descriptive, just easy to remember. ―Mandruss ☎ 05:02, 9 April 2024 (UTC)Reply
Doc pages don't require much more typing - and if four characters is too many, there is always the "view" link top right of the green doc box that is displayed on the main template page. --Redrose64 🌹 (talk) 13:18, 9 April 2024 (UTC)Reply
I'm talking about calling up template doc when I don't have a link to click, such as {{infobox person}} (I'm looking to read the doc, not edit it, so the transclusion on the "main template page" is all I need). So I'm typing into the search box, and typing nine characters before I even get to the template name. I would dislike three characters (tm:
) one-third (3⁄9) as much. My question is: Why NOT do this? Where's the significant downside? ―Mandruss ☎ 19:27, 9 April 2024 (UTC)Reply
I think Redrose thought that you meant actually manually going to the /doc subpage. Aaron Liu (talk) 20:23, 9 April 2024 (UTC)Reply
tp:
, I see at least tentative support for t:
,
, tl:tm:
, tmp:
, and tpl:
(am I missing any?). I don't think this needs ranked voting—the specific choice isn't that critical—so it would be great if editors could just specify their one favorite. ―Mandruss ☎ 22:31, 9 April 2024 (UTC) Redacted 05:55, 14 April 2024 (UTC)Reply
tm: t: ―Mandruss ☎ 22:31, 9 April 2024 (UTC) Redacted 04:50, 12 April 2024 (UTC)ReplyI'd be fine with any of the choices. Schazjmd (talk) 23:18, 9 April 2024 (UTC)Reply
{{
is my first choice and t is my second choice (and I don't understand why I have to say it twice). — Bilorv (talk) 09:18, 10 April 2024 (UTC)Reply
{{:
would pose a problem for many existing tools and scripts that parse wikitext, including syntax highlighting tools. isaacl (talk) 17:29, 10 April 2024 (UTC)Reply
:
to emphasize that the proposal is for a namespace alias, and not to suggest that there would be a colon in the namespace alias. Yes, the point of my comment was that not only might there be a need for changes to MediaWiki software, but to many existing tools and scripts, including syntax highlighting tools. isaacl (talk) 17:45, 10 April 2024 (UTC)Reply
tmp:
and tpl:
. Cocobb8 (💬 talk • ✏️ contribs) 14:21, 10 April 2024 (UTC)Reply
Second choice: Aliasing {{
Last choices: Anything with a number or 3+ letters
Honestly, I would suggest whoever closes this just narrowes down the 2-3 most viable options, selects one randomly, and comes up with a post-hoc justification. This isn't worth spending a lot of time on Mach61 17:22, 10 April 2024 (UTC)Reply
tm:
is the one gathering the most support so far. Cocobb8 (💬 talk • ✏️ contribs) 20:52, 10 April 2024 (UTC)Reply
I noticed that all here said that 'tp' seems to refer to 'talk page', so why not use it for talk pages?
You're proposing a tp: alias for talk:? Aren't you a bit off topic? Besides, it would save only two characters, not 5–7: a truly negligible improvement. Besides, there are at least two kinds of talk pages, article and user. That's if you exclude other talk spaces, such as this one. If any additional aliases might make sense, they would be atp: for talk: and utp: for user talk:—the words "talk page" can be ambiguous in some contexts, so I try to use those acronyms wherever such ambiguity might exist. Apologies for extending the off-topic; sometimes I can't help myself! ―Mandruss ☎ 05:06, 11 April 2024 (UTC)Replytp:
as an alias to talk:
, the latter being already pretty short. However, for whatever ends up being chosen for template:
, might it work to add an extra t in that alias for the template talk:
namespace? Say, if tm:
is the one chose, then tmt:
could alias template talk:
. Also, a shorter alias for user talk:
would be ut:
. Cocobb8 (💬 talk • ✏️ contribs) 12:54, 11 April 2024 (UTC)Reply
t:
is the existing psudeo-namespace for templates, as seen at T:CN and T:DYK? That doesn't mean you HAVE to support it, but it makes the arguments that it would be "confusing" stange, as it is already in use. Mach61 12:48, 11 April 2024 (UTC)Reply
tp:
would make it easier regardless of the platform people use to contribute. Cocobb8 (💬 talk • ✏️ contribs) 11:20, 9 April 2024 (UTC)ReplyTP:
and {{
in the Wikipedia search box with Template:
. --Ahecht (TALK
PAGE) 16:31, 11 April 2024 (UTC)Reply
Deprecating new unsourced articles
edit
I propose that articles that are created after 1st April 2024 and does not have any inline sources to be eligible for WP:PROD. Such a PROD can only be revoked after an addition of one inline, reliable, third-party source. That source does not need to completely establish the topic's notability (because that will be decided in AfD); its only job is to verify that this topic is not a hoax. CactiStaccingCrane (talk) 06:48, 17 March 2024 (UTC)Reply
- CactiStaccingCrane (talk) 07:07, 17 March 2024 (UTC)Reply
the page is not a redirect, never previously proposed for deletion, never undeleted, and never subject to a deletion discussion.So as long as the proposer reasonably believes that the deletion will be uncontroversial there doesn't appear to be any particular procedural barrier to prodding these articles now. Third, it would be helpful to see evidence that there is a problem that needs solving. A PetScan query for articles created since January 1, 2024 in Category:All articles lacking sources gives 8 results, including one article with listed references (so tagged incorrectly but still subject to this proposal) and one that is currently up for speedy deletion. The remaining six definitely have some issues, but I'm not sure we need this level of policy change to fix what seems to be a couple-of-articles-per-month problem. (OTOH, the counterargument could well be made that this just shows that the proposal is the best kind of wiki-rule: one that simply codifies existing practice to prevent future confusion. But if that's the argument it would likewise be helpful to have some quantitative details showing how this proposal maps onto existing practice.) -- Visviva (talk) 17:03, 17 March 2024 (UTC)Reply For what it’s worth, on March 1 and 2 I attempted to patrol the category in question and see if it was possible for one person to keep it down to zero. It sort of is but you run into articles that are unlikely to get deleted but next to impossible to source, and then things get out of hand if you miss a day. It’s a tough project. I just want to note that this is a burden on editors to fix, and a lot of times adding a inline source to a plainly bad article doesn’t do a lot. ForksForks (talk) 02:08, 18 March 2024 (UTC)Reply
purpose is to benefit readers by presenting information on all branches of knowledge. As others have said, having at least one source will at least verify the topic is not a hoax, and will ensure that the mentioned knowledge is not fake. These unsourced articles should at the very least be moved to a draft, in my opinion. Cocobb8 (💬 talk • ✏️ contribs) 20:38, 18 March 2024 (UTC)Reply Support. I don't love grandfather clauses either, but I think this is the least bad of the available solutions (the most bad being "Do nothing; just keep accumulating unsourced material indefinitely".) At some point, we have to turn the water off to the gushing pipe, and then we can focus on cleaning up the remaining mess. We really need to get across the idea of a "reverse BEFORE": Before you create or substantially add to an article, have in hand the reference material that verifies what you will write, and cite it. "Write first, hope someone sources it later, in practice let it sit unreferenced or CN tagged for the next ten years" should be an approach that is deprecated and ultimately not permitted (at least not in mainspace; if people want to do things backward in a draft or userspace, that's up to them.) An alternative might be to draftify unsourced new articles, and forbid returning them to mainspace until at least one source is added, but when you're already dealing with a flood, first turn the tap off. Seraphimblade Talk to me 21:04, 18 March 2024 (UTC)Reply Oppose mostly because a grandfather clause is generally a bad idea at best: why does this only become a problem on April 1, 2024? As other have pointed out, unsourced articles rarely make it through NPP and AfC, and even if we let PROD be used for this, it can still be contested and forced to go through AFD where WP:NEXIST makes it likely to be kept regardless of the number of citations in the article. The main practical effect I see is the grandfather clause, and it only makes sense if the goal of slowly removing the protection is bought into. The problem is that consensus from about a month ago doesn't show an appetite to apply this rule to articles that already exist, and without a mechanism to move the grandfather date automatically we'll have to keep having discussions to move it around which wastes time and risks running around consensus by tiring people out with constant discussions. I don't see this going well in practice. — Wug·a·po·des 21:05, 18 March 2024 (UTC)Reply
has been challenged or is likely to be challenged, and nowhere does it say that deletion of the article is the appropriate course of action for verifiable but not verified material. Thryduulf (talk) 02:51, 19 March 2024 (UTC)Reply
unsourcedarticle? An unreferenced article? An article consisting of one or more uncited claims? Or one that is not based on sources, cited or not? Those are not synonyms, and anyone who has got stuck into trying to write or salvage articles will know that there is a big difference between an article that lacks citations and an article that lacks sources.
inline source? Do you expect people to copy the whole text into the article, or do you mean inline citation? In which case, how do you square this new requirement with WP:MINREF, WP:GENREF, WP:LISTVERIFY, and WP:LEADCITE?
eligible for PROD? All articles are eligible for PROD, if the deletion is expected to be uncontroversial. Does this remove the 'uncontroversial' requirement? Does that mean that this new type of PROD can be used multiple times? Or after an AfD?
verify that this topic is not a hoax, what information actually needs to be in it? Or should it verify some of the article content? If so, how much? If not, where are you supposed to put the citation, if it doesn't actually relate to any actual article text? What about articles that are obviously not hoaxes (i.e. most of them)?
almost obsolete PROD (since folks always just unprod these and they end up at AFD). Try looking at the evidence rather than repeating silly tropes. Phil Bridger (talk) 22:30, 19 March 2024 (UTC)Reply
I propose that articles that [...] [do] not have any inline sourcescan be PRODed. Unsourced articles aren't the same as articles lacking inline citations. He then specifies (3) "Such a PROD can only be revoked after an addition of one inline, reliable, third-party source" – apparently raising the bar even higher, since articles lacking inline, reliable, third-party citations aren't the same as articles merely lacking inline citations. There must be clarity on what exactly is proposed to be changed. – Teratix ₵ 16:24, 22 March 2024 (UTC)Reply Oppose Seems to be covered well by existing (albeit broken) processes. Sungodtemple (talk • contribs) 01:01, 23 March 2024 (UTC)Reply Oppose There are ways other than deletion that can be employed to clear the backlog. I would support a draftification process for unsourced articles to get potentially problematic content out of mainspace, but simply deleting discourages new editors from learning how to write articles and ultimately staying on the site. funplussmart (talk) 02:51, 23 March 2024 (UTC)Reply Comment- MediaWiki Edit Check project - (has anyone else mentioned this? sorry if so) this looks as though it is about to deal with most of the issues raised here, to the liking of some if not of others. Ingratis (talk) 12:07, 23 March 2024 (UTC)Reply Support OrdinaryGiraffe (talk) 01:00, 24 March 2024 (UTC)Reply
==References==
section, I'm not too worried that the references aren't "inline" and require some syntax formatting to not have it summarily deleted. — xaosflux Talk 23:49, 9 April 2024 (UTC)Reply
There is currently no way to track template substitutions without adding code to templates that adds tracking marks to the template's output, and some bot watching for these marks. Aside from all that overhead, these marks may make use of this mechanism impossible in some cases.
Tracking substitutions should be a comparatively simple modification to MediaWiki. When a template gets substitued, just increment the appropriate per-template counter, which could be accessed through a magic word. If you want to get fancy, you can add a list of the substitutions performed for this edit to its page history entry.
Having such a counter would be useful when a template is up for discussion, and to help gage when protection is appropriate. So, why not make a feature request? Paradoctor (talk) 03:02, 6 April 2024 (UTC)Reply
{{subst:X}}
to increment a counter referenced to page X, you will indeed need to open a feature request upstream for that. Feel free to do so, there are lots of ideas opened that way. — xaosflux Talk 14:39, 9 April 2024 (UTC)Reply
why not make a feature request?[2] Sometimes I wonder why I bother to say anything at all. Paradoctor (talk) 15:56, 9 April 2024 (UTC)Reply
Software changes which have consensus should be filed at Phabricator.to be discussed here, what I called out is that this type of software change isn't the type that will require community consensus. It would have no impact on readers, and no direct impact on editors. — xaosflux Talk 23:53, 9 April 2024 (UTC)Reply What's the mechanism by which page saves get run through edit filters? Presumably there is something being carried out there which is capable of evaluating whether a thing's been done or not -- I don't know, maybe it's impossible to detect if template text is being expanded or not, but it seems kind of simple to me. At the very least it shoudl be possible to detect if {{subst: is being added, right? jp×g🗯️ 18:40, 11 April 2024 (UTC)Reply Well, no bigbrain comments on how this fits into the mw db schema or anything, but one issue with this does jump out to me, which is that this seems like it would fail to reflect if the template were removed later. Like, if there is some template that's getting substed 80 times a day in 2024, then we decide it's inefficient and stop using it completely in 2025, wouldn't a {{TOTALSUBSTCOUNT}} in 2026 be kind of misleading? jp×g🗯️ 18:40, 11 April 2024 (UTC)Reply
Not sure what happened here Wikipedia:Sandbox? May have been a talk about redoing layout adding tabs? Would have brought this up on its talk but iit is also a sandbox (where to talk about sandbox?).
To thw point..... Not only does it look very bad, but its an accessibility nightmare.
Tabs look horrible...2 tabs are using the strike parameter for those using the strike out usernames gadget...word "sandbox" is reapted over and over making tabs huge for no reason.
Main problem is the accessibility of the sandbox message that is a wall of text that is not clear as to what to click.start. Tabs cause whole page to have vertical scroll bar for some. Why so many sandboxes and some with odd space in naming i.e Wikipedia talk Sandbox? Why link Module:Sandbox that is template editor level protected? Looks messy and a bit overwhelming for new editors Moxy🍁 06:00, 12 April 2024 (UTC)Reply
The tabs were added in this edit to Template:Sandbox header by Awesome Aasim. – Joe (talk) 06:41, 12 April 2024 (UTC)Reply
I guess that is what WP:BRD is for.
2 tabs are using the strike parameter for those using the
probably because User:Sandbox and User_talk:Sandbox are both user pages of a blocked demonstration account. It shouldn't be like that; maybe it should only be struck out, etc. in contributions and history pages and not on content pages. Hmm.... Awesome Aasim 06:53, 12 April 2024 (UTC)Reply
Tangentially related, but I've made a request at Template talk:Page tabs#Tab background color to change the default tab colors so it meets the MOS:CONTRAST accessibility guidelines. hinnk (talk) 13:57, 16 April 2024 (UTC)Reply
Suicide hotlines
edit
strike out usernames gadget
For the proposal see User:TheSpacebook/lifeline
Firstly, is this the correct place to put this? Also, I can’t find this proposal on Perennial proposals. I have concerns about the Suicide methods article. I believe it to be a clear violation of WP:NOTHOWTO. Failing that, the article is just a WP:BADIDEA. The consensus is currently for the page to stay, so for now, possibly the suicide crisis line for the reader could be displayed at the top of the page subtly embedded into the article.
But for now, I’ve spun this up in 15 minutes and sourced the numbers from List of suicide crisis lines. This might have to be expanded, as some lines have opening and closing times, so it can be expanded to display just the emergency telephone number when the number is closed. It relies on one thing though, IP address lookup service ‘ipapi’. There are probably better in-house Wikipedia databases that can do this, for better reliability. But essentially it curls the IP address and returns the ISO 3166-1 alpha-2.
The script is ultra-simplistic as I don't know what the specific technicalities of Wikipedia are, so it's a basic HTML script. If a more advanced tool would be better, point me towards the Wikipedia dev docs for the technical specifications. Also, I can build other tools for Wikipedia by piggybacking off the pre-existing ones.
I imagine that some people who have attempted suicide will probably have the Suicide methods article in their internet history. It should work with HTML, so the quickest solution is to insert the script only on the Suicide methods page. Sort of like an WP:IAR. It will also need to be styled so it looks better on the page.
All the phone numbers should be checked for accuracy, but the raw basic script for HTML can be found here: User:TheSpacebook/Suicide crisis line script. And the full HTML page, if it needs testing, can be found here: User:TheSpacebook/Suicide crisis line script HTML page. Just copy and paste it into a text editor, save it with the extension ".html", and then open it in a web browser.
EDIT: I’ve reworked my proposal to be more subtle, it can be found here User:TheSpacebook/lifeline. TheSpacebook (talk) 23:15, 17 April 2024 (UTC)Reply
Technical issues aside, this feels a lot like WP:RIGHTGREATWRONGS to me. * Pppery * it has begun... 23:29, 17 April 2024 (UTC)Reply
For background, see Wikipedia:Village pump (proposals)/Archive 161 § Proposal to add suicidal disclaimer at Suicide and Wikipedia:Village pump (proposals)/Archive 192 § Suicides. isaacl (talk) 23:46, 17 April 2024 (UTC)Reply
there are probably better in-house Wikipedia databases that can do this
. I’m not suggesting an external service is actually used. TheSpacebook (talk) 01:26, 18 April 2024 (UTC)Reply
The user's assumed country is available using Geo.country in javascript. the wub "?!" 08:55, 18 April 2024 (UTC)Reply
Perfect. What format does that return? Would it be Geo.country_code, as the 2 letter ISO country code, or something else? Now I can take away the fetch part:
const response = await
fetch('ipapi.co/country_code');
const country = await response.text();
and have then replace this part:
const country = await fetchCountry();
with the following:
const country = Geo.country
Anyone is welcome to make amendments to User:TheSpacebook/Suicide crisis line script to make it better. Still need to check the format it returns the country in, however. Is that still not an external package/library? If not, the script now fully works in-house with Wikipedia/WMF, using no external services. TheSpacebook (talk) 11:01, 18 April 2024 (UTC)Reply
I realise that this proposal is slightly different, but the comments that I made at Wikipedia:Village pump (proposals)/Archive 161 § Proposal to add suicidal disclaimer at Suicide and Wikipedia:Village pump (proposals)/Archive 192 § Suicides still stand. Phil Bridger (talk) 11:30, 18 April 2024 (UTC)Reply
I quite plainly believe it is not within Wikipedia's mandate to have this sort of thing on an article. Buddy Gripple (talk) 12:48, 18 April 2024 (UTC)Reply
This is not displaying the US/Canadian line for everyone
, it literally is displaying the number for everyone, no? If List of suicide crisis lines was put up for AfD (which I’d oppose for it even being considered to be deleted), my theory is that it would be 'keeped', as per WP:IAR or some similar exceptional policy. TheSpacebook (talk) 14:29, 18 April 2024 (UTC)Reply
As I said before, this image is present as an example of a prevention campaign not as a "here is the number to call" listing. It's a subtle distinction and I have no objection to removing that image. --User:Khajidha (talk) (contributions) 14:59, 18 April 2024 (UTC)ReplySome suicides may be preventable by removing the means. Making common suicide methods less accessible leads to an overall reduction in the number of suicides. Some method-specific ways to do this include restricting access to pesticides, firearms, and known-used drugs. Other important measures… and calling a crisis hotline.
TheSpacebook (talk) 14:23, 18 April 2024 (UTC)Reply
I have recently noticed that @Liz has reverted my edits on blocked sockpuppet User:JayCubby for adding the {{Sockmaster}} tag on the userpage. The template page itself states that it is reserved for administrator and checkusers only, however I believe that it should be open to use for everyone in good faith who attempt to save others' time by putting this template on a blocked sock's user page to help improve the encyclopedia. I propose that the rules on that template be changed to accomodate this requirement. 2003 LN6 15:53, 18 April 2024 (UTC)Reply
Also pinging @Primefac as original blocker. 2003 LN6 15:57, 18 April 2024 (UTC)Reply
How exactly do you mean, "help improve the encyclopedia"? -- zzuuzz (talk) 16:35, 18 April 2024 (UTC)Reply
@Zzuuzz:It would save time for editors wanting to know exactly why the user was blocked and when. This way, they would not need to go into their contribs and find out themselves. 2003 LN6 18:55, 18 April 2024 (UTC)Reply
So why propose this for just sock blocks if the intention is to save time on finding why a user was blocked? Not that I want it called out on the user page for everybody, but I'm just saying, why stop there if that's the goal? Hey man im josh (talk) 21:33, 18 April 2024 (UTC)Reply
There's probably an appropriate amount of information on the talk page for that purpose. The global lock reasons also raise significant questions. These tags can sometimes be useful to help locate the correct SPI/LTA page for finding, reporting and actioning repeat customers where it's not entirely obvious (carefully balanced with WP:DENY), but for someone who just made a mistake it's overkill with little utility. Not only might it oversimplify a complex situation, it may even overcomplicate a simple situation. Whatever the case, I don't really see how the tags would really help with anything here. -- zzuuzz (talk) 23:29, 18 April 2024 (UTC)Reply
Template documentation isn't policy and while non-admins/non-clerks are informally discouraged from tagging socks, in practice most will look the other way if the tagging is reasonable. But there are various situations where we will choose not to tag in the interests of WP:DENY, discretion, or not oversimplifying a complex situation. I would not have tagged this account and I would suggest you find a more interesting thing to do on Wikipedia than applying tags to user pages. Spicy (talk) 16:54, 18 April 2024 (UTC)Reply
(edit conflict) Agreed; there are more productive things for editors to do than go around tagging blocked users' pages. Primefac (talk) 16:58, 18 April 2024 (UTC)Reply
Thank you for all of your comments. I appreciate the feedback and will conform to these guidelines in the future. 2003 LN6 19:06, 19 April 2024 (UTC)Reply
The admin, @Drmies, had also asked you to leave the tagging of socks to admins or SPI clerks, as well: Special:Diff/1218557430. – 143.208.238.41 (talk) 06:11, 19 April 2024 (UTC)Reply