Hac pagina scriptorium Vicifontis est. Nunc iam sunt20 049 paginae. Hodiedies Iovis, 19 februarii 2026.
(DE) Neue Nachrichten dürfen auf Latein, Französisch, Englisch oder Italienisch gestellt werden. (EN) You can write a new message in Latin, French, English or Italian. (FR) Vous pouvez écrire en latin, en français, en italien ou en anglais. (IT) Potete scrivere in latino, italiano, francese o inglese.
(ALIAE)Aliis linguis uti potes, sed noli iubere nos facile eas intellegere
Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, interface administrator, etc.) was adopted byglobal community consensus in 2013. According to this policy, thestewards are reviewing administrators' activity on all Wikimedia Foundation wikis with no inactivity policy. To the best of our knowledge, your wiki does not have a formal process for removing "advanced rights" from inactive accounts. This means that the stewards will take care of this according to theadmin activity review.
We have determined that the following users meet the inactivity criteria (no edits and no logged actions for more than 2 years):
These users will receive a notification soon, asking them to start a community discussion if they want to retain some or all of their rights. If the users do not respond, then their advanced rights will be removed by the stewards.
However, if you as a community would like to create your own activity review process superseding the global one, want to make another decision about these inactive rights holders, or already have a policy that we missed, then please notify thestewards on Meta-Wiki so that we know not to proceed with the rights review on your wiki. Thanks,EPIC (disputatio)22:22, 22 Februarii 2025 (UTC)Reply
Request for updating the text of the Clementine Bible
Fortunately, the list of changes made since the import of on Wikisource can be foundhere. There is alsoa repository (although I am not sure if it is up to date).
TheWikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.
All traffic will switch on19 March. The switch will start at14:00 UTC.
Unfortunately, because of some limitations inMediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
A banner will be displayed on all wikis 30 minutes before this operation happens. This banner will remain visible until the end of the operation.
You will be able to read, but not edit, all wikis for a short period of time.
You will not be able to edit for up to an hour on Wednesday 19 March 2025.
If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
The proposed modifications to theUniversal Code of Conduct Enforcement Guidelines and the U4C Charterare now on Meta-wiki for community notice in advance of the voting period. This final draft was developed from the previous two rounds of community review. Community members will be able to vote on these modifications starting on 17 April 2025. The vote will close on 1 May 2025, and results will be announced no later than 12 May 2025. The U4C election period, starting with a call for candidates, will open immediately following the announcement of the review results. More information will be posted onthe wiki page for the election soon.
Please be advised that this process will require more messages to be sent here over the next two months.
Hello everyone, I am excited to share news of an upcoming online event calledWikidata and Sister Projects celebrating the different ways Wikidata can be used to support or enhance with another Wikimedia project. The event takes place over 4 days betweenMay 29 - June 1st, 2025.
We would like to invite speakers to present at this community event, to hear success stories, challenges, showcase tools or projects you may be working on, where Wikidata has been involved in Wikipedia, Commons, WikiSource and all other WM projects.
If you are interested in attending, pleaseregister here.If you would like to speak at the event, please fill out this Session Proposal template on theevent talk page, where you can also ask any questions you may have.
TheUniversal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review of the EG and Charter was planned and implemented by the U4C. Further information will be provided in the coming months about the review of the UCoC itself. For more information and the responsibilities of the U4C, you mayreview the U4C Charter.
Please share this message with members of your community so they can participate as well.
Latest comment:abhinc 7 menses18 comments3 people in discussion
On EN wikisource, they have a template {{longs}} to produceſ on the transcription page, and by default,s on the ebook page. users on EN WS can toggle these on and off.
In this book,De principe, there are a number of unusual characters that could do with toggling:ſ (s); ß (ss); ẽ (en / em) ũ (un / um) æ (ae) ę (ae) õ (on / om) ã (an / am) œ (oe). (formula:ls already exists here for ſ, and some other characters semi-implemented atCategoria:Formulae litterarum but the toggling is not switched on.)
In order to implement this:
(1) What would LA WiCategoria:Formulae litterarumkisource need to enable for user toggling of special characters?
Personally I think it would be somewhat useful to implement the toggle feature only for æ and œ, since of all the ligatures they are the only ones that carry some meaning (that ae or oe in that word is a diphthong) and the only ones that easily show up in search results and correctly displayed in web-browsers.
Note that both English and Italian wikisources in their transcription guidelines take in consideration the ability of both modern readers and search engines to correctly interpret the character shown (seeen:Wikisource:Style guide/Orthography andit:Wikisource:Convenzioni di trascrizione). Though it would be useful to write rules specific to the Latin wikisource.
In regards to theDe principe it would be appropriate to encode the text in a way that we do not lose your work of accurately transcribing the above characters, while still showing to the end user a normalized form. My edit was trying to achieve this with the templates currently in wikisource.
From a technical standpoint, it would be useful to have a general template not specific to any character that could be used both inad hoc situations, and in creating other templates.
Also if such a template is created for abbreviations it should behave differently from the long s and ligatures, since 1) the text displayed is context dependent, and 2) it is common use in diplomatic transcriptions to show the abbreviated characters in parentheses (so I were taught in paleography class).
To give an example of point 2 from the text (page 45, line 11):
I agree something adhoc would be helpful. The template would need to specify
the text as-is and
the modernised version
and hopefully there would be a system to pick up which to display.
In terms of the display: this could be the js system, perhaps adapted, that we have on en.ws, or possibly it could be an adjustment to the page templates set up, to allow two different books, or sets of pages, to be presented. This would have the advantage that exports would facilitate both (IDK but suspect that exports support the default rather than user choice).JimKillock (disputatio)15:48, 3 Maii 2025 (UTC)Reply
I have set out this information in atable including information about dictionary lookups and likely search engine issues. In short, from a user perspective, all the characters can be problematic, but æ and œ work within Alpheios for dictionary lookups, so are a bit more tolerable than the others from a default perspective. However I think it is useful tobe able to see and use the originals for some people, eg those practicing reading Renaissance scans etc; or researchers or academics looking to use source texts.JimKillock (disputatio)16:09, 3 Maii 2025 (UTC)Reply
I’m afraid it is based on #"https://en.wikisource.org/wiki/MediaWiki:Gadget-Visibility.js" title="en:MediaWiki:Gadget-Visibility.js">en:MediaWiki:Gadget-Visibility.js
@Alex brollo checking in whether we can implement this, or find another solution. I am holding off further changes until I know how to proceed - but I am sure there should be a way to do this!JimKillock (disputatio)20:40, 19 Maii 2025 (UTC)Reply
OK, I have developed templates as this is holding up other people's work. I have based each template on the existingformula:ls, and avoid duplicating those that already exist using the same method atCategoria:Formulae litterarum. Meantime if anyone has further thoughts about using Visibility Gadget or going another way, I would be very grateful.JimKillock (disputatio)18:02, 17 Iunii 2025 (UTC)Reply
@SZC 03 I have made a very basic template for flexible character switching atFormula:Scr; this returns the first entry on the book page, and the second in main space, eg {{scr|qꝫ|que}} would work the same as {{que}}.
However there is advice on ENWS not to use characters but use HTML entities for CSS reasons, so it is probably better for users to use specific templates. For example, I also created {{po}} which allows a user to decide what it might best represent, eg {{po|;}} or {{po|?}}.
In general, using set templates like {{que}}, {{em}}, {{um}}, {{etc}} is much easier for proofing, so I think I will continue to add these where it seems useful.JimKillock (disputatio)08:29, 24 Iunii 2025 (UTC)Reply
Hi folks, so that you know, I have made something of a workaround to be able to enable these features, which works well enough for me. I will perhaps add some guidance somewhere. What I have done:
Installed the font Garamontio, as it has the qꝫ character, and all the possible ligatures
The second script looks for the various spans with the css style typographic-long-s, and replaces the characters as appropriate. This seems to work surprisingly well, Garamontio does all of the discretionary ligatures etc, and is a very well designed font (fork of EB Garamond, with some extra touches useful here). The issue is of course that this applies to the whole of Latin Wikisource all of the time.JimKillock (disputatio)18:35, 25 Iunii 2025 (UTC)Reply
Thanks @SZC 03; my list of scribal transformations has got quite long tho. And I need to check on the possible logic of it, some needs to hide and unhide, rather than search and replace.JimKillock (disputatio)08:27, 11 Iulii 2025 (UTC)Reply
We will be enabling the new Charts extension on your wiki soon!
Latest comment:abhinc 9 menses1 comment1 person in discussion
(Apologies for posting in English)
Hi all! We have good news to share regarding the ongoing problem with graphs and charts affecting all wikis that use them.
As you probably know, theold Graph extension was disabled in 2023due to security reasons. We’ve worked in these two years to find a solution that could replace the old extension, and provide a safer and better solution to users who wanted to showcase graphs and charts in their articles. We therefore developed theCharts extension, which will be replacing the old Graph extension and potentially also theEasyTimeline extension.
After successfully deploying the extension on Italian, Swedish, and Hebrew Wikipedia, as well as on MediaWiki.org, as part of a pilot phase, we are now happy to announce that we are moving forward with the next phase of deployment, which will also include your wiki.
The deployment will happen in batches, and will start fromMay 6. Please, consultour page on MediaWiki.org to discover when the new Charts extension will be deployed on your wiki. You can alsoconsult the documentation about the extension on MediaWiki.org.
If you have questions, need clarifications, or just want to express your opinion about it, please refer to theproject’s talk page on Mediawiki.org, or ping me directly under this thread. If you encounter issues using Charts once it gets enabled on your wiki, please report it on thetalk page or atPhabricator.
Latest comment:abhinc 9 menses1 comment1 person in discussion
The results of voting on the Universal Code of Conduct Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter isavailable on Meta-wiki.
Latest comment:abhinc 8 menses1 comment1 person in discussion
(Apologies for posting in English, if this is not your first language)
Hello all! We opened a discussion on Meta about a very delicate issue for the development ofAbstract Wikipedia: where to store the abstract content that will be developed through functions from Wikifunctions and data from Wikidata. Since some of the hypothesis involve your project, we wanted to hear your thoughts too.
We want to make the decision process clear: we do not yet know which option we want to use, which is why we are consulting here. We will take the arguments from the Wikimedia communities into account, and we want to consult with the different communities and hear arguments that will help us with the decision. The decision will be made and communicated after the consultation period by the Foundation.
This year, the term of 2 (two) Community- and Affiliate-selected Trustees on the Wikimedia Foundation Board of Trustees will come to an end [1]. The Board invites the whole movement to participate in this year’s selection process and vote to fill those seats.
The Elections Committee will oversee this process with support from Foundation staff [2]. The Governance Committee, composed of trustees who are not candidates in the 2025 community-and-affiliate-selected trustee selection process (Raju Narisetti, Shani Evenstein Sigalov, Lorenzo Losa, Kathy Collins, Victoria Doronina and Esra’a Al Shafei) [3], is tasked with providing Board oversight for the 2025 trustee selection process and for keeping the Board informed. More details on the roles of the Elections Committee, Board, and staff are here [4].
Here are the key planned dates:
May 22 – June 5: Announcement (this communication) and call for questions period [6]
June 17 – July 1, 2025: Call for candidates
July 2025: If needed, affiliates vote to shortlist candidates if more than 10 apply [5]
August 2025: Campaign period
August – September 2025: Two-week community voting period
October – November 2025: Background check of selected candidates
Board’s Meeting in December 2025: New trustees seated
Learn more about the 2025 selection process - including the detailed timeline, the candidacy process, the campaign rules, and the voter eligibility criteria - on this Meta-wiki page[link].
Call for Questions
In each selection process, the community has the opportunity to submit questions for the Board of Trustees candidates to answer. The Election Committee selects questions from the list developed by the community for the candidates to answer. Candidates must answer all the required questions in the application in order to be eligible; otherwise their application will be disqualified. This year, the Election Committee will select 5 questions for the candidates to answer. The selected questions may be a combination of what’s been submitted from the community, if they’re alike or related.[link]
Election Volunteers
Another way to be involved with the 2025 selection process is to be an Election Volunteer. Election Volunteers are a bridge between the Elections Committee and their respective community. They help ensure their community is represented and mobilize them to vote. Learn more about the program and how to join on this Meta-wiki page[link].
Latest comment:abhinc 6 menses4 comments2 people in discussion
Hi there,
I am noticing a lot of pages that say that the current version is not checked; and versions I have amended are not (apparently) displayed because they need approval. Am I right in assuming this is due to a lack of (active) administrator time?JimKillock (disputatio)10:53, 30 Maii 2025 (UTC)Reply
Latest comment:abhinc 8 menses8 comments2 people in discussion
Dear all,
Over the past month, with the help of others, I’ve been compiling a list of older and often overlooked books on mnemonic techniques available onWikisource English. Many of these works—some dating back decades or even centuries—offer fascinating insights into how memory has been understood, trained, and improved across different cultures and time periods.
I've recently added a new section to the portal: "Multilingual Works on Mnemonic Techniques." This is in part because several of the English-language texts reference related works in other languages, particularly Latin.
Unfortunately, many of these referenced works are written in Classical Latin, and my ability to work with them is quite limited—I’ve done what I can, but they remain largely inaccessible to me.
If anyone has expertise in Classical Latin and might be willing to help with these texts, your assistance would be greatly appreciated.
I can do the pages you have put into the first, as a start for you. BTW the transcribed text does not always look like it originated from the source. It is very correct, but some has different orthography and missed certain parts. That is fine of course if we are correcting to the original. (PS: you might want to create a user account so that you can be notified of replies, hide your IP address, etc).JimKillock (disputatio)08:57, 15 Iunii 2025 (UTC)Reply
I had a go at the first page or two; some of the orthography was removed while other parts were kept. I kept all of it as a first go. See the discussion above about how we treat orthography, hopefully we can address this with templates.JimKillock (disputatio)09:11, 15 Iunii 2025 (UTC)Reply
I'm using Google OCR and some AI tools to pull out text and sometimes translate it into English so I can understand it. If anyone could help me proofread or check it, I’d be super grateful!82.167.147.500:50, 17 Iunii 2025 (UTC)Reply
I have added all the templates we need for the special characters / orthography, I will start doing the pages with those. The end result will be that on the main space ebook pages, the chars will toggle on and off, at least once that is properly implemented.JimKillock (disputatio)19:25, 17 Iunii 2025 (UTC)Reply
This year, the Wikimedia community will vote in late August through September 2025 to fill two (2) seats on the Foundation Board. Could you – or someone you know – be a good fit to join the Wikimedia Foundation's Board of Trustees? [3]
Learn more about what it takes to stand for these leadership positions and how to submit your candidacy onthis Meta-wiki page or encourage someone else to run in this year's election.
Best regards,
Abhishek Suryawanshi Chair of the Elections Committee
On behalf of the Elections Committee and Governance Committee
A vision of relevant, accessible, and impactful free knowledge has always guided the Wikimedia Movement. As the ecosystem of Wikimedia projects continues to evolve, it is crucial that we periodically review existing projects to ensure they still align with our goals and community capacity.
Despite their noble intent, some projects may no longer effectively serve their original purpose.Reviewing such projects is not about giving up – it's about responsible stewardship of shared resources. Volunteer time, staff support, infrastructure, and community attention are finite, and the non-technical costs tend to grow significantly as our ecosystem has entered a different age of the internet than the one we were founded in. Supporting inactive projects or projects that didn't meet our ambitions can unintentionally divert these resources from areas with more potential impact.
Moreover, maintaining projects that no longer reflect the quality and reliability of the Wikimedia name stands for, involves a reputational risk. An abandoned or less reliable project affects trust in the Wikimedia movement.
Lastly,failing to sunset or reimagine projects that are no longer working can make it much harder to start new ones. When the community feels bound to every past decision – no matter how outdated – we risk stagnation. A healthy ecosystem must allow for evolution, adaptation, and, when necessary, letting go. If we create the expectation that every project must exist indefinitely, we limit our ability to experiment and innovate.
Because of this, SPTF reviewed two requests concerning the lifecycle of the Sister Projects to work through and demonstrate the review process. We chose Wikispore as a case study for a possible new Sister Project opening and Wikinews as a case study for a review of an existing project. Preliminary findings were discussed with the CAC, and a community consultation on both proposals was recommended.
Theapplication to consider Wikispore was submitted in 2019. SPTF decided to review this request in more depth because rather than being concentrated on a specific topic, as most of the proposals for the new Sister Projects are, Wikispore has the potential to nurture multiple start-up Sister Projects.
After careful consideration, the SPTF has decidednot to recommend Wikispore as a Wikimedia Sister Project. Considering the current activity level, the current arrangement allowsbetter flexibility and experimentation while WMF provides core infrastructural support.
We acknowledge the initiative's potential and seek community input on what would constitute a sufficient level of activity and engagement to reconsider its status in the future.
As part of the process, we shared the decision with the Wikispore community and invited one of its leaders, Pharos, to an SPTF meeting.
Currently, we especially invite feedback on measurable criteria indicating the project's readiness, such as contributor numbers, content volume, and sustained community support. This would clarify the criteria sufficient for opening a new Sister Project, including possible future Wikispore re-application. However, the numbers will always be a guide because any number can be gamed.
We chose to review Wikinews among existing Sister Projects because it is the one for which we have observed the highest level of concern in multiple ways.
Since the SPTF was convened in 2023, its members have asked for the community's opinions during conferences and community calls about Sister Projects that did not fulfil their promise in the Wikimedia movement.[1][2][3] Wikinews was the leading candidate for an evaluation because people from multiple language communities proposed it. Additionally, by most measures, it is the least active Sister Project, with the greatest drop in activity over the years.
While the Language Committee routinely opens and closes language versions of the Sister Projects in small languages, there has never been a valid proposal to close Wikipedia in major languages or any project in English. This is not true for Wikinews, where there was a proposal to close English Wikinews, which gained some traction but did not result in any action[4][5], see section 5 as well as a draft proposal to close all languages of Wikinews[6].
Initial metrics compiled by WMF staff also support the community's concerns about Wikinews.
Based on this report, SPTF recommends a community reevaluation of Wikinews. We conclude that its current structure and activity levels are the lowest among the existing sister projects. SPTF also recommends pausing the opening of new language editions while the consultation runs.
SPTF brings this analysis to a discussion and welcomes discussions of alternative outcomes, including potential restructuring efforts or integration with other Wikimedia initiatives.
Options mentioned so far (which might be applied to just low-activity languages or all languages) include but are not limited to:
Restructure how Wikinews works and is linked to other current events efforts on the projects,
Merge the content of Wikinews into the relevant language Wikipedias, possibly in a new namespace,
Merge content into compatibly licensed external projects,
Archive Wikinews projects.
Your insights and perspectives are invaluable in shaping the future of these projects. We encourage all interested community members to share their thoughts on the relevant discussion pages or through other designated feedback channels.
We'd be grateful if you want to take part in a conversation on the future of these projects and the review process. We are setting up two different project pages:Public consultation about Wikispore andPublic consultation about Wikinews. Please participate between 27 June 2025 and 27 July 2025, after which we will summarize the discussion to move forward. You can write in your own language.
I will also host a community conversation 16th July Wednesday 11.00 UTC and 17th July Thursday 17.00 UTC (call links to follow shortly) and will be around at Wikimania for more discussions.
I am thinking about using a bot to wholesale search and replace long s, and other scribal characters mapped there
Between these things, the work to transcribe and correct early printed Latin books should be very much reduced. If anyone feels like helping test this out, do give me shout. Meantime I will run tests on Congestorium Artificiosae Memoriae to check how well the bot system works.JimKillock (disputatio)07:50, 1 Iulii 2025 (UTC)Reply
Latest comment:abhinc 5 menses3 comments2 people in discussion
Hi there,
I would like to do some work on navigation, to provide some "portal" pages similar to EN Wikisource. For example, this would help with learner texts a lot 9I often get asked how to find these texts, I point to the category pages, but these are very basic.
I would also like to know what we should do about page validation. Some really necessary changes are currently languishing in the backlog. This is an admin only task: should we asking for more administrators, or is this something existing admins here can take on?JimKillock (disputatio)14:08, 13 Iulii 2025 (UTC)Reply
HiJimKillock good idea, don't hesitate to start and/or ask for help. That said, I'm not sure to see why this is an admin task (even if, yes, the underlying point is true, we need more admins). Cheers,VIGNERON (disputatio)09:31, 2 Septembris 2025 (UTC)Reply
Latest comment:abhinc 7 menses1 comment1 person in discussion
(Apologies for posting in English, you can help by translating into your language)
Hello everyone, theWikidata For Wikimedia Projects team is excited to announce an upcoming change in how Wikidata edit changelogs are displayed in yourWatchlists andRecent Changes lists. If an edit is made on Wikidata that affects a page in another Wikimedia Project, the changelog will contain some information about the nature of the edit. This can include a QID (or Q-number), a PID (or P-number) and a value (which can be text, numbers, dates, or also QID or PID’s). Confused by these terms? See theWikidata:Glossary for further explanations.
The upcoming change is scheduled for17.07.2025, between1300 - 1500 UTC.The change will display the label (item name) alongside any QID or PIDs, as seen in the image below:
These changes will only be visible if you have Wikidata edits enabled in your User Preferences for Watchlists and Recent Changes, or have the active filter ‘Wikidata edits’ checkbox toggled on, directly on the Watchlist and Recent Changes pages.
Your bot and gadget may be affected! There are thousands of bots, gadgets and user-scripts and whilst we have researched potential effects to many of them, we cannot guarantee there won’t be some that are broken or affected by this change.
Further information and context about this change, including how your bot may be affected can be found on thisproject task page. We welcome your questions and feedback, please write to us on this dedicatedTalk page.
Latest comment:abhinc 6 menses1 comment1 person in discussion
Hello everyone,
(Apologies for posting in English if English is not your first language. Please help translate to your language.)
The Campaigns Product Team is planning a global deployment of theCampaignEvents extension to all Wikisource, including this Wikisource, during theweek of August 25th.
This extension is designed to help organizers plan and manage events, WikiProjects, and other on-wiki collaborations - and to make these efforts more discoverable.
Invitation Lists: A tool to help organizers find editors who might want to join, based on their past contributions.
Note: The extension comes with a new user right called"Event Organizer", which will be managed by administrators on this Wikisource. Organizer tools like Event Registration and Invitation Lists will only work if someone is granted this right. The Collaboration List is available to everyone immediately after deployment.
The extension is already live on several wikis, includingall Wikipedia, Meta, Wikidata, and more ( See the full deployment list)
If you have any questions, concerns, or feedback, please feel free to share them on the extension talkpage. We’d love to hear from you before the rollout.
Temporary accounts are successfully live on 30 wikis, including many large ones like German, Japanese, and French. The change they bring is especially relevant to logged-out editors, who this feature is designed to protect. But it is also relevant to community members like mentors, patrollers, and admins – anyone who reverts edits, blocks users, or otherwise interacts with logged-out editors as part of keeping the wikis safe and accurate.
Why we are building temporary accounts
Our wikis should be safer to edit by default for logged-out editors. Temporary accounts allow people to continue editing the wikis without creating an account, while avoiding publicly tying their edits to their IP address. We believe this is in the best interest of our logged-out editors, who make valuable contributions to the wikis and who may later create accounts and grow our community of editors, admins, and other roles. Even though the wikis do warn logged-out editors that their IP address will be associated with their edit, many people may not understand what an IP address is, or that it could be used to connect them to other information about them in ways they might not expect.
Additionally, our moderation software and tools rely too heavily on network origin (IP addresses) to identify users and patterns of activity, especially as IP addresses themselves are becoming less stable as identifiers. Temporary accounts allow for more precise interactions with logged-out editors, including more precise blocks, and can help limit how often we unintentionally end up blocking good-faith users who use the same IP addresses as bad-faith users.
How temporary accounts work
Any time a logged-out user publishes an edit on this wiki, a cookie will be set in this user's browser, and a temporary account tied with this cookie will be automatically created. This account's name will follow the pattern:~2025-12345-67 (a tilde, current year, a number). On pages like Recent Changes or page history, this name will be displayed. The cookie will expire 90 days after its creation. As long as it exists, all edits made from this device will be attributed to this temporary account. It will be the same account even if the IP address changes, unless the user clears their cookies or uses a different device or web browser. A record of the IP address used at the time of each edit will be stored for 90 days after the edit. However, only some logged-in users will be able to see it.
What does this mean for different groups of users?
For logged-out editors
This increases privacy: currently, if you do not use a registered account to edit, then everybody can see the IP address for the edits you made, even after 90 days. That will no longer be possible on this wiki.
If you use a temporary account to edit from different locations in the last 90 days (for example at home and at a coffee shop), the edit history and the IP addresses for all those locations will now be recorded together, for the same temporary account. Users whomeet the relevant requirements will be able to view this data. If this creates any personal security concerns for you, please contact talktohumanrights at wikimedia.org for advice.
For community members interacting with logged-out editors
A temporary account is uniquely linked to a device. In comparison, an IP address can be shared with different devices and people (for example, different people at school or at work might have the same IP address).
Compared to the current situation, it will be safer to assume that a temporary user's talk page belongs to only one person, and messages left there will be read by them. As you can see in the screenshot, temporary account users will receive notifications. It will also be possible to thank them for their edits, ping them in discussions, and invite them to get more involved in the community.
For users who use IP address data to moderate and maintain the wiki
For patrollers who track persistent abusers, investigate violations of policies, etc.: Users whomeet the requirements will be able to reveal temporary users' IP addresses and all contributions made by temporary accounts from a specific IP address or range (Special:IPContributions). They will also have access to useful information about the IP addresses thanks to theIP Info feature. Many other pieces of software have been built or adjusted to work with temporary accounts, including AbuseFilter, global blocks, Global User Contributions, and more. (For information for volunteer developers on how to update the code of your tools – see the last part of the message.)
For admins blocking logged-out editors:
It will be possible to block many abusers by just blocking their temporary accounts. A blocked person won't be able to create new temporary accounts quickly if the admin selects theautoblock option.
It will still be possible to block an IP address or IP range.
Temporary accounts will not be retroactively applied to contributions made before the deployment. On Special:Contributions, you will be able to see existing IP user contributions, but not new contributions made by temporary accounts on that IP address. Instead, you should use Special:IPContributions for this.
If you want to test the temporary account experience, for example just to check what it feels like, go to testwiki or test2wiki and edit without logging in.
Tell us if you know of any difficulties that need to be addressed. We will try to help, and if we are not able, we will consider the available options.
Look at ourprevious message about requirements for users without extended rights who may need access to IP addresses.
To learn more about the project, check outour FAQ – you will find many useful answers there. You may alsolook at the updates (we have just posted one) andsubscribe to our new newsletter. If you'd like to talk to me (Szymon) off-wiki, you will find me on Discord and Telegram. Thank you!
Latest comment:abhinc 5 menses16 comments4 people in discussion
Hi all, given that we have quite a lot of admin requests (mostly relating to "pending" changes), I would like to request administrator status so that some of these can be cleared. If anyone else wants to step up to help out, that would also be welcome.JimKillock (disputatio)17:23, 1 Septembris 2025 (UTC)Reply
I see... I had a quick look and all changes seem good. Do we even need this extension on Wikisource? Also, if we keep it, I guess we need more reviewers rather than admins (more admins would be useful too, but that's a separate point). Cheers,VIGNERON (disputatio)10:35, 2 Septembris 2025 (UTC)Reply
What do you need us to do? BTW, it would be great to know why edits require administrator approvals. Sorry, but I‘m afraid this makes contributing almost pointless. Many thanks for your help, --Ousia (disputatio)14:15, 3 Septembris 2025 (UTC)Reply
So there are two reasons it would be helpful for me to be an admin; one is if we carry on with the approval system (it looks like we will not) and the other is around updating or adding certain components, modules for example. There may be other tasks I am not aware of that I could help with, but these are the ones I know about. Implementing Portal pages for example needs some work by an admin AIUI.
In terms of what you / others need to do, it seems that if there is a consensus to allow me administrator permissions, then a bueaucrat user would implement it (I mistakenly opening a request at meta, and they referred me back here); so we just need to have your views, yes, no, maybe, etc.JimKillock (disputatio)17:01, 3 Septembris 2025 (UTC)Reply
Thanks, it seems editable now so Iadded my request there, if anyone wants to support it. Regardinggrapheocrates -ae, how is this declined? Is it otherwise treated as a masculine first declension? Thinking it ought to be added to Wiktionary as it is missing from there.JimKillock (disputatio)17:00, 4 Septembris 2025 (UTC)Reply
I don't remember all the details but I worked on that page in the Spanish Wikisource almost a decade ago. I'll make a mockup in the talk page, but I can't promise to get all the Latin words right. For ease, parameter names and help tooltips will be in English internally, but they will show in Latin in the form.Ignacio Rodríguez (disputatio)16:56, 2 Septembris 2025 (UTC)Reply
Latest comment:abhinc 4 menses8 comments5 people in discussion
Hi all,
Moving the discussion regarding the backlog atSpecialis:PendingChanges: @VIGNERON asks whether we need to have this feature. I suspect it was switched on because of spam, vandalism, or some other similar issue. Without it we might need to be keeping an eye on recent changes. I am not sure how the proteccted changes permissions works, or whether permissions to make approvals to changes can be delegated more widely.JimKillock (disputatio)19:56, 2 Septembris 2025 (UTC)Reply
Changes to pages affecting project *function* must be controlled. But it seems that Pending Changes doesn't actually stop changes to something like a template/formula from having effect? See my report about Formula:Sidenotes begin above.
And checking a couple of the other initial items inSpecialis:PendingChanges, it seems that all pending changes are actually immediately applied to active, visible pages.
So Pending Changesdoes not prevent damage to the project. It ismerely a tracking and notification method?
That can be useful, but requires a set of people to be change reviewers. And changes to subject matter would seem to require reviewers knowledgeable about the subject?
And when changes affect *function*, like templates, who can review and approve those? I'd think only admins.
The link to monitoring Recent Changes is undeniable. I monitor Recent Changes often at Spanish Wikisource because I've seen the random damage people can do. That is the only way to react quickly to damage. (?) But then that assumes people are checking lists frequently, at least daily.
Neither Pending Changes or monitoring Recent Changes prevent damage. They can be only part of a solution to damage. I don't know what to think about Pending Changesin isolation.Shenme (disputatio)03:48, 3 Septembris 2025 (UTC)Reply
vandlism is low to inexistant on la.ws (and it's already low on most Wikisources), making this extension useless and even problematic. Because it doesn't prevent changes but it prevents them to be effective.
this extension is actually caleldmw:Extension:FlaggedRevs and it's deprecated for years (seeVicifons:Scriptorium/Vetera_XI#Futrue_of_FlaggedRevs_(Pending_Changes)_extension or the warning on the extension itself « Flagged Revisions is complex, poorly documented, very clunky, and not recommended for production use »). Also, people on Wikisource don't seem to really master or even using it (including the reviewers rights). Maybe it's aan opportunity to list exactly what we need and find a new extension that fit these needs.
In the end, I see a lot of cons and only a few pros...
@JimKillock, @Shenme: many thanks for your replies. I must admit that I’m an occasional Wikisource (or even Wikipedia contributor). I essentially (or exclusively) contribute corrections.
Some days ago, I wanted to download an ePub file for theNoctes Atticae (to do some regexp searches), but the export was wrong. I tried to modify the code (which I have done successfully for the Greek Wikisource many times) and I found out that I needed anihil obstat (I’m afraid this would be way to name it).
Of course, I’m the least interested in vandalism (either contributing it myself, or being any collaborative project being infested/polluted by it). But I think there should be a way of distinguishing between vandalism and non-hardcore (or occasional) contributors.
I don’t know any perfect system, but it should be worth considering a mixed approach. Approval could be required for: already flagged users (for vandalism) and recent users (how about a five-year publishing embargo?).
Only to mention a case, myfirst contribution to the Greek Wiksource was in 2012. I don’t know for how long I have been registered in Wikimedia (I guess this was before 2010).
This isn’t about myself, the issue here is that Wikisource needs contributions to even exist (not to mention for its growth). If no regular user is allowed to contribute without approval, cooperation is basically non-existing.
Even with approval, the reply times are incredibly slow (because of the system). It is not that attention spans are getting shorter, time is the most scarce resource we all are (and I don’t have weeks or months to see whether I’m allowed to haveNoctes Atticae as ePub).
Sorry, the sentence in parentheses isn’t a complaint. Please, do as you please, but my contribution is: consider that you might be making contributions way harder, project growth way slower and administrators’ roles way more complicated (probably, than they could and should be).
This might be the infamous "0x0 bug" that has plagued Wikisource for two? three? years. Normally it resolves doing a purge in both the file page in Commons and in the local Wikisource.Ignacio Rodríguez (disputatio)19:34, 5 Septembris 2025 (UTC)Reply
TheWikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.
All traffic will switch on24 September. The switch will start at15:00 UTC.
Unfortunately, because of some limitations inMediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
A banner will be displayed on all wikis 30 minutes before this operation happens. This banner will remain visible until the end of the operation. You can contribute to thetranslation or proofreading of this banner text.
You will be able to read, but not edit, all wikis for a short period of time.
You will not be able to edit for up to an hour on Wednesday 24 September 2025.
If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
Latest comment:abhinc 3 menses1 comment1 person in discussion
Hello. Please help pick a name for the new Abstract Wikipedia wiki project. This project will be a wiki that will enable users to combine functions fromWikifunctions and data from Wikidata in order to generate natural language sentences in any supported languages. These sentences can then be used by any Wikipedia (or elsewhere).
There will be two rounds of voting, each followed by legal review of candidates, with votes beginning on 20 October and 17 November 2025. Our goal is to have a final project name selected on mid-December 2025. If you would like to participate, thenplease learn more and vote now at meta-wiki.Thank you!
Latest comment:abhinc 3 menses1 comment1 person in discussion
Hi there, @Laura1822 is transcribingLiber:Missale Romanum 1862.djvu, and needs the characters ℣ and ℟ , and ✠ to display for users, when these are in mainspace. We think it may be necessary to use a special / embedded font to do this, as I think was meant for {{blackletter}} (exempli gratia; seeFormula:Blackletter/styles.css, although this does not seem to be calling a font at the moment). Does anyone have any advice about how we would add a webfont to LAWS's CSS, particularly for ℣ and ℟ ; or if there is a way to use an existing webfont with these characters that might be available to us? (Or if there is some other workable solution).JimKillock (disputatio)08:58, 24 Octobris 2025 (UTC)Reply
Applications for the committees open on October 30, 2025. Applications for the Affiliations Committee, Ombuds commission and the Case Review Committee close on December 11, 2025. Learn how to apply byvisiting the appointment page on Meta-wiki. Post to the talk page or email cstwikimedia.org with any questions you may have.
Latest comment:abhinc 2 menses1 comment1 person in discussion
Hello. Reminder: Please help to choose name for the new Abstract Wikipedia wiki project. The finalist vote starts today. The finalists for the name are:Abstract Wikipedia, Multilingual Wikipedia, Wikiabstracts, Wikigenerator, Proto-Wiki. If you would like to participate, thenplease learn more and vote now at meta-wiki.Thank you!
We hope you are doing well, and we wish you a happy New Year.
Last year, we captured light. This year, we’ll capture legacy.
In 2025, communities around the world shared the glow of Ramadan nights and the warmth of collective iftars. In 2026,Wiki Loves Ramadan is expanding, bringing more stories, more cultures, and deeper global connections across Wikimedia projects.
We invite you to explore theWiki Loves Ramadan 2026Meta page to learn how you can participate andsign up your community.
I am writing to you to let you know the annual review period for the Universal Code of Conduct and Enforcement Guidelines is open now. You can make suggestions for changes through 9 February 2026. This is the first step of several to be taken for the annual review.Read more information and find a conversation to join on the UCoC page on Meta.
