Lint errors
I support and supported this bot, but it has been a huge annoyance in my watchlist now going in for days/weeks. In particular old AfDs. It so floods my watchlist I am having trouble seeing legit edits. I can not disable bot notifications for other reasons. What can we do such that it doesn't keep editing the same pages repeatedly, and makes a single edit to the page fixing all errors at once? GreenC 15:10, 11 February 2022 (UTC)
- There are a few things:
- The easiest would be to hide only MalnadachBot from your watchlist as explained in WP:HIDEBOTS.
- You can proactively fix Lint errors in pages that appear in your watchlist so that no further edits would be necessary. WP:LINTHINT would be a useful tool for this.
- Follow up on the above step and add any Lint error pattern you find to User:MalnadachBot/Signature submissions so that I can add it to the Bot run logic.
- The ideal solution would be to have general purpose regexes with zero (or as close to zero as possible) false positives so that I can use them instead of specific regexes. I had spent a lot of time trying to build a perfect set of regexes to no avail. At this point I don't think it is possible to build general regexes with false positive rates as low as specific regexes for a fully automated Bot task. If anyone is interested in taking this on, reading the subpages of Task 2 will give you an idea of the sheer number of things to consider (and there are lots more). For many pages it is very hard to fix all errors in one edit even if done manually. Here it took me 3 tries and 1.5 hrs to get all errors.
- The flood of AFD page edits is because my Bot is currently going through items number 71 and 72 listed in User:MalnadachBot/Task 12/51-100, along with opportunistically fixing 90 other signatures if present in a page. This is the single largest Lint error pattern ever to exist in en.wp, being present in about 330k pages or nearly every AFD page from before March 2018. Since every AFD page is transcluded in a daily log page, the errors in individual pages gets transcluded there as well doubling the number of errors. When my Bot is done with this, 660k Lint errors would be fixed. About 60% of this is done, the rest will be over in a couple of weeks. Edits to AFD pages after that will not be as high volume as now. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:06, 11 February 2022 (UTC)
- Do you use AWB pattern matching or custom software? The later could be more flexible. Can still use AWB for login, download and posting, via the external program feature that does the actual page processing. That way you can build up a library of separate regex as you find them, and by the end it will get most of them in one edit. If I understand the situation correctly. Anyway, I'll try hidebots. -- GreenC 19:16, 11 February 2022 (UTC)
- I use AWB's find and replace in both simple and advanced settings depending on the error. I go on adding replacements to the list as I find them. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 04:08, 12 February 2022 (UTC)
- Do you use AWB pattern matching or custom software? The later could be more flexible. Can still use AWB for login, download and posting, via the external program feature that does the actual page processing. That way you can build up a library of separate regex as you find them, and by the end it will get most of them in one edit. If I understand the situation correctly. Anyway, I'll try hidebots. -- GreenC 19:16, 11 February 2022 (UTC)
Sorry why is this bot messing with editor's signatures? GiantSnowman 11:52, 21 February 2022 (UTC)
- My bot is replacing the obsolete
<font>...</font>
tags with CSS. This is so that signatures and other usages continue to display as editors originally intended when support for font tags is dropped. This work has been going so since 2018. A small group of gnomes have reached out to users who had font tags in their signature and convinced them to change it to prevent its further spread. The vast majority of users have already replaced it. However this particular editor has refused to change their signature despite multiple requests. So they continue to leave error reports wherever they sign. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 12:29, 21 February 2022 (UTC)- This is one reason why banning the use of templates for editor sigs is so silly. If custom sigs were done in a template lint errors (and I remind everyone these were not errors at the time the sigs were created) could be fixed with a single edit across the whole wiki. Nobody would get anything in their watchlist except the editor who owned that sig and anyone watching the template. SpinningSpark 14:46, 14 April 2022 (UTC)
- I fully agree. I guess you found your way here because your old signature is among a batch that MalnadachBot is currently replacing, item 597 in User:MalnadachBot/Task 12/551-600. --ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 15:22, 14 April 2022 (UTC)
- This is one reason why banning the use of templates for editor sigs is so silly. If custom sigs were done in a template lint errors (and I remind everyone these were not errors at the time the sigs were created) could be fixed with a single edit across the whole wiki. Nobody would get anything in their watchlist except the editor who owned that sig and anyone watching the template. SpinningSpark 14:46, 14 April 2022 (UTC)
Hello
Any idea how many different signatures the bot has to fix to finish task 12? 🐔dat (talk) 11:12, 22 February 2022 (UTC)
- Considering only the signatures present in more than 50 pages, I would say it will be at least ten times the size of User:MalnadachBot/Task 2, which makes it 15,000. Then there is a lot more of non signature lint. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 11:41, 22 February 2022 (UTC)
Username
Hi, I just wanted to make a quick comment about your username. As per Wikipedia:Username policy, a non-Latin username is allowed, but can be problematic. From Wikipedia:Signatures;
Editors with non-Latin usernames are welcome to edit in Wikipedia. However, non-Latin scripts, such as Arabic, Armenian, Chinese, Cyrillic, Greek, Hebrew, Indic scripts, Japanese, Korean, Persian, Thai and others, are illegible to most other contributors of the English Wikipedia. Not everyone uses a keyboard that has immediate access to non-Latin characters, and names that cannot be pronounced cannot be retained in memory. As a courtesy to the rest of the contributors, users with such usernames are encouraged to sign their posts (at least in part) with Latin characters. For an example refer to User:Παράδειγμα, who signs his posts as "Παράδειγμα/Paradigma."
I understand your username is apparently Kannada, one of the languages of India, and seems to translate to "Malnadach Konkno
". I'm not sure what the significance of that is to you, but if you would consider adding that, or another Latinized name or word to your signature, it would make interacting with you a great deal easier for your fellow editors, eg: ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ/Malnadach Konkno.
To attach a Latinized word or name to your signature, just go to "Preferences", and on the first page, under "User Profile", scroll down to "Signatures". There you will see a text box where you can customize your signature to your liking and you will be able to modify it with an add-on in Latin script that will help others identify and communicate with you. There are additional instructions at Wikipedia:Signature tutorial, and at the bottom of the page you will find a list of unique, colorful and creative signatures, just as you will see throughout Wikipedia, that may help give you some ideas. If you need any assistance, you can contact the Help Desk. I hope you find this useful and, happy editing! - wolf 08:43, 24 February 2022 (UTC)
- @Thewolfchild: I understand the point about being illegible to most en.wp users, but that is a consequence of username being global across all WMF wikis. I am active in Kannada script wikis too and my username is well established there.
- I did consider adding a Roman transliteration in my signature before, but decided against it to avoid confusing new users. For example, if I sign as ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ/Malnadach Konkno or other variations, a new user not familiar with wikitext and custom signatures may get confused about what is my actual username. They may try to ping me using
{{ping|ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ/Malnadach Konkno}}
,{{ping|Malnadach Konkno}}
and other invalid uses. If I use the deafult signature, there wouldn't be this confusion. You can see this which explains more on how new users are confused by custom signatures. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 12:17, 24 February 2022 (UTC)- That link is a tp post from a single user (and rather lengthy one at that... I didn't read it, I'll just take your word that they think custom signatures are "confusing to new users"). That said, my post is just a suggestion, with relevant WP policy included to support it and to help guide you. The simple fact is this is the English WP, and by far, very, very few readers will understand what your username means, or even what language it is. The idea of adding something, anything, in English with Latin script, (or even just a number!) is also from the the policy attached.
If users are previewing their posts as they should, they will see that any altered signature will show as a red link and they can take the few extra seconds to correct accordingly (I use my own signaure and your own reply here as an example of that.) But, pinging is one thing, while simple identification is quite another. Having the abilty to refer to you directly, or to others, especailly in an on-going discussion can be of great use, while conversely not being able to do so, particularly because of a lack of that specific keyboard, can be of great hindrance. I just wanted you to be mindful of others here. But as I said, it was just a suggestion, and what you do with your signature is up to you. Have a nice day. - wolf 13:45, 24 February 2022 (UTC)
- That link is a tp post from a single user (and rather lengthy one at that... I didn't read it, I'll just take your word that they think custom signatures are "confusing to new users"). That said, my post is just a suggestion, with relevant WP policy included to support it and to help guide you. The simple fact is this is the English WP, and by far, very, very few readers will understand what your username means, or even what language it is. The idea of adding something, anything, in English with Latin script, (or even just a number!) is also from the the policy attached.
Signature
While another bot fixed a lint issue here, I noticed that the signature itself is using the font tag. I'm not sure how many instances of this signature are around, or if it is already reported, but figured I'll leave a note here. Gonnym (talk) 17:25, 27 February 2022 (UTC)
- Thanks Gonnym, I will add it to my bot replacement list. Not sure why WOSlinker did not replace font tags while fixing the misnesting. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 18:12, 27 February 2022 (UTC)
- Another signature I came across which colored an entire talk page is
[[User:NoSeptember|<font color="A29EBA">'''NoSeptember''']]<sup><font color=00cc00>[[User_talk:NoSeptember|-]]
. Gonnym (talk) 06:26, 7 March 2022 (UTC)- @Gonnym: I've replaced all instances of this sig. You can add anything that needs done to User:MalnadachBot/Signature submissions. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 08:28, 7 March 2022 (UTC)
- Another signature I came across which colored an entire talk page is
The Signpost: 27 February 2022
- From the team: Selection of a new Signpost Editor-in-Chief
- News and notes: Impacts of Russian invasion of Ukraine
- Special report: A presidential candidate's team takes on Wikipedia
- In the media: Wiki-drama in the UK House of Commons
- Technology report: Community Wishlist Survey results
- WikiProject report: 10 years of tea
- Featured content: Featured Content returns
- Deletion report: The 10 most SHOCKING deletion discussions of February
- Recent research: How editors and readers may be emotionally affected by disasters and terrorist attacks
- Arbitration report: Parties remonstrate, arbs contemplate, skeptics coordinate
- Gallery: The vintage exhibit
- Traffic report: Euphoria, Pamela Anderson, lies and Netflix
- News from Diff: The Wikimania 2022 Core Organizing Team
- Crossword: A Crossword, featuring Featured Articles
- Humour: Notability of mailboxes
ITN recognition for Shane Warne
On 4 March 2022, In the news was updated with an item that involved the article Shane Warne, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. GihanJayaweeraTALK 14:57, 4 March 2022 (UTC) |
ITN recognition for Shane Warne
On 4 March 2022, In the news was updated with an item that involved the article Shane Warne, which you nominated. If you know of another recently created or updated article suitable for inclusion in ITN, please suggest it on the candidates page. — Amakuru (talk) 20:44, 4 March 2022 (UTC) |
Lint errors on blocked user talk pages
Perhaps it would be best if the bot didn't create new unblock requests on user talk pages that have been blocked for eight years, such as User talk:Elle(Sri Lanka). It creates unnecessary extra work for those of us who attend to such requests. --jpgordon𝄢𝄆𝄐𝄇 17:42, 19 March 2022 (UTC)
- @Jpgordon: that was due to a bug caused by an unclosed nowiki tag and template further up in the page. It caused strange things when my bot edited the page, which I tried to fix here. I was not aware it opened an unblock request, sorry for the trouble. When you restored the page to older version, it has caused your signatures to appear after comments which you didn't make. Special:MobileDiff/1078066283 ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 18:01, 19 March 2022 (UTC)
- Perhaps the bot shouldn't bother on talk pages of blocked users? Anyway, I appreciate what you're doing; I just got more puzzled by the unblock request than was useful. --jpgordon𝄢𝄆𝄐𝄇 21:40, 19 March 2022 (UTC)
- I just deleted the thing; there's no reason for it to exist and it's a mess. --jpgordon𝄢𝄆𝄐𝄇 04:32, 20 March 2022 (UTC)
- Perhaps the bot shouldn't bother on talk pages of blocked users? Anyway, I appreciate what you're doing; I just got more puzzled by the unblock request than was useful. --jpgordon𝄢𝄆𝄐𝄇 21:40, 19 March 2022 (UTC)
The Signpost: 27 March 2022
- From the Signpost team: How The Signpost is documenting the 2022 Russian invasion of Ukraine
- News and notes: Of safety and anonymity
- Eyewitness Wikimedian – Kharkiv, Ukraine: Countering Russian aggression with a camera
- Eyewitness Wikimedian – Vinnytsia, Ukraine: War diary
- Eyewitness Wikimedian – Western Ukraine: Working with Wikipedia helps
- Disinformation report: The oligarchs' socks
- In the media: Ukraine, Russia, and even some other stuff
- Wikimedian perspective: My heroes from Russia, Ukraine & beyond
- Discussion report: Athletes are less notable now
- Technology report: 2022 Wikimedia Hackathon
- Arbitration report: Skeptics given heavenly judgement, whirlwind of Discord drama begins to spin for tropical cyclone editors
- Traffic report: War, what is it good for?
- Deletion report: Ukraine, werewolves, Ukraine, YouTube pundits, and Ukraine
- From the archives: Burn, baby burn
- Essay: Yes, the sky is blue
- Tips and tricks: Become a keyboard ninja
- On the bright side: The bright side of news
Administrators noticeboard discussion
There is currently a discussion at Wikipedia:Administrators' noticeboard regarding an issue with which you may have been involved. Thank you.Catfish Jim and the soapdish 18:37, 30 March 2022 (UTC)
The Signpost: 24 April 2022
- News and notes: Double trouble
- In the media: The battlegrounds outside and inside Wikipedia
- Special report: Ukrainian Wikimedians during the war
- Eyewitness Wikimedian – Vinnytsia, Ukraine: War diary (Part 2)
- Technology report: 8-year-old attribution issues in Media Viewer
- Featured content: Wikipedia's best content from March
- Interview: On a war and a map
- Serendipity: Wikipedia loves photographs, but hates photographers
- Traffic report: Justice Jackson, the Smiths, and an invasion
- News from the WMF: How Smart is the SMART Copyright Act?
- Humour: Really huge message boxes
- From the archives: Wales resigned WMF board chair in 2006 reorganization
A bowl of strawberries for you!
Thank you for this comment and for sharing this information with everyone. I really appreciate it. WhatamIdoing (talk) 20:45, 16 May 2022 (UTC) |
CSD G2 - test pages
Hallo, You nominated a user's sandbox page for CSD G2, but please note that "This criterion applies neither to sandboxes nor to pages in the user namespace." A user can do what they want in their own sandboxes as long as it does not breach copyright, include unsourced controversial BLP content, or appear to be in some other way totally unacceptable. I have reverted. PamD 11:22, 25 May 2022 (UTC)
- PamD, you may not have noticed that the page is in mainspace and is not a userspace page at the moment. -- WOSlinker (talk) 11:57, 25 May 2022 (UTC)
- @WOSlinker and ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ: Of course. Sorry about that. Just like the page creator, I didn't spot the difference! PamD 13:17, 25 May 2022 (UTC)
The Signpost: 29 May 2022
- From the team: A changing of the guard
- News and notes: 2022 Wikimedia Board elections
- Community view: Have your say in the 2022 Wikimedia Foundation Board elections
- In the media: Putin, Jimbo, Musk and more
- Special report: Three stories of Ukrainian Wikimedians during the war
- Discussion report: Portals, April Fools, admin activity requirements and more
- WikiProject report: WikiProject COVID-19 revisited
- Technology report: A new video player for Wikimedia wikis
- Featured content: Featured Content of April
- Interview: Wikipedia's pride
- Serendipity: Those thieving image farms
- Recent research: 35 million Twitter links analysed
- Tips and tricks: The reference desks of Wikipedia
- Traffic report: Strange highs and strange lows
- News from Diff: Winners of the Human rights and Environment special nomination by Wiki Loves Earth announced
- News from the WMF: The EU Digital Services Act: What’s the Deal with the Deal?
- From the archives: The Onion and Wikipedia
- Humour: A new crossword
In appreciation of you and your bot
The Million-Gnome-Edit Star | ||
This barnstar is awarded to ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ and their bot for fixing literally millions of Linter errors. Thank you so much for running the bot; it has turned the idea of ridding the English Wikipedia of Linter errors from a hopeless fantasy into a possible reality. – Jonesey95 (talk) 16:05, 8 June 2022 (UTC) |
- You're welcome :-) I can hardly believe how much we have dented the backlog in an year. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 17:03, 8 June 2022 (UTC)
- Have you considered replacing obsolete center tags in article space? There are thousands of articles with straightforward replacements; I would guess that easy center tag replacements represent at least 100,000 of the 108,000 obsolete tag errors in article space. You might run into some of the same resistance about not replacing every single instance. Optionally, if your bot can check for remaining center tags after applying its replacements but before saving the article, it could decide not to save the edit. I think that almost all articles would require at most two passes to get rid of all of the center tags (one to replace the single-line text wraps, and another manual or semi-automated pass to replace the centering of block content like tables, as well as any stragglers). A clever regex constructor might even be able to figure out how to replace at least some of the table centering during the first pass; I am not that clever. – Jonesey95 (talk) 18:00, 13 June 2022 (UTC)
- Originally my plan was to ignore article space and focus on discussion namespaces since they are not suitable for linting by gnomes. I'll see how feasible it is to do center tag replacement using my bot. Probably best to do it supervised, although LintHint cannot be used from AWB. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 11:00, 14 June 2022 (UTC)
- I have made some 250 supervised edits, skipping pages that still have center tags after applying changes. I will examine the skipped pages later and include them in a second run after the easier ones are replaced. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 13:13, 14 June 2022 (UTC)
- I noticed that the error count was dropping like a rock! Nice work. Would you consider running your bot through the list at User:Galobot/report/Articles by Obsolete Tags, if you have not done so already? I have some (admittedly not great, but no false positives) regexes at User:Jonesey95/AutoEd/coauthors.js that fix about 90% of in-line center tags. They currently don't find things like check mark characters or most non-Latin-alphabet characters, because I don't entirely trust myself with some of the regex character-capturing symbols. I really dislike false positive replacements and replacement errors, so I stay very conservative. – Jonesey95 (talk) 17:22, 14 June 2022 (UTC)
- I think your regexes can be simplified and match more characters at the same time. For exmaple
str.replace(/\<center\>([\d\'\"a-z _\%\&\|\}\{\-\.\,\(\)–—\*:\+ößáàăâåäãāảạæćČçĐéèêếềễěëėęēệíìîïİįīịıĽńñóòôỗöõøōơờọœřšŞúùûüũūưứýỳ¡§:\!\?⊕⊗会話投稿記録日本穣投稿]*\<ref name\=\"*[a-z_ \d\-]+\"*\s*\/\>\s*)\<\/center\>/gi, '\{\{center\|$1\}\}');
can be replaced withstr.replace(/<center>([^<]+?<ref name\=\"*[^/]+?\/> *)<\/center>/gi, '{{center|$1}}');
. I have some at User:ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ/center.js, though they are mainly for replacing it withstyle="text-align:center;"
in table cells. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 12:05, 15 June 2022 (UTC)
- I think your regexes can be simplified and match more characters at the same time. For exmaple
- I noticed that the error count was dropping like a rock! Nice work. Would you consider running your bot through the list at User:Galobot/report/Articles by Obsolete Tags, if you have not done so already? I have some (admittedly not great, but no false positives) regexes at User:Jonesey95/AutoEd/coauthors.js that fix about 90% of in-line center tags. They currently don't find things like check mark characters or most non-Latin-alphabet characters, because I don't entirely trust myself with some of the regex character-capturing symbols. I really dislike false positive replacements and replacement errors, so I stay very conservative. – Jonesey95 (talk) 17:22, 14 June 2022 (UTC)
- Have you considered replacing obsolete center tags in article space? There are thousands of articles with straightforward replacements; I would guess that easy center tag replacements represent at least 100,000 of the 108,000 obsolete tag errors in article space. You might run into some of the same resistance about not replacing every single instance. Optionally, if your bot can check for remaining center tags after applying its replacements but before saving the article, it could decide not to save the edit. I think that almost all articles would require at most two passes to get rid of all of the center tags (one to replace the single-line text wraps, and another manual or semi-automated pass to replace the centering of block content like tables, as well as any stragglers). A clever regex constructor might even be able to figure out how to replace at least some of the table centering during the first pass; I am not that clever. – Jonesey95 (talk) 18:00, 13 June 2022 (UTC)
Center tag replacement advice
Wikipedia:HTML 5#Tables says that center tags in table cells should be replaced with style="text-align:center;" |
But I see that they are often, although not always, replaced with the {{center}} template. Which should I be using?
Your bot is currently hard at work replacing center tags in cells, so there may not be much left for us gnomes to fix when it's finished!
—Bruce1eetalk 08:54, 18 June 2022 (UTC)
- Either is fine.
style="text-align:center;" |
can be used on a larger set, but is harder to apply in bulk. {{center}} is easier to do in bulk, but it cannot be used if the text has unescaped=
or|
in it. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 10:10, 18 June 2022 (UTC)
Arbitration case opened
You recently offered a statement in a request for arbitration. The Arbitration Committee has accepted that request for arbitration and an arbitration case has been opened at Wikipedia:Arbitration/Requests/Case/Conduct_in_deletion-related_editing. Evidence that you wish the arbitrators to consider should be added to the evidence subpage, at Wikipedia:Arbitration/Requests/Case/Conduct_in_deletion-related_editing/Evidence. Please add your evidence by July 9, 2022, which is when the evidence phase closes. You can also contribute to the case workshop subpage, Wikipedia:Arbitration/Requests/Case/Conduct_in_deletion-related_editing/Workshop. For a guide to the arbitration process, see Wikipedia:Arbitration/Guide to arbitration. For the Arbitration Committee, firefly ( t · c ) 11:20, 18 June 2022 (UTC)
Bot mistake: replacing center tags in nested wikitables
Hi! MalnadachBot recently made this edit, which caused many table-open tags ({|
) to be placed on lines that already had a colspan defined, which caused the table tags not to work. I'm not sure if it's made this mistake more often, but could you make sure it doesn't happen again? Thanks! --rchard2scout (talk) 14:13, 28 June 2022 (UTC)
- Thanks for bringing this to my attetion, now set it to properly handle this. Centered nested tables with row or colspan is rare enough it is unlikely to have screwed up more than a few pages. This search doesn't give any other result. ಮಲ್ನಾಡಾಚ್ ಕೊಂಕ್ಣೊ (talk) 14:51, 28 June 2022 (UTC)
MalnadachBot 13
Wikipedia:Bots/Requests for approval/MalnadachBot 13 has been approved. Happy editing! TheSandDoctor Talk 18:15, 9 July 2022 (UTC)