Wikipedia:Village pump (WMF)/Archive 13
From Wikipedia, the free encyclopedia
This page contains discussions that have been archived from Village pump (WMF). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.
< Older discussions · Archives: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15
Wikimedia Foundation Bulletin 2025 Issue 21

Upcoming and current events and conversations
Let's Talk continues

- Wikimania 2027: Santiago, Chile is announced as the location for Wikimania 2027. The annual conference returns to Latin America after more than 10 years, following previous editions in Buenos Aires (2009) and Mexico City (2015).
- Wikidata recognized as a Digital Public Good: Wikidata became the second Wikimedia project to be officially recognized as a digital public good by the Digital Public Goods Alliance.
Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org
- Tech News: Read updates from Tech News week 44 and 45 including the community-submitted tasks that were resolved last week.
- Activity Tab: The Wikipedia Android app expands the new Activity tab to all users. It offers a complete view of your Wikipedia activity: reading time, saved articles, edits, and donation history (for known donors). This change aims to make Wikipedia a more engaging experience for readers and contributors alike, while keeping all personal data private and stored locally on your device.
- Tabbed browsing: Tabbed browsing is now available on the Wikipedia App for iOS. Tabs will let you keep more than one article open at a time, making it easier to explore complex topics, follow links without losing your place, and pick up where you left off.
- CampaignEvents extension: Autoconfirmed users on small and medium wikis with the CampaignEvents extension can now use Event Registration without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages.
- Image browsing: The Wikimedia Foundation launched image browsing, an experiment that puts images on top of your Wikipedia article reading journey, on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias.
- Temporary accounts: Temporary Accounts are now enabled on 1,000+ projects including English Wikipedia.
- Abstract Wikipedia naming contest: The first round of “abstract content wiki” naming vote has ended and the first legal review had begun to determine the 6 names that will make it to the second round on November 17.
- Wikifunctions: Wikifunctions is now deployed across 12 Wiktionaries and 4 Wikipedias.
Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · list of movement events

- Privacy in Wikipedia research: The Wikimedia Foundation published Privacy in Public: Navigating Research, Personal Data, and Safety on Wikipedia, a whitepaper which guides researchers in navigating privacy of Wikipedia editors in their research. Read the highlights and key takeaways for researchers and Wikipedians.
- Digital Safety: The Wikimedia Foundation is launching Digital Safety Office Hours to explore how to stay safe digitally, what does digital safety mean, what extra precautions can Wikimedians take. The first session will take place on November 28 at 9 AM and 7 PM UTC. Check out also our Digital Safety Resources Center to learn practical tips and tools you can use immediately.
- Volunteer roles for movement governance: The Movement governance committees are seeking new volunteers to support essential and high-impact work across the Wikimedia ecosystem. The current appointment cycle is open for the AffCom, Ombuds Commission, and Case Review Committee. Applications for these committees will remain open until December 11. The team will host a community conversation on November 26, at 3 AM UTC.
- Don't Blink: The latest developments from around the world about protecting the Wikimedia model, its people and its values.
- Wikimedia Core Curriculum: Want to learn how to edit Wikipedia? – A new free self-paced course, all in video with subtitles, is available from the Wikimedia Foundation!
Foundation statements
- Transparency builds trust: The latest edition from the series "Lessons from Wikipedia" explores how deep transparency has helped make Wikipedia one of the most trusted sources on the internet.
Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · The Wikipedia Library · Milestones · Wikidata · Central and Eastern Europe · other newsletters
Subscribe or unsubscribe · Help translate
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. Let askcac
wikimedia.org know if you have any feedback or suggestions for improvement!
MediaWiki message delivery 23:05, 12 November 2025 (UTC)
Donation cancelled due to annoying begging
Please see WP:VPM#Donation cancelled due to annoying begging. Fram (talk) 16:34, 14 November 2025 (UTC)
WP:TA, how's it going so far?
We've had it for a couple of weeks now, is there any interesting data etc that can be shared? Is the volume of TA/IP edits about the same, for example? Gråbergs Gråa Sång (talk) 09:59, 17 November 2025 (UTC)
Consider providing a donations link for logged in mobile users
On at least two two occasions a newbie editor with an account has asked how to donate from a mobile device. It is not at all obvious. I suggest putting a Donations link in the hamburger menu (☰), perhaps without the animated gif that logged out users get.
I haven't looked, but if this is already in Phabricator, please provide the link :-). Commander Keane (talk) 02:07, 18 November 2025 (UTC)
- Hi @Commander Keane,
- Just to let you know I have seen this and am looking into finding an answer for you. Best, JBrungs (WMF) (talk) 06:57, 18 November 2025 (UTC)
- @Commander Keane, I work on the fundraising team with @JBrungs (WMF): we can confirm that the default behavior on mobile is to hide the Donate link if the user is logged in. For logged-out readers, it’s in the hamburger menu as you describe. It sounds like we are missing an opportunity to make it easy for editors to give if they wish to. This is very helpful feedback, we will pass it to our colleagues in the Product & Tech team. SPatton (WMF) (talk) 21:30, 19 November 2025 (UTC)
WMF fundraising banner campaign - more updates on collaboration page
Hi all,
Just a quick update, that over at the English banner fundraising community collaboration page we have introduced more ideas for fundraising feature experimentst, such as:
- Abandoned cart experiment
- In App donation reminder experiment
- Donor badge experiment
- Donor banner experiment
If you are interested in any of those, or just a general update on how our fundraising collaboration is going, head to the page and have a look. Best, JBrungs (WMF) (talk) 13:40, 18 November 2025 (UTC)
Wikimedia Foundation Bulletin 2025 Issue 22

Upcoming and current events and conversations
Let's Talk continues

- Board election: The 2025 Wikimedia Foundation Board of Trustees vote has elected two new trustees, Bobby Shabangu (Bobbyshabangu) and Michał Buczyński (Aegis Maelstrom), who will be appointed at the next Board meeting in December 2025.
- Wikipedia 25: Wikipedia is turning 25 and it’s time to party! Register now for Wikipedia’s 25th virtual birthday bash on 15 January at 16:00 UTC.
- Wikimedia Hackathon: The 2026 Wikimedia Hackathon will be taking place in person May 1 - 3, 2026 in Milan, Italy. Scholarship applications are open until November 28.
- Language Community: The next language community meeting will be held on November 28 at 16:00 UTC.
Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org
- Tech News: Some of the latest updates from Tech News week 46 and 47: Wikimedia Foundation is experimentating with reading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later; One new wiki has been created: a Wikisource in Minangkabau.
- Wikifunctions: The second round of voting for naming the wiki with abstract content is kicking off with six name proposals to vote for.
- Reference check: The A/B test for reference check has begun on English Wikipedia and will run until December 17. This is a feature which prompts new editors to add citations before they publish an edit adding content to an article.
- Image browsing: Wikimedia Foundation is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, is taking place on on Arabic, Chinese, English, French, Indonesian, and Vietnamese wikis, affecting a small number of users.
- CampaignEvents extension: Campaign events extension is now available on all Wikimedia wikis. The extension offers tools for running and coordinating events and other on-wiki collaborations. These features include Event Registration, Collaboration List, and Invitation List, plus a new feature, Collaborative contribution, which helps organizers and participants see the impact of their collaborative activities. Join the upcoming learning session to see the new feature in action and share your feedback.
- Dark Mode: Dark mode is now available on all Wikimedia projects for all anonymous users! This enhancement aims to deliver a more enjoyable reading experience, especially in dimly lit environments. Learn how to activate this feature.
- Wikimedia Apps: The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging.
- Usability Improvements: Improvements for talk pages is being rolled out. Users can opt out of these changes in their user preferences in “Show discussion activity.”
Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · list of movement events
- Wikipedia 25 Press toolkit: Wikimedia Foundation is providing press toolkit as guidance and resources to Wikimedia volunteers and affiliates to spread the word about Wikipedia’s 25th birthday to local and regional media.
- Language and Internationalization: Read some key highlights from the October 2025 edition of the Language and internationalization newsletter.
- Information integrity: Wikimedia Project from South America Selected by the UNESCO Global Initiative for Information Integrity on Climate Change Fund.
- The Wikipedia Library: The Wikipedia Library team attended the CEE Meeting 2025 celebrated a new partnership with Times of Malta.
- Understanding movement organizers: Wikimedia Foundation concluded a literature review on organizers in the Wikimedia movement focused on capturing their personas, motivations, and impact in order to highlight best practices and opportunities for further support.
Annual Goals Progress on Effectiveness
See also: Progress on the annual plan
- Wikimedia Enterprise: Reef Media uses Wikimedia Enterprise Snapshot API to Fact Check and Verify Sources.
Board and Board committee updates
See Wikimedia Foundation Board noticeboard · Affiliations Committee Newsletter
- Affiliations Committee: Draft recommendations on three strategic areas that need continuous consideration to best support Wikimedia affiliates.
Foundation statements
- Lessons from Wikipedia: The latest edition from the series explores the art of disagreement and how Wikipedia navigates disputes.
- Artificial Intelligence: In the AI era, Wikipedia has never been more valuable. This explainer shows how human-created knowledge isn’t replaceable.
Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · The Wikipedia Library · Milestones · Wikidata · Central and Eastern Europe · other newsletters
Subscribe or unsubscribe · Help translate
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. Let askcac
wikimedia.org know if you have any feedback or suggestions for improvement!
MediaWiki message delivery 17:30, 25 November 2025 (UTC)
Temporary accounts: Post deployment
After deployment
Now deployed! ~2025-31082-27 (talk) 08:15, 4 November 2025 (UTC)
- This appears to have been our last ever IP edit: Special:Diff/1320371783
- (I'm the same person as the previous message, but I closed my incognito tab between that message and this one. When I tried to post this in my new incognito tab, I saw the message "Visitors to Wikipedia using your IP address have created 1 accounts in the last 24 hours, which is the maximum allowed in this time period. As a result, visitors using this IP address cannot create any more accounts at the moment." Isn't the limit meant to be 6 accounts per 24 hour period?) ~2025-30907-85 (talk) 08:26, 4 November 2025 (UTC)
- I believe there's a rate limit of one every ten minutes. (Testing ping to ~2025-30907-85, hope this works) Perfect4th (talk) 08:29, 4 November 2025 (UTC)
- This appears to be a bug. We're looking into it. There is a limit of 1 every 10 minutes with a maximum of 6 temp account creations allowed every 24 hours. -- NKohli (WMF) (talk) 09:30, 4 November 2025 (UTC)
- This is now fixed via https://phabricator.wikimedia.org/T409161 KHarlan (WMF) (talk) 12:23, 4 November 2025 (UTC)
- Things like Wikipedia:Sockpuppet investigations/~2025-31011-02 and Wikipedia:Sockpuppet investigations/~2025-30821-77 show that many editors don't seem to be aware of temporary accounts being deployed. Should we send the mass-message to everyone? Children Will Listen (🐄 talk, 🫘 contribs) 13:09, 4 November 2025 (UTC)
- I threw up a message on MediaWiki:Recentchanges-summary. Sohom (talk) 13:18, 4 November 2025 (UTC)
- Yeah, I don't think I would have been aware either if I didn't watch some admin talk pages many years ago. In other issues, I'm interested to see how LTA behavior will change in response to this. For example, will Andrew5 start clearing his cookies or use throwaway accounts instead (as I personally believe he already has, but this isn't a place to discuss that in detail)? wizzito | say hello! 13:22, 4 November 2025 (UTC)
- Also want to clarify sth: IP ranges/addresses that are currently blocked are unable to create temporary accounts, correct? wizzito | say hello! 13:32, 4 November 2025 (UTC)
- They usually aren't, except if file an unblock request on their user talk page (but in this case they can only edit their user talk page and only as long as the option to block talk page access isn't enabled) -> phab:T398673. Johannnes89 (talk) 17:44, 4 November 2025 (UTC)
- Also want to clarify sth: IP ranges/addresses that are currently blocked are unable to create temporary accounts, correct? wizzito | say hello! 13:32, 4 November 2025 (UTC)
- Special:IPContributions/122.171.23.189 is exactly what I was concerned about way above. Never made it to AIV because it was three different accounts so they never got warned enough. ScottishFinnishRadish (talk) 15:28, 4 November 2025 (UTC)
- Also worth noting this was the first temporary account I looked at. Bodes well for how this will work in practice. ScottishFinnishRadish (talk) 15:36, 4 November 2025 (UTC)
- This also adds significantly more time than I originally estimated. As a for instance, you need another page load to go from the temporary user IP contribution page to the IP contribution page if you want to use twinkle to place a block. ScottishFinnishRadish (talk) 16:33, 4 November 2025 (UTC)
- That sounds like a description of a feature request to the Twinkle developers. RoySmith (talk) 16:41, 4 November 2025 (UTC)
- Sounds like something that probably should have been addressed before a major rollout. This isn't a minimum viable product situation, this is the production environment on one of the top 10 visited websites in the world, and this seriously affects anti-abuse efforts which are entirely undertaken by volunteers. ScottishFinnishRadish (talk) 16:45, 4 November 2025 (UTC)
- Doesn't blocking a TA autoblock the IP address? SuperPianoMan9167 (talk) 16:46, 4 November 2025 (UTC)
- WP:AUTOBLOCK:
There is an internal autoblock expiry time variable, which is set to 24 hours, meaning that autoblocks that are automatically applied will only last for that amount of time and will expire afterwards.
That's just another issue, you have to look at the IP to see the history of editing to determine how long a block should be. It essentially adds a "check the IP" step to every temporary account block, which then adds an additional "Legacy IP edits" step to see the history from the IP, as the IP editing history is on a different page than the IP editing history since temporary accounts were created. Luckily this task only has to be completed ~10,000 times a month, so adding 30 seconds to a minute only adds 80-160 hours of volunteer burden a month. ScottishFinnishRadish (talk) 16:52, 4 November 2025 (UTC)- Why do you need to do that? When you encounter a vandalizing account you also don’t perform CU to check if there are other sockpuppets. Just block the TA indefinitely like any regular vandal account and only care about their IP / IP range if you observe a pattern of abusive behavior with multiple TA. Johannnes89 (talk) 16:55, 4 November 2025 (UTC)
- The vast majority of reports at AIV were IPs. I look at the history of each to determine the correct block length. The point is to prevent disruption, not to allow someone to vandalize until they are blocked (assuming they're not changing their temporary account to avoid scrutiny and never get blocked) every 24 hours. ScottishFinnishRadish (talk) 17:09, 4 November 2025 (UTC)
- You should treat vandalizing TA the same way as vandalizing accounts. If you would issue an indefinite block for a regular account, do the same with the TA. There's no point looking up the IP unless you suspect long-term abuse. Just as we rely on autoblock when it comes to blocking regular vandal accounts, autoblock is also sufficient in most cases when it comes to TA vandals.
- To put things in perspective, some stats from other large wikis on IP reveal usage in the last 24 hours, based on Special:Log/checkuser-temporary-account:
- ~20x on plwiki
- ~90x on zhwiki
- ~100x on jawiki
- ~150x on dewiki
- ~170x on itwiki
- ~330x on frwiki (but ~200 of those from a single non-admin patroller who seems to use IP reveal much more often than anyone else on any project I've seen so far)
- Those numbers used to be higher when TA got introduced on each project but after some time people realized that they need to look up the IP less often than we thought in the pre-TA time. Johannnes89 (talk) 18:07, 4 November 2025 (UTC)
You should treat vandalizing TA the same way as vandalizing accounts. If you would issue an indefinite block for a regular account, do the same with the TA. There's no point looking up the IP unless you suspect long-term abuse.
That's entirely incorrect. If we're trying to prevent disruption then checking the editing history of the IP is a must. That log is also very inaccurate, I just checked the IPContributions page, revealing the temp accounts, of half a dozen IPs and it logged a single action. As I said, literally the first TA I looked at today was abusing the ability to reset their account to commit personally targeted bigoted vandalism. They had far surpassed the point where they would have been at AIV, but due to the way temp accounts work, they hadn't been reported. ScottishFinnishRadish (talk) 18:42, 4 November 2025 (UTC)- Entirely incorrect? That's precisely what Wikipedia:Temporary accounts#Impact for administrators says and matches my experience dealing with TA for almost half a year on my home wiki.
- There's simply no need to check the IP for every TA just to make sure they haven't been operating other TA's on the past – based on your way of thinking you would also run CU on every vandalizing account just to make sure they haven't used other vandal accounts?
- I would be curious to see which TA you are talking about (we could also continue discussing the specific example offwiki). Personally targeted bigoted vandalism that sounds to me like a something people could report no matter how many times the TA vandalized. Blocking one TA would have stopped the vandal due to autoblock – no matter how many other TA they created (blocking old TA once the vandal has moved on already is also not needed by the way, they can't re-used old TA once they abandoned them). Johannnes89 (talk) 19:01, 4 November 2025 (UTC)
- Entirely incorrect? That's precisely what Wikipedia:Temporary accounts#Impact for administrators says and matches my experience dealing with TA for almost half a year on my home wiki.
- You should treat vandalizing TA the same way as vandalizing accounts. If you would issue an indefinite block for a regular account, do the same with the TA. There's no point looking up the IP unless you suspect long-term abuse. Just as we rely on autoblock when it comes to blocking regular vandal accounts, autoblock is also sufficient in most cases when it comes to TA vandals.
- The vast majority of reports at AIV were IPs. I look at the history of each to determine the correct block length. The point is to prevent disruption, not to allow someone to vandalize until they are blocked (assuming they're not changing their temporary account to avoid scrutiny and never get blocked) every 24 hours. ScottishFinnishRadish (talk) 17:09, 4 November 2025 (UTC)
- Why do you need to do that? When you encounter a vandalizing account you also don’t perform CU to check if there are other sockpuppets. Just block the TA indefinitely like any regular vandal account and only care about their IP / IP range if you observe a pattern of abusive behavior with multiple TA. Johannnes89 (talk) 16:55, 4 November 2025 (UTC)
- WP:AUTOBLOCK:
- Doesn't blocking a TA autoblock the IP address? SuperPianoMan9167 (talk) 16:46, 4 November 2025 (UTC)
- Sounds like something that probably should have been addressed before a major rollout. This isn't a minimum viable product situation, this is the production environment on one of the top 10 visited websites in the world, and this seriously affects anti-abuse efforts which are entirely undertaken by volunteers. ScottishFinnishRadish (talk) 16:45, 4 November 2025 (UTC)
- That sounds like a description of a feature request to the Twinkle developers. RoySmith (talk) 16:41, 4 November 2025 (UTC)
- This also adds significantly more time than I originally estimated. As a for instance, you need another page load to go from the temporary user IP contribution page to the IP contribution page if you want to use twinkle to place a block. ScottishFinnishRadish (talk) 16:33, 4 November 2025 (UTC)
- Also worth noting this was the first temporary account I looked at. Bodes well for how this will work in practice. ScottishFinnishRadish (talk) 15:36, 4 November 2025 (UTC)
- Is anyone else getting a weird bug of usernames getting cut across the linebreak in mobile watchlist view? I suspect it might be an issue only for admins and/or editors with temporary account viewer permissions? signed, Rosguill talk 15:46, 4 November 2025 (UTC)
- Yes, I've spotted that today as well. Andrew Gray (talk) 17:47, 4 November 2025 (UTC)
- @Rosguill @Andrew Gray can you share more details and a screenshot please? We can investigate the issue. -- NKohli (WMF) (talk) 08:08, 7 November 2025 (UTC)
- NKohli (WMF) see File:Wikipedia watchlist bug report 11-7-25 1.png and File:Wikipedia watchlist bug report 11-7-25 2.png. These screenshots were taken on an iPhone 13 running iOS 18.6.2 signed, Rosguill talk 16:38, 7 November 2025 (UTC)
- @NKohli (WMF) File:Screenshot 20251108-105844.png is the same issue on Android 16/Chrome 142 in (mobile) Vector 22. There's also an odd extra line-break on the later ones. Andrew Gray (talk) 11:04, 8 November 2025 (UTC)
- Thank you @Andrew Gray and @Rosguill. I have reported it on phab and tagged the Readers' team who would know what's going on. -- NKohli (WMF) (talk) 14:29, 11 November 2025 (UTC)
- @NKohli (WMF) File:Screenshot 20251108-105844.png is the same issue on Android 16/Chrome 142 in (mobile) Vector 22. There's also an odd extra line-break on the later ones. Andrew Gray (talk) 11:04, 8 November 2025 (UTC)
- NKohli (WMF) see File:Wikipedia watchlist bug report 11-7-25 1.png and File:Wikipedia watchlist bug report 11-7-25 2.png. These screenshots were taken on an iPhone 13 running iOS 18.6.2 signed, Rosguill talk 16:38, 7 November 2025 (UTC)
- @Rosguill @Andrew Gray can you share more details and a screenshot please? We can investigate the issue. -- NKohli (WMF) (talk) 08:08, 7 November 2025 (UTC)
- Yes, I've spotted that today as well. Andrew Gray (talk) 17:47, 4 November 2025 (UTC)
- Is there really no way to see ips short of tracking down the edit on recentchanges or the watchlist? Nothing in history or diffs or Special:Contributions (for the temp account - though at least on that, I get the ipinformation collapsed box, with everything except the ip itself), and even turning on autoreveal doesn't do anything. —Cryptic 17:18, 4 November 2025 (UTC)
- @Cryptic Show IP is displayed for me in page histories, user contributions, and in diffs. Sam Walton (talk) 17:22, 4 November 2025 (UTC)
Way up above, I was one of several people to express concerns about the fact that IP addresses are only stored for ninety days. I just found and reverted some fairly severe vandalism from May last year; if temporary accounts had been used then, that edit would've been even harder to track down without going to the article in question and checking the page history. Here's what happened; today I came across an IP address on my watchlist that turned out to be part of a problematic school IP range, 168.212.0.0/16. I noticed that the range had been blocked several times. I know many people wouldn't go to the lengths of doing this, but I audited all edits from that range since the expiry of the last block in April 2024, which is how I found that vandalism among other things that escaped the three-month window. I messaged the admin who had previously blocked the range and he re-blocked it. These sorts of problems are why I think that with temporary accounts the way they are now, we should be more severe with blocks of school IP addresses, because by default they'll be firehoses of vandalism. Feel free to move this message if it'd be more suitable somewhere else. Graham87 (talk) 15:19, 8 November 2025 (UTC)
- And some of our worst IP hopping vandals, including this one, are just blasting right through temporary accounts; I hoped this rollout would help stop some of these people, given that cookies are connected to accounts now, but oh well... wizzito | say hello! 23:55, 11 November 2025 (UTC)
- One thing we should have done was made people unable to log out of temporary accounts unless they forced it themselves (e.g. clearing browser cookies). This would have probably stopped some vandalism. wizzito | say hello! 00:07, 12 November 2025 (UTC)
- You can log out of a temporary account??? CMD (talk) 02:25, 12 November 2025 (UTC)
- It looks like you can by going to Special:UserLogout RoySmith (talk) 02:32, 12 November 2025 (UTC)
- Another fun fact: it looks like a TA gets created when you try to make an edit, even if it fails. In my case, I opened an incognito window, tried to edit WP:Sandbox and hit an edit conflict. Ended up creating a TA with zero contributions and zero log entries. RoySmith (talk) 02:50, 12 November 2025 (UTC)
- We need to create a temp account for anything that can generate a log entry. On the positive side, perhaps this will be more useful as a signal when examining a temporary account (e.g. for https://phabricator.wikimedia.org/T409396) KHarlan (WMF) (talk) 07:13, 12 November 2025 (UTC)
- Another fun fact: it looks like a TA gets created when you try to make an edit, even if it fails. In my case, I opened an incognito window, tried to edit WP:Sandbox and hit an edit conflict. Ended up creating a TA with zero contributions and zero log entries. RoySmith (talk) 02:50, 12 November 2025 (UTC)
- Yeah, there's an "Exit Session" link in the top right corner. This is top level in Vector 2010 and in a menu in Vector 2022. –Novem Linguae (talk) 14:33, 12 November 2025 (UTC)
- It looks like you can by going to Special:UserLogout RoySmith (talk) 02:32, 12 November 2025 (UTC)
- You can log out of a temporary account??? CMD (talk) 02:25, 12 November 2025 (UTC)
- The link shows 15 edits, with 14 of them by one account and 1 edit by another account. Are there other accounts associated with this vandal? For vandals who change IPs, is the activity you've linked to similar to what one would have seen with legacy IP edits, the difference being that the activity is partially obscured because there are two different accounts externally visible, rather than a single IPv6 /64 range? KHarlan (WMF) (talk) 07:18, 12 November 2025 (UTC)
- KHarlan (WMF), there are 3 TAs on that range, not 2. 45dogs (they/them) (talk page) 07:29, 12 November 2025 (UTC)
- You are right, sorry about that. Yes, the first edited over the course of ~60 minutes, then a second account edited once ~90 minutes after the first one stopped editing, and a third one created 11 minutes after the second one. KHarlan (WMF) (talk) 07:33, 12 November 2025 (UTC)
- KHarlan (WMF) The thing is: the first TA was blocked a minute after that 60 minute period. Another account showed up about 2 hours after that and kept on editing, presumably because the user was able to switch to another device or simply... log out? wizzito | say hello! 09:58, 14 November 2025 (UTC)
- The former solution would have been to block the /64 from the beginning, which would have prevented the edits from 20:09 - 20:56 from being made. wizzito | say hello! 09:59, 14 November 2025 (UTC)
- Or even block the IP in general, since only one IP on the /64 was used for all 15 edits. Given how IPv6 works, it suggests to me like the vandal just logged out to avoid scrutiny instead of switching devices. wizzito | say hello! 10:02, 14 November 2025 (UTC)
- The former solution would have been to block the /64 from the beginning, which would have prevented the edits from 20:09 - 20:56 from being made. wizzito | say hello! 09:59, 14 November 2025 (UTC)
- KHarlan (WMF) The thing is: the first TA was blocked a minute after that 60 minute period. Another account showed up about 2 hours after that and kept on editing, presumably because the user was able to switch to another device or simply... log out? wizzito | say hello! 09:58, 14 November 2025 (UTC)
- You are right, sorry about that. Yes, the first edited over the course of ~60 minutes, then a second account edited once ~90 minutes after the first one stopped editing, and a third one created 11 minutes after the second one. KHarlan (WMF) (talk) 07:33, 12 November 2025 (UTC)
- KHarlan (WMF), there are 3 TAs on that range, not 2. 45dogs (they/them) (talk page) 07:29, 12 November 2025 (UTC)
- One thing we should have done was made people unable to log out of temporary accounts unless they forced it themselves (e.g. clearing browser cookies). This would have probably stopped some vandalism. wizzito | say hello! 00:07, 12 November 2025 (UTC)
Twinkle and Special:Block aside
As an aside, long-term I think we will want to move away from using Twinkle for blocks and have everyone use Special:Block. I wrote the Twinkle block module 10 years ago as a way to block and issue a talk page template at the same time. That was the extent of it. Over the past decade, we've painfully been trying to maintain feature parity with Core. Now we're at a point where it's the opposite, and Core is missing functionality that's in Twinkle (phab:T392857). It will still be a "while", but the plan is to continue on with that effort and eventually there will be no need for Twinkle at all.
I guess just keep this in mind. Anything that you think Twinkle does better, please file a task or let me know, and we'll get it tracked. Ultimately I hope that, apart from browsing contributions or checking talk pages, admins will never need to leave Special:Block to do their job. — MusikAnimal talk 19:01, 4 November 2025 (UTC)
- Twinkle's present killer feature are prefills and templates. It's also convenient that it's a dialog rather than a whole separate page. Izno (talk) 19:09, 4 November 2025 (UTC)
- The dialog is the big thing. I'd rather never open special:block and take action from a dialog on the contribs page. ScottishFinnishRadish (talk) 19:14, 4 November 2025 (UTC)
- +1 KevinL (aka L235 · t · c) 19:18, 4 November 2025 (UTC)
- This is one of those things that happens 10,000+ times a month, so seconds add up to hours pretty quick. From the contribs page, it takes about 3-5 seconds to block through twinkle, including selecting the reason filling out the template. Just having to click and load Special:Block would double that time, and that's without filling things out, and then placing the template. ScottishFinnishRadish (talk) 19:25, 4 November 2025 (UTC)
- A dialog is great, but it can't give you all the information you need with such limited space. For example, Twinkle only reports if there was any past block and gives only one set of details (and even then there are bugs!). I suspect most of us want to see the full log if there were any previous blocks. Special:Block does this, and likewise for any active range blocks.
- The templates, prefills etc. are part of phab:T392857. That would indeed be a requirement if we were ever to retire Twinkle. Fortunately virtually ever wiki has this or a similar workflow, so it seems it's time to bring it to Core! :) Once we have that, I suspect you'll find Special:Block just as convenient as it will be designed as a "one-stop shop" for all things blocking. Heck, we could even throw in the contributions there in another accordion.
- Anyway, fret not, as this is a long ways away. We'd need design and user research, a full product treatment, etc. Besides, Twinkle is a gadget which we as a community are free to continue to use and maintain. I just don't know if I will be able to maintain it, is all! The multiblocks project was a massive effort. I didn't have it in me to parity that in Twinkle. Especially after hearing the affirmation from @Novem Linguae, I figure engineering resources are better spent on Special:Block so that all wikis get the same benefits. — MusikAnimal talk 03:11, 5 November 2025 (UTC)
- This is one of those things that happens 10,000+ times a month, so seconds add up to hours pretty quick. From the contribs page, it takes about 3-5 seconds to block through twinkle, including selecting the reason filling out the template. Just having to click and load Special:Block would double that time, and that's without filling things out, and then placing the template. ScottishFinnishRadish (talk) 19:25, 4 November 2025 (UTC)
- Yes, I almost framed it as that big for me also. Special:Block isn't especially slow if it had the parity of prefill/template, but having to make the context switch Sucks. Izno (talk) 19:27, 4 November 2025 (UTC)
- +1 KevinL (aka L235 · t · c) 19:18, 4 November 2025 (UTC)
- Oh yeah, the other big feature: Twinkle drops a block notice on the talk page. Izno (talk) 00:15, 5 November 2025 (UTC)
- The dialog is the big thing. I'd rather never open special:block and take action from a dialog on the contribs page. ScottishFinnishRadish (talk) 19:14, 4 November 2025 (UTC)
- What Izno and SFR said, essentially. Unfortunately for you, the software you wrote is good as hell and everybody finds it more usable than the other thing... jp×g🗯️ 22:24, 4 November 2025 (UTC)
- Which is also software he wrote. Either way he's a winner! ScottishFinnishRadish (talk) 22:26, 4 November 2025 (UTC)
Another Twinkle feature for sending a message to IP users is (was) the Shared IP notice. One could use the WHOIS link to fill out the name of the owning org. I guess this feature is no longer meaningful. But if a shared IP is blocked, how would an editor from that IP be able to know this in advance? David Brooks (talk) 22:42, 4 November 2025 (UTC)
Distinguishing individual accounts
The very, very similar temp account names make it a lot harder to spot the same editor in e.g. recent changes (not always easy with IPs, but at least often a lot easier than it is now). I didn't spot the pattern of edits from here in recent changes, would probably have been easier before today. Fram (talk) 16:15, 4 November 2025 (UTC)
- This seems like a perfect opportunity for some add-on script which assigns colors to TA account names in the various listings. Perhaps as a hash of the account name, so they're stable across listings. I'm guessing it would be a no-brainer for somebody who is good at javascript. RoySmith (talk) 16:20, 4 November 2025 (UTC)
- Adding such a script to mw:Trust and Safety Product/Temporary Accounts/Repository might be valuable for other projects. There’s already a script for highlighting the last three digits of TA user names in order to make it easier to spot edits from the same TA. Johannnes89 (talk) 17:00, 4 November 2025 (UTC)
- I'll try to make that. Aaron Liu (talk) 17:07, 4 November 2025 (UTC)
- It looks like in both RecentChanges and RevisionHistory the TA accounts have class=mw-tempuserlink, so you can key off that. RoySmith (talk) 17:12, 4 November 2025 (UTC)
- Or, instead of colors, add an Identicon. RoySmith (talk) 17:26, 4 November 2025 (UTC)
- I don't think these are easy to distinguish at such small sizes. Aaron Liu (talk) 17:56, 4 November 2025 (UTC)
- Remember that a non-negligible number of people is colour-blind. Phil Bridger (talk) 11:16, 9 November 2025 (UTC)
- It's not like there's a requirement for only one script though. A person with normal color vision could use a color-based script, one with color blindness but good acuity could use an icon-based script, etc. Anomie⚔ 15:14, 9 November 2025 (UTC)
- I agree. I was trying to prompt those with more technical knowledge than I have to do even more work. Phil Bridger (talk) 15:55, 9 November 2025 (UTC)
- It's not like there's a requirement for only one script though. A person with normal color vision could use a color-based script, one with color blindness but good acuity could use an icon-based script, etc. Anomie⚔ 15:14, 9 November 2025 (UTC)
- Remember that a non-negligible number of people is colour-blind. Phil Bridger (talk) 11:16, 9 November 2025 (UTC)
- I don't think these are easy to distinguish at such small sizes. Aaron Liu (talk) 17:56, 4 November 2025 (UTC)
- Or, instead of colors, add an Identicon. RoySmith (talk) 17:26, 4 November 2025 (UTC)
- One lunch later: User:Aaron Liu/TemporaPaint.js currently would give a text color. Sometimes the differences are small, though, so I plan to later add an inverted background color (which should also help readability a little) and maybe use a different hash function. Aaron Liu (talk) 17:54, 4 November 2025 (UTC)
- Fixed color inversion. Aaron Liu (talk) 18:02, 4 November 2025 (UTC)
- Hmmm. Some of the color combinations don't work very well, making the underlying text impossible to read. RoySmith (talk) 22:45, 4 November 2025 (UTC)
- I made a simpler version with just CSS. It works at Special:RecentChanges even with Live Updates. It's keyed off the last digit, and all my color combinations have a contrast greater than 5.13: Special:Contribs/~2025-31439-70, Special:Contribs/~2025-31439-71, Special:Contribs/~2025-31439-72, Special:Contribs/~2025-31439-73, Special:Contribs/~2025-31439-74, Special:Contribs/~2025-31439-75, Special:Contribs/~2025-31439-76, Special:Contribs/~2025-31439-77, Special:Contribs/~2025-31439-78, Special:Contribs/~2025-31439-79. VectorWorld (talk) 13:57, 5 November 2025 (UTC)
- Hmmm. Some of the color combinations don't work very well, making the underlying text impossible to read. RoySmith (talk) 22:45, 4 November 2025 (UTC)
- I've made my own version, User:Seercat3160/ColourfulTemporaryAccounts, as a fork of yours. It has (in my opinion) better colours, and it works on pages that update (e.g. recent changes). I've made a comparison table on my documentation page, if anyone would like to take a look. Seercat3160 (talk) 10:40, 9 November 2025 (UTC)
- As one of the many colour-blinds :) I've created my own text-based version that gives the temp user a replacement human-readable username. It's deterministic so a user should always get given the same username each time they're seen (although there is a risk of collisions, such that two users might be given the same name, albeit quite unlikely.) User:JeffUK/VerboseTemporaryAccounts.js - Wikipedia JeffUK 09:41, 11 November 2025 (UTC)
- Very cool. I was actually considering writing this myself but you've done a better job at it than I could. I've added it to my comparison table for anyone interested. Seercat3160 (talk) 09:55, 11 November 2025 (UTC)
- @Seercat3160 You should add de:Benutzer:Aka/tempkontfett.js to your table. --Ahecht (TALK
PAGE) 18:10, 12 November 2025 (UTC)- @Ahecht: Done. Seercat3160 (talk) 21:57, 12 November 2025 (UTC)
- @Seercat3160 You should add de:Benutzer:Aka/tempkontfett.js to your table. --Ahecht (TALK
- Very cool. I was actually considering writing this myself but you've done a better job at it than I could. I've added it to my comparison table for anyone interested. Seercat3160 (talk) 09:55, 11 November 2025 (UTC)
- As one of the many colour-blinds :) I've created my own text-based version that gives the temp user a replacement human-readable username. It's deterministic so a user should always get given the same username each time they're seen (although there is a risk of collisions, such that two users might be given the same name, albeit quite unlikely.) User:JeffUK/VerboseTemporaryAccounts.js - Wikipedia JeffUK 09:41, 11 November 2025 (UTC)
- I created another CSS-only version (see User:isaacl/style/temporary-account-names) that inserts a bi-colour square next to temporary account names on history pages, and next to links to contributions from temporary accounts. It uses a very simplistic heuristic to detect links so it may produce false positives or negatives. (The implementation is subject to change as I gain more experience with it.) isaacl (talk) 04:24, 14 November 2025 (UTC)
- I added a mockup to the documentation page that roughly shows how it looks on signatures. isaacl (talk) 00:17, 15 November 2025 (UTC)
- Fixed color inversion. Aaron Liu (talk) 18:02, 4 November 2025 (UTC)
- It looks like in both RecentChanges and RevisionHistory the TA accounts have class=mw-tempuserlink, so you can key off that. RoySmith (talk) 17:12, 4 November 2025 (UTC)
- Yeah, I came back after a break to do a little recent changes patrolling and honestly thought someone had set a few thousands bots on us....!. There needs to be a 'Temporary User' notification somewhere on the Temp user pages, Contribution pages, and Talk pages, to make it abundantly clear that this is a temporary user User contributions for ~2025-32507-53 - Wikipedia, and that this is not. User contributions for -2025-40404-6O - Wikipedia. It should also be clear from the signature that the IP user is a temporary account, or I can easily see people getting very confused about who they're talking to, a load of temporary users with nearly identical names commenting on an article, for instance, is going to be very hard to parse; requiring a user script to be manually installed to patch this is not acceptable, this will confuse new (and returning, source:me) users who won't know they need to do that.. JeffUK 10:39, 10 November 2025 (UTC)
Autoblocks
Before temporary accounts were introduced, most IP blocks used to be anon. only, which means they don't affect registered users operating under that IP/range. However, if a temporary account gets blocked, it'll autoblock any registered user using the same IPs for 24 hours (unless the admin unchecks autoblock, which most aren't right now). I'm not sure if this'll cause significant problems, but I'm putting it out here so people can be aware. Children Will Listen (🐄 talk, 🫘 contribs) 04:44, 5 November 2025 (UTC)
Blocked from Draft namespace
Logged out editors can no longer create draft articles. See Wikipedia:Village pump (technical)#Page creation disabled in DRAFTspace for temp accounts?. --Ahecht (TALK
PAGE) 23:04, 5 November 2025 (UTC)
- a patch has been pushed in the recent backport window. temp accounts now should be able to create draft articles. – robertsky (talk) 08:18, 6 November 2025 (UTC)
Resolved
Active users jump
The Special:ActiveUsers count (NUMBEROFACTIVEUSERS) which appears on the Main Page has sharply jumped in the last few days, from around 115 thousand on November 3 to 140 thousand on November 7, because temporary accounts are now included, but IP addresses have not been listed. This number will probably fluctuate a lot in the future, because of how easy it is to create a new temporary account, so it could be more consistent with the magic word's previous behaviour to exclude them from the count. Xeroctic (talk) 08:35, 7 November 2025 (UTC)
- T339291: Should temp users be counted as registered & active users on Special:Statistics? is a related task. KHarlan (WMF) (talk) 08:38, 7 November 2025 (UTC)
- They also show at Special:ListUsers (also different from IP addresses), so they may need removing from that count/list as well. Xeroctic (talk) 13:57, 7 November 2025 (UTC)
- I used their appearance in the listusers page to help make the entry about them at Wikipedia:Wikipedia records. Temporary accounts have user ID numbers, etc., just like registered users. Graham87 (talk) 14:45, 8 November 2025 (UTC)
- They also show at Special:ListUsers (also different from IP addresses), so they may need removing from that count/list as well. Xeroctic (talk) 13:57, 7 November 2025 (UTC)
User page missing any identifier that accounts are temporary
For IP users it's quick and easy to tell that you're looking at an IP user, for temporary accounts they're indistinguishable from a normal account, unless you happen to know that a ~2 in the name means temporary. Requiring this special knowledge is a developer hack not a robust user-friendly solution. We need "Temporary User" in big letters on the Temporary Users' User Page, Talk Page, Contributions, and default signature, for this to even be remotely workable. JeffUK 10:44, 10 November 2025 (UTC)
- The user info card does show a different icon for temporary accounts compared to regular accounts. 45dogs (they/them) (talk page) 21:28, 10 November 2025 (UTC)
Thank you to Trust & Safety Product Team
@NKohli (WMF): I know some people hate temporary accounts and the rollout has had some hiccups (which isn't surprising for such a huge technical change), but personally I think this is a change for the better, both from a privacy and legal compliance perspective. Despite the roll-out bugs, I think this feature could easily have been a total disaster if the Trust & Safety Product Team had not spent the past six years carefully planning its implementation, along with all the supporting tools that were needed for mitigating its impact. This is probably the biggest technical change to Wikipedia in the past decade and despite some predictions otherwise, the sky is not yet falling. So I would like to say thank you to the Trust & Safety Product Team for your hard work and collaboration with the community to roll out this monumental change. That is all. Nosferattus (talk) 08:10, 12 November 2025 (UTC)
- TSP's (now PSI's) work on mw:Extension:SecurePoll has also been very helpful. They're a great team. –Novem Linguae (talk) 19:22, 12 November 2025 (UTC)
Assessment of an old time regular's experiment with TAs
I didn't want to write an alternative version but was invited here to share my experience. I will simply link the impression that I posted when deciding to stop using TAs for now. The outgoing IP address of the system in use is about to be changed, so I'll just share it now: . The title was humorous, not polemic. Thanks. ~2025-35304-53 (talk) 14:20, 27 November 2025 (UTC)
Replacing our CAPTCHA with a new bot detection service, part 2: editing
Hello again from the Wikimedia Foundation Product Safety and Integrity team. As you may remember, we've been integrating a new bot detection service, with the goal of replacing the current CAPTCHA with something that can hold up better against modern bots and other automated activity.
In our previous message about the hCaptcha account creation trial, we mentioned that we would expand this trial to include editing for higher-risk sessions. We are now ready to begin this next phase of the trial.
We are still running the account creation trial and collecting data, and we are seeing good initial results. Some bots are getting stopped from creating accounts, and humans rarely see a challenge at all. As expected, not all bots will get challenged either, and some can be subtle – but as the checkuser team recently shared, we've been able to use hCaptcha's data to help checkusers find and respond to those bots as well. We’ll share more about data from both account creation and editing after the trial concludes.
We'll now be taking the same approach to higher-risk editing. Here's how that will work:
- This will affect logged-out editors making their first edit, temporary account users, and non-autoconfirmed users. In other words, all sessions that don't have the skipcaptcha right.
- Like with account creation, this will work primarily invisibly. Most visitors (around 99.9%) will never see a challenge to solve at all.
- However, if an AbuseFilter that uses the showcaptcha consequence is triggered, this will always show an hCaptcha challenge to the user.
We will be enabling this on wikis which are already participating in the hCaptcha account creation trial, over the course of the next few weeks. First, we’ll deploy this week to idwiki, jawiki, and ptwiki. Shortly after, we’ll deploy to fawiki, zhwiki, and trwiki. Finally, we will deploy shortly after that to frwiki and enwiki.
To learn more, see our previous discussion here or the project page. As always, if you'd like to talk to us, comment here or find us on Discord. Thanks! EMill-WMF, KHarlan (WMF), SGrabarczuk (WMF) (talk) 14:33, 17 November 2025 (UTC)
- What happens to the people who have JavaScript disabled? Would they simply not be able to edit? Children Will Listen (🐄 talk, 🫘 contribs) 14:42, 17 November 2025 (UTC)
- This is a good question and I am curious to hear as well. In the interim, I'll point out that (a) the great majority of internet websites require JS for their captchas; (b) legitimate no-JS users are a vanishingly small slice of the internet use pie; and (c) under this current implementation we should be able to exempt legitimate no-JS users from hCaptcha upon request by giving them the "confirmed" user group (which comes with skipcaptcha), though I imagine that skipcaptcha might someday move out of confirmed to some higher group. Best, KevinL (aka L235 · t · c) 16:11, 17 November 2025 (UTC)
- In a sense there is, global CAPTCHA exemption, though that isn't local and is only assigned by stewards. Tenshi! (Talk page) 16:19, 17 November 2025 (UTC)
- @ChildrenWillListen sessions which do not have the skipcaptcha right, and do not have JavaScript enabled, will not be able to submit the wikitext form. (The same thing applies to Special:CreateAccount.) From our instrumentation, of sessions from users without skipcaptcha who successfully save edits with the wikitext editor, about ~0.6% of the sessions do not have JavaScript loaded at form submission time. Disallowing no JS edits from higher risk sessions (those without skipcaptcha) is one of the tradeoffs needed to be able to use hCaptcha for improved bot detection and mitigation in the editing path. KHarlan (WMF) (talk) 17:10, 17 November 2025 (UTC)
- This is a good question and I am curious to hear as well. In the interim, I'll point out that (a) the great majority of internet websites require JS for their captchas; (b) legitimate no-JS users are a vanishingly small slice of the internet use pie; and (c) under this current implementation we should be able to exempt legitimate no-JS users from hCaptcha upon request by giving them the "confirmed" user group (which comes with skipcaptcha), though I imagine that skipcaptcha might someday move out of confirmed to some higher group. Best, KevinL (aka L235 · t · c) 16:11, 17 November 2025 (UTC)
- Thanks for sharing this, all. As a CU, I've been impressed by what hCaptcha has helped us with even with just account creation, and I think enabling it on editing will add a lot of value. Best, KevinL (aka L235 · t · c) 16:01, 17 November 2025 (UTC)
- Here someone talked about age details in the hCaptcha TOS, do these indeed apply? Sjoerd de Bruin (talk) 19:17, 17 November 2025 (UTC)
- @Sjoerddebruin Thanks for flagging that comment. No, the use of hCaptcha isn't imposing any age requirements on our users. We always understood the age provisions in the ToS to apply specifically to their customers (like us) and not end users. But their one merged terms of service did have some imprecision in how they expressed that.
- I just replied to the comment there to say the same, and to point to hCaptcha's newly updated terms, which added a "if you are registering an account" qualifier to that clause, for avoidance of doubt. EMill-WMF (talk) 03:33, 18 November 2025 (UTC)
- Please humour me - I'm not up with all the latest technical details of web programming - but why would anyone today disable JavaScript? Phil Bridger (talk) 20:33, 17 November 2025 (UTC)
- Some privacy-minded folks, virus-paranoid folks, or folks that just don't like a bunch of layout thrashing use browser add-ons such as NoScript to disable all JavaScript. –Novem Linguae (talk) 22:22, 17 November 2025 (UTC)
- Wikipedia is significantly smoother, faster and less obnoxious when scripting is disabled! Almost every major browser vulnerability occurs via script. Johnuniq (talk) 00:09, 18 November 2025 (UTC)
- Some adherents to the free software movement (such as Richard Stallman) block/refuse to run nonfree, non-trivial JavaScript through extensions like LibreJS, while still allowing free or trivial JavaScript. This includes the nonfree, heavily obfuscated JavaScript used by hCaptcha. I am not aware of any instance up until this point where Wikipedia used nonfree JavaScript, other than possibly that time in 2019 when Wikimedia used Cloudflare to defend against a DDoS attack. OutsideNormality (talk) 02:10, 22 November 2025 (UTC)
- I just did a test with a spoofed browser configuration and the AbuseFilter "showcaptcha" mode, and apparently if hCaptcha thinks you are a bot, it will let you solve the CAPTCHA, but your edit will never submit no matter what you do, showing cryptic error messages. Pretty smart. Also, the text CAPTCHAs were different this time, asking questions like "What do we sit on at a desk?" (my question is: do these text CAPTCHAs support other languages?). OutsideNormality (talk) 20:45, 23 November 2025 (UTC)
- That doesn't sound like expected behavior. If you file a ticket with some details, we'd be happy to take a look into it. EMill-WMF (talk) 23:12, 23 November 2025 (UTC)
- @OutsideNormality thanks for flagging this issue. I filed T410863: hCaptcha: SiteKey mismatch error on "always challenge" workflow. To answer your question, yes, the text challenges are available in other languages. KHarlan (WMF) (talk) 09:46, 24 November 2025 (UTC)
- That doesn't sound like expected behavior. If you file a ticket with some details, we'd be happy to take a look into it. EMill-WMF (talk) 23:12, 23 November 2025 (UTC)
So what should a legitimate no-JS user do to edit Wikipedia now (except enabling JS)? Would requesting an account and confirmed/global CAPTCHA exemption rights with it be enough? sapphaline (talk) 13:18, 18 November 2025 (UTC)
- Btw, for some reason there's no "Request an account" link on the account creation page. sapphaline (talk) 13:20, 18 November 2025 (UTC)
- @SGrabarczuk (WMF): @KHarlan (WMF):? sapphaline (talk) 09:37, 19 November 2025 (UTC)
- Is there some urgency in your question requiring you to ping them within 24 hours? Sjoerd de Bruin (talk) 10:08, 19 November 2025 (UTC)
- @Sapphaline In the current configuration, users who have "skipcaptcha" right (autoconfirmed users, which is a fairly low bar to clear) can continue to edit without JavaScript. KHarlan (WMF) (talk) 22:00, 19 November 2025 (UTC)
- I'm asking about account creation and obtaining this right. sapphaline (talk) 22:05, 19 November 2025 (UTC)
- outsourcing captchas to a third party is a great way for that party to collect massive amounts of data to sell to advertisers.
- hcaptchas are made with generative ai, and the answers are used to train generative ai.
- see the terms of service didn't read for hcaptcha for what you're agreeing to when you run hcaptcha.
WMF banner fundraising campaign starts today
Hi all, The WMF banner fundraising campaign for logged-out users on English Wikipedia in Australia, Canada, Ireland, New Zealand, the UK, and the US will start at 9:00 UTC today. You can find more information on the Community Collaboration page. Best, JBrungs (WMF) (talk) 06:26, 1 December 2025 (UTC)
Death by AI?: Will large language models diminish Wikipedia
Authors: Christian Wagner and Ling Jiang
Published: 2025 in Journal of the Association for Information Science & Technology (Volume 76, Issue 5, Pages 743-751)
In this article, the authors argue that with the expansion of large language models and the ability of AI systems to automatically generate text, the value of Wikipedia is at risk of declining. The primary reason, they claim, is a reduction in human contributors’ motivation. Wikipedia is built on voluntary participation and the “altruistic, volunteer-driven” will of its users. In other words, most of the content is created by individuals who contribute without compensation. When users sense a kind of “AI competition”—that is, when they see that AI can produce content without their effort—the motivation to edit articles or add new material diminishes, leading to a drop in human participation.
As human participation declines, Wikipedia becomes increasingly dependent on AI-generated content or AI-assisted activity. This can produce a “vicious cycle”: fewer contributors → fewer readers → lower quality or freshness of content → reduced attractiveness → even fewer contributors. This cycle may gradually result in stagnation or “content decay.”
Reduced diversity of sources: With fewer human contributors, niche topics, less-represented languages, and non-mainstream or local perspectives may receive less coverage. This undermines the diversity and comprehensiveness of the encyclopedia. Slower updates: Without active editors, articles may be updated less frequently, errors may persist, and new developments across fields may be insufficiently reflected. Exclusive reliance on AI carries risks: the content may become more superficial, incomplete, or error-prone, because machines reproduce data rather than deliberately reviewing, analyzing, verifying sources, and validating claims.
The authors conclude that the real threat to Wikipedia is not merely AI-generated content, but the decline of human motivation to contribute. If this trend continues, Wikipedia may gradually become “a shadow of its former self”—a space lacking the collective engagement, diversity, and accuracy that once defined it. In other words, “death by AI” does not mean the literal disappearance of Wikipedia, but rather a loss of value, dynamism, and public trust.
The authors pose several questions to the Wikimedia Foundation and the Wikipedia community:
* Can human participation be preserved through mechanisms that align with Wikipedia’s ethical principles and community norms?
* Could the use of AI as an assistive tool (rather than a complete replacement) serve as a viable solution?
* How can the quality, diversity, and timeliness of articles be ensured—especially in languages with smaller contributor communities?
Perhaps this topic has already been discussed in various forms, but I am raising it because I am certain it is a fundamental question for many other users and contributors, and it deserves attention. Pereoptic Talk✉️ 15:55, 3 December 2025 (UTC)
- this paper is... not good. the main problem is that it seems to mistake all bot edits for generative AI, and all human edits for non-AI, so the entire argument is just dead on arrival. and then there's stuff like:
- "In the age of generative AI, Wikimedia thus addresses emerging challenges through strategic community design and adaptive governance (Kraut & Resnick, 2012)." - lol, lmao
- "Furthermore, Wikipedians also engage in collective endeavors to mitigate the negative impacts of bot use and sustain high-quality human contributions such as the Wikipedia Education Program engaging college students for long-lasting contributions" -- no comment
- "Elsewhere deletionist writer bots (Livingstone, 2016) became a source of frustration" -- what the fuck is a "deletionist writer bot"? (answer: it isn't anything, the paper is garbling this interview about a mass article creation bot, i.e., the near exact opposite.)
- Gnomingstuff (talk) 03:46, 4 December 2025 (UTC)
- @Gnomingstuff: This article is only a starting point for initiating a discussion about the impact of AI on Wikipedia. We should avoid Focalism. Instead of focusing on insignificant details, it is better to concentrate on the overall issue. The important question here is whether AI systems have directly influenced the pattern of Wikipedia usage or not.
- The issue is not the important role Wikipedia currently plays in AI systems; rather, as the article itself notes, the core concern is the decline in contributors. Evidence shows that due to the rise of artificial intelligence, people’s visits to websites have dropped sharply (For example, this trend is evident in Google.)—and this implies that Wikipedia’s readership is also decreasing. When users do not visit Wikipedia, they either do not realize that the platform can be edited, or even if they do, the lack of engagement reduces any motivation to correct or update content. Such individuals shift from being potential contributors to becoming mere consumers (i.e., readers of AI-generated content), and this dynamic is exactly what the article highlights:
- fewer direct readers → fewer contributors → lower quality or freshness of content → reduced attractiveness → even less participation.
- And this is without even considering AI-generated content that users themselves add to Wikipedia. Studies show that about 5% of newly created content on Wikipedia is already produced by AI. In other words, in the future, AI systems will rely on a Wikipedia in which a substantial portion of the content has also been generated by AI.
- It is true that AI cannot produce original knowledge and depends on primary sources. But, in fact, Wikipedia is also not a producer of scientific knowledge—it aggregates it. Current AI models cannot replace journalists, reporters, or researchers who produce first-hand content, yet they perform the very function Wikipedia serves: gathering information from primary and secondary sources. The difference is that Wikipedia depends on voluntary human editing, while AI can perform this aggregation far more quickly.
- Unfortunately, I am not sure what the Wikimedia Foundation is currently focusing on, but just a month ago they published an article on AI and Wikipedia that reads more like a desperate appeal to AI companies to support Wikipedia: *“In the AI era, Wikipedia has never been more valuable.”* These developments will inevitably affect future generations of users who are supposed to be drawn into contributing to Wikipedia. Pereoptic Talk✉️ 11:01, 4 December 2025 (UTC)
- The impact of AI has been discussed on en.wiki and in the WMF for a couple of years now. Drawing in contributors has been a topic of discussion even before then. En.wiki have a couple of llm-related policies already, more can be found at WP:LLM. CMD (talk) 11:23, 4 December 2025 (UTC)
- Is this comment itself generated with AI? Gnomingstuff (talk) 14:52, 4 December 2025 (UTC)
- @Gnomingstuff: No, I wrote these comments myself. I am a Persian speaker and use translation tools to write better. Grammarly says this message is structurally correct. I don't know why when talking about AI, some people try to tarnish the image with these false and absurd accusations of these opinions. Is the level of discussion high? Are the technical terms or references to cognitive biases surprising? I wonder where these paranoid opinions come from. Pereoptic Talk✉️ 16:06, 4 December 2025 (UTC)
- Grammarly uses AI. Which means that in this case I correctly picked up on what it does, namely, the Markdown formatting around links.
- I wonder where these comments that are like "I used AI, but why are you saying I used AI?" come from. Gnomingstuff (talk) 16:09, 4 December 2025 (UTC)
- Also, don't ping me. Gnomingstuff (talk) 16:09, 4 December 2025 (UTC)
- @Gnomingstuff: No, I wrote these comments myself. I am a Persian speaker and use translation tools to write better. Grammarly says this message is structurally correct. I don't know why when talking about AI, some people try to tarnish the image with these false and absurd accusations of these opinions. Is the level of discussion high? Are the technical terms or references to cognitive biases surprising? I wonder where these paranoid opinions come from. Pereoptic Talk✉️ 16:06, 4 December 2025 (UTC)
- I initially reverted this comment as LLM-generated due to the fabrication of quotes not present in the source. Pereoptic reverted, though those issues do not seem to have been fixed. I encourage readers to treat the above summary with caution. Toadspike [Talk] 00:33, 5 December 2025 (UTC)
- Thank you for prompting us to think about whether AI poses a risk to contributor motivation, @Pereoptic. I don’t think we’ve met yet - I’m Sonja, and I lead the Contributor Product teams at the Foundation. We’ve recently published a blog post about the decline in traffic we’ve seen over the past year, and the question of motivation is an important one we’re trying to tackle to turn that trend around. AI may play a role in this, but there are a lot of other aspects that contribute to it as well. We’ve outlined some of these issues in a strategy draft around the current state of contributing, centered around 3 areas that we plan to focus on with our 4 WMF Contributor Product teams over the coming years. We’d love to get feedback on that draft, and in particular, I’m interested to hear from you what it is that motivates you to continue editing on the wikis today, and what would you need to still feel motivated to edit a few years from now, especially with the rise of AI? SPerry-WMF (talk) 17:50, 5 December 2025 (UTC)
- @SPerry-WMF: Nice to meet you and talk to you and Thank you for the educational points you raised (I appreciate the post you wrote and the project you initiated, and I’d be glad to help in this regard.). I had really been waiting for such a deep and well-informed answer. I brought up this discussion because the project needs to take action in order to continue and survive in the coming years, considering the changes that have occurred on the Internet and the shifting paradigms of this space.
- I am an active contributor on my local Wikipedia (Persian Wikipedia) and am one of the few active users working in the medical field there (of course, my contributions to technical topics are also significant; for example, I participated in the Wiki Hackathon 2025). My main motivation for editing Wikipedia is that, in addition to contributing content, I can first read the material myself. The content I read in reliable sources—and then use to write Wikipedia articles—stays in my memory longer. This means that, besides writing Wikipedia, I also read it and increase my knowledge. But there is a problem: this may be a personal experience, and new contributors may not join Wikipedia with such a motivation.
- Like the English Wikipedia, Education program is still active on Persian Wikipedia, and we have restored it. As one of the trainers and speakers in the workshops we hold to promote Wikipedia in universities, I use Adam Smith’s “invisible hand” concept to motivate students. This means that if the owner of a restaurant gives you a bowl of soup for free along with the main course, it is not out of pure kindness or generosity but rather an attempt to encourage you to visit again. Because it benefits you (you received a free bowl of soup) and it benefits the owner (you may return to the restaurant), individual interests invisibly guide you toward an outcome that benefits the collective.
- In these workshops, I highlight Wikipedia’s personal benefits alongside its collective and public value. For example, in addition to contributing to Wikipedia, you gain access to a valuable resource such as the Wikipedia Library, which helps you find more material to study. Another point I emphasize is that Wikipedia can serve as your sandbox for learning how to write scientific articles and develop academic and scientific thinking. (This was true for me as well in the early stages, as I became familiar with scientific literature through Wikipedia.) It can help you pursue your scientific and research goals. In some cases, I even mention Wikipedia’s collaborative and international events, which allow you to exchange experiences and knowledge with contributors from other communities and cultures—an enjoyable and enriching activity. However, the methods I have proposed are not feasible for many non-academic participants, and new ideas and solutions need to be put forward to generate further discussion and debate on this issue. This is especially true for our wiki because the Persian-speaking community (compared to the English Wikipedia) is made up of developing countries and individuals may face certain constraints to participation (such as long working hours, economic hardship, etc.).
- Sorry for the rambling. The issue of maintaining contributions and increasing those contributions is a very important issue. This means escaping the algorithm or ignoring the risks that may jeopardize the continuity of the project. This is crucial because Wikipedia, like many institutions like Westinghouse or academic institutions that have been around for a long time (although Wiki is different from commercial companies), has the ability to adapt to progress and technology. There are two possible futures for Wikipedia. Either it changes itself with the new conditions, or if it cannot keep up with them, it is forgotten. Pereoptic Talk✉️ 15:28, 7 December 2025 (UTC)
- Could you respond to the concern regarding fabricated quotes above? ~2025-31733-18 (talk) 18:35, 7 December 2025 (UTC)
- Of course, I did not start this discussion to talk about my personal experiences or to promote my wiki (I am afraid that, as happened at the beginning of the discussion when they complained about minor issues, some users might say, “So what does this have to do with us?”). It simply responded to the question you raised.
- My main goal in creating this discussion was, first, to find out whether the Foundation has a solution to the problem of declining user numbers and what contribution I and other users can make in this regard. This is important because the golden period for taking action to find solutions and adapt Wikipedia to the new Internet ecosystem might be now, before the project faces a sharp decline in participation and page views.
- For example, over the long lifespan of Wikipedia, the trend in the number of new registered user has been downward, and this data is statistically significant. A similar pattern is visible in the statistics for all editors. A probabilistic explanation also suggests that if the graph continues to follow the same behavioral regime, based on the fact that the number of edits and active contributors remained constant during the same period of time then in the future edits per user will increase while the number of users will decrease, meaning that even future active users will have to participate more actively than current active users in order for the total number of edits to remain constant and a drop in the number of edits can be expected in the future. Pereoptic Talk✉️ 17:10, 8 December 2025 (UTC)
- Thank you so much for all this detail, @Pereoptic! I agree with you that we should feel a sense of urgency to turn these trends around and ensure our projects are sustainable long-term, and hearing different perspectives on things like what motivates you to edit are really helpful for us to ensure that we're not too biased towards one particular problem space or wiki as we try to address these challenges over the coming years with our strategy. It's good to hear that The Wikipedia Library and collaborative events are strong motivators for you - I agree! In fact, we just recently deployed a new feature you might be interested in on the CampaignEvents extension that lets you attribute an edit to a specific event as part of a collaboration. SPerry-WMF (talk) 22:48, 10 December 2025 (UTC)
- Sorry for the rambling. The issue of maintaining contributions and increasing those contributions is a very important issue. This means escaping the algorithm or ignoring the risks that may jeopardize the continuity of the project. This is crucial because Wikipedia, like many institutions like Westinghouse or academic institutions that have been around for a long time (although Wiki is different from commercial companies), has the ability to adapt to progress and technology. There are two possible futures for Wikipedia. Either it changes itself with the new conditions, or if it cannot keep up with them, it is forgotten. Pereoptic Talk✉️ 15:28, 7 December 2025 (UTC)
Wikimedia Foundation announces new CEO, Bernadette Meehan
From the Wikimedia Foundation:
The Wikimedia Foundation Board of Trustees has appointed Bernadette Meehan as the new CEO of the Wikimedia Foundation. She will officially join on January 20, 2026. Current CEO Maryana Iskander will stay in her role until then for a seamless handoff.
Bernadette has spent her career in roles dedicated to mission driven and public service work. Most recently, she served as the U.S. Ambassador to Chile from 2022-2025. Prior to her ambassadorship, she served as Executive Vice President for Global Programs at the Obama Foundation, where she designed and led international leadership programs spanning Africa, Asia-Pacific, Europe, Latin America, and South Asia. You can read more about her background below and the announcement to the media here.
Bernadette joins the Foundation at an important moment, on the cusp of Wikipedia’s 25th birthday. The world is facing unprecedented social, technological, regulatory and generational shifts. How people search and find information is being transformed. As Wikipedia’s influence has grown, so too has the importance of ensuring that people and decision makers understand its model and contribute to its future. Now more than ever, we need to increase awareness about the Wikimedia projects, and Bernadette will be the right leader to guide the Foundation in this new era.
qcne (talk) 19:00, 9 December 2025 (UTC)
- Hello, I don't know anything about the qualifications for Wikimedia CEOs in the past, but are they usually Wikimedia editors or community figures? What does Ms. Meehan's career have to do with the Wikimedia movement specifically? ✨ΩmegaMantis✨blather 20:32, 9 December 2025 (UTC)
- @OmegaMantis The trend has been for CEOs to be executives with non-profit experience, with no Wikipedia editing experience. As CEO they would direct priorities, strategy, budgets, policy, etc of the Foundation, so would have some removed impact on the English Wikipedia. qcne (talk) 20:37, 9 December 2025 (UTC)
- Ah, ok. Thanks for the quick response! ✨ΩmegaMantis✨blather 20:38, 9 December 2025 (UTC)
- I don't think we have ever had a CEO who was a Wikimedia editor or community figure in any real sense. We have also never had a board member with any experience creating an encyclopedia in academia or commercial publishing. The nearest was Sue Gardner, the longest-serving CEO (and many would say the best), from December 2007 to May 2014. She is a Canadian journalist, previously "the director of the Canadian Broadcasting Corporation's website and online news outlets". One thing all WMF CEOs share (Meehan will be the 6th) is being women. Johnbod (talk) 22:20, 9 December 2025 (UTC)
- @OmegaMantis The trend has been for CEOs to be executives with non-profit experience, with no Wikipedia editing experience. As CEO they would direct priorities, strategy, budgets, policy, etc of the Foundation, so would have some removed impact on the English Wikipedia. qcne (talk) 20:37, 9 December 2025 (UTC)
- Interesting that User:Feelingfancyfree created the article Bernadette Meehan and was a blocked as a sock a few months later, followed by paid editing revelation. Is there anymore to this story? Asking for a friend. CNC (talk) 02:19, 10 December 2025 (UTC)
- As an ambassador she was notable on her own right, so I do not see any issues with this. The article was properly sourced. Ymblanter (talk) 21:30, 10 December 2025 (UTC)
- As a spokes
womanperson for the National Security Council you mean, but ok. CNC (talk) 21:37, 10 December 2025 (UTC)
- As a spokes
- As an ambassador she was notable on her own right, so I do not see any issues with this. The article was properly sourced. Ymblanter (talk) 21:30, 10 December 2025 (UTC)
Wikimedia Foundation Bulletin 2025 Issue 23


Upcoming and current events and conversations
Let's Talk continues
- CEO appointment: The Wikimedia Foundation Board of Trustees has appointed Bernadette Meehan as the new CEO of the Wikimedia Foundation. She will be meeting communities around the puzzle globe when she officially joins on January 20, 2026.
- Wikipedia's 25th birthday party: Join the virtual celebration for games, prizes, musical performances, volunteer spotlights, data visualization, surprise guests and more. January 15 at 16:00 UTC. Register on Meta.
- Wikimedia Foundation Board of Trustees: Join the next Conversation with the Trustees on December 11 at 17:30 UTC.
Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org
- Wishathon: 15 patches were written and 5 merged, as part of a Wishathon for the Community Wishlist. One wish from the community was completed ("Preview page with this template" should not work with pages that do not transclude the template), and three more now have a clearer path forward.
- Activity Tab on Mobile App: The Wikipedia iOS app is running an experiment that replaces the History tab with a redesigned Activity tab. This new tab surfaces personalized insights about reading, editing, and donations — all stored locally on your device for privacy. The goal is to see whether the new experience increases engagement and retention among logged-in readers.
- Wikipedia Year in Review in Apps: The Wikipedia Year in Review 2025 is now available for the iOS and Android apps. This year introduces new personalized insights, updated reading highlights, and refreshed designs.
- Add a Link: A feature that suggests links to be added to articles based on a prediction model, Add a link, has been deployed at Japanese, Urdu and Chinese Wikipedias. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time.
- Abstract Wikipedia: The second round of voting on the name of Abstract Wikipedia concluded with Abstract Wikipedia as the top-voted name with 100 votes, followed by Wikigenerator with 91 votes. The name for the wiki project will now remain Abstract Wikipedia.
- Anti-vandalism tool: Automoderator, now has the option to choose between two machine learning models to power the software on wikis using the tool.
- Tools to support newcomers: Newcomers failing to add a citation to support added content has been one of the most common mistakes on Wikipedia. Reference Check, a tool that prompts them to add a citation before publishing an edit, has gone live for an A/B test on English Wikipedia.
- Tech News: Latest updates from Tech News week 48 and week 49 include the Foundation working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful, and informative; and two new wikis being created: a Wikipedia in Toki Pona and a Wikiquote in Nigerian Pidgin.
- Infrastructure: Unifying our mobile and desktop domains achieved 20% faster mobile response times, improved SEO, and reduced infrastructure load.
Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · list of movement events
- Legal win in France: Wikimedia Foundation secures crucial legal win in France against legal attacks on freedom of speech.
- CEE Hub: Overview of three years of growth, learning, and regional impact of CEE Hub.
- Don't Blink: The latest developments from around the world about protecting the Wikimedia model, its people and its values.
- Digital Violence: How the Wikimedia movement is responding to digital gender based violence.
- Wikimedia Research Showcase: The next research showcase will feature a special panel on "Experimentation on Wikipedia" and will take place on December 10 at 17:30 UTC.
Annual Goals Progress on Effectiveness
See also: Progress on the annual plan
- Audit Report: Key takeaways from the Foundation’s audit report for fiscal year 2024-2025.
- Wikimedia Enterprise: Wikimedia Enterprise Financial Report for fiscal year 2024-2025.
- Annual Plan Progress: A look back at progress made against the plan during the second half of our fiscal year. Up to date regular updates are included in the Foundation Bulletin.
Board and Board committee updates
See Wikimedia Foundation Board noticeboard · Affiliations Committee Newsletter
- Sister Projects Task Force: Results of the consultation about Wikispore and Wikinews: No immediate changes should be made to Wikispore's current technical setup and archive all editions of Wikinews, preserving their content.
Foundation statements
- Wikipedia's unique revenue model: How is Wikipedia funded and how does the Wikimedia Foundation use donations to Wikipedia?
- Most read articles: Wikipedia’s most-read articles of 2025.
Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · The Wikipedia Library · Milestones · Wikidata · Central and Eastern Europe · other newsletters
Subscribe or unsubscribe · Help translate
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. Let askcac
wikimedia.org know if you have any feedback or suggestions for improvement!
MediaWiki message delivery 04:50, 11 December 2025 (UTC)
Wikipedia’s 25th birthday party on January 15
Hiyas. Sharing an invite to Wikipedia’s 25th birthday party, happening on January 15 at 16:00 UTC. It’ll be an hour-long virtual event with trivia, prizes, musical performances, dramatic readings, spotlights on editors, and special guests. The event will be live-interpreted in 6 languages and streamed to Eventyay and Wikipedia’s YouTube. You can register for the event to save the date and get updates, and please let me know if you have questions :) RAdimer-WMF (talk) 20:48, 11 December 2025 (UTC)
Wikimedia Foundation Banner fundraising campaign finished
Hi everyone,
Just a quick message to let you know that fundraising banners have now been disabled across all Big English campaign countries (Australia, Canada, Ireland, New Zealand, the UK, and the US). Thank you very much for your support, collaboration, and understanding during this campaign. We will post a campaign wrap up on the collaboration page in late January. Best, JBrungs (WMF) (talk) 11:09, 1 January 2026 (UTC)
Reactions to comments?
Would you prefer banning anonymous edits instead of temporary accounts?
The discussion above about temporary accounts is quite heated. It's clear that there is some opposition, but I'd like to know if it's a majority of editors or just a couple of loud critics. I don't think it will change anything, as WMF never asked our opinion and made it clear that it will introduce temporary accounts regardless of what we say, but I think it is important to register what our opinion is. Furthermore, I think both alternatives are undesirable, but the legal situation forces us to choose one of these paths, so I'm asking a simple yes/no question to focus the debate and facilitate counting. Tercer (talk) 08:57, 8 October 2025 (UTC)
- How will asking the same question in the same forum, read by the same audience, enable you to determine whether it is "a majority of editors or just a couple of loud critics"? --Elmidae (talk · contribs) 09:49, 8 October 2025 (UTC)
- The question hasn't been explicitly asked before. We have lots of back and forth above, about several different subjects. And yes, I'm interested in the opinion of the editors that participate in this forum, who haven't expressed it clearly or didn't participate in the above discussion (that includes you). If you want to advertise this topic in other forums to get a wider participation that would be great. Tercer (talk) 10:06, 8 October 2025 (UTC)
- Like Elmidae, I have not contributed to the "Temporary accounts rollout" thread and do not plan to. WP:PETITION disfavors such yes/no questions "since they not only encourage the community to avoid meaningful discourse and engagement, but also limit their scope to only one initially-stated opinion or preference with little or no opportunity for discussing and reconciling competing or opposing points of view." Even if you had 60% of a whopping 1000 respondents to vote for banning IP edits rather than introducing temporary accounts, that would be insufficient for our consensus-based model. ViridianPenguin🐧 (💬) 17:09, 8 October 2025 (UTC)
- What is definitely insufficient for our consensus-based model is WMF's imposition of temporary accounts without asking for our opinion or giving us any alternatives.
- A cornerstone of our consensus-based model are WP:RfCs, which do involve asking editors what their opinion is. Perhaps I should have started one straight away instead of trying to gather opinions informally. Then at least I wouldn't have had two responses that are only talking about format instead of the subject matter. Tercer (talk) 17:38, 8 October 2025 (UTC)
- Decisions of the WMF are exempt from consensus. SuperPianoMan9167 (talk) 14:43, 9 October 2025 (UTC)
- I think we're asking this question too early. I think we should let temporary accounts roll out, then if it goes poorly, someone will likely propose an RFC to ban logged out editing at that time. However, WMF has rolled out temporary accounts to most other wikis now, and those wikis haven't imploded. I think that is good evidence that temporary accounts won't create a vandalism catastrophe, and that we can continue to permit logged out editing. –Novem Linguae (talk) 00:47, 9 October 2025 (UTC)
- As a matter of fact I believe that editors should make the decisions about Wikipedia, not WMF. It is not too early, it is too late, because the decision has been made without our input and will be implemented regardless. As for the other wikis, we have seen feedback only from a single editor from a single wiki, and it was very negative. That's not good evidence, but it is evidence of the opposite of what you claim. Tercer (talk) 09:19, 9 October 2025 (UTC)
- @Tercer: The vast majority of WMF wikis have already implemented temporary accounts. As an administrator at en.wikibooks, I can express a positive experience. JJPMaster (she/they) 16:29, 14 October 2025 (UTC)
- I can confirm that is also the case with Wikibooks and Meta-Wiki (I hold admin privileges on both projects). Codename Noreste (discuss • contribs) 16:36, 14 October 2025 (UTC)
- Thanks for chiming in. Can you elaborate on what was positive about it? Tercer (talk) 16:52, 14 October 2025 (UTC)
- @Tercer: The vast majority of WMF wikis have already implemented temporary accounts. As an administrator at en.wikibooks, I can express a positive experience. JJPMaster (she/they) 16:29, 14 October 2025 (UTC)
- Reacting once an implosion has occured is too late. How is a community going to recover from said implosion anyway?
- In phab:T364073 the Lithuanian Wikipedia disabled Content Translate because it had so many edits that the admins could not keep up.
- Writing that, temporary accounts are not that bad. If an temporary account vandal ip hops without invalidating the account one ban is enough, while one ban per ip, or an rangeblock (if the ip's are close enough together without collateral damage) would be needed now. Tempoarary account vandals become hard when they invalidate their accounts. I checked the Norwegian Wikipedia in June/July and compared ip's in months of last year compared to temporary accounts in the same month of this year. I found out the ratio hovers around 1:1, with occasional spikes to 2 temp accounts per ip. That spike is normal to me, because temp accounts only exist for 90 days maximum. For an IP hopping, temporary account invalidator, there is always IP auto-reveal mode which shows for admins IP's in recent changes as they are shown now for a limited time. Snævar (talk) 13:58, 9 October 2025 (UTC)
- As a matter of fact I believe that editors should make the decisions about Wikipedia, not WMF. It is not too early, it is too late, because the decision has been made without our input and will be implemented regardless. As for the other wikis, we have seen feedback only from a single editor from a single wiki, and it was very negative. That's not good evidence, but it is evidence of the opposite of what you claim. Tercer (talk) 09:19, 9 October 2025 (UTC)
- Please stop talking about banning IP edits until the new system has had a six months trial. People have tried banning IPs in the past and it gets quickly shot down. Repeating the half-baked proposal is counterproductive because it biases people such that they reflexively vote no next time, rather than examine the issue yet again. Johnuniq (talk) 00:56, 9 October 2025 (UTC)
- What about "Please stop talking about introducing temporary accounts until we do a six months trial of banning IP edits"? Unlike temporary accounts, that would be very easy to implement, and very easy to reverse, so we could actually have a trial. You know very well that temporary accounts is not a trial, it will not be revisited after six months.
- And frankly, there's nothing "half-baked" about banning IP edits. It's technically simple, and has been done already. What else do you need to consider it fully baked? Tercer (talk) 09:23, 9 October 2025 (UTC)
- All discussion prior to implementation will be entirely overshadowed by what actually happens when they're implemented. Either they will work out ok or they will make it to difficult to counter disruptive editing and will have to be limited somehow. Realistically I don't believe there is enough evidence to say for certain what will happen, but given the feedback I've seen from the WMF and the experience of other smaller Wikis I think it should be ok. -- LCU ActivelyDisinterested «@» °∆t° 19:52, 9 October 2025 (UTC)
- I don't think the impact will be large, but I'm certain it will be unambiguously negative. And I think that when Wikipedia is under attack from very powerful people, including the US government, WMF should be making the life of malicious actors harder, not easier. Tercer (talk) 19:50, 10 October 2025 (UTC)
- While I’m not a fan of temporary accounts for LTA/sock-tracking purposes (IP geolocation is a cornerstone of linking accts to sockmasters), banning IP edits altogether would be a horrible idea - for every two-bit vandal, there’s a productive contributor that just didn’t want to or hasn’t decided to create an account yet. Hell, half of the recent USHL season pages have been maintained by an IP who’s filling a valuable gap in WP:NHL. The Kip (contribs) 02:13, 11 October 2025 (UTC)
- Yes, I am in favor of banning IP edits and temporary accounts. All editors should be required to create an account connected to a verified email address or phone number. Anyone can still edit and vandalism practically ceases to exist. 216.126.35.228 (talk) 17:14, 14 October 2025 (UTC)
- This just defeats the whole point of all Wikimedia projects, in which anyone else can edit. If votes were allowed here, I would be strongly opposed to banning all unregistered edits, and strongly support the introduction of temporary accounts. Codename Noreste (discuss • contribs) 22:26, 14 October 2025 (UTC)
- @Codename Noreste: How would requiring a verifiable account defeat the whole point to create a repository of the entire sum of human knowledge which anyone can edit? Anyone can create an account. 216.126.35.228 (talk) 16:37, 15 October 2025 (UTC)
- Principles aside, I invite you to check out Citizendium and see how that worked out. 184.152.65.118 (talk) 01:34, 3 November 2025 (UTC)
- Just to note, not all Wikimedia projects allow for non-registered accounts to edit. --Super Goku V (talk) 15:03, 3 November 2025 (UTC)
- @Codename Noreste: How would requiring a verifiable account defeat the whole point to create a repository of the entire sum of human knowledge which anyone can edit? Anyone can create an account. 216.126.35.228 (talk) 16:37, 15 October 2025 (UTC)
You are an IP address yourself xD Mickey mouse 129 (talk) 18:39, 1 January 2026 (UTC)—
Blocked sockpuppet.
- This just defeats the whole point of all Wikimedia projects, in which anyone else can edit. If votes were allowed here, I would be strongly opposed to banning all unregistered edits, and strongly support the introduction of temporary accounts. Codename Noreste (discuss • contribs) 22:26, 14 October 2025 (UTC)
- Let's see how the "temporary accounts" bit works out, first, once the dust settles. If it works okay and there's not a major increase in vandalism and abuse, then the temporary accounts thing is still not good, and it would've been better to keep IPs, but if it's not causing massive headaches, then it is what it is. If it is causing major headaches and we do see a noticeable spike in vandalism, socking, LTA activity, etc., then we'll have to decide on next steps at that point, which may involve restricting or disabling anonymous editing. But let's wait until we actually have the data, rather than just speculation. Seraphimblade Talk to me 22:58, 14 October 2025 (UTC)
- Even if 99% of Wikipedia editors support disabling IP/temporary account editing, I believe the WMF will still have the final say on whether to implement this change (and I believe they've stated before that they will not get rid of IP/temporary account editing). Some1 (talk) 23:03, 14 October 2025 (UTC)
- Counter-example: Portuguese Wikipedia turned off IP editing years ago. –Novem Linguae (talk) 12:43, 15 October 2025 (UTC)
- Some statistics which might be helpful evaluating TA rollout on enwiki. I've checked those stats for my home wiki after TA deployment and everything seemed fine. Johannnes89 (talk) 21:36, 4 November 2025 (UTC)
- Counter-example: Portuguese Wikipedia turned off IP editing years ago. –Novem Linguae (talk) 12:43, 15 October 2025 (UTC)
- Strongest possible oppose to either, frankly. I would not be here if it were not for IP editing, and I know many of our greatest editors started out as IP addresses. I think this whole temporary account thing is dumb, but that is outside the scope of this. We've been doing this for over 20 years and it's worked fine. That's all. Lynch44 16:52, 2 November 2025 (UTC)
- I disagree that it's worked fine, both from a privacy and legal perspective. Nosferattus (talk) 07:22, 12 November 2025 (UTC)
- Not opposed to the idea, but I currently don't support it at the moment. If I had responded last week, I might have been more supportive to banning IP edits over the temporary account program, but Sohom posted a research article in the discussion above that does indicate with evidence that there are costs to prohibiting non-registered edits, so I do have concerns. --Super Goku V (talk) 15:09, 3 November 2025 (UTC)
- I think this would be a bad idea, anonymous users are , on the whole, a net positive, and adding friction to the "Spot issue with article > Fix issue with article" process is going to reduce the quality of articles on the whole. I would not like "Spot issue with the article > Try to edit it > Get told you have to register > Lose interest" I would much rather see a more integrated, proactive solution to getting people registered, something like, the 'submit' page for any anonymous edit giving you a 'Now select a username and password' page, with a prominent 'skip' option. ("Spot issue with the article > edit it > register or not.") If having something like that in place, we find that the number of temporary users reduces significantly (with an equivalent increase in registrations), then we can review. This is how a lot of e-commerce sites do it, as they too are motivated to get the value (fixing pages/buying stuff) without adding friction, but also would like you to register if you don't mind thank you very much. JeffUK 11:38, 10 November 2025 (UTC)
- @JeffUK IP users were never anonymous, to start with. In fact, they were the opposite of that. IP editing is a privacy and security breach which should have never been allowed, now or back in 2001 when the risks were already perfectly known. Darwin Ahoy! 09:29, 10 December 2025 (UTC)
- None of my comment hinges on their anonymity, or otherwise. But ok. JeffUK 19:54, 14 December 2025 (UTC)
- @JeffUK IP users were never anonymous, to start with. In fact, they were the opposite of that. IP editing is a privacy and security breach which should have never been allowed, now or back in 2001 when the risks were already perfectly known. Darwin Ahoy! 09:29, 10 December 2025 (UTC)
- I have long considered the idea of temporary accounts to be unnecessary technical debt that only adds confusion to anti-abuse mechanisms. It's long past time that we followed other websites' leads in requiring registration. The fact that it is fairly easy to get access to the IP information means the privacy gains are not great; cutting off access to it also assumes catching such leakers in the first place, which is not happening if said IP address information was leaked privately and can't be discovered by us.--Jasper Deng (talk) 08:24, 15 November 2025 (UTC)
The fact that it is fairly easy to get access to the IP information means the privacy gains are not great
Before temp accounts, everybody could see an unregistered editor's IP. Now, it's 1000 people for English Wikipedia globally. Regarding the ease of getting to the threshold, see{{Registered editors by edit count}}. SGrabarczuk (WMF) (talk) 11:17, 15 November 2025 (UTC)- The barrier is still much lower than virtually any other website. It's also a poor metric given the manual nature of this process. Jasper Deng (talk) 17:56, 15 November 2025 (UTC)
- It's better than what it was before. The barrier to seeing IPs used to be nothing. Everyone saw logged-out editors' IP addresses even if they didn't want to. There's zero reason to know the IP address of a logged-out constructive contributor; the main benefit of attributing logged-out edits to IPs in the first place was that it made tracking vandals easier.
- If we instead required registration for everyone, good-faith logged-out contributors would likely lose interest if they saw that they had to make an account. The bad-faith editors could just as easily vandalize after taking the 10 seconds to register. So requiring registration would be a net negative to the project.
- SuperPianoMan9167 (talk) 19:27, 15 November 2025 (UTC)
- Registered-only is even better in the privacy regard, so that is not an argument in favor of the current situation. And, the amount of registrations we get shows that good-faith users still will register, so that is not an argument either.
- We always have to balance good-faith contributions with the feasibility of anti-abuse mechanisms. By your argument, we should allow open proxy editing as well. Jasper Deng (talk) 19:48, 15 November 2025 (UTC)
- We can and do allow good-faith contributors to edit via open proxy by granting WP:IPBE. In most cases, open proxies are abused for vandalism and block evasion so much that it is dangerous to leave them unblocked. SuperPianoMan9167 (talk) 19:53, 15 November 2025 (UTC)
- I understand IPBe, having been on this project for 17 years, thank you very much (while you have not been here for even a year). You know what I mean.
- A bad-faith user's ability to obtain new accounts by simply clearing cookies or even refusing them outright is an obvious vulnerability here, and with this change we have lost our ability to easily detect obvious rangeblocks by looking at the IP addresses they use, outside /64's. And, even when bad-faith users do register usernames, they often do so with usernames that give themselves away (see any WP:LTA category), something they would still have to do if registration is required. Jasper Deng (talk) 19:59, 15 November 2025 (UTC)
- (edit conflict) Oh, I'm sorry; I didn't realize you probably knew about IPBE already. I see your point. SuperPianoMan9167 (talk) 20:05, 15 November 2025 (UTC)
- We can and do allow good-faith contributors to edit via open proxy by granting WP:IPBE. In most cases, open proxies are abused for vandalism and block evasion so much that it is dangerous to leave them unblocked. SuperPianoMan9167 (talk) 19:53, 15 November 2025 (UTC)
- The barrier is still much lower than virtually any other website. It's also a poor metric given the manual nature of this process. Jasper Deng (talk) 17:56, 15 November 2025 (UTC)
- No, the majority of IP or edits made from a user without an account are in good faith. Best wishes, Macaw*! 00:48, 20 November 2025 (UTC)
|
- While I am not yet a firm yes to banning anonymous editing, I am leaning in that direction. I think there should be a community wide discussion of the impact of the temp accounts, and in particular their effect on vandalism and impact on counter vandalism efforts. That said, I think we need to wait at least six months in order to get a clear picture that is more than just anecdotal reports. -Ad Orientem (talk) 01:26, 28 November 2025 (UTC)
- I’ve changed my mind on the topic. I don’t think temporary accounts change much of anything. It’s still just unregistered users, just a bit more private. It’s still an issue. Additionally I don’t like the false sense of security it gives people who are like oh my ip isn’t visible. But it is to like pretty much everyone. Even socks. It’s barely any work. Best wishes, Macaw*! 02:35, 28 November 2025 (UTC)
- Oppose per The Kip. sapphaline (talk) 09:59, 16 December 2025 (UTC)
Wikimedia Foundation Bulletin 2026 Issue 1



Highlights
- Wikipedia turns 25: Time to start the party! Join the virtual celebration featuring musical performances, games, and more on January 15 at 16:00 UTC. and The party will be live interpreted into Arabic, Chinese, French, Spanish, and Portuguese.
Annual Goals Progress on Infrastructure
See also newsletters: Wikimedia Apps · Growth · Product Safety and Integrity · Readers · Research · Wikifunctions & Abstract Wikipedia · Tech News · Language and Internationalization · other newsletters on MediaWiki.org
- Annual planning: Key questions for the Wikimedia movement to shape the Wikimedia Foundation’s 2026-2027 annual goals. Join the discussion on-wiki.
- Hackathon:
- Apply to join the Northwestern Europe 2026 Hackathon from March 13-14 in Arnhem, the Netherlands. Application will close mid-January 2026 or earlier based on event capacity.
- General Registration for the 2026 Wikimedia Hackathon is now open! The hackathon will take place in Milan, Italy from May 1 - 3, 2026. Event details can be found here and registration will remain open until March 30th or until event capacity is reached.
- Semantic search: Wikimedia Foundation is working on making it easier to find the information readers want.
- Tech News: Latest updates from Tech News week 50, week 51, and week 52 include that now edit filters can be set to automatically suppress their details which will help oversighters to prevent doxxing.
- Wikifunctions: The first Wikifunctions Volunteers' Corner of the next year will take place on February 9.
- Blazegraph Migration: To support the migration away from Blazegraph as the backend of Wikidata Query Service (WDQS), we are hosting regular calls starting on January 27. Wikidata users and tool maintainers are are invited to join, ask questions, and share migration-related concerns.
Annual Goals Progress on Volunteer Support
See also blogs: Global Advocacy blog · Global Advocacy Newsletter · Policy blog · WikiLearn News · list of movement events · The Wikipedia Library
- Upcoming Conferences: Announcing the six Wikimedia conferences funded for 2026 in the first round.
- Wikimania 2026: A glimpse on what the team is currently working on to prepare for Wikimania 2026 in Paris.
- Public Policy: Explore the resources available for public policy advocacy work, including explainers that describe key policy positions, guides on how to build a campaign or write a policy brief, and examples of open letters submitted to governments.
- Don't Blink: The latest developments from around the world about protecting the Wikimedia model, its people and its values.
- Public-Interest content: The Project Gayatri content expansion program brought 7,656 new articles on Indonesian Wikipedia.
- Wikimedia Research Showcase: The research showcase will return on January 22 at 17:30 UTC with the theme "Celebrating 25 Years of Wikipedia and the Research Behind It".
- Wikimedia Research Report: The Wikimedia Foundation has published its 13th bi-annual Research Report, highlighting the work completed during the first six months of this fiscal year.
Annual Goals Progress on Effectiveness
See also: Past issues of the bulletin for progress on the annual plan
- Wikimedia Enterprise: Read the full annual wrap-up of 2025 of Wikimedia Enterprise and how the year marked a fundamental shift in open knowledge.
Board and Board committee updates
See Wikimedia Foundation Board noticeboard · Affiliations Committee Newsletter
- Board of Trustees: Wikimedia Foundation welcomes two new Board Trustees Bobby Shabangu and Michał Buczyński.
- Affcom News: Read the year-end issue of AffCom News (July-December 2025), the newsletter that distributes relevant news and events about the work of Wikimedia's Affiliations Committee.
Other Movement curated newsletters & news
See also: Diff blog · Goings-on · Planet Wikimedia · Signpost (en) · Kurier (de) · Actualités du Wiktionnaire (fr) · Regards sur l’actualité de la Wikimedia (fr) · Wikimag (fr) · Education · GLAM · Wikidata · Central and Eastern Europe · other newsletters ·Milestones ·
Subscribe or unsubscribe · Help translate
For information about the Bulletin and to read previous editions, see the project page on Meta-Wiki. Let foundationbulletin
wikimedia.org know if you have any feedback or suggestions for improvement!
MediaWiki message delivery 00:30, 14 January 2026 (UTC)
No disclaimers on mobile pages?
WP:DISCLAIM says that Wikipedia will not deploy disclaimers about potentially sensitive/objectionable content. However, the footer on mobile (default skin) does not contain a link to disclaimers, unlike desktop versions. Is there a reason for this? Szmenderowiecki (talk · contribs) 06:40, 2 January 2026 (UTC)
- There are plenty of debates about the extent to which Wikipedia should have disclaimers, but putting all that aside, I just want to confirm I'm replicating the more technical aspect of what you're noticing. There is a list of links at the very bottom of the screen on desktop, with things like "Privacy policy," "About Wikipedia," etc. "Disclaimers" is among those links. On the standard mobile web view, there is also a list of links. However, it does not contain the disclaimers link (nor, I'm noticing, the "About Wikipedia" link; it also has a "Terms of Use" link that on desktop is absent and appears instead just above it in MediaWiki:wikimedia-copyright-footer, which is a bit odd in that the privacy policy is not treated the same).
- I'm not quite sure why that is, and whether it was a deliberate decision or just a technical artifact (perhaps those links are English Wikipedia-specific in a way that the others aren't and got missed when building the mobile version). Cheers, Sdkb talk 15:50, 2 January 2026 (UTC)
- Looks like the Minerva skin hides the "Disclaimers" link under the hamburger menu instead of putting it in the footer for some reason. Anomie⚔ 16:36, 2 January 2026 (UTC)
- Sdkb nailed my concern. Anomie, fair enough, but it's confusing as hell. Szmenderowiecki (talk · contribs) 21:38, 2 January 2026 (UTC)
- Looks like the Minerva skin hides the "Disclaimers" link under the hamburger menu instead of putting it in the footer for some reason. Anomie⚔ 16:36, 2 January 2026 (UTC)
- You mean a reason besides the mobile version being crap that should be chucked in the bin?--User:Khajidha (talk) (contributions) 18:19, 4 January 2026 (UTC)
- Hi @Szmenderowiecki, thanks for sharing this concern. This situation dates back to 2013, when the mobile site wasn't fully integrated into MediaWiki's skin system and we supported WAP phones. The main menu had two items "Random" and "Home" and was the primary menu (see wayback link). There was a small footer but nobody was clicking on the links there. It was therefore decided to merge the two menus.
- That said, the Reader Experience team at WMF will take a look at this to see if we can bring consistency between the mobile and desktop footers. Appreciate the flag again! EBlackorby-WMF (talk) 00:29, 8 January 2026 (UTC)
- There's a lot of stuff that just isn't on mobile for no discernable reason, like categories and navboxen. jp×g🗯️ 02:26, 18 January 2026 (UTC)
- And no Help link in the hamburger menu :-(. Commander Keane (talk) 02:40, 18 January 2026 (UTC)
WMF/Wikidata post Wikipedia text on new site without the necessary attribution...
Apparently Toolforge (i.e. WMF) now hosts a site called "Wikiflix", of which Wikidata proudly proclaims: "All WikiFlix content is generated from Wikidata and maintained by that community. " Well, no, that's not true. Every page has a text intro which is taken straight from enwiki, without any attribution at all. Compare e.g. their page for Nosferatu with the lead of our article Nosferatu, or their page with our It's a Wonderful Life. No idea why they consider films like Tarzoon: Shame of the Jungle or Close-Up (1990 film) as public domain, but it again has the text copied from us. If they are still copyrighted, then this really is a bad idea.
It's sad to see what is supposed to be a sister project neglect to show the most basic respect and instead claim that what is provided on Wikiflix is somehow the product of Wikidata editors. Fram (talk) 09:08, 8 January 2026 (UTC)
- WMF is not the creator or maintainor of Wikiflix. It is hosted on toolforge, which is a cloud computing like service for volunteers to host their programs and code which help wikimedia projects. That particular tool is created by @Magnus Manske ~/Bunnypranav:<ping> 10:51, 8 January 2026 (UTC)
- Who, then, is responsible for things like compliance with copyright? Phil Bridger (talk) 11:07, 8 January 2026 (UTC)
- That, I am not sure of. Copyright infringement in general in prohibited when using wikimedia cloud services (toolforge is a part of that). I just wanted to say that wmf does not operate Wikiflix, I do not have any comments on the lack of attribution done by Wikiflix, or any other issue raised. ~/Bunnypranav:<ping> 11:16, 8 January 2026 (UTC)
- @JJMC89 @Lucas Werkmeister @Pintoch @SD0001 @Sohom Datta is this something which falls under the remit of the Toolforge standards committee? RoySmith (talk) 12:22, 8 January 2026 (UTC)
- Taking a cursory look, for the wiki page itself I would encourage folks to edit the Wikidata page to provide credit to Wikipedia contributors/expand on who curate the content being displayed. Wrt to the lack of attribution within the tool itself, maybe raising a ticket with this repo would be a good place to start. For what it's worth, (in my personal opinion) the toolforge-standards-committee should be the point of last resort (not unlike arbcom) and should be contacted when y'all have made attempts to reach out to the maintainer, but there hasn't been any movement/there has been a refusal to follow Wikitech:Cloud_Services_Terms_of_use. Sohom (talk) 12:43, 8 January 2026 (UTC)
- @Sohom Datta thanks. To be honest, I've been following the progress of the TSC for a while and I'm still unclear on exactly what it is supposed to be doing. In any case, I do see that a ticket was opened about a month ago on this very topic with no apparent response. RoySmith (talk) 12:54, 8 January 2026 (UTC)
- I've opened another issue focusing more specifically on the attribution problem. RoySmith (talk) 13:09, 8 January 2026 (UTC)
- @RoySmith Facilitating right to fork requests would be it's primary function. I have mentioned/forwarded this thread (about Wikiflix/Wikivibes) to the list for further comments to see what folks think/what we can do. Sohom (talk) 13:29, 8 January 2026 (UTC)
- Is that list publicly accessible? RoySmith (talk) 13:39, 8 January 2026 (UTC)
- @RoySmith The list should be toolforge-standards-committee@lists.wikimedia.org. The archives to the list are non-public since there are cases where these discussions include non-public information (like non-compliant code/exposed secrets etc). Tbh, the best way probably to reach us/get a public response is to file a phab ticket under the toolforge-standards-committee project. Sohom (talk) 13:50, 8 January 2026 (UTC)
- Is that list publicly accessible? RoySmith (talk) 13:39, 8 January 2026 (UTC)
- On his github page he last responded in February 2024, none of the 7 issues there (oldest March 2024) has had any response at all. Fram (talk) 13:26, 8 January 2026 (UTC)
- @Sohom Datta thanks. To be honest, I've been following the progress of the TSC for a while and I'm still unclear on exactly what it is supposed to be doing. In any case, I do see that a ticket was opened about a month ago on this very topic with no apparent response. RoySmith (talk) 12:54, 8 January 2026 (UTC)
- Taking a cursory look, for the wiki page itself I would encourage folks to edit the Wikidata page to provide credit to Wikipedia contributors/expand on who curate the content being displayed. Wrt to the lack of attribution within the tool itself, maybe raising a ticket with this repo would be a good place to start. For what it's worth, (in my personal opinion) the toolforge-standards-committee should be the point of last resort (not unlike arbcom) and should be contacted when y'all have made attempts to reach out to the maintainer, but there hasn't been any movement/there has been a refusal to follow Wikitech:Cloud_Services_Terms_of_use. Sohom (talk) 12:43, 8 January 2026 (UTC)
- @JJMC89 @Lucas Werkmeister @Pintoch @SD0001 @Sohom Datta is this something which falls under the remit of the Toolforge standards committee? RoySmith (talk) 12:22, 8 January 2026 (UTC)
- That, I am not sure of. Copyright infringement in general in prohibited when using wikimedia cloud services (toolforge is a part of that). I just wanted to say that wmf does not operate Wikiflix, I do not have any comments on the lack of attribution done by Wikiflix, or any other issue raised. ~/Bunnypranav:<ping> 11:16, 8 January 2026 (UTC)
- Thanks. By the way, the similar site for sounds, Wikivibes, has the same problems. Fram (talk) 11:31, 8 January 2026 (UTC)
- well, the two projects share the same code base, that's why. – robertsky (talk) 13:54, 8 January 2026 (UTC)
- Who, then, is responsible for things like compliance with copyright? Phil Bridger (talk) 11:07, 8 January 2026 (UTC)
- Attribution added. --Magnus Manske (talk) 14:51, 8 January 2026 (UTC)
- Where? Fram (talk) 15:10, 8 January 2026 (UTC)
- It says
Description from Wikipedia, under Creative Commons Attribution-ShareAlike 4.0 License.
in the tiniest font size possible /s on "entries" that have a description. example — DVRTed (Talk) 15:14, 8 January 2026 (UTC)- Just checked on that page (which I might had cached) and some pages I hadn't visited yet, and I can't see it and a search for "description" yields no results... Fram (talk) 15:29, 8 January 2026 (UTC)
- That's odd but it's very likely due to caching. I guess the "entry-page.html" component is cached in the browser for you. You can either visit the page manually to force update the cache https://wikiflix.toolforge.org/vue_components/entry-page.html (it shows up as a blank page) and go back to one of the "entries", or you can try in a private/incognito window. — DVRTed (Talk) 15:53, 8 January 2026 (UTC)
- Thanks, yes, now I see it, and it's indeed barely legible. Fram (talk) 15:55, 8 January 2026 (UTC)
- I'm seeing it. It's a little hard to read, being in 6 pt type and (partly) in blue on a black background, but I'd argue that it meets the "any reasonable manner" requirement of CC-BY-SA license statement. RoySmith (talk) 15:57, 8 January 2026 (UTC)
- That's odd but it's very likely due to caching. I guess the "entry-page.html" component is cached in the browser for you. You can either visit the page manually to force update the cache https://wikiflix.toolforge.org/vue_components/entry-page.html (it shows up as a blank page) and go back to one of the "entries", or you can try in a private/incognito window. — DVRTed (Talk) 15:53, 8 January 2026 (UTC)
- Just checked on that page (which I might had cached) and some pages I hadn't visited yet, and I can't see it and a search for "description" yields no results... Fram (talk) 15:29, 8 January 2026 (UTC)
- It says
- Any indication how you will prevent copyright violations? Because there seem to be quite a few of those among the more recent films, and since the only purpose of the site is to provide an easy link to full video's, that seems rather bad... Fram (talk) 15:57, 8 January 2026 (UTC)
- Where? Fram (talk) 15:10, 8 January 2026 (UTC)
- Close Up is in the public domain in Iran because copyright only lasts 30 years there. --Ahecht (TALK
PAGE) 16:24, 8 January 2026 (UTC) - It looks like the site is linking to versions of these films hosted on other sites and playing them in an embedded video player. If the films are copyrighted, this would violate the English Wikipedia's rules on linking to pirated material (WP:COPYLINK), but it's not hosting the content, which would be more problematic. In Switzerland, for instance, such a link is generally not illegal, with some asterisks of course. Toadspike [Talk] 19:25, 8 January 2026 (UTC)
- But we don't really care about Swiss laws? COPYLINK explains "Knowingly and intentionally directing others to a site that violates copyright has been considered a form of contributory infringement in the United States ". So now that the Wikiflix editors know about this, they should remove these links. Or else Wikidata should stop supporting this site, and Toolforge should probably cease hosting it. Right? Fram (talk) 09:20, 9 January 2026 (UTC)
- @Fram, Whether or not Wikidata supports Wikiflix feels like a discussion for the Wikidata community to have. Please discuss it there, not on the English Wikipedia. For what's worth, this page on the tool points out that video links should be only added for public domain material.
- With respect to where the data is coming from, for Tarzoon: Shame of the Jungle (and basically all the items on wikiflix), the data of the youtube video is present on the associated wikidata item (using the P1651 property on Q1773542). At a technical level, the tool is doing nothing but surfacing wikidata's data in a slightly different format. If you have issues with the YT data being on Wikidata (where they also link to the youtube video) you should WP:BRD and engage with the Wikidata community. This does not appear to be a WMF or even a Toolforge issue, this is a Wikidata community issue and the correct forum to hash this out is Wikidata:Project chat. Sohom (talk) 10:49, 9 January 2026 (UTC)
- "At a technical level, the tool is doing nothing but surfacing wikidata's data in a slightly different format. "? That's a very strange way of looking at this. The tool is changing Wikidata (a very large general informational database with links to many, many different places, which may occasionally include copyvio links, just like Wikipedia) into a specialized small single-purpose site with additional Wikipedia text, with the sole intention of directing people to places where they can find films, but without any care whether these links are to copyvio's or not. Why wouldn't this be a Toolforge issue? If I start "Wikinudechildren.org" at Toolforge, only showing images of nude children which are already at Commons (i.e. "resurfacing" their data "in a slightly different format"), then you would claim that this is not a WMF or Toolforge issue either? After all, I don't add anything that isn't available yet, I just make it much much easier to find it and don't care about the appearance such a selection might give. Fram (talk) 11:19, 9 January 2026 (UTC)
- Linking/displaying/surfacing public domain material with a latent risk of potential contributory copyright infringement due to a noisy data source (as a tool) is very different issue from one actively promoting CSAM obviously (which for the record would require engineering outside just surfacing commons content). Promoting CSAM is a T&S issue which should be dealt with swiftly with a ban. Surfacing public domain videos and audio however, is not a illegal activity in itself. Looking at the codebase, there are controls to make sure that the wiki-data items were at some point marked as being in the public domain (by checking if they are linked to Q19652 through P6216). The fact that a few have been mislabeled is at best a oversight and at worst Wikidata editorial problem that the needs some moderation as I have said above. (for example, I've added a the exclusion property to the item which should remove it from Wikiflix consideration).
- Taking a step back, I think following up a statement that where I basically said "the tool works like so" with a response "So, by extension of your logic, you think CSAM is fine? Do you?" That is uncalled for and frankly unhelpful to the point of being disruptive. Sohom (talk) 17:43, 9 January 2026 (UTC)
- The images hosted at Commons shouldn't be CSAM (or they should be deleted there), plenty of images of nude children are not CSAM and I never claimed anything of the kind. But compiling/presenting acceptable material in a new manner can still be offensive. I'm glad that you immediately found such a page unacceptable, but you haven't explained why the two scenarii are so different (again, assuming that the base material in itself, whether they are Wikidata pages about movies or Commons images, are acceptable in the original context). "The tool works like so" doesn't mean that an acceptable content line shouldn't be drawn somewhere and that you only should be concerned about technological aspects. Fram (talk) 09:51, 12 January 2026 (UTC)
- To rehash my statement above, you might have missed
(which for the record would require engineering outside just surfacing commons content)
. I will refuse to elaborate further due to WP:BEANS, but you can have it from me that both situation are not parallels at a technical level in the way you are trying to insinuate. That being said, even if I for arguments sake assume in this context that both of these were somehow technologically equivalent and we apply the "is the presentation unsavoury" context, I still fail to see how Wikiflix is necessarily in violation given that there have been significant backend effort to restrict the films to only public domain ones (unless somebody banned public domain content while I was out on holiday). I don't think this is a spicy take, but we generally should not de-platform individual tool developers over vandalism/miscategorization that is outside their control that can be easily fixed by editing Wikidata items. This is especially relevant given that this isn't a casewhere the tool in it's current form is itself actively circumventing policies, Terms of Use, laws or even actively encouraging users to add copyright infringing material (even the "list of candidates" is filtered to public domain content only and contains a disclaimer that only public domain material will be considered). For what it's worth, when I made the comment "the tool works like so" my thought here was to clarify the argument "but is there is a mechanism for random non-editors to indiscriminately add YT links to any content through the tool". I still stand by the meat of the message in that this is a wikidata problem, not a Toolforge/WMF one. Sohom (talk) 10:12, 18 January 2026 (UTC)
- To rehash my statement above, you might have missed
- The images hosted at Commons shouldn't be CSAM (or they should be deleted there), plenty of images of nude children are not CSAM and I never claimed anything of the kind. But compiling/presenting acceptable material in a new manner can still be offensive. I'm glad that you immediately found such a page unacceptable, but you haven't explained why the two scenarii are so different (again, assuming that the base material in itself, whether they are Wikidata pages about movies or Commons images, are acceptable in the original context). "The tool works like so" doesn't mean that an acceptable content line shouldn't be drawn somewhere and that you only should be concerned about technological aspects. Fram (talk) 09:51, 12 January 2026 (UTC)
- "At a technical level, the tool is doing nothing but surfacing wikidata's data in a slightly different format. "? That's a very strange way of looking at this. The tool is changing Wikidata (a very large general informational database with links to many, many different places, which may occasionally include copyvio links, just like Wikipedia) into a specialized small single-purpose site with additional Wikipedia text, with the sole intention of directing people to places where they can find films, but without any care whether these links are to copyvio's or not. Why wouldn't this be a Toolforge issue? If I start "Wikinudechildren.org" at Toolforge, only showing images of nude children which are already at Commons (i.e. "resurfacing" their data "in a slightly different format"), then you would claim that this is not a WMF or Toolforge issue either? After all, I don't add anything that isn't available yet, I just make it much much easier to find it and don't care about the appearance such a selection might give. Fram (talk) 11:19, 9 January 2026 (UTC)
- "we don't really care" – please speak for yourself. On the rest, I agree with Sohom that this is a Wikidata problem, not an enwiki problem. Toadspike [Talk] 13:13, 10 January 2026 (UTC)
- I have not been following every detail of this thread, but I agree that this has moved onto topics which are not enwiki issues, so this conversation should move to some more appropriate forum. Perhaps wikidata:Wikidata:Community portal or somewhere on meta? RoySmith (talk) 13:22, 10 January 2026 (UTC)
- In what way does WMF/enwiki care about the Swiss laws for non-Swiss material? Fram (talk) 09:53, 12 January 2026 (UTC)
- What has whether or not the WMF or enwiki care about Swiss law for non-Swiss material got to do with Wikiflix, Wikidata or anything else relevant to this thread? I agree with RoySmith that this thread has run its course here. Issues related to Wikidata need to be directed to the Wikidata community, any issues actually relevant to the English Wikipedia should be raised in a new thread. Thryduulf (talk) 20:45, 12 January 2026 (UTC)
- But we don't really care about Swiss laws? COPYLINK explains "Knowingly and intentionally directing others to a site that violates copyright has been considered a form of contributory infringement in the United States ". So now that the Wikiflix editors know about this, they should remove these links. Or else Wikidata should stop supporting this site, and Toolforge should probably cease hosting it. Right? Fram (talk) 09:20, 9 January 2026 (UTC)
Wikipedia’s 25th birthday party today! (15 January)
Hiyas, a reminder about Event:Wikipedia 25 Virtual Celebration happening online on January 15 at 16:00 UTC. We’ll have musical performances, games, prizes, special appearances, trivia, and it will be interpreted into Arabic, Chinese, French, Spanish, and Portuguese. Best, RAdimer-WMF (talk) 08:18, 15 January 2026 (UTC)
Questions to the community in preparation for WMF Annual Plan
The Wikimedia Foundation's Product and Technology department (the part that develops features and works on code changes) is starting it's Annual planning process (APP) where it decides what it will be allocating resources to/prioritizing over the next fiscal year. To inform WMF's decision making on what to prioritize, they are requesting community members to answer a few questions/provide feedback on what should be considered at this meta wiki page until Feb 10. -- Sohom (talk) 16:51, 20 January 2026 (UTC)
- Thanks @Sohom Datta, I was coming here to post this message and you beat me to it! I'll just highlight for everyone here that the annual planning questions are ones Wikimedia Foundation staff are thinking a lot about these days and deal with some of the toughest challenges facing the Wikimedia projects, including editor support, attracting and retaining readers, and testing features more quickly and effectively. We are really curious how all of you would answer these questions, so thanks in advance to anyone who shares their thoughts! KStineRowe (WMF) (talk) 22:49, 20 January 2026 (UTC)
- Thanks a lot to both of you for this (and for putting it on WP:CENT)! I'll share my thoughts there! Chaotic Enby (talk · contribs) 23:31, 20 January 2026 (UTC)
- Do we not already have the community wishlist? CMD (talk) 02:38, 21 January 2026 (UTC)
- The community wishlist is very underattended. Last I checked, it consisted mostly of ~5 editors from enwiki. That is the consequence of turning an annual event with all its fanfare into an ongoing one with zero advertising and zero community awareness. Toadspike [Talk] 08:58, 21 January 2026 (UTC)
- What Toadspike said, I think this is the best opportunity at the moment we (the community) have of influencing what the WMF works on. Sohom (talk) 12:25, 21 January 2026 (UTC)
- I suppose, but a new process with the same purpose as an existing process ignoring that existing process doesn't give me much hope for the new process. CMD (talk) 12:48, 21 January 2026 (UTC)
- The two processes have existed side by side for a long time. I think the wmf seeking community feedback on annual planning is a good thing. We should encourage and reward the wmf whenever they solicit community feedback (i.e. give volunteers a seat at the table). –Novem Linguae (talk) 16:30, 21 January 2026 (UTC)
- That, the annual planning process has been around for a while running alongside the Community Wishlist but has typically been a opaque process from the volunteers POV. Last year, besides PTAC's "focus on mobile editing" recommendation, there wasn't community input. This time around, after receiving feedback about it's opaqueness, they are trying to open it up further (to my understanding). Sohom (talk) 17:53, 21 January 2026 (UTC)
- The two processes have existed side by side for a long time. I think the wmf seeking community feedback on annual planning is a good thing. We should encourage and reward the wmf whenever they solicit community feedback (i.e. give volunteers a seat at the table). –Novem Linguae (talk) 16:30, 21 January 2026 (UTC)
- I suppose, but a new process with the same purpose as an existing process ignoring that existing process doesn't give me much hope for the new process. CMD (talk) 12:48, 21 January 2026 (UTC)
- The wishlist is underattended because there are no followups. Whatever the participation is, the developed routinely say they are not interested / do not have resources working on the projects community voted for. After the top voted proposal was turned down a few years back, I lost any interest in voting for new proposals. Ymblanter (talk) 16:34, 22 January 2026 (UTC)
- The leadership has changed significantly since then. The current status quo is that stuff on the wishlist do get worked on, but there isn't too much engagement with the process from the community (not the communities fault though) -- this is something I have been wanting to change, but progress has been slow. Sohom (talk) 11:52, 23 January 2026 (UTC)
- What Toadspike said, I think this is the best opportunity at the moment we (the community) have of influencing what the WMF works on. Sohom (talk) 12:25, 21 January 2026 (UTC)
- The community wishlist is very underattended. Last I checked, it consisted mostly of ~5 editors from enwiki. That is the consequence of turning an annual event with all its fanfare into an ongoing one with zero advertising and zero community awareness. Toadspike [Talk] 08:58, 21 January 2026 (UTC)
WMF announces new AI partnerships with Amazon, Meta, Microsoft, Perplexity...
Reported in TechCrunch earlier today: https://techcrunch.com/2026/01/15/wikimedia-foundation-announces-new-ai-partnerships-with-amazon-meta-microsoft-perplexity-and-others/. - Shearonink (talk) 19:00, 15 January 2026 (UTC)
- On a first read very few details of the partnerships seem to be given. I just hope that it has been remembered that the WMF does not own the copyright to Wikipedia, so doesn't have the right to give it away or sell it. Phil Bridger (talk) 19:40, 15 January 2026 (UTC)
- It can't sell the copyright, but it can sell the content. Anyone can. Our license allows for commercial use and that is a feature of this great project. That's not really what Enterprise is doing, though. It's simply providing a more efficient way for these companies to access the content they're using anyways. Toadspike [Talk] 20:25, 15 January 2026 (UTC)
- I mean, for $500 I will sell you a piece of paper saying I authorize you to say the word "the". jp×g🗯️ 09:04, 18 January 2026 (UTC)
- From what I understand, these partnerships concern Wikimedia Enterprise, which provides AI companies with large-scale API access. Chaotic Enby (talk · contribs) 20:06, 15 January 2026 (UTC)
- Has the Foundation thought about the optics of this from an ethical standpoint? As the "hot" Gaza war is slowing I would expect to see more being uncovered about the partnerships tech companies have undertook with the IDF, giving them AI technology and possibly making them complicit in a genocide. Its not a good look if the WMF is happy to give those companies tools to supercharge their AI, especially if its used for any future military purposes -- which, given the current state of the US on foreign policy, may drastically expand. ✨ΩmegaMantis✨(they/them) ❦blather | ☞spy on me 23:58, 15 January 2026 (UTC)
- Those companies, whatever you think of them, are taking Wikipedia's content anyway (and can't be stopped from doing so). As far as I can tell this is simply a way to persuade them to pay for what they are already taking by giving them access to more efficient tools. Mike Christie (talk - contribs - library) 00:15, 16 January 2026 (UTC)
- Definitely, and I agree that the strategy's goal is to turn this taking of content into an opportunity to fund our projects. I just wonder if the Foundation has thought about how they are now active clients in large technology companies for the purpose of AI construction, which is used for military purposes, as opposed to a general font of knowledge agnostic to use. ✨ΩmegaMantis✨(they/them) ❦blather | ☞spy on me 00:21, 16 January 2026 (UTC)
- I don't think you can really separate the two out. Every AI company would love a lucrative defense contract. voorts (talk/contributions) 00:34, 16 January 2026 (UTC)
- That sounds like a capitalism problem more than an AI-specific problem. Chaotic Enby (talk · contribs) 01:23, 16 January 2026 (UTC)
- I don't think you can really separate the two out. Every AI company would love a lucrative defense contract. voorts (talk/contributions) 00:34, 16 January 2026 (UTC)
- Definitely, and I agree that the strategy's goal is to turn this taking of content into an opportunity to fund our projects. I just wonder if the Foundation has thought about how they are now active clients in large technology companies for the purpose of AI construction, which is used for military purposes, as opposed to a general font of knowledge agnostic to use. ✨ΩmegaMantis✨(they/them) ❦blather | ☞spy on me 00:21, 16 January 2026 (UTC)
- Those companies, whatever you think of them, are taking Wikipedia's content anyway (and can't be stopped from doing so). As far as I can tell this is simply a way to persuade them to pay for what they are already taking by giving them access to more efficient tools. Mike Christie (talk - contribs - library) 00:15, 16 January 2026 (UTC)
- We're on the front page of apnews.com now too: https://apnews.com/article/wikipedia-internet-jimmy-wales-50e796d70152d79a2e0708846f84f6d7
- I'm not sure "Wikipedia inks AI deals with Microsoft, Meta and Perplexity as it marks 25th birthday" is a very good headline for us. I don't really want the public to associate us with either AI or big tech, nor to associate our 25th birthday with these things. –Novem Linguae (talk) 05:54, 16 January 2026 (UTC)
I don't really want the public to associate us with either AI or big tech
-- Wikipedia has been preferred by Google in search results for many years now, that's why Wikipedia is the encyclopedia and not Everipedia or Citizendium or any of the others. That's why the others can't compete. Also, Wikipedia is preferred by Siri (Apple), Alexa (Amazon), and all the LLMs. "Big tech" has donated hundreds of millions of dollars and given us the monopoly on search results in almost every search platform in use. I'm sorry to break the news: Wikipedia is part of big tech, it only exists because of big tech, and it would not exist without big tech's support. And why do you think big tech supported Wikipedia all these years? Because they use it to make money. LLM is just the latest iteration of that, but they used Wikipedia to make Google search, Siri, and Alexa better, too. We are volunteering to write content that is sold by big tech to the world. That's what we've been doing for 25 years, FYI. Levivich (talk) 16:51, 22 January 2026 (UTC)- ...Oh, and if we want to change that, we should change the license from WP:CC-BY-SA to CC-BY-SA-NC, but the community so far has been against doing that. Perhaps because the community realizes that Wikipedia wouldn't survive if big tech couldn't sell our content for profit. Levivich (talk) 16:55, 22 January 2026 (UTC)
- Agree with some others above that while the core idea behind Enterprise is reasonable, the timing is very odd, especially given the importance that brand management seems to have. CMD (talk) 06:06, 16 January 2026 (UTC)
- Also fully agree with that. Not ideal, and perplexed about the choice of announcing it for the 25th birthday. Chaotic Enby (talk · contribs) 09:22, 16 January 2026 (UTC)
- Shall I state the obvious as say this should have been discussed with the community? Not that I expected the WMF to, of course... Cremastra (talk · contribs) 18:32, 18 January 2026 (UTC)
- The timing of this is terrible. With all the terrible decisions the WMF has been making recently, I'm nearly convinced they're either trying to kill wikipedia or are being run by people who see us and our work as free labor for their big tech buddies. Is there any way for a wikipedia to break ties with the WMF? I think it's clear they don't have our best interests in mind mgjertson (talk) (contribs) 15:25, 21 January 2026 (UTC)
- This misrepresentation of our values to the public is frustrating, but certainly does not rise to the level of breaking ties over. Let's turn down the temperature a bit. –Novem Linguae (talk) 16:25, 21 January 2026 (UTC)
- Fully agree. We may not always see eye to eye, but more communication is always preferable to breaking ties. Chaotic Enby (talk · contribs) 17:46, 21 January 2026 (UTC)
- This misrepresentation of our values to the public is frustrating, but certainly does not rise to the level of breaking ties over. Let's turn down the temperature a bit. –Novem Linguae (talk) 16:25, 21 January 2026 (UTC)
- well it's either that the WMF sells them API access and makes a couple of bucks or they scrape all of Wikipedia manually and cost the WMF a bunch of money
- in both cases, they end up with their content but in the current case, the WMF profits from it Laura240406 (talk) 23:36, 23 January 2026 (UTC)
Very, very bad timing to make this announcement now. The message on W25 should have been the human aspect of Wikipedia, not "AI!!!". Some very worrying statements in that AP article as well.
- "While AI isn’t good enough to write Wikipedia entries from scratch, it could, for example, be used to update dead links by scanning the surrounding text and then searching online to find other sources." Please no! At worst post such things to the talk page, but don't let AI loose on articles to add sources. There is no guarantee at all that these would be good sources for the content and not unreliable ones, citogenesis ones, or hallucinated ones. Fram (talk) 09:58, 16 January 2026 (UTC)
- Best explainer I've read is this https://www.citationneeded.news/free-and-open-access-in-the-age-of-generative-ai/. Nthep (talk) 10:00, 16 January 2026 (UTC)
- On second and third reads I still can't see any details of the partnership agreements. If the WMF wants to avoid wild speculation about what may be in them then it should be transparent and publish the agreements. If "commercial confidentiality" prevents that then they shouldn't have been signed. Phil Bridger (talk) 11:48, 16 January 2026 (UTC)
- Hi @Phil Bridger. I've got an response in the FAQ page about "what's in the contracts?", if you're interested. Short answer is quite practical things like duration, jurisdiction, uptime/SLA obligations. Many of the things which normally go in such contracts like copyright or content-quality guarantees are not there becuase WMF doesn't own the copyright or have editorial control over the content. This is just part of why it's not a content license but a service contract for access to a high-speed pipeline of data.
- In terms of financial transparency, you might also like to read the most recent annual financial report of the project - covering the USA fiscal year 2024-25.
- I hope that helps. For further questions/details, I suggest you come over to the talkpage on Meta. LWyatt (WMF) (talk) 18:44, 16 January 2026 (UTC)
Hello all,
Here on Meta wiki at the talkpage for the Enterprise API project is where this announcement is discussed. With links to technical documentation, financial reports, operating principles, etc.
Significantly, is the fact that the mainstream media frequently misrepresent and simplify this to being a "licensing" deal. It is not.
As mentioned by many - the content is already licensed freely, and as a consequence WP content is used to train LLMs already (as we all know). This announcement refers to these companies now being customers of the high-speed/volume API service - where they can obtain the same Wikipedia (and sister projects) content, but in a metadata structure more tailored for repurposing (and with Service-level agreements about uptime etc). The API is open source, and the feed is also available for free, for anyone, as per our culture and principles. Moving high-speed/volume users over to this "enterprise grade" service helps address the issue of heavy-impacts on the public infrastructure by crawlers bots. So, now major AI companies can pay for their own heavy usage, rather than being subsidised by our donors. The water's the same, but they're paying for a dedicated pipe - freeing up space for the general public who want to draw water from the well.
Moreover, having these formalised relationships now also means we can have a more proactive conversation with major external reusers of content about such issues as consistent attribution.
If you've any questions after having read the documentation at the link I provided above, please contact me via the project's talkpage on Meta! LWyatt (WMF) (talk) 14:21, 16 January 2026 (UTC)
- And whose idea was it to make this the big announcement for the 25th birthday? It feels disrespectful to your editors and like bad PR to your readers. Fram (talk) 14:26, 16 January 2026 (UTC)
- The "announcement" of this list of new customers was one paragraph within a much longer press-release about all the things that Wikimedians/WMF are doing as part of this Birthday. Many people are - rightly interested in "who" is a partner of this project and so this announcement is also an important display of transparency. LWyatt (WMF) (talk) 14:35, 16 January 2026 (UTC)
- "one paragraph within a much longer press-release", one of the three subtitles, and one of the two things highlighted by the WMF right at the top ("New video docuseries celebrates the humans who make knowledge on Wikipedia possible; new tech partnerships highlight Wikipedia's value in age of AI."
- But I see you also did this: "In honor of this milestone, we interviewed a few volunteer editors from around the world about what moves them to contribute to Wikipedia’s pages. " Surprise, the co-founder, who hasn't done any "volunteer editing" worth mentioning in the last decade or so (in a positive way at least) is one of the 8. Again, quite a show of respect for actual editors. Fram (talk) 14:46, 16 January 2026 (UTC)
- The "announcement" of this list of new customers was one paragraph within a much longer press-release about all the things that Wikimedians/WMF are doing as part of this Birthday. Many people are - rightly interested in "who" is a partner of this project and so this announcement is also an important display of transparency. LWyatt (WMF) (talk) 14:35, 16 January 2026 (UTC)
- I've responded on the Meta talkpage, thank you very much! Chaotic Enby (talk · contribs) 14:36, 16 January 2026 (UTC)
- Not trying to be aggressive with this point, but it would be helpful for communication to get less boilerplate responses on this noticeboard. No concerns were raised above about this being a "licensing deal". The only mention of licensing was that this action was explicitly permitted by our licence. Meanwhile, an issue that was raised multiple times was not addressed before a follow up question. This gives off the impression, whether true or not, that the existing discussion has not been read or engaged with. CMD (talk) 15:35, 16 January 2026 (UTC)
- Hi @Chipmunkdavis. I didn't mean to come across as "boilerplate" - especially since I wrote that response specifically in the edit window on this page (not copy-pasted from some pre-prepared list of replies) so it is literally the opposite - a bespoke response! And yeah - I've seen a lot of media (and subsequently people reading about the project via that media reporting) referring to this as a 'licensing' deal, so I'm predisposed to notice and react to that critique!
- If you're noting that the core concern raised in this comment thread is one of timing rather than content of this announcement... Well:
- The reason for the timing is that - as per the naming of customers policy of the WMF - We WANT to name all customers (transparency) but cannot always do so (privacy). The fact of this birthday milestone meant there was an opportunity for all of these organisations also wanted to be able to show their long-term support for Wikimedia - both to financially support it, and technicaly to ingest the content in an ethical/official way. So, this was an excellent moment for them them all to do so, simultaneously.
- It is not the 'only' or 'biggest' part of the press-release, nor the most important part of the birthday celebrations - but it is the thing that some (not all) journalists chose to highlight. I've been collecting a list of the news articles that focus on this story over on the 'enterprise' talkpage, but there are many other news stories which discuss other aspects of the 25th birthday celebrations. LWyatt (WMF) (talk) 18:38, 16 January 2026 (UTC)
- Apologies if I'm mistaken, but it sounds that the reason was 'free' advertising for those companies? Kowal2701 (talk) 23:13, 16 January 2026 (UTC)
- It was a single paragraph in a press release. That would be a pretty bad form of advertising if that was the intent. voorts (talk/contributions) 01:02, 17 January 2026 (UTC)
- Lotta headlines though, idk what else “show their long-term support for Wikimedia” could mean other than brand management Kowal2701 (talk) 01:06, 17 January 2026 (UTC)
- It's big news. Although, as has been clarified, this isn't a licensing deal, who and for what AI companies are paying is being heavily litigated and closely watched. voorts (talk/contributions) 01:26, 17 January 2026 (UTC)
- Lotta headlines though, idk what else “show their long-term support for Wikimedia” could mean other than brand management Kowal2701 (talk) 01:06, 17 January 2026 (UTC)
- It was a single paragraph in a press release. That would be a pretty bad form of advertising if that was the intent. voorts (talk/contributions) 01:02, 17 January 2026 (UTC)
- Apologies if I'm mistaken, but it sounds that the reason was 'free' advertising for those companies? Kowal2701 (talk) 23:13, 16 January 2026 (UTC)
- If these are simply purchases of the WMF's Enterprise package then that's fine. The word "partnership" confused me, but it seems that any deal that was done in the last year or two is a "partnership" and somehow linked to our 25th anniversary. This is just marketing hype. Phil Bridger (talk) 17:44, 16 January 2026 (UTC)
- Yeah, "partnership" is just common vocab for this kind of thing. But moreover it's actually an attempt to point out that this isn't a question of a one-time payment for a product (merely a temporary and transactional thing). It's actually building long-term relationships where external organisations have contractually engaged in the development and use of this infrastructure. This is more than just revenue - this means that we can now talk on a regular basis with their engineering teams about, for example, how attribution could be improved. This is about moving from our historical basis of agnosticism of reusers - knowing that big-tech use our content but not overtly assisting them to do it "well" - to being proactive in getting them to [financially and technically] invest in doing so in a sustainable manner. This helps their customers to get access to attributed Wikimedia content accurately. Ultimately, it is in their interest that our content is diverse, up-to-date, cited, accurate, and available in their user's native language.
- So... although "partnership" is a wolly word, it is indeed more accurate than merely calling them "customers" - even if that nuance doesn't come across in a press-release or news-story. LWyatt (WMF) (talk) 18:24, 16 January 2026 (UTC)
- Do you really think that the owners of these companies see us in any more than transactional terms? When I was working for various software companies I spewed the party line that deals were partnerships, as you have to, but I knew that they weren't. Phil Bridger (talk) 19:50, 16 January 2026 (UTC)
- In more concrete terms, it could be amazing if we were now able to get concrete reassurances regarding issues like attribution. We do see them as partners, but we want guarantees that this goes both ways and that they're actually willing to negotiate something there, rather than just saying that for the sake of signing a contract. Chaotic Enby (talk · contribs) 00:03, 17 January 2026 (UTC)
- They don't do attribution for clearly copyrighted work, nothing indicates that they will do any attribution for Wikipedia. They pay to get easy access without bringing down our servers, that's about it, and in return they get major headlines on what should have been a celebration of 25 years of volunteer-driven content dissemination (Wikipedia, Commons, ...), and give many people outside Wikipedia the wrong impression that Wikipedia has capitulated for AI as well. Fram (talk) 10:12, 19 January 2026 (UTC)
- In more concrete terms, it could be amazing if we were now able to get concrete reassurances regarding issues like attribution. We do see them as partners, but we want guarantees that this goes both ways and that they're actually willing to negotiate something there, rather than just saying that for the sake of signing a contract. Chaotic Enby (talk · contribs) 00:03, 17 January 2026 (UTC)
- Do you really think that the owners of these companies see us in any more than transactional terms? When I was working for various software companies I spewed the party line that deals were partnerships, as you have to, but I knew that they weren't. Phil Bridger (talk) 19:50, 16 January 2026 (UTC)
- I think it's a good thing these deals were made. If they're going to be using our content anyways, might as well have them pay for it. I am a bit curious as to how much these companies are paying for access however, though I suppose that would be revealed in the next financial report. ARandomName123 (talk)Ping me! 07:57, 17 January 2026 (UTC)
- The comments I've seen online from Wikipedia's user-base and donors?...they are really really not happy. There is a lot of anger about this partnership or whatever you want to call it. And maybe it looks great and is great and yes all these companies are taking the WP content anyway (that we all create and have created), but people feel betrayed and oh MAN the optics sure do suck. - Shearonink (talk) 02:09, 18 January 2026 (UTC)
- @Shearonink, This is less optics, more survival. The alternative to the partnership (which as mentioned above is just a Wikimedia Enterprise subscription where they give Wikimedia money to offset the load caused on our servers at a high level) in this context is to have significantly degraded experience as these AI companies scrape Wikipedia's content for profit anyway while decimating our bandwidth to serve actual humans. Atleast this way, we can tell me "dude, if you scrape anything on Toolforge.org, we are kicking you out of the subscription". Sohom (talk) 00:36, 19 January 2026 (UTC)
- I think WMF needs to be careful with its PR strategy. The kind of messaging that will generate Wikimedia Enterprise clients may not be the same kind of messaging that will present our values correctly to the general public. Headlines such as "Wikipedia inks AI deals with Microsoft, Meta and Perplexity as it marks 25th birthday" plant a seed in the public's mind that we are all about inking deals with big tech and embracing AI, which I would argue are probably the opposite of our values. –Novem Linguae (talk) 02:15, 19 January 2026 (UTC)
- Agreed. - Shearonink (talk) 03:16, 19 January 2026 (UTC)
- Yes and no. I see better where you are and can agree that the PR should have been handled better and WMF should take this as a bit of a learning experience, but we also need to keep in mind that TechCrunch in particular (and many journalists in this industry) are "AI-pilled" and have a interest in reading text to be more favorable towards big-tech/AI. Misrepresentation/over simplification is not uncommon even amongst the best RS in the tech industry (I say this as somebody who has written articles about tech, even on a best day, I've found blogposts that are often more factually accurate than what Tech RS churns out). Sohom (talk) 11:04, 19 January 2026 (UTC)
- Why do you suppose journalists are "AI-pilled"? And can you give an example? –Novem Linguae (talk) 18:43, 19 January 2026 (UTC)
- TechCrunch (which operates in the startup space) is not known for being AI-critical at all. The first article I can see on their site is which needs to be much much more critical of AI, similarly, the journalist that wrote the Wikipedia piece has also written which hides Alexa's AI agent's failing in one small sentence at the end that is immediately followed by a Amazon statement that the complaints are overrepresented. Sohom (talk) 22:51, 19 January 2026 (UTC)
- Because AI is the current moneymaker and that is the point of running a business. Shareholders have eaten the AI hype hook line and sinker. Journalists can't afford to be critical to it mgjertson (talk) (contribs) 19:23, 26 January 2026 (UTC)
- Why do you suppose journalists are "AI-pilled"? And can you give an example? –Novem Linguae (talk) 18:43, 19 January 2026 (UTC)
- Yes and no. I see better where you are and can agree that the PR should have been handled better and WMF should take this as a bit of a learning experience, but we also need to keep in mind that TechCrunch in particular (and many journalists in this industry) are "AI-pilled" and have a interest in reading text to be more favorable towards big-tech/AI. Misrepresentation/over simplification is not uncommon even amongst the best RS in the tech industry (I say this as somebody who has written articles about tech, even on a best day, I've found blogposts that are often more factually accurate than what Tech RS churns out). Sohom (talk) 11:04, 19 January 2026 (UTC)
- Fully agree here. There is a big difference between the partnership (which is necessary) and the communication around it (which can be controlled). Chaotic Enby (talk · contribs) 02:30, 19 January 2026 (UTC)
- Yes. - Shearonink (talk) 03:16, 19 January 2026 (UTC)
- Agreed. - Shearonink (talk) 03:16, 19 January 2026 (UTC)
- I get all that, but the optics, the PR, are bad. Go read some of the general public's comments, like at the TechCrunch article and elsewhere and take them all in. People are upset. Wikipedia's supporters are upset. Our donors are upset. - Shearonink (talk) 03:16, 19 January 2026 (UTC)
- I think WMF needs to be careful with its PR strategy. The kind of messaging that will generate Wikimedia Enterprise clients may not be the same kind of messaging that will present our values correctly to the general public. Headlines such as "Wikipedia inks AI deals with Microsoft, Meta and Perplexity as it marks 25th birthday" plant a seed in the public's mind that we are all about inking deals with big tech and embracing AI, which I would argue are probably the opposite of our values. –Novem Linguae (talk) 02:15, 19 January 2026 (UTC)
- @Shearonink, This is less optics, more survival. The alternative to the partnership (which as mentioned above is just a Wikimedia Enterprise subscription where they give Wikimedia money to offset the load caused on our servers at a high level) in this context is to have significantly degraded experience as these AI companies scrape Wikipedia's content for profit anyway while decimating our bandwidth to serve actual humans. Atleast this way, we can tell me "dude, if you scrape anything on Toolforge.org, we are kicking you out of the subscription". Sohom (talk) 00:36, 19 January 2026 (UTC)
- The comments I've seen online from Wikipedia's user-base and donors?...they are really really not happy. There is a lot of anger about this partnership or whatever you want to call it. And maybe it looks great and is great and yes all these companies are taking the WP content anyway (that we all create and have created), but people feel betrayed and oh MAN the optics sure do suck. - Shearonink (talk) 02:09, 18 January 2026 (UTC)
- The timing is just awful and shouldn't have been included in the 25th anniversary event at all. It's causing a large amount of the public to consider Wikipedia to now be taken by AI companies. Even when that's not true, the optics are as such. Whatever marketing person decided this should be at all done now is terrible at their job. SilverserenC 18:58, 19 January 2026 (UTC)
- Hi Silver,
- As I wrote above, the fact of this birthday milestone meant there was a positive opportunity for all of these organisations who wanted to be able to show their long-term support for Wikimedia - both to financially support it, and technically to ingest the content in an ethical/official way - to do so. So, this was an excellent moment for these companies to do so. As per the naming of customers policy of the WMF, transparency of these names is something we consistently push for (and is a frequent [and very valid!] request from the community), so getting their simultaneous consent to be named publicly was great. It is my professional opinion that it would not have been possible to get permission for naming most of these new names outside of the context of the birthday. Believe me, we tried.
- It is not the 'only' or 'biggest' part of the birthday press-release, nor the most important part of the birthday celebrations, but it is the thing that some (not all) journalists chose to fixate on. Which is - as people have pointed out here - not desirable because the focus should have been on the knowledge itself, and the volunteers who curate it. In the end I feel we have a bit of a "damned if you do, damned if you don't" situation where two ideals partially conflicted: transparency (of the finances) and clarity (of the message).
- But more fundamentally, while it is understandable that the general public might not grasp the nuances of free-licensing (which meant that all Wikimedia content was already being used in AI/LLM training for commercial purposes without needing further permission), some of the articles I've seen misrepresented the fact of this API service with the outright falsehoods of this being a licensing deal. WMF Comms team have done a valiant effort in successfully request some of the worst-offending and highest-visibility news stories be fixed. Much like the work that goes on at WP:Redirects for discussion, the results of that tiring work is often invisible to the end-user.
- I hope this comment helps explain how/why this announcement occurred at this specific time, and that overall you feel that the benefits outweigh that concern: We can now say to the world that big-tech is indeed "paying their own way" for their heavy infrastructure cost and investing (financially and technically) in our long term existence (and improved attribution, improved information-integrity of downstream reuse), rather than Wikimedia's donors subsidising their business model.
- If you've any specific questions or would like to discuss further, I encourage you to come over to the project talkpage on meta wiki. LWyatt (WMF) (talk) 14:53, 20 January 2026 (UTC)
- So these companies wanted to show their long-term support and their interest to get our data in an ethical way, but only if they were included in the press releases for the 25th birthday? What an incredible way to show how ethical you are and how long-term that support is! Fram (talk) 15:32, 20 January 2026 (UTC)
- @Fram In this context, I think
It is my professional opinion that it would not have been possible to get permission for naming most of these new names outside of the context of the birthday. Believe me, we tried.
means that they would not have allowed disclosure outside of a press release and WMF in this context, prioritized disclosure over having shadowy backers that were unknown to the community. "Leaked Records Reveal Wikimedia Foundation Quietly Funded by Major AI Firms" is probably a worse PR problem to have in this scenario. Sohom (talk) 16:12, 20 January 2026 (UTC)- My issue is not with having a press release about this, but that this apparently had to be included in the 25th birthday celebrations or they wouldn't have agreed to it. Which is basically blackmailing WMF into "we want to get attention during the 25th birthday celebrations" (which worked perfectly for these companies). Calling this "long-term support" and doing things in an ethical way (or calling them "partners" in official communications) when it looks more like getting cheap exposure on the reporting of the otherwise ad-free Wikipedia, is dubious. Your "worse PR problem" is a false dilemma. Fram (talk) 16:20, 20 January 2026 (UTC)
- @Fram In this context, I think
- Your insinuation that the disclosure of the companies' names was contingent on tying it to the anniversary, if true, is less reassuring than is unsettling. Nardog (talk) 01:19, 21 January 2026 (UTC)
- So these companies wanted to show their long-term support and their interest to get our data in an ethical way, but only if they were included in the press releases for the 25th birthday? What an incredible way to show how ethical you are and how long-term that support is! Fram (talk) 15:32, 20 January 2026 (UTC)
- I think that this just demonstrates that the role WMF sees itself as having (as large as possible) conflicts with the role many editors here wish it to have (as small as possible). I don't think we'll get very far by talking in this thread. Personally I give some of my time to Wikipedia, not to brand Wikipedia, or any brand for that matter. Phil Bridger (talk) 19:06, 20 January 2026 (UTC)
Soon we will able to breathe the word "realistic medieval world" and an AI will be able to comb all the Wikipedia articles and sources related to this topic and generate an entire reconstructed reality of the past and it wouldn't be possible if Wikipedia hadn't thoroughly maintained and built up the knowledge over 25 years, especially the link to (archived) sources so the AI creation tools can simulate an entire reality as realistically as possible while sticking to history and TRUE facts. Slyceth (talk) — Preceding undated comment added 01:24, 22 January 2026 (UTC)
- I hope that that day will come when I'm no longer here to experience it. Even so, can't we do better than the actual medieval world? Phil Bridger (talk) 10:33, 22 January 2026 (UTC)
- And I hope a day will come when people learn to write posts online that use sufficient punctuation. Cremastra (talk · contribs) 16:25, 22 January 2026 (UTC)
Feedback on next iteration of PTAC
Folks at the Wikimedia Foundation are proposing a new iteration of the Product and Technology Advisory Council for 2026 and are seeking community feedback on the same until February 28th. Sohom (talk) 03:57, 17 January 2026 (UTC)
- Thanks a lot! Replied on the talk page. Chaotic Enby (talk · contribs) 05:15, 17 January 2026 (UTC)
- Can anyone point to any concrete results from the proposals generated the last time we did this? Serious question, not trying to be snarky. I am genuinely wondering if actions were taken that I never heard about. --Guy Macon (talk) 16:05, 25 January 2026 (UTC)
- To quote myself from the metawiki talk page,
there has also been growth in the right direction with WMF members engaging with the community more directly through discord, onwiki at en:WP:VPT before and after proof of concepts are being built (using a consistent scheme to denote at what stage experiments are) and more recently inviting community comments on the Annual plan before it gets written
Sohom (talk) 17:51, 25 January 2026 (UTC)
- To quote myself from the metawiki talk page,
- Can anyone point to any concrete results from the proposals generated the last time we did this? Serious question, not trying to be snarky. I am genuinely wondering if actions were taken that I never heard about. --Guy Macon (talk) 16:05, 25 January 2026 (UTC)

