User talk:Jonesey95

This talk page is automatically archived by MiszaBot III. Any sections older than 90 days will be automatically archived to User talk:Jonesey95/Archive2026.

Archives

This page has archives. Topics inactive for 90 days are automatically archived by if there are more than 20.

Request for review – Zinfandel / Kratošija proposal

Hi Jonesey95, I hope you’re doing well. Some time ago, you kindly helped me restore a draft that had been prematurely removed — and I truly appreciated your fair and balanced approach back then. I’d like now, if I may, ask for your brief review my new proposal, before posting, on the Talk:Zinfandel page, related to the structure and sourcing balance concerning Kratošija (the Montenegrin grape variety genetically identical to Zinfandel / Primitivo / Tribidrag). For context, the original Kratošija page was redirected to Zinfandel on October 12, unilaterally, without prior discussion, following a POV fork claim raised by another editor,(she redirected it). Although editor Liz initially reverted the redirect, and advised that a discussion should be opened, the page was later left redirected without a proper consensus. The redirect, therefore, remains in place, grounded only in that earlier POV fork assertion, rather than in an established community agreement. I contacted ANI, and they redirected me to the Talk:Zinfandel page for discussion.

My intention, for now, is not to reopen that past issue. I uderstood that this subject is not very familiar to many independent editors, who have no regional bias, so my current goal is simply to introduce these important scientific findings and the confirmation of historical heritage, by improving the existing article Zinfndel, in a balanced and verifiable way. I’d be very grateful if you could take a quick look at the text, before I publish it on Talk:Zinfandel, just to ensure that it’s neutrally written and consistent with Wikipedia’s standards. Truly appreciate ,again, for your time and for all the work you do across Wikipedia.

The text is:

Questions about request the template automatic substitution

I would like to request the automatic substitution for some road templates, for example {{BAB-A}} and {{MES-E}}, what things I need to do to request the automatic substitution by bot such as {{MES-E(2)}} and {{JKR(2)}}?

Thank you. DiaoBaoHuaJian (talk) 17:01, 8 January 2026 (UTC)[reply]

There needs to be a discussion that determines that these templates should be substituted. Templates generally are not substituted, so that changes can be made to the template instead of making the same change to many templates. – Jonesey95 (talk) 17:23, 8 January 2026 (UTC)[reply]

That template

Is that the one I edited some time ago? This fool seems to forget. [Now casting around for ways of remembering.] Tony (talk) 01:30, 10 January 2026 (UTC)[reply]

I forget things too. That's why I put hidden comments into the wikitext to remind you and others that the links were there deliberately. Also, please use edit summaries; edits that remove stuff from working templates and have no edit summaries look like vandalism. – Jonesey95 (talk) 01:45, 10 January 2026 (UTC)[reply]

Template documentation

Hello, what guideline were you referring to saying that templates must have documentation? I've never heard that. Thanks. — Hex • talk 13:21, 13 January 2026 (UTC)[reply]

Wikipedia:Template namespace#Guidelines. Templates should be clearly documented as to their usage and scope. – Jonesey95 (talk) 15:42, 13 January 2026 (UTC)[reply]

Okay, I asked you about "must" and you quoted a "should". — Hex • talk 17:43, 16 January 2026 (UTC)[reply]

Removing documentation from a template, or not providing it at all, is user-unfriendly. I prefer to help my fellow editors when it is reasonable to do so. See RFC 2119 for a good explanation of what "should" means in a technical documentation context. (For talk page stalkers, this is the relevant set of edits.) – Jonesey95 (talk) 17:57, 16 January 2026 (UTC)[reply]

Asking for help on Talk:Zinfandel

Hello Jonesey,

I thought I wouldn’t bother you anymore, but I truly need your help. I’m still trying to handle the Zinfandel discussion the right way as a newer editor, and I’m worried I’m missing the best process step.

Seven days ago, I posted my latest reply to DalidaEditor on Talk:Zinfandel . I explained that I want every proposed change to be discussed on the talk page and agreed by consensus, before it’s added to the main article, to avoid back-and-forth reverts, so I’m waiting for a response to my new proposals. But, as usual, I’m being ignored. Then, after that “silence,” when, for example, I make minor edits to the text, I get accused of “violating” some WP policies.

The thread is unfortunately quite long (with multiple collapsible sections), rather extensive, and may not be very well structured, and I don’t want to overwhelm anyone or choose the wrong venue. If you have the time, I’d appreciate it if you could take a look at what has been happening on that page and, if possible, keep an eye on it going forward, as I’m concerned about how the discussion is developing. Could you also, please, tell me what you’d recommend as the next step: a Third Opinion, an RfC, or something else?

I’d really value your guidance, and I must thank you for your help in my previous messages. You’re one of the few people who hasn’t ignored my attempts to keep this policy-based and calm, all in the name of improving the article.

Thank you, VitisArchivum (talk) 12:26, 16 January 2026 (UTC)[reply]

I browsed through that long talk page and looked at the article. It appears that you want to add some sourced material to the History section, but after all of that discussion, it is not clear to me what you want the section to look like when you are done. I might put a proposed version of the History section on the talk page, or in my sandbox, and then ask for feedback. Posting a request for feedback at Wikipedia talk:WikiProject Food and drink/Wines task force might also help. Keep your requests concise. – Jonesey95 (talk) 13:32, 16 January 2026 (UTC)[reply]

Thank you for taking the time to look through everything. It really means a lot to me.I understand your point. I’m currently preparing a draft of the History section, and I’ll send it as soon as possible. Thanks again, I truly appreciate your understanding and help. VitisArchivum (talk) 12:56, 21 January 2026 (UTC)[reply]

Regexes

Hi Jonesey95. I've ran Task 6 a bit today and ran into a persistent issue I don't know how to tackle. Currently the code uses two different sets of regexes to handle two tag misnests and three tag misnests respectively. The problem is that I'm not sure on how to prevent the two tag regexes from trying to handle three tag misnests which ends up like this and essentially feeds the three tag regexes bad input. Any ideas on how I could fix this? — Tenshi! (Talk page) 15:30, 18 January 2026 (UTC)[reply]

Managed to fix this eventually. You might want to hold off on fixing template-arg-in-extension-tag lint errors that aren't being caused by extension tags, see gerrit:c/mediawiki/services/parsoid/+/1229617 which isn't deployed yet. Tenshi! (Talk page) 17:47, 22 January 2026 (UTC)[reply]

Thanks for the note. I looked at your message a couple of times and did not find an answer, and then I forgot to respond.

As for the Linter tag parameter errors, I can't make heads or tails of the code, but I wonder why they would disable the error in Template space. I'm pretty sure that all of the ones that I fixed were being caused by extension tags, but I could definitely be wrong. – Jonesey95 (talk) 18:00, 22 January 2026 (UTC)[reply]

Stopgap measure, probably. I don't think they have a fix for it currently (even though its probably something simple in theory like ignore any lint errors pointing to an unescaped template param). Tenshi! (Talk page) 18:11, 22 January 2026 (UTC)[reply]

I think I see. I think they are saying that this change was not needed, since the parameter name with three braces around it that would show in the absence of a parameter value is not actually template code to be interpreted once it is transcluded. The braces and the parameter name are displayed in plain text and should not cause any Linter problems. The lack of a required parameter value in those templates is obviously a problem, but it should be captured with an error message or category within the template code, not with Linter, which should not care. – Jonesey95 (talk) 18:17, 22 January 2026 (UTC)[reply]

Tech News: 2026-04

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

The Global Watchlist lets you view your watchlists from multiple wikis on one page. The extension continues to improve — it now automatically determines the text direction (ensuring correct display of sites with unusual domain names) and shows detailed descriptions for log actions. Later this week, a new permanent link for page creations and CSS classes for each entry element will be added. [1][2][3][4]

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 20:27, 19 January 2026 (UTC)[reply]

[trimmed by Jonesey95]

January 2026

Hi, I saw that u have move page for:

Also removed the Italic title font.

Nagercoil–Mangaluru Amrit Bharat Express

To know ur best is, all Amrit Bharat Express train services which is now present 24 are dash & Italic title. So this these 3 articles which u moved dash little front and removed Italic be same as all articles how is it.

Thank u. DAR.45m (talk) 05:22, 22 January 2026 (UTC)[reply]

See MOS:ENBETWEEN for an explanation. When connecting two destinations, we use an en dash (–), not a hyphen (-). And when one or more of the destinations has a space in the name, like "Thiruvananthapuram North", we put spaces around the en dash. So: "Charlapalli – Thiruvananthapuram North" is correct, not "Charlapalli–Thiruvananthapuram North" or "Charlapalli-Thiruvananthapuram North". Also, "Nagercoil–Mangaluru" is correct, because each destination is only one word. I hope that makes sense.

And we do not use italics for the names of train lines or routes. See MOS:NAMESANDTITLES. – Jonesey95 (talk) 05:34, 22 January 2026 (UTC)[reply]

No brother, in every premium service Train there will be dash (–) like ' Charlapalli–Thiruvananthapuram North ' because in Wikipedia there are lot of many articles which is (–), If u don't trust me

See this..

Like this, there are 1000 of many articles.

I'm not mentioning MOS:NAMESANDTITLES & MOS:ENBETWEEN. I'm truly talking about the articles of Indian Railways to trains be (–) not (-) or giving a gap. Becuase, it looks odd. DAR.45m (talk) 05:46, 22 January 2026 (UTC)[reply]

Please do not assume my gender.

All of the articles that you linked to needed to be moved to names that conform to MOS:ENBETWEEN. None of them should have italics in their titles. If there are 1,000 such articles, then 1,000 articles need to be moved. It is not uncommon to find sets of articles like this that all have incorrect formatting. – Jonesey95 (talk) 06:02, 22 January 2026 (UTC)[reply]

thank you

your probably the first person so i just want to say my thank you :) Nerd-in-history (talk) 20:31, 26 January 2026 (UTC)[reply]

You're welcome. – Jonesey95 (talk) 22:39, 26 January 2026 (UTC)[reply]

Lint errors

Hello, Jonesey!

Some months ago you helped me fix some lint errors on my homewiki (sqwiki). During this time I've tried fixing what I can, starting from the ones with the highest priority and going down in the hierarchy. Currently there are only 2 pages left on the high priority for us (excluding Duplicate IDs). Would you mind helping me clean up those 2? I also tried cleaning up the medium priority ones but couldn't get the number down more than what it is currently. Are there any tools or techniques you use beside sheer experience? Maybe you can give me some suggestions. - Klein Muçi (talk) 10:22, 28 January 2026 (UTC)[reply]

Sheer experience (I have been fixing Linter errors for seven years!) is helpful. The Help pages on the MediaWiki site (click "Ndihma" on any Linter page) sometimes contain useful examples; I wrote or expanded some of those pages myself. Take a look at my Contributions on sqwiki to see the kinds of fixes I have made. Let me know if you have questions about specific fixes.

I have fixed the high-priority errors and a couple of easy medium errors. Look at my Contributions to see two techniques for fixing misnested inline tags. You have made excellent progress! – Jonesey95 (talk) 15:21, 28 January 2026 (UTC)[reply]

Thank you very much! How are you able to locate the area where the error is most likely to be though? For example, how were you able to fix the errors with sq:Familja Mediçi?

In sq:Speciale:LintErrors/wikilink-in-extlink, two pages appear to have a lot of errors: Wikipedia:Kuvendi/Arkivi 6 and Arti i rilindjes. Both are very, very long, the later being one of the longest articles on SqWiki. How would I go about locating the errors in them? I want to understand the underlying mechanics of your work, maybe they can help me speed up the process somehow. - Klein Muçi (talk) 01:12, 29 January 2026 (UTC)[reply]

One way is to go to "Page information" ("Informacioni i faqes"), scroll to the bottom, and click "View detailed information on the lint errors." Next to the error that you want to fix, click "edit". That will take you to an editing view, with the relevant section highlighted. Sometimes, if the error occurs in a big template or long passage starting and ending with a div tag, it can be difficult to find the error. In that case, copy and paste the highlighted section to https://sq.wikipedia.org/wiki/Speciale:ExpandTemplates and click OK, then click your yellow LintHint button to highlight the small section where the error can be found. If you do not have the LintHint script installed, you should. See https://sq.wikipedia.org/wiki/P%C3%ABrdoruesi:Jonesey95/common.js for the code to put in your own common.js file to make LintHint work. – Jonesey95 (talk) 02:08, 29 January 2026 (UTC)[reply]

Tried that method here but the whole page got opened for edit. :/ - Klein Muçi (talk) 02:31, 29 January 2026 (UTC)[reply]

I saw that as well on another page. On one page, I was able to scroll down and find the highlighted section, but on another, I did not see a highlighted section. I don't know why. The LintHint extension still works; press the down-arrow to jump to a highlighted section where the error lives. – Jonesey95 (talk) 02:33, 29 January 2026 (UTC)[reply]

Thank you! That is true. It had been a while without using LintHint. I'll try to finish the medium priority ones utilizing it. Thank you one more time! :) - Klein Muçi (talk) 03:00, 29 January 2026 (UTC)[reply]

Through the use of LintHint, I’ve been able to resolve nearly all medium-priority issues. There are only a few remaining, but they’re proving a bit too complex for me to tackle on my own.

When you have some time, would you mind taking a look so I can clear out that category as well and focus solely on the low-priority ones going forward?

I've also noticed that new issues are now introduced very rarely, as VE has become the standard editing tool. When they do appear, they’re usually limited to bogus file options. - Klein Muçi (talk) 12:47, 30 January 2026 (UTC)[reply]

All fixed except for one. See this talk page request, which I think will fix the problem. – Jonesey95 (talk) 14:46, 30 January 2026 (UTC)[reply]

Indeed. I wasn't expecting for you to act this fast, thank you very much! Do you think there is any way possible to bot-handle some of the low priority ones? Or whatever automatic process that can speed up the time. I mean, I know there aren't that many errors to fix, relatively speaking. In ~20 years no one had worked with those and in 1-2 years, high and medium priority ones were zeroed by 2-3 people only. In that sense, it's definitely doable to fix ~5000 more. But if there was any way to cut down those numbers with a sort of automatization it would turn the process in something that actually can be worked actively with a fixed deadline. You are more knowledgeable than me in this matter and thought I'd ask. - Klein Muçi (talk) 16:46, 30 January 2026 (UTC)[reply]

At this point, going through page by page should be fine. If you can fix 50 errors per day, you'll be done in 100 days. At first, you will be able to fix many more than 50 per day, because some pages have 20+ missing end tags or 20+ <tt>...</tt> tags that you can fix with one edit. I like to start by limiting the list to pages with templates, which does two things: it sometimes finds problems that can be fixed in many pages by fixing the template, and other times, it highlights problems that are the same in many pages. The latter situation requires manual editing, but it is easier to fix 50 of the same problem than 50 different problems. I fixed a few templates just now, which should reduce the overall error count by a few hundred. – Jonesey95 (talk) 17:28, 30 January 2026 (UTC)[reply]

Yes, it did. Thank you! I'll start by filtering by templates themselves, maybe that creates a meaningful change. - Klein Muçi (talk) 01:09, 31 January 2026 (UTC)[reply]

I left you a note on your talk page at sq.WP. There are at least a thousand very easy fixes left. Do a few each day, and you'll be close to zero soon. Drop me a note when you get stuck. – Jonesey95 (talk) 01:38, 31 January 2026 (UTC)[reply]

Yes, I saw it. I've put a reply there. I just finished dealing with some of the templates and the number dropped around 4K. Now I'll start dealing with the list you provided. - Klein Muçi (talk) 02:19, 31 January 2026 (UTC)[reply]

Hello, Jonesey! I've continued working with the linter errors and yet again my progress has come to an halt on w:sq:Speciale:LintErrors/stripped-tag (which I was trying to get down to 0). There are some cases which are proving to be too complex for me to handle, can you give me a hand when you have some free time? One specific situation is related to the template w:sq:Template:WPBannerMeta which is rather old and should be deleted (along with its subpages). The only problem is that I'm having a hard time devising a plan on how to switch all its use cases to using the better Lua way. - Klein Muçi (talk) 00:18, 23 February 2026 (UTC)[reply]

Here are some useful diffs: 1; 2; diff. For others, look at my contributions for today. Let me know if you have any questions or if I broke any pages. – Jonesey95 (talk) 01:57, 23 February 2026 (UTC)[reply]

It is unclear to me why you deleted "Stampa:Column-width". It is used in 2,000 pages (through Stampa:Reflist, primarily). That deletion might cause problems. If you want it to stay deleted, you may need to edit three templates to remove references to the template.

I have fixed nearly all of the stripped tags. Some of them are not worth worrying about if they are not causing problems in other pages. Some of them are protected, so I can't edit them. I recommend working on the missing end tags until you get stuck. – Jonesey95 (talk) 02:23, 23 February 2026 (UTC)[reply]

Thank you very much! You were faster than I expected. I deleted that template along some other similar ones because we tend to preserve parity with EnWiki when it comes to the technical infrastructure to make updates easier. You had deleted that template here a long time ago so I followed along and did the same but since currently I was focused on fixing the linter errors, I left the transclusion issues for another time. Hadn't realized it was being used over 50 pages though, that's usually the limit where I won't take such actions. Now I updated our reflist template to match the one here along what you showed me in that search. Some of the pages had some code that caused a strange editor issue that messed up the cursor placement for me and that's why I didn't know how to handle them. Not sure if I'm describing it properly to you.

I'm thinking to continue with obsolete HTML tags before finally pushing through the missing end tags one. Seeing them reach 0 provides a bit of psychological support. - Klein Muçi (talk) 03:04, 23 February 2026 (UTC)[reply]

Hello!

I've managed to clear every category except Missing end tag and posted a brief update at VP summarizing the progress. I mentioned you there for all the help and guidance yo've given us — I hope that's alright.

Before I dive fully into the last batch, I wanted to ask if you have any tips or tricks in mind. With the previous categories, there were often shortcuts (template fixes, pattern-based cleanups, etc.), but here it feels much more granular and page-by-page. I'm wondering if there's still something structural I might be overlooking.

In any case, thank you again — your advice has genuinely accelerated the whole effort. - Klein Muçi (talk) 08:31, 27 February 2026 (UTC)[reply]

Happy to help. I looked through the missing end tags, and I do not see any obvious patterns. I recommend using the "Filter by tag name" and "Filter by template state" menus to make it easier to find patterns that are similar to each other. I did notice a lot of articles using mismatched "col" templates like "col-begin" with "columns-end" instead of "col-end". The documentation for those templates is typically missing, but there are confusing differences between templates that seem like they should be the same. – Jonesey95 (talk) 11:33, 27 February 2026 (UTC)[reply]

Follow-up to “Asking for help on Talk:Zinfandel

Hello Jonenesy95,

I’ve placed my proposed draft in my sandbox, so it’s easier to review visually:User:VitisArchivum/Zinfandel draft

If you have time, I’d really appreciate it if you could follow up on what you suggested earlier. Thank you very much. If I’ve made any mistakes, technical or otherwise, please correct them. This is part of the edit I have in mind, but I don’t want it to be too much.For example, I believe that per WP:NPOV it would be appropriate to add Montenegro next to the one-sided, “Croatia only” display in the “Origin” section of the infobox. But for now, I’ve left it as it is. Of course, if even this is too much for a first proposal, please feel free to tell me, and I can expand further later. VitisArchivum (talk) 14:47, 29 January 2026 (UTC)[reply]

The scope of that request looks reasonable. I have copy-edited the text. The only big problem I see is the significant unsourced claim about "longer than anywhere else". That will cause editors to reject the whole text, whether that rejection is reasonable or not. Either source it or remove it. – Jonesey95 (talk) 17:34, 29 January 2026 (UTC)[reply]

Dear Jonesey95,

Thank you very much for your reply

I completely agree with you. In fact, I am the one who requested and I originally added the {{citation needed}} tag, because the statement “ longer than anywhere else” is clearly WP:NOR and WP:TE and is not part of my proposal .It is a legacy statement from the existing text, and I originally added a {{citation needed}} tag to that exact phrase because it appeared unsourced. I wanted to remove it, but whatever I do in that section, or in article in general, I am being accused. That is why I sent it to you, so you could take a look.

In the draft I previously shared, my proposed edits were mixed with the current version of the History section, which understandably made it unclear what was mine and what was already present. My actual additions are limited to the reference to the Statute of Budva, the mention of the town of Bar in the final paragraph, and some adjustments in the infobox (regions and synonyms).

But, the {{citation needed}} tag I requested was recently removed under a WP:TE rationale, by [[User:DalidaEditor]]. ." I do not understand how requesting scholarly sources for verification can constitute WP:TE, as the burden of proof lies with those who want to include the statement?

For clarity, I am planning to restore the tag as follows:

^{[citation needed]}

I would really appreciate your advice on the best next step regarding the proposed edits: whether you would prefer to place them in your sandbox, discuss them on Talk:Zinfandel, or proceed in another way you consider suitable. What would be next step? I do not want to make wrong steps.

Thank you again for your understanding, time and guidance. VitisArchivum (talk) 12:16, 30 January 2026 (UTC)[reply]

I think the next step is to propose your changes on the article's talk page. – Jonesey95 (talk) 14:19, 30 January 2026 (UTC)[reply]

Dear Jonesey95,

Thank you very much for your suggestions. I followed your advice and posted my proposed changes on the Talk:Zinfandel page, as you suggested. Since you are familiar with my situation, any comments there, on the Talk:Zinfandel page, would be greatly appreciated, because your neutral, experienced perspective and input are very helpful and important to me. If your time allows, I would also be grateful if you could follow the situation there and on the main article as well.

Thanks again. All the best. VitisArchivum (talk) 14:08, 5 February 2026 (UTC)</nowiki> VitisArchivum (talk) 14:03, 5 February 2026 (UTC)[reply]

Listing for discussion of Template:30 most populous cities of Denmark

Template:30 most populous cities of Denmark has been listed for discussion, which may result in the template being merged or deleted by consensus. You are invited to comment on the proposed action at the entry on the Templates for discussion page. Logoshimpo (talk) 23:05, 29 January 2026 (UTC)[reply]

Australian cricket team in England and North America in 1878

I can see from your talk page that you are always right, but you may wish to consider that there is an onus on you to correct unintentional errors when you spot them, without making a song-and-dance about it. Everybody makes mistakes, including (perhaps, especially) yourself. Kindly stop trying to make yourself seem like some kind of perfect editor. Otherwise, people might start thinking you are some kind of.......whatever. Jack (talk) 01:49, 1 February 2026 (UTC)[reply]

I do make mistakes. When I am alerted to my mistakes, I work to fix them rather than reverting to the version of the page with big red mistakes in it. Based on your uninformative edit summary of "high", I had no way to know whether the edit you made to Talk:Australian cricket team in England and North America in 1878 was vandalism or a good-faith edit. Please use Preview when you edit.

And this reverting edit, with its misleading edit summary, is purely disruptive. Please see MOS:ITALICS, MOS:BLOCKQUOTE, MOS:DATERANGE, and MOS:INDENT, for starters. I am happy to help you learn better editing practices if you are open to that. – Jonesey95 (talk) 05:43, 1 February 2026 (UTC)[reply]

And I love that what you concluded from my talk page is that I am always right. Here are a few direct quotes from me, in my posts and responses above:

I could be wrong, though.
I could definitely be wrong.
I think this might be a false positive, if I am remembering correctly.
I forget things too.
Editors are responsible for their own edits.

The last one is for you, if you are open to owning it. I do. – Jonesey95 (talk) 05:59, 1 February 2026 (UTC)[reply]

Bairds12

I've written the expansion as it was on one of my suggestions. Lua is fun! (I'm a programmer/DBA for a living). Could you take a look at Template:Bairds12 and give me any suggestions, while the main contributers to the Wikiproject like it, your suggestions will be more technical.Naraht (talk) 15:42, 3 February 2026 (UTC)[reply]

Empty headers

Just an FYI, all of the remaining Empty headers need an unsigned added. I'd skipped these on first run due to the extra step. Zinnober9 (talk) 22:35, 3 February 2026 (UTC)[reply]

Do you mean {{unsigned}}? Typically the sections with empty headings are so ancient and messy that adding an unsigned template is not worth the effort, IMO. The pages typically don't have enough sections on them to worry about archiving or other fancy activity. – Jonesey95 (talk) 22:37, 3 February 2026 (UTC)[reply]

Yes. It's typically been the first IP editor, so hasn't been too hard to find most of the time. Zinnober9 (talk) 22:42, 3 February 2026 (UTC)[reply]

January 2026 GOCE drive award

		The Minor Barnstar
This barnstar is awarded to Jonesey95 for copy edits totaling between 1 and 3,999 words (including bonus and rollover words) during the GOCE January 2026 Backlog Elimination Drive. Congratulations, and thank you for your contributions! Dhtwiki (talk) 04:34, 4 February 2026 (UTC)[reply]

Reminder

Sorry, I forgot to ping you in my reply from two days ago on Wikipedia:Templates for discussion/Log/2026 February 2#Template:PKP colour. Thanks,

Fortek67 (talk) 16:45, 5 February 2026 (UTC)[reply]

Thank you

Thank you for help editing my user page!

Feather&Martin (talk) 00:32, 7 February 2026 (UTC)[reply]

You're welcome. Let me know if you have any questions about editing. – Jonesey95 (talk) 02:43, 8 February 2026 (UTC)[reply]

Adding Math to the Bairds templates

See Template:Bairds10, I've added a calculation as far as I can tell, so that if the user inserts the page, but not the url-page, the value for the url will be calculated from the page. May need a type checker to be stronger. Opinions?Naraht (talk) 03:15, 9 February 2026 (UTC)[reply]

Bot list?

What would be involved in creating a user subpage, bot updated, list like your User:Jonesey95/Linter tags in AFDs, but for Simple Wikipedia's protected pages? Essentially Wikipedia:Linter/reports/Protected pages by Lint Errors but for the pages at Simple and in my userspace rather than project space. And how easy would it be to later decide to include or exclude obsolete tags in the list, or would it just be better to make two lists, one with, one without? I believe I'd need to host the page here on enwiki since SDZeroBot is not editing on Simple (which is fine). Thanks, Zinnober9 (talk) 12:51, 9 February 2026 (UTC)[reply]

I copied over some of the pages to simple, in your User space, but it looks like the sdzerobot toolforge functions may be hard-coded to look at en.WP. You could ask at Template talk:Database report. One question you could ask there is "Can I host a page here on en.WP but have it query the simple.Wikipedia database instead of the en.Wikipedia database?" If the answer to that is yes, I should be able to help you with everything else. – Jonesey95 (talk) 15:38, 9 February 2026 (UTC)[reply]

Posted, thank you. We'll see what the answer is. I've mostly carved off a lot of the unprotected pages for the errors over there other than missing, obsolete and misnested, (tidy and stripped still have a little bit to go) but wasn't sure the protected quantity in these large sets and was hoping to get some sort of read on this before making an edit access request. Zinnober9 (talk) 18:12, 9 February 2026 (UTC)[reply]

SD0001 confirmed your suspicion that sdzerobot is only querying the enwiki database. I don't see any approved bot on Simplewiki doing any database query type tasks, so I'll resort to a manually created spreadsheet (probably omitting font tags to make it more manageable) and use that. Thank you for your efforts on this. Zinnober9 (talk) 02:11, 19 February 2026 (UTC)[reply]

Yes, I saw that. Too bad. – Jonesey95 (talk) 02:20, 19 February 2026 (UTC)[reply]

Tech News: 2026-07

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

Logged-in contributors who manage large or complex watchlists can now organise and filter watched pages in ways that improve their workflows with the new Watchlist labels feature. By adding custom labels (for example: pages you created, pages being monitored for vandalism, or discussion pages) users can more quickly identify what needs attention, reduce cognitive load, and respond more efficiently. This improves watchlist usability, especially for highly active editors.

[trimmed]

The Global Watchlist lets you view your watchlists from multiple wikis on one page. The extension continues to improve — it now properly supports more than one Wikibase site, for example both Wikidata and testwikidata. In addition, issues regarding text direction have been fixed for users who prefer Wikidata or other Wikibase sites in right-to-left (RTL) languages. [5][6]
The automatic "magic links" for ISBN, RFC, and PMID numbers have been deprecated in wikitext since 2021 due to inflexibility and difficulties with localization. Several wikis have successfully replaced RFC and PMID magic links with equivalent external links, but a template was often required to replace the functionality of the ISBN magic link. There is now a new built-in parser function {{#isbn}} available to replace the basic functionality of the ISBN magic link. This makes it easier for wikis who wish to migrate off of the deprecated magic link functionality to do so. [7]

[trimmed by Jonesey95]

MediaWiki message delivery 23:28, 9 February 2026 (UTC)[reply]

Question

Where is the TPER you mention in this edit summary? I no can find.... Zackmann (^{Talk to me}/_{What I been doing}) 03:34, 10 February 2026 (UTC)[reply]

"Find" on the template talk page sometimes works, including in this case (late-night sassiness, no charge). – Jonesey95 (talk) 06:19, 10 February 2026 (UTC)[reply]

Ok in my defense I searched for defending_champions, with the underscore, and got nothing... But should have tried without it. Appreciate the sassiness though! With that, bed time for me! Zackmann (^{Talk to me}/_{What I been doing}) 06:39, 10 February 2026 (UTC)[reply]

February 2026 meetup in Portland

Hey Jonesey95,

You're invited to the February 2026 meetup in Portland, Oregon! Join us at the Northwest Library at 2:00 PM on Saturday, February 28.

Please RSVP at the link above, even if you might be interested, so we can know how many people to expect. Hope to see you there!

(To unsubscribe from these updates, remove yourself from this list.) Sent via MediaWiki message delivery (talk) —TechnoSquirrel69 (sigh) 05:34, 14 February 2026 (UTC)[reply]

Template update request

Hi. In Template talk:Infobox India university ranking#Request to add parameters, you commented me to update in the sandbox and show at the testcases page. I did the same and informed you. Since it is around 8 days without any reply, I am informing you here. I hope you will do the required. AnkurPl 10:50, 14 February 2026 (UTC)[reply]

Listing for discussion of Template:NBA arena statues

Template:NBA arena statues has been listed for discussion, which may result in the template being merged or deleted by consensus. You are invited to comment on the proposed action at the entry on the Templates for discussion page. SportsGuy789 (talk) 22:38, 17 February 2026 (UTC)[reply]

BERSADAP Mantap

BERSADAP Mantap! - Mangkuk Ming ~2026-11292-19 (talk) 05:02, 20 February 2026 (UTC)[reply]

And to you as well. – Jonesey95 (talk) 05:03, 20 February 2026 (UTC)[reply]

We had PASDAP, BERSADAP, PEJUADAP, WARIDAP, PANDAP, why not UMDAP? ~2026-15240-19 (talk) 08:32, 10 March 2026 (UTC)[reply]

One DAPig detected: N niyaz ~2026-19460-75 (talk) 19:49, 28 March 2026 (UTC)[reply]

Zayin N: giPAD Eno. – Jonesey95 (talk) 20:14, 28 March 2026 (UTC)[reply]

Why so antagonistic?

To quote a recent edit summary on Template:User Profane that you left, “Add a damn category to get this into a sorting category instead of being completely uncategorized, per Wikipedia:Categorization#Categorizing pages”. Why would you be so rude when you could have instead been polite? Coolgurl5555 🩷 (talk)(sign) 02:41, 23 February 2026 (UTC)[reply]

Because This user swears too much!!! I was just trying to read the room and set the tone of my edit summary accordingly. If we can't have fun in our edit summaries, where can we have fun? Happy editing! (P.S. I'll be happy to put a quarter in your swear jar for my edit summary. Let me know where it lives.)– Jonesey95 (talk) 02:46, 23 February 2026 (UTC)[reply]

Oh I’m fucking stupid I’m so so sorry. Coolgurl5555 🩷 (talk)(sign) 02:47, 23 February 2026 (UTC)[reply]

I wasn't sure if you came here to continue the joke or were legitimately missing the bit. Either way, I hope we brightened the mood of a few of my talk page stalkers. Conveying tone in pure written words has always been a challenge. – Jonesey95 (talk) 02:49, 23 February 2026 (UTC)[reply]

February 2026 GOCE blitz award

		The Modest Barnstar
This barnstar is awarded to Jonesey95 for copy edits totaling over 2,000 words (including rollover words) during the GOCE February 2026 Copy Editing Blitz. Congratulations, and thank you for your contributions! GoldRomean (talk) 00:40, 24 February 2026 (UTC)[reply]

Old signature discussion

Can you find the old signature discussion that resulted in blocking lint errors from new signatures? I couldn't find it while searching the VP archives. Gonnym (talk) 06:59, 24 February 2026 (UTC)[reply]

Are you looking for this MW page? The change was announced in Tech News in July 2020 and implemented a week or two later. There may have been VPT discussions here around that time. – Jonesey95 (talk) 15:20, 24 February 2026 (UTC)[reply]

No. I'm pretty sure we had a discussion, probably an RfC, that disallowed signatures with lint errors. Gonnym (talk) 18:19, 24 February 2026 (UTC)[reply]

I don't remember. I don't think that technical decision was subject to an RFC. I see this July 2020 VPT thread with no real dissent. If you do a find on "signature" on that archive page, you will see a few other threads. There is one note about not erroring on font tags; maybe there was an RFC about that issue later.

(After much searching ...) I found this 2023 RFC about obsolete tags in signatures. That thread links to a discussion from the previous month. – Jonesey95 (talk) 19:04, 24 February 2026 (UTC)[reply]

Yeah it was the 2023 one. I found it also while going through the MW link you linked. Gonnym (talk) 19:42, 24 February 2026 (UTC)[reply]

Ah, that is a different RfC. I meant Wikipedia:Village_pump_(proposals)/Archive_210#RfC:_applying_signature_validation_retroactively. Gonnym (talk) 19:43, 24 February 2026 (UTC)[reply]

Hmm, that one has never been implemented. It might be time to use a different means to go through the report and reset those editors' signatures to the default, if that is possible. – Jonesey95 (talk) 21:11, 24 February 2026 (UTC)[reply]

User:HouseBlaster, is that correct? Gonnym (talk) 07:37, 25 February 2026 (UTC)[reply]

I'll let HB respond, but the bug has not been acted upon AFAICT, and the link above is to a list of editors with invalid signatures who have posted to talk pages in the last 90 days. – Jonesey95 (talk) 15:14, 25 February 2026 (UTC)[reply]

It was implemented (phab:T355462). Editors who try to sign with an invalid signature get their signature automatically converted to the default signature, but their signature is not changed in their preferences. I added a <font>...</font> tag to my signature, and you can see that it's been signed with the default one instead.

There are three asterisks in the above. The dark mode linter error is not checked by the software (phab:T360796). The Toolforge tool is not 1:1 with what MediaWiki checks for (for example, sig-too-long-post-subst is against WP:SIGLEN but not enforced by the software; invalid signatures are still reported even if the software automatically fixes them). And finally, editors can still manually sign their messages and add all the lint errors they wish. Best, HouseBlaster (talk) 15:50, 25 February 2026 (UTC)[reply]

That is some fascinating magic. I can see it in action at this diff, where User:Aareakinbo's signature, "Akinbo A. A. Cornerstone", was apparently automagically replaced with a default signature. Fascinating. As for the background-color linter error, I can't tell whether we can control that error locally using $SignatureAllowedLintErrors. If there is a way to see the value of that setting locally, I don't have a link to it. – Jonesey95 (talk) 15:58, 25 February 2026 (UTC)[reply]

With this commit they've excluded hidden errors from SignatureValidator. So if the color error is set to hidden, it will be ignored. Gonnym (talk) 16:04, 25 February 2026 (UTC)[reply]

We do control it locally; it is at InitialiseSettings.php—search for wgSignatureAllowedLintErrors. It is currently set to just night-mode-unaware-background-color. That lint error is not hidden; if it were, it wouldn't show up at Special:LintErrors. Best, House Blaster (talk • he/they) 16:07, 25 February 2026 (UTC)[reply]

Thanks for that useful link. I have saved it on my reference sheet of things that I like to look up but have trouble finding. That limitation should probably be removed. It can, but does not always, cause problems in dark mode, and proliferation of the errors means more work for the humans and bots who will eventually want to clean them up. – Jonesey95 (talk) 16:12, 25 February 2026 (UTC)[reply]

Template:Glrefresh

I'll add a description shortly. I was busy when I made it yesterday.

Note that if you had checked the 'what links here' and then searched for 'refresh' on the one page it is used on, especially if you had gone on to similar pages (including the teahouse and various other graphics lab workshops) and doubly especially if you had noted the large number of times people have given bad advice on how to do so (I've seen editors advised to use Ctrl+F4 and Shift+F5 many, many times) you would probably understand why I created it as a template. You may even understand the name. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 19:41, 25 February 2026 (UTC)[reply]

I always check "What links here". I saw that it was used on just one page, and I saw that the template has no parameters. All of that is unusual for a template. Thanks in advance for adding the required documentation and at least one category. As for the name, if it is to be used at the Teahouse and other pages that are not the Graphics Lab, it might benefit from a better name. It's easier to get the name right before the template becomes popular. – Jonesey95 (talk) 20:13, 25 February 2026 (UTC)[reply]

I'm not opposed to renaming it. I literally created it while I was mid-comment, because I realized I'd gotten sick of typing it out a hundred times, and it would be trivial to just make a template., and the name was the first thing that popped into my head (something I would name a variable in code, albeit with camel case capitalization). I forgot that WP automatically capitalizes the first letter, so what I actually typed was glrefresh, which is a bit easier to read than Glrefresh I think.

What would you think of something like Template:CtrlF5? ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 14:39, 26 February 2026 (UTC)[reply]

I added the documentation. Following on from several other templates I looked at which lack parameters, I excluded the TemplateData section as "params" is a required parameter, and there was no way (of which I am aware) to format it to simply say there are no parameters without it looking quite hokey. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 15:02, 26 February 2026 (UTC)[reply]

I think that name, and the template, are Windows-centric. What should people do on mobile phones, Mac OS devices, or other interfaces? – Jonesey95 (talk) 15:07, 26 February 2026 (UTC)[reply]

That's a good point. The majority of editors over the course of my tenure here have used Windows, so I simply ran with that (a consequence of doing it last-minute).

Perhaps I should make the contents a wikilink to a page giving instructions for different platforms... I think I'll do that and update it. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 14:49, 27 February 2026 (UTC)[reply]

Have you considered just using the existing {{Purge}}, as in (If you don't see the changes, refresh this page to update it.)? – Jonesey95 (talk) 15:48, 27 February 2026 (UTC)[reply]

That will only work on the page it is used on, not on image pages (here or on commons) or when viewing an image directly. ᛗᛁᛟᛚᚾᛁᚱPants Tell me all about it. 16:11, 27 February 2026 (UTC)[reply]

Thanks about this edit

I already have the syntax highlighter on but somehow neglected that part because, uh... I think I was trying to fix an accidental [[content here] link I created on that same line that broke the entire {{navbox}} template in preview

And then I forgot to italicise that award lol Whyiseverythingalreadyused (t · c · he/him) 14:03, 28 February 2026 (UTC)[reply]

You're welcome. Be careful out there. – Jonesey95 (talk) 15:13, 28 February 2026 (UTC)[reply]

Tech News: 2026-10

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

Wikipedia 25 Birthday mode is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on ~2,500 articles, waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via community configuration on the local wiki.

Updates for editors

The new Parsoid parser continues to be deployed to additional wikis, improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views.

[trimmed by Jonesey95]

MediaWiki message delivery 17:49, 2 March 2026 (UTC)[reply]

Note to self: Parsoid read views is scheduled to come to the English Wikipedia in Q4 2026. Should be fun, with tons of cleanup to do when it arrives. – Jonesey95 (talk) 18:54, 2 March 2026 (UTC)[reply]

Wikipedia:Administrators'_noticeboard/Incidents#Jonesey95's_wikilawyering

There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. sapphaline (talk) 07:53, 4 March 2026 (UTC)[reply]

Thank you for the notice. I was definitely involved. – Jonesey95 (talk) 12:14, 4 March 2026 (UTC)[reply]

I can't find an appropriate category for my template

As a very experienced Wikipedia editor, of course I know every page should be categorized. I just don't know which category to use in this case. If you have an idea which one I can go with, that would be very appreciated. Cheers! Stefen 𝕋ower ^{Huddle • Handiwerk} 20:55, 5 March 2026 (UTC)[reply]

I'm not great with finding categories, but the {{uncategorized}} template that I put in the documentation will put the template in a maintenance category that is watched by a few experts. Someone will probably take care of it. – Jonesey95 (talk) 21:50, 5 March 2026 (UTC)[reply]

Try working down from Category:Wikipedia templates by task. --Redrose64 🌹 (talk) 22:53, 5 March 2026 (UTC)[reply]

Thanks. I tried doing that before but nothing felt like a good fit, so I have ended up selecting a category that might work based on a couple entries within it that do vaguely similar things using article content to produce a stat or report. Stefen 𝕋ower ^{Huddle • Handiwerk} 01:00, 6 March 2026 (UTC)[reply]

Listing for discussion of Template:ClockBlock/doc

Template:ClockBlock/doc has been listed for discussion, which may result in the template being merged or deleted by consensus. You are invited to comment on the proposed action at the entry on the Templates for discussion page. Gonnym (talk) 13:36, 9 March 2026 (UTC)[reply]

Good idea. Thanks. – Jonesey95 (talk) 13:51, 9 March 2026 (UTC)[reply]

Tech News: 2026-11

[trimmed by Jonesey95]

Later this week, Suggestion Mode will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at Special:EditChecks and there are instructions for how administrators can customize the links to point to local guidelines. The feature is connected to Edit check which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment. [8]

Updates for technical contributors

API rate limiting update: To help ensure fair use of infrastructure, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits.

MediaWiki message delivery 18:51, 9 March 2026 (UTC)[reply]

Code review?

I know you are going on your wikibreak soon... Any chance you can review this before you go? Zackmann (^{Talk to me}/_{What I been doing}) 01:42, 10 March 2026 (UTC)[reply]

Done. – Jonesey95 (talk) 13:51, 10 March 2026 (UTC)[reply]

Much appreciated! About to head to work, but will address your concerns this evening. Enjoy your break and catch ya later! Zackmann (^{Talk to me}/_{What I been doing}) 13:52, 10 March 2026 (UTC)[reply]

Thank you

Thank you very much for your support! May God's blessing be with you every day. (Kedassio5538i (talk) 23:24, 14 March 2026 (UTC))[reply]

Tech News: 2026-12

[trimmed by Jonesey95] Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

The Improved Syntax Highlighting beta feature, also known as CodeMirror 6, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new features to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, please share. [9]
Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'. [10]

Updates for technical contributors

A new special page, Special:LintTemplateErrors, has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: Special:LintTemplateErrors/night-mode-unaware-background-color. [11]
Users of the Improved Syntax Highlighting beta feature have been using CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. Feedback or concerns are welcome. [12]

MediaWiki message delivery 19:34, 16 March 2026 (UTC)[reply]

Liste der Grafen und Fürsten von Ostfriesland

[copied from User:Jonesey95/sandbox, where the above header and the second bullet below do not display]

Jonesey95: Interwiki links need a colon. —Anomalocaris (talk) 06:02, 17 March 2026 (UTC)[reply]

Anomalocaris, and yet User_talk:Biruitorul/Archive4#Liste_der_Grafen_und_Fürsten_von_Ostfriesland displays a link. It seems to work in User talk space but not in User space. Mysterious? – Jonesey95 (talk) 12:22, 17 March 2026 (UTC)[reply]

Jonesey95: H:FOREIGNLINK says:

To show the language code and the link to the other language article: ''[[:fr:Jeux olympiques]]'' or [[:ja:東京都]] These links look like this: fr:Jeux olympiques or ja:東京都. The language abbreviation is displayed, so the reader knows that they are links to foreign language articles.
On Talk pages and on Meta, you can omit the leading colon. An interlanguage link like [[fr:Jeux olympiques]] will appear inline in the text, like a regular link.

This is not a talk page, so it's normal that [[de:Liste der Grafen und Fürsten von Ostfriesland|Liste der Grafen und Fürsten von Ostfriesland]] (Liste der Grafen und Fürsten von Ostfriesland) or [[fr:Jeux olympiques]] (fr:Jeux olympiques) are null. —Anomalocaris (talk) 17:02, 17 March 2026 (UTC)[reply]

Thanks for that link. That distinction doesn't make sense to me, so if I ever read it, I didn't remember. In any event, LintHint shows an Empty heading error on User talk:Biruitorul/Archive4, but Page information does not show an error. I have reported a similar instance at T419596. I'm going to move this discussion to my talk page so that it gets archived. – Jonesey95 (talk) 21:21, 17 March 2026 (UTC)[reply]

March 2026 meetup in Portland (online participation available!)

Hey Jonesey95,

You're invited to the March 2026 meetup in Portland, Oregon! Join us either in person at the Northwest Library or online at 10:00 AM on Saturday, March 28.

Please RSVP at the link above, even if you might be interested, so we can know how many people to expect. Hope to see you there!

(To unsubscribe from these updates, remove yourself from this list.) Sent via MediaWiki message delivery (talk) —TechnoSquirrel69 (sigh) 01:45, 18 March 2026 (UTC)[reply]

You're not kidding...

[13] "Extremely" is almost understating it! 😄 JBW (talk) 22:07, 18 March 2026 (UTC)[reply]

The doubly ironic and wonderful part is that my wikifriend User:Beland fixes TONS of typos on Wikipedia, and partners with the Guild of Copy Editors to work on Wikipedia:WikiProject Guild of Copy Editors/Database Report, a monthly report of articles with high numbers of typos (along with some new words that need to go into Wiktionary). I literally laughed out loud when I saw who had added that nonexistent template to an article. – Jonesey95 (talk) 22:12, 18 March 2026 (UTC)[reply]

ISBN check

Hi, I'm looking at https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Check_Wikipedia/ISBN_errors I see many listings for ISBNs beginning with 9796500xxxxxx. I've checked a couple using https://ataraxic.net/isbn-tool/ which tells me "The agency group length was not found in the range data." I haven't been able to find a registration group numbered 6500 but that doesn't necessarily mean it doesn't exist. Do you know of any web-based tool that verifies multiple ISBNs in bulk? Thanks --Lexiconaut (talk) 19:04, 19 March 2026 (UTC)[reply]

Template

Yes, I have a plan for the template. I am working on a draft version in my user space. Sorry, it's taking longer than I expected. Vector2019 (talk) 08:34, 21 March 2026 (UTC)[reply]

Night mode..

{{text color default}} useful? ShakespeareFan00 (talk) 15:59, 22 March 2026 (UTC)[reply]

It's sets the var stuff in one place :) ShakespeareFan00 (talk) 15:59, 22 March 2026 (UTC)[reply]

I think it might be overly complicated for what it does, but I'm open to the idea. It needs documentation and a category, per template guidelines, and I fixed a typo in it the other day. – Jonesey95 (talk) 19:26, 22 March 2026 (UTC)[reply]

Linter

Do we have and/or should we have a Phab ticket like the following?

Title: Exclude certain pages and userspaces from Linter errors (Special:LintErrors).

**Feature summary**: Add the ability to exclude specific pages from Linter error reports. Ideally this would consist of two lists: one for specific pages, and one for usernames whose entire userspace (userpage, user talk page, and subpages of those) should be excluded.

**Use case(s)**: Linter error reports currently include pages outside of mainspace, including userspace. It is not clear that Linter errors outside of mainspace should be reported at all. If so, userspace is the strongest candidate for exclusion: these pages are personal sandboxes, archives, and scratch spaces that editors may intentionally keep in a non-standard state and have no obligation to maintain to article standards. Without a way to exclude them, Linter reports are cluttered with entries that don't really need to be acted on. Editing in people's userspace can cause friction.

**Benefits**:
*Reduces noise in Linter reports by allowing exclusion of pages that will not or cannot be fixed.
*Allows editors to focus on actionable errors in mainspace.
*Reduces friction between gnomes who fix linter errors and people who don't want others to edit their userspace.

As an example, [[ https://en.wikipedia.org/wiki/User_talk:SchroCat/littertray_2 | User talk:SchroCat/littertray 2 ]] is listed in [[ https://en.wikipedia.org/wiki/Special:LintErrors/html5-misnesting | Misnested tag with different rendering in HTML5 and HTML4 ]]. Check out the [[ https://en.wikipedia.org/w/index.php?title=User_talk:SchroCat/littertray_2&action=history | history page ]].

Please let me know what you think, Polygnotus (talk) 20:20, 22 March 2026 (UTC)[reply]

I don't think this is a good idea. Pages in User space are sometimes transcluded into pages outside of User space and can cause problems there. I think it might be worth having this discussion once we have cleared all of the Linter errors that we can clear. We are perhaps a few years away from that point. And don't worry about one-off issues like User talk:SchroCat/littertray. They have always gotten cleared up eventually. Work on some of the three million other errors and ignore that one. – Jonesey95 (talk) 21:06, 22 March 2026 (UTC)[reply]

Interesting, thank you. I have to think about this a bit and I may return with a follow-up. Work on some of the three million other errors and ignore that one. That is excellent advice for all parties, methinks. Polygnotus (talk) 21:09, 22 March 2026 (UTC)[reply]

Guild of Copy Editors/Membership/News/2025 Annual Report

Guild of Copy Editors Annual Report

Our 2025 Annual Report is now ready for review.

Highlights:

Introduction
Membership news and election results
Summary of Drives, Blitzes and the Requests page
Closing words

– Your Guild coordinators

To stop receiving GOCE newsletters, please remove your name from our mailing list.

MediaWiki message delivery (talk) 05:35, 31 March 2026 (UTC)[reply]

Apologies

It was my first time making userboxes, and I'm sorry you had to clean up my error. Thank you for fixing it though. Raskuly (talk) 18:04, 2 April 2026 (UTC)[reply]

No worries. There are many things to learn about how this place works. There is no way that one person can know all of the traditions, guidelines, policies, informal rules, and other quirks of this glorious encyclopedia. – Jonesey95 (talk) 20:39, 2 April 2026 (UTC)[reply]

March 2026 GOCE drive award

		The Minor Barnstar
This barnstar is awarded to Jonesey95 for copy edits totaling between 1 and 3,999 words (including bonus and rollover words) during the GOCE March 2026 Backlog Elimination Drive. Congratulations, and thank you for your contributions! GoldRomean (talk) 23:03, 3 April 2026 (UTC)[reply]

Dating maintenance tags on templates

Hi Jonesey. Unlike for articles, there isn't a bot to date maintenance tags on templates, so we have to do it ourselves. Cheers. Bsherr (talk) 14:17, 4 April 2026 (UTC)[reply]

I've made over 100 edits to Template space in the last week, and over 1,000 in the last two months, so I'm not sure what you are referring to. Please link to an edit of mine so that I can see what you are talking about. – Jonesey95 (talk) 14:26, 4 April 2026 (UTC)[reply]

If you are referring to {{uncategorized}}, it does not subst properly in /doc pages. See the history of Template:WMATA ridership/doc. I'm not willing to manually type the date and inevitably make typos; I copy and paste when I do these template page cleanup operations. If you want AnomieBOT to add dates to these tags, it might do so if you ask nicely. – Jonesey95 (talk) 14:56, 5 April 2026 (UTC)[reply]