If you want to report a JavaScript error, please follow this guideline. Questions about MediaWiki in general should be posted at the MediaWiki support desk. Discussions are automatically archived after remaining inactive for 5 days.
This tends to solve most issues, including improper display of images, user-preferences not loading, and old versions of pages being shown.
No, we will not use JavaScript to set focus on the search box.
This would interfere with usability, accessibility, keyboard navigation and standard forms. See task 3864. There is an accesskey property on it (default to accesskey="f" in English). Logged-in users can enable the "Focus the cursor in the search bar on loading the Main Page" gadget in their preferences.
No, we will not add a spell-checker, or spell-checking bot.
You can use a web browser such as Firefox, which has a spell checker.
If you changed to another skin and cannot change back, use this link.
Alternatively, you can press Tab until the "Save" button is highlighted, and press Enter. Using Mozilla Firefox also seems to solve the problem.
If an image thumbnail is not showing, try purging its image description page.
If the image is from Wikimedia Commons, you might have to purge there too. If it doesn't work, try again before doing anything else. Some ad blockers, proxies, or firewalls block URLs containing /ad/ or ending in common executable suffixes. This can cause some images or articles to not appear.
I guess you have already installed the app on your new phone. On your old phone, open the app, tap the three-dot menu, and select Transfer accounts, then choose Export accounts. Select the accounts you want and a QR code will appear. On your new phone, open the app, choose Import accounts, then Scan QR code, and scan the code from your old phone. Your accounts will be copied over, and you should keep your old phone until you have confirmed that everything is working correctly. – DreamRimmer■07:46, 18 August 2025 (UTC)Reply
@DreamRimmer, you should keep your old phone until you have confirmed that everything is working correctly Better yet, make sure you know where the printout of your recovery codes is and verify it hasn't faded. — Alexis Jazz (talk or ping me) 16:17, 18 August 2025 (UTC)Reply
Another way is to disable 2FA when on the old phone, and then re-enroll with the new phone. This does require that you are still eligible for 2FA however (different groups have different eligibility). As you are still an oversighter, you should still be eligible. —TheDJ (talk • contribs) 08:54, 18 August 2025 (UTC)Reply
Global requirements are slowly increasing over time. There are some sensitive groups that we require to have 2FA, and some that their tools become disabled when 2FA isn't set up now. — xaosfluxTalk14:09, 18 August 2025 (UTC)Reply
I think there needs to be a better recovery system other than "have a database admin manually flip the 2FA bit" before it's made mandatory for a larger group of editors. --Ahecht (TALK PAGE)19:42, 25 August 2025 (UTC)Reply
Latest comment: 1 day ago8 comments7 people in discussion
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
Later this week, people who are logged-in and have the "Discussion tools" Beta Feature enabled will gain the ability to "Thank" individual comments directly from talk pages, rather than needing to navigate to page history. Learn more about this feature. [1]
An A/B test comparing two versions of the desktop donate link launched on testwiki on 12 August and on English Wikipedia 14 August for 0.1% of logged out users on the desktop site. The experiment will run for three weeks, ending on 12 September. [2]
An A/A test to measure the baseline for reader retention was launched 12 August using Experimentation Lab. This measures the percentage of users who revisit a wiki after their initial visit over a 14-day period. No visual changes are expected. The experiment will run through 31 August. [3]
Yeah, that screenshot is from ptwiki, where we had already been testing that feature out. If you're curious to see more about it, it's also on testwiki.
We released Thanks there first (without the beta feature), because it already had the overflow menu present for Report and the editors were thus used to an extra button being present. DLynch (WMF) (talk) 20:16, 21 August 2025 (UTC)Reply
I do have to say, the single-item overflow menu just for "Thank" is a bit goofy, but it will make more sense once "Report" is rolled out. --Ahecht (TALK PAGE)13:52, 26 August 2025 (UTC)Reply
What Report does and when it should be used seems unclear to the casual visitor. I suspect most of its clicks will accidentally escalate minor matters which are best dealt with by local admins. Certes (talk) 22:48, 26 August 2025 (UTC)Reply
Latest comment: 1 day ago10 comments7 people in discussion
no class
mw-no-invert
OK, so the image at right in "light mode", renders correctly. When you switch it to "dark mode", the colors become a bit de-saturated, this is especially obvious in the reds. I initially thought this was an optical illusion, but confirmed it by inspecting the element in Firefox's DOM/style inspector.
The guilty CSS for handling dark mode appears to be this CSS:
If I remove the hue-rotate(180deg) the image renders correctly, however, the other colors on the page do not. I initially thought it might be possible to override the filter property on just the image element, but this does not appear to work. I know there's a CSS class, .mw-no-invert, but this seems to have the effect of inverting the image (see other example at right).
That got it. Oddly I disabled the dark mode gadget in preferences, hit save, then went to appearance and chose vector-2022, hit save and came back and the issue was still present. Went into the appearance widget in vector-2022 and dark/light mode were disabled, saying the gadget was still active, helpfully it had a button to disable it and that finally got it working.
Same. I much prefer the gadget version + skin:Minerva Neue, it looks nicer on smartphone, even while viewing desktop pages without even enabling the browser's desktop mode. The downsides are that there are templates where it doesn't work[a] (usually the underused/undocumented ones), and certain images need to have |class=skin-invert in their source code to be visible; and also, of course, the one you posted above. I don't like that the default Dark Mode (Vector 2022) keeps the background white for certain transparent images.
If the gadget is deprecated and the vector2022 dark mode is preferred one for vector 2022, is it possible to disable the gadget from running if the skin is vector 2022? – robertsky (talk) 17:14, 22 August 2025 (UTC)Reply
We can remove it from the options. I am fairly certain that does not remove it from the selection people will have made in their preferences, but I am not totally certain.
Yeah, I don't know that deprecated is the right word. It currently says not recommended, which makes sense, but if you want to use a non-vector 2022 skin, I think that gadget is the only thing that enables a dark mode option. —Locke Cole • t • c19:51, 22 August 2025 (UTC)Reply
Like I said, 'if the skin is vector 2022'. Have additional codes or something to detect if current skin used is v22 and either direct the user to enable the darkmode option in their preferences or enable that for them instead of allowing the css to load. It shouldnt impact on the other skins until they get dark mode support... if ever. – robertsky (talk) 05:53, 24 August 2025 (UTC)Reply
Latest comment: 5 days ago15 comments5 people in discussion
Hi, as you know the Vector 2022 skin has the TOC on the sidebar, which is no longer inserted inside articles. However, it seems most TOC templates (such as {{Compact TOC}}) automatically hide the TOC, and other pages manually hide it by using the _NOTOC_ magic word. This makes browsing lists much harder. Since it could be argued that alphabetical lists are the kind of pages where having a TOC is most important, why haven't the TOC templates and specific list pages been updated?
Since it could be argued that alphabetical lists are the kind of pages where having a TOC is most important, why haven't the TOC templates and specific lists been updated?
I guess my question is "shouldn't we check the NOTOC pages (or use a bot or script to do that) and correct the outdated templates/magic words that cause the TOC to not appear?" FaviFake (talk) 15:31, 22 August 2025 (UTC)Reply
It would probably be nice to not break things for people who use skins other than Vector 2022, however, so it's likely not that simple. Anomie⚔17:26, 22 August 2025 (UTC)Reply
Yup! This is one of the reason I asked here before doing anything :) I had suspected that would be a problem. I'd like to find a solution to this problem that hopefolly works for everyone. FaviFake (talk) 17:29, 22 August 2025 (UTC)Reply
Oh, that's smart! I don't see any drawbacks. What would it take for all templates and pages using NOTOC to start using that method instead?
Maybe we could create a template that just contains <div style="display:none">__TOC__</div> and replace every NOTOC with it. It could be called {{hit}} (hide inline toc). Thoughts? FaviFake (talk) 09:41, 23 August 2025 (UTC)Reply
The trend over the past several years would prefer the template be named like {{hide inline toc}} over an abbreviation like {{hit}}. I'd be wary of blindly replacing all__NOTOC__ with this template, and if there really aren't ever reasons to hide the TOC in Vector2022 it'd probably be better for devs to remove support for __NOTOC__ from that skin entirely rather than hackily having the TOC be hidden with CSS in all other skins. Anomie⚔13:34, 23 August 2025 (UTC)Reply
Yes, of course, i intended {hit} to be a redirect. (But we still haven't renamed ambox...).
Sure, it would be better for the devs to do something, but it's been two years since this started happening and nothing has changed. in the interim we should try to do something for these poor lists. Also, some very specific pages might still need to hide the TOC, but they're likely very few in comparison to the many article needlessly lacking a sticky TOC. This might make the devs wary of removing the magic word.
They tried renaming ambox, but it failed for that case.Manual replacement, 🤷. I'd still skip the cryptic redirect name in this case and use the more descriptive name though. And hopefully no one decides to act like an unauthorized bot or a WP:MEATBOT about it. Anomie⚔14:02, 23 August 2025 (UTC)Reply
Since all non–Vector 2022 ToCs are inside .mw-parser-output, you could just have TemplateStyles with #toc{display:none;} and it would hide the ToC for all non–Vector 2022 skins. Nardog (talk) 16:00, 23 August 2025 (UTC)Reply
Many custom TOC's like {{Compact TOC}} add id="toc" so it isn't that simple. If duplicate id's are still considered problematic when one of them is in display:none then my approach may also need more work. PrimeHunter (talk) 19:58, 25 August 2025 (UTC)Reply
It's more just input on the accessibility part @Pppery as I was unsure if my correction to give mbox role="none" instead of role="presentation" is correct, and also that would affect our version because I'd make an edit request because it's a meta template, and it would of course be most ideal if our mbox met accessibility requirements... waddie96 ★ (talk)18:20, 25 August 2025 (UTC)Reply
Why is Add topic button shiverring and reappearing sometimes while scrolling down or up? This is much more common while scrolling to see content below. It behaves unintuitively. Sometimes, it flashes near plus symbol on the other hand. (mobile view, updated Android Chrome browser more than a week ago to latest version) 5.43.101.148 (talk) 08:26, 25 August 2025 (UTC) [e]Reply
It is because of clashing animations. When it is in view, it should always be visible. When it is not in view, and you scroll down, it is not visible, but if you scroll up, it makes itself visible.. When you get to the bottom these commands seem to conflict at times. I have filed the ticket phab:T402798. —TheDJ (talk • contribs) 12:59, 25 August 2025 (UTC)Reply
It is flashing also when click at Edit link from three dots loaded somewhere in the middle, along with loaded text Reply and arrow before that are flashing and are part of same tech feature. --5.43.101.148 (talk) 08:49, 26 August 2025 (UTC)Reply
Reply tool changed IMDb link in unrelated section?
Check your scripts first to see if anything would do something like this, but otherwise I think it's fair to file an upstream for it. Izno (talk) 16:23, 25 August 2025 (UTC)Reply
Latest comment: 5 days ago3 comments3 people in discussion
I came across this page and its page history makes no sense. It is full of seemingly RevDels for the edit summary and a lot of zero byte edits with no diff from the previous edit. I have browsed edits that have had revdel/oversight applied to them on other pages and they don't appear like this, normally it won't let the edit be selected for diff comparison in the history. For example, I haven't seen a diff between consecutive edits like this before where there is (No difference). If this is the wrong place for this question or if this is not good for a public forum, please let me know and I'll remove, but what is happening with this page history and is it broken? Casablanca 🪨(T)16:03, 25 August 2025 (UTC)Reply
@Casablanca Rock: Yes, the two edits by Milan092 were actually page moves and the following edits reverted the moves so they didn't change the wikitext. The edit summary would have started with "45dogs moved page ...", but the whole edit summary was revisiondeleted. For comparison, here is a normal move without revisiondeletion. PrimeHunter (talk) 17:12, 25 August 2025 (UTC)Reply
Latest comment: 5 days ago1 comment1 person in discussion
I've been experiencing a problem using the visual editor today: if I click on "edit" or open the source editor and then try to switch to the visual editor via the pencil icon, it starts to open the visual editor and then stalls ~2/3s of the way through. (2/3s is based on the how much of the block at the top of the screen turns from white to blue; see image.) I've encountered this problem on every page I've tried to edit using the visual editor (e.g., Deportation of Kilmar Abrego Garcia). I've tried clearing the cache and restarting my browser, Firefox 142.0 for Mac, but neither helped. Wondering if anyone has a suggestion. Thanks, FactOrOpinion (talk) 19:48, 25 August 2025 (UTC)Reply
Latest comment: 5 days ago1 comment1 person in discussion
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
Template authors can now use additional CSS properties, since the CSS sanitizer used by TemplateStyles was updated. For example: width: fit-content; ruby-align; relative units such as lh; and custom strings in list-style-type. These improvements are a Community Wishlist wish. [9][10][11][12][13][14][15][16][17][18]
On large wikis, the default time period to display edits from, within the Special:RecentChanges page, has been changed from 7 days to 1 day. This is part of a performance improvement project. This should have no user-facing impact due to the quantity of edits on these wikis. [19]
Wikimedia Commons videos were not shown in the Videos tab in Google Search. The problem was investigated and reported to Google who have now fixed the issue. [21][22]
Two fields of the recentchanges database table are being removed. rc_new and rc_type are being removed in favor of rc_source. Queries to these older fields will start to fail starting this week and developers should use rc_source instead. These older fields were deprecated over 10 years ago and should not be in use. This is part of work to improve the performance and stability of queries to the recentchanges table. [24]
The latest quarterly Language and Internationalization Newsletter is now available. This edition includes: support for new languages in MediaWiki and translatewiki; the start of the Language Onboarding and Development project to help support the growth of new and small wikis; updates on research projects; and more.
Meetings and events
The next Language Community Meeting is happening soon, August 29th at 15:00 UTC. This week's meeting will cover: the Avro keyboard developers from Wikimedia Bangladesh, who were recently awarded a national award for their contributions to this keyboard; and other topics.
Latest comment: 2 days ago6 comments3 people in discussion
I don't know if this is the right place to ask this question, but I was sent here. I know there's a way to do it via the user CSS page, but I don't know how. There isn't really a guide or tutorial (as far as I can see) from the Preferences page. I'm not trying to make a new skin, or make changes to the default skin itself, I just want to configure/customize how it looks personally; I just want to make the default Dark Mode as dark as the gadget version, and also make some color changes. CheckNineEight (talk) 01:59, 26 August 2025 (UTC)Reply
It doesn't tell me how to actually customize skin appearance, it just tells me that a CSS subpage is a thing that I can do – which I already know about. The Main page for that link is almost close enough for providing samples, though; still, doesn't really give me a good grasp of how this works, doesn't give me confidence of doing what I intend to do – which is to customize the look of Dark Mode. CheckNineEight (talk) 02:44, 28 August 2025 (UTC)Reply
"easily import a default skin's entire CSS code" No, Wikipedia's CSS is pretty complicated, stretches hundreds of lines and even differs for almost every single page of the site. This is also why it isn't further explained. People who know how CSS works should be capable to change it already, for those who don't it mostly boils down to "you are going to have to learn or copy from someone else (if that person exists)". If you just want to change colors, you should be able to get the list of CSS variables from your browser's web inspector (they are all on the html element, as they are for most websites in the world) and be able to change them as you see fit via you common.css. —TheDJ (talk • contribs) 08:19, 28 August 2025 (UTC)Reply
Latest comment: 3 days ago5 comments2 people in discussion
Template:WikiProject status is confusing people. They usually see this at the top of a WikiProject's main page (e.g., Wikipedia:WikiProject Biography). If they want to leave a note for the WikiProject, they click the bolded link to Wikipedia:WikiProject (not what they want), and then to the talk page (which is WT:COUNCIL and definitely not what they want).
Latest comment: 4 days ago4 comments4 people in discussion
Wikipedia previously had one of the best fuzzy search engines on the Web. Lately, it seems to be getting dumber and dumber. Today I searched for "Former NPR host Hansen," and it gave me every entry containing "NPR," EXCEPT "Liane," which is the correct answer. It even gave me pages containing "Liane Hansen" in both text and hypertext link, but didn't return the actual "Liane Hansen" page. This is TERRIBLE performance from what was previously one of the best search engines around. What was done to dumb down the search engine? Gil gosseyn (talk) 22:28, 26 August 2025 (UTC)Reply
YMMV, but I always go to Google and type "wiki xxx", where xxx is the thing I want. "wiki Former NPR host Hansen" takes me to the right page. For all of the complaints about Google that I hear, it still works great for me. In my 12 years of active editing, I have never had good luck with the Wikipedia search page when doing plain-text searches; it can give a lot of results, but they are never sorted by relevance. – Jonesey95 (talk) 22:45, 26 August 2025 (UTC)Reply
mw:Help:Searching says "The results will only include pages that contain all the words in your search.", and has done since at least 2013. The word "Former" doesn't appear anywhere in the text of that article (ignoring the templates), so it is working as expected. It is possible to make a "fuzzy" search (details in mw:Help:CirrusSearch#Words, phrases, and modifiers) but that isn't the default. If we search for NPR host Hansen that gives the expected results. I hope that info helps. Quiddity (WMF) (talk) 22:52, 26 August 2025 (UTC)Reply
@Gil gosseyn: The navbox is deliberately ignored because it has the class autocollapse. That's usually good to eliminate irrelevant hits. Here the occurrence of "former" in the navbox was indeed irrelevant to her being a former NPR host but Google picked up the random hit on the word so it gave the right result for the wrong reason. It's an odd word to include in the search. The article is the first hit on NPR host Hansen. PrimeHunter (talk) 07:51, 27 August 2025 (UTC)Reply
The css file doesnt work and I dont know how to get it to work, Ive tried adding an extra comma but that did nothing (link to the revision[25]). I swear i hit publish on it three seperate times but my contributions history says i only did it once. regardless,I used the 2008 section of the wiki contraversies article and Depictions of Muhammad to check and all three times the images still showed, before i added and after.if anyone has any advice please do pitch in, thank you! AssanEcho (talk) 18:05, 27 August 2025 (UTC)Reply
That CSS examples page uses a pretty brittle method in that it targets the specific image names. Someone needs to update it for the images that are presently on the page.
Example: One of the lines in the CSS is a[href="/wiki/File:Muammad-as-youth-meeting-monk-bahira-compendium-persia-1315-edin-550.jpg"],. The file has been renamed such that this rule doesn't match any longer (a[href="/wiki/File:Young_Muhammad_meets_the_monk_Bahira_-_from_Jami'_al-Tawarikh.jpg"], would now match what I believe to be the same image).
An alternative would be to use the |class= that images have to add something like |class=image-of-muhammad on that page and then target that. It would be marginally less brittle. Izno (talk) 18:09, 27 August 2025 (UTC)Reply
perhaps that should just be whats added instead of the current method even if (im guessing) it results in the more tame images (eg, depictions with a veil) being censored too.
also, general wiki policy dectates an editor shouldnt edit a talkpage post beyond minor grammar corrections soon after originally posting but i copied and pasted by accident an older version of this post from notepadd and left out a sentance, could i readded even though its a bit against guidlines, it doesnt add anything which would require you change your post AssanEcho (talk) 18:16, 27 August 2025 (UTC)Reply
Latest comment: 2 days ago5 comments5 people in discussion
The dark mode in Wikipedia settings makes the transparent background of equations black but leaves the equation itself a black and unreadable. There's a tiny difference in the shade so you can technically read it if you turn your brightness way up or strain your eyes really hard, but that defeats the point of dark mode so it should really just make the equations the same color as text. NNNNNNNN (talk) 02:28, 28 August 2025 (UTC)Reply
NNNNNNNN, Johnjbarton makes a good point: when reporting a bug of something you see somewhere, make sure you say exactly where you are seeing it so others can try to help diagnose a cause. There are at least five different ways of creating equations I can think of off the top of my head, each of which has different tricks and traps, and traps when editors use tricks to overcome other traps. DMacks (talk) 02:55, 28 August 2025 (UTC)Reply
When it comes to "dark mode", it's also worth specifying whether it's the Vector 2022 dark mode or the Gadget dark mode. Anomie⚔13:04, 28 August 2025 (UTC)Reply
Latest comment: 1 day ago16 comments11 people in discussion
Outline of Sen̓áḵw (red), in the Kitsilano neighbourhood of Vancouver.
The {{Maplink}} on the right is an exact copy of the one used on Sen̓áḵw. Despite working perfectly fine last time I checked a few weeks ago, |id=Q116290876 no longer automatically navigates to, and displays, the boundary defined by Q116290876. No meaningful changes have been made to the Wikidata entry, nor the OpenStreetMap feature it's linked to.[3] Switching to the similar |id=Q17018530 also doesn't work. I have no idea what happened here. — AFC Vixen 🦊 09:02, 28 August 2025 (UTC)Reply
I think the issue is related to the link between OpenStreetMap and Wikidata rather than Wikidata as such. I am using a module/template that shows rivers (based on OpenStreetMap) as well as their basin (based on Commons .map). Currently it is showing the basins, but not the rivers themselves (see https://sv.wikipedia.org/wiki/Indals%C3%A4lven for an example). Gunnar Larsson (talk) 17:19, 28 August 2025 (UTC)Reply
I have the same issue, all I see is a blank blue box. I'm using the latest version of Firefox and the only addon I have installed is an adblocker, which is disabled.
Testing in incognito mode in Firefox, and normally in Edge and Chrome, the issue also persists. It exists both logged out and logged in. Nebman227 (talk) 12:53, 28 August 2025 (UTC)Reply
Hmm. Works fine for me here both logged in and in incognito mode in Firefox 141, and while logged out in Chromium 139. Anomie⚔13:08, 28 August 2025 (UTC)Reply
I know they just joined one of the datacenters back, after upgrading it to newer version of Debian and Kartotherian. That might have something to do with it, and explain why some ppl have different results than others. —TheDJ (talk • contribs) 17:36, 28 August 2025 (UTC)Reply
Hi folks! I am working on https://phabricator.wikimedia.org/T381565 and yesterday I depooled the eqiad datacenter to test the new stack in codfw. I just repooled it, and now I see the map reported up above rendered correctly (same thing for the Kansas city neighborhoods. I am still a little puzzled why this happened, since we upgraded the postgres backend in codfw, kartotherian was upgraded months ago. LToscano (WMF) (talk) 13:02, 29 August 2025 (UTC)Reply
I'm getting blue and brown, but the other thing that's weird for me is that I'm not getting a map consistent between what's displayed currently and the MediaViewer version of it. Firefox 142 on Win10. Izno (talk) 18:05, 27 August 2025 (UTC)Reply
Latest comment: 1 day ago3 comments3 people in discussion
I have run into a named account with recent activity that appears to be a continuation of an IP account that did a handful of edits in 2019. Now I realize that I don't understand IP accounts - how they become "users", and what security exists on them since they do not have passwords. Presumably one would need to access WP with that same IP address to then take over the IP account and give it a username. I have seen this IP account: User_talk:159.224.181.7, which now (after 6 years of inactivity) has a username - Qrivas - which appears to be a synonym for the IP account.
This case may be completely legitimate and I do not want to cast aspersions on this user. I ask this because if it is possible to "hijack" IP accounts that seems to me to be a security issue for WP. I am presuming that it is possible to fake an IP address, but I don't know if that is true. Lamona (talk) 03:36, 29 August 2025 (UTC)Reply
There is no way (baring burying the entire edit and asking one of the two people with import upload access to re-import it, which would leave an audit trail a mile wide and definitely wasn't done here) to reassign edits from an IP address to a username. It's just not possible. That, of course, doesn't stop Qrivas from posting on 159.224.181.7 as if they were the same person as 159.224.181.7, since it's all just text and I could respond to talk page comments as if I were you in the same way. * Pppery *it has begun...03:40, 29 August 2025 (UTC)Reply
Yes, Qrivas simply made two edits to an IP talk page in 2019. That's all, and anyone can do it. It may or may not have been their IP address at the time. It's allowed to respond to a talk page post without being the associated IP or user. I sometimes do it myself. PrimeHunter (talk) 09:47, 29 August 2025 (UTC)Reply
Latest comment: 1 day ago5 comments4 people in discussion
I used some Python code to update my list of articles linking to example (here). That uses mw:API:Exturlusage. The result seems mostly correct but I noticed some pages do not contain "example", for example CLCN5 + PAK1 + PAK3 + PAK4 + PAK5 + PAK6. I cannot see any 'related changes' that would explain why the API thinks CLCN5 has an external link to example.com. Does anyone have a reasonable way of checking that API:Exturlusage does return the articles mentioned in this post? Any clues for why example.com is not present now? Johnuniq (talk) 05:54, 29 August 2025 (UTC)Reply
You can adjust your script to skip pages that do not have a direct link in the wikitext and include only those where the link is used directly, as this will save your time. – DreamRimmer■07:47, 29 August 2025 (UTC)Reply
"This is a step in the right direction" - User:Cremastra
"I think this is a good idea" - User:Danubeball
"Definitely agree - now is the time to innovate and try new things" - User:Chaotic Enby
"I agree with the above" - User:Sahaib
(In the interest of honesty, users like User:PerfectSoundWhatever and User:Rosguill are skeptical.)
However, none of us are apparently adept enough at technical skills to create a proper mockup of the idea. Can someone help me create a proper template that can be used to illustrate this proposal and to implement it if it ever gets to that stage?
Here's my non-dynamic, hardcoded mockup. The new mockup must have a) parameters for the linked article, intro paragraph, and lead image, b) be formatted similarly to other main page templates. Once we get that down, we can create a mock queue system to demonstrate the idea to Wikipedia:Village pump (policy).
Latest comment: 1 day ago2 comments2 people in discussion
Got this idea after taking a look at WP:AISIGNS and seeing that more than 2000 links have a UTM source=chatgpt parameter.
If we blacklist utm source, it may help prevent the addition of some AI generated content by spambots and the like.
Lightly tested regex: .*(\?|\&)utm_source=.*
We can do an abuse filter if needed as well if we want to be less WP:BITEy. There isn't a legitimate reason to have utm_source in links. Affiliate marketers often use utm_source and similar tracking IDs to ensure who gets last click attribution for sales and advertising, and that is not something we want to encourage on Wikimedia projects. There already are some tracking URLs blocked such as bing (dot) com (slash) ck and youtube (dot) com (slash) url, those are on the global spam blacklist as they are just one of the ways spammers bypass our filters.
We can maybe even give a separate message for those with utm_source= some AI chatbot like Copilot or ChatGPT or Gemini that shows that we are almost certain that an LLM was used. Aasim (話す) 22:21, 29 August 2025 (UTC)Reply
Latest comment: 2 hours ago3 comments2 people in discussion
Let's say I partially block a user from a page, and the page gets deleted. Is the user still blocked from editing the page (i.e. can't create it), or does the deletion end the relevant action, comparable to how it ends a protection? Also, what if the page gets recreated by someone else: can the partially blocked user edit it? I just did a partial block on User:ThisIsaTest — the first I've ever done — and have no idea what would happen if I did the same thing to a real user. Nyttend (talk) 04:57, 31 August 2025 (UTC)Reply
The pblock remains on the books but has no effect unless the page is undeleted (and even then may not be effective). While a block appears in most of the UI to be preventing a specific title, it's actually technically implemented by preventing edits to a specific Page ID; this means pblocks survive moves but don't survive deletions. * Pppery *it has begun...05:15, 31 August 2025 (UTC)Reply
View all 46 community-submitted tasks that were resolved last week.
You are invited to join the discussion at meta:Module talk:Message box § c-Waddie96-20250823092200-Edit protected 2025-08-23. Relating to giving messageboxes/mbox's the 
Template authors can now use additional CSS properties, since the CSS sanitizer used by TemplateStyles was updated. For example: 
