Guvans at no ebinoms dunotik dü muls plu 6.Malafaya 12:03, 6 dekul 2007 (UTC)
Veratö... Ab ba mutoy säkön omes, va viloms nog bitön as guvans. Openob bosi su bespikapads omsik (in Vükipeds votik). --Smeira 14:02, 6 dekul 2007 (UTC)
Baicedob. Binos gudikum ad säkön omes, if sevol ladetis omsik. Begö, säkolös. (Pidob pro pük fibik oba:) ) --Malafaya 14:14, 6 dekul 2007 (UTC)
Glidis! This is Jmb. You may remove my admin status if you want. I may be back from time to time to help out with editing pages. Fleniko,Jmb 01:39, 7 dekul 2007 (UTC)
Soäsä pepenos in bespikapad zifa:Hageri, dabinon vo pök in pads anik tefü zifs (vilags) Lestiyänik: num: 58 (u 57 u 59) pekopiedon as lödanef, ab binon te koordinat. Suno odunob klad nulik ad konletön padis labü pök at, kelis poso okoräkob. --Smeira 14:26, 13 dekul 2007 (UTC)
Danö pro plän olik.Malafaya 15:15, 13 dekul 2007 (UTC)
In bespikapad tefüm:Proposals for closing projects/Radical cleanup of Volapük Wikipedia su Meta, ya anikna pesagos, das mutobs bespikön gebi elas bots ad jafön yegedis smalik nulik ("sids", a.s. tefü zifs e vilags). Kisi cedols-li? Stütols-li gebi soik, u taols-li ta on? (Utans, kels vilons gebön pükis votik -- a.s. Linglänapüki -- dalons dunön osi.)
stütob. Nüns in sids at binons nemödiks, ab binons i:
a) verätiks;
b) frutiks;
c) siklopediks (patuvons in Vükipeds votik)
Zuo sids at ai kanons pagretükön fa gebans nitedälöls.
stütob, ab cedob, das mutobs gudikön yegedis at vifik, e ba no jafön yegedis nulik pluik, pato tefü zifs. Mobob ad gudikobs yegedis vipabik e votik, e jafobs pads tefü Vükiped pro Komotanef as dranöf balid.
Lio gudükön onis? I me bots? Me nüns pluik, se Vükipeds votik? (l. sidis se Vükiped Nedänapükik tefü zifs Fransänik, a.s.nl:Buchères) --Smeira 10:07, 28 dekul 2007 (UTC)
Si, me bots u redakams menik. Yegeds Nedänapükik logotons gudik saidik. No glömobsös de gudükön i yegeds votik (a.s. yegeds vipabik e läns).Malafaya 11:20, 28 dekul 2007 (UTC)
Parametis kinik mutoy-li gebön ad sludön, va yeged bal moükabon u no? Kisi cedols-li?Which parameters should we use to decide if an article should be deleted or not? What do you think?
Mob balid: Yegeds miniludik binons uts, kels:First proposal: suspicious articles are those that:
a. klüliko papenons ad nofön votikanis;are obviously written to offend others;
b. binons kopiedots vödemas labü kopiedagitäts;are copies of copyrighted texts;
c. no labons vödemi reidabik (in Volapük ud in pük votik seimik).do not have a readable text (in Volapük or any other language)
Yegeds sömik mutons getön sunädo samafomoti:{{Moükön}}.Such articles must immediately get the template{{Moükön}} (= remove).
Lautans yegedas sömik mutons getön (su bespikapad oksik) nunedi tefü nepöt yegedas oksik.The authors of such articles must immediately get a warning (on their talk pages) about the inappropriateness of their articles.
If lautans steifülons e plöpons ad gudükön yegedis oksik, yegeds ma fomam nulik oksik kanons blibön is.If the authors try and succeed in correcting their articles, then the articles in their new version can stay here.
If lautans no geükons, u no plöpons ad gudükön yegedis oksik, tän yegeds at pamoükons fa bal guvanas pos vig bal.If the authors don't react, or don't succeed in correcting their articles, then these articles are deleted by one of the admins after one week.
What happens if somebody writes an article about, for example, his grandmother? Or about his company, which was founded in 2005 and has 25 employees? In other words, is there some kind of notability guidelines? Which template should be used for such cases instead of the (speedy?){{Delete}}? --145.254.190.21417:53, 2008 yanul 15id (UTC)Reply
We'll in principle follow the usual criteria for notability: if the person's grandmother doesn't happen to be sufficiently famous, or if no one other than the author him/herself can verify the data, then the article will be considered for deletion. But thus far no one has tried to do that; so, in a sense, it is a problem we don't anticipate we'll have any time soon. Hence the absence of a dedicated template. If such a case occurs -- if there's a Volapük speaker who wants to write an article about his/her own non-famous grandmother -- then we'll set policies for dealing with that. For the time being,{{Delete}} will do -- until there really is a of the kind you anticipate, and then new approaches (e.g. new deletion templates) will be developed. --Smeira19:45, 2008 febul 27id (UTC)Reply
Glidis! (Pidob vemo. No-nolob "navigation". I don't know the word for "navigation".) It may worth consideringdisabling (or relegating) the "pad fadik" and replacing it with an index of articles, as in, e.g.; and also consider making the Klads a more prominent means of navigation. This will lead readers to read the good articles; and the relative weight of the retäds would be reduced. -Hillgentleman 19:37, 2 yanul 2008 (UTC)
Glidis! (Navigation = nafam if you use the same maritime metaphor; at least one Volapükist I know doesn't like that and is looking for a less metaphorical description.) I don't see clearly the relation between the description of the use of bots on it.wp and the "pad fädik" link -- isn't it a link on all other Wikipedias? And it can be used for statistical purposes. Now, the idea of making Klads more visible as a navigation tool I find really interesting. How should we do that? (en.wp has only a few links to generic categories on the top of its main page; is this a good way to do that?) --Smeira 01:20, 3 yanul 2008 (UTC)
Glidis! You must have seen: someone comes, "pad fadik" a dozen times, and makes her conclusions. Well, we sometimes browse a dictionary this way, but this is not the best for a project under construction. (And by the way, hasn't Britannica got some one-liner entries? I don't remember.) It is my impression that you would yourself peace and quietous make if you behave professionally. Vukiped is a reference work. Make it useful. A good index is the key. -Hillgentleman 02:08, 3 yanul 2008 (UTC)
We can at least put links to the major categories, major portals, and an index in the most promenant position on the Cifapad. Now, whether that is enough is subjective. The question is what do you want people to see on the Cifapad. Do we want featured articles? perhaps. Do we want links to events happening on that date? And what do we want for the front page? At present, it would be 1. to entice new editors; and 2. to aid site navigation, ie guide the reader quickly to the information he seeks. The question is how to balance them.Hillgentleman 02:17, 3 yanul 2008 (UTC)
Some people also putKlad:Klads on the sidebar. (Langcom did that.)Hillgentleman 02:20, 3 yanul 2008 (UTC)
I basically agree with you. Do you have a suggestion as to a layout? En.wp has a few major categories on the main page and a link to a more detailed categorization. Is this a good idea? (Perhaps not; not very evident.) By the way, how do you add something to the sidebar? --Smeira 16:19, 3 yanul 2008 (UTC)
I have placed a link toKlad:Klads under 'Yegeds mä jäfüds' (= articles by discipline / area of interest / specialization) in the Cifapad. Do you think, Hillgentleman, that this is sufficiently visible? (One problem for newcomers: if they don't speak Volapük, they won't know what the options on the main page link to. Won't they in this case still prefer to go to 'Pads fädik'?) --Smeira 16:24, 3 yanul 2008 (UTC)
I believe a better design of the main page can help even those who do not speak Volapük (those Nuvola icons are really great). Maybe we should develop some proposals for a new main page with a bit more of imagery and more "vivid" colors. I'll look into it when I have a bit of time (weekend?).Malafaya 16:31, 3 yanul 2008 (UTC)
What is this sidebar page? When I click on the link, I get the message that the page was deleted. How come? --Smeira 20:57, 3 yanul 2008 (UTC)
Curious. Apparently this messges is deprecated, it has been deleted from the software but it still has contents?Malafaya 21:35, 3 yanul 2008 (UTC)
This page is in a namespace better know as "mediaWiki:". That is where the sysops can fix their local interface messages (ie without having to hardcode them into the phps.Hillgentleman 22:16, 3 yanul 2008 (UTC)
My opinion: This is an encyclopaedia above all. It would be good to have direct access the entrances to the principal classifications
([+]Lekans[+] Nolavs[+] Rels[+] Sogäd[+] Spot[+] Telplänovapads) If the Klad is too big, create a portal for it and provide link to it instead. One more klickon away is one more chance for confusion. -Hillgentleman 22:23, 3 yanul 2008 (UTC)
The project began in spring 2007. The encyclopedia now has placeholder pages for one million species, of which 30,000 have been populated with detailed information. There are also about a dozen highly developed multimedia pages giving a taster of what to expect in time from the EOL.Hillgentleman
Soäsä kanols reidön in keblünot hiela Timichal löpo, mutobs dunön bosi tefü magods nelibik in Vükiped. Postelspikot ko el Timichal, jinos, das magods te vemo nemödiks in Vükiped binons nelibiks. Äsagom, das kanom dalogön magodis obsik ad tuvön nelibikis e (a) moükön onis u (ä) plaädön onis me magods sümik se Kobädikos. Kisi cedols-li? Cedü ob, mob omik binon legudik! --Smeira20:30, 2008 mäzul 25id (UTC)Reply
Baicedob ko ol. Kobädikos mutonöv binön top balik. Ab sevobs, das en.wp (äsi eo.vp ed i vüks votik) labons nomis tefü "Geb Gidöfik" ("Fair Use"), kelos sinifon, das en.wp, eo.wp e r. kanons gebön magodis, kelis obs no kanobs gebön. Bi Volapük no binon pük netik läna semik, kanobsöv labön, id obs, nomis tefü "Geb Gidöfik". Ab cedob id ob, das Kobädikos binon gudikum. Tefü magods no libiks... Ah! c'est la vie... --Smeira16:30, 2008 mäzul 26id (UTC)Reply
Currently 87.97% of the MediaWiki messages and 57.38% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM10:28, 2008 mayul 17id (UTC)Reply
Currently 85.49% of the MediaWiki messages and 48.17% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM11:59, 2008 yulul 11id (UTC)Reply
Currently 83.68% of the MediaWiki messages and 46.04% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM15:34, 2008 gustul 9id (UTC)Reply
Currently 79.86% of the MediaWiki messages and 42.84% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM11:52, 2008 setul 11id (UTC)Reply
Currently 77.14% of the MediaWiki messages and 40.99% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM10:44, 2008 tobul 18id (UTC)Reply
Currently 77.00% of the MediaWiki messages and 31.78% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM10:10, 2008 novul 11id (UTC)Reply
Currently 75.56% of the MediaWiki messages and 30.86% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising and proof reading atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM12:31, 2008 dekul 15id (UTC)Reply
Currently 96.92% of the MediaWiki messages and 68.13% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising and proof reading atBetawiki. This is therecent localisation activity for your language. Thanks,GerardM21:54, 2009 yanul 12id (UTC)Reply
English: Wikimania 2009, this year's global event devoted toWikimedia projects around the globe, is now acceptingapplications for scholarships to the conference. This year's conference will be handled from August 26-28 inBuenos Aires,Argentina. The scholarship can be used to help offset the costs of travel and registration. For more information, check the officialinformation page. Please remember that theCall for Participation is still open, please submit your papers! Without submissions, Wikimania would not be nearly as fun!
The Wikimeda Movement is in a one year process of strategic planning. Proposals are collected on strategy.wikimedia.org. Your input would be much appreciated. In the current fact finding phase people are looking for drivers of participation. A little research revealed that the Volapük Wikipedia features the greatest number of articles per speaker,see the top line entry in this table. What drives the activity in your community? Please tell us.Dedalus17:59, 2009 gustul 19id (UTC)Reply
Hi, Dedalus. I'm sorry but I didn't understand what you want us to do. You want to know what drives our community. Where should I write that? The links you provided don't seem to be surveys. Cheers,Malafaya10:28, 2009 gustul 20id (UTC)Reply
Hi, Malafaya. Anywhere onthis page, or on the talk page of that page on the strategy wiki. It isn't a survey, though if you browse the pages of the strategy wiki, you'll come across a lot of questions. Your input would be appreciated.Dedalus13:28, 2009 gustul 21id (UTC)Reply
Hello! I am a Polish wikipedian and I would like to ask you for writing a new article about former Polish President who won the Nobel Peace Prize in 1983 –Lech Wałęsa. I have looked for his article in your Wikipedia but without success. Polish Wikipedians will be grateful for your help. Thank you so much in advance! PS article in English you can findhere. Best wishes from Poland,Patrol11019:31, 2009 setul 21id (UTC)Reply
Currently 89.08% of the MediaWiki messages and 30.23% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising and proof reading attranslatewiki.net. This is therecent localisation activity for your language. Thanks,GerardM21:00, 2009 setul 30id (UTC)Reply
Currently 87.75% of the MediaWiki messages and 28.81% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising and proof reading attranslatewiki.net. This is therecent localisation activity for your language. Thanks,GerardM18:33, 2009 novul 1id (UTC)Reply
Currently 89.69% of the MediaWiki messages and 31.69% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising and proof reading attranslatewiki.net. This is therecent localisation activity for your language. Thanks,GerardM14:21, 2009 dekul 14id (UTC)Reply
Currently 88.97% of the MediaWiki messages and 28.41% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising and proof reading attranslatewiki.net. This is therecent localisation activity for your language. Thanks,GerardM14:31, 2010 yanul 25id (UTC)Reply
How can we improve the usability for your language
We expect that with the implementation of LocalisationUpdate the usability of MediaWiki for your language will improve. We are now ready to look at other aspects of usability for your language as well. There are two questions we would like you to answer:Are there issues with the new functionality of the Usability InitiativeDoes MediaWiki support your language properly
The best way to answer the first question is to visit the translatewiki.net. Change the language to your language, select the “vector” skin and add the advanced tool bar in in the preferences and check out the new functionality. And make some changes in your user page. When there is a need to improve on the localisation, please make thenecessary changess . It should update your localisation straight away. We would like you to report each issue individually athttp://meta.wikimedia.org/wiki/Usability_issues.
When there are problems with the support of MediaWiki for your language, we really want to know about this. It is best to report each issue separately. In this way there will be no large mass of issues to resolve but we can address each issue on its own. Consider issues with the display of characters, the presentation of your script, the position of the side bar, the combination of text with other languages, scripts. It is best to try this in an environment like the prototype wiki as it provides you with a clean, basic and up to date environment. The prototype wiki is available for five languages but you can select any of them, change the preferences to your language and test out MediaWiki for your language.
We would like you to report each issue individually athttp://meta.wikimedia.org/wiki/Languageissues. The issues you raise will all be assessed. It is important to keep each issue separate, because this will make it easier to understand the issues and find solutions.
Many of the most active editors on this wiki are bots. As a learner of Volapük I'd like to volunteer so that more oversight can be given. I runvolapuk.com and am working on a number of Volapük publications.Evertype17:36, 2012 yanul 22id (UTC)Reply
You have my support since you are a very active member of the Volapük community. Unfortunately, I'm not too active here andGeban:Smeira is missing in action. It would be great if someone could give this project a kick up. Let's just wait a few days for other (if any) voices to be heard.Malafaya17:12, 2012 yanul 23id (UTC)Reply
The Wikimedia Foundation has brought together a new team of developers who are dedicated to language support. This team is to support all the languages and consequently it is not realistic to expect that the team members can provide proper support for your language. It is for this reason that we are looking for volunteers who will make up alanguage support team.
This language support team will be asked to provide us with information about their language. Such information may need to be provided either to us or on a website that we will indicate to you. Another activity will be to test software that will likely have an effect on the running of the MediaWiki software. We are looking for people who clearly identify their ability. Formal knowledge is definitely appreciated.
Hello. It seems to me, having looked at the morphology of Volapük, that the name of this wikipedia is badly formed. The first two letters,vü , are confusable with a preposition meaning "between" (corresponding to the prefix "inter-"), the last two letters,ed, are confusable with a common suffix, and the word as a whole is further blighted by the fact that the middle three letters,kip, are confusable with a root meaning "keep/retain". The word is thus highly ambiguous, and I wonder if it shouldn't be replaced. I understand there is a procedure for word coining whereby the Academy (theKadäm) is consulted and then makes a decision. And I wonder who the person was who invented the word "Vükiped", and whether he/she had any contact with the Academy.
Hi. I don't have a clue. The word had already been adopted when I first came here. Let me just tell you that just because words seem to be composed of known prefixes/suffixes doesn't mean they are not allowed. In Volapük there are many words that start that way, with particles that match prefixes, and yet morphologically they are not prefixes: for example, "jied" (a bad concept for an example, I know:)) is not composed of prefix "ji-" and suffix "-ed". Regards,Malafaya (talk)14:30, 2013 yanul 29id (UTC)Reply
Hi. This is because not all MediaWiki messages are translated. This is mainly because MediaWiki is not static and is continuously evolving. Thus, it's not easy to keep pace:).Malafaya (talk)13:26, 2013 yulul 12id (UTC)Reply
Hi, I have translated this book list --en:Le Monde's 100 Books of the Century -- into 30 or 40 natural languages. I thought I would try 2 artificial languages, Volapük and Esperanto. (The only artificial language I know is Nadsat, fromA Clockwork Orange.) What would be a good title for the page when I finish compiling the list? Le Monde is the newspaper in Paris. Thanks very much,Varlaam (talk)19:25, 2013 yulul 5id (UTC)Reply
But I don't trust this word "Calanem". It matches the German "Titel", but Titel has more than one meaning. And "calanem" is never actually used in vowiki.
I'm not sure that "Calanem" is correct, but it does seem to mean title. It might be a different sense of the word. Can someone confirm that "calanem" is correct?PiRSquared17 (talk)21:41, 2013 yulul 16id (UTC)Reply
Hello, Sorry for English but It's very important for bot operators so I hope someone translates this.Pywikipedia is migrating to Git so after July 26, SVN checkouts won't be updated If you're using Pywikipedia you have to switch to git, otherwise you will use out-dated framework and your bot might not work properly. There is amanual for doing that and ablog post explaining about this change in non-technical language. If you have question feel free to ask inmw:Manual talk:Pywikipediabot/Gerrit,mailing list, or in theIRC channel. BestAmir(viaGlobal message delivery).13:55, 2013 yulul 23id (UTC)Reply
Hello. A new policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc) was recently adopted byglobal community consensus (your community received a notice about the discussion). According to this policy, thestewards are reviewing administrators' activity on smaller wikis. 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 the newadmin activity review here.
We have determined that the following users meet the inactivity criteria (no edits and no log actions for more than 2 years):
Flauto Dolce (bureaucrat, administrator)
ILVI (administrator)
Manie (bureaucrat, administrator)
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,Rschen775400:29, 2014 prilul 6id (UTC)Reply
Hello and sorry for writing in English. Can anyone help me translate a small article (2 paragraphs) from English to your language and create the article in your wiki? Please, fell free to answer in my talk page in your wiki anytime. Thanks!Xaris333 (talk)00:33, 2014 gustul 13id (UTC)Reply
Hello. A new policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc) was adopted byglobal community consensus in 2013. According to this policy, thestewards are reviewing administrators' activity on smaller wikis. 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 log actions for more than 2 years):
Evertype (administrator)
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,Rschen775419:57, 2015 yanul 31id (UTC)Reply
De geban ela 151.20.4.40: I need to speak to an admin, may I ask you? It's about the problem of the article "Portobuffolé": it was disussed both in en.wikipedia and in it.wikipedia about the correct spelling, and it was established that it must have the acute accent. The following are some of the sources brought in the discussions, proving the correct spelling:. They're the most authoritative dictionaries and encyclopedias about Italian language and they all agree about the spelling. Also almost all other Wikis have already changed the uncorrect spellings, but there's a Dutch admin/rollbacker who's going against consensus and moving back a lot of pages on several Wikis to the uncorrect spelling, in this way actually vandalising the Wiki-pedia. Can you please move once for all the page "Portobuffolè" to "Portobuffolé", or delete the page "Portobuffolè" with the uncorrect spelling, please? If an admin of vo.wikipedia does it, this could prevent the Dutch rollbacker from keeping this senseless edit-war. Thank you in advance if you will!Robert (bespik)14:14, 2016 yanul 22id (UTC)Reply
Hi. I can see that this project has old JavaScript that needs to be updated. I would happily make the required updates myself, but I would have to – at least temporarily – become an admin here to do that (because the relevant pages are in the MediaWiki namespace). I have already made these updates on a number of other projects, so it would be very easy for me to do this. If no one does anything, some JavaScript-related tools will break later this year. If you want me to make these updates, you can grant me admin rights and I will make the updates as soon as I can.Nirmos (bespik)21:45, 2016 yunul 8id (UTC)Reply
Hello. A new policy regarding the removal of "advanced rights" (administrator, bureaucrat, etc) was adopted byglobal community consensus in 2013. According to this policy, thestewards are reviewing administrators' activity on smaller wikis. 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 log actions for more than 2 years):
Smeira (bureaucrat, administrator)
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,Rschen775406:55, 2016 yulul 15id (UTC)Reply
Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, 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 log actions for more than 2 years):
Evertype (administrator)
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,علاء (bespik)07:12, 2018 yulul 1id (UTC)Reply
Dear people, I've seen a lot of categories appearing under the titles "Moteds in XXXX" and "Deadams in XXXX". Unless I am gravely mistaken, this is incorrect in Volapük:in always refers to a place. When it refers to a year,ün should be used. In other words: "Moteds ün XXXX" or "Moteds ün yel XXXX". Regards,IJzeren Jan (bespik)15:54, 2019 yanul 24id (UTC)Reply
Hello. A policy regarding the removal of "advanced rights" (administrator, bureaucrat, 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 log actions for more than 2 years):
Evertype (administrator)
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,علاء (bespik)06:55, 2021 yanul 8id (UTC)Reply
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,علاء (bespik)10:36, 2022 yanul 4id (UTC)Reply
This is not really an opinion, but let me ask: why do you want this status if you don't use it anyway? I mean, not every admin has to be there 24/7, but ten small edits in more than eight years? A whole box full of stuff that was submitted for immediate deletion a long time ago but is still lingering? Don't get me wrong, I appreciate the work you've been doing here, but it seems like you haven't been really active here since 2010.IJzeren Jan (bespik)23:24, 2022 yanul 20id (UTC)Reply
My intention was to keep at least an administrator in this project. But as you are coming forward as a candidate, I truly don't need to keep admin status, and I surely endorse your candidacy.Malafaya (bespik)11:59, 2022 febul 4id (UTC)Reply
Keep I am probably the only active person here on Vükiped, I'm in favor of the user keeping the admin rights.Łukasz Winek (bespik) 21:57, 2022 yanul 14id (UTC) I'm withdrawing support. In my opinion, an active person should be an admin. Best regards,Łukasz Winek (bespik)12:40, 2022 yanul 21id (UTC)Reply
Malafaya, I am not against prolongation of your admin rights, but I would appreciate it if you'd at least answer the question I asked you. Will you at least be available once or twice a month to do some minimal maintenance and respond to questions? If so, then you have my support.IJzeren Jan (bespik)16:49, 2022 yanul 30id (UTC)Reply
I'd like to request admin status on this wiki. I am aware of the fact that due to my rather demanding job I haven't been too active here during the last two years, but I still care a lot for the Vükiped, check up on it regularly and I keep having the feeling that it needs work. I've been participating here since 2005 (modestly, I admit), written a few articles myself and made nearly 2000 edits here. In general, I have been active on Wikipedia as a registered user since 2004, I have been a moderator and Arbcom member of nlwiki. At many occasions, I have considered requesting adminship here, but I simply don't feel like going through the same bureaucratic procedure every three months. Now I understand that permanent adminship is also possible here, and that made me decide to give it a try after all. And I encourageŁukasz Winek to do the same: the more admins here the merrier.
What I'd really like to do is creating some order here, because at present, the Vükiped is in a deplorable state. Sergio Meira's past actions (creating massive amounts of bot-generated articles 15 years ago) have been successful in so far that Volapük made it into the top-10 of biggest Wikipedia editions for a while, which generated lots of attention from various sides, and fortunately, Vükiped survived efforts to have it closed. However, currently there is another problem, namely that at least 99.5% of the ca. 127K articles we have here are either generated by a bot or human-written oneliners of the type"[X] is a [Y] from [Z]" or"[X] is a [Y] in [Z]".
I am aware of the fact that this wiki is not primarily a place where Volapük speakers will be looking for information, but rather a place for showcasing Volapük itself. Since almost every article follows literally the same format, we are doing a poor job at that. Most bot-generated articles are completely outdated by now. And "real" articles with some critical mass (let's say: at least a few sentences written in decent Volapük, not counting infoboxes and the like) are almost impossible to find. The size of this wiki makes it practically unmanageable. My personal opinion is that Vükiped would be a lot better off with 500 real articles, but the least we can (and should) do is to find a way to distinguish them from the rest, for example by creating a special category, or by moving everything that does not meet certain criteria to a draftspace, or by deleting everything that has never been touched by a human hand, so to speak. Anyway, as far as there is still a community left over here, I'd like to have a discussion about these things.
I absolutely endorse your candidacy as an administrator on this wiki, and thank you for encouraging me to do so. As for changes to this wiki, they are necessary - incl. on the home page, which has not been updated for many years. Changes should be necessary in some articles (I'm not saying that in all of them), especially those concerning countries of the world - they should be longer and contain specific information (an example of this isRumän). In short, there is a lot to do here. Yours sincerely,Łukasz Winek (bespik)22:13, 2022 yanul 29id (UTC)Reply
Thank you! Indeed, the main page desperately needs work.Geban:Malafaya, would it be possible to unlock it, so that other users can work on it as well? And Łukasz, what would you suggest we could to to make this wiki somewhat more manageable? Cheers,IJzeren Jan (bespik)16:43, 2022 yanul 30id (UTC)Reply
Slopob (support). E baiädob das mutoy dunön bosi ko vükiped at, ab duliunam u topätükam yegedas 127000 jinon vobod nemögik. Vio vilol jenöfükön atosi?Nüm bal (bespik)09:22, 2022 febul 9id (UTC)Reply
Danö! Ogespikob linglänapüko, bi Volapükinol oba binon pestöböl. Tikob reto, das dabinanef isik suemon linglänapüki gudikumo.
I know, it's complicated. Doing everything manually will be practically impossible and I have no experience whatsoever with handling a bot. For now, I've been going through the 10,000largest articles in size and found ca. 150 truly presentable, human-written articles (interestingly, about 15% of them are about the Volapük movement and 30% of them are about paleontology, mostly dinosaurs). All remaining articles are either bot-generated articles about French and American towns and villages, a few of them are lists. Unfortunately, the list of long articles doesn't go further than 10,000 (which equals 2,318 characters), whereas a decent article in Volapük without an infobox can very well have 1,000 characters.
Bot-generated articles are not necessarily a bad thing as long as they don't obscure the real articles. But right now, we have no less than 104,586 articles about cities, towns and villages (including 36,512 in France, 28,944 in the USA and 12,068 in Germany), virtually all of which are clones of each other. Some of them have technical mistakes (likethis one that may never even have been noticed by anyone. And although articles likethis orthis actually look quite nice, is it really necessary for us to have the same text here 29K times? My suggestion would be to leave a few of these per country (say, only a few big cities) and delete the rest. I think a bot would be able to handle that. Cheers,IJzeren Jan (bespik)13:44, 2022 febul 9id (UTC)Reply
I would also be in favor of such a solution (although I could leave them all out of sentiment). I would suggest creating an infobox for cities, towns and villages (and if necessary - updating templates starting with "topam" - from this category:), because looking at articles about cities (even in these words made by me) - it does not look very good. This is my opinion. Yours sincerely,Łukasz Winek (bespik)20:40, 2022 febul 9id (UTC)Reply
Hehe, I absolutely share that sentiment, that's why I would definitely not delete all of them, but just 99% or so (which would still leave us with over a thousand). And yes, I started with one of those myself as well, before I even knew the basics of Volapük. But look at it from the positive side: the absence of an article might actually inspire someone to create it and thus learn about the language. And let's also consider that these articles no longer fulfill their original purpose: generating lots of attention for Volapük. BTW, I agree about the infobox, I'll try to make one. Which BTW is one more reason to delete articles that don't contain any information that isn't already contained in the infobox. Cheers,IJzeren Jan (bespik)22:28, 2022 febul 9id (UTC)Reply
Dear all, it has been about five months since I became admin of this Wikipedia. As you may have noticed, I have reworked theMain Page, which hadn't been updated since about 13 years. My idea was to use a colour scheme more suitable for Volapük, a new featured article every day and a new featured image every week. Of course, ideas for further improvement are more than welcome! Besides, I have deleted some 10,000 pages, most of which were bot-generated microstubs, bot-generated pages with serious technical errors and broken redirects.
But instead of turning this into an admin report, there's something I'd like to hear opinions of others about. During the last few days, I have deleted over 2,500 towns in Romania, almost all of which were generated by Smeirabot. Going through each and every one of them, I noticed how problematic these things really are:
Only 11 of the bot-generated articles had ever been edited by a human (by adding an image, an external link or a link to Commons). One other one contained a heavily racist slur added some 12 years ago by an anonymous vandal (something like "All niggers must be killed").
About 5% of them had technical problems: links to non-existing images, pieces of unnecessarily copied Romanian text, wikicode errors, incorrectly copied data (f.ex. over 100,000 inhabitants for some hellhole with no inhabitants at all), etc.
For practically all of them goes that data are 20 years old.
What is worse: every single one of them is calledzif ("city, town"), even when there are less than ten inhabitants. In other words, the bot didn't distinguish betweenzif,vilag andkomot ("municipality"). I found the same mistake in the case of Dutch towns as well: municipalities consisting of a number of small villages were consistently called "zif". This is problematic, because it renders the information in these bot-generated articles utterly unreliable. Of course, one might argue: who cares, nobody comes here looking for information about Romanian villages anyway. My opinion is that there is no place here for information that is not just obsolete, but also seriously flawed.
So the question is: what shall we do about that? I was thinking about carrying on withKlad:Zifs_in_Jveizän (towns in Switzerland), but here we have the same problem: the 2653 towns listed here are in fact municipalities. Of course, many of them have an eponymous town in them, but not necessarily so. And besides, you can't tell me that atown with 104 inhabitants really deserves the name "zif". One solution could be to change the word "zif" to "komot" in every article. But not only would it be a hell of a job to do that manually, it also wouldn't solve the problem of maintainability, nor will it keep those articles from getting more and more outdated. Besides, the bot made other mistakes here as well. For example,Oberwil is said to have 10 inhabitants, although in reality is has over 11,000. Changing everything to "X binon komot in Jveizän" and having an infobox do the rest could solve that problem, but it would still leave us with 2653 articles that are merely clones of each other.
All in all, I can see three serious options here:
Delete all of them.
Delete everything with less than 10,000 inhabitants.
Delete everyting that hasn't been edited by anyone.
Thank you, that's pretty much what I had in mind myself as well. Deleting everything would go a bit too far IMO, but 10,000 should be a reasonable criterion that leave with something but not too much. I will delete all towns with less than 10,000 inhabints and leave those that have been edited by someone.
And what to do with towns in other countries? The ca. 4500 articles about places in Estonia distinguish correctly between towns and villages, but the number is still way too high. Same goes for Germany, Italy, France, Brazil and the USA.IJzerenJan18:16, 2022 yulul 24id (UTC)Reply
Indeed. as you can see, I have started with Estona. Estonia is a small country with not too many cities and towns, so I am currently deleting everything with less than 1000 inhabitants that hasn't been edited by anyone. The vast majority are villages with less than 100 inhabitants.IJzerenJan19:01, 2022 yulul 25id (UTC)Reply
Estonia is done: from 4656 to 129 articles. Pretty decent, I believe. Romania and Switzerland are done, too. I'll try to make a beginning with Germany. There we have 12.061 articles. Same problem as in Switzerland: everything is called a "zif", even though it may as well be a (former) municipality or a village. I guess I'll follow the same approach as in the case of Switzerland: delete everything with less than 10,000 inhabitants, unless the article has been edited by someone, and unless the article is linked to from another article.IJzerenJan13:01, 2022 yulul 27id (UTC)Reply
Beg tefü lunükam guvanistadi oba / Request for prolongation of my admin status
O valikans löfik! Bü yel ze bal pecalob ad guvan ela ,Wikipedia’ Volapükik pro tüp mö yel. Vütimo edunob mödikosi: staböfiko ecenob logoti cifapada ed esteifülob ad dunön bosi tefü mödot lemuik yegedas itjäfidiko pijafädölas, brefiko: esteifülob ad vedükön eli ,Wikipedia’ at ini bos, demü kelos Volapükan alik kanonöv pleidön. Ye dins mödik eretöns ad dunön is. Ibä calam obik ofinon suno, me at begob stüti olsik pro dönudaväl oma pro tüp sököl mö yel. Ladöfiko,IJzerenJan00:00, 2023 febul 9id (UTC)Reply
Dear all! Almost a year ago I became a moderator on the Volapük Wikipedia. In the meantime, I have done a lot: I have thoroughly modified the appearance of the main page and done my best to do something about the extreme predominance of bot-generated articles, in short: tried to make this Wikipedia into something to be proud of. Yet, there still is a lot to be done here. Since my term is going to end soon, I am hereby asking for your support for a prolongation of one more year. Sincererily,IJzerenJan00:00, 2023 febul 9id (UTC)Reply
The Volapük Wikipedia does not have any „featured articles”, but we do have a few „good articles” in the categoryYegeds gudik. These are, basically, the articles we can be most proud of. A good article does not necessarily have to be bigger than in other language versions, but it should be at least be reasonably complete, be nicely illustrated, and be written in correct Volapük. Good articles are marked by a star that is also visible in the equivalent articles in other languages and thus might attract some attention from outside. At present, this category contains 15 items, of which the last one has been added some ten years ago. In the meantime, I think a few newer articles have been created that might qualify as well:
If there are no objections, I will give them a star one of these days. And if any of you have ideas for more articles, don't hesitate to nominate them by adding them to the list!IJzerenJan23:59, 2023 mäzul 22id (UTC)Reply
I support this initiative. They are well written and I believe that, after what happened with this Wikipedia regarding its quality of content, having more quality articles is a good sign and a way to prove that there are people working to improve it.Caro de Segeda (bespik)06:35, 2023 mäzul 23id (UTC)Reply
Beg tefü lunükam guvanistadi oba / Request for prolongation of my admin status
Dear all,I just noticed that my adminship is about to expire. It's sad enough, but it seems to be impossible to obtain permanent adminship, so every year we'll have to go through the same circus again. Any objections against prolongation of my adminship of the Volapük Wikipedia. Cheers,IJzerenJan19:39, 2024 febul 15id (UTC)Reply
Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.
Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. Follow their work onMeta-wiki.
Apologies, as this message is not in your native language;Please help translate to your language.
TheWMF Language team proposes to enable the Section and Content translation tool by default to your Wikipedia if there are no objections from members of your community. TheSection Translation extends the capabilities ofContent Translation to support mobile devices. Below is background information about the tools and how to test the Section translation tool.
Background information
Content Translation has been a successful tool for editors to create content in their language. More than one million articles have been created across all languages since the tool was released in 2015. However, the tool is not out of beta in Volapük Wikipedia, limiting the discoverability of the tool and its use and blocking the enablement of the Section translation in your Wikipedia.
Section Translation extends the capabilities of Content Translation to support mobile devices. On mobile, the tool will:
Guide you to translate one section at a time to expand existing articles or create new ones
Make it easy to transfer knowledge across languages anytime from your mobile device
So, we will enable the tools on Volapük Wikipedia by June 20th, 2024, if there are no objections from your community.
Try the Section translation tool
Before the enablement, you can try the current implementation of the tool inour testing instance. Once it is enabled in your Wikipedia, you’ll have access tohttps://vo.wikipedia.org/wiki/Special:ContentTranslation with your mobile device. You can select an article and translate it from scratch. Currently, there is no machine translation support for your Wikipedia. Often, this is due to the lack of parallel data to train translation models for your language. Considering that making translations of Wikipedia articles isa way to generate such parallel corpora, we consider that enabling these tools by default for visibility and more use can benefit your language.
Request for feedback
Please provide feedback about the Section translation in this thread or onthis project talk page. We want to hear about your impressions on
The section translation tool
What do you think about our plans to enable it
Your ideas for improving the tool
Thanks, and we look forward to your feedback and questions.
The final text of theWikimedia Movement Charter is now up on Meta in more than 20 languages for your reading.
What is the Wikimedia Movement Charter?
The Wikimedia Movement Charter is a proposed document to define roles and responsibilities for all the members and entities of the Wikimedia movement, including the creation of a new body – the Global Council – for movement governance.
Join the Wikimedia Movement Charter “Launch Party”
Join the“Launch Party” onJune 20, 2024 at14.00-15.00 UTC (your local time). During this call, we will celebrate the release of the final Charter and present the content of the Charter. Join and learn about the Charter before casting your vote.
The voting to ratify theWikimedia Movement Charter is now open. The Wikimedia Movement Charter is a document to define roles and responsibilities for all the members and entities of the Wikimedia movement, including the creation of a new body – the Global Council – for movement governance.
Voting commenced on SecurePoll onJune 25, 2024 at00:01 UTC and will conclude onJuly 9, 2024 at23:59 UTC. Please read more on thevoter information and eligibility details.
After reading the Charter, pleasevote here and share this note further.
If you have any questions about the ratification vote, please contact the Charter Electoral Commission atcec@wikimedia.org.
A special election has been called to fill additional vacancies on the U4C. The call for candidates phase is open from now through July 19, 2024.
TheUniversal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of theUCoC. Community members are invited to submit their applications in the special election for the U4C. For more information and the responsibilities of the U4C, please review theU4C Charter.
In this special election, according tochapter 2 of the U4C charter, there are 9 seats available on the U4C:four community-at-large seats andfive regional seats to ensure the U4C represents the diversity of the movement.No more than two members of the U4C can be elected from the same home wiki. Therefore, candidates must not have English Wikipedia, German Wikipedia, or Italian Wikipedia as their home wiki.
Read more and submit your application onMeta-wiki.
After carefully tallying both individual and affiliate votes, theCharter Electoral Commission is pleased to announce the final results of the Wikimedia Movement Charter voting.
Ascommunicated by the Charter Electoral Commission, we reached the quorum for both Affiliate and individual votes by the time the vote closed onJuly 9, 23:59 UTC. We thank all 2,451 individuals and 129 Affiliate representatives who voted in the ratification process. Your votes and comments are invaluable for the future steps in Movement Strategy.
The final results of theWikimedia Movement Charter ratification voting held between 25 June and 9 July 2024 are as follows:
Individual vote:
Out of 2,451 individuals who voted as of July 9 23:59 (UTC), 2,446 have been accepted as valid votes. Among these,1,710 voted “yes”;623 voted “no”; and113 selected “–” (neutral). Because the neutral votes don’t count towards the total number of votes cast, 73.30% voted to approve the Charter (1710/2333), while 26.70% voted to reject the Charter (623/2333).
Affiliates vote:
Out of 129 Affiliates designated voters who voted as of July 9 23:59 (UTC), 129 votes are confirmed as valid votes. Among these,93 voted “yes”;18 voted “no”; and18 selected “–” (neutral). Because the neutral votes don’t count towards the total number of votes cast, 83.78% voted to approve the Charter (93/111), while 16.22% voted to reject the Charter (18/111).
I am writing to you to let you know the voting period for the Universal Code of Conduct Coordinating Committee (U4C) is open now throughAugust 10, 2024. Read the information on thevoting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, pleasereview the U4C Charter.
Please share this message with members of your community so they can participate as well.
The voting period for the Universal Code of Conduct Coordinating Committee (U4C) is closing soon. It is open through 10 August 2024. Read the information onthe voting page on Meta-wiki to learn more about voting and voter eligibility. If you are eligible to vote and have not voted in this special election, it is important that you vote now.
Why should you vote? The U4C is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community input into the committee membership is critical to the success of the UCoC.
Please share this message with members of your community so they can participate as well.
Hello. For many years, community members have requested an easy way to re-use references with different details. Now, a MediaWiki solution is coming: The new sub-referencing feature will work for wikitext and Visual Editor and will enhance the existing reference system. You can continue to use different ways of referencing, but you will probably encounter sub-references in articles written by other users. More information onthe project page.
We want your feedback to make sure this feature works well for you:
Sign up here to get updates and/or invites to participate in user research activities.
Wikimedia Deutschland’sTechnical Wishes team is planning to bring this feature to Wikimedia wikis later this year. We will reach out to creators/maintainers of tools and templates related to references beforehand.
The next language community meeting is scheduled in a few weeks—on August 30th at 15:00 UTC. If you're interested in joining, you cansign up on this wiki page.
This participant-driven meeting will focus on sharing language-specific updates related to various projects, discussing technical issues related to language wikis, and working together to find possible solutions. For example, in the last meeting, topics included the Language Converter, the state of language research, updates on the Incubator conversations, and technical challenges around external links not working with special characters on Bengali sites.
Do you have any ideas for topics to share technical updates or discuss challenges? Please add agenda items to the documenthere and reach out to ssethi(__AT__)wikimedia.org. We look forward to your participation!
I am pleased to announce the following individual as regional members of the U4C, who will fulfill a term until 15 June 2026:
North America (USA and Canada)
Ajraddatz
The following seats were not filled during this special election:
Latin America and Caribbean
Central and East Europe (CEE)
Sub-Saharan Africa
South Asia
The four remaining Community-At-Large seats
Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.
Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. You can follow their work onMeta-Wiki.
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 on25 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 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 onWednesday 25 September 2024.
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.
Apologies for cross-posting in English. Please consider translating this message.Samafomot:Tracked
Hello everyone, a small change will soon be coming to the user-interface of your Wikimedia project.TheWikidata itemsitelink currently found under theGeneral section of theTools sidebar menu will move into theIn Other Projects section.
We would like the Wiki communities feedback so please let us know or ask questions on theDiscussion page before we enable the change which can take place October 4 2024, circa 15:00 UTC+2.More information can be found onthe project page.
Apologies for writing in English. Please help to translate in your language.We are excited to announce the upcomingWiki Loves Ramadan event, a global initiative aimed at celebrating Ramadan by enriching Wikipedia and its sister projects with content related to this significant time of year. As we plan to organize this event globally, your insights and experiences are crucial in shaping the best possible participation experience for the community.
To ensure that Wiki Loves Ramadan is engaging, inclusive, and impactful, we kindly invite you to participate in our community engagement survey. Your feedback will help us understand the needs of the community, set the event's focus, and guide our strategies for organizing this global event.
TheContribute entry point is based on collaborative work with other product teams in the Wikimedia Foundation onEdit discovery, which validated the entry point as a persistent and constant path that contributors took to discover ways to contribute content in Wikipedia.
Therefore, enabling this entry point in your Wikipedia will help contributors quickly discover available tools and immediately click to start using them. This entry point is designed to be a central point for discovering contribution tools in Volapük Wikipedia.
Who can access it
Once it is enabled in your Wikipedia, newcomers can access the entry point automatically by just logging into their account, click on the User drop-down menu and choose the "Contribute" icon, which takes you to another menu where you will find a self-guided description of what you can do to contribute content, as shown in the image below. An option to "view contributions" is also available to access the list of your contributions.
For experienced contributors, the Contribute icon is not automatically shown in their User drop-down menu. They will still see the "Contributions" option unless they change it to the "Contribute" manually.
This feature is available in four Wikipedia (Albanian, Malayalam, Mongolian, and Tagalog). We have gotten valuable feedback that helped us improve its discoverability. Now, it is ready to be enabled in other Wikis. One major improvement was tomake the entry point optional for experienced contributors who still want to have the "Contributions" entry point as default.
We plan to enable iton mobile for Wikis, where the Section translation tool is enabled. In this way, we will provide a main entry point to the mobile translation dashboard, and the exposure can still be limited by targeting only the mobile platform for now. If there are no objections to having the entry point for mobile users from your community, we will enable it by 24th October 2024.
We welcome your feedback and questions in this thread on our proposal to enable it here. Suppose there are no objections, we will deploy the "Contribute" entry point in your Wikipedia.
While these candidates have been ranked through the vote, they still need to be appointed to the Board of Trustees. They need to pass a successful background check and meet the qualifications outlined in the Bylaws. New trustees will be appointed at the next Board meeting in December 2024.
Applications for the committees open on 16 October 2024. Applications for the Affiliations Committee close on 18 November 2024, and applications for the Ombuds commission and the Case Review Committee close on 2 December 2024. Learn how to apply byvisiting the appointment page on Meta-wiki. Post to the talk page or emailcst@wikimedia.org with any questions you may have.
Hello everyone, I previously wrote on the 27th September to advise that theWikidata item sitelink will change places in the sidebar menu, moving from theGeneral section into theIn Other Projects section. The scheduled rollout date of 04.10.2024 was delayed due to a necessary request for Mobile/MinervaNeue skin. I am happy to inform that the global rollout can now proceed and will occur later today, 22.10.2024 at 15:00 UTC-2.Please let us know if you notice any problems or bugs after this change. There should be no need for null-edits or purging cache for the changes to occur. Kind regards, -Danny Benjafield (WMDE)11:29, 2024 tobul 22id (UTC)Reply
Final Reminder: Join us in Making Wiki Loves Ramadan Success
We’re thrilled to announce the Wiki Loves Ramadan event, a global initiative to celebrate Ramadan by enhancing Wikipedia and its sister projects with valuable content related to this special time of year. As we organize this event globally, we need your valuable input to make it a memorable experience for the community.
Last Call to Participate in Our Survey: To ensure that Wiki Loves Ramadan is inclusive and impactful, we kindly request you to complete our community engagement survey. Your feedback will shape the event’s focus and guide our organizing strategies to better meet community needs.
Please take a few minutes to share your thoughts. Your input will truly make a difference!
Volunteer Opportunity: Join the Wiki Loves Ramadan Team! We’re seeking dedicated volunteers for key team roles essential to the success of this initiative. If you’re interested in volunteer roles, we invite you to apply.
This participant-driven meeting will be organized by the Wikimedia Foundation’s Language Product Localization team and the Language Diversity Hub. There will be presentations on topics like developing language keyboards, the creation of the Moore Wikipedia, and the language support track at Wiki Indaba. We will also have members from the Wayuunaiki community joining us to share their experiences with the Incubator and as a new community within our movement. This meeting will have a Spanish interpretation.
We’re happy to announce the launch ofWiki Loves Ramadan 2025, an annual international campaign dedicated to celebrating and preserving Islamic cultures and history through the power of Wikipedia. As an active contributor to the Local Wikipedia, you are specially invited to participate in the launch.
This year’s campaign will be launched for you to join us write, edit, and improve articles that showcase the richness and diversity of Islamic traditions, history, and culture.
To get started, visit thecampaign page for details, resources, and guidelines: Wiki Loves Ramadan 2025.
Addyour community here, and organized Wiki Loves Ramadan 2025 in your local language.
Whether you’re a first-time editor or an experienced Wikipedian, your contributions matter. Together, we can ensure Islamic cultures and traditions are well-represented and accessible to all.
Feel free to invite your community and friends too. Kindly reach out if you have any questions or need support as you prepare to participate.
Apologies, as this message is not written in your native language.Please help translate to your language.
TheWikimedia Foundation Web team will be enablingdark mode here on your Wikipedia by February 2025 now that pages on your wiki have passed our checks for accessibility and other quality checks. Congratulations!
The plan to enable is made possible by the diligent work of editors and other technical contributors in your community who ensured that templates, gadgets, and other parts of pages can be accessible in dark mode. Thank you all for making dark mode available for everybody!
For context, the Web team has concluded work on dark mode. If, on some wikis, the option is not yet available for logged-out users, this is likely because many pages do not yet display well in dark mode. As communities make progress on this work, we enable this feature on additional wikis once per month.
If you notice any issues after enabling dark mode, please create a page:Reading/Web/Accessibility for reading/Reporting/xx.wikipedia.org in MediaWiki (like these pages), and report the issue in the created page.
My apologies for writing in English.Please help translate to your language.
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 3 February 2025. 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.
You are humbly invited to organize theFeminism and Folklore 2025 writing competition from February 1, 2025, to March 31, 2025 on your local Wikipedia. This year, Feminism and Folklore will focus on feminism, women's issues, and gender-focused topics for the project, with aWiki Loves Folklore gender gap focus and a folk culture theme on Wikipedia.
You can help Wikipedia's coverage of folklore from your area by writing or improving articles about things like folk festivals, folk dances, folk music, women and queer folklore figures, folk game athletes, women in mythology, women warriors in folklore, witches and witch hunting, fairy tales, and more. Users can help create new articles, expand or translate from a generated list of suggested articles.
Organisers are requested to work on the following action items to sign up their communities for the project:
Create a page for the contest on the local wiki.
Set up a campaign onCampWiz tool.
Create the local list and mention the timeline and local and international prizes.
This year, the Wiki Loves Folklore Tech Team has introduced two new tools to enhance support for the campaign. These tools include theArticle List Generator by Topic andCampWiz. The Article List Generator by Topic enables users to identify articles on the English Wikipedia that are not present in their native language Wikipedia. Users can customize their selection criteria, and the tool will present a table showcasing the missing articles along with suggested titles. Additionally, users have the option to download the list in both CSV and wikitable formats. Notably, the CampWiz tool will be employed for the project for the first time, empowering users to effectively host the project with a jury. Both tools are now available for use in the campaign.Click here to access these tools
Learn more about the contest and prizes on ourproject page. Feel free to contact us on ourmeta talk page or by email us if you need any assistance.
Dear Wiki Community,You are humbly invited to participate in theWiki Loves Folklore 2025 an international media contest organized on Wikimedia Commons to document folklore and intangible cultural heritage from different regions, including, folk creative activities and many more. It is held every year from the1st till the 31st of March.
You can help in enriching the folklore documentation on Commons from your region by taking photos, audios, videos, andsubmitting them in this commons contest.
You can alsoorganize a local contest in your country and support us in translating theproject pages to help us spread the word in your native language.
Feel free to contact us on ourproject Talk page if you need any assistance.
My apologies for writing in English.Please help translate to your language.
This is a reminder that the first phase of the annual review period for the Universal Code of Conduct and Enforcement Guidelines will be closing soon. You can make suggestions for changes throughthe end of day, 3 February 2025. 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. After review of the feedback, proposals for updated text will be published on Meta in March for another round of community review.
Please share this information with other members in your community wherever else might be appropriate.
We’re excited to announce that the nextLanguage Community Meeting is happening soon,February 28th at 14:00 UTC! If you’d like to join, simply sign up on thewiki page.
This is a participant-driven meeting where we share updates on language-related projects, discuss technical challenges in language wikis, and collaborate on solutions. In our last meeting, we covered topics like developing language keyboards, creating the Moore Wikipedia, and updates from the language support track at Wiki Indaba.
Got a topic to share? Whether it’s a technical update from your project, a challenge you need help with, or a request for interpretation support, we’d love to hear from you! Feel free toreply to this message or add agenda items to the documenthere.
Also, we wanted to highlight that the sixth edition of the Language & Internationalization newsletter (January 2025) is available here:Wikimedia Language and Product Localization/Newsletter/2025/January. This newsletter provides updates from the October–December 2024 quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and ideas for contributing to projects. To stay updated, you can subscribe to the newsletter on its wiki page:Wikimedia Language and Product Localization/Newsletter.
We look forward to your ideas and participation at the language community meeting, see you there!
Apologies as this message is not in your language,Please help translate to your language.
TheLanguage and Product Localization team has improved theContent Translation dashboard to create a consistent experience for all contributors using mobile and desktop devices. The improved translation dashboard allows all logged-in users of the tool to enjoy a consistent experience regardless of their type of device.
With a harmonized experience, logged-in desktop users now have access to the capabilities shown in the image below.
Notice that in this screenshot, the new dashboard allows: Users to adjust suggestions with the "For you" and "...More" buttons to select general topics or community-created collections (like the example of Climate topic). Also, users can use translation to create new articles (as before) and expand existing articles section by section. You can see how suggestions are provided in the new dashboard in two groups ("Create new pages" and "Expand with new sections")-one for each activity.In the current dashboard, you will notice that you can't adjust suggestions to select topics or community-created collections. Also, you can't expand on existing articles by translating new sections.
We will implementthis improvement on your wikion Monday, March 17th, 2025 and remove the current dashboardby May 2025.Please reach out with any questions concerning the dashboard in this thread.
Thank you!
On behalf of the Language and Product Localization team.
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 onWednesday 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.
Wikimedia Ukraine, in cooperation with theMFA of Ukraine andUkrainian Institute, has launched the fifth edition of writing challenge "Ukraine's Cultural Diplomacy Month", which lasts from14th April until16th May 2025. The campaign is dedicated to famous Ukrainian artists of cinema, music, literature, architecture, design, and cultural phenomena of Ukraine that are now part of world heritage. We accept contributions in every language!
The most active contesters will receive prizes.
If you are interested in coordinating long-term community engagement for the campaign and becoming a local ambassador, we would love to hear from you! Please let us know your interest.
We invite you to take part and help us improve the coverage of Ukrainian culture on Wikipedia in your language! Also, we plan to set up abanner to notify users of the possibility to participate in such a challenge!OlesiaLukaniuk (WMUA) (talk)
16:11, 2025 prilul 16id (UTC)
Vote now on the revised UCoC Enforcement Guidelines and U4C Charter
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.
Get a sneak peak and help shape theVisual Editor user designs
Help us test the new design prototypes by participating in user sessions –sign up here to receive an invite. We're especially hoping to speak with people from underrepresented and diverse groups. If that's you, please consider signing up! No prior or extensive editing experience is required. User sessions will startMay 14th.
We plan to bring this feature to Wikimedia wikis later this year. We’ll reach out to wikis for piloting in time for deployments. Creators and maintainers of reference-related tools and templates will be contacted beforehand as well.
Thank you very much for your support and encouragement so far in helping bring this feature to life!
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.
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.
(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].
(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 Wikipedias, including this wiki, during theweek of June 23rd.
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 wiki. 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, includingMeta, Wikidata, English Wikipedia, 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.
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.
(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.
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!
Hello everyone! I am glad to inform you that as the next step in theParser Unification project, Parsoid will soon be turned on as the default article renderer on your wiki. We are gradually increasing the number of wikis using Parsoid, with the intention of making it the default wikitext parser for MediaWiki's next long-term support release. This will make our wikis more reliable and consistent for editors, readers, and tools to use, as well as making the development of future wikitext features easier.
If this disrupts your workflow, don’t worry! You can still opt out through a user preference or turn Parsoid off on the current page using the Tools submenu, as described in theExtension:ParserMigration documentation.
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 onWednesday 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.
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!
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.
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!
.png)
